Unsuccessful open is not necessarily the end of the world. The application might choose to issue a message and terminate. Or open some other file. Or proceed without file input. It's not wise to forge ahead trying to perform I/O to an unopen file, but nothing systemically prevents you.
In my experience, S0C1 is the most likely consequence, I presume because some location that should contain a valid instruction after open does not. The key to solving this problem is the message 'file-name DD MISSING'. Figure out why that's happening, fix it, and move on. . . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-302-7535 Office robin...@sce.com -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Andy Wood Sent: Monday, July 11, 2016 3:40 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: Error in a simple COBOL program On Mon, 11 Jul 2016 17:19:17 -0500, Bill Woodger <bill.wood...@gmail.com> wrote: >It's a Severe run-time error. Nothing can be done about it (except make the >appropriate correction). Well, possibly you could use an LE abend handler, but >why? > >Plain ACCEPT does not have a SELECT statement, so you can't specify FILE >STATUS. It is not a "file" to the COBOL program, I don't think you can get at >it with DECLARATIVES (I should check). > >I think you meant S0C4, not S0C1. No, I didn't mean S0C4: > CEE3201S The system detected an operation exception (System Completion > Code=0C1 Serve error or not, why confound things with an operation exception? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
