IBM Support

PK71568: DB2 COLLECT REPORT DATA BATCH JOB DOES NOT RUN THE FINAL FOLLOW UP JOB AFTER TERMINATING

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When GDGDATASET() and JOB() parms are specified for the Collect
    Report Data job and the CRD job was stopped, the task specified
    in JOB() parm does not run so the last portion of collected data
    remains unprocessed.
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: OMEGAMON XE for DB2 PE/DB2PM                 *
    *                 users of component:                          *
    *                 -   Batch Reporting                          *
    ****************************************************************
    * PROBLEM DESCRIPTION: When GDGDATASET() and JOB() parms are   *
    *                      specified for CRD batch job there are   *
    *                      some problems to specify proper         *
    *                      generation dataset for JOB() because    *
    *                      this follow-up job runs in parallel     *
    *                      with accumulation job and last one      *
    *                      creates new generation faster than      *
    *                      JES submits follow-up job.              *
    *                                                              *
    ****************************************************************
    * RECOMMENDATION: Apply this PTF                               *
    ****************************************************************
    PROBLEM SUMMARY:
    When GDGDATASET() and JOB() parms are specified for CRD batch
    job there are some problems to specify proper generation
    dataset for JOB() because this follow-up job runs in parallel
    with accumulation job and last one creates new generation
    faster than JES submits follow-up job.
    
    PROBLEM CONCLUSION:
    Give an opportunity to invoke follow-up job with parameter
    &GDGDSN which is the last closed GDG.
    

Problem conclusion

  • Give an opportunity to invoke follow-up job with parameter
    &GDGDSN which is the last closed GDG.
    
    KEYWORDS : CRD BATCH GDGDATASET INVOKE JOB TIMING PROBLEM
    

Temporary fix

Comments

APAR Information

  • APAR number

    PK71568

  • 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

    2008-09-05

  • Closed date

    2008-10-31

  • Last modified date

    2008-12-02

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

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

    UK41243

Modules/Macros

  • DGOZCRDC FPEZCRD
    

Publications Referenced
SC18998302    

Fix information

  • Fixed component name

    OM XE DB2PE/PM

  • Fixed component ID

    5655OPE00

Applicable component levels

  • R410 PSY UK41243

       UP08/11/05 P F811

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:
02 December 2008