IT Management

DB2 YDB Server for z/OS Version 8

5 Pages

The New Release migration is similar to migrations done in the past (say from DB2 V6 to DB2 V7). It invokes CATMAINT to migrate the catalog and directory to the Version 8 level, and includes:

  • Adding entries for new catalog objects (such as SYSIBM.SYSEBCDC)
  • Adding new columns to existing catalog tables
  • Changing data types of certain columns
  • Adding or changing catalog referential constraints.

Note that the column changes in this phase of migration are those involving FOR BIT DATA and no column lengths are being changed during the Compatibility Mode migration. Prior to running this migration, you must ensure that your DB2 V7 subsystem has installed the appropriate fallback SPE and DB2 has been started at least once.

In a data-sharing environment, all subsystems must have the fallback SPE applied before a migration is attempted.

After migration to New Function mode, there will be some incompatibilities, which are being extensively documented. See the appropriate manuals for further details. The important incompatibilities are:

  • Unicode Parser – Based on a new ZPARM setting, all SQL statements may be written into IFCID records in Unicode UTF-8 (not EBCDIC).
  • Customers will no longer be able to define or run LANGUAGE COMPJAVA stored procedures after migration. They must be converted to LANGUAGE JAVA.
  • New Function migration massively re-tailors the catalog, including converting it to Unicode. In particular:
  • Many catalog columns (especially those defining long names) are greatly expanded
  • Most of the catalog and directory tablespaces are converted to Unicode
  • Some tablespaces are reassigned to 8KB and 16KB virtual pools
  • The SYSLINKS and SYSPROCEDURES catalog tables are dropped •SYSDUMMY1 is moved to a new tablespace
  • Many indexes are changed to NOT PADDED.

This migration is done one catalog tablespace at a time using the Online Reorg utility. New Function migration is only supported from Compatibility Mode. All active DB2 subsystems must be at the proper catalog level. Once a system has been migrated to New Function mode in Version 8, there is no fallback to Version 8 Compatibility Mode or to DB2 Version 7.

Here are some additional considerations:

  • Plans and packages dependent on some of these catalog objects may be invalidated
  • You should ensure that Image Copies of all catalog and directory tablespaces exist or the New Function Mode conversion process cannot occur
  • Ensure that you have defined and sized the appropriate 8KB and 16KB virtual pools
  • Some catalog indexes may be placed in Advisory Reorg Pending state (AREO*) during the process and will be rebuilt as the process completes.

Once you have migrated to New Function mode, several incompatibilities may exist. Here are the most important ones:

  • CREATE INDEX now defaults to the ZPARM padding setting chosen. NOT PADDED is the default ZPARM chosen during installs, but defaults to PADDED for subsystems that are migrated.
  • Tablespace partitioning can now be table-based instead of index-based; hence, the syntax for CREATE TABLESPACE has changed.
  • Queries that accessed the catalog prior to its conversion to Unicode may have to be rewritten due to the Unicode values or collating sequence.


DB2 supports the coexistence of only two releases at a time. While DB2 V7 and DB2 V8 subsystems can coexist, this is only possible if the V8 subsystem(s) are in Compatibility Mode. Once any DB2 subsystem is in New Function Mode, all of the subsystem members will be in New Function Mode.


5 Pages