CXX Upgrade

The process of upgrading from r11 to Version 12 differs from the process of upgrading from r10 to r11. The ability to leave the CXX at the previous release for a time is not allowed. Using the upgrade process requires the conversion of CXX to Version 12 and compatible solutions applied to r11 to provide protected access to its features.

During the upgrade to Version 12, the CXX is assigned a CXX level of LEVEL 1. The level is reported but there is no other immediate visibility. Additionally, a new database level format of FORMAT 1 is assigned to each database.

FORMAT 1 specifies that the database is compatible between Version 12 and r11 and features in Version 12 that are not compatible with r11 are disabled in Version 12.

The following are the disabled features of FORMAT 1 Version 12:

The ability to define the dynamic extend value in cylinders instead of tracks
The ability to have key level loaded status. One use of this status is having a loaded table with n keys, adding a new key, and to RETIX the new key instead of all keys.
The ability to have multiple index data sets within one database.

You can enable the Version 12 features that are disabled upon the decision that no fallback is needed from Version 12 to r11. Enable the Version 12 features with a DBUTLTY function that alters the format for all databases from FORMAT 1 to FORMAT 2.

If you need to fallback from Version 12, use Version 12 to backup its CXX, use r11 to initialize the CXX as r11, and execute Version 12 to convert the Version 12 backup into the r11 CXX. This restores the complete CXX r11 specifications and blocks Version 12 from access.

Important! It is presumed there is no need for fallback to r11 if you catalog a database with a new DBID to a Version 12 CXX, and the database is therefore set as FORMAT 2. If the Version 12 FORMAT 2 is not the desired format, the format should be set with DBUTLTY to FORMAT 1 after the catalog.