UIB-DATE-TIME-STAMP VALUE different with 15.1

Products

• Datacom
• DATACOM - AD
• CIS
• COMMON SERVICES FOR Z/OS
• 90S SERVICES
• DATABASE MANAGEMENT SOLUTIONS FOR DB2 FOR Z/OS
• COMMON PRODUCT SERVICES COMPONENT
• Common Services
• CA ECOMETER SERVER COMPONENT FOC
• Easytrieve Report Generator for Common Services
• INFOCAI MAINTENANCE
• IPC
• UNICENTER JCLCHECK COMMON COMPONENT
• Mainframe VM Product Manager
• CHORUS SOFTWARE MANAGER
• CA ON DEMAND PORTAL
• CA Service Desk Manager - Unified Self Service
• PAM CLIENT FOR LINUX ON MAINFRAME
• MAINFRAME CONNECTOR FOR LINUX ON MAINFRAME
• GRAPHICAL MANAGEMENT INTERFACE
• WEB ADMINISTRATOR FOR TOP SECRET
• Xpertware

Issue/Introduction

Why is the CA Datacom support for Metacobol Version 15.1 generated UIB-DATE-TIME-STAMP VALUE different than with CA MetaCOBOL+ Version 1.1?

For example, when the translation was run on April 8,2018: 

Version 15.1 generated:
    02 UIB-DATE-TIME-STAMP PIC S9(05) COMP-3 VALUE +42036. 

Version 1.1 generated:
   02 UIB-DATE-TIME-STAMP PIC S9(05) COMP-3 VALUE +82057. 
 

Environment

z/OS

Cause

A solution was needed for 15.1 to the DLM macro (MCT#DLM).

According to the ​CA Datacom® support for MetaCOBOL - 15.1 documentation section on "Other Generated Data-Names":

UIB-DATE-TIME-STAMP PIC S9(5) COMP-3.

This data item assures a unique UIB. It is intialized to the following at translation: The first byte contains the least significant character of the current day, and the remaining bytes contain the current time. A data item containing the date and time of the access. 
https://docops.ca.com/ca-datacom-metacobol/15-1/en/program-development-ca-datacom-db/program-development-reference/generated-names/other-generated-data-names

But, with 15.1, the first byte contains the least significant character of the current month, rather than the current day.

 

Resolution

The VALUE should be the same as was generated with prior CA MetaCOBOL+ Version 1.1.

CA Datacom/DB 15.1 PTF SO04526 is available.