Performing a Version 14.0 to 15.0 Multi-User Facility (MUF) Upgrade

Product: CA Datacom®/DB

Release: 15.0

OS: z/OS

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.0 completely removes the outage. Version 15.0 supports a CXX initialized and used as Version 14.0. In fact, 15.0 can only initialize a CXX as Version 14.0. There is no such thing as a CXX set as 15.0.

The new process employs few changes to the CXX between Versions 14.0 and 15.0. The full CXX options are compatible between the two releases. However, options known only to Version 15.0 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.0 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.0 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.0 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.0 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.0 refers to only the system database resources that are associated with a MUF instance. In the Version 15.0 upgrade these resources are the CA Datadictionary databases, the CA Dataquery database and the Dynamic System Tables database.

This Knowledge Base Article constitutes a portion of the official CA Datacom documentation for this CA product. This Knowledge Base Article is subject to the following notices, terms and conditions.

Overview

Beginning with Version 15.0, there are a total of three ways to upgrade a CA Datacom/DB Version 14.0 Multi-User Facility (MUF) to Version 15.0. In all prior CA Datacom versions, there was just one method. The three Version 15.0 upgrade methods are:

Active MUF Upgrade (new)
Parallel MUF Upgrade (new)
Traditional Upgrade (prior single method)

Changes made to Version 15.0 to make it compatible with Version 14.0

The following information summarizes the necessary changes.

A database that is opened in Version 15.0 and found to be FORMAT 2 (or 1) is upgraded to FORMAT 3. A message (DB00914) is issued to make note of the fact.
Data sets with secondary JCL allocations are noted as they are opened by a Version 15.0 MUF and saved to the CXX. Secondary allocations set in the FORMAT 2 definition from a prior setting by Version 15 remain and may or not be accurate until the area is opened by MUF again. Secondary allocations as noted previously are a new Version 15.0 feature that is documented and reported on in the REPORT AREA=CXX.
The URI reuse option is unset during an upgrade from FORMAT 2 to 3. Any index information existing from a prior setting is not used.
If a key was defined as having no access to a RAAT program from a previous time of the database being FORMAT 3 then that setting remains and is again in effect by Version 15.0.
A CXX initialized using Version 15.0 level code is set as Version 14.0.
A Version 15.0 DBUTLTY function ‘BACKUP AREA=CXX’ backs up all contents of the CXX, all formats the same as Version 14.0.
A Version 15.0 DBUTLTY function ‘LOAD AREA=CXX’ or ‘CXXCLONE’ that is connected to a Version 15.0 MUF will upgrade any FORMAT 2 (or 1) databases to FORMAT 3.

Changes made to Version 14.0 to make it compatible with Version 15.0

The following information summarizes the necessary changes.

The internal CXX level stays at 1 for both Version 14.0 and 15.0.
Version 15.0 is built to support and process databases set to FORMAT 3; whereas Version 14.0 is built to support and process databases set to FORMAT 2 (or 1).
A database that is opened in a Version 14.0 MUF and found to be FORMAT 3 is downgraded to FORMAT 2. A message (DB00914) is issued to make note of the fact.
Secondary JCL allocations is a new Version 15.0 FORMAT 3 feature. Any secondary JCL allocations known to a FORMAT 3 database remain unchanged by the downgrade to FORMAT 2. The information is not set, altered, or reported on by Version 14.0.
The URI reuse option is a new Version 15.0 FORMAT 3 feature. If a FORMAT 3 database is found with the URI reuse option set, Version 14.0 unsets it during the downgrade to FORMAT 2.
A key can be defined as having no access to a RAAT program in Version 15.0. If that CXX setting is present, it is not altered or reported on by Version 14.0.
A key can be defined as being in a status of ‘adding’ or ‘deleting’ in Version 15.0. If that CXX status is present, Version 14.0 physically removes it from the CXX.
A DBUTLTY function ‘BACKUP AREA=CXX’ backs up all contents of the CXX, all formats. The output information in both the Version 14.0 and 15.0 CXX backups is the same.
A DBUTLTY function ‘LOAD AREA=CXX’ or ‘CXXCLONE’ that is connected to a Version 14.0 MUF downgrades any FORMAT 3 databases to FORMAT 2. If the MUF is at Version 15.0 any FORMAT 2 (or 1) databases are modified to be FORMAT 3.

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.0 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 CA Datacom Installation Guide for z/OS Version 15.0.

Parallel MUF Upgrade

This is the second of the new methods for performing a Version 15.0 MUF upgrade. The Version 14.0 MUF system resources that are involved in the Parallel Upgrade process are:

MUF directory (CXX)
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.0 Parallel MUF Upgrade Phase
Version 15.0 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.0 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.0 system resource backups that are implemented back into their original environments as a set.

Active MUF Upgrade

This is the second new method for performing a Version 15.0 MUF upgrade. The Version 14.0 MUF system resources that are involved in the Active MUF Upgrade process are:

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.0 Code Change Phase – Switches the Version 14.0 MUF that is to have its system resources upgraded to running with the version 15.0 code level. This is the candidate MUF going forward in the document.
MUF Version 14.0 to 15.0 System Resource Upgrade Phase – Upgrades the CA Datadictionary component, the CA Dataquery component, and the Dynamic System Tables database from Version 14.0 to Version 15.0.

MUF Version 14.0 to 15.0 Code Change Phase

The Active MUF Upgrade process requires that the candidate MUF be running at the Version 15.0 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.0 MUF system resources, including the CXX, are now release independent, the switch to the Version 15.0 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 s to point the Version 15.0 code level
Restarting the MUF as a Version 15.0 Shadow MUF
Making the Version 15.0 Shadow MUF the Primary MUF
Making the Version 14.0 MUF the Shadow MUF dataset

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 Guide Version 15.0.

MUF Version 14.0 to 15.0 System Resource Upgrade Phase

The CXX no longer goes through a conversion process as a part of the upgrade. Therefore, the term "upgrade" in Version 15.0 refers to the system database resources associated with a CA Datacom/DB MUF. These resources are:

CA Datadictionary component
CA Dataquery component
Dynamic System Tables database

Important! In all cases, the MUF must already be running at the CA Datacom Version 15.0 code level before performing a Version 14.0 to 15.0 Active MUF upgrade.

The upgrade process can be performed in one of three different configurations:

Single MUF configuration – This configuration has one Version 15.0 MUF that is enabled and actively servicing application requests either locally or remotely through XCF or CCI connections. A MUF in this type of configuration is also referred to as a “Stand Alone MUF”. The CA Datadictionary (DD) database (default DBID 002), and the Data Definition Directory (DDD) database (default DBID 015) can be open and active in MUF at the time the upgrade process is performed. The same is true for the CA Dataquery and Dynamic System Tables database upgrades. You do not need to perform all three upgrades at the same time. However, the Datadictionary upgrade must be successfully completed first.
The detail regarding this process is documented in a separate scenario. For more information, see the scenario "How to Perform an Active Multi-User Facility (MUF) Upgrade".
Shadow MUF configuration - One fully enabled Version 14.0 primary MUF and one fully enabled.
MUFPLEX MUF configuration - Takes the resources from the parallel upgrade process and returns them to the original candidate MUF environment.

Copyright

This Documentation, which includes embedded help systems and electronically distributed materials, (hereinafter referred to as the “Documentation”) is for your informational purposes only and is subject to change or withdrawal by CA at any time. This Documentation is proprietary information of CA and may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in part, without the prior written consent of CA.

If you are a licensed user of the software product(s) addressed in the Documentation, you may print or otherwise make available a reasonable number of copies of the Documentation for internal use by you and your employees in connection with that software, provided that all CA copyright notices and legends are affixed to each reproduced copy.

The right to print or otherwise make available copies of the Documentation is limited to the period during which the applicable license for such software remains in full force and effect. Should the license terminate for any reason, it is your responsibility to certify in writing to CA that all copies and partial copies of the Documentation have been returned to CA or destroyed.

TO THE EXTENT PERMITTED BY APPLICABLE LAW, CA PROVIDES THIS DOCUMENTATION “AS IS” WITHOUT WARRANTY OF ANY KIND, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NONINFRINGEMENT. IN NO EVENT WILL CA BE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY LOSS OR DAMAGE, DIRECT OR INDIRECT, FROM THE USE OF THIS DOCUMENTATION, INCLUDING WITHOUT LIMITATION, LOST PROFITS, LOST INVESTMENT, BUSINESS INTERRUPTION, GOODWILL, OR LOST DATA, EVEN IF CA IS EXPRESSLY ADVISED IN ADVANCE OF THE POSSIBILITY OF SUCH LOSS OR DAMAGE.

The use of any software product referenced in the Documentation is governed by the applicable license agreement and such license agreement is not modified in any way by the terms of this notice.

The manufacturer of this Documentation is CA.

Provided with “Restricted Rights.” Use, duplication or disclosure by the United States Government is subject to the restrictions set forth in FAR Sections 12.212, 52.227-14, and 52.227-19(c)(1) - (2) and DFARS Section 252.227-7014(b)(3), as applicable, or their successors.