Rational Developer for System z

Setting preferences for the CICS XML Transformation Assistant (XSDBind)

To set preferences for the CICS® XML Transformation Assistant (XSDBind), open the XML Assistant (XSDBind) page in the Enterprise Service Tools preferences. These options affect the generated XSDBind and language structure files.

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.

To set preferences for the XML Transformation Assistant (XSDBind):
  1. On the workbench menu bar, select Window > Preferences. The Preferences window opens.
  2. In the left pane of the Preferences window, expand Enterprise Service Tools and select XML Transformation Assistant (XSDBind).
  3. Change the preferences (the preferences are described in the following sections).
  4. Click OK when done.

The XML transformation assistant

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 XML transformation assistant is invoked by the following wizards or utilities in the Enterprise Service Tools: Again, the XML transformation assistant is invoked only when generating output files for the XML Transformation for CICS runtime environment.
The XML transformation assistant includes two procedures, DFHLS2SC and DFHSC2LS:
The XML transformation assistant is invoked whether you select compiled runtime XML conversion or interpretive runtime XML conversion (see Runtime XML conversion: compiled or interpretive). The type of XSDBind file generated depends on the type of runtime XML conversion that you select:

Preferences on the Common tab

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):

Mapping level: (This is displayed in the XML Transformation Assistant as the parameter: MAPPING-LEVEL)
Specifies the version of the programmatic interface shared between CICS and the application. Generally, it is best to specify the highest mapping level that is available. Mapping levels 1.0 to 1.2 are supported in CICS TS 3.1 and later with APAR PK23547 applied. Mapping levels 1.0 to 2.1 are supported in CICS TS 3.2 and later with APAR PK59794 applied. The use of old mapping levels is only recommended when regenerating the XML binding files for services that were previously deployed with an old mapping level. The details on the mapping levels can be found in the online CICS Transaction Server Infocenter, see:
1.0
This is the CICS runtime default mapping level. For more information on mapping levels see CICS TS 4.1 documentation at:

https://publib.boulder.ibm.com/infocenter/cicsts/v4r1/topic/com.ibm.cics.ts.webservices.doc/concepts/dfhws_utility.html

or

CICS® Transaction Server for z/OS, Version 4 Release 1 Information Center

1.1
Use this mapping level if you need to regenerate a binding file at this specific level.
1.2
This mapping level provides the following features:
  • It enables the Char varying parameter on the DFHLS2SC tab and the DFHSC2LS tab of the preferences.
  • It supports VARYING and VARYINGZ arrays,
Note: Mapping level 1.2 requires APAR PK23547.
2.0
Use this mapping level for CICS TS 3.2.

For more information on mapping levels see CICS TS 4.1 documentation at: https://publib.boulder.ibm.com/infocenter/cicsts/v4r1/topic/com.ibm.cics.ts.webservices.doc/concepts/dfhws_utility.html

or

CICS® Transaction Server for z/OS, Version 4 Release 1 Information Center

2.1
Use this mapping level for CICS TS 3.2 and later with APAR PK59794 applied. At this level you can use the following features:

Support has been added for xsd:any and xsd:anyType (for DFHSC2LS), see:https://publib.boulder.ibm.com/infocenter/cicsts/v4r1/topic/com.ibm.cics.ts.applicationprogramming.doc/datamapping/dfhws_anytypesupport.html

or

CICS® Transaction Server for z/OS, Version 4 Release 1 Information Center

2.2
Use this mapping level with a CICS TS 3.2 region that has APAR PK69738 applied. Mapping level 2.2 provides the following support:
  • Elements with fixed values
  • Enhanced support for <xsd:choice> elements
  • Abstract data types
  • Abstract elements
  • Substitution groups
3.0
Use this mapping level for CICS TS 4.1.
Minimum runtime level: (This is displayed in the XML Transformation Assistant as the parameter: MINIMUM-RUNTIME-LEVEL)
This preference specifies the minimum CICS runtime environment that the XML binding file can be deployed into. An error message is displayed if you select a level that does not match the other parameters that you have specified.

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.

MINIMUM
The lowest possible runtime level of CICS is allocated automatically given the parameters that you have specified.
3.0
The generated XML binding file deploys successfully into CICS TS 4.1
CURRENT
The generated XML binding file deploys successfully into a CICS region at the highest available runtime level as the one you are using to generate the XML binding file.
CCSID: (This is displayed in the XML Transformation Assistant as the parameter: CCSID)

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).

Data Truncation: (This is displayed in the XML Transformation Assistant as the parameter: DATA-TRUNCATION)
Selecting this option specifies how the CICS native conversion mechanism handles truncated data. When set to ENABLED, then CICS accepts truncated aplicatoin data and assumes that missing data is set to nulls. The ENABLED setting is only supported at mapping levels 3.0 and higher. When set to DISABLED, then CICS rejects truncated application data and sends an error message. The default value is DISABLED.

Preferences on the DFHLS2SC tab

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.

Char varying: (This is displayed in the XML Transformation Assistant as the parameter: CHAR-VARYING)
This preference specifies how character arrays in the language structure are mapped when the mapping level is 1.2 or higher.
Note: This preference does not apply to Enterprise and Other PL/I language structures.
NO
Character arrays are mapped to an xsd:string and are processed as fixed length fields. The maximum length of the data is equal to the length of the array.
NULL
Character arrays are mapped to an xsd:string and are processed as null-terminated arrays. CICS adds a terminating null character when transforming from a SOAP message. The maximum length of the character string is calculated as one character less than the length indicated in the language structure.
COLLAPSE
Generate XML character data description with the whiteSpace attribute set to "collapse". This value is only available at mapping levels of 1.2 and higher. This value is the default for mapping levels 2.1 and higher.
BINARY
Any character arrays defined in the language structure are mapped to fixed length xsd:base64Binary fields in the WSDL rather than to xsd:string fields.
Date/Time: (This is displayed in the XML Transformation Assistant as the parameter: DATETIME)
This preference specifies XML elements are mapped in a bottom-up scenario and is only valid for the CICS interpretive type (this preference is ignored for the vendor compiled conversion type). Selecting this option specifies how the XML elements of xsd:dateTime type are mapped into CICS ASKTIME format. The valid values are PACKED15 or UNUSED.
Note: This preference is only available at mapping level 3.0 and higher.

Preferences on the DFHSC2LS tab

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.

Char varying: (This is displayed in the XML Transformation Assistant as the parameter: CHAR-VARYING)
This preference specifies how variable length character data is mapped when the mapping level is 1.2. Variable length binary data types are always mapped to either a container or a varying structure. If you do not specify this parameter, the default mapping depends on the language specified.
NO
Variable length character data is mapped as fixed length strings.
NULL
Variable length character data is mapped to null terminated strings.
YES
Variable length character data is mapped to a Char varying data type in PL/I. In the COBOL, C and C++ languages, variable length character data is mapped to an equivalent representation that composed of two related elements, data length and the data.
Char varying limit: (This is displayed in the XML Transformation Assistant as the parameter: CHAR-VARYING-LIMIT)
This preference specifies the maximum size of binary data and variable length character data that is mapped to the language structure when the mapping level is 1.2. The value can range from 0 to 32767 bytes. The default value is 32767 bytes.

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.

Default char max length: (This is displayed in the XML Transformation Assistant as the parameter: DEFAULT-CHAR-MAXLENGTH)
This preference specifies the default array length of character data in characters for mappings where no length is implied in the Web service description document, when the mapping level is 1.2. The value can be a positive integer in the range of 1 to 2147483647.
Char multiplier: (This is displayed in the XML Transformation Assistant as the parameter: CHAR-MULTIPLIER)
This preference specifies the number of bytes to allow for each character when the mapping level is 1.2. The value of this parameter can be a positive integer in the range of 1 to 2147483647. All nonnumeric character-based mappings, are subject to this multiplier. Binary, numeric, zoned and packed decimal fields are not subject to this multiplier.

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.

Inline maxOccurs limit: (This is displayed in the XML Transformation Assistant as the parameter: INLINE-MAXOCCURS-LIMIT)
The value specified by this preference is used to decide whether or not to in-line variable repeating content based on the value of the maxOccurs attribute from the source XML Schema. For a full description see:
Date/Time: (This is displayed in the XML Transformation Assistant as the parameter: DATETIME)
This preference specifies XML elements are mapped in a top-down scenario and is only valid for the CICS interpretive type (this preference is ignored for the vendor compiled conversion type). Selecting this option specifies how the XML elements of xsd:dateTime type are mapped into CICS ASKTIME format. The valid values are PACKED15 or UNUSED.
Note: This preference is only available at mapping level 3.0 and higher.

Terms of use | Feedback

This information center is powered by Eclipse technology. (http://www.eclipse.org)