Reinitializing DSNDB01.SYSUTILX

You need to reinitialize the DSNDB01.SYSUTILX directory table space if you cannot successfully execute the DISPLAY UTILITY and TERMINATE UTILITY commands. In this case, DSNDB01.SYSUTILX is damaged and you cannot recover DSNDB01.SYSUTILX, because errors occur in the LOGAPPLY phase.

About this task

Because DSNDB01.SYSUTILX contains information about active and outstanding utilities, the process of reinitializing this table space involves determining which objects have a utility in progress and resolving any pending states to make the object available for access.

Procedure

If DSNDB01.SYSUTILX must be reinitialized, use the following procedure with caution:

  1. Issue the -DIS DB(*) SPACENAM(*) RESTRICT command and analyze the output. Write down the following items:
    • All of the objects with a utility in progress (The objects in UTUT, UTRO, or UTRW status have utilities in progress.)
    • Any pending states for these objects (RECP, CHKP, and COPY are examples of pending states.
  2. Edit the following installation jobs so that they contain only the commands that pertain to DSNDB01.SYSUTILX:
    1. DSNTIJDE: Edit this job so that it contains only the AMS statement to delete the VSAM linear data set (LDS) for DSNDB01.SYSUTILX.
    2. DSNTIJIN: Edit this job so that it contains only the AMS statement to define the VSAM LDS for DSNDB01.SYSUTILX, and tailor that statement to fit the needs of your DB2® system. If DB2 is running in conversion mode, use the DSNTIJIN job for the release you migrated from as your starting point for editing. Also, if the DEFINE statement for SYSUTILX contains a CONTROLINTERVALSIZE parameter, set it to 4096. If DB2 is running in enabling-new-function mode, the response depends on the current control interval size of the SYSUTILX VSAM data set; contact IBM® Software Support for guidance.
    3. DSNTIJID: Edit this job so that it initializes only DSNDB01.SYSUTILX. If DB2 is running in conversion mode, use the DSNTIJID job for the release you migrated from as your starting point for editing. Also, verify that this job allocates the SDSNSAMP library for that release and that the EXEC DSNTIN statement for SYSUTILX specifies SAMPLE=DSNTIS03. If DB2 is running in enabling-new-function mode, contact IBM Software Support for guidance.
  3. Start of changeIssue the following commands to stop table space DSNDB01.SYSUTILX and the indexes on tables in DSNDB01.SYSUTILX: 
    -STOP DATABASE(DSNDB01) SPACENAM(SYSUTILX)
-STOP DATABASE(DSNDB01) SPACENAM(DSNLUX01,DSNLUX02)
    End of change
  4. Run the three edited installation jobs in the order listed.
  5. Start of changeIssue these commands to start table space DSNDB01.SYSUTILX and the indexes on tables in DSNDB01.SYSUTILX: 
    -START DATABASE(DSNDB01) SPACENAM(SYSUTILX)
-START DATABASE(DSNDB01) SPACENAM(DSNLUX01,DSNLUX02)
    End of change
  6. Issue the -START DB(dbname) ACCESS(UT) command for each database that has objects with a utility in progress.
  7. Issue the -START DB(dbname)SPACENAM(spname) ACCESS(FORCE) command on each object with a utility in progress. This action clears all utilities that are in progress or in pending states. (Any pending states are cleared, but you still need to resolve the pending states as directed in the next step.)
  8. Resolve the pending states for each object by running the appropriate utility. For example, if an object was in the RECP status, run the RECOVER utility.
  9. Issue -START DB(dbname) ACCESS(RW) for each database.