Again, you autolog the machine, not the operating system. For example, if a virtual machine named GLORP ipls CMS and is autologged, it is GLORP that is autologged, not CMS. Imagine the confusion that would exist if you autologged the O/S. We have, at almost any given time, some 200 virtual machines that have been autologged. Of these, 3 will be in the GCS group, 100 or more will IPL CMS and the rest will IPL TPF from a virtual device address. It would not be very meaningful, and certainly the intent would not be too clear, if I entered the command "autolog 4000" to bring up a TPF guest. (Which test image? We have over 20 of them. What userid?) It makes no sense to state that "x" must be done when "y" IS AUTOLOGGED and must not be done if "y" is not autologged if "y" is the name of an operating system instead of a virtual machine.
You can autolog a virtual machine that is capable of IPLing any operating system that will run on the bare metal and some that cannot. GCS and CMS fall into the latter category. Regards, Richard Schuh > -----Original Message----- > From: The IBM z/VM Operating System > [mailto:[EMAIL PROTECTED] On Behalf Of Ed Zell > Sent: Tuesday, February 05, 2008 8:46 AM > To: [email protected] > Subject: Re: RSCS question. > > > You autolog a machine, not an operating system. (Hmmm, I have never > > tried to autolog z/OS 1.7; maybe it will work.) > > > I don't know anything about z/OS, but I can autolog a virtual > machine that runs z/VSE and it works just fine. We do it > with our tech support z/VSE system all the time since no one > needs access to the "real console". > > Ed Zell > Illinois Mutual Life > (309) 674-8255 x-107 > . > > > CONFIDENTIALITY: This e-mail (including any attachments) may > contain confidential, proprietary and privileged information, > and unauthorized disclosure or use is prohibited. If you > receive this e-mail in error, notify the sender and delete > this e-mail from your system. >
