IBM Support

PK88698: BATCHCRD MISSING DATA START-DB2-MEMBER

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • In a datasharing group,
    Batch CRD is started on one LPAR with 2 members
    and one member on another lpar is started afterwards.
    The data seems to not be collected for the new member.
    

Local fix

  • n/a
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: OMEGAMON XE for DB2 PE/DB2PM                 *
    *                 users of component                           *
    *                 - Batch CRD                                  *
    *                 - Performance Warehouse user                 *
    ****************************************************************
    * PROBLEM DESCRIPTION: If a DB2 member was started after       *
    *                      BatchCRD was started, data were not     *
    *                      collecting for this new member.         *
    ****************************************************************
    * RECOMMENDATION: Apply this PTF                               *
    ****************************************************************
    PROBLEM SUMMARY:
    The handling of the IFCAs of all DB2 members was not done
    correctly. (Re)started DB2 members were not taken in
    consideration for the data collection.
    
    PROBLEM CONCLUSION:
    The IFCAs of all DB2 members, after the READA, is now handled
    correctly. If a DB2 member is started afterwards or the traces
    are not here anymore, the DB2 traces are restarted for the DSG
    group.
    
    KEYWORDS: BATCHCRD IFCA DB2 MEMBER RESTART MISSING DATA
    

Problem conclusion

  • The IFCAs of all DB2 members, after the READA, is now handled
    correctly. If a DB2 member is started afterwards or the traces
    are not here anymore, the DB2 traces are restarted for the DSG
    group.
    
    KEYWORDS: BATCHCRD IFCA DB2 MEMBER RESTART MISSING DATA
    

Temporary fix

Comments

APAR Information

  • APAR number

    PK88698

  • Reported component name

    OM XE DB2PE/PM

  • Reported component ID

    5655OPE00

  • Reported release

    410

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-06-12

  • Closed date

    2009-07-01

  • Last modified date

    2009-08-03

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

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

    UK47715 PK90623

Modules/Macros

  • DGOZCRDC DGOZCRDS DGOZDB2M FPEZCRD  HKDB410J
    KDB410J
    

Fix information

  • Fixed component name

    OM XE DB2PE/PM

  • Fixed component ID

    5655OPE00

Applicable component levels

  • R410 PSY UK47715

       UP09/07/08 P F907

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":"SSAV2B","label":"IBM Db2 Buffer Pool Analyzer for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"410","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}},{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCT4H5","label":"IBM Tivoli OMEGAMON XE for Db2 PE \/ PM \/ BPA"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"410","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
03 August 2009