On 5/21/19, Seymour J Metz <[email protected]> wrote:
> What happens if you hit enter after the READY prompt?

I get another READY prompt.

>
> Was the keyboard unlocked when you hit PA1?

The keyboard is  locked after the program starts (either with CALL or
 TEST/GO).

I am unlocking it to be able to send ATT or  PA1

Mike

>
>
> --
> Shmuel (Seymour J.) Metz
> http://mason.gmu.edu/~smetz3
>
> ________________________________________
> From: IBM Mainframe Discussion List <[email protected]> on behalf of
> Mike Stramba <[email protected]>
> Sent: Tuesday, May 21, 2019 2:11 PM
> To: [email protected]
> Subject: Re: PL/I TSO Interrupt - Attention handling - SLIP trap X33E /
> X13E
>
> Also tried these variants :
>
> CALL 'MYLOGIN.LOAD(PLINT)' 'TRAP(ON)/123456789012'
> CALL 'MYLOGIN.LOAD(PLITSO)' 'TRAP(ON)/123456789012'
> CALL 'MYLOGIN.LOAD(PLIMVS)' 'TRAP(ON)/123456789012'
>
> Same results ( ATTENTION  kills program back to TSO READY,  PA1 no effect)
>
> Mike
>
> On 5/21/19, Mike Stramba <[email protected]> wrote:
>> Ok I have tried running the program from the TSO ready prompt.
>>
>> CALL (LOAD(PLIxxx)
>>
>> I have compiled three versions :
>>
>> Enterprise PL/I for z/OS       V5.R2.M4 (Built:20190424)
>>  z/OS 02.03.00
>>
>> 1)  SYSTEM(TSO)   option    (+  INTERRUPT
>> 2) SYSTEM(MVS)    option   (+  INTERRUPT
>> 3)  no  "SYSTEM(XXX) option ( INTERRUPT
>>
>> Pressing "T. Brennan Vista " ATTENTION   (SH-ESC  mapped),  just
>> "kills" all versions.
>>
>> pressing PA1 has no effect.
>>
>> Mike
>>
>> On 5/21/19, Seymour J Metz <[email protected]> wrote:
>>> 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 <[email protected]> on behalf
>>> of
>>> Lennie Dymoke-Bradshaw <[email protected]>
>>> Sent: Tuesday, May 21, 2019 12:02 PM
>>> To: [email protected]
>>> 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:            [email protected]
>>> 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 <[email protected]> On Behalf
>>> Of
>>> Seymour J Metz
>>> Sent: 20 May 2019 21:17
>>> To: [email protected]
>>> 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 <[email protected]> on behalf
>>> of
>>> Mike Stramba <[email protected]>
>>> Sent: Monday, May 20, 2019 12:37 AM
>>> To: [email protected]
>>> 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 [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
>>>
>>> ----------------------------------------------------------------------
>>> 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
>>>
>>
>
> ----------------------------------------------------------------------
> 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
>

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to