While SET RUN ON is a good idea for a server running under VM, it would not have prevented the forced logoff in your case. Adding the "Disconnect_timeout Off" statement to your SYSTEM CONFIG will prevent it, after you reIPL VM. Your problem was because the server's console was connected to a real terminal, and then that connection was broken but a CP DISC command wasn't entered. That makes your virtual machine go into a CP READ state without a terminal and then 15 minutes later, the default "disconnect timeout" period ends and you are forced by the system.
On Tue, Jan 12, 2010 at 9:53 AM, Frank M. Ramaekers <framaek...@ailife.com>wrote: > Guess, I’ll have to include it (“SET RUN ON”) in my $0JCL startup. > > > > Frank M. Ramaekers Jr. > > > > Systems Programmer > > MCP, MCP+I, MCSE & RHCE > > American Income Life Insurance Co. > > Phone: (254)761-6649 > > 1200 Wooded Acres Dr. > > Fax: (254)741-5777 > > Waco, Texas 76701 > > > > > _____________________________________________________ This message > contains information which is privileged and confidential and is solely for > the use of the intended recipient. If you are not the intended recipient, be > aware that any review, disclosure, copying, distribution, or use of the > contents of this message is strictly prohibited. If you have received this > in error, please destroy it immediately and notify us at > privacy...@ailife.com. > -- Bruce Hayden Linux on System z Advanced Technical Support IBM, Endicott, NY
