Defining a CICS Transaction Server for z/OS data structure
Mapped data structures, such as COBOL copybooks or C structures, can be used to define an MRM message definition for a CICS® Transaction Server for z/OS® COMMAREA or a channel container.
Before you begin
- 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 online.
- 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.
After you have created the message definition, complete the following steps.
About this task
- 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.
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.