Upgrading Multi-User Facility (MUF) Version 14.0 to 15.x

In prior releases, CA Datacom presented different strategies to upgrade a CXX from one release to the next. All of them required an outage for the conversion.
datacom151
In prior releases,
CA Datacom®
presented different strategies to upgrade a CXX from one release to the next. All of them required an outage for the conversion.
Version 15.x completely removes the outage. Version 15.x supports a CXX initialized and used as Version 14.0. In fact, 15.x can only initialize a CXX as Version 14.0. There is no such thing as a CXX set as 15.x.
The new process employs few changes to the CXX between Versions 14.0 and 15.x. The full CXX options are compatible between the two releases. However, options known only to Version 15.x are ignored if Version 14.0 code is executing.
Changes at the database level are handled using the FORMAT that was built at Version 12.0. A CXX built and used by Version 14.0 has each database with a FORMAT of 1 or 2. If Version 15.x code is executed with this CXX, when it opens a database the FORMAT 1 or 2 bases are converted to a FORMAT 3 and a message is issued about the conversion. A solution of support within Version 14.0 causes it to recognize a database at FORMAT 3 and downgrade it to 2.
With these abilities, the CXX is removed as a roadblock between Datacom executing as Version 15.x and Version 14.0. In fact, users using MUFPLEX may have different physical MUFs executing at different releases. This allows easy upgrades with no outage and also fallbacks with no outage.
In a single MUF configuration, it is now possible for MUF to run at a Version 15.x code level while all applications that access the MUF remain at the Version 14.0 code level. To accomplish this, MUF has to use new Version 15.x libraries while the applications continue to use the old Version 14.0 libraries.
Since the CXX no longer goes through a conversion process, the term "upgrade" in Version 15.x refers to only the system database resources that are associated with a MUF instance. In the Version 15.x upgrade these resources are the CA
CA Datacom® Datadictionary™
databases, the
CA Dataquery
database and the Dynamic System Tables database.
The following topics are discussed on this page:
Overview
Beginning with Version 15.x, there are a total of three ways to upgrade a
CA Datacom®/DB
Version 14.0 Multi-User Facility (MUF) to Version 15.x. In all prior
CA Datacom®
versions, there was just one method. The three Version 15.x upgrade methods are:
  • Active MUF Upgrade (new)
  • Parallel MUF Upgrade (new)
  • Traditional Upgrade (prior single method)
Active MUF Upgrade
This is the first new method for performing a Version 15.x MUF upgrade. The Version 14.0 MUF system resources that are involved in the Active MUF Upgrade process are:
  • CA Datacom® Datadictionary™
    (DD) and Data Definition Directory (DDD) databases and the ADRPNL VLS file
  • Dynamic System Tables (DST) database
  • CA Dataquery
    DQM data area
Each system resource can be upgraded independently or in sets. If an unexpected problem occurs with any one of the system resource upgrades, you can restore that system resource and can perform the upgrade of that resource again later. It is unlikely that a problem is encountered during any one of the component upgrades that would adversely impact the active MUF.
The new Active MUF Upgrade process is accomplished in two phases.
  • MUF Version 14.0 to 15.x Code Change Phase
    - Switches the Version 14.0 MUF that is to have its system resources upgraded to running with the version 15.x code level. This is the candidate MUF going forward in the document.
  • MUF Version 14.0 to 15.x System Resource Upgrade Phase
    - Upgrades the
    CA Datacom® Datadictionary™
    component, the
    CA Dataquery
    component, and the Dynamic System Tables database from Version 14.0 to Version 15.x.
MUF Version 14.0 to 15.x Code Change Phase
The Active MUF Upgrade process requires that the candidate MUF be running at the Version 15.x code level before upgrading its system resources. Two techniques are available to accomplish this. The traditional MUF shutdown and startup method or a Shadow MUF configuration transition.
The traditional method is accomplished by:
  • Shutting down the MUF
  • Modifying the JOBLIB/STEPLIB datasets to point to or contain the newer version code
  • Restarting the MUF
Although it is a small MUF downtime period, it requires all application access to be halted while the MUF recycle is performed.
Because all Version 14.0 and 15.x MUF system resources, including the CXX, are now release independent, the switch to the Version 15.x code level can also be performed using a Shadow MUF configuration.
The Shadow MUF configuration is accomplished by:
  • Shutting down the Version 14.0 Shadow MUF instance
  • Modifying the Shadow MUF JOBLIB/STEPLIB to point the Version 15.x code level
  • Restarting the MUF as a Version 15.x Shadow MUF
  • Making the Version 15.x Shadow MUF the Primary MUF
  • Making the Version 14.0 MUF the Shadow MUF data set
There are various techniques for performing the Primary to Shadow MUF transition. It is beyond the scope of this article to cover those techniques. If you are currently not running a Shadow MUF or MUFPLEX configuration and want more detailed information about these configurations, see the CA Datacom/DB Database and System Administration Version 15.x page.
MUF Version 14.0 to 15.x System Resource Upgrade Phase
Once the MUF to be upgraded is running at the Version 15.x code level, regardless of the technique that is used to accomplish it, the Active MUF Upgrade process is the same. As a part of the Active MUF upgrade process, a new CAI.HLQ.ACT.INSTJCL dataset is created. It contains the JCL members needed to upgrade a MUF systems resources from Version 14.0 to Version 15.x while it is enabled and processing user application requests. For more information about the Active MUF Upgrade process, see How to Perform an Active Multi-User Facility Upgrade.
Parallel MUF Upgrade
This is the second of the new methods for performing a Version 15.x MUF upgrade. The Version 14.0 MUF system resources that are involved in the Parallel Upgrade process are:
  • MUF directory (CXX)
  • CA Datacom® Datadictionary™
    (DD) database
  • Data Definition Directory (DDD) database
  • Dynamic System Tables (DST) database
It is deemed the least likely of the three methods to encounter a problem that impacts the MUF being upgraded because the upgrade process is done off line.
A Parallel Upgrade is accomplished in two phases. They are:
  • Version 14.0 to 15.x Parallel MUF Upgrade Phase
  • Version 15.x System Resource Implementation Phase
The two phases can be performed back to back or in sets depending on the situation. One Version 14.0 MUF could be upgraded and its Version 15.x system resource backups that are immediately implemented back into their original environment. Or, backups from multiple Version 14.0 MUFs could be upgraded by the Parallel Upgrade Phase and the upgraded Version 15.x system resource backups that are implemented back into their original environments as a set.
Version 14.0 to 15.x Parallel Upgrade Phase
The Parallel Upgrade Phase provides a means where you can upgrade a MUF instance to the next release level without interrupting application processing until the upgraded system resources are ready to be implemented back into their original environment. This process involves editing and running three new 15.x installation JCL members in addition to the traditional BDUPG
sfx
JCL members used to perform an upgrade while the candidate 14.0 MUF is out of service. A Parallel Upgrade is accomplished by:
  • Creating stable backups of candidate 14.0 MUF system resources
  • Creating a new standalone Version 15.x Parallel Upgrade MUF
  • Loading the Version 14.0 backups into Parallel Upgrade MUF
  • Editing and executing the new and traditional upgrade JCL members in the Parallel Upgrade MUF environment
  • Creating 15.x DBUTLTY backups of the now upgraded system resources
After the upgrade process completes successfully, the Parallel Upgrade environment system resource backups can be returned to their original environment at any time.
For more information, see How to Perform a Parallel Upgrade.
Version 14.0 System Resource Implementation Phase
Implementing the Version 15.x backups into the original Version 14.0 environment is accomplished by:
  • Shutting down the Version 14.0 MUF and associated CICS regions
  • Using DBUTLTY to replace the DD, DDD and DST definitions in the Version 14.0 CXX
  • Loading the Version 15.x DD and DDD backups
  • Modifying the candidate MUF startup JCL to use the Version 15.x code
  • Modifying the CICS(s) startup JCL members that are associated with the MUF
  • Updating the
    CA Datacom® Datadictionary™
    On-Line (DDOL) sign-on/off panels;
  • Restarting the candidate MUF and its associated CICS(s) regions
For complete details about the System Resource Implementation Phase, see How to Implement Parallel Upgrade MUF Resources.
Traditional MUF Upgrade
This method was the only one that was provided in prior
CA Datacom®
versions and is available for use in performing the Version 14.0 to Version 15.x upgrade if you want to use it. However, all user application activity must be disconnected from the MUF while the upgrade process is performed. It is deemed the most likely of the three methods to encounter an unexpected problem during the upgrade process. Depending on the nature of the problem, it could result in the upgrade process not completing in the time allotted to perform it.
For complete details about this method, see the Installing page.