Use this form set level rule when the extract list loaded by the transaction contains the name of an external file source for the XML tree.
Note | The extract list and the XML tree are separate items. Even if you are only using an XML file as the source of the transaction, there will be two copies of the information in memory — one as the extract list and one as the XML tree. |
For the parameter, you can use one of the following:
Where filename is the name of the XML file, including path information.
Where group and option are defined in the INI files
Parameter |
Description |
offsetofmask |
the offset of the search mask |
offsetofdata |
the offset where the path and the file name start |
lengthofdata |
the length of the file name |
Where globalvariablename is the name of a GVM that contains the file name.
Here are examples of how you can use this rule:
;XMLFileExtract;2;FILE=SAMPCO.XML;
;XMLFileExtract;2;INI=Group,Option;
;XMLFileExtract;2;SCH=11,FILENAME 20,20;
;XMLFileExtract;2;GVM=FileNameVar;
Keep in mind...
< RunMode >
XMLExtract = Yes
;LoadExtractData;;
;XMLFileExtract;2;FILE=SAMPCO.XML;
For single or two-step mode, place the XMLFileExtract rule after the NoGenTrnTransactionProc rule, as shown here:
;NoGenTrnTransactionProc;;
;XMLFileExtract;2;FILE=SAMPCO.XML;
To preserve the space when mapping data, use two exclamation marks (!!). Otherwise, the system assumes it should remove the leading white space.
© Copyright 2014, Oracle and/or its affiliates. All rights reserved. Legal notices.