Thank you. Cecelia Dusha -----Original Message----- From: Romanowski, John (OFT) [mailto:[EMAIL PROTECTED] Sent: Friday, May 05, 2006 1:38 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: zVM 5.1 Res Volume
You said you DDR-ed the old 510RES to the new 510RES and reworked cyl 0 of the new 510RES; and you're running now using the old 510RES. So you can fix the new 510RES's cyl 0 from the VM system that's still running off the old 510RES, no need to IPL the new 510RES first with the NODIRECT option and try to fix it (easier to do it that way on a guest). First, To avoid issues of old 510RES's contents having diverged from new 510RES's, repeat your steps that DDR-ed the old to new 510RES, , CPFMTXA, etc. Then on MAINT, Get your latest CP directory in source file format as file USER DIRECT A (on userid VMXSYSAD do VMXBKP01 NOTAPE to create file USER DIRECT) The DIRECTORY statement in USER DIRECT says DIRECTORY nnnn ... ATTACH the new 510RES to MAINT at virtual addr nnnn Response from CP Q V nnnn should then say: DASD nnnn ON DASD zzzz R/W 510RES ... Then fix new 510RES's active-directory pointer in cyl 0 DIRECTXA USER DIRECT A (TEST DIRECTXA USER DIRECT A Will update the new 510RES object directory (DRCT area) and fix its cyl 0 active-directory pointer. You could also do this more safely from a class G userid to which you attach zzzz as nnnn and give the USER DIRECT A file. Then shutdown VM and re-ipl using the new fixed 510RES. VMSECURE's 191 file DIRECT STATEMNT, still has the old 510RES device address, nnnn, in it. You'll want to fix that file to change nnnn to zzzz. Alternative: don't ddr entire old 510RES to new, just run the DIRECTXA steps to fix new 510RES cyl 0 and rewrite DRCT cyls; use a guest to test that new 510RES IPL's and finds valid directory. Shutdown VM, use stand-alone DDR to copy new 510RES cyl 0 to old, and new 510RES DRCT cyls to old 510RES, re-IPL old 510RES -----Original Message----- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Dusha, Cecelia Ms. WHS/ITMD Sent: Friday, May 05, 2006 11:45 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: zVM 5.1 Res Volume When it started to report the problem with the directory, I shutdown the system and IPLed with the original volume. I will IPL with the new volume and check to see if I can do a DIRECTXA with the user direct file. (We are using VM:Secure for directory management and as the ESM.) Thank you. Cecelia Dusha -----Original Message----- From: Romanowski, John (OFT) [mailto:[EMAIL PROTECTED] Sent: Friday, May 05, 2006 11:10 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: zVM 5.1 Res Volume The problem may have originated with the VTOC IBM shipped on cyl 0 of the VM5.1 System DDR of 510RES. It says 3340 cyls. CP doesn't care, it knows the pack is 3339 cyls. You CMS ACCESS-ed the device and CMS's Q DISK reported that the VTOC says the size is 3340 cyls. This 510RES VTOC bit me when our MVS folks ran a MVS tool to migrate our VM dasd to a DS8000 storage box; their dasd migration tool compared the VTOC size info against the actual pack size and quit if they didn't match. All of our VM5.1 systems had this VTOC discrepancy on 510RES and the tool wouldn't migrate them until I fixed cyl 0. Anyway, as Dave Kreuter pointed out, when you re-formatted cyl 0 you trashed the active-directory pointer. Hopefully you're in a position to run DIRECTXA with the source directory file and update that cyl 0 pointer. -------------------------------------------------------- This e-mail, including any attachments, may be confidential, privileged or otherwise legally protected. It is intended only for the addressee. If you received this e-mail in error or from someone who was not authorized to send it to you, do not disseminate, copy or otherwise use this e-mail or its attachments. Please notify the sender immediately by reply e-mail and delete the e-mail from your system. -----Original Message----- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Dusha, Cecelia Ms. WHS/ITMD Sent: Friday, May 05, 2006 10:19 AM To: IBMVM@LISTSERV.UARK.EDU Subject: zVM 5.1 Res Volume I am experiencing a strange problem with my zVM 5.1 res volumes. The zVM 5.1 res volume is on a 3390 mod 3 pack. This volume should be 3339 cylinders. It is on DASD carved from a DS6800 as 3339 cylinders. When I attach this volume and access it, I get the following: LABEL VDEV M STAT CYL TYPE BLKSZ FILES BLKS USED-(%) BLKS LEFT BLK TOTAL 510RES 001 Z R/W 3340 3390 OS I have tried the following: DDR to a new volume CPFMTXA FORMAT cylinder 0 CPFMTXA ALLOCATE system areas DRCT 1-20 PARM 21-38 PARM 39-128 PARM 129-188 SALIPL for the IPL data When this new volume (same name) is IPLed it says the directory is invalid... Any ideas as to what I should try next to get the res volume to see itself as a 3339 cylinder volume? Thank you. Cecelia Dusha
