Alert monitor
The alert monitor transaction, CKAM, handles unscheduled events (known as pending events) that occur as a result of connect requests to instances of WebSphere® MQ. The alert monitor generates messages that are sent to the system console.
- 1. Deferred connection
- A pending event (called a deferred connection) is
activated if CICS® tries to
connect to WebSphere MQ
before a suitable queue manager is started. A suitable queue manager
could be either a single named queue manager or a member of a WebSphere MQ queue-sharing
group, depending on the setting for the connection. When a suitable
queue manager is available, the CICS-WebSphere MQ adapter issues a
connection request, a connection is made, and the pending event is
canceled.
You can have multiple deferred connections, one of which is connected when a suitable queue manager is started.
If you are using a WebSphere MQ queue-sharing group for the connection, and all the queue managers in the group are unavailable, the CICS-WebSphere MQ adapter initiates connection to each queue manager in turn, resulting in multiple deferred connections. When one of the queue managers is started, the CICS-WebSphere MQ adapter makes the connection. If more than one queue manager is started on the same LPAR, the CICS-WebSphere MQ adapter connects to one of them.
- 2. Termination notification
- When a connection is successfully made to WebSphere MQ, a pending event called a
termination notification is created. This pending event expires when
one of the following occurs:
- The queue manager to which CICS is connected shuts down normally with MODE(QUIESCE). The alert monitor issues a quiesce request on the connection.
- The queue manager shuts down with MODE(FORCE) or ends abnormally.
- The connection is shut down from the CKQC transaction.
The maximum number of pending events that CICS can handle is 99. If this limit is reached, no more events can be created until at least one current event expires.
The alert monitor stops itself when all pending events have expired. It is subsequently restarted automatically by any new connect request.