A fix is available
APAR status
Closed as new function.
Error description
New counters in IFCID 1 (QWOS section) and new IFCID 197 (DB2 Messages) can be shown in the TEP user interface. Additionally IFCID 225 is enabled for the TEP user interface.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: OMEGAMON XE for DB2 PE/DB2PM * * users of component: * * - OMEGAMON Server * * - PE Server * * - Common Collector * * - Tivoli Enterprise Monitoring Agent * * - ICAT * **************************************************************** * PROBLEM DESCRIPTION: SUPPORT OF DB2 INSTRUMENTATION * * ENHANCEMENTS: IFCID 1, IFCID * * 197 in Tivoli Enterprise Portal. * * ENABLEMENT OF IFCID 225 IN * * Tivoli Enterprise Portal. * * * * Additional ICAT problems fixed: * * * * I1: For the LROWS parameter in the * * Classic interface configuration a * * minimum value of 99 is acceptable. * * Currently the user can specify all * * values in the range from 1 to 9999. * * * * I2: In case you have configured more * * than one DB2 subsystems and you * * want to use Automatic Exception * * Processing only for one DB2 * * subsystem and you specified values * * for the Exception log dataset or * * the Exception file dataset, * * then you will get a RC=12 when you * * run the "Allocate additional * * runtime datasets" job. * * * * I3: If you enable Near-Term History or * * Object Analysis during * * configuration then these functions * * are started for each DB2 subsystem * * at startup of the OMEGAMON Server. * * When you create the runtime * * members you can specify the * * DB2 subsystems that you want to * * monitor. When you have configured * * more than one DB2 subsystems and * * OA or NTH enabled, but when you * * generate the runtime members you * * decide not to monitor a certain * * DB2 subsystem then OA or NTH is * * still started for this DB2 * * subsystem. * * I4: Starting the Event Collection * * Manager (Object Analysis) in * * seperate started task is an option * * that is not applicable any more * * and has to be removed from the * * ICAT configuration. * * * * P1: UNICODE attributes in different * * TEP workspaces ("Thread Activity", * * "Locking Conflicts", "Detailed * * Thread Exception" and others) * * show up as blank values. * **************************************************************** * RECOMMENDATION: APPLY THIS PTF * **************************************************************** PROBLEM SUMMARY: Instrumentation for IFCID 197 and 225 as well as a recent IFCID 1 extension (CPU metrics) is not supported via Tivoli Enterprise Portal workspaces. I1: The checking of the minimum value for the LROWS parameter is incorrect. I2: RC=12 is returned when allocating the runtime datasets. I3: Near-Term History or Object Analysis are started for DB2 subsystems although the user specified not to monitor the respective DB2 subsystem. I4: Starting the Event Collection Manager (Object Analysis) in seperate started task is an option that is not applicable any more and has to be removed from the ICAT configuration. P1: UNICODE attributes in different TEP workspaces ("Thread Activity", "Locking Conflicts", "Detailed Thread Exception" and others) show up as blank values. PROBLEM CONCLUSION: By applying the subject PTF and the corresponding TEP fixpack, customers will now see IFCID 197 and IFCID 225 instrumentation information in two new workspaces called "DB2 Messages" (IFCID 197) and "Storage Consumption" (IFCID 225). Furthermore the "System Status" workspace has been enhanced to show the values being introduced by an IFCID 1 extension (CPU metrics). I1: On the panel the user can only enter values in the range of 99-9999 for the LROWS parameter from now on. I2: Only the datsets that were specified during configuration are allocated. I3: The startup member was changed to only start functions for DB2 subsystems that the user wants to monitor. Important NOTE: --------------- This change ("I3") also affects the Classic Interface. The startup members are now only generated for the DB2 subsystems that you select for monitoring. On panel KD261PO 'Classic Interface Information' you can specify the default DB2 subsystem ID for the Classic Interface by using the parameter 'Default DB2 ID for real-time VTAM mode'. In this panel you have to specify a DB2 subsystem ID that is configured in this RTE and that you later select as a DB2 subsystem to monitor. If you specify a default DB2 subsystem that is either not configured in this RTE or that you later decide not to monitor then OBVTAM is not initialized and when you try to log on to Classic Interface the following message is displayed: VAMP152 CLSDST/PASS TO <your applid> FAILED, RTNCD=1000, SENSE=0857 To check if the Classic Interface is ready to be used verify that the following message is written to the server log: OMV002I APPL <your applid for Classic logon> OPENED SUCCESSFULLY I4: The configuration panel is adjusted to not let the user specify a started task name for the Event Collection Monitor and the helps were adjusted accordingly. P1: The Code was adjusted to treat UNICODE attributes properly.
Problem conclusion
Temporary fix
Comments
By applying the subject PTF and the corresponding TEP fixpack, customers will now see IFCID 197 and IFCID 225 instrumentation information in two new workspaces called "DB2 Messages" (IFCID 197) and "Storage Consumption" (IFCID 225). Furthermore the "System Status" workspace has been enhanced to show the values being introduced by an IFCID 1 extension (CPU metrics). I1: On the panel the user can only enter values in the range of 99-9999 for the LROWS parameter from now on. I2: Only the datsets that were specified during configuration are allocated. I3: The startup member was changed to only start functions for DB2 subsystems that the user wants to monitor. Important NOTE: This change ("I3") also affects the Classic Interface. The startup members are now only generated for the DB2 subsystems that you select for monitoring. On panel KD261PO 'Classic Interface Information' you can specify the default DB2 subsystem ID for the Classic Interface by using the parameter 'Default DB2 ID for real-time VTAM mode'. In this panel you have to specify a DB2 subsystem ID that is configured in this RTE and that you later select as a DB2 subsystem to monitor. If you specify a default DB2 subsystem that is either not configured in this RTE or that you later decide not to monitor then OBVTAM is not initialized and when you try to log on to Classic Interface the following message is displayed: VAMP152 CLSDST/PASS TO <your applid> FAILED, RTNCD=1000, SENSE=0857 I4: The configuration panel is adjusted to not let the user specify a started task name for the Event Collection Monitor and the helps were adjusted accordingly. P1: The Code was adjusted to treat UNICODE attributes properly. KEYWORDS : TEP IFCID1 IFCI197 IFCID225 INSTRUMENTATION LROWS MINIMUM ALLOCATION RUNTIME DATASETS RC12 OA NTH STARTUP ECM STARTED TASK VAMP152 OMV002I
APAR Information
APAR number
PK59975
Reported component name
OM XE DB2PE/PM
Reported component ID
5655OPE00
Reported release
410
Status
CLOSED UR1
PE
NoPE
HIPER
NoHIPER
Special Attention
YesSpecatt / New Function / Xsystem
Submitted date
2008-01-29
Closed date
2008-01-30
Last modified date
2017-02-04
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK33296
Modules/Macros
KD5AGENT KD5ATC00 KO2$CIOB KO2$DMRB KO2$FIOB KO2$LOCB KO2$MSJB KO2$QIOB KO2$SFXB KO2$TDBB KO2ACAFA KO2ACAFS KO2ACAF2 KO2ACAPA KO2ACAPS KO2ACAP2 KO2ACONB KO2AGNTB KO2AINIB KO2AOMBB KO2APCAA KO2APCAS KO2APCA2 KO2APCBA KO2APCBS KO2APCB2 KO2APCCA KO2APCCS KO2APCC2 KO2APCSB KO2APC1A KO2APC1S KO2APC12 KO2APC2A KO2APC2S KO2APC22 KO2APC3A KO2APC3S KO2APC32 KO2APC4A KO2APC4S KO2APC42 KO2APC5A KO2APC5S KO2APC52 KO2APC6A KO2APC6S KO2APC62 KO2APC7A KO2APC7S KO2APC72 KO2APC8A KO2APC8S KO2APC82 KO2APC9A KO2APC9S KO2APC92 KO2APINA KO2APINS KO2APIN2 KO2ARECB KO2ARSBA KO2ARSBS KO2ARSB2 KO2ASPFB KO2ASUBA KO2ASUBS KO2ASUB2 KO2ATRCB KO2ATREB KO2ATRPB KO2ATRTB KO2AUSRB KO2CBUFB KO2CCAFA KO2CCAFS KO2CCAF2 KO2CCINB KO2CCISA KO2CCISS KO2CCIS2 KO2CCNSA KO2CCNSS KO2CCNS2 KO2CCPUB KO2CDCIB KO2CDCMA KO2CDCMS KO2CDCM2 KO2CDCNB KO2CDFCA KO2CDFCS KO2CDFC2 KO2CDFSA KO2CDFSS KO2CDFS2 KO2CDINA KO2CDINS KO2CDIN2 KO2CDSCB KO2CDSYA KO2CDSYS KO2CDSY2 KO2CIFIA KO2CIFIS KO2CIFI2 KO2CIMSA KO2CIMSE KO2CIMSF KO2CIMSG KO2CISBA KO2CISBS KO2CISB2 KO2CLKDA KO2CLKDS KO2CLKD2 KO2CLKRC KO2CLKRD KO2CLKRE KO2CLOGB KO2CMVIC KO2CMVIF KO2CMVSC KO2CMVSF KO2CNADB KO2CNAGB KO2CNAPB KO2CNASB KO2CNSRB KO2CNTPA KO2CNTPS KO2CNTP2 KO2CRLIC KO2CRLID KO2CRLIE KO2CRLSC KO2CRLSD KO2CRLSE KO2CSTPA KO2CSTPS KO2CSTP2 KO2CSTSB KO2CST1A KO2CST1S KO2CST12 KO2CST2A KO2CST2S KO2CST22 KO2CST3A KO2CST3S KO2CST32 KO2CST4A KO2CST4S KO2CST42 KO2CSYSA KO2CSYSS KO2CSYS2 KO2CTEXB KO2CTHAA KO2CTHAS KO2CTHA2 KO2CTHBA KO2CTHBS KO2CTHB2 KO2CTHCA KO2CTHCS KO2CTHC2 KO2CTHIA KO2CTHIS KO2CTHI2 KO2CTHSA KO2CTHSS KO2CTHS2 KO2CTH1A KO2CTH1S KO2CTH12 KO2CTH2A KO2CTH2S KO2CTH22 KO2CTH3A KO2CTH3S KO2CTH32 KO2CTH5A KO2CTH5S KO2CTH52 KO2CTH6A KO2CTH6S KO2CTH62 KO2CTH7A KO2CTH7S KO2CTH72 KO2CTH8A KO2CTH8S KO2CTH82 KO2CTH9A KO2CTH9S KO2CTH92 KO2CT2IA KO2CT2IS KO2CT2I2 KO2CT2SA KO2CT2SS KO2CT2S2 KO2CVTIC KO2CVTIF KO2CVTIG KO2CVTSC KO2CVTSF KO2CVTSG KO2CZPMB KO2DATA KO2DAUDA KO2DAUDS KO2DAUD2 KO2DBCIB KO2DCINB KO2DCS1B KO2DCS2B KO2DDINB KO2DDSBA KO2DDSBS KO2DDSB2 KO2DINTB KO2DMSCA KO2DMSCS KO2DMSC2 KO2DNTHA KO2DNTHS KO2DNTH2 KO2DTHDA KO2DTHDS KO2DTHD2 KO2DXACB KO2DXSTB KO2DXS1A KO2DXS1S KO2DXS12 KO2DXS2A KO2DXS2S KO2DXS22 KO2DXS3A KO2DXS3S KO2DXS32 KO2EAPIC KO2EAPIF KO2ECTLC KO2ECTLF KO2EC01C KO2EC01F KO2ED01A KO2ED01T KO2ED01W KO2ED013 KO2EGX1A KO2EGX1T KO2EGX1W KO2EGX13 KO2EINTB KO2EIXMC KO2EIXMF KO2EIX1A KO2EIX1T KO2EIX1W KO2EIX13 KO2ELDBB KO2EOJAB KO2EOJSA KO2EOJSS KO2EOJS2 KO2ETDBB KO2ET01C KO2ET01F KO2EUSRB KO2EVLAB KO2EVLSA KO2EVLST KO2EVLSW KO2EVLS3 KO2GHT KO2HARCB KO2HCAFB KO2HDTIB KO2HDTPB KO2HINTB KO2HMSGB KO2HPRCB KO2HPR1B KO2HPR2B KO2HSQIB KO2HSQPB KO2HSVIB KO2HSVPB KO2HTRMB KO2HVINB KO2HWLMB KO2ICAFA KO2ICAFS KO2ICAF2 KO2ICBCA KO2ICBCS KO2ICBC2 KO2ICOLA KO2ICOLS KO2ICOL2 KO2IFCTA KO2IFCTS KO2IFCT2 KO2IINIA KO2IINIS KO2IINI2 KO2IINTB KO2ISUBA KO2ISUBS KO2ISUB2 KO2ITABA KO2ITABS KO2ITAB2 KO2ITCAA KO2ITCAS KO2ITCA2 KO2LCAPB KO2MI00B KO2NCSTB KO2NDRVB KO2NUSRB KO2NXCPB KO2OBPSB KO2OBUFB KO2OCINB KO2OCMAB KO2OCMCB KO2OCMDB KO2OCONB KO2OCUAB KO2ODBGB KO2ODCNB KO2ODFEB KO2ODINB KO2ODSTB KO2OEDSB KO2OENDB KO2OEVCB KO2OEXPB KO2OFUDB KO2OHILB KO2OH2IB KO2OINTB KO2OJACB KO2OJALB KO2OJCNB KO2OJOPB KO2OJTHB KO2OJVLB KO2OLOGB KO2OLOKB KO2OMAJB KO2OMA2B KO2OMEMB KO2OMGCB KO2OMGEB KO2OMGXB KO2OMODB KO2OMSGB KO2ONAFB KO2ONAGB KO2ONAPB KO2ONASB KO2ONTAB KO2ONTSB KO2OOPTB KO2OPCKB KO2OPCNB KO2OPTFB KO2ORCTB KO2ORCVB KO2ORLGB KO2ORLMB KO2OSBSB KO2OSNEC KO2OSNEF KO2OSNPB KO2OSORB KO2OSPCB KO2OSQPB KO2OSTDB KO2OSTPB KO2OSTSB KO2OSUBB KO2OSYXB KO2OTCCB KO2OTCIA KO2OTCIS KO2OTCI2 KO2OTEXB KO2OTHAB KO2OTHBB KO2OTHCB KO2OTHDB KO2OTHEB KO2OTHFB KO2OTHGB KO2OTHHB KO2OTHIB KO2OTHLB KO2OTHXB KO2OTH1B KO2OTH2B KO2OTH3B KO2OTH4B KO2OTH5B KO2OTH6B KO2OTH7B KO2OTH8B KO2OTH9B KO2OTRAB KO2OTRCB KO2OUPFB KO2OUSRB KO2OUTLB KO2OVERC KO2OVERF KO2OXCIB KO2OXCMB KO2OXDVB KO2OXIMB KO2OXMGB KO2OXSYB KO2OXTDB KO2OXTHB KO2OXTRB KO2OXTSB KO2OZM2B KO2OZOMB KO2OZPMB KO2O225B KO2PAPCB KO2PARSB KO2PCSVC KO2PCSVF KO2PCTCC KO2PCTCF KO2PCTIC KO2PCTIF KO2PCTLC KO2PCTLF KO2PCTOC KO2PCTOF KO2PCVTC KO2PCVTF KO2PDRVC KO2PDRVF KO2PLIOC KO2PLIOF KO2PMEMC KO2PMEMF KO2PMGRB KO2PMSGC KO2PMSGF KO2PRDRC KO2PRDRF KO2PRECC KO2PRECF KO2PSRVC KO2PSRVF KO2PTKNB KO2PUSIC KO2PUSIF KO2PUSRB KO2PUTLC KO2PUTLF KO2PWHCB KO2PWTRC KO2PWTRF KO2RSUBB KO2SABP KO2SABS KO2SACS KO2SADD KO2SADS KO2SAGB KO2SAGS KO2SAPK KO2SAPS KO2SAU1 KO2SAU2 KO2SAU3 KO2SAU4 KO2SAU6 KO2SAU7 KO2SAU8 KO2SSBP KO2SSDD KO2SSGB KO2SSUB KO2SZPM KO2TIOSB KO2TSB1B KO2TSB2B KO2TSB3B KO2TSB4B KO2VDINB KO2VIOSB KO2WGETB KO2WINTB KO2WNCYB KO2WTCAA KO2WTCAS KO2WTCA2 KO2WTHTB KO2WXCPB KO2XBPSA KO2XBPSS KO2XBPS2 KO2XCINB KO2XCISA KO2XCISS KO2XCIS2 KO2XDBSA KO2XDBSS KO2XDBS2 KO2XDDSB KO2XDFSA KO2XDFSS KO2XDFS2 KO2XDINA KO2XDINS KO2XDIN2 KO2XIMSA KO2XIMSE KO2XIMSF KO2XIMSG KO2XLKDA KO2XLKDS KO2XLKD2 KO2XLKRC KO2XLKRD KO2XLKRE KO2XMVIC KO2XMVIF KO2XMVSC KO2XMVSF KO2XRCIS KO2XRCI2 KO2XRCTT KO2XRCTU KO2XRCTV KO2XRCTW KO2XRCT3 KO2XRLIC KO2XRLID KO2XRLIE KO2XRLSC KO2XRLSD KO2XRLSE KO2XSTPA KO2XSTPS KO2XSTP2 KO2XSYSA KO2XSYSS KO2XSYS2 KO2XSY2A KO2XSY2S KO2XSY22 KO2XTEXB KO2XTHSA KO2XTHSS KO2XTHS2 KO2XVTIF KO2XVTIG KO2XVTSF KO2XVTSG
Fix information
Fixed component name
OM XE DB2PE/PM
Fixed component ID
5655OPE00
Applicable component levels
R410 PSY UK33296
UP08/02/05 P F802
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":"410","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":"410","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
04 February 2017