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
XML and COBOL type compatibility. 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 Information Center. 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.