> Ooops, sorry, you're right. I've always thought I have to > reboot when I've > updated the user.direct because the new adresses were not > active. Now I've > spend some time with the bookmanager, nice thingy. A "#cp > define mdisk" returns > "Invalid option - MDISK", which I've solved with the entry > "OPTION DEVMAINT" > for the designated z/VM user. Now I can enter "#cp define > mdisk 205 1 1500 > xyz" - wohaa - Linux recognizes the new disk.
If you've defined the disk in the CP directory entry and it's online, you should be able to just do a CP LINK * vaddr vaddr MR and not have to care about the extents. DEFINE MDISK is a dangerous tool -- one mistype, and you can easily clobber real data. It's intended for emergency situations, not normal use. -- db
