Running the CICS Transaction Server for z/OS Connectivity sample
When you run the CICS Transaction Server for
z/OS Connectivity sample, the
sample_input_111111.xml,
sample_input_222222.xml, and
sample_input_FILEB.xml messages move through the
message flow. You can run the sample to find out what happens in either of the
following scenarios:
- The input .xml message retrieves a record from
FILEA.
- The input .xml message attempts to open a
non-existent file.
For more information, see About the
CICS Transaction Server for z/OS Connectivity sample.
If you have not set up FILEA in the CICS region,
you cannot observe the effects of retrieving records from FILEA. To set up FILEA
in your target CICS region, see
Setting up the CICS Transaction Server for z/OS Connectivity sample.
However, if you have not set up FILEA in the CICS region, you can still explore
the configuration of the node properties and attempt
to open a non-existent file.
Troubleshooting
Try the following troubleshooting tips if you encounter any problems when you
run the sample:
- 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 FILEA definitions in the CICS region.
- If you still encounter any problems when you run the sample,
see Resolving problems when running samples
in the WebSphere Message Broker documentation.
Running the sample with a .xml message to
retrieve record 111111 from FILEA
- In the Broker Development view, expand the
CICS Connectivity Message Flows > Flow Tests
folder.
- Double-click CICSConnectivityTest.mbtest to open
the file in the Test Client.
- The invoke command is set up to send the input message to retrieve record
111111 from FILEA.
- Right-click Invoke Message Flow > Re-run.
- Observe the input and output messages.
<record>
<stat></stat>
<recid>111111</recid>
<name>C. BAKER</name>
<address>OTTAWA, ONTARIO</address>
<phone>51212003</phone>
<date>26 11 81</date>
<amount>$0011.00</amount>
<comment>*********</comment>
</record>
Running the sample with a .xml message to
retrieve record 222222 from FILEA
- Right-click Invoke Message Flow > Duplicate.
- Change <record>111111</record> to
<record>222222</record>.
- Click Send Message.
- Observe the input and output messages.
<record>
<stat></stat>
<recid>222222</recid>
<name>DR E. GRIFFITHS</name>
<address>FRANKFURT, GERMANY</address>
<phone>20034151</phone>
<date>26 11 81</date>
<amount>$0022.00</amount>
<comment>*********</comment>
</record>
Running the sample with a .xml message to
attempt to open a non-existent file
- Right-click Invoke Message Flow > Duplicate.
- Change <file>FILEA</file> to
<file>FILEB</file>.
- Click Send Message.
- Observe the input and output messages.
<record>
<stat>File could not be found</stat>
</record>
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