PK63984: PROBLEM AFTER THE GDG+255 SWITCH.

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• In the job where we postprocess the switched
  tracedataset, I can conclude that  the
  allocatetion of the  underlaying dataset I
  refer to as SYSP.OMMONX2.OMDB2VFM(-1) remains
  the same after hidding the gdg+255.
  Logs says ex: IGD104I SYSP.OMMONX2.OMDB2VFM.G3555V00
  until I recycle the DGOZCRD trace job. After recycle,
  I get a new dataset again (G3556V00, and so on) until
  +255. I think the question is, is it a GDG problem
  every time one hits the limit, or is it DGOZCRD,
  conflicting here ?
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: OMEGAMON XE for DB2 PE/DB2PM                 *
  *                 users of component:                          *
  *                 -   Batch Reporting                          *
  ****************************************************************
  * PROBLEM DESCRIPTION: GDG Batch CRD fails. Wrong GDG member   *
  *                      used for the Batch reporting, this      *
  *                      result in duplicate records (wraparound *
  *                      is not working correctly).              *
  *                                                              *
  ****************************************************************
  * RECOMMENDATION: Apply this PTF                               *
  ****************************************************************
  PROBLEM SUMMARY:
  Old GDG members are not deleted correctly when the GDG limit
  is reached. Wrong GDG member is then used as input for the Batch
  Reporting, this could result in wrong or duplicate records in
  the report.
  
  PROBLEM CONCLUSION:
  The way how the GDG are handled has been changed.
  

Problem conclusion

• The way how the GDG are handled has been changed.
  
  KEYWORDS :
  BATCH CRD GDG SWITCH FAILS DUPLICATE ENTRIES
  

Temporary fix

Comments

APAR Information

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

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

  UK35343

Modules/Macros

• DGOZCRD  DGOZCRDC
  

Fix information

• Fixed component name

  OM XE DB2PE/PM

• Fixed component ID

  5655OPE00

Applicable component levels

• R410 PSY UK35343

     UP08/04/16 P F804

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.