How to verify a CXX version?

Document ID : KB000055624
Last Modified Date : 14/02/2018
Show Technical Document Details

Starting with r10, the CXX conversion phase is no longer part of the upgrade procedure but it is run after one has determined that there is no need to fall back to previous Advantage CA-Datacom release (BDCNVnn and BECNVnn jobs).

Sites running several Multi-User Facilities may need to check if the CXX conversion phase has been already run or not.

WHEN RUNNING r10 CODE:

If you run a REPORT AREA=CXX using and r10 DBUTLTY and the //CXX file is still in r9 format, the date on the TABLE LOADED entry will NOT reflect a century on the report:

For example:

 an r9 CXX report will reflect TABLE LOADED - YES, DATE--2/27/03
where
 an r10 CXX report will reflect TABLE LOADED - YES, DATE--2/27/2003

WHEN RUNNING r11 CODE:

If you run a full REPORT AREA=CXX using and r11 DBUTLTY and the //CXX file is still in r10 format, the following message will appear in the joblog not on the report:

DB00101I - STARTED JOB-jobname NUMBER-nnnnn CXX=xxxxxxxx
DB00905I - DIRECTORY (CXX) VERSION 10.0
DB00102I - ENDED JOB-jobname NUMBER-nnnnn

Also, an r11 MUF startup will print the following message if the CXX has not been converted to r11 format:

DB00210I - MULTI-USER RUNNING AUTHORIZED - YES
DB00905I - DIRECTORY (CXX) VERSION 10.0
DB00219I - MVS ECSA REQUIREMENT - 1,088 K