PM92604: KO2O0801E MAXIMUM DB2S (32) BEING MONITORED

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• There is a product limit of Omegamon, only 32 monitored DB2
  ssids per LPAR.  This limit is controlled by the area in CSA
  with DB2 names.  This area is cleared only during re-IPL.
  
  The customer originally complained that they had message
  "KO2O0801E MAXIMUM DB2S (32) BEING MONITORED" although they had
  4 Omegamon STCs with 8 DB2 subsystems each.  And the reason of
  the original problem was that they tried to logon with 'fake'
  DB2 ssid "NONE" (it was treated as 33-d).  This problem was
  solved by PM82353(UK93441).
  
  From current data we see that the customer removed from
  monitoring 5 DB2 ssids and added 3 new ones.  And, although they
  have 30 DB2 ssids now, they begin to receive the messages about
  MAXIMUM DB2S (32) BEING MONITORED because area in CSA with DB2
  names still has old list of DB2 ssids names.
  
  We decided not to use this area any more and to utilize another
  logic to control the number of monitored DB2 ssids.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: OMEGAMON XE for DB2 PE/DB2PM                 *
  *                 users of component                           *
  *                 - Classic Interface                          *
  *                 - CUA Interface                              *
  *                 - NTH - Near Term History                    *
  ****************************************************************
  * PROBLEM DESCRIPTION: KO2O0801E MAXIMUM DB2S (32) BEING       *
  *                      MONITORED.                              *
  ****************************************************************
  * RECOMMENDATION: Apply this PTF                               *
  ****************************************************************
  PROBLEM SUMMARY:
  THE PRODUCT LIMIT OF 32 MONITORED DB2 SSIDS PER LPAR IS
  RELATED TO A 32-ENTRY TABLE WHICH IS ONLY RESET AT IPL TIME.
  
  PROBLEM CONCLUSION:
  CHANGE THE CODE TO UTILIZE ANOTHER METHOD OF CONTROLLING THE
  NUMBER OF MONITORED DB2 SSIDS.
  

Problem conclusion

• CHANGE THE CODE TO UTILIZE ANOTHER METHOD OF CONTROLLING THE
  NUMBER OF MONITORED DB2 SSIDS.
  

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:

  UK98301 UK98302 PM99346

Modules/Macros

• KO2CDCNB KO2HSVIB KO2HWLMB KO2OCMCB KO2ORCVB
  KO2OSBSB
  

Fix information

• Fixed component name

  OM XE DB2PE/PM

• Fixed component ID

  5655OPE00

Applicable component levels

• R510 PSY UK98301

     UP13/10/13 P F310

• R511 PSY UK98302

     UP13/10/13 P F310

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.