Setting preferences for the CICS XML Transformation Assistant (XSDBind)

Edit online

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

In the left pane of the Preferences window, expand Enterprise Service Tools and select XML Transformation Assistant (XSDBind).
Change the preferences (the preferences are described in the following sections).
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 V5.2 or later, 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:

Create New XML Transformation (bottom-up) wizard
Create New XML Transformation (top-down) wizard
Command-line batch processor (see Batch processor)
Note: The Map an Existing Service Interface (meet-in-middle) wizard is not supported.

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:

DFHLS2SC generates an XML schema and an XML binding file from a high level language data structure.
DFHSC2LS: generates a high level language data structure(s) and an XML binding file from either (1) an XML schema or (2) the types section of a WSDL file.

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:

A Native-interface XSDBind file is generated if you select interpretive runtime XML conversion.
A Vendor-interface XSDBind file is generated if you select compiled runtime XML conversion.

Limitation: XMLCP of DFHLS2SC is not supported.

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)

This preference specifies the version of the programmatic interface shared between CICS and the application (see CICS® Transaction Server for z/OS®, Version 5 Release 4 IBM® Documentation). 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 with APAR PK23547 applied.
Mapping levels 1.0 to 2.1 are supported in CICS TS 3.2 with APAR PK59794 applied.
Mapping levels 1.0 to 2.2 are supported in CICS TS 3.2 with APAR PK69738 applied.
Mapping levels 1.0 to 3.0 are supported in CICS TS 4.1.
Mapping levels 1.0 to 4.0 are supported in CICS TS 5.2.
Mapping levels 1.0 to 4.1 are supported in CICS TS 5.3 with APAR PI67641 applied.

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.

1.0

This is the CICS runtime default mapping level.

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.

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:

INLINE-MAXOCCURS-LIMIT
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).

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.

4.0

Use this mapping level with a CICS TS 5.2 region or later. At this level, the following features are available:

DFHLS2SC and DFHLS2WS support the COBOL OCCURS DEPENDING ON clause and also supports mapping of COBOL character arrays into XML strings. You can set this behavior by using the CHAR-OCCURS parameter on the CICS assistants.
CICS web services support the conversion of application data that is encoded using UTF-16 Unicode.

For more information, see Mapping levels for the CICS assistants.

4.1

Use this mapping level with a CICS TS 5.3 region with APAR PI67641 or later. With this runtime level, the following features are available:

TRUNCATE-NULL-ARRAYS and TRUNCATE-NULL-ARRAY-VALUES parameters are supported by DFHLS2SC, DFHLS2WS, and DFHLS2JS.

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
4.0: The generated web service binding file deploys successfully into a CICS TS 5.2 region or later. With this runtime level, you can use a mapping level of 4.0 or earlier for the MAPPING-LEVEL parameter.
4.1: The generated web service binding file deploys successfully into a CICS TS 5.3 region or later. With this runtime level, you can use a mapping level of 4.1 or earlier for the MAPPING-LEVEL parameter.
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 application 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.

Data screening: (This is displayed in the XML Transformation Assistant as the parameter:DATA-SCREENING)

Select this option to specify whether application supplied data is screened for errors. When it is set to ENABLED, any application-supplied runtime data that is inconsistent with the language structure, is treated as an error and message DFHPI1010 is issued. An error response is returned to the application. When set to DISABLED, data values in application-supplied runtime data that are inconsistent with the language structure are replaced by default values.

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.

Char occurs: (This is displayed in the XML Transformation Assistant as the parameter: CHAR-OCCURS)

This preference specified how character arrays in the language structure are mapped when the mapping level is 4.0 or higher. For example, PIC X OCCURS 20 . This parameter is only for use by the COBOL language.

ARRAY
Character arrays are mapped to an XML array, which means that every character is mapped as an individual XML element. This also applies on the behavior at mapping levels 3.0 and earlier.
STRING
This option is default. Character arrays are mapped to an XML string, which means that the entire COBOL array is mapped as a single XML element.

Char usage: (This is displayed in the XML Transformation Assistant as the parameter: CHAR-USAGE)

In COBOL, the national data type, PIC N, can be used for UTF-16 or DBCS data. This setting is controlled by the NSYMBOL compiler option. You must set the CHAR-USAGE parameter on the assistant to the same value as the NSYMBOL compiler option to ensure that the data is handled appropriately. This is typically set to CHAR-USAGE=NATIONAL when you use UTF-16.

DBCS
Data from PIC ( n ) fields is treated as DBCS encoded data.
NATIONAL
This is the default value. Data from PIC ( n ) fields is treated as UTF-16 encoded data.

Truncate null arrays: (This is displayed in the XML transformation Assistant as the parameter TRUNCATE-NULL-ARRAYS)

This preference specifies how structured arrays are processed. If enabled, CICS will attempt to recognize empty records within an array.

Truncate null array values: (This is displayed in the XML transformation Assistant as the parameter TRUNCATE-NULL-ARRAY-VALUES)

This preference specifies which values are treated as empty for TRUNCATE-NULL-ARRAYS processing. If all of the bytes of storage in a record of a structured array contain nulls, the entire record is considered to be empty. One or more of the NULL, SPACE and ZERO values can be specified in a list separated by commas.

NULL
0x00, or low-values is treated as empty
SPACE
0x40 is treated as empty
ZERO
0xF0 is treated as empty

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:

Variable arrays of elements

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.

Name truncation: (This is displayed in the XML Transformation Assistant as the parameter: NAME-TRUNCATION)

This preference specifies how a generated field name is shortened if it is too long for use in the specified high-level language. This option is available at all mapping levels.

RIGHT: This is the default value. The field name is truncated from the right and a numeric suffix is added if necessary.
LEFT: The field name is truncated from the left and a numeric suffix is added if necessary.

31 - digit decimal support: (This is displayed in the XML Transformation Assistant as the parameter: WIDE-COMP3)

This preference controls the maximum size of the pack decimal variable length that is mapping to a COBOL Language structure. If set to YES, it will use 31 digits for DECIMAL and INTEGER types. If set to NO (default), the number of digits remains at 18. This option is available at all mapping levels.

Less duplicate names (This is displayed in the XML Transformation Assistant as the parameter: LESS-DUP-NAMES)

For PL/I only. This parameter generates non-structural structure field names with _value at the end of the name to enable direct referencing to the field. The suffix _value is appended only when there is a name conflict between the structural name and non-structural name.

Underscores as hyphens (This is displayed in the XML Transformation Assistant as the parameter: UNDERSCORES-AS-HYPHENS)

For COBOL only. This parameter converts any underscores in the WSDL document to hyphens, rather than the character X, to improve the readability of the generated COBOL language structures. If any field name clashes occur, the fields are numbered to ensure they are unique.

Hyphen as underscores: (This is displayed in the XML Transformation Assistant as the parameter: HYPHEN-AS-UNDERSCORES)

For PL/I only. This parameter converts any hyphens in the WSDL document to underscores rather than the character X, to improve the readability of the generated PL/I language structures. This option is not selected by default.

Default fraction digits: (This is displayed in the XML Transformation Assistant as the parameter: DEFAULT-FRACTGION-DIGITS)

This parameter specifies the default number of fraction digits to use in the JSON decimal schema type. The default value is 3. For COBOL, the valid range is 0 to 17, or 0 to 30 if parameter WIDE-COMP3 is being used. For C or PL/I, the valid range is 0 to 30.