IBM Support

PI86365: DYNAMIC ACTIVATED MONITORING AGENT THEN DYNAMICALLY DEACTIVATED SHOULD NOT AUTOMATICALLY REACTIVATE IF THE DB2 IS RESTARTED

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When a Monitoring Agent is dynamically activated for a DB2 and
    then subsequently dynamically deactivated, it should not
    automatically reactivate if the DB2 subsystem is restarted.
    The Monitoring Agent will now remain deactivated for that DB2
    until it has been activated again by the user.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of IBM DB2 Query Monitor z/OS.         *
    ****************************************************************
    * PROBLEM DESCRIPTION: When a Monitoring Agent is dynamically  *
    *                      activated for a DB2 and then            *
    *                      subsequently dynamically deactivated,   *
    *                      it should not automatically reactivate  *
    *                      if the DB2 subsystem is restarted.      *
    *                      The Monitoring Agent will now remain    *
    *                      deactivated for that DB2 until it has   *
    *                      been activated again by the user.       *
    ****************************************************************
    * RECOMMENDATION: APPLY the PTF.                               *
    ****************************************************************
    Code has been changed to correct this condition.
    

Problem conclusion

  • APPLY the PTF.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI86365

  • Reported component name

    DB2 QUERY MONIT

  • Reported component ID

    5655E6701

  • Reported release

    320

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-08-24

  • Closed date

    2018-01-10

  • Last modified date

    2018-02-01

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

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

    UI53115 UI53116

Modules/Macros

  • CQM#SSMN
    

Fix information

  • Fixed component name

    DB2 QUERY MONIT

  • Fixed component ID

    5655E6701

Applicable component levels

  • R320 PSY UI53115

       UP18/01/18 P F801

  • R330 PSY UI53116

       UP18/01/18 P F801

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.2.0","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
14 December 2020