Migration step 19: Tailor Db2 12 catalog: DSNTIJTC

Job DSNTIJTC invokes the CATMAINT utility to migrate the Db2 11 catalog to the Db2 12 catalog, and its successful completion makes Db2 12 available for use.

Before you begin

Ensure that no incompatible applications will interfere with the catalog migration. For details, see Identify applications that are incompatible with online migration.

About this task

By completing this step, you migrate the Db2 catalog and make it available for use in Db2 12.

When you start Db2 12 before you complete this step, Db2 returns various messages because the Db2 12 catalog is not yet available for use. Examples include the following messages and reason codes:

  • Start of changeDSNT500I with reason code 00C900A6End of change
  • DSNT501I with reason code 00C900A6
  • Start of changeDSNL700I with reason code 00C900A6 (if DDF is auto-started). This message might be followed by messages DSNL007I and DSNL008I, indicating that DDF is terminating.End of change
  • Abend 04E with reason code 00E70014 (during DDL registration)
You can determine the existing restrictions by issuing the command after you start Db2. (However, this command might also generate message DSNT501I with reason code 00C900A6.)
-DSN1 DISPLAY DATABASE(*) SPACENAM(*) RESTRICT

DSNTIJTC contains the following job steps:

DSNTITC
Job step DSNTITC, which creates new catalog and directory objects, adds columns to existing catalog tables, and creates and updates indexes on the catalog tables to accommodate new Db2 12 objects. All IBM-supplied indexes are created or updated sequentially during the execution of this step. At migration to Db2 12 this job step updates that catalog level to V12R1M500.
Start of changeCHKTITCEnd of change
Start of changeJob step CHKTITC checks the return code of the CATMAINT utility. If the return code is 8 or greater, the job executes the job steps that follow CHKTITC.End of change
DSNTIRI
Job step DSNTIRI executes only when job step DSNTITC terminates abnormally or with a return code of 8 or greater. DSNTIRI rebuilds catalog indexes that were placed in REBUILD-pending status during execution of DSNTITC.
Start of changeDSNTITDEnd of change
Start of changeJob step DSNTITD executes only when job step DSNTITC terminates abnormally or with a return code of 8 or greater. DSNTITD issues the DISPLAY BLOCKERS command with the DETAIL option and displays information about locks or claims that might have interfered with the catalog migration.End of change

Procedure

To complete the tailoring of the Db2 catalog:

  1. Run job DSNTIJTC on your Db2 12 subsystem.

    A status message, DSNU777I, is issued at several points to indicate migration progress. Diagnostic error messages are issued when CATMAINT processing fails. If a problem is found during the SQL processing phase of migration, message DSNU778I is issued. If non-supported functions are encountered, message DSNU776I is issued. All of these messages are written to the SYSPRINT data set.

    If you receive abend reason code 00C200EF, the catalog and directory data sets are not in a compliant SMS environment.

    Start of change When the catalog update is complete, Db2 records the catalog level change in the SYSIBM.SYSLEVELUPDATES catalog table and issues message DSNG014I to the console.End of change

  2. If job DSNTIJTC fails, save the output and correct the problem.
    1. Terminate the CATMAINT utility if it is pending.
    2. Run job DSNTIJTC again without modification.
  3. If job DSNTIJTC fails again, return to Db2 11.
    Because CATMAINT failures roll back all Db2 12 changes, the catalog and directory are in the format of Db2 11. Altered indexes are not rolled back. Determine if any index is in a pending status by using the CHECK INDEX utility. To return to Db2 11, complete these steps:
    1. Rename procedures to use the libraries of your previous release.
    2. Reconnect TSO, IMS, and CICS® to the libraries of your previous release.
  4. If your previous release is damaged, you need to complete a point-in-time recovery to recover the system. To complete a point-in-time recovery:
    1. Restore your previous version's catalog and directory from image copies.
    2. Restore the BSDSs from archive logs that were made prior to migration.
    3. Flush the SCA (for data sharing environments only).
    4. Recover the catalog and directory indexes.
    When you remigrate to Db2 12, run the DSNTIJTC job again.

Results

Start of changeThe catalog is now tailored at catalog level V12R1M500, which supports Db2 12 function level 100, function level 500, and function level 501. For more information about function levels and catalog levels in Db2 12 continuous delivery, see Function levels and related levels in Db2 12.End of change

What to do next

  • If you received message DSNL700I with reason code 00C900A6 and DDF terminated after you started Db2 12 for the first time, start DDF manually after you run DSNTIJTC.
  • If the CATMAINT utility jobs from the previous step placed any altered Db2 catalog objects in REORG-pending (AREO*) advisory status, run the REORG utility for those objects.

Start of changeEnd of change