OTMA send-then-commit messages

OTMA send-then-commit messages can also be processed on any IMS system in the shared queue group.

Synchronous and asynchronous transactions created by a program-to-program switch from an input synchronous transaction always run on the same IMS system as the transaction that initiated the program-to-program switch.

Figure 1. OTMA messages being processed on multiple IMS systems in a shared-queues group

In addition, program-to-program switching is not allowed for protected conversations (sync level 2).

Synchronous transactions which use send-then-commit processing support the following commit levels:
  • NONE
  • CONFIRM
  • SYNCPT
Asynchronous transactions which use commit-then-send processing support the following commit levels:
  • RESYNC
  • NO RESYNC
The commit levels for synchronous and asynchronous transactions are shown in the following figure.
Figure 2. Synchronous and asynchronous transactions and their respective commit levels
begin figure description. This figure is described in the surrounding text. end figure description.

Use the /DISPLAY ACTIVE command to determine whether the shared queue function for OTMA send-then-commit is active.

Using other IMS commands

The IMS command /DISPLAY TMEMBER membername TPIPE tpipename QCNT shows the tpipe status and the output message queue count in a shared queue for a particular IMS system.