WebSphere Message Broker, Version 8.0.0.7 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

See information about the latest product version

Processing responses from a CICSRequest node

The CICSRequest node can return different response messages that indicate the success or failure of the request sent to CICS® Transaction Server for z/OS®.

Before you start:

Ensure that you have built a message for the CICSRequest node, as described in Building a message for the CICSRequest node.

The CICSRequest node has four output terminals:
  • Out: The output terminal from which the message tree is propagated, including the data returned from CICS.
  • Failure: The output terminal to which a message is routed if a CICSRequest node exception is detected, or a CICSRequest node to CICS connection failure occurs.
  • Error: The output terminal to which a message is propagated if a CICS error (abend) occurs.
  • Timeout: The output terminal to which the message is propagated if a per-request timeout occurs when an individual request is sent to CICS, but the request takes too long.
You can select the location to which to send the response by configuring the Output data location Result property on the CICSRequest node. This property specifies the location in the message tree to which the CICSRequest node places the output.
You can use the CICSConnection configurable service to change connection details for the CICSRequest node. See Changing connection information for the CICSRequest node for details about creating, changing, reporting, and deleting the CICSConnection configurable service.
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2016Copyright IBM Corporation 1999, 2016.

        
        Last updated:
        
        Last updated: 2016-05-23 14:47:44


Task topicTask topic | Version 8.0.0.7 | bc16100_