These preferences affect the generation of resources only when you are generating files for the XML Transformation for CICS runtime environment. These preferences do not affect the generation of resources for the other runtime environments.
The preferences on this page affect the values that the Enterprise Service Tools passes as input parameters to the XML transformation assistant. The XML transformation assistant is a set of batch utilities, provided in CICS Transactions Server V4.1, that generate necessary for creating a new CICS XML Transformation service.
The preferences on the Common tab are passed to the XML transformation assistant no matter which runtime scenario you select (bottom-up, meet-in-middle, top-down) and no matter which runtime XML conversion type you select (compiled or interpretive):
The use of old mapping levels is recommended only when regenerating the XML binding files for XML transformation resources that were previously deployed with an old mapping level (see CICS® Transaction Server for z/OS, Version 4 Release 1 Information Center).
See the description of the Inline maxOccurs limit preference on the DFHSC2LS tab (see Inline maxOccurs limit).
Support has been added for the XML schema element <xsd:any> and the data type xsd:anyType (for DFHSC2LS) (see Support for <xsd:any> and xsd:anyType).
The value that you select for this preference is used only if you also select interpretive runtime XML conversion. If you select compiled runtime XML conversion, then the Enterprise Service Tools wizard or utility always sets the minimum runtime level to VENDOR.
Specifies the CCSID that is used at run time to encode data between the application program and the XML binding file. The value of this parameter overrides the value of the LOCALCCSID system initialization parameter. The value must be an EBCDIC CCSID that is supported by Java™ and z/OS conversion services. If you do not specify this parameter, the application program uses the CCSID specified in the system initialization parameter, and the XML binding file is encoded in US EBCDIC (Cp037).
The preferences on the DFHLS2SC tab are passed to the XML transformation assistant only when the scenario type is Create New Service Interface (bottom-up) and the runtime XML conversion type is interpretive. (The batch processor equivalent of Create New Service Interface (bottom-up) is the EISService element.)
These preferences are not enabled if the option selected in Mapping level list box or the Minimum runtime level list box on the Common tab does not support them.
The preferences on the DFHSC2LS tab are passed to the XML transformation assistant only when the scenario type is Create New XML Transformation (top-down)and the runtime XML conversion type is interpretive. (The batch processor equivalent of Create New XML Transformation (bottom-up is the EISServiceImplementation element.)
These preferences are not enabled if the option selected in Mapping level list box or the Minimum runtime level list box on the Common tab does not support them.
If the character or binary data is larger than the value specified in this parameter, it is mapped to a container and the container name is used in the generated language structure.
This parameter can be useful if, for example, you are planning to use DBCS characters where you could opt for a multiplier of 3 to allow space for potential shift-out and shift-in characters around every double byte character at run time.