Don't forget that a disconnected user that issues a VM READ will also be forced after the same wait. The idea is that a disconnected user can not respond to the read, regardless of the source.
All bets (forces) are off if the user has a SECUSER. Regards, Richard Schuh > -----Original Message----- > From: VM/ESA and z/VM Discussions [mailto:[EMAIL PROTECTED] > Behalf Of Alan Altmark > Sent: Monday, November 14, 2005 7:18 AM > To: [email protected] > Subject: Re: Users disconnected and forced by the system > > > On Monday, 11/14/2005 at 06:38 PST, william JANULIN > <[EMAIL PROTECTED]> wrote: > > > 14:49:29 GRAF L000D DISCONNECT JOHMA06 USERS = 65 > > FORCED BY SYSTEM > > > > user JOHMA06 was forced into a disconnected state. > > > > 15:04:29 USER DSC LOGOFF AS JOHMA06 USERS = 62 > > FORCED BY SYSTEM > > > > 15 minutes later the user gets logged off. > > > > Is 15 minutes the criteria in both cases and is there > > one parameter in System Config that controls both > > situations? > > The forced disconnect is an immediate response to, for > example, someone > shutting down their TN3270 client without logging off first. > With a local > 3270, it is the result of an I/O error on the terminal (e.g. > test/normal > switch). More generally, the terminal session ended without > CP's prior > consent. If this results in the user entering CP READ, the > user is forced > after 15 minutes (configurable). > > Alan Altmark > z/VM Development > IBM Endicott >
