The agents in a MAS

For a CICS® system to be managed by CICSPlex® SM, agent code must exist and be in communication with a CMAS. The agent code in a MAS is started in much the same way that CICSPlex SM code is started in a CMAS. A program is added to the CICS PLTPI that does a CICS START of a transaction; that transaction invokes EYU9XLEV, the same program that is used in a CMAS.

Once the MAS environment is initialized, a long running task is started that waits for requests from the controlling CMAS. Depending on the type of request received, a method call is made to process the request either synchronously or asynchronously. The long running task is also responsible for starting and stopping the other tasks involved in agent processing, such as monitoring tasks.

Another agent task is responsible for sending a heartbeat to the controlling CMAS. The heartbeat is used to let a CMAS know that the MAS is still able to communicate and to send required data on a regular basis. This data includes a current task count and the health status of the MAS.

The agent code in a managed CICS system is part of the CICSPlex SM component called the Managed Application System. This component has an identifier of MAS and its module names have the character N in the fifth position (for example, EYU0NLRT). So MAS is the identifier for both a Managed Application System (a CICS system in which CICSPlex SM agent code resides), and for the component that implements the bulk of that agent code.

[[ Contents Previous Page | Next Page Index ]]