Ah, yes, I've never seen a (real) COBOL program run under TSO with user interaction either.
On the other hand I've seen many batch programs with CONSOLE interaction (for better or worse!). As for your other question, no I would not be keen on using labels, PERFORM...THRU (or SECTION!!), and GO TO statements for those code structures; which is why I am so pleased that I can use EXIT PERFORM instead! Frank ________________________________ From: IBM Mainframe Discussion List <[email protected]> on behalf of Bill Woodger <[email protected]> Sent: Monday, July 11, 2016 4:25 PM To: [email protected] Subject: Error in a simple COBOL program Yes, sorry, Frank, I meant "not with interaction". I've never run a COBOL program under TSO, so never attempted to "interact" with it (on the Mainframe). I have seen some VS and VSE programs which communicated with the Operator (I've even seen one go into a loop, but it is not difficult to CANCEL), but never seen that allowed (for mere programmers) from MVS onwards. The reason for the explicit priming-read paragraph is that usually/often there is stuff to do on the first read which is irrelevant for subsequent ones. It's late here, so I'll have a look at your code tomorrow. For now, would you be as keen on the code structures if those were plain GO TOs (given that you'd have to have THRU and extra labels, but...)? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
