Registering an OM command processing client

An Operations Manager (OM) command processing client must register its command with OM, whereas automated operator program (AOP) clients do not have to register to OM.

1. Identify the exit routines that are needed to drive interactions between the CSL SCI and the client.
   The SCI handles communications between all CSL managers in the IMSplex and their client applications.
   1. Identify the SCI Notify exit for the client.
      A database connection can be routed through any active OM in the IMSplex, so an OM command processing client must registered to all OMs. A SCI Notify exit is driven when a new OM becomes active in the IMSplex and notifies the client with information about the new OM. The client can then register to the new OM. The SCI Notify exit is identified with the NOTIFYEXIT parameter of the CSLSCREG request.
   2. Identify the SCI Input exit for the client with the INPUTEXIT parameter of the CSLSCREG request.
      An OM command processing client must be able to receive OM directives sent from any OM in the IMSplex. The SCI Input exit is driven when there is a message or request for the client, so that the client can receive and process it.
2. Issue the CSLSCREG request to SCI with the information gathered in step 1.
   A client must register to the CSL SCI in the IMSplex before it can register with a CSL manager such as OM.
3. Issue the CSLSCQRY request to SCI to determine which instances of OM are active in the IMSplex.
   Before registering with the OMs for the first time, the client must manually identify all active OMs with this request. Once registered, the SCI Notify exit automatically informs the client when new OMs become active.
4. Issue the CSLOMBLD request to build the command list that will be passed to OM.
5. Issue the CSLOMREG request to all OMs in the IMSplex that are reachable and ready to accept registration requests.
6. Issue the CSLOMRDY request to indicate that the client is ready to begin processing commands from OM.