Completing enabling-new-function mode (from Version 8 or Version 9) processing

You must complete several processing actions while your DB2® subsystem is in enabling-new-function mode (from Version 8 or Version 9), which is the mode between conversion mode (from Version 8 or Version 9) and new-function mode. New DB2 functions are not available when your DB2 subsystem is in enabling-new-function mode (from Version 8 or Version 9).

To complete enabling-new-function mode (from Version 8 or Version 9) processing:

1. Take an image copy of the DB2 catalog and directory.

   This step must be completed before running DSNTIJEN for the first time.

2. 
   If you had a user-managed real-time statistics database in your previous release, make it accessible so that DSNTIJEN can copy it.

   If you do not want the real-time statistics database of your previous release to be copied, delete it because it is not used after completion of DSNTIJEN. If you do not have a user-defined real-time statistics database (DSNRTSDB) defined, DSNTIJEN issues a warning for step ENFM1100 and skips execution of steps ENFM1103 and ENFM1105.

   
3. Create shadow data sets for user-defined indexes on the DB2 catalog that reside on user-managed storage.

   You must create shadow data sets for user-defined indexes that are on user-managed storage before you run job DSNTIJEN. DB2 uses these shadow data sets in the REORG steps that convert the catalog table spaces to new-function mode. One of the queries in job DSNTIJPM identifies the affected indexes.

4. Run job DSNTIJEN in LOCALSITE mode. If you run DSNTIJEN in REMOTESITE mode, it fails with an error message.
   Recommendation: Do not manually reorganize a table space or rebuild indexes on tables in that table space before the migration job step (ENFM0nn7) for that table space is complete.

   If you need to restart job DSNTIJEN, you can do so at any time. Always restart the whole job; do not use step restart. Job DSNTIJEN automatically locates and resumes processing of the first table space that was not completely processed. Job steps ENFM000A and ENFM000B automatically detect and copy any DB2 catalog and directory table spaces that were left in COPY-pending or informational COPY-pending status when DSNTIJEN previously ended. If you need to determine how much of the enabling-new-function mode process has completed, use the DISPLAY GROUP DETAIL command.

   If the job fails at a table space migration step (ENFM0nn7) because of an unrecoverable sort program work space shortage, use one of these options:

   • Increase the number of temporary data sets indicated by the SORTNUM option of the REORG TABLESPACE control statement in the failing step.
   • Remove the SORTNUM and SORTDEVT options of the REORG TABLESPACE control statement, and allocate sort work (SORTWKxx) files in the failing step.

   Expect a return code of 1 from job steps ENFM0020 and ENFM0030, which convert the SPT01 and DBD01 directory table spaces. Directory objects do not have DDL invoked, so their enabling-new-function mode conversion is different from the conversion for catalog table spaces, which uses DDL. Job steps ENFM0010 and ENFM0040, which process the SYSUTILX and SYSLGRNX directory table spaces, end with a return code of 0 because no conversion is performed.

   
   During copying of the user-defined real-time statistics database to the DB2-defined real-time statistics database (job steps ENFM1103 and ENFM1105), DB2 might issue message DSNT501I with reason code 00C90080. You can ignore this message.
   

5. Take an image copy of the DB2 catalog and directory after job DSNTIJEN has completed processing.
6. Optional: Run job DSNTIJCI to run the CHECK INDEX utility on all the catalog and directory indexes that were modified or added by job DSNTIJEN.