APAR status
Closed as canceled.
Error description
============================================================ SECTION 1: TOLERATION, COEXISTANCE AND COMPATIBILITY PTFS. ============================================================ 5740XYR00 DB2 V4.1 MIGRATION/FALLBACK INFOAPAR TO/FROM DB2 V5.1 R410 TO R510 OR R510 TO R410 FOLLOWING PTFS ARE REQUIRED FOR DB2 V4.1 & V5.1 BEFORE MIGRATION: DB2 system administrator should take a back up from DB2 environment (SMP/E, Active logs, BSDSs, DB2 Catalog/Directory) before applying maintenance. Non_DataSharing customers need to apply all PTFs in SECTION 1. Note: apply all the following PTFs plus their associated prereqs, fixing PTF (if PE'd) and superseding PTF/s. APAR PTF PUT ******* ******* ******* PN84642 / UN92416 put9607 PN89355 / UN96124 put9610 PN87829 / UN98205 put9612 PN91395 / UN98593 put9612 PN87672 / UN90165 put9701 PN87673 / UN90165 put9701 PN87674 / UN90165 put9701 PN91515 / UQ08376 put9708 PN91681 / UQ00314 put9701 (IPL required for ERLY 5740XYR01 fix) PQ00396 / UQ00855 put9702 PQ01103 / UQ01335 put9702 PQ01569 / UQ02249 put9703 PQ01092 / UQ02285 put9703 PQ01902 / UQ02500 put9703 PQ00861 / UQ02661 put9704 PQ00173 / UQ02684 put9704 PQ01380 / UQ02909 put9704 PQ04437 / UQ05051 put9706 PQ04074 / UQ05525 put9706 PQ05493 / UQ06661 put9707 PQ06203 / UQ08067 put9708 PQ05908 / UQ09505 put9710 PQ09421 / UQ12208 put9712 PQ13045 / UQ15498 put9803 PQ16944 / UQ19915 put9808 (only needed if R510 was >put9808) PQ15492 / UQ22192 put9810 PQ22050 / UQ28835 put9904 (V4/V5 coexistence environment. This is required if PQ22051 is applied to V5. If PQ22051 is applied to V5, this fix has to get applied on all V4 members of a DataSharing Group before Migration of first member). DSNHDECP has to get relinkedited after ACCEPTing of this PTF if JCLIN is not created for DSNHDECP. Please refer to SECTION 3 of this Info APAR to bypass ACCEPT processing PQ23074 / UQ27559 put9903 Abend0C4 on CATMAINT CONVERT to type 2 index after UQ22814. PQ24378 / UQ28814 put9904 This is a prerequisite to PQ22050. PQ27412 / UQ30993 put9906 0C4 DSNUTILA.DSNUSUCD+0EFC EXECUTING RUNSTATS on a DS member after PQ22050 PQ27432 / UQ32308 put9907 Prevent duplicate OBIDs PQ30313 / UQ34319 put9909 Coexistance DataSharing environment if PQ29582 is applied to DB2 V5.1. PQ34199 / UQ40802 put0003 DSNX208E & DSNR032R at start up time. coexistence PTF for Datasharing Group UQ35788 has to be applied to all V410 members before applying this PTF ELSE Maintenance MUST get applied to DS Group (Recycling DS). UQ40802 must be applied to all members at the same time. Please pay attention to cover letter. This PTF, Customers need to recreate DSNHDECP after applying this PTF. PQ35206 / UQ41002 put0003 RUNSTATS lead to ABEND04E RC00E40213 after PQ22050. PQ39555 / UQ45887 put0008 Coexistence PTF. PQ36846 / UQ46610 put0009 SOME HEADER PAGE INFO. is INCORRECT. ========= Following PTFs are for DB2 R5.1 ================ PQ20214 / UQ23085 put9811 needs to be on to DB2 V5.1 before Mig. PQ23074 / UQ27560 put9903 Abend0c4 on RECOVER INDEX after UQ23002. PQ23490 / UQ28018 put9904 UQ28018 is necessary if PQ16674(UQ23612) is applied. Putting UQ23612 without UQ28018 causes Abend04E with RC00E40601 and associated Reg4 & Reg5 of generated SVC Dump points to FFFFFF39 within CATMAINT processing (DSNTIJTC job). PQ22051 / UQ28912 put9905 This PTF has to get Applied before MIGRATION if PQ22050 is already Applied to V5.1 and/or V4.1. NOTE: Remove any VIEWs from SYSCOLDIST & SYSCOLDISTSTATS before running DSNTIJTC. PQ27412 / UQ30994 put9906 0C4 DSNUTILA.DSNUSUCD+0EFC EXECUTING RUNSTATS on a DS member after PQ22050 PQ27432 / UQ32309 put9907 Prevent duplicate OBIDs PQ29582 / UQ34283 put9909 To resolve DSNX208E issue. PQ31296 / UQ36505 put9911 ABEND0C4 &| 04E during CATMAINT from DSNUT510 on DSNUEDTT (batch DSNTIJTC) Please see II12123 for more symptoms. PQ35325 / UQ40315 put0003 CATMAINT sets BOUNDTS field starting 19.. during Migration in 2000. PQ34199 / UQ40803 put0003 DSNX208E & DSNR032R at start up time. coexistence PTF for DS Group. UQ35788 has to be applied to all V410 members before applying this ELSE Maintenance MUST get applied to DS Group (Recycling DS). UQ40802 has to be applied to all V410 members before applying this PTF. UQ34283 has to be applied to all V510 members before applying this PTF. Please pay attention to cover letter This PTF, Customers need to recreate DSNHDECP after applying this PTF. PQ35206 / UQ41003 put0003 RUNSTATS lead to ABEND04E RC00E40213 after PQ22051. PQ39555 / UQ45888 put0008 Coexistence PTF. PQ36846 / UQ46611 put0009 SOME HEADER PAGE INFO. is INCORRECT. =============================================================== SECTION 2: DSNR032I and/or DSNX208E Messages =============================================================== If RMID of DSNARIB module is a PTF, that PTF has to get ACCEPTed before relinkedit of DSNHDECP(DSNTIZQ step of DSNTIJUZ) if JCLIN is not created for DSNHDECP. Please refer to SECTION 3 of this Info APAR to bypass ACCEPT processing. * If the following error occurred: DSNR032I -DSN DSNRRPRC DB2 IS STARTING AT RELEASE LEVEL 410, WHICH IS NOT COMPATIBLE WITH RELEASE 510 DSNV086E -DSN DB2 ABNORMAL TERMINATION REASON= 00D900FA The possible causes are: -The user is trying to start DB2 in the fallback/coexistance mode and the fallback spe UN90165 is not installed. -The user is trying to start DB2 in the fallback/coexistance mode but DSNHDECP is down level ADDITIONAL SYMPTOMS: msgDSNR032i DSNARIB in DSNHDECP is NOT at correct level. DataSharing users may see: msgDSNR041E rc00D900F9 rc00D90110 * Following are steps that could identify DSNARIB module level: 1 - Browse DSNARIB module in ADSNLOAD distribution library and find UN90165. 2 - Issue the following MVS SLIP command to generate a SVC Dump on a Message : SLIP SET,IF, ACTION=SVCD, SDATA=(ALLNUC,PSA,SUM,TRT,CSA,SQA,LSQA,RGN,GRSQ), ASIDLST=(CURRENT,H), JOBLIST=(xxxxMSTR,xxxxDBM1), LPAMOD=(IGC0003E), DATA=(1R?+4,EQ,C4E2D5D9,AND,1R?+8,EQ,F0F3F2C9), END. WTO messages IRLM DB2 message 3 - Get into IPCS and select COMMAND from IPCS Primary Option Menu and Issue following commands: 3/1- DROPD 3/2- SETDEF DSNAME('your Dump dataset name') 3/3- VERBX DSNWDMP 'SG,SUBSYS=ssid' 3/4- F SCOM & pickup the address 4 - Select BROWSE from IPCS Primary Option Menu (you have to see your Dump dataset name else go to 3/1) and press ENTER 5 - Browse the address that you picked up from 3/4 and locate In eyecatcher section of dump you see DSNARIB and PTF level. * Following are steps to resolve this issue: =============================================================== SECTION 3: MODIFIED LINKEDIT JCL FOR DSNHDECP TO BYPASS ACCEPT =============================================================== Under V5.1 apply PQ29582, under V4.1 apply PQ34199 OR Submit following JCL for both V4.1 and/or V5.1. //JOBCARD JOB ........... //DSNTIZP EXEC PGM=ASMA90,PARM='OBJECT,NODECK',COND=(4,LT) . . The same content to Assemble DSNHDECM macro - From DSNTIJUZ . //DSNTIZQ EXEC PGM=IEWL,PARM='LIST,XREF,LET,RENT', // COND=(4,LT) //ADSNLOAD DD DISP=SHR, // DSN=prefix.SDSNLOAD // DD DISP=SHR, // DSN=prefix.ADSNLOAD //SYSPUNCH DD DSN=&&LOADSET(DSNHDECA),DISP=(OLD,DELETE) //SYSLMOD DD DISP=SHR, // DSN=prefix.SDSNEXIT //SYSPRINT DD SYSOUT=* //SYSUDUMP DD SYSOUT=* //SYSUT1 DD UNIT=SYSDA,SPACE=(1024,(50,50)) //SYSLIN DD * INCLUDE SYSPUNCH(DSNHDECA) ORDER DSNAA INCLUDE ADSNLOAD(DSNAA) INCLUDE ADSNLOAD(DSNHDECP) ENTRY DSNHDECP MODE AMODE(24),RMODE(24) NAME DSNHDECP(R) //* //DSNTIMQ EXEC DSNTIJSM, // COND=(2,LT) //SMPCNTL DD * SET BDY(targetzonename). JCLIN. //SMPJCLIN DD DISP=SHR, // DSN=prefix.NEW.SDSNSAMP(DSNTIJUZ) //* NOTE: ADSNLOAD DD statement of DSNTIZQ step has to point to SDSNEXIT target library of SMP/E if SYSLIB of JCLIN or PTF points to: SYSLIB SDSNEXIT SDSNLOAD, listed in CSI QUERY of LMOD ENTRY DSNHDECP for its LASTUPD field of related target zone. ============================================================== SECTION 4: CUSTOMERS EXPERINCE AND INFORMATIONAL ISSUES ============================================================== 08/01/97 - plb PTF UN90165 changes the RMODE & AMODE of DSNECP00, DSNECP10 and DSNESM00. Effected modules within DB2 V4 with UN90165 + later release/s: DSNECP00 - TSO Attach DSN command DSNECP10 - TSO Attach RUN subcommand DSNESM00 - TSO Attach SPUFI DB2 application which was link edited with old AMODE/RMODE needs to get link edited again to pick up new AMODE/RMODE. the Bind/Rebind/Free commands obtain response message buffers using GETMAIN LOC=ANY which may return 31-bit buffer addresses. DSN will abend when these commands try and pass 31bit buffers to DSN if the AMODE of DSN is AMODE(24). 08-29-97 TEB DB2 DCLGEN users requesting DB2 table statement declarations in COBOL may receive TSO error messages IKJ56284I, IKJ56285I and IKJ56286I if PN87674/UN90165 applied. However, the resultant output table mapping structure provided by DCLGEN is correct and may still be used in a COBOL application program. Customers can apply pq01103 (uq01335 / uq01336) for this. 10/13/97 MRS ABEND04e was issued for DSNXGRDS.DSNXLDDL with RC00E70014 at Migration step 16 (Start DB2 for OS/390 Version 5) when RGFINST of ZPARM module was equal to YES and created tables for Registration Data Base was empty. When RGFINST was changed to NO abend was not issued. 12/09/97 JE DSNTIJTC - If you receive an Abend04e with RC00E40601 which Reg4 &/| 5 of associated SVC Dump contains FFFFFDA7, that means the name of the object to be created by CATMAINT is identical to an existing one. FFFFFDA7 is SQLCODE601. You need to DROP any existing ones before CATMAINT processing. Reg2 of the same Dump should point to the area that eye-catcher shows: DSNXI14 RETURNED SQLCODE < 0, R3->STMT and Reg3 of the same Dump should point to the area that eye-catcher Please note APAR PQ28045 also (LOCAL FIX). Please look at continuing Informational APAR II12123.
Local fix
Problem summary
Problem conclusion
Temporary fix
Comments
closed for DB2INFO retention
APAR Information
APAR number
II10128
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
1997-01-06
Closed date
1997-06-02
Last modified date
2000-10-18
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"},"Platform":[{"code":"PF054","label":"z\/OS"}],"Version":"001"}]
Document Information
Modified date:
03 March 2021