How CICS checks for the availability of the MVS logger

At intervals, CICS® itself checks for the availability of the MVS™ logger. It uses one of two procedures to perform these checks, depending on your operating system.

If the check fails, CICS either abends or quiesces, depending on the returned MVS logger reason code.

The interval at which CICS checks for the availability of the MVS logger varies, depending on the amount of system logging activity in the CICS region. The first check is made after CICS has not made contact with the MVS logger for 10 seconds. If CICS continues to perform no system logging after the first check, the interval between checks doubles each time, up to a maximum of 600 seconds. If CICS makes contact with the MVS logger at any point, the interval between checks is halved, down to a minimum of 10 seconds.

The checking interval can be affected by the exit time interval specified in the ICV system initialization parameter, as follows:

The statistics field IGXQUERY in the CICS log manager statistics enables you to monitor the number of checks that CICS makes for the availability of the MVS logger.

Related concepts
Some conditions that cause CICS log manager error messages
Related tasks
Tuning the region exit interval (ICV)
Interpreting journalname and log stream statistics
Monitoring the logger environment
Related references
ICV
[[ Contents Previous Page | Next Page Index ]]