Thank you for responding.
No spool files were found on the FORCE start. I think I selected that out of habit verses reason... Our production system has only a few spool files, the delay to check the spool area does not have a large impact. Although I have been informed that is not the best approach to take after a normal shutdown for starting the system. The production system here does not have many spool files. I greatly appreciate everyone's help. Panic took over for a little while... Thank you. Cecelia Dusha WHS/ITMD/AEFDD 703-697-2305 _____ From: Mike Walter [mailto:[EMAIL PROTECTED] Sent: Monday, December 12, 2005 1:09 PM To: [email protected] Subject: Re: DS6800 & zVM 5.1 Cecelia, It appears that you may uncertain of the differences between WARM, FORCE, COLD, and CLEAN system starts. While you are waiting for the support contract to be "awarded" you might want to check out "Chapter 3. Bringing up the System" (in particular: "Selecting the Type of Start You Want to Perform") in the "z/VM System Operation" manual (SC24-6121-00). See: http://publibz.boulder.ibm.com/epubs/pdf/hcsf2b00.pdf Q: After your FORCE start (which could have been OK if you had just formatted/allocated all the SPOL areas), were there any old files on SPOOL? If so, that would b an indicator that you have SPOL areas somewhere else. A COLD or CLEAN start would not have yielded any better results that FORCE since you have just formatted and allocate all the SPOL space. Did you get any errors while restoring the SDFs or other SPOOL files? You should not need to format the CKPT or WARM areas (which would result in all SPOOL files being lost). Not should the DRCT cylinders need to be formatted (which would require a DIRECTXA, or External Security Manager of your choice, command to re-write the Object Directory from the source file(s) to the DRCT cylinders). T-disk space is formatted when CP comes up, and when it is detached (depending on your SYSTEM CONFIG file). If you want to getter a better "warm fuzzy" feeling for the new SPOL areas, you could write a REXX EXEC to start filling SPOOL up until it had completely, or almost filled all up (obviously, depending on your tolerance for a full SPOOL area, and not when lots of users are logged on), then purge the file(s). Mike Walter Hewitt Associates The opinions expressed herein are mine alone, not my employer's. "VM/ESA and z/VM Discussions" <[email protected]> wrote on 12/12/2005 03:40:52 AM: > Brian: Thank you. Your presence is missed. > > The spool problem reoccurred as I was dumping the NSSs this morning. I > CPFMTXAed the 510SPL and 510PAGE volumes. (I did allocate PERM space to > cylinder 0 on both volumes.) I then shutdown, IPLed the system and loaded > the NSSs. (I just noticed your message said to COLD start... I did a FORCE > start...) I won't know immediately if this corrected the problem. I > suspect it will for the spool and page areas. There are other system > defined space on the volumes such as $DIRECT$, $SYSCKP$, $SYSWRM$, $TDISK$ > that are defined. $TDISK$ should not be a problem, but what about the > others areas? $SYSCKP$ and $SYSWRM$ probably could be CPFMTXAed easily > enough, but directory space would be more difficult... I don't need to > worry about the areas that are used for CMS type data if the CPFMTXA of the > spool and page areas corrected the spool problems? > > FLASHCOPY problem (I tried various combinations with no success.): > Ready; T=0.01/0.01 01:27:30 > link $dasd$ 1000 100 rr > DASD 0100 LINKED R/O; R/W BY MAINT > Ready; T=0.01/0.01 01:27:44 > att 2000 * 200 > DASD 2000 ATTACHED TO MAINT 0200 WITH DEVCTL > Ready; T=0.01/0.01 01:27:57 > flashcopy 100 000 end 200 000 end > HCPNFC332E Invalid control unit type - 100 > Ready(00332); T=0.01/0.01 01:28:44 > > link $dasd$ 1000 1000 rr > DASD 1000 LINKED R/O; R/W BY MAINT > Ready; T=0.01/0.01 01:29:48 > att 2000 * 2000 > DASD 2000 ATTACHED TO MAINT 2000 WITH DEVCTL > Ready; T=0.01/0.01 01:29:58 > flashcopy 1000 000 end to 2000 000 end > HCPNFC332E Invalid control unit type - 1000 > Ready(00332); T=0.01/0.01 01:30:16 > > q v 123 > DASD 0123 3390 510RES R/W 3339 CYL ON DASD 1000 SUBCHANNEL = 000B > Ready; T=0.01/0.01 01:31:28 > q v 2000 > DASD 2000 ON DASD 2000 R/W FREE SUBCHANNEL = 004B > Ready; T=0.01/0.01 01:31:38 > flashcopy 123 000 end to 2000 000 end > HCPNFC332E Invalid control unit type - 123 > Ready(00332); T=0.01/0.01 01:32:01 > > The intermittent problem with the IPL of the guest occurred several times in > a row before a successful IPL for the guest. > > IPL 100 > HCPGIR450W CP entered; disabled wait PSW 00020000 00000000 00000000 > 00001010 > Q V 100 > DASD 0100 3390 310RES R/W 3339 CYL ON DASD 1005 SUBCHANNEL = 001A > > HCPGIR450W > User Response: To interpret the wait state code in > the PSW, refer to the section on wait states of the corresponding manual for > the system you were running in your virtual machine. Take the specified > corrective action, then re-IPL the virtual system again. > > I had run DSF followed by a CPFMTXA on these volumes prior to restoring them > from the HIDRO backup. But at the time I had not yet applied the 1750 PSP > bucket... I had recently applied maintenance for HIDRO. I will check to > make sure that maintenance included support for the 1750. > > Thank you. > > Cecelia Dusha > WHS/ITMD/AEFDD > 703-697-2305 > > -----Original Message----- > From: Brian Nielsen [mailto:[EMAIL PROTECTED] > Sent: Friday, December 09, 2005 2:46 PM > To: [email protected]; Dusha, Cecelia, Ms., WHS/ITMD > Subject: Re: DS6800 & zVM 5.1 > > Cecelia, > > Sorry I'm coming into this late. > > Link to the DASD as a differnent virtual device address. Virtual address > 001 is on the same virtual controller as your virtual console (009), > reader (00C),and punch (00D). Pick a virtual address not on this same > virtual controller. If you use something like 100 that will be on a > completely different virtual channel and so will be safe. If you stay on > virtual channel Zero I'd have to look up the range for that virtual > controller (it's probably 16 or 32). > > As for your spool space, I don't have access to an Installation Guide at > the moment, so I can't give you any page references. I know you're doing > this 1st level, so I'll tailor to that environment. > > There should have been a step where you formatted the volumes used for > PAGE and SPOOL space. I don't know what was on the restore from DVD as > far as the PAGE and SPOOL volumes is concerned, but I'd bet money that's > where the source of the problem lies. > > In any case, since this is a clean install one easy thing to do is SPXTAPE > your NSS's and such (unless you just want to rebuild them), shutdown CP & > reformat your SPOOL volume (I'd probably do PAGE as well) with standalone > ICKDSF, then IPL with a COLD start and reload anything you saved via > SPXTAPE. > > If you're not up to standalone ICKDSF, use CPFMTXA while the system is up > to prepare new volumes as SPOOL & PAGE. I'd use the same volids as the > existing ones, relabel the existing ones to something else, then shutdown > and IPL COLD. (If you don't like using the same volids then use different > ones and make the necessary edits in SYSTEM CONFIG before you shutdown.) > > Wish I could have been there to help out! > > Brian Nielsen (Cecelia's former colleague) > > > On Fri, 9 Dec 2005 16:55:17 -0000, Dusha, Cecelia, Ms., WHS/ITMD > <[EMAIL PROTECTED]> wrote: > > >When I try to use the CP FLASHCOPY command I get an error message that > >indicates the control unit does not support this function. The DS6800 has > >the correct license because I can invoke the DSCLI commands for flashcopy > on > >the SMC... > > > >Any ideas what the problem could be? > > > >(I have tried using the website http://www.ibm.com/support/us/ for > research, > >but the elements that support VM do not appear to be up. Also I have > tried > >to access the website for the VM listserv to see if similar problems have > >already been reported, but no luck in accessing that website. Although I > >can see activity on the listserv from the emails discussing problems...) > > > >link $dasd$ 1000 1 rr > >DASD 0001 LINKED R/O; R/W BY MAINT > >Ready; T=0.01/0.01 06:33:25 > >att 2000 * 2 > >DASD 2000 ATTACHED TO MAINT 0002 WITH DEVCTL > >Ready; T=0.01/0.01 06:33:35 > >flashcopy 1 000 end 2 000 end > >HCPNFC332E Invalid control unit type - 1 > >Ready(00332); T=0.01/0.01 06:33:57 > > > >The HCPNFC332E message: > >HCP332E Invalid control unit type - <rdev|vdev> > > > >Explanation: The device is attached to a control unit that is not valid > for > > > >the entered command. The control unit does not support this function. > > > >System Action: The command is not executed. > > > >Operator Response: Enter the command again specifying the device number > of > >a device that is attached to a valid control unit. > > > >Note: The SET CACHE command cannot be entered for a 3880 Model 11 or 21. > > > > > >The $DASD$ userid: > >USER $DASD$ NOLOG > >* ------ zVM 5.1 Volumes ------------------------ > > MDISK 1000 3390 000 END 510RES MR xxxxxxxx xxxxxxxx xxxxxxxx > > > >Within the IOCP the DS6800 is defined as: > >FICON CHPID PATH=(10),PCHID=110,TYPE=FC,SHARED > > CHPID PATH=(11),PCHID=111,TYPE=FC,SHARED > > CHPID PATH=(12),PCHID=112,TYPE=FC,SHARED > > CHPID PATH=(13),PCHID=113,TYPE=FC,SHARED > >FICON CHPID PATH=(14),PCHID=140,TYPE=FC,SHARED > > CHPID PATH=(15),PCHID=141,TYPE=FC,SHARED > > CHPID PATH=(16),PCHID=142,TYPE=FC,SHARED > > CHPID PATH=(17),PCHID=143,TYPE=FC,SHARED > >DASD CNTLUNIT CUNUMBR=100,PATH=(10,14,15,11),UNITADD=((00,256)), X > > CUADD=0,UNIT=1750 > > IODEVICE ADDRESS=(1000,256),UNIT=3390,CUNUMBR=100,PATH=10, X > > STADET=Y,PART=VM1 > >DASD CNTLUNIT CUNUMBR=200,PATH=(10,14,15,11),UNITADD=((00,256)), X > > CUADD=8,UNIT=1750 > > IODEVICE ADDRESS=(2000,256),UNIT=3390,CUNUMBR=200,PATH=10, X > > STADET=Y,PART=(VM1,IFL) > > > >Thank you. > > > >Cecelia Dusha > >WHS/ITMD/AEFDD > >703-697-2305 > >========================================================================= > The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited.
