Writing a CSL RM client
The topics in this section describe the client requests and directives for writing an RM client.
Sequence of RM client requests
If you want to use RM to manage global resources in an IMSplex for your own product or service, you have to write one or more RM clients. An RM client uses RM requests issued in a particular sequence to communicate with RM.
Issue CSL RM requests to manage global resources
Before a client can access or change global resource information, it must register to SCI using the CSLSCREG request. After the client registers to SCI, it must register to RM using the CSLRMREG request. The client must issue an SCI registration request for every IMSplex with which it intends to communicate.
Issue CSL RM requests to coordinate IMSplex-wide processes
You can use RM-supplied requests to coordinate IMSplex-wide processes. All clients that are to participate in the process register to RM using the RM client registration request (CSLRMREG). After the clients are registered, several different requests can be utilized to coordinate processes.
CSLRMDEL: delete resources
You can issue the CSLRMDEL request to delete one or more uniquely named resources, or all resources by owner for a specific resource type on a resource structure.
CSLRMDRG: deregister clients
The deregister request is issued by a client when the client no longer wants to process resource requests or IMSplex-wide process requests from RM. The deregister request removes client information from RM and stops RM from sending new resource requests to the client. Some information about the client is retained that can affect IMSplex-wide processes.
CSLRMPRI: process initiate
With the CSLRMPRI request, a client can initiate a process across an IMSplex. RM ensures that only one IMSplex-wide process of a type can be in progress at one time. The process initiation fails if any other IMSplex-wide process of the type is in progress.
CSLRMPRR: process respond
By issuing the CSLRMPRR request, a client can respond to a step in an IMSplex-wide process.
CSLRMPRS: process step
By issuing the CSLRMPRS request, a client can perform a step in an IMSplex-wide process that can consist of zero, one, or more steps.
CSLRMPRT: process terminate
You can issue the CSLRMPRT request to terminate an IMSplex-wide process. Any client that is participating in the process can issue a CSLRMPRT FUNC= TERMINATE request to terminate the process.
CSLRMQRY: query resources
You can issue the CSLRMQRY request to query one or more uniquely named resources on a resource structure.
CSLRMREG: register clients
You use the CSLRMREG request to register a client to RM and, optionally, to register the client's resource types and associated name types. The client being registered to RM must be authorized to issue a CSLRMREG request. However, you cannot register a client if an IMSplex-wide process is in progress.
CSLRMUPD: update resources
By issuing the CSLRMUPD request, you can create a resource if it does not exist, or update a resource if it does exist (as long as the version specified matches the version of the resource). A resource can be created or updated with or without client data.
CSL RM directives
An RM directive is a function that RM defines that can be sent as a message to RM clients, informing the RM clients of work to be processed. After a resource processing client is registered to RM, RM can direct that client to perform RM functions, or directives, by issuing the CSLSCMSG request. A resource processing client is any system that manages resources and uses RM to manage global information about those resources.
Parent topic:
Common Service Layer (CSL)