Anne,
I don't think you want to copy PAGE or SPOOL volumes if it's not a straight DDR to the same type and size device -- when the VM system is down.
PAGE is easy. Just run CPFMTXA on the new volumes (be sure to both FORMAT **all** the cylinders you'll be using for page, and ALLOC all of those pages as PAGE). The recommendations for paging on a production system has long been to dedicate whole volumes for PAGE (same for SPOOL), because any other use of the volume interrupts the "seldom-ending channel program" to those volumes. Performance degrades quickly if that channel program is interrupted for other I/O's.
For SPOOL, similarly FORMAT the whole volume (any CP-dedicated areas must always be formatted before use), and then ALLOCATE those cylinders as SPOL space. Same recommendations: whole volume(s) dedicated to SPOOL. The only way to get the SPOOL files from the old to the new DASD is to use SPXTAPE command. You might want to have logged off every user except OPERATOR, then run SPXTAPE from there so that you capture as much as possible for the new SPOOL volumes. SPXTAPE is pretty fast nowadays. Be sure to dump the SDFs (System Data Files), too! Read the doc on SPXTAPE carefully. Practice dumping ahead of time so that you know how to do it in the least time possible when you need to. Be sure to issue: CP Q F, and CP Q SDF and match the number of files to the number of files dumped and restored. Coming up without CMS and other NSSes is painful.
When you bring up the system using the new DASD, you probably want to come up with options CLEAN, and NOAUTOLOG. Then from OPERATOR immediately SPXTAPE to restore SPOOL. Then you can SHUTDOWN REIPL.
Personally,for historic reasons I always like to ALLOCATE cylinder ZERO of every DASD volume as PERM space. But that's just me. If you get in that habit, it *may* be helpful later on for various reasons.
Once the new volumes are formatted and available (even when still using the old volsers), you can run CPFMTXA on the old volumes to change the **label** to something not listed in "SYSTEM CONFIG" as "CP_OWNED". CP won't see the volser change until the next time the volume is brought online, at which point you'll be using the new DASD. No, you cannot DETACH the old SPOOL and PAGE volumes from the running system, but you can define a full-Volume minidisk (or even just cylinder zero) for those DASD needing to be relabeled, then LINK to it and run CPFMTXA to LABEL it. We tend to define a userid for each DASD volume so we can LINK to it as needed for various reasons (this would be one), such as:
USER -VMPG01- NOLOG 64M 64M
MDISK A00 3390 0000 0001 VMPG01 R
MDISK F00 3390 0000 3339 VMPG01 R
You might wish to consider (if you have the available DASD) allocating a whole DASD as dump space. FORMAT/ALLOCATE it as SPOOL, then in SYSTEM CONFIG, define is as (for example, "DUMP" being the key to reserve it): CP_Owned Slot 5 VMDUMP DUMP
As long as you are messing with SPOOL (assuming you are moving ALL SPOOL DASD), you might want to move all your SPOOL volumes to the top of your "SYSTEM CONFIG" file so that they don't tend to get moved around for the sake of neatness later on. E.g.
/* CP_Owned Slot # volser|RESERVED Own|Dump|Shared */
CP_Owned Slot 1 VMSP01 OWN
CP_Owned Slot 2 VMSP02 OWN
CP_Owned Slot 3 RESERVED
CP_Owned Slot 4 RESERVED
CP_Owned Slot 5 VMDUMP DUMP
Food for thought.
Mike Walter
Hewitt Associates
The opinions expressed herein are mine alone, not my employer's.
| "Anne Crabtree"
<[EMAIL PROTECTED]>
Sent by: "VM/ESA and z/VM Discussions" <[email protected]> 01/19/2006 01:39 PM
|
|
I want to copy my 510SPL and 510PAG volumes from mod 3's to mod 9's.
We will be reiniting an LCU with all mod 3 to all mod 9. What is the best way to do this? Since the cylinder count is not the same, will it let me do it with ICKDSF or should I do it some other way?
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.
