IBM Support

PM01322: DB2 ONLINE CHECK INDEX JOBS CONTAIN MANY ADRXXX MESSAGES IN THE THE JOBLOG EVEN WHEN THE JOB RUNS WITHOUT ERRORS

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • This customer runs a lot of Online Check Index utilities in his
    shop and he complains about the excessive amount of DFDSS
    messages (ADRxxxx) in the job outputs, even when the jobs run
    fine.
    Messages can be directed to DSSPRINT dataset if the DD card is
    coded in the job, while if it is not coded the messages fill
    the SYSPRINT output.
    Customer would liKe DB2 to dynamically allocate the DSSPRINT
    dataset if the DD is not explicitely coded in the JCL.
    

Local fix

  • Code a DSSPRINT DD in the JCL.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All DB2 V8 for z/OS and DB2 9 for z/OS       *
    *                 users of CHECK utilities with SHRLEVEL       *
    *                 CHANGE                                       *
    ****************************************************************
    * PROBLEM DESCRIPTION: CHECK INDEX/LOB/DATA SHRLEVEL CHANGE    *
    *                      invokes DSSCOPY to copy shadow          *
    *                      data sets, but DSSPRINT DD card is      *
    *                      not honored for DSSCOPY messages.       *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    A DSSPRINT DD card was specified on a CHECK INDEX SHRLEVEL
    CHANGE job, but the DSSCOPY output was still routed to
    SYSPRINT. This error occurs on CHECK DATA SHRLEVEL CHANGE
    and CHECK LOB SHRLEVEL CHANGE as well.
    
    Additional Keywords: CHECK LOB DATA INDEX SHRLEVEL CHANGE
                         DSSPRINT
    

Problem conclusion

  • Modified CHECK utilities using SHRLEVEL CHANGE to honor the
    DSSPRINT DD card.
    
    When using DSSPRINT error messages for the DSSCOPY will
    be routed to the DSSPRINT DD card and will not appear
    in the utility job output routed to SYSPRINT.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM01322

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    810

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-11-16

  • Closed date

    2009-12-08

  • Last modified date

    2010-01-05

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

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

    UK52731 UK52732

Modules/Macros

  • DSNUKCOP DSNUKCPX
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • R810 PSY UK52731

       UP09/12/24 P F912

  • R910 PSY UK52732

       UP09/12/24 P F912

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":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEPEK","label":"Db2 for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.1","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.1","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
05 January 2010