No, it's not a "good call". I do have the INTERRUPT option enabled.
At least that's what the compiler listing says. What code does the INTERRUPT option generate ? Mike On 5/20/19, Steve Smith <sasd...@gmail.com> wrote: > Good call... the INTERRUPT option is the likely culprit (the O.P. can say > for sure). Now maybe someone could explain why such an option exists. > Would you like an 'EOF' option to specify whether EOF should be detected? > > TSO is a very-multi-tasked environment. Each command is ATTACHed as a > subtask, and the default for attention is to mercilessly DETACH it (which > is essentially CANCEL for a task). Except for the exceptions, of course. > > sas > > > On Mon, May 20, 2019 at 11:03 AM Joe Monk <joemon...@gmail.com> wrote: > >> If youre trying to run under TSO, did you compile with the INTERRUPT >> option? >> >> Joe > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
