|
On Tue, 18 September 2001, Terry Herrin wrote: > barsa@barsaconsulting.com wrote: > >I would caution that the code to determine that you are truly in a > >restricted state is tricky. > > There may be a "gotcha" to my method, but I monitor the QSYSOPR > message queue for the "System has ended to a restricted state" > message. Once I receive that message, which I leave on the message > queue, then I proceed with the save. I've seen a couple of comments referring to "restricted state is tricky", but never any useful background info to support it. (Nor can I refute it.) Interactively, the QSYSOPR message has worked for me as far back as I can remember. Programmatically, I prefer the Retrieve System Status (QWCRSSTS) API, format SSTS0200. The 'Restricted state flag' field returns '1' when in restricted state, '0' otherwise. Pretty simple. Tom Liotta -- Tom Liotta The PowerTech Group, Inc. 19426 68th Avenue South Kent, WA 98032 Phone 253-872-7788 Fax 253-872-7904 http://www.400Security.com ___________________________________________________ The ALL NEW CS2000 from CompuServe Better! Faster! More Powerful! 250 FREE hours! Sign-on Now! http://www.compuserve.com/trycsrv/cs2000/webmail/
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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
