REXX SPOC API within a transaction

Transactions can be written in the REXX language. A REXX EXEC runs as an IMS application and has characteristics similar to other IMS-supported programming languages. The REXX SPOC API can be used to issue commands from a transaction and to examine the command responses.

In the IMS Adapter for REXX environment, the OM API command authorization is performed with the MPP user ID. To use the transaction origin user ID rather than MPP user ID, a user exit must be utilized. The Build Security Environment user exit (BSEX) is called for non-OTMA/non-APPC input messages. The exit can request that IMS build a security environment in the MPP region when a message is scheduled (an accessor environment element (ACEE) will be anchored on TCBSENV). After use of the exit, the transaction origin user ID is used for OM API security checking. OTMA/APPC messages are not supported unless SECURITY=FULL or SECURITY=PROFILE, and the selection for the input message is FULL.