: VMSERVS and RMSMASTR
To: IBMVM@LISTSERV.UARK.EDU
We first shutdown RMSMASTR before we attempt the shutdown of
SFS
servers. Indeed, when it is running the SFS can't shutdown.
I had seen
this for VMSERVU, I guessed this is because it has an open
file in the
filepool.
Cortes
Sent: Wednesday, March 25, 2009 3:49 PM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: VMSERVS and RMSMASTR
I wanted to point out that if IBM is going to ship stuff that enables
iself to shutdown nicely, it shouldn't also be shipping a component that
prevents that out of the box
Careful, though to set the timeout somewhat higher for VSE virtual
machines to allow the shutdown process to complete.
When the shutdown timer expires z/VM will blast the VSE system. That
will definitely leave a mark.
Berry van Sleeuwen wrote:
VSE does, to some extent. When you SIGNAL a
An observation...
VMSERVS registers himself for signal shutdowns and shuts himself down
nicely
UNLESS
You also use RMSMASTR to support your ATLs and VTSs.
Then it never gets shutdown nicely and you wait the full shutdown
timeout value... Sigh...
Seems like RMSMASTR should be registering
We first shutdown RMSMASTR before we attempt the shutdown of SFS
servers. Indeed, when it is running the SFS can't shutdown. I had seen
this for VMSERVU, I guessed this is because it has an open file in the
filepool.
I can think of some other CMS services that could do very well with a
signal
On 3/25/09 4:06 PM, Berry van Sleeuwen berry.vansleeu...@xs4all.nl
wrote:
I can think of some other CMS services that could do very well with a
signal shutdown. Er, DIRMAINT, MONWRITE (or all recording services for
that matter), PERFKIT just to name a few. It would make shutting down VM
a
David Boyes wrote:
There is an open requirement for this via WAVV, but I don't know what the
status is.
-- db
The previous WAVV requirements and statuses are here:
http://www.wavv.org/wavv_requirements_old.shtml
The only ones that I see submitted over the past 5 years are for the
I can think of some other CMS services that could do very well with a
signal shutdown. Er, DIRMAINT, MONWRITE (or all recording services
for
that matter), PERFKIT just to name a few. It would make shutting down
VM a lot easier: SIGNAL SHUTDOWN ALL WITHIN 30; SLEEP 30 SEC;
SHUTDOWN
There is
Subject: Re: VMSERVS and RMSMASTR
I can think of some other CMS services that could do very well with a
signal shutdown. Er, DIRMAINT, MONWRITE (or all recording services
for
that matter), PERFKIT just to name a few. It would make shutting down
VM a lot easier: SIGNAL SHUTDOWN ALL WITHIN 30
On 3/25/09 4:30 PM, Ed Zell ewz...@illinoismutual.com wrote:
There is an open requirement for this via WAVV, but I don't know what
the status is.
I found a couple of requirements for SIGNAL SHUTDOWN for
TCPIP (RETURNED) and RSCS (REJECTED) from 2007. I couldn't find
any others though
] On
Behalf Of Huegel, Thomas
Sent: Wednesday, March 25, 2009 1:34 PM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: [IBMVM] VMSERVS and RMSMASTR
We went through this a while back .. SHUTTRAP .. on the VM download page
will enable signal in a CMS machine.
-Original Message-
From: The IBM z/VM Operating
LINUX enables shutdown, I beleive I heard that VSE was going to soon too.
-Original Message-
From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu]on
Behalf Of Marcy Cortes
Sent: Wednesday, March 25, 2009 3:49 PM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: VMSERVS and RMSMASTR
12 matches
Mail list logo
