Other OTMA program switch considerations

The following considerations also apply to program-to-program switching.

• The P2P message switch is not supported for OTMA protected messages (send-then-commit input with synclevel = SyncPt).
• If a non-conversational program performs a program-to-program message switch to a program in a Shared Queues environment, the program in the SQ environment must be running on the same IMS where the first program gets scheduled, unless the support for synchronous APPC/OTMA is active (AOS=Y) and the IMS start-up parameter OTMAASY=S is specified.
• If an input conversational transaction occurs, only the message-switched-to continuation of the conversation is scheduled synchronously. All other transactions are scheduled asynchronously.
• In a shared queues environment that has both synchronous APPC/OTMA support (AOS=Y on the DFSDCxxx PROCLIB member) and z/OS® Resource Recovery Services (RRS) support (RRS=Y on the startup procedure) enabled, an application program running on a back-end IMS system that initiates an outbound APPC protected conversation with another IMS system is restricted to a single program-to-program switch to the same destination transaction.

  If an application program performs multiple program-to-program switches after allocating an APPC outbound protected conversation on another IMS system, the results are unpredictable and can include a WAIT-RRS/PC condition in the MPP dependent region.