I have already completed the Datacom/AD R14 to R15.1 upgrade to a point where the MUF tasks are up and running with the R15.1 runtime libraries.
I have already run INSTJCL(AXACTALC) for both MUFs.
The next steps are to run INSTJCL(AXACTDD1 and AXACTDD2) for both MUFs. I do not have a Sandbox for this environment and hence could not simulate it. What can I expect from my next steps and is there something that I should be aware of?
Release : 15.1
Component : Datacom/AD
AXACTDD1 takes a backup of your CXX, along with databases 2 and 15 (the Datadictionary). These three should always be backed up together, as the Datadictionary and CXX need to be kept in sync. This backup is run using SEQ=PHYSICAL, which means it can run without any special consideration for MUF operation, so the MUF does not need to be shut down.
AXACTDD2 is the job to complete the upgrade to Version 15.1 and should be run once you are satisfied that your applications are working fine with this release. This job will upgrade the Datadictionary to v15.1, and will add or change any internal attributes to support the Version 15.1 code base. The MUF should be up and running for this job to run.
You will not see anything different in your application as a result of these changes, but the next time the MUF is started, you will see the new version number in your MUF log for the Datadictionary databases. For example, you currently have:
DB00915I - CXX DBID 15 DDD-DATABASE DEFINITION VERSION 14.0 CHANGE LEVEL 0
DB00915I - CXX DBID 2 DATA-DICT DEFINITION VERSION 14.0 CHANGE LEVEL 0
After the AXACTDD2 job runs, you will see these messages in the log:
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
Note that there is a similar message for database 1000 (the Datacom Dynamic System Tables), and it will stay with Version 14.0 - this is expected. Here is that message:
DB00915I - CXX DBID 1000 CASYSTEMTABLES DEFINITION VERSION 14.0 CHANGE LEVEL 0
Note that you might receive a Condition Code of 4 in the AXACTDD2 job. As noted in the flowerbox comments at the top, this is acceptable. The cause will be seen in messages
DDWKEY0013 SIGNED NUMERIC FIELD IN KEY
and these are not a problem.
As always, please contact Broadcom support for Datacom if you have further questions.