IBM Support

PH06406: 00C90101 DSNKCEST:2001 OR 00C20305 DSNB1CPP+2504 ABEND AFTER A FAILED DFSMSHSM RECALL.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • 00C90101 DSNKCEST:2001 or 00C20305 DSNB1CPP+2504 abend after a
    failed DFSMShsm recall of some of the pieces of a multi-piece
    Db2 object.
    Db2 may also come down, if this failure occurs during a Db2
    "Must Complete" activity.
    This abend would only occur when the "LEVELID UPDATE FREQ"
    (DLDFREQ subsystem parameter) value is set to "NO" or a zero
    value.
    RC00C90101
    MODDSNKCEST
    ERQUAL2001
    RC00C20305
    MODDSNB1CPP
    OFFSET2504
    MSGDSNV086E
    RC00D94001
    ABEND04F
    

Local fix

  • Set the "LEVELID UPDATE FREQ" (DLDFREQ subsystem parameter)
    value to "YES" or a non-zero value, to enable down-level
    detection.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All Db2 11 and Db2 12 for z/OS users.        *
    ****************************************************************
    * PROBLEM DESCRIPTION: When a DFSMShsm recall fails on a       *
    *                      multi-piece non-partitioned object,     *
    *                      Db2 may abend if DLDFREQ is set to 0.   *
    ****************************************************************
    * RECOMMENDATION: Apply corrective PTF when available.         *
    ****************************************************************
    The problem occurs because there is a timing window where the
    catalog entry for the dataset that is being recalled doesn't
    exist. When this window is hit, DSM will not see the dataset in
    question and will fail to report the correct number of PB0s,
    even if one was already created. Thus, the PB0 will not be
    opened and a later attempt to extend into that space will
    cause Db2 to abend due to a PB0 already existing there.
    

Problem conclusion

  • The fix is to compare the created PB0s to the number reported by
    DSM to make sure that it is consistent. Furthermore, we enforce
    the RNA failure when HPGHPREF exceeds the last open dataset
    whether or not the SYSPDFRQ ZPARM is set.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH06406

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    B10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-12-11

  • Closed date

    2019-02-25

  • Last modified date

    2019-04-02

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

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

    UI61479 UI61481

Modules/Macros

  •    DSNB1OPP
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • RB10 PSY UI61481

       UP19/03/12 P F903

  • RC10 PSY UI61479

       UP19/03/12 P F903

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":"11.0","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":"11.0","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
02 April 2019