> 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. Correcting the problem between the terminal and the chair is probably cheaper... and much more entertaining for the system staff...8-)
