Some conditions that cause CICS log manager error messages

Problems in the CICS® log manager and its interface with the MVS™ system logger can arise from various conditions, as a result of which the CICS region can fail because of loss of access to its system log. You need to be aware of the more common conditions, which (although very rare) result in a failure in this component of CICS.

In order to understand what has happened in a particular failure, it is helpful to look at the various combinations of messages that can be issued by CICS in different error situations. This approach is useful in ensuring that you gather the necessary diagnostic information at the time of the failure, to enable accurate problem determination and resolution. It also helps to ensure a rapid restart of the CICS region, with a full appreciation of the possible impact on data integrity.

The following CICS log manager messages cover some of the CICS logger failure situations. The more common message combinations are as follows:
  • DFHLG0772, DFHLG0800, and DFHLG0738
  • DFHLG0772, DFHLG0800, DFHLG0736, and DFHLG0741
  • DFHLG0772 and DFHLG0740
  • DFHLG0772 and DFHLG0734
  • DFHLG0002 and DFHLG0734
Note that if messages DFHLG0736, DFHLG0738, or DFHLG0740 are issued, CICS recovery manager sets its global catalog type-of-start override record to AUTODIAG. For more information, see Restarting CICS after a system log failure.
Note: For details of all the return and reason codes for the MVS logger macros, see z/OS MVS Programming: Authorized Assembler Services Reference (Volume 2).