Re: Client Access stays connected

[nina jones <ddi@xxxxxxxxxxxxxxxxx>]

> When any of our users need to reboot their PC because of a Windows lockup or 
>error, their Client Access sessions remain active on the AS/400.  From the 
>As/400 they look like they are still active.  Then, since we name our display 
>sessions to match the PC the person is at, they can't reconnect to the AS/400 
>after reboot because that device is still active and in use. The user just 
>gets a black screen with no indication of the problem.  We have tested this 
>and sometimes the session will remain active for 30 minutes or more.  We 
>usually end of terminating the sessions so the user can reconnect.  Is there 
>some setting somewhere that we can change that would stop this from happenning 
>?


gee, i was hoping someone would answer because we have the same problem,
especially on remote connections when line noise knocks us off.  

what i do is use the generic connection to sign back on (y'know, the
little as/400 on the desktop), end the named sessions, wait about 2
minutes, and then restart my batch file.  not really elegant, but it
does the job.

nj
+---
| 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
+---