OTMA security

Security for OTMA is enforced by RACF® or a similar security product. The following topics describe implementing security for OTMA and OTMA clients by using RACF.

RACF security levels for OTMA
OTMA uses four levels of RACF security: CHECK, FULL, JOIN, NONE, PROFILE.
Specifying OTMA security
You can make most security specifications for OTMA and OTMA clients by using the transaction message prefixes, the /SECURE OTMA command, and during system definition.
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.
Security for OTMA IMS-to-IMS TCP/IP connections
For OTMA ALTPCB messages sent to a remote IMS system on an IMS-to-IMS TCP/IP connection, transaction authorization is performed by the remote IMS system.
General OTMA security considerations
A number of general security considerations exist for OTMA that you should be aware of.

Parent topic: Enabling and using OTMA