sage-
From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On
Behalf Of Neale Ferguson
Sent: Friday, November 14, 2008 11:00 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: Verify from z/VM that a Linux guest is up
Q SYSOPER - you'll probably find that the user MAINT became the system
operat
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: R
ation."
-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 9:56 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: Verify from z/VM that a Linux guest is up
Hi
I am revisiting this
h 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
Q SYSOPER - you'll probably find that the user MAINT became the system
operator as the normal one got logged off somehow and MAINT was the 1st
CLASS A user to logon to the system. VM grants this user the mantle of
system operator.
Use SET SYSOPER to rectify.
On 11/14/08 10:56 AM, "Martin, Terry
t; 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
yden
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
On Sat, Nov 8, 2008 at 1:25 AM, Alan Altmark <[EMAIL PROTECTED]> wrote:
> "Timebomb". Diag 0x288. Give it a command and an interval. If you fail
> to re-issue the diag within the interval, CP will issue the command.
Be aware of the resource usage and scalability of your application. In
this ca
On Friday, 11/07/2008 at 05:55 EST, Kris Buelens <[EMAIL PROTECTED]>
wrote:
> Or, also exploit the "deadman" diagnose feature that came with one of
the more
> recent z/VM releases. This diagnose tells CP that the virtual machine
must do
> something (maybe re-issue the diagnose, I just don't r
>
>> *From:* The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] *On
>> Behalf Of *Scott Rohling
>> *Sent:* Friday, November 07, 2008 10:55 AM
>> *To:* IBMVM@LISTSERV.UARK.EDU
>> *Subject:* Re: Verify from z/VM that a Linux guest is up
>>
>>
>>
>
--
>
> *From:* The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] *On
> Behalf Of *Scott Rohling
> *Sent:* Friday, November 07, 2008 10:55 AM
> *To:* IBMVM@LISTSERV.UARK.EDU
> *Subject:* Re: Verify from z/VM that a Linux guest is up
>
>
>
>
410 786-0386
[EMAIL PROTECTED]
From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On
Behalf Of Scott Rohling
Sent: Friday, November 07, 2008 10:55 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: Verify from z/VM that a Linux guest is up
Well - somewher
(CTR)
Sent: Friday, November 07, 2008 10:14 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Verify from z/VM that a Linux guest is up
Hi
I have written some REXX (with help from this list) to shutdown and my z/Linux
guests and I also have an EXEC to XAUTOLOG them when I am ready to bring them
back u
Huegel, Thomas wrote:
I don't know much about LINUX, but if it has a TCP/IP stack running,
how about just a simple PING from a CMS to the LINUX?
Ping doesn't prove that it's ready for multiple interactive logins. The
IP stack comes up before everything
is running.
--
Jack J. Woehr
:* IBMVM@LISTSERV.UARK.EDU
> *Subject:* Re: Verify from z/VM that a Linux guest is up
>
> 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)...
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 ma
IBMVM@LISTSERV.UARK.EDU
Subject: Re: Verify from z/VM that a Linux guest is up
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
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
When I need to XAUTOLOG an SVM (linux is just another SVM) and watch its
console, I use the AUTOSCIF exec from the SCIF package at the IBM DOWNLOA
DS
website. This xautologs the svm and sets me as the SECUSER (secondary
console user) so that I can see the messages and enter commands if necess
ary.
Hi
I have written some REXX (with help from this list) to shutdown and my
z/Linux guests and I also have an EXEC to XAUTOLOG them when I am ready
to bring them back up. I would like to know if there is a way from z/VM
to check something in the Linux guest to confirm that in fact the guest
is u
20 matches
Mail list logo
