IDMS DC081001 MAP TIME-DATE STAMPS IN MAP <map-name> AND APPL PROGRAM <program-name> DO NOT AGREE using Alternative Maps

book

Article ID: 221413

calendar_today

Updated On:

Products

CA IDMS

Issue/Introduction

IDMS DC081001 V10 T41667 TASK: ADS2; MAP TIME-DATE STAMPS IN MAP CPMU0401 AND APPL PROGRAM: ADSOMAIN(BCDSQL00) DO NOT MATCH

Environment

Release : 19.0

Component : CA IDMS/DB

Resolution

When the map name identified in the DC081001 message is not the same as the map that was used to compile the dialog this means Alternative Maps are being used.

To identify the map being used by the dialog, take the dialog name from the DC081001 message such as BCDSQL00 in this example. 

Enter LOOK PROGRAM=BCDSQL00 from enter next task code. It returns this. The map name is in yellow and the dialog name is in green. Note that the map name from the DC081001 message is CPMU0401 and is not the same as the map name followed by it's datetime stamp in yellow is different from CPMU0401.

     BCDSQL00 was #LOADed From --> APPLDICT                                     
Entry Point Offset +0      -  Reentrant     -  AMODE 31  -  RMODE ANY           
        8,336 Bytes in Load Module BCDSQL00 loaded at 3CE6FA00                  
                                                                                
            Module    Offset   Date   Time    FMID      RMID                    
                                                                                
           BCDSQL00   +4      210721  1127                                      
           BCMSQL00   +1C     210721  0957                                      
                                                                                
3CE6FA00 +0      C6C4C25C C2C3C4E2 D8D3F0F0 F0F761F2 FDB*BCDSQL0007/2           
3CE6FA10 +10     F161F2F1 F1F1F2F7 F2F9F2F9 C2C3D4E2 1/2111272929BCMS           
3CE6FA20 +20     D8D3F0F0 F0F761F2 F161F2F1 F0F9F5F7 QL0007/21/210957           
3CE6FA30 +30     F3F8D9F2 40404040 40404040 40404040 38R2        

For more on Alternative Maps refer to https://techdocs.broadcom.com/us/en/ca-mainframe-software/database-management/ca-idms-reference/19-0/mapping-facility/generate-alternative-maps.html.

The main and alternative maps must have the same datetime stamps. The alternative map is created by copying it from the main map in MAPC. The only changes that should be made to the alternative maps are non-critical changes that will not cause the datetime stamp to be updated. When the alternative map is compiled you should get this message DC366119 Map mapname has been compiled and not message DC366115 SPNMAP01 successfully compiled:  time/date stamp updated. 

 If the datetime stamp is updated as shown my this message then the DC081001 will occur.

What is a Critical Change?
The following types of changes, which are considered critical, update the date/time stamps for panel and map occurrences:
1 Adding a variable field to a map/panel
2 Deleting a variable field from a map/panel
3 Changing a pageable map to a nonpageable map, or vice versa
4 Changing the version of a record
To update the date/time stamp for the map load module and incorporate the critical changes that were made, recompile the map load module.

The only changes that should be made to the alternate map are:

1 Hiding fields on the map layout.

2 Moving/rearranging fields on the map layout.

 

         

Additional Information

https://techdocs.broadcom.com/us/en/ca-mainframe-software/database-management/ca-idms-reference/19-0/mapping-facility/generate-alternative-maps.html