[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 <[email protected]> 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 >
