A fix is available
APAR status
Closed as program error.
Error description
An invalid managed system name may appear in the TEP interface. The invalid name will look something like :DB2plex:DSGROUP There will be no name before the DB2plex portion of the origin node. DB2DSGRP is set incorrectly to x'0000000000000000' instead of x'4040404040404040' when the DB2 subsystem is not a member of a Data Set Group ( DSG ), resulting in an incorrect db2plex node name. In one case, exporting informaton to a spreadsheet, including DB2DSGRP, resulted in an invalid origin node name. Additional Keywords: incorrout db2 dsgrp data sharing group dsg
Local fix
No workaround
Problem summary
**************************************************************** * USERS AFFECTED: OMEGAMON XE for DB2 PE/DB2PM * * users of component: * * - The component that transfers DB2 * * monitoring data collected by the * * OMEGAMON collector to the TEMA * * - Classic Interface * **************************************************************** * PROBLEM DESCRIPTION: DB2DSGRP is set incorrectly to * * x'0000000000000000' instead of * * x'4040404040404040' when the DB2 * * subsystem is not a member of DSG. * **************************************************************** * RECOMMENDATION: Apply this PTF * * * **************************************************************** PROBLEM SUMMARY: Data Sharing Group name is set incorrectly when the DB2 subsystem is not a member of DSG. The result is an incorrect db2plex node name in TEP. PROBLEM CONCLUSION: Change logic to provide the correct name of Data Sharing Group when the DB2 subsystem is not a member of DSG.
Problem conclusion
Change logic to provide the correct name of Data Sharing Group when the DB2 subsystem is not a member of DSG. KEYWORDS : DB2DSGRP x'0000000000000000' x'4040404040404040' DB2 SUBSYSTEM DSG
Temporary fix
Comments
APAR Information
APAR number
PM04452
Reported component name
OM XE DB2PE/PM
Reported component ID
5655OPE00
Reported release
420
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-01-06
Closed date
2010-04-26
Last modified date
2010-05-04
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK56393
Modules/Macros
KO2OTCIA KO2OTCIS KO2OTCI2
Fix information
Fixed component name
OM XE DB2PE/PM
Fixed component ID
5655OPE00
Applicable component levels
R420 PSY UK56393
UP10/05/01 P F004
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":"4.2.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":"4.2.0","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
04 May 2010