PK91945: BATCH CRD DOES NOT PROCESS LAST FILE WHEN DB2 SUBSYSTEM BEING MONITORED STOPS

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• A Batch CRD (Collect Report Data) job can be configured to
  collect DB2 trace data to a GDG dataset. When collecting to a
  GDG, the user can specify a job to post process the trace data
  when the GDG dataset switches.
  
  If the monitored DB2 comes down, the connection to the CRD
  collection job is lost and the CRD job stops. The post
  processing job is not submitted in this case.
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: OMEGAMON XE for DB2 PE/DB2PM                 *
  *                 users of component:                          *
  *                 -   PE Server subtask                        *
  *                 -   Classic Interface                        *
  *                 -   ISPF Monitoring dialogs                  *
  *                 -   Performance Expert Client                *
  *                 -   Batch Reporting                          *
  *                 -   Batch CRD                                *
  *                 -   Performance Warehouse users              *
  ****************************************************************
  * PROBLEM DESCRIPTION: - In case of an error in BatchCRD, the  *
  *                      last GDG generation is not processed.   *
  *                      - The GDG generations within BatchCRD   *
  *                      are too small when collecting a lot of  *
  *                      data.                                   *
  ****************************************************************
  * RECOMMENDATION: Apply this PTF                               *
  ****************************************************************
  PROBLEM SUMMARY:
  - If the monitored DB2 is stopped or the GDG generation is
  full, BatchCRD is also stopped but the last GDG generation is
  not processed. Now when BatchCRD is stopped, the last GDG
  generation is processed.
  - There was no possibility to specify the size of the different
  GDG generations for BatchCRD. Now you can specify a dataset
  size type when starting BatchCRD.
  
  PROBLEM CONCLUSION:
  - When BatchCRD is stopping (due to an error or not), process
  the last GDG generation.
  - To avoid the error dataset full, a new parameter has been
  defined for the BatchCRD: DSSIZE. This will allow the user
  to overwrite the default dataset allocation for each GDG
  generation. There will be 5 different dataset types (from BLK
  up to CYL).
  

Problem conclusion

• - When BatchCRD is stopping (due to an error or not), process
  the last GDG generation.
  - To avoid the error dataset full, a new parameter has been
  defined for the BatchCRD: DSSIZE. This will allow the user
  to overwrite the default dataset allocation for each GDG
  generation. There will be 5 different dataset types (from BLK
  up to CYL).
  
  KEYWORDS :
  BATCHCRD GDG FILE GENERATION NOT PROCESSED OUTPUT DATASET FULL
  

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:

  PK93793 UK49658

Modules/Macros

• BPOMAB00 BPOMAXA0 BPOMGIO0 DGO@BTCH DGO@CHKB
  DGO@CONV DGO@CRDP DGO@DB   DGO@DB2I DGO@DB2S DGO@DTA1 DGO@DTA3
  DGO@DTA5 DGO@DTA6 DGO@DTA7 DGO@LLOG DGO@LOAD DGO@MAIN DGO@MIG1
  DGO@MIG2 DGO@MT1  DGO@MT2  DGO@MT3  DGO@MT4  DGO@MT5  DGO@PC1
  DGO@PC2  DGO@PC3  DGO@PC4  DGO@PRV1 DGO@PRV2 DGO@SCRD DGO@SDOB
  DGO@SIDS DGO@SP   DGO@SQPA DGO@TBL  DGO@VW1  DGO@VW2  DGO@WRPA
  DGO@WRP2 DGO@WR2C DGO@WSTE DGOACMER DGOACREC DGOADYNA DGOASAVE
  DGOBMAIN DGOBMODL DGOBSELL DGODIDAT DGOEINIT DGOFPCRS DGOFPECO
  DGOFPE35 DGOFPSIC DGOFP000 DGOMAXA0 DGOMEDSN DGOMERPL DGOMGIO0
  DGOPMICO DGOPMIC1 DGOSSAVE DGOSSWSR DGOVBMG  DGOVCCP  DGOVCINI
  DGOZUAUT DGOZVW1  DGOZVW2  DGOZWDIV DGOZWFE  DGOZWIE  DGOZWJE
  DGOZWSE  DGOZWSTE FPE@DB2I FPE@DB2S FPE@WRPA FPE@WRP2 FPE@WR2C
  FPECHE35 FPECMAIN FPECQE35 FPECSORT FPECVCRS FPECVDDO FPECVICM
  FPECVOJS FPECVRMP FPECVRTZ FPECVSRD FPECVVCD FPECVVFN FPEMDSUB
  FPEMMAIN FPEUCBLD FPEUCXDL FPEUFIOI FPEUFIO2 FPEUFI24 FPEUFOCR
  FPEUFOC2 FPEUFUIS FPEUFUIT FPEUFWMX FPEUFYDY FPEUFYD2 FPEUHUGO
  FPEUPRNT FPEUT100 FPEVDB2I FPEVDB2S FPEVDB22 FPEVMST1 FPEVM000
  FPEVRACF FPEVREQ0 FPEVSERV FPEVSQLI FPEVWRPA FPEVWRP2 FPEVWR2C
  FPEVZMAI FPEVZRAC FPEZCRD  FPEZPMS  KO2PRCAP
  

Fix information

• Fixed component name

  OM XE DB2PE/PM

• Fixed component ID

  5655OPE00

Applicable component levels

• R410 PSY UK49658

     UP09/09/02 P F909

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.