IBM Support

PK74494: INVALID DATE '0000-00-00' SAVED INTO LASTUSED OF SYSPACKAGE / SYSPLAN 09/03/20 PTF PECHANGE

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Invalid date '0000-00-00' is saved in LASTUSED of SYSPLAN /
    SYSPACKAGE when binding a plan/package in V8 (after fallback
    from V9) , and the same problem can occur when running in
    co-existence mode.
    .
    The LASTUSED '01/01/0001' date is a valid date.  The LASTUSED
    field will be operational in V10 for SYSPACKAGES.
    .
    DB2MIGV10/K  DB2COEXIST/K
    DB2INCORR/K
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All DB2 V8 users who fall back from DB2 9 or *
    *                 are in a co-existence environment with       *
    *                 DB2 V8 and DB2 9.                            *
    ****************************************************************
    * PROBLEM DESCRIPTION: Incorrect values found in LASTUSED      *
    *                      column of a package(SYSPACKAGE)or plan  *
    *                      (SYSPLAN) record which has been created *
    *                      after fall back from a newer DB2        *
    *                      release, or in a coexistence            *
    *                      environment with DB2 V8 and DB2 9.      *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    After fall back from a newer DB2 release or in a coexistence
    environment with DB2 V8 and DB2 9, the newer catalog
    table SYSPACKAGE and SYSPLAN contain a column called LASTUSED
    which is not being used, nor properly initialized in the current
    release. Therefore, packages or plans created after the fall
    back process or in coexistence contain an incorrect value in the
    LASTUSED column of SYSPACKAGE or SYSPLAN table.
    

Problem conclusion

  • DB2 has been modified to properly initialize the LASTUSED column
    of SYSPACKAGE and SYSPLAN table during BIND PACKAGE/PLAN if a
    fall back situation or coexistence is detected. DB2 users who
    already have packages or plans with incorrect LASTUSED value
    need to FREE those packages or plans and BIND new ones to make
    the fix effective.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PK74494

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    810

  • Status

    CLOSED PER

  • PE

    YesPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2008-10-26

  • Closed date

    2009-01-19

  • Last modified date

    2011-05-09

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

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

    UK43330

Modules/Macros

  • DSNTBCM1 DSNTBCM2
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • R810 PSY UK43330

       UP09/02/06 P F902

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":"BU050","label":"BU NOT IDENTIFIED"},"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":"BU048","label":"IBM Software"},"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:
09 May 2011