Execute: CP QUERY SYSOPER Does it say MAINT is the system operator? That means that OPERATOR got logged off somehow. The next CLASS A user to logon becomes the system operator when this happens. Just log off MAINT and log OPERATOR back on (and if he's already on log off/on to re-establish him as SYSOPER).
-Mike -----Original Message----- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Martin, Terry R. (CMS/CTR) (CTR) Sent: Friday, November 14, 2008 10:56 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Verify from z/VM that a Linux guest is up Hi I am revisiting this now and I am having some trouble that someone might be able to help me with. From my test z/Linux host I am issuing: vmcp msg operator I am up But this message keeps going to MAINT userid instead of OPERATOR which is where the command is telling it to go. Am I missing something? Thank You, Terry Martin Lockheed Martin - Information Technology z/OS & z/VM Systems - Performance and Tuning Cell - 443 632-4191 Work - 410 786-0386 [EMAIL PROTECTED] -----Original Message----- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Bruce Hayden Sent: Friday, November 07, 2008 11:52 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Verify from z/VM that a Linux guest is up I hope that would be 'vmcp msg operator I am up and running' and not a warning message. Sending a warning requires CP class A, B, or C and I hope nobody gives a Linux machine those privileges! Terry, it sounds like you may want to look at a some system automation software such as VM Operations manager or a similar product. On Fri, Nov 7, 2008 at 10:55 AM, Scott Rohling <[EMAIL PROTECTED]> wrote: > Well - somewhere in /etc/rc3.d you could put a script that issues 'vmcp wng > operator I am up and running!' (or wng to whatever userid will be bringing > them up and watching)... hopefully, vmcp is loaded at that point.. > > Other than capturing console messages, there is no way to know that Linux is > up and running unless you get Linux to tell you it is.. > > I suppose one more way would be to telnet (on VM) to the Linux ip address > using port 22 -- until you get a response .. but not sure how I'd code that > without playing with it more. > > Scott Rohling -- Bruce Hayden Linux on System z Advanced Technical Support IBM, Endicott, NY