When the system logger address space fails

This topic applies to both coupling facility and DASD-only log streams, with differences noted in the text.

If the system logger address space fails, the following processing occurs:

Log stream connections are terminated.
The system issues a X'1C5' abend code.
Any system logger requests from the system where the system logger component failed are rejected.

Contact the IBM® Support Center for a fix for the problem, providing the SVC dump that accompanies abend code X'1C5'.

Subsystems or applications that held the lost connections may be required to be restarted. To start the system logger address space again after a failure, use the IXGLOGRS procedure in SYS1.PROCLIB:

START IXGLOGRS

This procedure starts the system logger address space as a system address space. At z/OS® V1R5 or higher, or on a system with OW53349 applied, system logger will be automatically restarted after a failure. Check for messages IXG056I and IXG067E, which may be issued during the restart.

For coupling facility log streams, recovery processing for the system logger address space is done by peer connectors, if available, and consists of either offloading the coupling facility log data for the system where the failure occurred to DASD log data sets so that it is on a persistent media or ensuring that the log data is secure in a persistent duplex-mode list structure. The recovery process for the system logger address spaces is the same as that for system failures. See When an MVS system fails for a description of the recovery process.