No and no. TSO does not support concurrent execution of tasks. When an unauthorized task calls an authorized command, the TMP doesn't let the unauthorized task continue until the authorized task completes.
The default for attention is to allow the terminal user to decide what to do, e.g., TEST. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> on behalf of Steve Smith <sasd...@gmail.com> Sent: Monday, May 20, 2019 1:32 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: PL/I TSO Interrupt - Attention handling - SLIP trap X33E / X13E 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
