IBM Support

PI09804: ELIMINATE THE " END OF SQL CALL ALERT ", IF A SIMILAR ALERT HAS ALREADY BEEN GENERATED INFLIGHT FOR THE SAME CALL.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as new function.

Error description

  • Currently alerts are generated due to the following sequence of
    events:
    
    1. An "InFlight" alert is issued if SQL runs long enough to
    cross a threshold while the call is executing.
    
    2. An alert is issued at the end of the SQL call.
    
    3. At the close of the SQL section, a final alert is sent with
    the final statistics for that section
    
    This APAR eliminates the "End of SQL Call alert" if a similar
    alert has already been generated inflight for the same call.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of DB2 Query Monitor.                  *
    ****************************************************************
    * PROBLEM DESCRIPTION: Currently alerts are generated due to   *
    *                      the following sequence of events:       *
    *                      1. An "InFlight" alert is issued if     *
    *                      SQL runs long enough to cross a         *
    *                      threshold while the call is executing.  *
    *                      2. An alert is issued at the end of     *
    *                      the SQL call.                           *
    *                      3. At the close of the SQL section, a   *
    *                      final alert is sent with the final      *
    *                      statistics for that section.            *
    *                      This APAR eliminates the "End of SQL    *
    *                      Call alert" if a similar alert has      *
    *                      already been generated inflight for     *
    *                      the same call.                          *
    ****************************************************************
    * RECOMMENDATION: APPLY the PTF.                               *
    ****************************************************************
    Code has been changed to correct this condition.
    

Problem conclusion

Temporary fix

Comments

  • APPLY the PTF.
    

APAR Information

  • APAR number

    PI09804

  • Reported component name

    DB2 QUERY MONIT

  • Reported component ID

    5655E6701

  • Reported release

    310

  • Status

    CLOSED UR1

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-01-16

  • Closed date

    2014-04-07

  • Last modified date

    2014-05-02

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

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

    UI16795 UI16796

Modules/Macros

  • CQMMEXXX
    

Fix information

  • Fixed component name

    DB2 QUERY MONIT

  • Fixed component ID

    5655E6701

Applicable component levels

  • R310 PSY UI16795

       UP14/04/13 P F404

  • R320 PSY UI16796

       UP14/04/13 P F404

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":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"3.1.0","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
14 December 2020