Andy, The S0C1 with that exact set-up does not "normally" happen in COBOL (by which I mean, by COBOL running in batch).
COBOL programs are not "normally" run under TSO. There is an explicit run-time message which explains the issue. The S0C1 is unexpected. It is some artefact of running that program under TSO. It was easy to miss not through ignoring it because it always happens, but through not hunting for something additional when you hit a message stating the exact cause. Maybe the program even S0C1s once the direct problem is fixed (SYSIN assinged), who knows? It should be raised with IBM if it can be reproduced, and if such reproduction confirms that it is not a user-error. Going back to the original compile-and-go, the go part is redundant if the intention is to run the program under TSO. Cameron needs to sit down with someone, if possible, and go through the process that was attempted. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
