APAR status
Closed as canceled.
Error description
OEM vendor products that have caused problems in DB2 or IRLM =================KF 04/21/05==================================== ABEND0C4 RC00000004 DSNXERT 00B0 007A from DB2 V8 Related to trigger wild branch from CA ITH$ENTY to DSNXERT Apply CA PTF UDTE149 ================LCK ============================================ Any batch job or TSO user that issues a DISplay command for databases or utilites is hung. SYSLOG shows timeouts with CORRELATION-ID=021.EUSDTU09 DSNT376I -D2D6 PLAN=DSNUTIL WITH CORRELATION-ID=ZCAACL12 CONNECTION-ID=UTILITY LUW-ID=B1001.CODB2T6.BCD8C8968C26=22715 THREAD-INFO=CAA&:*:*:* IS TIMED OUT. ONE HOLDER OF THE RESOURCE IS PLAN= WITH CORRELATION-ID=021.EUSDTU09 CONNECTION-ID=D2D6 LUW-ID=B1001.CODB2T6.BCD8E81452F2 THREAD-INFO=SYSOPR:*:*:* ON MEMBER D2D6 dump shows task for CORRELATION-ID=021.EUSDTU09 is processing in CASR230K CA code. This task was in the process of switching execution units to do the DISPLAY command. The fix is TE49574 from CA The fix is for a CAS90 component and does not require a cycle of DB2 in order to implement. Additional symptoms is hang with Autbnd06& 020.DBCMD =========== lsk 3/28/05 ============== Slow hang poor performance of DSNTIAUL when using SPIFFY (non IBM TSO/ISPF adendum product ) Batch job . Running DSNTIAUL under IBM's TSO batch program runs normally. ======================= lsk 3/03/05 ========================== Symptoms: abend0c4 in dsnvdlc dsnvialc or ABEND0C4 pic10 module unknown also ABENd0C1 00000001 DSNSCON +028E Problem caused by having module DSNXGRDS in SDSNEXIT due to a third party software . Deleting module from SDSNEXIT corrected the problem. ============lsk 2/22/05 =============================== ABEND04E 00C90101 C=810 r810 DSNIPPHO:2003 rc00c90101 DSNIPPHO 2003 erqual2003 DSNI014I -DST2 DSNIPPHO DATA IN USE DURING ABEND REASON 00C90101 ERQUAL 2003 TYPE 00000302 ( also could see TYPE 00000303 ) NAME PSMADMO .PTTBL .X'00001414' CONNECTION-ID=TSO CORRELATION-ID=C33KDV LUW-ID=MEIJER.DST2APPL.BC791E80FD88=0 You can use DSN1PRNT to format the header page x'0000'. Check to see if garbage is at x'0800' - x'0A0F'. CDB about their technical bulletin TB180 dated August 26, 2004 for CDB's solution and how to find problem and REPAIR the garbaged header page =================== rjl 02/03/05 =============================== Overlay of DB2 control block in common storage. ecsa csa erly Please contact the verdor Informatica for PowerExchange fix. =================== LSK 01/28/05 ============================ ABND=04E-00E20017 DSNSTACK+0350 with Reg8 not on double word boundary. DSNSTACK at UQ54498 and customer was doing Runstats processing. Ca module *CASR230K 10/05/04 was not following the rules for STACK storage when making calls to DSNXKAL. CA fix is TE49570. 04e s04e 00e20017 rc00e20017 DSNSTACK 0350 350 R8 =================== 12/14/04 lsk ===================== COMPON=SSI,COMPID=5752SC1B6,ISSUER=IEFJSARR,MODULE=IEFJRASP, ABEND=S0E0,REASON=0000002E,SNAME=DBXA Csect name: IEFJRASP System abend code: 00E0 reason code: 0000002E abend00e0 rsn2e rc2e abend0e0 with MQ DB2 MIM found an eyecatcher module ( MIMETFIVTPCF4.6 ) in the dumps. This module belongs to MIM, a CA product. MIM PMR #13853831 The MIM fix, TD46065, has resolved the problem. The fix addresses problems z/900 hardware and z/os 1.6 driver level 55. =================== 12/17/04 rjl =============================== We have also seen the abend0e0 rc2e for CA ENF/DB2. The fix number is TE49563. ================ 9/22/04 LSK ============================ Candle fix QD2I224 Abend04e 00E50079 rc00e50079 DSNVSR +1262 1262 or pic11 DSNVRDAG +0256 0256 256 or pic04 DSNAPRHX + AD2 Stored procedure which was looping and exceeding ASUTIME . Possible Messages: MSGO21916 ABEND0C4 THREAD ALLTHOUT DSNAPRHX *DSNV086E - DB2 ABNORMAL TERMINATION REASON=00E50054 msgdsnv086e *DXR167E PRLM001 IRLM HAS DETECTED A DELAY IN COMPLETION OF ASID00E1 PROCESS msgdxr167e DXR168I PRLM001 DELAYED PROCESSES NO LONGER DETECTED msgdxr168i The save area pointed to by reg13 in SKB, seemed to be overlaid Also abend0c6 because thread in DBM1 branched to PSA . Might abend in DSNTFRCV - recovery routine. Overlaying ACE and EB control blocks . Candle fix QD2I224 <===== for ALL OMEGAMON II FOR DB2 USERS ABEND OCCURS WHEN RETRIEVING ALL ACTIVE THREAD INFORMATION. WHEN POPULATING THE ALLTHOUT TABLE, AN END OF TABLE CONDITION WAS NOT BEING PERFORMED RESULTING IN DB2 ACE CONTROL BLOCKS BEING overlayed . ===================7/6/04 JAK ========================== ABEND0C4 LOC=DSNXGRDS. DSNXERB( UQ85919 ) +0B02 due to wild branch when called by CA module ITH$ENTY ABEND04E rc00E2000D DSNSFBK +6C2 Caller is DSNLZS00 at UQ76490 R11 has the inavlid Block which showed the storage overlay by the BMC . overlaid overlays abend0c1 s0c4 s0c1 abend0c1 Module name 'CTOX' by New Dimension Software Ltd - belonging to BMC Software. Here's a snippet: | ........CTOX... | NTROL-O, REL 6. | MENSION SOFTWAR | ...Y......}.... | .02 LICENSED | LTD. BO1234 * | ..CTOSSI - 10 | ATERIAL - NEW D | **............. | 31/02 10.40 - C BMC informed that PA11525 has been marked PE and PA12887 is the PE HIPER fix. control control-o ============================= 8/18/04 KLK ====================== abend04e rc00e2000d dsnsfbk +6B6 and other data sharing member received abend0c4 pic10 dsnvxr +1904 , then db2 crash w/ rc00e50727 00e50727 . The invalid block being freed has been overlayed by the OMIIDB2 oem Omegamon perfm monitor and the customer reported the prob to Candle and informed that they applied QD2I244 for Omegamon db2 v5.2 which appears to resolve this overlay prob. But this introduces an abend18A prob in Omegamon db2 which is being looked at for now. Customer closed this pmr for the overlay prob. ===================== 8/24/04 JAK ============================= COMPON=RACF,COMPID=5752XXH00,ISSUER=DSNX@FRR,MODULE= DSNX@XAC ABEND=S00C4 REASON=00000011 L=000051A4 Dump shows 0C4 irrrfc20+C66 because of bad R7=008CFD50 XAPLACEE = 008CFD50 DSNX210I DB2x DSNXACAE - ACCESS CONTROL 064 ... problem fixed by CA XMANAGER ( DETECTOR address space ) CA fix for this problem is embedded in UXMD050 ================== 8/30/04 MMM ============================ INCORROUT - data with NULLs rows not found Symptom: V620 FLASH - When Generating Null Values, LOADPLUS Loads Incorrect Data Fix: BMC LOADPLUS for DB2/6.2.00 Failure ID: 362692 Resolution ID: 135542 ================================================================ ============10/29/2004 KLK ===================================== Abend0c4 rc=0 seen from dsnl027i msg with no dump and no logrec info. Set a slip to capture the dump of abend0c4. PSW in the dump showed the code is in OEM product COMPUWARE XPEDITER . | .........0A.XPED | ITER/TSO07.02.00 | PRIXPDB2PCR 15.3 | 8 20030214 COPYR | IGHT (C) 2003, C | OMPUWARE CORPORA Below is the OEM Vendor fix and apply process: HOLDDATA ? CT1069457 XTB0185 IF YOUR SITE USES THE XPEDITER/TSO STORED PROCEDURE INTERCEPT FOR DB2, YOU MUST DO THE FOLLOWING AFTER APPLYING THIS PTF. After applying this PTF, execute the XPEDITER/TSO DB2 Stored Procedure Intercept Installation Utility specifying 1. "DEACTIVATE" to deactivate the Stored Procedure Intercept 2. "MAINTENANCE" to update the Stored Procedure Interface 3. "ACTIVATE" to reactivate the Stored Procedure Intercept For more information, see "DB2 Stored Procedure Intercept Installation Utility" on page 4-5 of the XPEDITER/TSO 7.2 Installation Guide.). . XTB0188 After applying this PTF, an IPL should be scheduled. This will force a new fresh copy of Xpediter control blocks, including the Xpediter trace table. The normal install of the Xpediter Stored Procedure intercept can be done after the IPL. For more information, see "Activate the XPEDITER/TSO DB2 Stored Procedure Intercept" on pages 4-4 thru 4-5 of the XPEDITER/TSO 7.2 Installation Guide.). ============================================================= ==============KLK 11/08/2004 ================================ pmr 65214,500 dsnl027i with abend052 rc00000000 Logrec showed the following sequence: abend0c4 pic10 DT$DIXRC from PTXMAN CA detector monitor code abend052 rc00001212 with the same EB (Reg6) . Abend052 is a victim of the CA abend0c4. Customer received the CA fix UDTD216 and informed a good testing result with the CA fix to stop the abend052. ================== 12/07/04 rjl ================================ CSA below the line in the db2 mstr address space with getmain from dccmgetm for sp241. Storage show the eye catchers sm1 skb dcctidcm. The product is BMC data collector. Fix number R185858 is available from BMC. =================== 12/21/04 rjl =============================== If the AX value is not 00 when an allied task connects to DB2 a AX value will be reserved and set for the allied address space. This value must not be changed while DB2 is processing on behalf of the allied task. If it is a ABEND0D7 will be issued when DB2 issues a cross memory instructions like SSAR. The SSAR was issued from DB2 csect DSNYALLI. There is a small timing window where DB2 and a non DB2 application can both issue a AX extract and get a zero value indicating a AX value is not set. Both applications will then RESERVE and SET a different AX value for the allied address space. The first application to do so will later fail due to the AX value being changed by the other application. This has been reported with the other application MQSERIES. The connection request from the allied task should be reissued. ================ 01/04/2005 KLK =============================== PMR 34647,7TD reported running DB2 utility getting SPIN LOOP in RSM IAXUA to get real storage frame. Storage getmained was in SP3 Key7 in 64 MB chulks under OEM product of SYNCSORT. SYNCSORT informed that EW5892 will reduce the amount of storage used by the DB2 sort. So, EW5892 is the fix to this SPIN LOOP / Storage prob with DB2 utility run. ===================== 2/1/05 JC ====================== PQ99095 - the symptom RC00D70020 in DSNPXTRC is seen when DB2 is running in z/OS 1.5 or above with BMC Mainview. ========================================================== ===================== 3/4/05 EK ========================== Abend04E 00C90101 RC00C90101 DSNKSALO 2003 or 2001 because the shift value in the OBD (OBDINSHF) does not match the shift value in the index header page (HPGINSHF). . This problem occurred with partitioned tablespaces which had DSSIZE 8G (see PMR 56695,211,788 and related PMRs for more details). . The problem was caused by an error in OEM Reorg utility. The vendor (Infotel) have provided fixes for InfoLoad and InfoReorg: Version 4200: PTF UT420015 Version 4100: PTF UT41009P ========================================================== ==========03/23/2005 Kai-Li Kow KLK ====================== pmr 57777,005 spin loop abend071 rc30 DT$DIXRC CA PTXMAN Detector. Customer received the following fix from CA to fix the prob, ie. UDTE140, UDTE143, UDTE146, UDTE149, UDTE151, UDTE152 =========================================================== 86088,49R,000 .. QYU DB2W,ABND=0C1-00000001,U=GNLINTW ,C=XYR00.710.RDS -SQL ,M=DSNTFRCV,PSW=070C0000808E0AEA,A=00C5 Verbx Logdata shows 2 ABEND0C1s have also taken place previously. Inspection of both of those ABEND0C1 logrec entries shows REG 14: x'10715016' pointing into Computer Associates Module after Branch and link 14,15 instruction. ncluded the eyecatcher for the module below: |DT$DIIC7V05.0010/12/0418.03 MVS4| |30DB2710(c)1993-2004 Computer As| |sociates International Inc. | it was fixed by two Detector's fixes:UDTD226 and UDTD236. ============GPUT 4/27/05 Georgann Putintsev ======= z/OS 1.4 DB2V8 - Unable to Connect to DB2 Connect due to OEM/Vendor Product. Errors include: DSNL027I -DBU1 SERVER DISTRIBUTED AGENT WITH 441 LUWID=CC410364.FA18.BCE3BB60C33E=1467 THREAD-INFO=WLK:M02HOST:WLK:* RECEIVED ABEND=0C4 FOR REASON=00000000 DSNL028I -DBU1 CC410364.FA18.BCE3BB60C33E=1467 442 ACCESSING DATA FOR LOCATION 204.65.3.100 IPADDR 204.65.3.100 . ABEND0C4 RC0000003B DSNXEPM +4D79-- 03/07/05 UK01215 . Using Visual Explain via DB2 Connect msg: [SQLSTATE=40003 - [IBM][CLI Driver][DB2] SQL30020N Execution failed because of a Distributed Protocol Error that will affect the successful execution of subsequent commands and SQL state- ments: Reason Code "1232". . Our DB2 RDS module DSNXERT should only be called by a DB2 module, normally DSNXERD. A vendor product TMON / SQL Analyzer from Allen Systems Group, Inc. intercepts DB2's RMFT (resource mgr function table). . The latest safe PTF level for SQL/Analyzer is TE02278 running with DB2 V8.1. User's can turn off SQL/Analyzer by specifying SQLC=N parameter in their TMON for DB2 startup PARMs. This is the member pointed to by the TMDBPRMS DD ...startup jcl. .. Please stay at TE02278 until SQL/Anlayzer becomes more STABLE. =------------------------------------------------------------+ ================= 05/04/2005 JC ============================ ABEND0C4 DSNPSYSP with OEM FASTVSAM. The FASTVSAM fix is EWV1442. Recyle DB2 after applying OEM fix.
Local fix
Problem summary
Problem conclusion
Temporary fix
Comments
can informational apar on OEM vendor product fixes for DB2
APAR Information
APAR number
II13897
Reported component name
PB LIB INFO ITE
Reported component ID
INFOPBLIB
Reported release
001
Status
CLOSED CAN
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2004-07-06
Closed date
2004-09-22
Last modified date
2007-12-07
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Applicable component levels
[{"Business Unit":{"code":null,"label":null},"Product":{"code":"SG19O","label":"APARs - MVS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEPEK","label":"Db2 for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
07 December 2007