On Tue, 12 Jul 2016 00:04:15 -0500, Bill Woodger <[email protected]> wrote:
. . . > >There are no S0C1s from COBOL IO. > For the reason that I explained previously, a missing DD statement can cause S0C1. As far as I am concerned, that should never happen, but I know it is an easy mistake to make in assembly code, where one has to explicitly check that the OPEN worked. Some OPEN errors cause Sx13 abends, but OPEN does not issue an abend for a missing DD. I don't expect the same S0C1 from Cobol, and I pointed out that Cobol obviously does check that OPENs work, because it produced a message saying that the OPEN was unsuccessful. So, if that did not cause the S0C1, what did? I guess I was just wondering if everybody was so conditioned to seeing a missing DD statement cause S0C1 that they no longer question it. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
