Hi, Richard.

Sorry to hear about your long evening, had some like that myself.

I've got a little routine here, written by Chris Langford, that can read (and *write*, too) VM spool files. Drop me a note off list if you think that it might be able to help you recover from this error.

Have a good one.

DJ
Schuh, Richard wrote:
Thanks, Jim. I had already found those. We will have to research them
when the day has not been so long :-) The one mentioning a corrupted
save area might also lead to other corrupted thingies - like SDFs and
Spool files. And page packs. I just finished draining a page pack that
was taking hits and added a replacement to the system. There went the
evening - it is now 10:30 PM local time...
________________________________

From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On
Behalf Of Stracka, James (GTI)
Sent: Friday, December 08, 2006 5:21 PM
To: [email protected]
Subject: Re: MCW002 Abend


There are three APARs for 5.2.0 that reference this type of abend:
VM63827, ,PER, ,ABENDMCW002 IN INSTRUCTION SIMULATION
VM63840, ,PER, ,ABENDMCW002 HCPFMVSM REPEATEDLY CALLING HCPHTFRF
VM63990, ,PER, ,PTE SERIALIZATION LEFT ON DUE TO CORRUPTED SAVEAREA

-----Original Message-----
From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED]
Behalf Of Schuh, Richard
Sent: Friday, December 08, 2006 7:00 PM
To: [email protected]
Subject: MCW002 Abend



        We just had our IFL LPAR VM crash with the code MCW002. It
appears that there was something wrong with SPOOL at the time so we did
not get a dump. In addition, the console log from the time of the crash
cannot be opened. I have no data to document the problem.

        A. Does anyone have or know of a tool that might allow me to
read the last few blocks of the hosed spool file? B. Is this problem familiar to anyone running multiple penguins
in an LPAR? I have a feeling that it is somehow related to a huge (38G)
Linux guest being readied for a contest with a Solaris box of equal size
(but having 15 cpus vs. 5 IFLs). Regards, Richard Schuh
________________________________

If you are not an intended recipient of this e-mail, please notify the
sender, delete it and do not read, act upon, print, disclose, copy,
retain or redistribute it. Click here <http://www.ml.com/email_terms/>
for important additional terms relating to this e-mail.
http://www.ml.com/email_terms/
________________________________


Reply via email to