IBM Support

PH65521: UTILITIES ON DSNDB06.SYSTSUTL INSERT ROWS INTO SYSIBM.SYSUTILITIES TABLE WHEN USING SYSLISTD DD

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Customer has set zparm UTILITY_HISTORY=UTILITY.
    Customer is copying the utility history table DSNDB06.SYSTSUTL
    and has included the object with a LISTDEF from SYSLIST DD .
    History for this utility history catalog object is collected
    anyway when it should not.
    i.e.:
    //STEPLIB DD DSN=DB2A.DSNLOAD,DISP=SHR
    //SYSLISTD DD *
    LISTDEF LISTA1 INCLUDE TABLESPACE DSNDB06.SYSTSUTL
    //SYSIN DD *
    TEMPLATE COPYDASD DSN SYSADM.FIC.&TS..T&TI..COPY2
              UNIT 3390
     COPY LIST LISTA1 SHRLEVEL CHANGE COPYDDN(COPYDASD)
    ...
    DSNU3031I -DB2A 365 06:37:06.94 DSNUHUTL - UTILITY HISTORY
    COLLECTION IS ACTIVE.               <<<<
    LEVEL: UTILITY, EVENTID: 1003       <<<<
    DSNU1044I   365 06:37:06.94 DSNUGTIS - PROCESSING SYSLISTD AS
    EBCDIC
    DSNU1033I   365 06:37:06.94 DSNUGULM - PROCESSING LIST ITEM:
    TABLESPACE DSNDB06.SYSTSUTL
    
    It is documented there should be a restriction, see Db2 online
    doc at:
    
    https://www.ibm.com/docs/en/db2-for-zos/13?topic=history-utility
    
    "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 "
    
    The restriction should apply to both cases , when LISTDEF
    statement is either in SYSIN or in SYSLISTD .
    

Local fix

  • BYPASS/CIRCUMVENTION:
    Use LISTDEF in SYSIN DD
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All Db2 13 for z/OS users of utility jobs    *
    *                 that use LISTDEF library data sets to        *
    *                 specify utility history catalog objects      *
    *                 or directory table space DSNDB01.SYSUTILX.   *
    ****************************************************************
    * PROBLEM DESCRIPTION: Utilities using SYSLISTD DD for         *
    *                      LISTDEFs that INCLUDE:                  *
    *                      o Catalog utility history objects       *
    *                        incorrectly collects information and  *
    *                        updates SYSIBM.SYSUTILITIES           *
    *                        catalog table.                        *
    *                      o Directory table space                 *
    *                        DSNDB01.SYSUTILX should process it    *
    *                        as a special object, but do not.      *
    ****************************************************************
    * RECOMMENDATION: Apply corrective PTF when available          *
    ****************************************************************
    When utility history is active with UTILITY_HISTORY subsystem
    parameter set to UTILITY or OBJECT, the LISTDEFs specified in
    SYSLISTD DD are not checked for history objects.
    
    Special checking for utility history objects and SYSUTILX
    objects on LISTDEF definition libraries was not done.
    
    An example:
    SYSLISTD DD *
    LISTDEF list-name INCLUDE TABLESPACE DSNDB06.SYSTSUTL
    
    This problem can also occur when using a LISTDEF library by
    specifying OPTIONS LISTDEFDD ddname.
    
    Additional keywords: DSNDB06.SYSTSOEV
    TABLE SYSIBM.SYSUTILITIES SYSIBM.SYSOBJEVENTS
    INDEX SYSIBM.DSNULX01 SYSIBM.DSNULX02
    SYSIBM.DSNOEH01 SYSIBM.DSNOEH02
    INDEXSPACE DSNDB06.DSNULX01 DSNDB06.DSNULX02
    DSNDB06.DSNOEH01 DSNDB06.DSNOEH02
    TABLE SYSIBM.SYSUTIL SYSIBM.SYSUTILX
    

Problem conclusion

  • Utility code has been corrected to check LISTDEFs specified in
    LISTDEFDD (defaults to SYSLISTD) for utility history objects
    and SYSUTILX objects.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH65521

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    D10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2025-03-05

  • Closed date

    2026-03-10

  • Last modified date

    2026-04-02

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

    UO07095

Modules/Macros

  • DSNUGUTC DSNUILDR
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • RD10 PSY UO07095

       UP26/03/18 P F603

Fix is available

  • Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSEPEK","label":"DB2 for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"D10","Line of Business":{"code":"LOB70","label":"Z TPS"}}]

Document Information

Modified date:
02 April 2026