I think my memory is running out now ☹. The experience I had with this was several decades ago. I know that I had a TSO command processor (CP) with STAX protection around a particular piece of code. However, when running under a CLIST I found that the CLIST attention facility gained control instead of getting control passed to the STAX routine in the program.
Maybe the behaviour has since changed. Lennie Dymoke-Bradshaw | Security Lead | RSM Partners Ltd Web: www.rsmpartners.com ‘Dance like no one is watching. Encrypt like everyone is.’ -----Original Message----- From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of Seymour J Metz Sent: 21 May 2019 21:41 To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: [IBM-MAIN] PL/I TSO Interrupt - Attention handling - SLIP trap X33E / X13E There is a queue for each task, but more than one task can issue STAX. The exit for a subtask get control before the exit for the parent task. Are you thinking of CLSTATTN (sp?) and TOPLEVEL? -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> on behalf of Lennie Dymoke-Bradshaw <lenni...@rsmpartners.com> Sent: Tuesday, May 21, 2019 2:11 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: PL/I TSO Interrupt - Attention handling - SLIP trap X33E / X13E Yes I did mean at the READY prompt. I think that STAX acts at the TCB level. The CLIST will be running on different TCB from any program that it invokes, as each command is invoked using an ATTACH macro. I have seen situations where the CLIST flushes the stack after the interrupt and so the TCB running the program or command is wiped out. I think there are parameters that are needed on the CLIST to protect against this I think. Lennie Dymoke-Bradshaw | Security Lead | RSM Partners Ltd Web: http://secure-web.cisco.com/1I2vgDyDq8crO7fF_Z1a6IDTn6qUZVMPJaFCBAgQytvoOMcN22fc106zIRsjze0QGpC7KMNNGEc7i2yeUG6mAvDZ1ha0YFNn69j-59BhOaiRRbzEQUnAq0Y6_-cwb0DLcR9j8ysUl4jpFiFCzGwIq7P_-eIe5YcwbTePo0cxgLDvokTJ6raAb4W_w7XYxV-D_WgG2mWnnBzEzrotzP9pHAJZ1XTwAQy9FDA7lGTqgFYfw_kfByeF24ve4LBSqEg66JNEbPmuYyJLjCMyvy0mvr4JG2iApjhCBQgdnY5wrDMbCnFooHtfddit1f95zsBDnz0qj9ShN50usZvYkF5qyLFaXEQwiVgTyZthOpKr5l8SZIm6i9fjaVgGLylCUUmu9UhhWV1ZXpGrIZvjb7ot1TysYlVxOXOlTMzYqB8-SNNk/http%3A%2F%2Fwww.rsmpartners.com 'Dance like no one is watching. Encrypt like everyone is.' -----Original Message----- From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of Seymour J Metz Sent: 21 May 2019 17:27 To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: [IBM-MAIN] PL/I TSO Interrupt - Attention handling - SLIP trap X33E / X13E By "native TSO" do you mean the READY prompt? The CLIST processor uses STAX; the override rules are the same as for any other user of STAX. REXX doesn't support attention handling code, but the REXX interpreter does do a STAX and writes a prompt for attention. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> on behalf of Lennie Dymoke-Bradshaw <lenni...@rsmpartners.com> Sent: Tuesday, May 21, 2019 12:02 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: PL/I TSO Interrupt - Attention handling - SLIP trap X33E / X13E You may get different results when running the program in a CLIST as opposed to running it from native TSO. I don't know what other mysteries REXX brings to the table. CLIST processing has ATTN handling, which (from memory) overrides the use of STAX (assembler TSO interrupt handling macro) from within a program. Lennie Dymoke-Bradshaw | Security Lead | RSM Partners Ltd Email: lenni...@rsmpartners.com Web: http://secure-web.cisco.com/1TP7I7bSJ0ibf2dNo3OyTavPh2FXX8KRFSQDk_7sE8ZUtm9-4NfLDadbpNKsXBSwz0hAIF-vGCHbAmhy3jV0wlj9aGRnQw_8EXDpKu7PCLUrGH-Av80gDpRRj4n-xvHNwBOsSKtS09VQh0otEj-GRfej4ivoGKUyf5pLSpPAxbvjkkvTMI8QHeLEstSYbZuytlUBX-1BNqNhXDXs-7ER0u__qEMhUc4b4Ai0FZOPg1r5G4ZpXmVv5Sf_6z_u98MyPbTGqDIm4gbhmgER6qulcl8QumK6HAJZuZ9FX8F9IX5mNuC5_f_40FguhQfCbi7kkpGGLRjnFEccpGZZCLTtdrT-w8B1F0iw9VtwaWZgwMPRxgYb-OlmRi9TLn6DEE3SdpkvkRlFmohV9fTdT9ZdFEqHaMlLC8pgCE3xH8S6q_rtPKPQxhCaELhg2v2WvGK0U/http%3A%2F%2Fwww.rsmpartners.com 'Dance like no one is watching. Encrypt like everyone is.' -----Original Message----- From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of Seymour J Metz Sent: 20 May 2019 21:17 To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: [IBM-MAIN] PL/I TSO Interrupt - Attention handling - SLIP trap X33E / X13E I'd say that the first step is to run a trace and find out what your terminal simulator is actually sending when you click on ATTENTION. Ideally, it will be the aid for PA1, exactly one time, but life is full of surprises. Does your ATTENTION key work as expected with other applications? -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> on behalf of Mike Stramba <mikestra...@gmail.com> Sent: Monday, May 20, 2019 12:37 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: PL/I TSO Interrupt - Attention handling - SLIP trap X33E / X13E I'm trying to compile and run the PL/I ON ATTENTION interrupt example from the PLI prog guide ver 4 r4 (pg 542 / GI11-9145-03) The code contains an ON ATTENTION handler with a simple message and prompt : and the main line is a simple endless loop. The goal was just to write an extremely primitive counter-tester, which the user can interrupt after X seconds to see what counting-performance had been achieved. When I run the program and then press my 3270 emulator attention key, the program just ends instead of the attention handler gaining control. The console log shows a SLIP TRAP X33E and X13E were matched. MVS system codes SA38-0665-30 says for 33E : "During processing of a DETACH macro that specified a STAE=YES operand, the system found that the specified subtask had not completed processing" code 13E is : "The task that created a subtask issued a DETACH macro for that subtask, specifying STAE=NO before the subtask ended. I ASSume the "subtask" is my test program ?? And the "task" is TSO ?? Or maybe not :/ How do I just get the ON ATTENTION handler to work ? Mike ---------------------------------------------------------------------- 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 ---------------------------------------------------------------------- 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 ---------------------------------------------------------------------- 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 ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
