Well it's listed there:
Signalled Timeout
Userid Signal Signal Status By Remaining
HOBBITVM SHUTDOWN Enabled - -
VMSERVA SHUTDOWN Enabled - -
VMSERVU SHUTDOWN Enabled - -
VMSERVS SHUTDOWN Enabled - -
VMSERVR SHUTDOWN Enabled - -
Frank M. Ramaekers Jr.
Systems Programmer
MCP, MCP+I, MCSE & RHCE
American Income Life Insurance Co.
Phone: (254)761-6649
1200 Wooded Acres Dr.
Fax: (254)741-5777
Waco, Texas 76701
________________________________
From: The IBM z/VM Operating System [mailto:[email protected]] On
Behalf Of Kris Buelens
Sent: Monday, October 26, 2009 7:53 AM
To: [email protected]
Subject: Re: HCPSHU6018I explaination
HELP HCPSHU6018I displays:
HCP6018I The processor controller has sent a shutdown signal with a
timeout
interval of duration seconds
Explanation: A hardware image deactivation has caused the processor
controller to signal the VM system to shut down. VM has the interval
shown in
which to complete its shutdown process.
System Action: System termination commences.
In my eyes, it means that someone instructed LPAR to deactivate the VM
partition, hence the HMC was probably used to give this instruction.
Why your extra SFS pool didn't respond? I don't know, normally nothin,g
is required to make it listen. Issue
CP Q SIGNALS
and all your SFS servers should be listed.
Maybe your extra SFS server didn't terminate quickly enough. You
message says SFS gets 66 seconds to terminate, maybe this SFS takes a
backup at end and that takes more than 66 seconds; maybe there was an
open LUW of some service machine and SFS wanted to give it time to
complete. Q FILEPOOL AGENT can tell you which LUWs are open.
2009/10/26 Frank M. Ramaekers <[email protected]>
I have a couple of questions, but first a description of the incident.
We had the system z/VM 5.4 "go into a disabled wait" (not my words).
Looking at the OPERATOR's console log:
09/10/25 00:00:00 : HCPMID6001I TIME IS 00:00:00 CDT
SUNDAY 10/25/09
09/10/25 00:09:26 : 00:09:26 HCPSHU6018I THE PROCESSOR
CONTROLLER HAS SENT A SHUTDOWN SIGNAL WITH A TIMEOUT
09/10/25 00:09:26 INTERVAL OF 66 SECONDS
09/10/25 00:09:26 : 00:09:26 HCPSIG2113I USER HOBBITVM
HAS REPORTED SUCCESSFUL TERMINATION
09/10/25 00:09:26 : 00:09:26 HCPSIG2113I USER VMSERVS
HAS REPORTED SUCCESSFUL TERMINATION
09/10/25 00:09:26 : 00:09:26 HCPSIG2113I USER VMSERVR
HAS REPORTED SUCCESSFUL TERMINATION
09/10/25 00:09:26 : 00:09:26 HCPSIG2113I USER VMSERVU
HAS REPORTED SUCCESSFUL TERMINATION
09/10/25 00:10:02 : 00:10:02 PROCESSOR 01 OFFLINE
09/10/25 01:51:25 PROP MKMFVM : PROP running with routing table
PROP RTABLE A1
I can't tell what caused the system to shutdown, specifically what
caused the HCPSHU6018I. (Or what is the "processor controller"?)
From the HMC:
Date: Oct 25, 2009
Time: 1:10:01 AM
Partition VM and central processor (CP) 1 are in a disabled wait state.
The disabled wait program status word (PSW) is
00020000000000000000000000009003.
Central storage bytes 0-7 are: 7ffff10f7ffff10f7ffff10f7ffff10f.
The next question relates to the above. There are 4 HCOSIG2113I. I
have added, since installation, an additional SFS server, yet it's not
showing up on this list. Was there something special I should have done
so that this file pool will terminate in cases like this?
Frank M. Ramaekers Jr.
Systems Programmer MCP, MCP+I, MCSE & RHCE
American Income Life Insurance Co. Phone: (254)761-6649
1200 Wooded Acres Dr. Fax: (254)741-5777
Waco, Texas 76710
_____________________________________________________ This message
contains information which is privileged and confidential and is solely
for the use of the intended recipient. If you are not the intended
recipient, be aware that any review, disclosure, copying, distribution,
or use of the contents of this message is strictly prohibited. If you
have received this in error, please destroy it immediately and notify us
at [email protected].
--
Kris Buelens,
IBM Belgium, VM customer support
_____________________________________________________
This message contains information which is privileged and confidential and is
solely for the use of the
intended recipient. If you are not the intended recipient, be aware that any
review, disclosure,
copying, distribution, or use of the contents of this message is strictly
prohibited. If you have
received this in error, please destroy it immediately and notify us at
[email protected].
