A fix is available
APAR status
Closed as program error.
Error description
Currently DDF threads are included in the value of "Current Threads" attribute in "Subsystem Management" TEP workspace but not included in the value of "Max Threads allowed" attribute. This difference causes value of "Thread Utilization" attribute to be senseless as it is the ratio of "Max Threads allowed" and "Current Threads".
Local fix
N/A
Problem summary
**************************************************************** * USERS AFFECTED: OMEGAMON XE for DB2 PE/DB2PM * * users of component: * * - D5API * * - The component that transfers DB2 * * monitoring data collected by the * * OMEGAMON collector to the TEMA * **************************************************************** * PROBLEM DESCRIPTION: Database Access threads were * * incorrectly included in Current * * Thread and Thread Utilization * * attribute values * * * **************************************************************** * RECOMMENDATION: Apply this PTF * * * **************************************************************** PROBLEM SUMMARY: Database Access threads were incorrectly included in Current Thread and Thread Utilization attribute values. PROBLEM CONCLUSION: 1. Remove Database Access Threads from Current Thread and Thread Utilization attribute values 2. Update XE help for the following attributes in attribute group DB2 SRM Subsystem Current Threads - The current number of active threads; Database Access threads are not included. Thread Utilization - The percentage of available threads being used; this percentage is calculated as Current Threads/CTHREAD parameter in DSNZPARM *100; Database Access threads are not included. Valid entry ranges from 0.0 to 100.0.
Problem conclusion
1. Remove Database Access Threads from Current Thread and Thread Utilization attribute values 2. Update XE help for the following attributes in attribute group DB2 SRM Subsystem Current Threads - The current number of active threads; Database Access threads are not included. Thread Utilization - The percentage of available threads being used; this percentage is calculated as Current Threads/CTHREAD parameter in DSNZPARM *100; Database Access threads are not included. Valid entry ranges from 0.0 to 100.0. KEYWORDS : CURRENT THREAD UTILIZATION
Temporary fix
Comments
APAR Information
APAR number
PM76283
Reported component name
OM XE DB2PE/PM
Reported component ID
5655OPE00
Reported release
510
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2012-11-01
Closed date
2013-01-25
Last modified date
2017-06-21
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
PM81053 UK91183
Modules/Macros
KO2APCAA KO2APCA2 KO2APCJA KO2APCJK KO2APCJ2
Fix information
Fixed component name
OM XE DB2PE/PM
Fixed component ID
5655OPE00
Applicable component levels
R510 PSY UK91183
UP13/01/29 P F301
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":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSAV2B","label":"IBM Db2 Buffer Pool Analyzer for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.1.0","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}},{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCT4H5","label":"IBM Tivoli OMEGAMON XE for Db2 PE \/ PM \/ BPA"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.1.0","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
21 June 2017