IBM Support

PM82953: ABEND60D-18 POSSIBLE ABEN0CX OR NO STATISTICS BEING COLLECTED OF AN ISOLATED THREAD, MISSING MONITORING DATA FOR A THREAD

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Isolated ABEND60D-18, possible ABEN0CX, or no statistics being
    collected for an isolated thread and missing monitoring data for
    a thread. abends60d s060d 60d
      Code is being added so that the IARV64 DISCARDDATA,KEEPREAL=NO
    request will ignore CLEAR=YES. There could potentially be memory
    object segments that are not cleared after product recycle. In
    order to logically perform a KEEPREAL=NO and CLEAR=YES code will
    be added to do a DISCCARDDATA CLEAR=YES followed by a
    DISCCARDDATA KEEPREAL=NO on start up.
    NOTE: The DB2 Query Monitor Collector started task shares code
    with the DB2 Audit Management Expert Collector and the
    InfoSphere Guardium S-TAP Collector started tasks. Customers
    running the Collector with either (or both) DB2 Query Monitor
    and DB2 Audit Management Expert or InfoSphere Guardium S-TAP may
    experience this problem.
    

Local fix

  • When cycling the CQM Collector STC, stop the CQM Master Address
    Space (CQMMSTR) and edit the CQMPARMS to change the
    MASTER_PROCNAME(xxxxxxxx) - to a value not used before.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of DB2 Query Monitor.                  *
    ****************************************************************
    * PROBLEM DESCRIPTION: Isolated ABEND60D-18, possible ABEN0CX, *
    *                      or no statistics being collected for    *
    *                      an isolated thread and missing          *
    *                      monitoring data for a thread.           *
    *                      abends60d s060d 60d                     *
    *                      Code is being added so that the IARV64  *
    *                      DISCARDDATA,KEEPREAL=NO request will    *
    *                      ignore CLEAR=YES. There could           *
    *                      potentially be memory object segments   *
    *                      that are not cleared after product      *
    *                      recycle. In order to logically perform  *
    *                      a KEEPREAL=NO and CLEAR=YES code will   *
    *                      be added to do a DISCCARDDATA           *
    *                      CLEAR=YES followed by a DISCCARDDATA    *
    *                      KEEPREAL=NO on start up.                *
    *                      NOTE: The DB2 Query Monitor Collector   *
    *                      started task shares code with the DB2   *
    *                      Audit Management Expert Collector and   *
    *                      the InfoSphere Guardium S-TAP Collector *
    *                      started tasks. Customers running the    *
    *                      Collector with either (or both) DB2     *
    *                      Query Monitor and DB2 Audit Management  *
    *                      Expert or InfoSphere Guardium S-TAP     *
    *                      may experience this problem.            *
    ****************************************************************
    * RECOMMENDATION: APPLY the PTF.                               *
    ****************************************************************
    Code has been changed to correct this condition.
    

Problem conclusion

  • APPLY the PTF.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM82953

  • Reported component name

    DB2 QUERY MONIT

  • Reported component ID

    5655E6701

  • Reported release

    230

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-02-15

  • Closed date

    2013-03-12

  • Last modified date

    2013-04-02

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

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

Modules/Macros

  • CQM#DRVX CQM#RESM CQM#REST CQM#SDIR CQM#SSMN
    CQM#SWTX CQMISMSX CQMMALOX CQMMINIX CQMMT2A1 CQMMT281 CQMMT291
    

Fix information

  • Fixed component name

    DB2 QUERY MONIT

  • Fixed component ID

    5655E6701

Applicable component levels

  • R230 PSY UK92452

       UP13/03/20 P F303

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

Document Information

Modified date:
14 December 2020