: The IBM z/VM Operating System
[mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of Alan Altmark
Sent: Monday, July 04, 2011 8:18 PM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: SHUTTRAP
On Monday, 07/04/2011 at 09:12 EDT, David Boyes
dbo...@sinenomine.net
wrote:
SA22-7832-08, pg. 11-16, in the section
On Monday, 07/04/2011 at 09:12 EDT, David Boyes dbo...@sinenomine.net
wrote:
SA22-7832-08, pg. 11-16, in the section on Warnings. There's about two
sentences referring to power failure. The rest is in the SHUTTRAP source
code.
I said it was tiny. 8-).
Indeed, and vague, too
the
conditions.
The exec that is run when SHUTTRAP catches a shutdown signal
starts its work by signaling PROP to turn off reloging.
Only after that does it start bringing down the various machines it is
responsible to stop.
If I were to cancel the SHUTDOWN, I would have to re-enable RELOGing
On Wednesday, 06/29/2011 at 10:11 EDT, Shimon Lebowitz shim...@iname.com
wrote:
If I were to cancel the SHUTDOWN, I would have to re-enable RELOGing,
but to date I have not built in such a function. I have also never
cancelled
a SHUTDOWN, so if it ever happens, I will need to do the enable
I just retrieved SHUTTRAP from the download page and tried it. In my first
simpleminded try, the results were mixed. The signal shutdown did indeed
trigger the command included with the shuttrap command. Then I got this:
SHUTTRAP: Shutdown in 900 seconds
DMSITP143T Addressing exception occurred
Richard,
I don't see that on my 5.4 system.
Here is how I start it.
/* */
say 'loading SHUTTRAP as a CMS nucleaus extension'
'nucxload shuttrap (system'
say 'enabling SGNLSHUT exec to process shutdown signal'
shuttrap exec sgnlshut
exit
And the sgnlshut exec.
/* exec to perform some functions
Hello Richard,
I believe the reason for your error message in using SHUTTRAP is that SHUTTRAP
can only issue CMS commands and not CP commands. Is the message associated with
your SHUTTRAP issuing a CP command? I had the same problem when my message was
a CP command. As a test for SHUTTAP I
My RxKernel has ShutTrap support. RxServer uses WAKEUP (EXT to catch the
interrupt. No abends then.
And, to complete handling a shutdown signal, one is supposed to load an FFF
wait state, not to LOGOFF. My first attempt was to end with a LOGOFF. But
then our automation saw the server go
Thanks Kris, that is not obvious, but it makes sense..
On Tue, Jun 28, 2011 at 11:07 AM, Kris Buelens kris.buel...@gmail.comwrote:
My RxKernel has ShutTrap support. RxServer uses WAKEUP (EXT to catch the
interrupt. No abends then.
And, to complete handling a shutdown signal, one
@LISTSERV.UARK.EDU
*Subject:* Re: SHUTTRAP
Thanks Kris, that is not obvious, but it makes sense..
On Tue, Jun 28, 2011 at 11:07 AM, Kris Buelens kris.buel...@gmail.comwrote:
My RxKernel has ShutTrap support. RxServer uses WAKEUP (EXT to catch the
interrupt. No abends then.
And, to complete
@LISTSERV.UARK.EDU] On Behalf
Of Kris Buelens
Sent: Tuesday, June 28, 2011 1:05 PM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: SHUTTRAP
That code is what CP will load when its shutdown is complete. So, not related
to signal shutdown's wait code. I don't remember where I found the code to
load, my guess
On Tuesday, 06/28/2011 at 03:10 EDT, Schuh, Richard rsc...@visa.com
wrote:
No only is it not obvious, so far I have been unable to find it in the
documentation. You can specify a wait state code on the SHUTDOWN command
and
it can be anything between 1 and . I cannot find where the
@LISTSERV.UARK.EDU] On Behalf Of Alan Altmark
Sent: Tuesday, June 28, 2011 1:56 PM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: SHUTTRAP
On Tuesday, 06/28/2011 at 03:10 EDT, Schuh, Richard
rsc...@visa.com
wrote:
No only is it not obvious, so far I have been unable to find it in
the documentation. You can
Phone: (508) 249-4076
Ext: 44076
-Original Message-
From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf
Of Schuh, Richard
Sent: Tuesday, June 28, 2011 6:22 PM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: SHUTTRAP
Given the lack of direction, I suppose that you can do
: The IBM z/VM Operating System
[mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of Raymond Noal
Sent: Tuesday, June 28, 2011 3:38 PM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: SHUTTRAP
Richard,
You can use the CP command - 'Q SIGNALS' to make your
determinations, as in -
q signals
On Tuesday, 06/28/2011 at 07:35 EDT, Schuh, Richard rsc...@visa.com
wrote:
Close, but I am not willing to grant you a cigar. If all, or even most,
have
the same Signalled by id, then either a signal shutdown all was done
or a
program did multiple signal shutdown user userid commands in
You will not find any published information on the mechanism.
There is a tiny amount of information in the POP manual in the external
interrupt section on the original LPAR deactivation signal and what's supposed
to happen when it triggers, but the end comment is that the effect will be
On Tuesday, 06/28/2011 at 10:06 EDT, David Boyes dbo...@sinenomine.net
wrote:
You will not find any published information on the mechanism.
There is a tiny amount of information in the POP manual in the external
interrupt section on the original LPAR deactivation signal and what's
I've been reading and testing:
- I get WAKEUP's RC 6 too, but when calling WAKEUP again, it directly
exist with RC 1. So, the SHUTTRAP signal triggers 2 WAKEUP events: COSN
SMSG. Removing the CONS option doesn't do anything.
- SHUTTRAP does not work like ADDRESS CMS, (so an eventual
, DRCT, TDISK) and
optionally on SFS server allocations.
/Tom Kern
/301-903-2211
Kris Buelens wrote:
I've been reading and testing:
* I get WAKEUP's RC 6 too, but when calling WAKEUP again, it
directly exist with RC 1. So, the SHUTTRAP signal triggers 2
WAKEUP events: COSN
with RC 1. So, the SHUTTRAP signal triggers 2
WAKEUP events: COSN SMSG. Removing the CONS option
doesn't do
anything.
* SHUTTRAP does not work like ADDRESS CMS, (so an eventual CP
EXEC
wouldn't matter)
* Diverting the SMSG delivery
On Fri, 9 Nov 2007 10:15:36 -0600, Thomas Kern [EMAIL PROTECTED]
wrote:
Now I have to clean it up just a bit more. Which brings up the next
tangent
on this discussion. When I signal a linux SVM to shutdown, CP reports th
at
the linux SVM has signalled its termination. When I am logged onto a
Logging off seems like a pretty good signal. :-) You can put any CP
command you want in the VMPOFF, so you could use MSG or SMSG to send a
signal back to a shutdown SVM, which could wait until all guests have
reported in before it issues the real CP SHUTDOWN.
Brian Nielsen
On Fri, 9 Nov
A CLASS G linux guest only needs to signal CP that ITS own shutdown
processing has been completed and apparently the x0FFF in the PSW does th
at.
An SVM or Operator or Sysprog that issued the SIGNAL SHUTDOWN command wil
l
get the HCPSIG2113I message when the target SVM has completed its shutdow
n
On Fri, 9 Nov 2007 10:15:36 -0600, Thomas Kern [EMAIL PROTECTED]
wrote:
Is this PSW code (x0FFF) the
indicator to CP that SHUTDOWN has completed? If it is, how can I nicely
load
the same indicator when my SVM has completed its shutdown processing?
Sorry, I mis-read your question the first
3, 2006 12:59 PM
To: VSE Discussion List
Subject: Re: ? SHUTTRAP ?
According to the documentation, there are two things to consider:
1) IUCV ALLOW ANY *SIGNAL in the VM directory
2) CP SET SIGNAL to determine shutdown delay.
That is all I have found so far.
Ken Meyer
CSI
Ron
26 matches
Mail list logo
