APAR status
Closed as canceled.
Error description
DB2 5740XYR00 R230, R310, R410, R510 ==================================== Following is advise for some problems encountered when running the DB2 installation verification programs (IVP's). These problems are typically caused by sources outside of DB2 and so are not considered program errors. Abend30A is one of the many errors if the following is not adhered to. 1) DSNTEJ1P or DSNTEP2: If using LE/370 runtime library with PL/I program DSNTEP2 ABENDU4093, ABENDU4038 & various RC's may occur. Check the PL/I manuals for why the user abend was issued. A recompile of DSNTEP2 may be required using different options. If DSNTEJ1P step PH01PS02 BIND DSNTEP2 fails with: msgIEL0970I compiler error 3 during phase EA msgIEL0276I something about an ELSE... This error is caused by using an old PL/I release in the DB2 V4.1 IVP job. Check program directory for correct versions. DB2 R410 PL/I IVPs do not work with PL/I Optimizing Compiler and Libraries V.1.5.1 (5734-PL3). For DB2 R410, your PL/I version must be either: PL/I Compiler, Library & Interactive Test Facility V.2.3 (5668-909) or PL/I for MVS & VM V1.1 (5668-235) 2) DSNTEJ2C: If you are using OS/VS COBOL, ensure that all occurrences of PARM.COB specify NORES and that all occurrences of PARM.LKED specify RENT. The DSNTEJ2 joblog should indicate that DSN8MSG has been compiled NORES and that it has been linked RES NO and RENT YES. If you are using COBOL II, ensure that all occurrences of PARM.COB specify NORES and NORENT and that all occurrences of PARM.LKED specify NORENT. The DSNTEJ2 joblog should indicate that DSN8MSG has been compiled NORENT and NORES and that it has been linked RES NO and RENT NO. If you are using COBOL 370, ensure that all occurrences of PARM.COB specify RES and RENT and that all occurrences of PARM.LKED specify RENT. The DSNTEJ2 joblog should indicate that DSN8MSG has been compiled RENT and RES and that it has been linked RES NO and RENT YES. If you are using IBM COBOL, ensure that all occurrences of PARM.COB specify RENT and that all occurrences of PARM.LKED specify RENT. The DSNTEJ2 joblog should indicate that DSN8MSG has been compiled RENT and that it has been linked RES NO and RENT YES. Miscelleneous DSNTEJ2C problems: - ABEND0C1 IN DSN8BC4 + X'06'. THIS ABEND WILL OCCUR WHEN COBOL HAS BEEN INSTALLED WITH THE DEFAULT OPTIONS OF 'BATCH AND NAME'. THIS CAUSES THE OUTPUT FROM THE COMPILER TO BE LINKEDITED INTO A LOAD MODULE BY ITSELF. THE JOB THEN LINKEDITS A LOAD MODULE BY THE SAME NAME WITH INCLUDES FOR DSNELI AND DSN8MCG BUT THE COMPILED CSECT DSN8BC4 IS NOT INCLUDED. THIS SECOND LINKEDIT OVERLAYS THE ORIGINAL MODULE AND HAS NO EXECUTABLE CODE. MSGIEW0132 CAN ALSO OCCUR FOR CSECT DSN8MCG DURING THE FIRST LINKEDIT. CIRCUMVENTION: SPECIFY THE COBOL OPTIONS 'NOBATCH AND NONAME' IN THE PARM.COB STATEMENT FOR EACH OF THE 4 COMPILER JOB STEPS. - ABEND0C1 IN DSN8MCG + X'7C' BRANCHING TO ADDRESS ZERO. WHEN USING COBOL II WITH THE DYNAM OPTION, MSGIEW046I OCCURS FOR IGZEBST IN STEP PH02CS02. THIS CAUSES THE ADDRESS OF IGZEBST TO BE UNRESOLVED IN DSN8MCG. DURING THE PROGRAM INITIALIZATION, COBOL LOADS THE VCON INTO REGISTER 15 AND ATTEMPTS TO BRANCH TO IT. CIRCUMVENTION: IF YOU ARE USING THE DYNAM OPTION OF COBOL II, YOU MUST ADD THE FOLLOWING LINKEDIT OVERRIDE TO PH02CS02: //LKED.SYSIN DD * INCLUDE SYSLIB(IGZEBST) - ABEND0C4 OR LOOP IN DSN8BC4 WHEN USING COBOL 2.4 WITH COMPILER OPTIONS DYNAM AND RES. COBOL VERSION 2.4 DOES NOT SUPPORT THE DYNAM OPTION. SPECIFY OPTIONS NODYNAM AND NORES FOR BOTH STEPS PH02CS02 AND PH02CS03. PP29812 PP53133. - ABENDU4093 RC=1C (RC1C) if using LE/370 for the DB2 IVPs. The JES2 default region size may not be large enough. Enlarge region size to run the IVPs should the abend occur 3) DSNTEJ3C: If you are using OS/VS COBOL, ensure both of the following are true: (a) You have run DSNTEJ2C, specifying NORES for all occurrences of PARM.COB and RENT for all occurrences of PARM.LKED. This is required because DSNTEJ3C uses module DSN8MCG, which is prepared by DSNTEJ2C. (b) All occurrences of PARM.COB in DSNTEJ3C specify NORES. The DSNTEJ3C joblog should indicate that DSN8CC, DSN8SCM, DSN8SC3, and DSN8HC3 have been compiled NORES and linked RES NO and RENT NO. If you are using COBOL II, ensure both of the following are true: (a) You have run DSNTEJ2C, specifying NORES and NORENT for all occurrences of PARM.COB and NORENT for all occurrences of PARM.LKED. This is required because DSNTEJ3C uses module DSN8MCG, which is prepared by DSNTEJ2C. (b) All occurrences of PARM.COB in DSNTEJ3C specify NORES and NORENT. You can also use the DSNTEJ3C joblog to verify that DSN8CC, DSN8SCM, DSN8SC3, and DSN8HC3 have been compiled NORENT and NORES and linked RES NO and RENT NO. If you are using COBOL 370, ensure both of the following are true: (a) You have run DSNTEJ2C, specifying RES and RENT for all occurrences of PARM.COB and RENT for all occurrences of PARM.LKED. This is required because DSNTEJ3C uses module DSN8MCG, which is prepared by DSNTEJ2C. (b) All occurrences of PARM.COB in DSNTEJ3C specify RES and RENT. The DSNTEJ3C joblog should indicate that DSN8CC, DSN8SCM, DSN8SC3, and DSN8HC3 have been compiled RENT and RES and linked RES NO and RENT NO. If you are using IBM COBOL, ensure both of the following are true: (a) You have run DSNTEJ2C, specifying RENT for all occurrences of PARM.COB and RENT for all occurrences of PARM.LKED. This is required because DSNTEJ3C uses module DSN8MCG, which is prepared by DSNTEJ2C. (b) All occurrences of PARM.COB in DSNTEJ3C specify RENT. DSN8SC3, and DSN8HC3 have been compiled RENT and linked DSNTEJ2U : To resolve return code 0008 in steps PH02US08 and PH02US09, either unnumber the source decks for programs DSN8EUDN and DSN8EUMN or change the NOMAR parm of Compiler options to MAR. Symtoms: CBC1260 &/| CBC1090 or msgcbc1260 msgcbc1090 4) DSNTEJ3P : - msgIEW2648e entry PLICALLA is not a CSECT or external name in the module. This error is caused by using OS PL/I Compiler/Library V2.3 during CLIST processing and then modifying the DSNHPLI PROC to use the new PL/I for MVS & VM V1.1. These two PL/I products have different entry point names as listed in step 1 SYSIN DD card of job DSNTEJ3P. OS PL/I uses entry point PLICALLA. PL/I for MVS & VM uses entry point CEESTART. Depending on what PL/I libraries were entered on panel DSNTIPG, a different entry point name will be used in DSNTEJ3P. 5) DSNTEJ5C: If you are using OS/VS COBOL, ensure both of the following are true: (a) You have run DSNTEJ2C, specifying NORES for all occurrences of PARM.COB and RENT for all occurrences of PARM.LKED. This is required because DSNTEJ5C uses module DSN8MCG, which is prepared by DSNTEJ2C. (b) All occurrences of the COPTION parmlist in DSNTEJ5C specify NORES and all occurrences of the LOPTION parmlist specify RENT. The DSNTEJ5C joblog should indicate that that DSN8CC0, DSN8CC1, and DSN8CC2 have all been compiled NORES and linked RES NO and RENT YES. If you are using COBOL II, you will need to -rerun- DSNTEJ2C -after- you have run DSNTEJ3C but -before- you run DSNTEJ5C. This is required because programs prepared by DSNTEJ5C use the DSN8MCG module prepared by DSNTEJ2C and DSN8MCG must be recompiled and relinked as re-entrant for CICS. ==> When you -rerun- DSNTEJ2C, first change NORES and NORENT in all occurrences of PARM.COB to RES and RENT and change NORENT in all occurrences of PARM.LKED to RENT. ==> Then, run DSNTEJ5C after ensuring that all occurrences of the COPTION parmlist specify RENT and that all occurrences of the LOPTION parmlist specify RENT. ==> The DSNTEJ5C joblog should indicate that DSN8CC0, DSN8CC1, and DSN8CC2 have been compiled RENT and RES and linked RES NO and RENT YES; the DSNTEJ2C joblog should indicate that DSN8MCG has been compiled RENT and RES and linked RES NO and RENT YES. If you are using COBOL 370, ensure both of the following are true: (a) You have run DSNTEJ2C, specifying RES and RENT for all occurrences of PARM.COB and RENT for all occurrences of PARM.LKED. This is required because DSNTEJ5C uses module DSN8MCG, which is prepared by DSNTEJ2C. (b) All occurrences of the COPTION parmlist in DSNTEJ5C specify RENT and all occurrences of the LOPTION parmlist specify RENT. The DSNTEJ5C joblog should indicate that that DSN8CC0, DSN8CC1, and DSN8CC2 have all been compiled RENT and linked RES NO and RENT YES. If you are using IBM COBOL, ensure both of the following are true: (a) You have run DSNTEJ2C, specifying RENT for all occurrences of PARM.COB and RENT for all occurrences of PARM.LKED. This is required because DSNTEJ5C uses module DSN8MCG, which is prepared by DSNTEJ2C. (b) All occurrences of the COPTION parmlist in DSNTEJ5C specify RENT and all occurrences of the LOPTION parmlist specify RENT. The DSNTEJ5C joblog should indicate that that DSN8CC0, DSN8CC1, and DSN8CC2 have all been compiled RENT and linked RES NO and RENT YES. 6) DSNTEJ5P - MSGIEW0241 DFHEPI DOUBLY DEFINED. THIS ERROR OCCURS IF, DURING THE INSTALL OF PL/I, THE OPTIONAL 6TH LINKEDIT STEP WAS NOT PERFORMED. THIS STEP CREATES AN ALIAS OF DFHEPI FOR DFHPL1OI. - MSGDSNH007I AND MSGDSNH105I WHEN INSTALLATION OPTION OF MIXED DATA = YES. THESE PRECOMPILER ERRORS OCCUR FOR VARIOUS STEPS OF DSNTEJ5P. STEP 6 (PH05CS06) EXECUTES THE CICS TRANSLATOR. THE TRANSLATOR GENERATES PL/I CALL STATEMENTS FOR EACH OF THE EXEC CICS STATEMENTS. THE GENERATED CODE INCLUDES X'0E' CHARACTERS. STEP 7 (PH05PS07) THEN EXECUTES THE DB2 PRECOMPILER. WHEN THE INSTALLATION OPTION MIXED=YES IS SPECIFIED, THE DB2 PRECOMPILER ASSUMES THIS X'0E' TO BE A SHIFT-OUT CHARACTER WHICH DOES NOT HAVE A PAIRED SHIFT-IN CHARACTER, RESULTING IN THE ERROR MESSAGES. CIRCUMVENTION: EXECUTE THE CICS TRANSLATOR AFTER THE DB2 PRECOMPILER. FOLLOWING IS ONE POSSIBLE METHOD OF CHANGING THE JOB AND THE INVOKED PROCEDURE TO ACCOMPLISH THIS. (1) CREATE A NEW PROCEDURE IN YOUR SYS1.PROCLIB. MAKE A COPY OF DSNHPLI UNDER A NEW NAME. CHANGE THE PROC AND PEND STATEMENTS TO THE NAME OF YOUR NEW PROCEDURE. ADD THE FOLLOWING STATEMENTS AFTER THE PC (PRECOMPILE) STEP AND BEFORE THE PLI (COMPILE) STEP: //* //* TRANSLATE THE CICS PROGRAM IF THE PRECOMPILE //* RETURN CODE IS 4 OR LESS //* //TRN EXEC PGM=DFHEPP1$,COND=(4,LT,PC) //SYSPRINT DD SYSOUT=* //SYSUDUMP DD SYSOUT=* //SYSPUNCH DD DISP=(NEW,PASS),DSN=&&CICSOUT,UNIT=SYSDA, // DCB=BLKSIZE=400,SPACE=(400,(&WSPC,&WSPC)) //SYSIN DD DSN=&&DSNHOUT,DISP=(OLD,DELETE) (2) MAKE THE FOLLOWING CHANGES TO JOB DSNTEJ5P: A) DELETE ALL CICS TRANSLATE JOB STEPS, STEPS 6, 8, 10, 12, 16, 18, 20. B) CHANGE ALL OCCURENCES OF PROC NAME DSNHPLI TO YOUR NEW PROCEDURE NAME. STEPS 7, 9, 11, 13, 17, 19, 21. C) CHANGE ALL OCCURENCES OF //PPLI.SYSIN TO: //PPLI.SYSIN DD DISP=SHR,DSN=DSN130.DSNSAMP(XXXXXXX) WHERE XXXXXXX IS THE MEMBER NAME AND IS THE SAME AS THAT ON THE STEP EXEC STATEMENT. D) CHANGE ALL OCCURENCES OF //PC.SYSCIN TO: //PC.SYSCIN DD DSN=&&DSNHOUT E) CHANGE ALL OCCURENCES OF //PLI.SYSIN TO: //PLI.SYSIN DD DSN=&&CICSOUT 7) DSNTEJ6D -Return code 0012 from step PH06DS03 and message "*** DSN8ED1 completed; highest return code was xxxxxxxx" where 'xxxxxxxx' is a large number. Ensure that DSN8ED1 has been compiled as NORENT. You may need to add NORENT to the PARM.C list in step PH06DS01. Please note that the stored procedure program, DSN8ED2 (prepared by job DSNTEJ6T) should be compiled as RENT.
Local fix
Problem summary
Problem conclusion
Temporary fix
Comments
APAR Information
APAR number
II03403
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
1988-05-31
Closed date
1988-12-30
Last modified date
2000-01-14
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":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEPEK","label":"DB2 for z\/OS"},"Platform":[{"code":"PF054","label":"z Systems"}],"Version":"001","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
31 July 2023