Datacom DDUTILTY "DATE-LAST-CHANGED" for KEYS

Products

• Datacom
• DATACOM - AD
• Datacom/DB
• Datacom/AD
• Datacom/Server

Issue/Introduction

Many KEYs are showing the "DATE-LAST-CHANGED:" in the DDUTILTY reports with the same date as when this Datacom Multi-User (MUF) was upgraded to Datacom/DB Version 15.0. Is this normal and expected?

 

Environment

Datacom/DB

 

 

Cause

In this particular case, there was a mass update during the upgrade of the KEYS via a DDUPDATE job -UPG and 1500 transactions. This caused multiple KEYs be to updated. Any of the KEYs that were updated by that process would reflect the "DATE-LAST-CHANGED:" (and "TIME-OF-CHANGE:") in a DDUTILTY report as the same date and time the DDUPDATE job was run.

The -UPG header transaction is used to update specific attribute information of a generic set of entity-occurrences in Datacom Datadictionary.

Example DDUPDATE transactions:
  -UPG KEY,ALL.ALL(PROD) 
  -1500 KEY-INDEX-NAME,& 
  -END

Resolution

Refer to the "Using the -UPG Header Transaction" and the "DDUTILTY - Producing Reports and Source Language Statements"