And with SHARE coming up soon, that requirement could get relayed to IBM fairly quickly. HINT! HINT!
Mark Post -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Alan Altmark Sent: Friday, June 30, 2006 10:29 AM To: [email protected] Subject: Re: Unexpectedly closing VM console breaks Linux server under z/VM -snip- IMO, a console disconnect (user-initiated or I/O error) should have no effect on RUNNING/CP READ state. It should simply be the equivalent of FORCE DISC. If it was running, leave it running. If was in CP READ, leave it there. Forever. The usual cadre of performance/idle monitors can decide (based on policy with exceptions) whether the user is "wasting" resource. If I Ran The Zoo, I would introduce new user event records and operator messages that indicate a disconnected virtual machine just entered VM READ or CP READ so as to make it more straightforward for system automation tools to act. If I ran the zoo. And if we had user requirements to change the behavior. :-) Alan Altmark z/VM Development IBM Endicott ---------------------------------------------------------------------- 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
