On: Mon, Apr 14, 2008 at 12:13:15PM -0400,David Boyes Wrote: } > Not really. We had a user logon to a z/Linux guest and hit <PA1> } > instead of <PA2> and left it sit there too long. I wanted to prevent } > hitting <PA1> putting it into CP READ. OPTION CONCEAL might be a too } > powerful hammer. } } Sounds like it. OPTION CONCEAL was really designed for CMS machines that } were supposed to be running captive applications dealing primarily with } R/O data or IUCV connections to a server to perform operations on data } (kind of an early stab at kiosks). Any attempt to break out of the app } was supposed to trigger an instant restart with storage clear of the } virtual machine so that you kept the user in the padded box. Not what } you really want to happen to a (potentially) multiuser guest OS with } cached data in memory. } } I think Rich is probably right -- SET RUN ON is in general probably what } you want. If someone hits PA1, then I'm not sure there's any way to } intercept that w/o doing something really ugly to the system as a whole.
Thanks Dave. AFAIK, the only way for Linux (or whatever is running in that V.M.) to catch a PA1 is to be running the console as a 3270 and catch the interrupt and get the AID. } Correcting the problem between the terminal and the chair is probably } cheaper... and much more entertaining for the system staff...8-) Yup, the old PEBKAC problem. :-) -- Rich Greenberg N Ft Myers, FL, USA richgr atsign panix.com + 1 239 543 1353 Eastern time. N6LRT I speak for myself & my dogs only. VM'er since CP-67 Canines:Val, Red, Shasta & Casey (RIP), Red & Zero, Siberians Owner:Chinook-L Retired at the beach Asst Owner:Sibernet-L
