REXX SPOC API

The REXX SPOC API allows REXX programs to submit IMS operator commands to an IMSplex, to retrieve command responses, and to subscribe to the Operations Manager (OM) for unsolicited system messages, which can include responses to commands issued from any SPOC in an IMSplex that are routed back through OM.

The REXX language is a powerful command procedure language. Many operator automation programs are written in REXX and they can run in various environments. REXX programs, using the REXX SPOC API, have the following advantages over other IMS automation tools like AOI and TCO:

• Can issue type-2 commands to IMSplexes. REXX programs can also issue other commands, such as z/OS® operator commands or TSO commands to operate the system.
• Can examine command responses, unlike TCO, and take further action based on those responses. Command responses that are returned to the REXX SPOC API are in the form of XML statements; these responses are easier to parse than the command responses that are returned to the AOI interface. You can write REXX routines to improve the self-healing and self-operating abilities of your system.
  For example, a REXX program issues the following command to query the system:

  QUERY TRAN NAME(prod001) SHOW(QCNT)

  If the command response from the REXX SPOC API shows that work is delayed (the queue count is greater than you want), the REXX program can issue additional operator commands to resolve the problem.

• Are independent of IMS (AOI runs as an IMS application program and TCO runs as an IBM® subtask), and are therefore easier to implement and run.
• Can run in Tivoli® NetView for z/OS.
• Can issue /NRE and /ERE commands, unlike TCO.