DC202027 message and 3027 abend at startup

Products

• IDMS
• IDMS - Database

Issue/Introduction

IDMS abends at startup with the following messages:

+IDMS DC202027 V52 Name/Date from DMCL on Journals different from Run Time DMCL
+IDMS DC202028 V52 Run Time DMCL Name: CV01DMCL , Compile Date/Time: 2014-04-03-11.08.58.096436
+IDMS DC202029 V52 Journal DMCL Name: CV01DMCL , Compile Date/Time: 2018-02-16-09.19.23.014512
+IDMS DC391008 V52 WARMSTART Failure - IOSTATUS=3027

Environment

Release: All supported releases.

Cause

When IDMS abends, the next restart must perform a warmstart, and it must be done with the same DMCL as the prior CV execution used in order to ensure that it will be able to recover properly. If in between the two startups, the DMCL was changed, IDMS checks for this change and issues the above abend.

Resolution

If it is known that the CV will be able to recover even with the changed DMCL (e.g. no areas or files in the old DMCL were changed or modified in any way), this check can be overridden with the JRNLDTS parameter in SYSIDMS. Insert a JRNLDTS parameter into the SYSIDMS ddname of the CV:

JRNLDTS=<date-time-stamp of journal>

The date-time-stamp must be what was listed in the DC202029 message.
 

Additional Information

SYSIDMS Parameter Descriptions (scroll down to JRNLDTS).