PK90623: BATCHCRD MISSING DATA START-DB2-MEMBER

Obtain the fix for this APAR.

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.         *
  *                      The submitted job from BatchCRD ends    *
  *                      with an abend S069 when processing      *
  *                      the data for the last GDG data.         *
  ****************************************************************
  * 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.
  When BatchCRD is terminated, the system is also terminating all
  submitted jobs that have been created by BatchCRD.
  The submitted job ends then with an abend S069.
  
  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.
  The adress space created for the new job is now no longer
  terminated by the system when BatchCRD is terminated.
  
  KEYWORDS: BATCHCRD IFCA DB2 MEMBER RESTART MISSING DATA
            S069 PROCESS JOB CANCELED
  

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.
  The adress space created for the new job is now no longer
  terminated by the system when BatchCRD is terminated.
  
  KEYWORDS: BATCHCRD IFCA DB2 MEMBER RESTART MISSING DATA
            S069 PROCESS JOB CANCELED
  

Temporary fix

Comments

APAR Information

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

  PK88698

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

  UK48395

Modules/Macros

• DGOZCRDC DGOZCRDS DGOZDB2M FPEZCRD  HKDB420J
  KDB420J
  

Fix information

• Fixed component name

  OM XE DB2PE/PM

• Fixed component ID

  5655OPE00

Applicable component levels

• R420 PSY UK48395

     UP09/07/28 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.