Security for OTMA

Security for OTMA is enforced by RACF® or a similar security product.

You can provide OTMA security by using:

RACF security levels
System execution procedures, the transaction message prefixes, and the /SECURE OTMA command
Protecting messages on asynchronous hold queues from unauthorized use

In addition to performing security checks, OTMA can pass to IMS the network security credentials, which includes a network user ID and a network session ID, that are entered from an application in a distributed environment. OTMA passes network security credentials to IMS in the security-data section of the OTMA message prefix if the credentials are entered from an application that uses one of the following user message exits:

HWSSMPL0
HWSSMPL1
HWSJAVA0

You can also use the following OTMA callable interface (C/I) APIs to pass network security credentials to IMS:

otma_send_receivey
otma_send_asyncx

For IMS callout requests, network security credentials are included in the OTMA message prefix of the callout message if both of the following conditions are true:

Network security credentials are in the security-data section of the OTMA message prefix of the input message to IMS.
The application that issues the RESUME TPIPE call supports network security credentials.