Before you start:
- Optional: If you are using a COMMAREA data
structure, read the COMMAREA concept information that is defined in
the
CICS Transaction Server for z/OS Version 4.1 product documentation. - Read the COMMAREA and channel concept information that is defined in COMMAREA or channel data structures.
- Create a message definition file by using the New Message Definition
File wizard in the IBM® Integration Toolkit.
- If you are using a C header file, see Message Sets: Importing from C.
- If you are using a COBOL data structure, see Message Sets: Importing from COBOL copybooks.
- For information about other data structures, see Message Sets: Working with data structures.
After you have created the message
definition, complete the following steps.
- Select the Data structure property value on the Basic tab of the CICSRequest node in accordance with the targeted CICS program. For example, if the target program is channel-based, select Channel as the data structure.
- Ensure that the properties on the Response Message Parsing tab of the CICSRequest node specify the output COMMAREA or container structure.
- Check that the upstream nodes are configured to provide the correct input structure.
- Optional: If you are using a COMMAREA data structure, ensure that the CICSRequest node Commarea length property is large enough to hold the serialized input or output structures to avoid a memory leak in the CICS application.
Next: If you are using a channel data structure, create
a message collection to represent the channel data structure, as described
in Creating a message collection by using ESQL.
Last updated Friday, 21 July 2017