I don't care for serialization, but wish to lock the keyboard until the end of the rexx execution. I know doing this with TSO macros, but just checking if Rexx can do this as well. If the keyboard is locked, the user can't enter debug mode (msg
ITschak On Wed, Oct 24, 2012 at 3:55 PM, Gerhard Postpischil <[email protected]>wrote: > On 10/24/2012 8:01 AM, Itschak Mugzach wrote: > >> We have a rexx exec that performs functionality we don't want to be >> interrupted or traced in any way. this mean that we need to disable the >> functions keys that might return control to the user, such as the >> Attention, PA1, PA2 keys. We play to write a small program that will call >> the TSO macros STATTN and STTMPMD to disable CLEAR, ATTENTION and PA1 >> keys. >> > > If you want to prevent interruptions, the stand way is to issue an ENQ > with the (authorized) System Must Complete (SMC) option. That also affects > other tasks running on the system. If you only wish to lock out the user, > than TSO services may suffice. > > I know of no way to prevent tracing. > > > Any alternatives that can be performed in the REXX exec itself? Will the >> assembler program disable the keys for the entire session? >> > > Not in REXX that I know of, and the effect may or may not last, depending > on what programs are invoked - in much of my code, I set keys explicitly. > If you really wish to control user interaction, the next best thing might > be to keep your code resident, and attach user commands, rather than > returning to TSO. At an extreme, you could write your own Terminal Monitor > Program? > > Gerhard Postpischil > Bradford, VT > > ------------------------------**------------------------------**---------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
