Running the CICS Transaction Server for z/OS Channel Connectivity sample
When you run the CICS Transaction Server for z/OS
Channel Connectivity sample, the sample XML message moves through the message
flow. You can run the sample to find out what happens in the following
scenarios:
- The input .xml message is used to create
multiple containers in a CICS channel by using a message collection.
- The input .xml message is used to create a
single container in a CICS channel.
For more information, see About the CICS Transaction Server for z/OS Channel Connectivity sample.
If you have not set up the CICS program, WMBCHAN1, in the CICS region, you
cannot observe the channel support in the CICSRequest node. To compile the
CICS program, see Setting up the CICS Transaction Server for z/OS Channel Connectivity sample.
Troubleshooting
If you encounter problems when you run the sample, see the following
troubleshooting tips:
- Check the configuration details that are specified on the CICSConnection
configurable service. For more information about the CICSConnection
configurable service properties, see
Configurable service properties
in the WebSphere Message Broker documentation.
- Check the log file and the WMBCHAN1 program definition in the CICS region.
- If you still encounter problems when you run the sample, see
Resolving problems when running samples
in the WebSphere Message Broker documentation.
Running the sample in message collection mode
- In the Broker Development view, expand the
CICS Channel Connectivity Message Flow > Flow Tests
folder.
- To open the file in the Test Client, double-click CICSChannelTest.mbtest.
- Look for the first invoke command: Invoke Message Flow (Create a Message
Collection for multiple containers).
- Right-click Invoke Message Flow and click
Re-run.
- Look at the input and output messages.
<Data>
<NumericSum>15</NumericSum>
<LongestString>A really long sentence that CICS can pick out and return in a container.</LongestString>
<OtherInfo>
<ChannelName>MYCHANNEL</ChannelName>
<MirrorTran>CPMI</MirrorTran>
</OtherInfo>
</Data>
Running the sample in single message mode
- Look for the second invoke command: Invoke Message Flow (Use a single
message for a single container).
- Right-click Invoke Message Flow and click
Re-run.
- Look at the input and output messages.
<Data>
<NumericSum>0</NumericSum>
<LongestString>
<Text>
In this test, we are sending a single XML message into the CICS node,
and the local environment overrides provide a container name
("string") and a channel name ("SINGLEMSG").
On output, a message collection is still produced from the response
channel.
</Text>
</LongestString>
<OtherInfo>
<ChannelName>SINGLEMSG</ChannelName>
<MirrorTran>CPMI</MirrorTran>
</OtherInfo>
</Data>
For detailed information about how to use the Test Client, see
Test Client Events tab
in the WebSphere Message Broker documentation.
Back to sample home