How AOP clients that run on a workstation communicate with the CSL OM

A workstation automated operator program (AOP) client cannot communicate directly with Operations Manager (OM). Instead, it must communicate with a z/OS® address space that acts as an OM AOP client.

Instead of issuing CSLOMCMD or CSLOMQRY requests, the z/OS address space issues CSLOMI, which passes the prebuilt string that it received from the workstation to OM. For example, if the workstation wants to query the command processing clients to see how many exist in the IMSplex, it can send the string QUERY(CMDCLIENTS) to the z/OS address space, which would then use CSLOMI to send the query to OM for command processing.

If the workstation wants to issue a QRY TRAN command to the IMSplex, it can send the following string to the z/OS address space:

CMD(QUERY TRAN NAME) ROUTE(IMSA) TIMEOUT(10) RQSTTKN2(QTRANCMD)

The z/OS address space would then use CSLOMI to send the string to OM for command processing. The z/OS address space should pass the user ID associated with the workstation application to ensure correct authorization processing by OM.

The following table illustrates the sequence of requests issued by a proxy AOP client, executing on z/OS, that is communicating with OM on behalf of a workstation AOP. The request is listed with its purpose.

Table 1. Sequence of requests for AOP running on the workstation
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.
CSLOMI	Issues OM requests (CMD(), QUERY()) 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 workstation, CSLSCRDY and CSLSCQSC are recommended for clients that want to receive messages routed by TYPE.