Thanks for the note.  I did check for hardware failures, but nothing is
on the HMC.  

________________________________

From: The IBM z/VM Operating System [mailto:[email protected]] On
Behalf Of Mrohs, Ray
Sent: Monday, September 21, 2009 2:51 PM
To: [email protected]
Subject: Re: z/VM Stopped Responding


The real ultimate solution would have been to do a restart dump so that
IBM could take a look at what was last happening on your system.
Hopefully your OPERATOR id has its console output spooled to someplace.
Type Q R OPERATOR or Q P OPERATOR. If you don't have VM:Spool, you need
to get those spool file(s) 'owned' by your userid via the TRANSFER
command. Then either PEEK the spool file, or RECEIVE the whole file to
your A disk. There is online help for all these commands. If you have an
external security manager, you would also want to look at those spool
files in a similar manner, since those facilities can sometimes bring
the OS to its knees. 
 
The hardware console should save any system abend codes if they are
generated. 
 
Did you check for hardware failure?
 
Ray Mrohs
US DOJ     
 
________________________________

From: The IBM z/VM Operating System [mailto:[email protected]] On
Behalf Of Kreiter, Chuck
Sent: Monday, September 21, 2009 2:24 PM
To: [email protected]
Subject: z/VM Stopped Responding


Last week, while I was out of the office, we had our first unplanned
z/VM outage.  
 
We are running z/VM 5.3 with about 20 guests.  Symptoms were that a user
tried to access a Linux guest to do a production code move around 10:00
PM.  He was unable to get in.  Then, the operators received lightening
bolt messages and nothing on z/VM or any of the Linux systems were
available.  
 
The ultimate resolution was to re-IPL.  All was fine afterwards.  
 
My dilemma is that I'm not accustomed to debugging z/VM. I'd really like
to look at the system logs for that time to see if there are any
messages.  I know that can be done, but for the life of me can not find
any procedures to do it.  
 
Any help would be greatly appreciated.
 
Thanks, 
 

Chuck Kreiter 
State Auto Insurance 

 

Reply via email to