IBM Mainframe Forum Index
 
Log In
 
IBM Mainframe Forum Index Mainframe: Search IBM Mainframe Forum: FAQ Register
 

An write operation error - ABENDED S000 U40


IBM Mainframe Forums -> COBOL Programming
Post new topic   Reply to topic
View previous topic :: View next topic  
Author Message
sandeep prajapati

New User


Joined: 23 Mar 2020
Posts: 19
Location: India

PostPosted: Sun Apr 12, 2020 12:16 pm
Reply with quote

SYSOUT error:

Code:
IGZ0020S A logic error occurred. Neither FILE STATUS nor a declarative was specified for file BALANCE in program ACCOUNTS at relative location X'86C'.  The status code was 48. From compile unit ACCOUNTS at entry point ACCOUNTS at compile unit offset +0000086C at entry offset +0000086C  at address 1AD0086C.   


JCL:

Code:
//COBRUN   JOB NOTIFY=Z56117,CLASS=A,MSGCLASS=A,PRTY=15   
//COBOL    EXEC IGYWCL,MBR=BANKCOB                         
//RUN      EXEC PGM=BANKCOB                               
//STEPLIB  DD   DSN=&SYSUID..LOAD,DISP=SHR                   
//BALANCE  DD DSN=Z56117.SOURCE.BALANCE,DISP=SHR           
//DEPOSIT  DD DSN=Z56117.SOURCE.DEPOSIT,DISP=SHR           
//WITHDRW  DD DSN=Z56117.SOURCE.WITHDRW,DISP=SHR           
//SYSOUT   DD SYSOUT=*     


File status is 48: A WRITE operation has been tried on a file not opened in the OUTPUT, I-O, or EXTEND mode, or on a file
open I-O in the sequential access mode.

file DD name: BALANCE Is used in I-O mode as it reads & writes the account balance.
Back to top
View user's profile Send private message
enrico-sorichetti

Superior Member


Joined: 14 Mar 2007
Posts: 10801
Location: italy

PostPosted: Sun Apr 12, 2020 9:38 pm
Reply with quote

Quote:
Neither FILE STATUS nor a declarative was specified for file BALANCE

fix the error
Back to top
View user's profile Send private message
Nic Clouston

Global Moderator


Joined: 10 May 2007
Posts: 2455
Location: Hampshire, UK

PostPosted: Mon Apr 13, 2020 1:43 am
Reply with quote

Please join this forum: Beginner's
Back to top
View user's profile Send private message
sandeep prajapati

New User


Joined: 23 Mar 2020
Posts: 19
Location: India

PostPosted: Mon Apr 13, 2020 6:53 am
Reply with quote

the issue is resolved.

I introduced a new file for the output, Avoiding opening any file in I-O mode.
adding File status it worked fine.

many thanks, for your time.
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic View Bookmarks
All times are GMT + 6 Hours
Forum Index -> COBOL Programming

 


Similar Topics
Topic Forum Replies
No new posts VB file copy COBOL program gives erro... COBOL Programming 3
No new posts AUTHORIZED database error in HALDB IMS DB/DC 2
No new posts Issue with CA Copycat-IGD17100I UNEXP... CA Products 5
No new posts Getting error S000 U0016 (Cn Internal... JCL & VSAM 4
This topic is locked: you cannot edit posts or make replies. regarding COBOL WRITE verb (VB File H... COBOL Programming 9
Search our Forums:

Back to Top