Sorry to disagree: on all 3270 implementations I used (apart this OSA ICC) it was and is possible to interrupt a fullscreen appl like XEDIT. I debugged too many XEDIT macros not to be 101% sure of this. (and a few hours ago I did it again on a PCOMM "TN3270 telnetted" into VM TCPIP. In PCOMM, by default the ESC key is set to [sys attn], pressing it brings you from your locked XEDIT directly in CP READ, then press PA1 and you have a VM READ to enter TS).
This unlock problem may make me switch back from OSA ICC to plain TN3270. (it is less frequent I have to restart VM's TCPIP stack than I want to breakin in a runaway XEDIT macro. 2010/3/31 Michael Coffin <michaelcof...@mccci.com> > When you have a fullscreen app (like XEDIT, or DMS, ISPF, etc.) doing a > full-screen write to the 3270, I don’t think there is any way to interrupt > it to get to CMS. > > > > A couple of “tricks” would include sending a CP MSG from any other userid > (or even a terminal with no user logged on, CP MSG is CLASS * by default), > that interrupts the full-screen write and you can get to CMS for HX, HI, TI, > TS, or any other CMS-IMMEDIATE command. Another trick is to do a LOGON HERE > from another terminal, when you reconnect you may have an opportunity to > stuff in a CMS-IMMEDIATE command before the full-screen write resumes. > > > > -Mike > > > > *From:* The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] *On > Behalf Of *Kris Buelens > *Sent:* Wednesday, March 31, 2010 7:25 AM > *To:* IBMVM@LISTSERV.UARK.EDU > *Subject:* Re: Interrupting a looping exec on OSA ICC > > > > Sorry, not related to HOLD at LOGOFF for example (to CP it appears as a > real 3270, hence no HOLD operand). > > It is pure 3270 behaviour, not even really related to VM: how can one break > in when in "input inhibited" > > I am in fullscreen XEDIT, hence the linemode command input area is not > available. Cannot use Alan's trick. > > <subject deviation> > Alan's trick is to create another VM READ than the "program prompt VM > READ", you use it when a for example REXX exec places you in VM READ with a > PARSE PULL (or PARSE EXTERNAL) and you want to enter an immediate CMS > command (like HX, HI or TS). With the cursor trick, the "program prompt VM > READ" becomes a VM READ by CMS' attention interrupt handler. > > Maybe easier to remember: when in the program prompt VM READ and you want > to enter an immediate command like TS, enter #TS (that is: place a linend > character before the immediate command). Not exactly the same as moving the > cursor, With my alternative: the program prompt is satisfied with a null > response and then the immediate command is honored. Wit the cursor trick, > the immediate command is honored, then you return to the program prompt. > </subject deviation> > > My issue remains: how can one reset "Input inhibited" on an OSA ICC 3270? > > 2010/3/31 Richard Troth <vmcow...@gmail.com> > > [oooooopppsss - try again] > > > ICC also doesn't support NOHOLD for DISCONN and LOGOFF like some other > > "real 3270s" and like LDEV. That's a whole nutha discussion. > > But ... does PCOMM not have an immediate PA1? (I'm not used to an > ATTN sequence for PA1.) You wouldn't get the trace, but you'd get > control. > > There's also the trick, I think I learned from Alan Altmark, of > putting the cursor back one position from the start of the command > line then <Enter> for a VM READ. It's a hack. (IMHO) Your 3270 > emulator may affect the viability of this behaviour. You MIGHT then > be able to TS. Alan? Wanna clarify this? > > -- R; <>< > > > > > > > On Wed, Mar 31, 2010 at 05:39, Kris Buelens <kris.buel...@gmail.com> > wrote: > > I think I found a bug in the behaviour of an OSA ICC: > > > > Experienced CMS programmers know that to start tracing a looping XEDIT > macro > > can be done by entering a TS command in the command area. But, first one > > needs to get the commandline. A bit difficult as the 3270 is in "input > > inhibited" (a green led on real 3277's, an X with the clock icon in the > > status area nowadays) and the display is in fullscreen mode. > > > > To get the command line, what is required depends on the terminal type > > - a real non-SNA 3270: press the reset key (the stop input Inhibited) and > > press enter, or PA1, .. > > - in SNA: press the ATTN key then enter, or PA1, ... > > - TN3270 with PCOMM: press ATTN > > > > Today, on my PCOMM connected to an OSA ICC on a z10, I found no means to > > break in (apart from "Communication" -> "Disconnect" or using some other > > userid to send a CP Message/Warning to the user in trouble). An OSA ICC > is > > supposed to simulate a non-SNA 3270, it does it well, except for this > > problem. > > > > Any comments? Is it working on your system? > > > > -- > > Kris Buelens, > > IBM Belgium, VM customer support > > > > > > > -- > Kris Buelens, > IBM Belgium, VM customer support > -- Kris Buelens, IBM Belgium, VM customer support
