How can I resolve a DC081001 map timestamp error in an application migrated using Endevor/DB?
A DC081001 error indicates that a mismatch has occurred between the timestamps in an application program (or dialog) and its associated map. When this occurs it is immaterial whether or not Endevor/DB was used to migrate the program. The Endevor data records (footprints, CLEs, etc) are never checked in the process which results in the DC081001 error. The fields that are compared at run-time are the timestamp in the map load module, and what's passed in the MRB (which is a copy of the map data stored in the application program or dialog load module). The MRB is a record of the map's status at the time the program or dialog was compiled, and it is stored in the application program or dialog load module. If the MRB date differs from the date in the map load module at run-time, the DC081001 error is produced.
The only way in which Endevor/DB may be involved when this error is produced, is that when the migration was processed by Endevor/DB, it may have moved the map as well as the program or dialog to the target destination. If that occurred, and the map module which was moved was not the same map used when the application program or dialog was compiled, that could explain why the error occurred. If the same error does not occur when manually punching (only) the program load module, then somehow in the Endevor/DB migration process the program or dialog load module is not the only entity being moved, and an inappropriate map load module was also migrated. The parameters used in the Endevor/DB process should be examined to prevent this from occurring; if an EXPAND IDD clause is included but it is desired to migrate only the program or dialog load module, then that should be removed. Also, procedures should be verified to ensure that if a map is migrated, it is the same load module that was stored in the dictionary at the time the program or dialog was compiled.