If you use Dirmaint: use the CLEAN option for a DMDDISK or CMDISK (delete/change minidisk): the DATAMOVE tries to get an exclusive link. Only when that succeeds, the minidisk is cleared after which it becomes free for re-use.
Without CLEAN, the problem is not only that current users of old minidisk are not protected at all, but you may get extra trouble: Suppose an old minidisk started at cyl 100, and cyl 90-99 were free. After a DMISK, a new 20 cylinder minidisk is created from cyl 90 through 109. Now if one tries to link the new minidisk in write, CP will refuse if the old minidisk is linked R/W. If you link R/O and issue Q LINKS to see who's prohibiting your R/W request, CP tells "no links". Because for Q LINKS CP checks who's having minidisks with the same start cylinder (no I don't have an exec to find this out, even though I think I once had). 2008/6/27 Michael Coffin <[EMAIL PROTECTED]>: > Actually, if your ESM is VM:Secure you don't have to worry about any of > this. He'll happily let you move R/O minidisks AND automatically > reclaim the old extent after ALL links to it have been severed. As long > as you aren't changing the size of the disk, I believe he'll copy it > track by track (just like DDR) so the NSS's shouldn't have a problem > either. > > -MC > > > > -----Original Message----- > From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On > Behalf Of Kris Buelens > > And, if you have an ESM, the passwords on the MDISK records don't count > anymore, so you can then also store some information on the 190 MDISK > record. > -- Kris Buelens, IBM Belgium, VM customer support
