CSL OM automated operator program clients

OM provides an API interface for application programs that automate operator actions known as automated operator programs (AOP). You can use an AOP to issue commands that are embedded in an OM API request to an OM.

OM provides an application programming interface (API) for application programs that automate operator actions. These programs are called automated operator programs (AOP). An AOP issues commands that are embedded in an OM API request to an OM. The responses to those commands are returned to the AOP embedded in XML tags.

If you want to use OM to manage commands and command responses in an IMSplex for your own product or service, you can use an AOP client, such as each of these clients:

• The IMS™-supplied AOP client, TSO single point of control (SPOC), which runs on the host. With the TSO SPOC, an automated operator can issue commands to the IMSplex and receive responses to those commands interactively.
• An AOP client that runs on a workstation (called a workstation SPOC).
• A command processing client, such as IMS.

An OM client uses OM requests to communicate with OM. Each OM client must register to SCI before it can issue OM requests.

If you intend to write AOPs, you can write them in either assembler or REXX. Assembler applications issue requests to the OM API; REXX applications issue REXX host commands to communicate with OM.

IMS provides a REXX SPOC API, which is a REXX program interface to a SPOC application. Your existing REXX applications can use this REXX SPOC API to interact with OM.