A fix is available
APAR status
Closed as program error.
Error description
From the OMEGDB2 Collector job log: 2011/03/12 23:46:04 FPEV0224I MSTR INSTANCE FOR DB2 SUBSYSTEM DB5T STOPPED 2011/03/12 23:46:09 KO2O1324E NEAR-TERM HISTORY DATA COLLECTOR - DISCONNECT FROM DB2 FAILED. RETURN CODE 00000004 (CHECKRC 2011/03/12 23:46:09 KO2O1325E NEAR-TERM HISTORY DATA COLLECTOR - DISCONNECT FROM DB2 FAILED. REASON CODE 00C12824 (CHECKRC ) 2011/03/12 23:46:41 IEA794I SVC DUMP HAS CAPTURED: 009 009 DUMPID=001 REQUESTED BY JOB (OMEGDB2 ) 009 DUMP TITLE=OMEGAMON II FOR DB2: COMPID=5655OPE00, JOB=OMEGDB2 , 009 LMOD=KOBAS510#L, CSECT=UNKNOWN , OFFSET=05F976 2011/03/12 23:46:54 KO2S0500E OSNP SDUMPx Failure. RC: 00000B08 2011/03/12 23:46:54 KO2S0508E OSNP LMOD: KOBAS510, CSECT: UNKNOWN , OFFSET: 05F976 From the dump: a U980 abend was issued: PSW: 077D1000 920663EE Instruction length: 02 Interrupt code: 000D Failing instruction text: 00181610 0A0DD247 2000D000 Breaking event address: 00000000_00000000 AR/GR 0-1 00000000/00000000_80000000 00000000/00000000_800003D4 AR/GR 2-3 00000000/00000000_126A97C0 00000000/00000000_128720B0 AR/GR 4-5 00000000/00000000_126BC14C 00000000/00000000_126A9488 AR/GR 6-7 00000000/00000000_00000005 00000000/00000000_126BB968 AR/GR 8-9 00000000/00000000_126CE278 00000000/00000000_12872000 AR/GR 10-11 00000000/00000000_11E858FC 00000000/00000000_126BB968 AR/GR 12-13 00000000/00000000_126B37C0 00000000/00000000_0013AC00 AR/GR 14-15 00000000/126A0018_91E8590E 00000000/00000000_920663BA The U980 was issued at offset X'5EC' in OMSUB3 (V620COM 06/03/10 14:37 UA54637) From a VERBX LOGDATA: TCA: 120E5C30 RECDEBUG: 1266B6A8 Using the TCA, found 4 RECDEBUG entries the same as: *RECDEBUG entry 1 at Address 1266B4A8 +0000 PSW: PSW...... 077D0000 90469252 REGISTERS AT TIME OF ERROR: +0008 R0 - R4 : 104694D2 10469550 120E86F8 0DB33000 +0018 R4 - R7 : 00000000 E2C1E2E2 120E8F20 0DB33000 +0028 R8 - R11: 120E8750 120E8F20 90468FF8 0F434094 +0038 R12- R15: 126BD718 120E86F8 90469238 120E61D8 +0048 CR03..... 01400074 CR04..... 00010074 ABCC..... 000A0000 CMD...... EXSY ENT...... ........ ENTA..... 00000000 +0064 CALR..... ........ TYPE..... E2D7C9F1 ACT...... FF ALOW..... FF INTR..... FF SYS...... FF +0074 CRC...... 00000000 ATIM..... 00829DA3 0111071F RECDEBUG entry 5 is the U980. From a SYSTRACE: PGM 011 077D0000 90469252 00040011 00000000 00000000 00000000 0074 0074 23:46:40.360146 0DB33000 00000000 This S0C4 (from the SYSTRACE and RECDEBUG) happened in KO2CCNS at offset X'2B2' ( O2CCNS V420510 05/12/10 13:54.PM05666 DB2810 ) The instruction that fails is: 5830 3050 L @W3,SCOMASCE(,@W3) ASCE CHAIN ANCHOR ADDR R3 is 0DB33000, and from the dump: 0DB33000.:0DB3AFFF. LENGTH(X'8000')--Storage not available Looks like macro RECOVERY ON,LABEL=ALCNRECV started it all. Part of this macro does a lookup for TCA Entry SCOM - The entry in the $TCA is: 087 SCOM 0DB33000 00000000 0DB33000 is a bad address. Omegamon base Level 3 identified that the XODV code is in some sort of a loop. The $STACK area in the dump shows repetitive entries for XDRV and XDB1. That area is pointed to by W#STAKCP (x'314) in $OMWORK. In this case, $OMWORK is at x'13AC00'. . additional symptoms: Dump Title: OMEGAMON II FOR DB2: COMPID=5655OPE00, JOB=OMXD2DX, LMOD=KOBAS510#L, CSECT=UNKNOWN, OFFSET=00162E RECDEBUG shows U980 abend is in OMSUB3. . Dump Title: OMEGAMON II FOR DB2: COMPID=5655OPE00, JOB=CANSO2 , LMOD=KOBAS510#L, CSECT=UNKNOWN , OFFSET=027E44 Load module name: KOBAS510 Csect name: #UNKNOWN User Abend code: 0920 ABENDU920 U920 .
Local fix
no workaround
Problem summary
**************************************************************** * USERS AFFECTED: OMEGAMON XE for DB2 PE/DB2PM * * users of component: * * - Classic Interface * * - CUA Interface * **************************************************************** * PROBLEM DESCRIPTION: ABENDU980 IN LMOD KOBAS510 CSECT * * UNKNOWN * * * **************************************************************** * RECOMMENDATION: Apply this PTF * * * **************************************************************** PROBLEM SUMMARY: DB2 subsystem "not active" condition causes to abend during exception process. PROBLEM CONCLUSION: Change logic to properly handle exception process when DB2 subsystem is terminating.
Problem conclusion
Change logic to properly handle exception process when DB2 subsystem is terminating. KEYWORDS : ABENDU980 IN LMOD KOBAS510
Temporary fix
Comments
APAR Information
APAR number
PM51940
Reported component name
OM XE DB2PE/PM
Reported component ID
5655OPE00
Reported release
410
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-11-10
Closed date
2012-03-02
Last modified date
2012-04-03
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK76746
Modules/Macros
KO2OXCMB
Fix information
Fixed component name
OM XE DB2PE/PM
Fixed component ID
5655OPE00
Applicable component levels
R410 PSY UK76746
UP12/03/03 P F203
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:
03 April 2012