Example 1

If the formlibrary is located under (SDF)SCREENDESIGN/BANKAPP ON PACK1, sign on with the SDF usercode and use the following CANDE statement  to generate the SDF XML output file from the formlibrary based on the default behavior for the type of form processing that is done by the formlibrary:

RUN $SYSTEM/EPORTAL/SDFXMLEXTRACTOR ("T27XMLEXTRACT");
FILE DICTIONARY (FILENAME = SCREENDESIGN);
FILE FORMLIBRARY (FILENAME = BANKAPP);
FILE RESULTS (LTITLE = SDFXML/"BANKAPP.XML");

The SDF XML output file is found at (SDF)SDFXML/"BANKAPP.XML" on PACK1.

If the formlibrary processes forms based on the message keys, the page identification region or regions are generated from the default value (transaction code) for the Message Key field of each form. If the form library does not process forms based on the message keys, the page identification region or regions are generated from the literal text of the form.

Example 2

If the formlibrary of Example 1 processes forms based on the message keys and the page identification region or regions should be generated using the literal text of the form, use the following CANDE statement  to generate the SDF XML output file:

RUN $SYSTEM/EPORTAL/SDFXMLEXTRACTOR ("T27XMLEXTRACT, UNIQUE=LITERALTEXT");
FILE DICTIONARY (FILENAME = SCREENDESIGN);
FILE FORMLIBRARY (FILENAME = BANKAPP);
FILE RESULTS (LTITLE = SDFXML/"BANKAPP.XML");

The SDF XML output file is found at (SDF)SDFXML/"BANKAPP.XML" on PACK1.

The page identification region or regions are generated from the literal text of the form.

Example 3

If no page identification region or regions should be generated, use the following CANDE statement to generate the SDF XML output file:

RUN $SYSTEM/EPORTAL/SDFXMLEXTRACTOR ("T27XMLEXTRACT, UNIQUE=NONE");
FILE DICTIONARY (FILENAME = SCREENDESIGN);
FILE FORMLIBRARY (FILENAME = BANKAPP);
FILE RESULTS (LTITLE = SDFXML/"BANKAPP.XML");

The SDF XML output file is found at (SDF)SDFXML/"BANKAPP.XML" ON PACK1.

The page identification region or regions are not generated from the forms. Refer to Planning the Data Identification Strategy in Preparing to Capture the Screens of T27 Applications to determine your strategy for identifying pages.

Example 4

To generate one output file for each form in the formlibrary, use the following CANDE statement:

RUN $SYSTEM/EPORTAL/SDFXMLEXTRACTOR ("T27XMLEXTRACT, SEPARATE=TRUE");
FILE DICTIONARY (FILENAME = SCREENDESIGN);
FILE FORMLIBRARY (FILENAME = BANKAPP);
FILE RESULTS (LTITLE = SDFXML/BANKAPP");

If the formlibrary contains 3 forms called customer, account, and transaction, the generated SDF XML output files are:

(SDF)SDFXML/BANKAPP/"CUSTOMER.XML" ON PACK1
(SDF)SDFXML/BANKAPP/"ACCOUNT.XML" ON PACK1
(SDF)SDFXML/BANKAPP/"TRANSACTION.XML" ON PACK1

If the formlibrary processes forms based on the message keys, the page identification region or regions are generated from the default value (transaction code) for the Message Key field of each form. If the form library does not process forms based on the message keys, the page identification region or regions are generated from the literal text of the form.

Example 5

If the formlibrary is in the coded character set JAPANV24JBIS8, but the HOSTCCS setting of the MCP is not set to JAPANV24JBIS8, then you must specify the optional INTMODE attribute of the FORMLIBRARY to JAPANV24JBIS8 in order to create the XML output file. If the formlibrary is located under (SDF)SCREENDESIGN/BANKAPP ON PACK1, sign on with the SDF usercode and use the following CANDE statement to generate the SDF XML output file from the formlibrary, based on the default behavior for the type of form processing that is done by the formlibrary.

RUN $SYSTEM/EPORTAL/SDFXMLEXTRACTOR ("T27XMLEXTRACT");
FILE DICTIONARY (FILENAME = SCREENDESIGN);
FILE FORMLIBRARY (FILENAME = BANKAPP, INTMODE=JAPANV24BISB8);
FILE RESULTS (LTITLE = SDFXML/BANKAPP.XML");

The SDFXML output file is found at (SDF)SDFXML/"BANKAPP.XML" on PACK1.

If the formlibrary processes forms based on the message keys, then the page identification regions are generated from the default value (transaction code) for the Message Key field of each form. If the formlibrary does not process forms based on the message keys, then the page identification region or regions are generated from the literal text of the form.