IBM has very nicely made sure to leave the last cylinder on the xxxRES an d xxxWnn packs empty to make copying them onto 1-END minidisks easy.
However, the installation instructions are written to allocate all the wa y to the end of the spool and page volumes. You *can* copy the spool and page volumes to 1-END minidisks and you'll be fine *most of the time*. I f the last cylinder of a 1st level spool volume had data you'll lose it. I f you dodge that, then when writing to spool/page you'll be fine up until the second level system tries to reference the last spool/page cylinder which doesn't exist. Doing re-allocates on the 2nd level page volumes is easy and safe, but no t a sure thing on spool volumes copied to 2nd level. You could do SPXTAPE, but that's ugly in an otherwise elegant method. Better is to not allocate the last cylinder on 1st level spool and page volumes during the initial installation. Brian Nielsen On Wed, 17 Oct 2007 15:44:07 +0200, Colin Allinson <[EMAIL PROTECTED]> wrote: >What I do is this :- > >1. Check that the last cylinder is not in use on the starter system >volumes (no starter system from IBM that I have ever seen uses cyl 3338) . > >2. Label new volumes with whatever label meets your local standard. > >3. Define a Userid on your 1st level system that will be used to run you r >2nd level system (i.e. VMLEV2) > >4. Define RW minidisks for VMLEV2 starting at CYL 1 to END on the new >volumes. > >5. Logon to VMLEV2 and DDR copy the real system volumes to you minidisks . >You will get 'Source is bigger than target' but this is OK. > >6. Detach the real system volumes and IPL from the Minidisk that you hav e >just copied the SYSRES to. > >Voila - you have a 2nd level copy of your system with spool integrity >maintained and no duplicate volume labels.
