RE: Off topic question on Client/Server. My appologies.

take a look at telnet exit programs.  They should be able to do what you
want.

Christopher K. Bipes     mailto:ChrisB@Cross-Check.com
Sr. Programmer/Analyst   mailto:Chris_Bipes@Yahoo.com
CrossCheck, Inc.         http://www.cross-check.com
6119 State Farm Drive    Phone: 707 586-0551 x 1102
Rohnert Park CA  94928 Fax: 707 586-1884

If consistency is the hobgoblin of little minds, only geniuses work here.
Karen Herbelin - Readers Digest 3/2000


-----Original Message-----
From: MacWheel99@aol.com [mailto:MacWheel99@aol.com]
Sent: Tuesday, May 02, 2000 1:35 PM
To: MIDRANGE-L@midrange.com
Subject: Re: Off topic question on Client/Server. My appologies.


from Al Macintyre

I want this feature also ... on 5350 emulation & when external Ethernet 
connected to AS/400 & when people dial in via PC Anywhere or consultants via

ECS line.  The As/400 is available 99.99% of the time but we need to 
temporarily disconnect people for backups, updates, various software package

related tasks & depending on where we are in different duties on different 
nites & fiscal schedules, there is a need for something between the MIS EOM 
etc. personnel & the other people using PCs on the network.

We have PC users across a spectrum from power user to PC novice & really do 
not want to have to be giving system training to beginners ... the network 
should tell the user that the network is down & do so in a user-friendly 
fashion, in which it is clear what the problem is.

PC User tries to start their AS/400 session & either gets a blank screen 
because we have shut down the connection, or they manage to get in & cause 
some problem with the job that needs dedicated access to some files, before 
they even see the message that we do not want them here.  

It would be wonderful if the PC users had a "front end" to the AS/400
sign-on 
screen that they never saw when  AS/400 access is allowed, but when MIS or 
EOM personnel need a dedicated system, they could designate which PC
sessions 
are authorized to be connected for the duration & which are to be locked
out, 
then when the dedicated tasks are completed MIS or EOM takes an option to 
restart everyone.  The act of "going dedicated" would give us a text screen 
for an explanation of the current scenario in which we include an estimate
of 
how long we will be.  

Then when the PC user clicks on AS/400 session they get Blighty's vision 
combined with the text screen that was filled in by whoever asked for 
"restricted state."

In the absense of this, we use techniques that are totally inadequate.
We phone people via voice mail & leave memos on their desks.
We fill up DSPMSG with text regarding PLEASE that over time gets ignored.
We ask PC ANYWHERE users to first sign on as QSYSOPR or QSECOFR & check
their 
messages to see if anyone doing anything that might be in conflict with what

they had in mind.
We vary off comm lines, controllers, sessions, ethernetwork.
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---