How AOP clients that run on the host communicate with the CSL OM
Automated operator program (AOP) clients that run on the host can communicate directly with Operations Manager (OM). After a z/OS® AOP is registered with SCI, it can issue an OM command (CSLOMCMD) or query (CSLOMQRY) requests. When the z/OS AOP is ready to terminate, it must deregister with SCI using the CSLSCDRG macro. Each of the requests can be sent directly to OM or SCI.
The following table lists the sequence of requests that are issued
from an AOP that is running on the host. The request is listed with
its purpose.
| Request | Purpose |
|---|---|
| CSLSCREG | Registers to SCI, which enables the client to send OM requests to OM through SCI. |
| CSLSCRDY | Readies the OM client to SCI, which routes messages to the client by client type. |
| CSLOMxxx | Issues OM requests (CSLOMCMD, CSLOMQRY) to send commands to OM. |
| CSLSCBFR | Releases the output buffer returned by the request, if any. |
| CSLSCQSC | Quiesces with SCI. |
| CSLSCDRG | Deregisters from SCI. |
Note: Although not required for an AOP executing on the host, CSLSCRDY
and CSLSCQSC are recommended for clients that want to receive messages
routed by TYPE.
An OM client uses OM requests to access and use OM services and resources. Some SCI and OM requests must be issued by the client to request OM services. Some of those requests must be issued in a particular sequence, as shown in Table 1. Other requests can be issued multiple times, in any order, based on the processing requirements of the client.