IBM Support

PK64261: RECP INCORRECTLY SET AFTER DSNU047I ON LOAD UTILITY AND EXCESSIVE GETPAGES DURING LOAD SHRLEVEL CH 08/06/04 PTF PECHANGE

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Running a LOAD utility with an unexisting or unspecified
    SYSREC dataset, after the job ends with rc=08 and message
    DSNU047I , the tablespace/partitions is/are left in RECP
    (DSNU560I).
    Also, Excessive GETPAGES during LOAD SHRLEVEL CHANGE on a
    partitioned table space with empty parts.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All DB2 for OS/390 or z/OS V7 users of PTF   *
    *                 UK21410, DB2 for z/OS V8 users of PTF        *
    *                 UK21411, and DB2 9 for z/OS utility users    *
    *                 of LOAD RESUME utility                       *
    ****************************************************************
    * PROBLEM DESCRIPTION: After applying V8 PTF UK21411 or for    *
    *                      all DB2 9 utility users,                *
    *                      LOAD RESUME YES leaves an empty         *
    *                      COMPRESS YES table space in RECP status *
    *                      after failing with MSGDSNU047I and      *
    *                      ending with RC8.                        *
    *                                                              *
    *                      After applying V7 PTF UK21410, V8 PTF   *
    *                      UK21411, or for all DB2 9 utility users *
    *                      LOAD SHRLEVEL CHANGE on a parititioned  *
    *                      table space with both empty and         *
    *                      non-empty partitions may encounter a    *
    *                      performance degradation in the UTILINIT *
    *                      phase.                                  *
    ****************************************************************
    * RECOMMENDATION: Apply corrective PTF when available          *
    ****************************************************************
    After applying V8 PTF UK21411 or for all DB2 9 Utility users the
    following problem can occur:
    A LOAD RESUME YES utility was run on an empty COMPRESS YES
    table space where the INDDN specified on the LOAD statement
    (INDDN SYSREC00) did not match the actual JCL DD card
    (//SYSREC).  The LOAD issued MSGDSNU047I - A REQUIRED DD CARD
    OR TEMPLATE IS MISSING.  NAME=SYSREC00 and MSGDSNU560I -
    TABLESPACE tsname PARTITION 1 IS IN RECOVER PENDING STATE and
    ended with RC8.  The table space should not be left in a RECP
    state when failing early in reload initialization.
    
    The problem can also occur for LOAD RESUME YES on an empty
    COMPRESS YES partition on a partitioned table space and for
    LOAD RESUME NO on an empty COMPRESS YES table space.
    
    After applying V7 PTF UK21410, V8 PTF UK21411, or for all DB2 9
    users the following problem can occur:
    LOAD RESUME YES SHRLEVEL CHANGE on a partitioned table space
    with both empty and non-empty partitions may encounter a
    performance degradation in the UTILINIT phase.  The performance
    degradation was caused by the check which determined if the
    partitions were empty causing additional GETPAGEs compared to
    before.  This check should have only been done for LOAD RESUME
    YES SHRLEVEL NONE on COMPRESS YES partitions.
    

Problem conclusion

  • Code has been modified for a LOAD RESUME YES or NO on an empty
    table space to remove the RECP state immediately following the
    procedure that required it.  This will leave the object
    available if an initialization error occurs.
    
    Code has been modified for LOAD RESUME YES to only check for
    empty partitions if SHRLEVEL NONE and COMPRESS YES is
    defined on the partition.
    

Temporary fix

  • *********
    * HIPER *
    *********
    

Comments

  • ž**** PE09/05/28 FIX IN ERROR. SEE APAR PK85985  FOR DESCRIPTION
    

APAR Information

  • APAR number

    PK64261

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    810

  • Status

    CLOSED PER

  • PE

    YesPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2008-04-10

  • Closed date

    2008-06-24

  • Last modified date

    2009-06-08

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

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

    UK37621 UK37622 UK37623 PK68325

Modules/Macros

  • DSNURWI
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • R710 PSY UK37621

       UP08/10/02 P F810 ®

  • R810 PSY UK37622

       UP08/10/02 P F810 ®

  • R910 PSY UK37623

       UP08/10/02 P F810 ®

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:
08 June 2009