Can a Datacom/DB MUF and the Datacom applications run with either Datacom/DB software version 15.1 or 15.0?
Release 15.1 15.0
Datacom/DB MUF and Datacom applications can run using either Datacom/DB Version 15.1 or 15.0 libraries.
A MUF's specific custom CUSLIB and the Datacom/DB release's CABDLOAD software library can be swapped from 15.0 to 15.1 or 15.1 to 15.0.
To summarize, here are the 15.0 to 15.1 active upgrade steps stripped from the CADATACOM CORE 15.1 Perform a 15.0 to 15.1 Active MUF Upgrade
Follow these steps:
Locate CAI.THLQ.CABDSAMP data set member
BDCUS00. This member allocates the CAI.HLQ.INSTJCL data set. It also copies the Version 15.1 upgrade JCL members from the CAI.THLQ.CABDSAMP library into the CAI.HLQ.INSTJCL data set.
...
Use the following JCL members to perform a new Version 15.1 installation or the Version 15.0 to 15.1 upgrade processes.
BDCUSU15 – Version 15.0 to 15.1 traditional or legacy MUF upgrade process. However, if you want to see the 15.1 core marks on the CUSLIB members merely execute this job. (This step is optional. You could still run your 15.1 environment with your 15.0 CUSLIB),
BDUPG09A – Upgrades the DDOL and SIGNOFF panels to Version 15.1
If you want the internal core marks in the custom modules to show 15.1 instead of 15.0, then run the BDCUS00 to allocate new 15.1 CUSLIB, CUSMAC, CUSPROC and generate the 15.1 CUSLIB members via job BDCUSU15.
NOTE: Before you upgrade to either 15.0 or 15.1, check the Datacom/DB 14.0 MUF startup for DB00915I messages indicating that the DD and DDD from 14.0 to 15.0 had been completed:
DB00915I - CXX DBID 2 DATA-DICT DEFINITION VERSION 15.0 CHANGE LEVEL 0
DB00915I - CXX DBID 15 DDD-DATABASE DEFINITION VERSION 15.0 CHANGE LEVEL 0
Datacom/DB 15.0 required that those had been upgraded to version 15.0 when the MUF was upgraded from 14.0.