|
If you wanted to control what a user can do with the SysRQ key, just modify this message description: CPX2313 Kenneth **************************************** Kenneth E. Graap IBM Certified Specialist AS/400e Professional System Administrator NW Natural (Gas Services) keg@nwnatural.com Phone: 503-226-4211 x5537 FAX: 603-849-0591 **************************************** -----Original Message----- From: Ed Fishel [mailto:edfishel@us.ibm.com] Sent: Tuesday, February 05, 2002 10:41 AM To: midrange-l@midrange.com Subject: Re: Programmatically disable SysReq key Fiona, >How about excluding *PUBLIC from cmd TFRSECJOB ? >Is the overhead the same ? The amount of overhead for the presystem request exit program depends on the program. Most programmers should be able to write an efficient presystem request exit program that will not be noticed when it is called. Likewise, the authority check of the TFRSECJOB command is not something users will notice. You would have to press the system request key a very large number of times before you would notice any difference between these two solutions. A question that should be asked is what is the difference between these two solutions. It has been pointed out that the a presystem request exit program can keep an *ALLOBJ user from using the system request menu. This is true, but it will not prevent them from using TFRSECJOB the next time they see a command line. So, if the objective is to keep any user from using the system request key during a critical part of the application, then a presystem request exit program is a good solution. On the other hand, if the objective is to always keep someone from using TFRSECJOB, then you should remove their authority to that command. Ed Fishel, edfishel@US.IBM.COM _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l or email: MIDRANGE-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.