Securing messages on the asynchronous hold queue

You can protect messages on asynchronous hold queues from unauthorized use of the RESUME TPIPE call by using either RACF®, the OTMA Resume TPIPE Security user exit (OTMARTUX), or both.

When security is enabled for tpipe hold queues, the user ID issuing the RESUME TPIPE call must be authorized to access the TPIPE name that is contained in the RESUME TPIPE call message before any of 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. They can be used in combination or either one by itself. 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.