Bottom-up wizard - Interpretive XML Conversion

Edit online

Use the Create New Service Interface (bottom-up) wizard with Interpretive XML Conversion to generate files in supported runtime environments.

Overview of bottom-up (interpretive) wizard pages

Edit online

This topic provides an overview of the pages in the wizards with interpretive XML conversion.

For this wizard and conversion type, Web Services for CICS® and XML Transformation for CICS are the only runtimes supported.

Table 1 summarizes the pages and tabs for this wizard:

Table 1. Bottom-Up Interpretive Wizard Page and Tab Overview
Wizard Page and Tabs:	Runtime Environment (See Note)
Wizard Page and Tabs:	W	I	B	T	M
Language structures page: - Request Language Structure - Response Language Structure	X				X
DFHLS2WS Application and Service properties page: - Application Properties - Service Properties	X				X
DFHLS2WS Target artifacts page: - Service Artifacts - Properties (Optional)	X				X
CICS Deployment Options page: - Specify deployment manifest properties	X				X
Language structures page: - Language Structure				X
DFHLS2SC XML Schema (XSD) Properties page: - XSD Properties				X
DFHLS2SC Target artifacts page: - Conversion Artifacts - Properties				X
CICS Deployment Options page: - Start Bundle deployment wizard upon finish				X
Note: W stands for Web Services for CICS I stands for IMS SOAP Gateway B stands for Batch, TSO, and z/OS® UNIX System Services T stands for XML Transformation for CICS M stands for MTOM/XOP (Message Transformation Optimization Mechanism)/(XML-binary Optimization Package) service

Language structures page

Edit online

The Language structures page for interpretive conversion lists all the high-level language structures in the source file that was used to start the wizard. Before starting the wizard, when using a selected source file, ensure that the source file contains both the request and response language structures for your application.

Follow these steps to complete this page:

On the Request Language Structure tab, select the language structure which is the response language structure of your existing application (that is, the language structure with which your application is invoked).
Note: When using the MTOM/XOP (Message Transformation Optimization Mechanism)/(XML-binary Optimization Package) development scenario, only DATA-STRUCTURE is allowed.
On the Response Language Structure tab, select the language structure which is the response language structure of your existing application (that is, the language structure that your application returns when it terminates). For One-Way (Request only) Web Service Generation, unselect the "Response Language Structure".
Note: When using the MTOM/XOP (Message Transformation Optimization Mechanism)/(XML-binary Optimization Package) development scenario, only DATA-STRUCTURE is allowed.
Click Change PL/I Preferences or Change COBOL Preferences button to open the desired preferences page. These preferences control how source files (PL/I or COBOL) are imported (see Setting Importer > PL/I preferences or Setting Importer > COBOL preferences).

Note: The Language structure tree views on this page can show certain data types that are not supported by the interpretive conversion. These types include the ones described in the topics Compatibility: Simple data types. These specific types are marked as (contains unsupported types) or unsupported type in the tree; these selections are automatically disabled. However, there are other types that are not supported by the interpretive conversion and they are described in the CICS TS 4.1 Documentation, refer to CICS® Transaction Server for z/OS, Version 4 Release 1 IBM® Documentation. These types are not marked as (contains unsupported types) or unsupported type in the tree and the selection is not automatically disabled. If you leave these data items selected, the generation fails and an appropriate error message is shown. An error entry is also put into the Remote error list view.

Related concepts

Introduction to mapping concepts

The DFHLS2WS Application and Service properties page

Edit online

The DFHLS2WS Application and Service properties page sets properties for the CICS application and for the Web service.

Follow these steps to complete this page:

On the Application Properties tab, specify the following options:
Program name

Specifies the name of the CICS application program that is exposed as a Web service.

Program interface
Specifies how CICS passes data to the target application program.
Note: When using the MTOM/XOP (Message Transformation Optimization Mechanism)/(XML-binary Optimization Package) development scenario:
- If CHANNEL is selected as the program interface, then the maximum size of an MTOM/XOP attachment (which is derived from a language structure) is 128 MB. This limitation is the maximum size of a COBOL data item (PL/I is not supported).
- If COMMAREA is selected as the program interface, then the maximum size of an MTOM/XOP attachment (which is derived from a language structure) is 32767 bytes. This limitation is the is the maximum size of a DFHCOMMAREA.
Container name

Specifies the name of the container that holds the high level language structure.

Request Channel
Specifies the location of the request channel description document (the location should be on the local system).
Note: If this value is used the mapping level must be 3.0 or higher.
Interaction between files referenced in the channel description document and language structure selection page:
- When the channel description document points to the main source file of the EST project, the item selections made in the Language structure selection page are PRESERVED.
- When the channel description document points to a source file that is NOT the main source file of the EST project, the item selections made in the Language structure selection page are IGNORED.
Response Channel
Specifies the location of the response channel description document (the location should be on the local system).
Note: If this value is used the mapping level must be 3.0 or higher.
Interaction between files referenced in the channel description document and language structure selection page:
- When the channel description document points to the main source file of the EST project, the item selections made in the Language structure selection page are PRESERVED.
- When the channel description document points to a source file that is NOT the main source file of the EST project, the item selections made in the Language structure selection page are IGNORED.
On the Service Properties tab, specify the following options:

Service Location:

Specifies the URI that a client uses to access the Web service.

Note: TXSeries® for Multiplatforms runtime only supports COMMAREA as Program interface.

The DFHLS2WS Target artifacts page

Edit online

The DFHLS2WS Target artifacts page sets options Web service files that are generated.

To complete this page:

On the Service Artifacts tab, specify the following options:

Note: Generate to: Is only applicable to single service Enterprise Service Tools projects.

Generate to:: Same project
Select this when the file container is on the local system (default).; Remote location
Select this when the file container is on a remote system. For additional information, see Generation of Enterprise Service Tools artifacts to remote systems.
File container: Specifies the folder in which the Web service files are generated.
WSDL file name: Specifies the name of the WSDL file.
WSBind file name: Specifies the name of the WSBind file.
Log file name: Specifies the name of the log file.
Overwrite files: This checkbox indicates that the wizard overwrites without warning, if files with the same name exist in the target directory.