A fix is available
APAR status
Closed as program error.
Error description
High CPU can be experienced in the OMPE classic task as a result of requests for lock data originated by the TEP when displaying a large number of threads Detail Thread Exception Workspace. Also possible is an ABEND0C4 or ABEND0C1 from a wild branch: KO2O0718E DBS2 EXCEPTION PROCESSING FAILED WITH UNEXPECTED PROGRAM CHECK IN LKUS (XDRVB2 ) Dump Title: OMEGAMON II FOR DB2: COMPID=5655OPE00, JOB=OMIIDB2 , LMOD=#UNKNOWN#L, CSECT=XDRVB2 , OFFSET= 02CA or an SVC DUMP with Dump Title: OMEGAMON II FOR DB2: COMPID=5655OPE00, JOB=CANSO2 , LMOD=#UNKNOWN#L, CSECT=SNP$0000, OFFSET= 0102 Symptoms can result in and ABEND0C4-04 or ABEND0C1 with a PSW address pointing to low core: 077D0000 80000002. R14 points to KO2OPCNB+5C8 (at PK49696 level), a BASSM (0CEF) instruction. The ABEND occurred when KO2OXTHB (LKUS) called KO2CTHE2 (FINDLKN) and the address of KO2CTHE2 in the $EVT was 80000000; it was used as a target branch address, leading to the program check. For searchability: KO2CTHES KO2CTHEA
Local fix
Avoid using the Detail Thread Exception workspace for display or to build situations For KO2O0718E message turn off LKUS exception
Problem summary
**************************************************************** * USERS AFFECTED: OMEGAMON XE for DB2 PE/DB2PM * * users of component: * * - Tivoli Enterprise Monitoring Agent * * - Classic Interface * * - CUA Interface * **************************************************************** * PROBLEM DESCRIPTION: Slow response on TEP workspace Detail * * Thread Exception. * * or * * message KO2O0718E PROGRAM CHECK IN LKUS * * (XDRVB2 ) in Classic session. * **************************************************************** * RECOMMENDATION: Apply this PTF * **************************************************************** PROBLEM SUMMARY: Collection routine for workspace was collecting more information than required causing slow response. LKUS Classic exception failed. PROBLEM CONCLUSION: Streamline collection for Detail Thread Exception Workspace. Fix error in LKUS exception processing. Additionaly sumptoms: Problem can also occur when using the ATF of the classical interface. bad $EVT entry: 80000000
Problem conclusion
Streamline collection for Detail Thread Exception Workspace. Fix error in LKUS exception processing. KEYWORDS : LKUS DETAIL THREAD EXCEPTION WORKSPACE
Temporary fix
********* * HIPER * *********
Comments
APAR Information
APAR number
PK82448
Reported component name
OM XE DB2PE/PM
Reported component ID
5655OPE00
Reported release
410
Status
CLOSED PER
PE
YesPE
HIPER
YesHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2009-03-12
Closed date
2009-03-26
Last modified date
2009-05-22
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK44995 PK86036
Modules/Macros
KO2APCBA KO2APCBS KO2APCB2 KO2CDINA KO2CDINS KO2CDIN2 KO2CIFIA KO2CIFIS KO2CIFI2 KO2CLKDA KO2CLKDS KO2CLKD2 KO2CTHNA KO2CTHNS KO2CTHN2
Fix information
Fixed component name
OM XE DB2PE/PM
Fixed component ID
5655OPE00
Applicable component levels
R410 PSY UK44995
UP09/04/09 P F904
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":"410"}]
Document Information
Modified date:
31 March 2021