DC081001 explanation
search cancel

DC081001 explanation

book

Article ID: 140401

calendar_today

Updated On:

Products

IDMS IDMS - Database IDMS - ADS

Issue/Introduction

Attempting to run an ADS application, the following abend is occurring:
 
IDMS DC081001 V1 T51018 TASK: ADS2; MAP TIME-DATE STAMPS IN MAP MAPNAME AND APPL PROGRAM: ADSOMAIN(DLGNAME) DO NOT AGREE
 
What does this mean and how can it be resolved?

Environment

Release: All supported releases.
Component: ADS.

Cause

When a MAP is compiled (generated) with a critical change, the date and time of the compilation is stored in the map load module. This can be viewed with the following display:

 DCMT D MEM PRO APPLDICT.MAPNAME 32
Program: MAPNAME  Dictname: APPLDICT
 <Addr>   <Offset>                 <Hex>                    <Character>
3F4F7A00  00000000  C9D1C8D4 D7C1C7C5 F1F161F1 F861F1F9  *MAPNAME 11/18/19*
3F4F7A10  00000010  F0F6F3F4 F2F2D9F2 00000000 00000000  *063422R2........*

When the related dialog is compiled, that time-stamp is copied into the dialog load module:

 DCMT D MEM PRO APPLDICT.DLGNAME 64
Program: DLGNAME  Dictname: APPLDICT
 <Addr>   <Offset>                 <Hex>                    <Character>
3F4F6200  00000000  C6C4C25C C9D1C8C4 D7C1C7C5 F1F161F1  *FDB*DLGNAME 11/1*
3F4F6210  00000010  F861F1F9 F0F6F3F5 F2F6F4F8 C9D1C8D4  *8/1906352648MAPN*
3F4F6220  00000020  D7C1C7C5 F1F161F1 F861F1F9 F0F6F3F4  *AME 11/18/190634*
3F4F6230  00000030  F2F2D9F2 C5D4D7E2 C3C8D440 C5D4D7E2  *22R2EMPSCHM EMPS*

Note that the time-stamp at offset x'24' of the dialog load module is the same as the time-stamp at offset x'8' of the map load module. At run-time, these two time-stamps are checked and if they are not the same, the task is abended with the DC081001 message. This is a mechanism built-in to ensure that the map and dialog are in synchronization with each other.

A critical change to a map is one that requires dialog compilation, such as the addition or deletion of fields, and is identified by message DC366115 when the map is compiled. A non-criticial change is less severe, such as a cosmetic change or positional move of an existing field. This results in message DC366119 when the map is compiled.

 

Resolution

Dialogs are automatically varied NEW COPY when compiled in ADSC. Maps are not, so it may be necessary to issue DCMT V PR APPLDICT.MAPNAME NCI in order to avoid this abend.

Also the map time-stamp check can be disabled by the use of optional bit 252, although this is not recommended.

Additional Information

Powered by Wolken Software