Sending type-1 commands from an OTMA client

You can submit type-1 IMS commands from an OTMA client application. Some restrictions and recommendations apply.

Most commands should be submitted with the send-then-commit (CM1) protocol. However, the following commands require the commit-then-send (CM0) protocol:

  • /DBDUMP DATABASE
  • /DBRECOVERY AREA|DATABASE
  • /START AREA|DATABASE
  • /START REGION
  • /STOP AREA|DATABASE
  • /STOP REGION

The DISPLAY TRANSACTION command behaves differently when it is issued from an OTMA client. The command sends its output directly to the client, not to the IMS master terminal. Depending on the setting of the extended-response-requested flag in the message-control information section of the message prefix, the output is either in an architected format (only supported for this command) or in the standard IMS format.

Recommendation: Because the client must use the commit-then-send (CM0) flow, the output from these commands cannot be tied to the input command. The OTMA prefixes are not replicated (the only field common to both the input and the output is the transaction-pipe name). Therefore, configure the client to submit IMS commands using a transaction pipe that the client reserves for IMS command processing.
Restrictions:

OTMA clients cannot submit IMS commands from the following types of subsystems:

  • An IMS Extended Recovery Facility (XRF) alternate subsystem
  • A CICS®-IMS DBCTL subsystem