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
PK57640
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
2007-12-05
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:
Modules/Macros
BPOMAWRT BPOMAXA0 BPOMAX00 BPOQAPVA BPOQASCD BPOQCREC BPOQINEX BPOQRHST BPOQRIOA BPOQRPLN BPOQRULN BPOQSRGB BPOQTPFC DGO@BTCH DGO@CHKB DGO@CONV DGO@CRDP DGO@DB DGO@DB2I DGO@DB2S DGO@DTA1 DGO@DTA3 DGO@DTA5 DGO@DTA6 DGO@DTA7 DGO@LLOG DGO@LOAD DGO@MIG1 DGO@MIG2 DGO@MT1 DGO@MT2 DGO@MT3 DGO@MT4 DGO@MT5 DGO@PC1 DGO@PC2 DGO@PC3 DGO@PC4 DGO@PRV1 DGO@PRV2 DGO@SCRD DGO@SDOB DGO@SIDS DGO@SP DGO@SQPA DGO@TBL DGO@VW1 DGO@VW2 DGO@WRPA DGO@WRP2 DGO@WR2C DGO@WSTE DGOABORD DGOABORE DGOACALC DGOACMER DGOACOMP DGOACREC DGOADIST DGOAEXIT DGOAEX20 DGOAFDDF DGOAFRCD DGOAIREC DGOAMTRC DGOAREDB DGOAREDC DGOAREDD DGOAREDG DGOAREDM DGOAREDP DGOAREDR DGOAREDX DGOATRAC DGOATREC DGOAZMER DGOAZREC DGOBGENL DGOFECAL DGOFECA2 DGOFEDAT DGOFEDPM DGOFPDAT DGOFPDPM DGOFPE15 DGOFPRF0 DGOFPRIC DGOFSIST DGOFS254 DGOFUCAL DGOFUCA1 DGOFUFAC DGOFUFDI DGOIPAIR DGOLADLK DGOLAREQ DGOLARES DGOLASUM DGOLASUS DGOLATIM DGOLCREC DGOLFILE DGOLIREC DGOLREDC DGOLTRAC DGOLXRES DGOMAXA0 DGOMDX00 DGOMERPL DGOMEXA0 DGOMEXA2 DGOMEXST DGOMLAFD DGOMLEXD DGOMSBCF DGOMSIST DGOMTADJ DGOMTDDF DGOMTFLR DGOMTLCK DGOMTLST DGOMTPKG DGOMTPOP DGOMTREF DGOMUPXT DGOMZF00 DGOMZF03 DGONFLST DGONFWHD DGONFWPA DGONFWP9 DGONF140 DGONF150 DGONF160 DGONF170 DGONF180 DGONF190 DGONF191 DGONF200 DGONF210 DGONF220 DGONF230 DGONF240 DGONF250 DGONF260 DGONF270 DGONF280 DGONF310 DGONF320 DGONF330 DGONF340 DGONF350 DGONIREC DGONTRAC DGOPMHDR DGORAEXT DGORASCN DGORCREC DGORCREP DGORCRE2 DGORDIST DGORINEX DGORIREC DGORIREP DGORPACC DGORPCAP DGORPEXI DGORPHIL DGORPHVA DGORPIOA DGORPMIN DGORPPAG DGORPPAR DGORPRID DGORPSCA DGORPSOR DGORPSUM DGORPSUS DGORPUDF DGORRCAP DGORRCOM DGORRDAT DGORRDDF DGORREXI DGORRHIL DGORRHVA DGORRIOA DGORRLOC DGORRMIS DGORRSOR DGORRSQL DGORRTHR DGORSRBY DGORUACC DGORUSUM DGORUWRK DGORZREP DGOSAPAW DGOSBLKX DGOSBORD DGOSBORE DGOSCREC DGOSFMTQ DGOSFMTR DGOSGENC DGOSGENS DGOSI199 DGOSI202 DGOSI225 DGOSTRAC DGOTAEXT DGOTAPVA DGOTARAD DGOTBWKL DGOTCREC DGOTCREP DGOTINEX DGOTIREC DGOTIREP DGOVABAN DGOVABND DGOVAEST DGOVALII DGOVBMG DGOVCCP DGOVCINI DGOVCRDB DGOVDB2C DGOVDB2E DGOVDB2F DGOVDB2I DGOVDB2M DGOVDB2S DGOVDMSG DGOVDS DGOVDSIN DGOVDSRC DGOVDSS DGOVEEDI DGOVEEDR DGOVEEDS DGOVEEDT DGOVEE00 DGOVEE01 DGOVEPAI DGOVGIFC DGOVHMCD DGOVHMDR DGOVHMM0 DGOVHMM1 DGOVHMM2 DGOVHMM3 DGOVHMSD DGOVHMS1 DGOVHMTC DGOVHMTM DGOVHMTX DGOVHM00 DGOVISI DGOVISIT DGOVMB DGOVMDI DGOVMDSP DGOVMIDI DGOVMMXM DGOVMRAP DGOVMRAS DGOVMSTR DGOVMTEX DGOVMTMR DGOVMUAE DGOVM000 DGOVM001 DGOVM002 DGOVPCON DGOVPDSC DGOVPIG0 DGOVPIG1 DGOVPMOV DGOVPOPT DGOVPP1 DGOVPP2 DGOVPP3 DGOVPP4 DGOVPUPD DGOVQUEU DGOVRGM1 DGOVRG00 DGOVRG01 DGOVRG02 DGOVRG03 DGOVRG04 DGOVRG10 DGOVRG11 DGOVRG12 DGOVRG13 DGOVRG20 DGOVRG21 DGOVRG22 DGOVRG23 DGOVRG24 DGOVRG25 DGOVRG26 DGOVRG27 DGOVRG28 DGOVRG4B DGOVRG4C DGOVRG4X DGOVRPRM DGOVSADJ DGOVSADK DGOVSAGG DGOVSCLO DGOVSCLR DGOVSCNI DGOVSCNT DGOVSCON DGOVSCO1 DGOVSCPI DGOVSCS1 DGOVSCS2 DGOVSCS3 DGOVSCTH DGOVSCT1 DGOVSCT2 DGOVSDDF DGOVSDOB DGOVSDOC DGOVSDPM DGOVSDSC DGOVSDTS DGOVSDTT DGOVSERI DGOVSERV DGOVSFKE DGOVSFLR DGOVSGET DGOVSGFT DGOVSGSA DGOVSLOC DGOVSORT DGOVSOUT DGOVSQRY DGOVSQSM DGOVSQTR DGOVSRQE DGOVSSEN DGOVSSP1 DGOVSSP2 DGOVSTAG DGOVSTDS DGOVSTQL DGOVSUBS DGOVSUTL DGOVS100 DGOVS140 DGOVS150 DGOVS700 DGOVTAC DGOVTBI DGOVTCL DGOVTCPD DGOVTCPL DGOVTCPS DGOVTCPT DGOVTDI0 DGOVTGC DGOVTGS DGOVTIA DGOVTLI DGOVTSCL DGOVTSD DGOVTSEX DGOVTSIA DGOVTSO DGOVTSOI DGOVTSSD DGOVTSSO DGOVTSTA DGOVTSTS DGOVTSX DGOVTTA DGOVTWR DGOVUAS0 DGOVUELD DGOVUFTL DGOVUINI DGOVUM00 DGOVUM01 DGOVUM02 DGOVUSS0 DGOVWDOG DGOVWLII DGOVWMLH DGOVWRPA DGOVWRP2 DGOVWR2C DGOVXMSG DGOVZAP DGOVZMAI DGOVZRAC DGOVZTCC DGOVZTRC DGOWFILE DGOWF106 DGOWF107 DGOWF201 DGOWF256 DGOW1FIL DGOXD000 DGOXFSQL DGOXF000 DGOXF001 DGOXF002 DGOXF003 DGOXF004 DGOXF005 DGOXF006 DGOXF008 DGOXR000 DGOXS001 DGOXS002 DGOXS003 DGOXS004 DGOXS005 DGOXS006 DGOXT000 DGOXT001 DGOXT002 DGOXT003 DGOXT004 DGOXT005 DGOXT006 DGOZBIND DGOZBTCH DGOZBTC2 DGOZCAF DGOZCHDR DGOZCHKB DGOZCMD DGOZCONV DGOZCOPY DGOZCRD DGOZCRDC DGOZCRDP DGOZCRDW DGOZDB DGOZDMDB DGOZDTA1 DGOZDTA3 DGOZDTA5 DGOZDTA6 DGOZDTA7 DGOZECB DGOZFL1 DGOZFL2 DGOZFL3 DGOZJEND DGOZLLOG DGOZLOAD DGOZMB DGOZMIG1 DGOZMIG2 DGOZMT1 DGOZMT2 DGOZMT3 DGOZMT4 DGOZMT5 DGOZPC1 DGOZPC2 DGOZPC3 DGOZPC4 DGOZPMS DGOZPRSE DGOZPRV1 DGOZPRV2 DGOZRSDS DGOZSCRD DGOZSIDS DGOZSP DGOZSQPA DGOZSUB1 DGOZSUB2 DGOZTBL DGOZVW1 DGOZVW2 DGOZWDIV DGOZWFE DGOZWIE DGOZWJE DGOZWSE DGOZWSTE FPECHASY FPECHATS FPECHE15 FPECHFLT FPECHGVR FPECHTRN FPECMAIN FPECMDAT FPECRDMP FPECVGLC FPECVGOL FPECVGSL FPECVICM FPECVPAC FPECVRMC FPEFMAIN FPEMDSUB FPEMGGST FPEMMAIN FPEUCBPR FPEUCHEC FPEUCHE2 FPEUCHK FPEUCHK2 FPEUCXPX FPEUCXSX FPEUFFER FPEUFFE2 FPEUFIOI FPEUFIO2 FPEUFOCR FPEUFOC2 FPEUFTDP FPEUFTDS FPEUFTP2 FPEUFTS2 FPEUFUIS FPEUFUIT FPEUFUNI FPEUFUN2 FPEUFWMG FPEUFWMX FPEUFYDY FPEUFYD2 FPEUFYLD FPEUFYST FPEUFYS2 FPEUHDRS FPEUIFCI FPEUIFC2 FPEUMSGS FPEUNIDT HKDB410J KDBZC03 KDB410J KD2BHELP KD2DDICT KD2SBATO KD261CB1 KD261CB2 KD261CCU KD261COS KD261CVA KD261CVU KD261DC1 KD261DC2 KD261DFI KD261HM KD261HU KD261HUA KD261HUB KD261HUC KD261HUD KD261HY KD261HYA KD261HYB KD261H7 KD261H7A KD261H8 KD261MV1 KD261PM KD261PO KD261PV1 KD261PV2 KD261SAG KD261SAT KD261SA1 KD261SA2 KD261SB1 KD261SB2 KD261SB3 KD261SDB KD261SEX KD261SJ4 KD261SJ5 KD261SN1 KD261SN2 KD261SO1 KD261SO2 KD261SO3 KD261SO4 KD261SPA KD261SPW KD261SSH KD261SS1 KD261SS3 KD261SS4 KD261SS5 KD261SU1 KD261SW1 KD261SW2 KD2610PC KD2610R1 KD5ATR KD5BHELP KD5CAT KD5DDICT KD5DOC KD5PDICT KD5SBATO KD5VOM KD541CCU KD541HA KD541HAA KD541HU KD541HUA KD541HUB KD541HUC KD541HUD KD541H4 KD541H4A KD541MV1 KD541P4 KD5410PC KD5410PP KD5410RN KD5410SP KO2SABP KO2SABS KO2SACS KO2SADD KO2SADS KO2SAGB KO2SAGS KO2SAPK KO2SAPS KO2SAU1 KO2SAU2 KO2SAU3 KO2SAU4 KO2SAU6 KO2SAU7 KO2SAU8 KO2SSBP KO2SSDD KO2SSGB KO2SSUB KO2SZPM
| GC18998001 |
Fix information
Fixed component name
OM XE DB2PE/PM
Fixed component ID
5655OPE00
Applicable component levels
R410 PSY UK33238
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