Map the disks as provided by IBM - in previous releases the last cylinder has deliberately been left unallocated - this allows you to create (nearly) "full-pack" minidisks at cylinder 1 of a real volume (through to the end of the volume) and then restore the whole of the, "starter" onto
those disks without problem. I would expect one to be able to run a complete install in a Class G second-level userid that possesses the requisite number of minidisks of this kind (that is, just ont cylinder short of a full pack). Because the real volume serial number is on real cylinder zero, the, "duplicate", second-level volumes (whose volsers are on virtual cylinder zero - real cylinder one) never have the chance to be exposed at first level and so cannot cause any, "first level" confusion. It's a grea t way to practise installations but, of course, the systems installed on minidisks that don't start on real cylinder zero can only be IPLed in a virtual machine so this kind of test system cannot be used as the emergency repair-kit for the production system - to do that one needs to go that one step further and change the labels so that the packs can coexist at first level - not difficult but maybe something to save until one feels a little more confident.
