A fix is available
APAR status
Closed as program error.
Error description
KDPGLKGN: wrong and garbage values for Resource related fields
Local fix
n/a
Problem summary
**************************************************************** * USERS AFFECTED: OMEGAMON XE for DB2 PE/DB2 PM * * users of component * * - Classic Interface * * - CUA Interface (V530 only) * * - TEP * * - Enhanced 3270 UI * * - NTH - Near Term History * **************************************************************** * PROBLEM DESCRIPTION: E3270UI panel KDPGLKGN, TEP workspace * * "Global Lock Conflicts": WRONG AND * * GARBAGE VALUES FOR RESOURCE RELATED * * FIELDS. * **************************************************************** * RECOMMENDATION: Apply the provided PTF. * **************************************************************** 1. Field "Elapsed" on E3270UI panel KDPGLKGN showed zeros and field "Lock Elapsed Time" in TEP workspace "Global Lock Conflicts" were often blank or dots while corresponding fields on KDPLKC2 panel and "Lock Conflicts" workspace showed correct values. 2. Fields "Resource Name 1", "Resource Name 2" on E3270UI panel KDPGLKGN displayed garbage, similar fields in TEP workspace "Global Lock Conflicts" could be blank or dots if one of monitored members of the same DSG had UNICODE=NO set. Corresponding fields on KDPLKC2 panel and "Lock Conflicts" workspace showed correct values. 3. Fields "Resource Name 1", "Resource Name 2","Resource Name 3", "Resource Name 4", "Resource Type 2", "Resource Type 3", "Resource Type 4" on E3270UI panel KDPGLKGN and similar fields in TEP workspace "Global Lock Conflicts" could be blank or dots if it was a local lock for DB2 subsystem which was remote to the monitored DB2 subsystem. 4. UNDT, DGTT, ACSC, CDBL lock types were not processed correctly in all interfaces. 5. N/C was displayed for SKPT lock type in Thread detail screens, in NTH, in exception processing in all interfaces while the lock data could be used for identifying the locked resource.
Problem conclusion
1. Provide similar logic for fields "Elapsed", "Lock Elapsed Time" in plex perspective as they have in local DB2 subsystem perspective. 2. Correct processing of UNICODE flag for fields "Resource Name 1", "Resource Name 2". 3. There is no way to find resource names for provided DBIDs, OBIDs for remote DB2 subsystem if OMEGAMON for DB2 task is not available from that LPAR, or XCF is not setup correctly. The logic has been changed to display decimal DBID, OBID values in such case in Classic, TEP, E3270UI. 4. Change logic to display UNDT, DGTT, ACSC, CDBL lock types correctly. 5. The SKPT locks are changed to only display the TOKEN= value which is the consistency token(CONTOKEN) column in SYSIBM.SYSPACKAGE and so it can be used for identifying the locked resource. Search Keywords: RESOURCE NAME TYPE LOCK ELAPSED TIME E3270UI KDPGLKGN TEP GLOBAL LOCK CONFLICTS UNDT DGTT ACSC CDBL SKPT
Temporary fix
Comments
APAR Information
APAR number
PI42115
Reported component name
OM XE DB2PE/PM
Reported component ID
5655OPE00
Reported release
530
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2015-06-01
Closed date
2018-04-20
Last modified date
2018-05-01
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI55349 UI55350
Modules/Macros
KO2APCFA KO2APCFK KO2APCFS KO2APCF2 KO2APCJA KO2APCJK KO2APCJS KO2APCJ2 KO2APCOA KO2APCOK KO2APCOS KO2APCO2 KO2APCPA KO2APCPK KO2APCPS KO2APCP2 KO2APCQA KO2APCQK KO2APCQS KO2APCQ2 KO2APCSB KO2APC1A KO2APC1K KO2APC1S KO2APC12 KO2APC2A KO2APC2K KO2APC2S KO2APC22 KO2APC3A KO2APC3K KO2APC3S KO2APC32 KO2APC4A KO2APC4K KO2APC4S KO2APC42 KO2APC7A KO2APC7K KO2APC7S KO2APC72 KO2APC9A KO2APC9K KO2APC9S KO2APC92 KO2CLKDA KO2CLKDK KO2CLKDS KO2CLKD2 KO2CNTPA KO2CNTPK KO2CNTPS KO2CNTP2 KO2CTHBA KO2CTHBK KO2CTHBS KO2CTHB2 KO2OCKCH KO2OCKOH KO2OCKWH KO2OLOKB KO2OTHLB KO2OXTHB KO2WAITH KO2XTHSA KO2XTHSK KO2XTHSS KO2XTHS2 KO2ZHPWA KO2ZLOCC KO2ZLOCH
Fix information
Fixed component name
OM XE DB2PE/PM
Fixed component ID
5655OPE00
Applicable component levels
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.
[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSZJXP","label":"DB2 Tools for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.3.0"}]
Document Information
Modified date:
30 March 2021