While attempting to build CMS, the following messages were displayed. HCPVSQ429E Punch 000D spool error; file held
HCPLDR8009E ERROR ON PUNCH VMFPAT1965E The command, HCPLDR, failed with return code 8009 when issued with the argument(s): $$$TLL$$ DMSVM (PUNCH VMFBDN1965E The command, $VMFPAT$, failed with a return code 100 when issued with the argument(s): $$$TLL$$ DMSVM XA BLD (PUNCH VMFBLD1851E (1 of 1) VMFBDNUC completed with return code 100. Some objects were not built. The HCPVSQ429E CP message: Explanation: A paging I/O error occurred while CP was reading or writing a file for the specified virtual device. System Action: If it is a printer or a punch spool file error, the virtual machine receives a unit check condition to stop the write operation. CP then places the file in system HOLD and makes the virtual device not ready. User Response: Issue the READY command to the virtual device and retry the output operation. Operator Response: The error is probably due to a hardware malfunction. There are no problem indicator lights lit on the DS6800. Any attempt to spool resulted in a message which indicated a hardware problem. I noticed it when I tried to build CMS. Cecelia Dusha WHS/ITMD/AEFDD 703-697-2305 ICE Comment Card -----Original Message----- From: Alan Altmark [mailto:[EMAIL PROTECTED] Sent: Thursday, December 08, 2005 1:20 PM To: [email protected] Subject: Re: DS6800 & zVM 5.1 On Thursday, 12/08/2005 at 04:04 GMT, "Dusha, Cecelia, Ms., WHS/ITMD" <[EMAIL PROTECTED]> wrote: > I have no idea why the intermittent problems are occurring. Nor do I have > any idea how to begin to tackle it given I am constrained by not having a > software maintenance contract. Please help. (I have a very short window to > get this system into production...) You say that the IPL CLEAR fails, but you don't supply the error indication. I suggeset you run EREP and look at the report to see if the dasd needs repair. Alan Altmark z/VM Development IBM Endicott
