DFHRM0401 during CICS startup if using DASD only logstreams

Question & Answer

Question

Why do I receive DFHRM0401 CICSAPPL There is no system log or an empty system log has been detected when attempting to start CICS? I am using DASD only logstreams and performing a disaster recovery exercise.

I see the following exception trace entries in my CICS dump:

 00004 QR    LG 3795 L2HS6 *EXC* IxgBrwse_cursor_start
             00000008,00000846,MVS,XXXXXXX.CICSREGN.DFHLOG
 00004 QR    LG 3795 L2HS6 *EXC* IxgBrwse_cursor_start
             00000008,00000846,MVS,XXXXXXX.CICSREGN.DFHSHUNT
 00004 QR    RM 06BB RMSL5 *EXC* Erroneous_empty_system_log_detected

The return code x'0008' and reason code x'0846' in the trace entries indicate that the log stream is empty.

Answer

The message DFHRM0401 that you are seeing during CICS startup was likely caused by z/OS APAR OA45042. The PTFs UA74157 (z/OS 1.13) and UA74158 (z/OS 2.1) for this APAR are in error.

This problem is fixed by System Logger HIPER APAR OA46962. Depending on your level of z/OS, you need to install either PTF UA76311 for z/OS 1.13 (HBB7780) or UA76312 for z/OS 2.1 (HBB7790).

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSGMGV","label":"CICS Transaction Server"},"Platform":[{"code":"PF035","label":"z\/OS"}],"Component":"Logger","Version":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Product Synonym

CICS/TS CICSTS CICS TS CICS Transaction Server

Was this topic helpful?

Document Information

Modified date:
23 March 2015

UID

dwa1181798

Tips