|
some of us are just graphically challenged. Al Al Barsa, Jr. Barsa Consulting Group, LLC 400>390 914-251-1234 914-251-9406 fax http://www.barsaconsulting.com http://www.taatool.com bdietz@3x.com Sent by: To: midrange-l@midrange.com midrange-l-admin@mi cc: drange.com Subject: Re: Programmatically disable SysReq key 02/02/02 11:54 AM Please respond to midrange-l I went right to the search and searched for " exit program presystem request " and found--> http://publib.boulder.ibm.com/pubs/html/as400/v5r1/ic2924/info/apis/xsysreq.htm Time 3 minutes (dialup from customer site during upgrade) ------------------------- Bryan Dietz 3X Corporation barsa@barsaconsult ing.com To: midrange-l@midrange.com Sent by: cc: midrange-l-admin@m Subject: Re: Programmatically disable SysReq key idrange.com 02/02/2002 11:22 AM Please respond to midrange-l Hi Bruce, Bruce, what is the name of the API? I spend over a half hour in the misinformation center (yes on the Internet for currency), and couldn't find it What are the advantages of using this (other than burning CPU cycles, which is good for IBM), as opposed to revoking the public authority the panel group QGYMNSYSR. Will it preclude access to a user with *ALLOBJ authority? Al Al Barsa, Jr. Barsa Consulting Group, LLC 400>390 914-251-1234 914-251-9406 fax http://www.barsaconsulting.com http://www.taatool.com bvining@vnet.ibm.co m To: MIDRANGE-L@midrange.com Sent by: cc: midrange-l-admin@mi Subject: Programmatically disable SysReq key drange.com 02/01/02 01:50 PM Please respond to midrange-l You may want to consider using the Presystem Request Program Exit Program (documented in the Work Management category of System APIs). This exit allows a user program(s) to get control when SysReq is used and alter the normal handling of SysReq. Bruce > >Good morning, sirs. Is it possible to programmaticaly disable SysReq key ? >This is to avoid object locking during critical operations. >Sincerely > _______________________________________________ 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. _______________________________________________ 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. _______________________________________________ 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.
midrange.com
