Datacom/AD shows "(14.02)" in DB00215I, CA-11 shows only 14.0
search cancel

Datacom/AD shows "(14.02)" in DB00215I, CA-11 shows only 14.0

book

Article ID: 38670

calendar_today

Updated On:

Products

Datacom DATACOM - AD Datacom/AD

Issue/Introduction

Maintenance has been applied to Datacom/AD Version 14.0 for use with Workload Automation Restart Option for z/OS Schedulers (aka CA-11). Now the Datacom/AD Multi-user (MUF) shows "(14.02)" in the message:

    DB00215I - CA Datacom/DB Version 14.0 (14.02)

However, the CA-11 started task DB00135I CONNECT and DB00136I DISCONNECT messages shows only 14.0 with no additional "(14.02)".

What is "(14.02)" and how to confirm that the CA-11 started tasks are using the level of Datacom maintenance?

Environment

Release: All supported releases.
Component: Datacom/AD.

Resolution

DB00135I CONNECT and DB00136I DISCONNECT correctly only show the version 14.0.
 
"(14.02)" in the DB00215I message indicates that a set of enhancement PTFs for Datacom/DB had been applied (see informational RI86001 which discusses 14.02).
 
One way to determine that all of the LPAR instances are using the same maintenance level is to run a simple batch DBUTLTY on each LPAR with ",PARM='/PGMDT=ccyymmdd'".  cyymmdd could be a very early date, such as ",PARM='/PGMDT=20010101'" so as not to limit the display of any DB00215I messages. With that PARM, any DBUTLTY execution will show the level (RMID) of each module being loaded by DBUTLTY. 
 
For example, using Datacom/AD 14.0 INSTJCL(AD14CXXR) change:
 
  //CXXRPT   EXEC PGM=DBUTLTY,REGION=6M,PARM='/PGMMONTH=1' 
 
       ...to...
 
  //CXXRPT   EXEC PGM=DBUTLTY,REGION=6M,PARM='/PGMDT=20010101' 
 
       ... and run the job on each Lpar.
 
Then review the DB00248I - PARM PGMDT=... displayed messages in each of the DBUTLTY jobs from each LPAR. They should be identical if using the same level of maintenance.

Additional Information