Start of change

Utility history restrictions and stopped utilities

FL 501 Utility history collection has some limitations, including restrictions for utility history catalog objects. Additionally, if a utility terminates or abends during utility history collection, the SYSUTILITIES row is updated upon termination, FL 504 but the SYSOBJEVENTS rows are not updated or deleted.

Utility history catalog objects

The utility history catalog objects are:

  • the SYSIBM.SYSUTILITIES table and its indexes
  • FL 504the SYSIBM.SYSOBJEVENTS table and its indexes
  • the DSNDB06.SYSTSUTL table space
  • FL 504the DSNDB06.SYSTSOEV table space

You can run utilities on these objects as needed. However, do not include other objects in the utility statement or list. When a utility needs exclusive use of or allows only limited access to the utility history catalog objects, avoid running other utilities so that utility history collection is not affected. For more information about backing up and recovering these objects, see Copying catalog and directory objects and Recovering catalog and directory objects.

Restrictions

Utility history and utility object-level history is not collected for the following situations:

  • When utilities are executed on the utility history catalog objects
  • When utilities are executed on other objects and the utility history catalog objects are in one of the following states:
    • a UTRO or UTUT utility-in-progress state
    • a prohibitive state, such as CHECK-pending, COPY-pending, GRECP (Group buffer pool RECOVER-pending), LPL (logical page list), REBUILD-pending, RECOVER-pending, REFRESH-pending, REORG-pending, RESTART-pending, or WEPR (write error page range)
    • started for read-only access (including persistent read-only)
    • stopped
  • When RECOVER or REBUILD INDEX is executed on any of the following catalog and directory objects:
    • table space DSNDB01.SYSUTILX, indexes SYSIBM.DSNLUX01 and SYSIBM.DSNLUX02
    • table space DSNDB01.DBD01, index SYSIBM.DSNDB01X
    • table space DSNDB01.SYSDBDXA, index SYSIBM.DSNDB1XA
    • table space DSNDB06.SYSTSCPY, indexes SYSIBM.DSNUCH01, SYSIBM.DSNUCX01, and any user created indexes
    • table space DSNDB01.SYSLGRNX, indexes SYSIBM.DSNLLX01 and SYSIBM.DSNLLX02
    • table space DSNDB06. SYSTSSTG, index SYSIBM.DSNSSH01 and any user created indexes
    • table space DSNDB06.SYSTSVOL, index SYSIBM.DSNSSH02 and any user created indexes
  • When the PREVIEW JCL parameter or OPTIONS PREVIEW is specified for the utility job step. In preview mode, normal utility execution does not occur.
  • When the utility parser has found a syntax error in a utility statement

Stopped utilities

If a utility abends, the SYSUTILITIES and SYSOBJEVENTS rows are not updated. Specifically:
  • For SYSUTILITIES, the ENDTS and RETURNCODE columns remain null, and the CONDITION column remains blank. The utility is in a stopped state, and the SYSUTILITIES row is not updated until termination, either after a restart or with the TERM UTIL command. A TERM UTIL command issued on a stopped utility updates the ENDTS, ELAPSEDTIME and CONDITION columns. A START DATABASE(…) SPACENAM(…) ACCESS(FORCE) command, which terminates a stopped utility, also updates these columns. The ENDTS and ELAPSEDTIME column values reflect the time when the utility was terminated by the command; the time when the utility was in a stopped status is included in ELAPSEDTIME. The CONDITION column value is set to T for TERM UTIL or F for START DATABASE with ACCESS(FORCE).
  • FL 504For SYSOBJEVENTS, the rows are not updated or deleted when a utility abends, or when the TERM UTIL and START DATABASE ACCESS(FORCE) commands are issued and the utility is terminated. Restart of a utility inserts or updates SYSOBJEVENTS rows as needed for object-level history collection.

If a TERM UTIL command is issued on an active utility, the ENDTS, ELAPSEDTIME and CONDITION columns in SYSUTILITIES are updated by the utility during termination processing. FL 504 SYSOBJEVENTS is not updated.

End of change