|
The trick is to use a Signon subsystem.
You create a signon subsystem and everyone logs in through that subsystem.
That subsystem has a routing entry that sends you to a program that
determines if the system is in a restricted state. If yes, you look to see
if that user is authorized to be on. If not, you throw a screen and say the
system not available and shut them down. I have some examples programs if
you interested.
Here is an article that talks about the process in a slightly different
way.
http://www.itjungle.com/mpo/mpo031303-story03.html
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
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-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.