APAR status
Closed as canceled.
Error description
5740xyr00 DB2 R220 R230 R310 R410 This is to document some of reported DB2 problems fixed by OEM vendors: MULTIPLE SYMPTOMS: ABEND0C4 RC04 IN DSNVSR ABEND0C4 RC10 IN DSNVSRR ABEND0C4 RC11 IN DSNB1RRR ABEND0C4 RC11 IN IEAVEGLU ABEND0C1 RC11 IN IEAVEGLU DB2 TERMINATED WITH AN ABEND04F RC00E50702 OVERLAY WAS CAUSED BY AN OEM MONITOR - INSIGHT/DB2 BY GOAL SYSTEMS. THEIR INTERNAL FIX NUMBER IS Z23143. * TMON (LANDMARK PRODUCT). INVALID DATA PASSED TO POST. FIX NUMBER U200444. TMONCICS R1.0 at PUT931A & PUT931B is U200796. Refer to II07160 for verification steps for cross memory post problem. ------------------------------------------------------- MULTIPLE SYMPTOMS: ABEND0C4 IN IEFU84 ABEND0C4 IN IEFU85 ABEND0C1 DSNAPRHX ABEND0C4 RC11 DSNVTFRR PRECEDED BY ABEND0C4 RC11 IEFU84 (RECOVERY CSECT IEEMB830 . DUMP TITLE SHOWS ABEND0C1-00000001, COMP=XYR00.220.IFC-DSNWTRC,M=DSNAPRHX. THESE ABENDS HAVE BEEN CAUSED BY OEM PRODUCTS. TO DETERMINE THE PRODUCT CAUSING THE ABEND, LOOK AT CVT X'C4' WHICH POINTS TO THE SMCA. SMCA X'7C' POINTS TO THE OFFENDING MODULE. 0C4 IEEMB830 REPORTED BY CUSTOMER WAS FOUND TO BE CAUSED BY THRUPUT MANAGER SOFTWARE MAINTENANCE (MVS SOLUTION INC). FIXES ARE TR34005 & TR34018. OEM VENDOR/PRODUCT: COMPUTER ASSOCIATES/CAIRIM REL 1.0 " ZAP/APAR: #CO35852 WITH INTRODUCTION OF IEFU85, THE SMF RECORD EXIT FOR A CALLER IN CROSS MEMORY MODE, IN MVS/ESA 3.1.3, S0C4 PROBLEMS MAY ALSO OCCUR IN CAIRIM SMF INTERCEPT MODULE, CAIMB838. BEING THAT CAIRIM IS 'FRONT-END'/INITIALIZATION MODULE FOR MANY CA PRODUCTS IT MAY BE WORTHWHILE TO NAME A FEW HERE (THE REST CAN BE FOUND IN NOTED CA APAR): CA-11-MVS REL 2.0, CA-7-MVS REL 2.9, CA-DISPATCH-MVS REL 4.0, CA-OPERA-MVS REL 2.0 AND CA-MANAGER-MVS REL B.2 ---------------------------------------------------------------- SYMPTOMS: THE USER IS ISSUING THE FOLLOWING COMMAND: -START TRACE (MON) DEST(SMF) CLASS(1,2,3) AND RECEIVES THE FOLLOWING ERROR: ABND=B78 - 0000001C, U=USERID, COMP=XYR00.220.IFC - DSNWTRC M=DSN9SCN9, PSW 070C100 811FA096, ASID 00C0. ONLY WHEN HE FOR ONE USER THE PROBLEM OCCURED AFTER MVS/ESA 313 (WORKED IN 310) AND R14 POINTED TO MODULE EBCSMFEP 1.1 COPYRIGHT 1989 ESSENTIAL SOFTWARE INC. EBCSMFEP IS PART OF SAR EXPRESS AND USER WAS ABLE TO GET A FIXING ZAP FROM GOAL SYTEMS. EBCSMFEP WAS LOCATED IN THE CSA AND USER HAD TO IPL MVS TO GET THE FIX TO TAKE. USER MAY REFERENCE FIXES EP011006 AND EP011007 WHEN CONTACTING GOAL SYSTEMS. (GOAL SYSTEMS AND ESSENTIAL SOFTWARE ARE ONE AND THE SAME). OTHER USERS HAVE HAD SIMILAR SYMPTOMS WITH REG14 POINTING TO OEM MODULES FROM CA CANDLE (OMEGAMON) OR BEI SYSTEMS. IN ALL CASES, THE USER NEEDS TO DETERMINE WHERE REG14 IS POINTING AND CONTACT THE APPROPRIATE VENDOR FOR THAT PRODUCT. ---------------------------------------------------- REORG UTILITY ABENDS WHEN 'SORTDATA' OPTION IS USED. USER ATTEMPTS A REORG WITH THE PARM 'SORTDATA' AND RECEIVED MSGDSNU044I AND MSGDSNU016I RC00E40005. SYNCSORT appears to be complaining about the parms being passed to it. If user adds SORTDEVT and SORTNUM parms to the REORG then it runs successfully. If either parms are missing, it fails. OEM SYNCSORT FIX NUMBER : EW2464-5 ------------------------------------------------------ DB2 2.2 MVS/ESA 4.2.2 WHEN AUTOMATIC JOB RUNS TO OFF LOAD THE ARCHIVE LOG, FAILURE WILL ONLY HAPPEN IN DB2 WITH DYNAMIC ALLOCATION. THEY GET TO THE POINT WHEN NO MORE TAPE DRIVES ARE AVAILABLE AND THE ONLY MESSAGE RECEIVED IS: MSGIEF244I, UNABLE TO ALLOCATE UNIT. USER WAS EXPECTING TO SEE MSGIEF290E AND MSGIEF238D FOLLOWING THE MSGIEF244I. DB2 APPEARS TO BE LOOPING. ... IT SEEMS THAT WHEN THE USER WENT TO MVS 4.2.2, MESSAGES NOW CAN BE SENT TO THE OPERATOR'S CONSOLE WITH TWO LINES. THE OEM PRODUCT WAS LOOKING FOR ONE LINE ONLY WHEN IT INTERCEPTED THE WTO. THIS IN TURN CAUSED A LOOP PROBLEM IN DB2. ... OEM VENDOR/PRODUCT: ZAP LEVEL IS BP22519 FOR THE ACTIVITY MONITOR FROM BOOLE/BABBAGE. THE FLASH IS DOCUMENTED IN FLASH DATED OCT 8, 1991. ----------------------------------------------------------- 02/12/93 S0C1 low-core in the DBM1 address space. PSW addr=80000004 and dump title references DSNYECTE. R1 points to an RLPL, R6 contains an EB address, R14 points to IEAVEGLU. This follows the cancel of a DB2 BIND job. DB2's FRR was purged which prevented the SYNC with IRLM during the abort/deallocate of the cancelled BIND job. ABEND0C1 Computer Associates fix G015297 for CA90 ACF2 ENF created to prevent purging of DB2's FRRs. Additional keywords/symptoms: RC00E80100 ABEND04F CASR210C CASR210D RC00F30801 3/15/93 -------------------------------------------------------- Candle Corp. Omegamon fix QO2B161 corrects a problem that can cause the monitor to terminate with ABEND04E RC00D93011. Other symptoms are possible because the problem involves the oem code doing an invalid resume against an execution unit that DB2 had suspended and the exact results of this unexpected resume are not predictable. * Additional keywords: Plan H2250PLN / Module O2HWLM / DSNRUC01 ABEND04E RC00D93012 RC00C200F7 RC00D31106 ---------------------------------------------------------------- Symptoms: abend0c4 in dsn3id00 x'176' (per ABEND-AID dump) sys1.logrec shows 0c4 in DSN3@ATH. Problem occurs after migrating to Top Secret Rel. 4.3 from Prev. Top Secret Rel. .. Solution: Top Secret Rel. 4.3 no longer requires ++USERMOD in order to run DB2 sample Auth. exit (DSN3SATH). User had to backout (reject/restore) Top Secret ++USERMOD before compiling DSN3SATH. ---------------------------------------------------------------- OEM Strobe applications monitor tool indicates DB2 has high cpu usage of pc stack/unstack module ieavxstk: ----- This is not a bug. It is not a bug in Strobe, DB2, or cross memory services. IBM db2, cross memory services, and Dallas Systems Center are all aware of the high cpu usage and there is no 'future fix' planned for this usage. ----- DB2 architecture makes extensive use of cross memory services. DB2 DSNZPARM option on panel DSNTIPJ allows the selection of PC=NO or PC=YES. PC=NO option will result in a reduction of cpu usage at a cost of increased ECSA virtual storage. PC=YES will cause increased cross memory activity and CPU utilization. ---------------------------------------------------------------- OEM Strobe applications monitor tool indicates DB2 has high cpu usage of MVS Timer Services module ieavrt05: ----- This is not a bug. It is not a bug in Strobe, DB2, or MVS Timer Services. IBM DB2, MVS, and Dallas Systems Center are all aware of the high cpu usage and there is no 'future fix' planned for this usage. ----- DB2 Accouting Trace Class 2 will cut an IFCID 121 record when DB2 is entered from an application and an IFCID 122 record when DB2 completes processing and returns control to the calling application. In each case, the IFCID 121 and IFCID 122 records are followed by a call to Timer Supervisor module IEAVRT05 for a timestamp. This results in the High CPU usage seen in IEAVRT05. Specifically, a program executing a large number of SQL statements, either a singleton SELECT (or DML) in a DO LOOP or an OPEN CURSOR followed by a FETCH in a DO LOOP will cause many calls to ieavrt05 (where many rows are returned to a program, one at a time). This can also be seen where the SQL statement is not very complex, in other words, not very CPU intensive. Also high cpu usage in ieavrt05 can be seen where the program does not spend a lot of time processing rows retrieved from DB2. In other words, class 1 CPU time is not much greater than class 2 CPU time. ----- In general, only turn on Accounting Trace Class 2 to investigate a problem, or collect information on a new program going into production. --------------12-29-95-------- Problem: If you are reorganizing a DB2 V3 compressed tablespace and you restart the reorg during the reload phase, the first spacemap may not be updated correctly to indicate which pages are used for the compression dictionary. After the Reorg, if DB2 tries to insert rows at the beginning of the tablespace, it may try to use the dictionary pages, which would cause DB2 errors with 00C90101 and 00C90105 reason codes. Resolution: Platinum Rapid Reorg, Versions P404AA-AF, and P411AA-AC Dated: Oct. 6, 1995 Problem number: PARS 191448 The zap is: PUT41102 --------------------------------------------------------------- PROBLEM: Storage overlay in high user private. Various DB2 storage manager errors like ABEND0C4, ABEND04E RC00E20005 DSNSVBK FIX: Candle OMEGAMON II/DB2 V270 csect O2CDCI fix number QD2D142 --------------------------------------------------------------- ABEND03F5 or ABEND3F5 in DSN9SCN9, CA/TMS, CA-1/TMS, TMSINIT DUMP TITLE=DBA2,ABND=3F5-00000000,U=SYSOPR ,C=XYR00.410.RLMC- DSNJDS04,M=DSN9SCN9,PSW=070C100080986FAA,A=0028 occurs for DB2 v4 with datasharing following messages: IEFTMS70 3YY-108 OPCODE=36 IEFTMS70 ***** CA-1 ABEND,IO,36 ***** ** DSNJ125I @DBA2 ERROR DUMPING BSDS, OFFLOAD CONTINUING 826 WITHOUT PRODUCING THE BSDS DUMP **Note:** This is not a DB2 error. This error occurs on behalf of CA-1/TMS or CA/TMS. TMS provides a TMSINIT job which is to be run on each CPU. If it is not, this error may occur because of a tape label problem. Check if the TMSINIT job has been run properly. ---------------------------------------------------------------- 6/20/96 ABEND04F RC00E80100 and/or ABEND0C1 with psw pointing to low core address (ie 80000004) after stopping and restarting DB2 but leaving BMC Activity Monitor up. Customer received a fix from BMC (P270153) that resolved the abends. ----------------------------------------------------------------
Local fix
-4-15-93------------------------------------------ an abend0c6 can occur in various mvs supervisor modules while an svc is being executed. So far the abend0c6 has been seen in: ieaveexp +16a ieavesvc +192 The problem has been identified as being cause by computer associates enf ca90. the trace entry for the scvr has a psw address pointing into cas9cms. a fix is not available. -------------------------------------------------- 05-05-93 START DB2 - MSGDSNR002I - RESTART COMPLETED IS RECEIVED MSGDSN9022I - DSNYASCP '-START DB2 NORMAL COMPLETION IS NEVER RECEIVED START STARTUP DB2 LOOP LOOPS LOOPING R230 - ACF2 FIX #C079781 LOOK AT SYSTEM TRACE TABLE USING DB2MSTR ASID. LOOK AT TCB OPSW FOR CURRENT RB. THIS WILL POINT TO ACF2. --------------------------------------- Catalog Visibility S806-04, module DSNXDBF1.When user is using catalog visibility, DESCRIBE option abend with SQLCODE551. ---------------------------------------------------------- Problem is caused by OEM CA. ---------------------------------------------------------- Fix: CA PTF# T99E045 for ENF. ------------------------------------------------------- MSGDSNX200I REBIND SQL ERROR USING XXXXX AUTHORITY PLAN=YYYYY , DBRM=ZZZZZ , STATEMENT=3379 , SQLCODE= -104 , TOKENS= :.( , CSECT NAME= DSNHPARS RDS CODE=0 MSGDSNT201I REBIND FOR PLAN YYYYY NOT SUCCESSFUL ... This problem is due to the OEM product ( IEF Version 4 ) of J.M.A. vendor and is solved with oem fix TIM40A2 . ---------------------------------------------------------------- Running migration job DSNTIJSG (step 25) on RLST, user gets SQLCODE551 when drop index sysibm.dsnarl01. Using ACF/2 (ACF2). The fix that CA has identified is for the ENF product. The fix number is T99E018. ------------------------------------------------------------- 06/12/93 ---------------------------------------------------- db2 archive goes to dasd, when the system zparm dsn6arvp is set to cart or tape: Problem: archives going to DASD instead of Tape. Symptoms may include ABEND013 and/or MSGIEC141I. Solution: OEMs intercepting/modifying allocation requests. POOL DASD - forces every allocation specifying SPACE parm to DASD. VAM - need new release for ESA 4.2 SMS - ACS routines override allocation - key off if the space parameter and assume dasd. ---------------------------------------------------------------- SQLCODE904 and RC00C9007F accessing a TABLE within a COMPRESSED TABLESPACE after Platinum Quick Copy. DICTIONARY PAGEs get overlaid. The Platinum Quick Copy fix is "QCM20090".
Problem summary
Problem conclusion
Temporary fix
Comments
pinned for retention db2info ====================================== 12/15/95 dchan sqlcode134 sqlcode180 on v4 or v3 after un82588, un82589, un82590 for intelligent environment's sql workbench product when length isn't specified for compiler for date, time and timestamp. workaround is to specify lengths for these variables: SQLTYPE WORKBENCH LENGTH SPECIFICATION DATE :#10 TIME :#8 TIMESTAMP :#26
APAR Information
APAR number
II06483
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
1992-10-28
Closed date
1995-09-14
Last modified date
2000-08-01
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:
13 December 2020