PI76644: WHEN STARTING FIRST TIME AFTER IPL, CQM MAY NOT COLLECT DATA IF OPTKEY(CORRNAME) IS ON AND GUARDIAM STAP IS MONITORING SAME DB2

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• If the STAP Collector (V9.1 or V10.0) is started first after an
  IPL and is monitoring a DB2 subsystem, CQM may not collect data
  if it is monitoring the same DB2 and was started after STAP,
  with the OPTKEY(CORRNAME) setting on.
  

Local fix

• 1. Stop CQM and STAP.
  2. Start CQM first, followed by STAP.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of IBM DB2 Query Monitor z/OS.         *
  ****************************************************************
  * PROBLEM DESCRIPTION: If the STAP Collector (V9.1 or V10.0)   *
  *                      is started first after an IPL and is    *
  *                      monitoring a DB2 subsystem, CQM may not *
  *                      collect data if it is monitoring the    *
  *                      same DB2 and was started after STAP,    *
  *                      with the OPTKEY(CORRNAME) setting on.   *
  ****************************************************************
  * RECOMMENDATION: APPLY the PTF.                               *
  ****************************************************************
  Code has been changed to correct this condition.
  

Problem conclusion

• APPLY the PTF.
  

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:

  UI46388

Modules/Macros

• CQM#SSMN
  

Fix information

• Fixed component name

  DB2 QUERY MONIT

• Fixed component ID

  5655E6701

Applicable component levels

• R330 PSY UI46388

     UP17/04/18 P F704

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.