I wonder what we're doing differently. I just tried this with my test server several times, and it disconnected properly each time, leaving the guest running.
When I logged back ON though, the session went to CP READ and the server was partly locked up until I satisfied the read. > -----Original Message----- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of > James Melin > Sent: Thursday, June 29, 2006 1:26 PM > To: [email protected] > Subject: Re: [LINUX-390] Unexpectedly closing VM console breaks Linux > server under z/VM > > > We ran into that here. SET RUN ON is specified in the profile > exec for all of the Linux guests, but if the 3270 session for > that guest (we would use > 3270 to manually IPL - otherwise xautolog is the choice) is > terminated (computer crashes, or someone closes the 3270 > program) without a #CP DISC the > session would go into a state other than disconnected and VM > would treat it as a 'dangling' session and kill it after a > period of time. This is > primarily aimed at situations where several hundred VM users > could be logged on and any number of them would leave a > session dangling and lock up the > resources for that user. It has dramatic and usually bad > consequences for ID's that are running guest operating > systems in the VM environment. > > The bottom line: DO NOT leave a 3270 session representing the > console of a Linux Guest just sitting someplace. Any variety > of scenarios can lead to a > 3270 session going into an abnormal state and VM will > diligently clean those up. Use #CP DISC when you're done if > you MUST access things by 3270. > Otherwise telnet/SSH is your better option for guest interaction. > > > > > "Post, Mark K" <[EMAIL PROTECTED]> > Sent by: Linux on 390 Port > <[email protected]> > > To > > [email protected] > > > cc > 06/29/2006 12:01 PM > > > Subject > > Re: Unexpectedly closing VM console breaks Linux > server under z/VM > Please respond to > Linux on 390 Port <[email protected]> > > > > > > > > > Since you say you have "set run on" I admit to being puzzled. I would > have expected that to work for you. Perhaps someone from the VM > development team can say whether dropped connections are handled > differently from CP disconnects or not. > > > Mark Post > > -----Original Message----- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of > Jack Hoarau > Sent: Thursday, June 29, 2006 11:24 AM > To: [email protected] > Subject: Unexpectedly closing VM console breaks Linux server > under z/VM > > -snip- > CP Q SET shows RUN set to ON but it > seems this is not to sufficient, am I missing some other important > function > settings of the guest ? > > Jack HOARAU > -------------------------------------------------------- If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. http://www.ml.com/email_terms/ -------------------------------------------------------- ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
