|
View previous topic :: View next topic
|
| Author |
Message |
Prashant Singh
New User
Joined: 03 Nov 2020
Posts: 1
Location: India
|
|
|
|
I am getting below mentioned error message in the SYSOUT of the error Step in the JCL
| Code: |
IGZ0035S THERE WAS AN UNSUCCESSFUL OPEN OR CLOSE
OF FILE P**R2602 IN PROGRAM PT**2602 AT RELATIVE
LOCATION X'FFFFFFFFE415D600'. NEITHER FILE STATUS
NOR AN ERROR DECLARATIVE WERE SPECIFIED.
THE STATUS CODE WAS 96.
FROM COMPILE UNIT PTKM2602 AT ENTRY POINT
PTKM2602 AT COMPILE UNIT OFFSET +00000A06
AT ENTRY OFFSET +00000A06 AT ADDRESS 1BF6FA06. |
Below is the JCL Error step where there is issue with the file name :
| Code: |
//STEP020 EXEC DSNTSO
//SYSOUT DD SYSOUT=*
//PTKR4211 DD DSN=D18PTK00.P**R4211.LIST,DISP=(,CATLG,CATLG),
// DCB=(RECFM=FBA,LRECL=133,BLKSIZE=0),
// SPACE=(133,(20,50),RLSE)
//PTKR4221 DD DSN=D18PTK00.P**R4221.LIST,DISP=(,CATLG,CATLG),
// DCB=(RECFM=FBA,LRECL=133,BLKSIZE=0),
// SPACE=(133,(20,50),RLSE)
//SYSTSIN DD *
DSN SYSTEM(JTY)
RUN PROG (P**P950D) PLAN(PPTKERA)
END
|
The issue the file P**R2602 mentioned in the SYSOUT is not defined in the JCL Step. Also there are no such file defined in the Cobol module P**P950D.
Below is the File-Section From Cobol Code :
| Code: |
INPUT-OUTPUT SECTION.
FILE-CONTROL.
DATA DIVISION.
FILE SECTION.
*-----------------------------*
WORKING-STORAGE SECTION. |
|
|
| Back to top |
|
 |
Nic Clouston
Global Moderator
Joined: 10 May 2007
Posts: 2455
Location: Hampshire, UK
|
|
|
|
Please use the code tags when posting code and data. I have edited your post to use them this time.
What you have not shown us is the code that causes the error within the program. Somewhere in the program reference to that file is being made. |
|
| Back to top |
|
|
Rohit Umarjikar
Global Moderator
Joined: 21 Sep 2010
Posts: 3053
Location: NYC,USA
|
|
|
|
Welcome!
verify the DD name specified in the JCL vs what is being used in the program , obviously they don’t match . |
|
| Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008
Posts: 8697
Location: Dubuque, Iowa, USA
|
|
|
|
| Quote: |
| The issue the file P**R2602 mentioned in the SYSOUT is not defined in the JCL Step. Also there are no such file defined in the Cobol module P**P950D. |
Yeah, the file status 96 pretty much means that your program attempted to open a file for which there was no DD statement in the JCL -- so your first statement is true (a tautology but still). As far as your second sentence about no such file defined in the COBOL module P**P950D -- so what? If you read the SYSOUT message again, you will note that the program name is NOT P**P950D but rather PTKM2602. So there is some mechanism by which P**P950D invokes PTKM2602 -- and PTKM2602 is the program with the missing DD statement. If you fix the JCL, you will fix the error. |
|
| Back to top |
|
|
|
|
