A fix is available
APAR status
Closed as program error.
Error description
The autodetect mechanism of the data server master (DGOVMSTR) is used to sense DB2 subsystems in the LPAR, we do a connect to DB2 to check whether it becomes alive or is still alive. For an example - 1. Assume the server is up and running - 2. Assume the server is searching for new DB2 subsystems every 3 secs - Now a new DB2 subsystem is started In case the server just did the autodetect we would again issue an identify in 3 secs to detect the new DB2 subsystem and begins monitoring. This is why there are so many identifies. . We will improve the identify function for autodetect.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: OMEGAMON XE for DB2 PE/DB2PM V310 * * users of component: * * - OMEGAMON Server * **************************************************************** * PROBLEM DESCRIPTION: When AUTODETECTION of DB2 subsystems * * is enabled for the DATA SERVER the * * LPAR is scanned for active DB2 * * subsystems every 3 seconds. This * * sample rate causes frequent module * * LOADS and connects to the sensed DB2 * * subsystems which generates CPU USAGE, * * DB2 activity and I/O ACTIVITY. * **************************************************************** * RECOMMENDATION: * ****************************************************************
Problem conclusion
The sample rate for autodetect will automatically decrease after start up of the data server from 3 seconds down to an ultimate sample interval of 3 minutes. When the ultimate sample rate is reached, new DB2 subsystems becoming active in the LPAR will no longer be detected instantaneously. Instead the detection may vary between immediately after start up of the DB2 subsystem and 3 minutes maximum. Detection of a stopping DB2 subsystem remains instantaneous. ------------------ SYSMOD TITLE: AUTODETECT KEYWORDS: AUTODETECT, DB2, LPAR
Temporary fix
Comments
APAR Information
APAR number
PK29100
Reported component name
OM XE DB2PE/PM
Reported component ID
5655OPE00
Reported release
310
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2006-08-01
Closed date
2006-08-11
Last modified date
2006-09-05
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK17136
Modules/Macros
DGOVMSTR
Fix information
Fixed component name
OM XE DB2PE/PM
Fixed component ID
5655OPE00
Applicable component levels
R310 PSY UK17136
UP06/08/15 P F608
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":"310","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":"310","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
05 September 2006