Resume tpipe protocol
The resume tpipe protocol retrieves asynchronous and synchronous callout messages from IMS™.
An IMS Connect client signals how long to wait for output from IMS by specifying an IRM timeout value with the IRM_TIMER field. The IRM timeout value affects the RESUME TPIPE call that is sent to IMS Connect and the ACK or NAK response message that is sent to IMS Connect.
When you use IMS TM Resource Adapter or IMS Enterprise Suite SOAP Gateway to handle the callout request from your IMS application, the communication with IMS Connect is handled for you.
Both the IMS TM Resource Adapter and SOAP Gateway listen for synchronous callout requests by continuously issuing the RESUME TPIPE call to IMS Connect. If a callout request message is on the tpipe queue, OTMA sends the callout request to IMS Connect, IMS Connect processes the message, converting the message to XML if necessary (for SOAP Gateway if using the IMS Connect XML adapter function), and then sends the message to the IMS TM Resource Adapter or SOAP Gateway.
If you have a custom IMS Connect client, you must code the client to issue a RESUME TPIPE call to retrieve the callout messages
Resume tpipe security
You can
protect callout messages from unauthorized use of the RESUME TPIPE
call by using either the Resource Access Control Facility (RACF®), the OTMA Resume TPIPE Security user exit (OTMARTUX), or both.
When security is enabled, the user ID that issues the RESUME TPIPE call must be authorized to access the tpipe name that is contained in the RESUME TPIPE call message before any messages are sent to an OTMA client.
The security checking performed by RACF and the security checking
performed by the OTMARTUX user exit are optional. If both RACF and the OTMARTUX are
used, RACF is called first
before giving control to the OTMARTUX user exit, in which
case, the OTMARTUX user exit can override RACF, depending on your needs.