Migration step 18: Tailor DB2 10 catalog: DSNTIJTC

Job DSNTIJTC invokes the CATMAINT utility to migrate the catalog of the DB2® 9 to the DB2 10 catalog.

Before you begin

You must have appropriate authority to complete this task. For details, see .

Starting in DB2 10, data sets for the DB2 catalog and directory are managed by DB2 and must be SMS-managed. The SMS environment that you use for DB2 catalog and directory data sets must be established before you begin installation or migration to DB2 10. The SMS environment must include a data class for allocating the data sets in extended format and using extended addressability. You are not required to convert existing DB2 catalog and directory data sets to the SMS environment before migrating to DB2 10. These data sets will be converted the next time the related table space is reorganized.

In a data sharing environment, do not run DSNTIJTC after installing non-originating members.

About this task

DSNTIJTC contains one step that 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 10 objects. All IBM-supplied indexes are created or updated sequentially during the execution of DSNTIJTC.

To complete the tailoring of the DB2 catalog:

1. Run job DSNTIJTC on your DB2 10 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.

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 your previous DB2 release. Because CATMAINT failures roll back all DB2 10 changes, the catalog and directory are in the format of your previous DB2 release. Altered indexes are not rolled back. Determine if any index is in a pending status by using the CHECK INDEX utility. To return to your previous DB2 release:
   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 10, run the DSNTIJTC job again.

Results

When you start DB2 10 for the first time, you might receive message DSNT501I with reason code 00C900A6. You can ignore this message. Running job DSNTIJTC corrects the cause of this message.

After CATMAINT has run successfully and module DSNICUBC issues message DSNT501I, you can restart your real-time statistics collection by stopping and starting the DSNRTSDB database. In a data sharing group, migrate all members to DB2 10 before stopping and starting the DSNRTSDB database.