Thanks Attila, but in both our cases the keyboard is definitely in the unlocked state when we are editing / writing code in the ISPF editor, so any difference in response that depends on locked vs unlocked isn't at issue here. It's the differing response to the "same" AID key (Attention) when the keyboard is definitively unlocked that was the question.
The observed difference in behavior is that when I press "Attention" to "reshow" the screen because I accidentally erased a section of code that I didn't mean to do (e.g. with an accidental EraseEOF), it ACTS as if I had pressed PA1 / PA2 and does the "reshow" function. "Attention" for that purpose does not work at my friend's shop. PA1 / PA2 always works as "reshow" for my friend, but "Attention" forces the terminal session into the INACTIVE state and the emulator must be disconnected and reconnected to their system to get back to the TSO / ISPF session. I think Ed Jaffe may have hit on the "network" difference; it is possible that my friend's TN3270E connection is non-SNA vs my very definitely SNA connection. Peter -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Attila Fogarasi Sent: Tuesday, February 19, 2019 9:46 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Where does ISPF determine how to repsond to "Attention" function? Peter, the answer to your PA1 Reshow mystery is simple: this is deliberate behaviour by ISPF which treats PA1 differently when keyboard is locked or unlocked. Pressing PA1 when unlocked (for example editing full screen as in your friend's case) will cause ISPF to treat PA1 as Reshow -- same as PA2. Pressing PA1 a second time will cause ISPF to treat it as ATTN which means interrrupt whatever is currently executing. By contrast if PA1 is pressed when the keyboard is locked (e.g. unlock using the Reset key and then PA1) will always be treated as an ATTN. All this changes if ISPF is invoked from a CLIST with an Attention exit but that is a topic for advanced or masochistic users. So the state of the keyboard locked/unlocked is different in your 2 cases. Lots of configuration options will cause this difference, but it has nothing to do with data streams constructed by the TN3270E emulator. Note that is the keyboard state as observed by ISPF and not necessarily what you see at the keyboard :) -- This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
