Or hey - maybe DIRM DASD CHANGE VOLUME oldid newid (followed I suppose by DIRM DASD CHANGE REGION oldid newid?)
I just discovered DIRM DASD recently.. which helps you manage the EXTENT CONTROL file -- and only recently mostly because (at least on my system) the DIRMAINT HELP menu doesn't list it. But DIRM HELP DASD will show you this neat command... It would be great if the EXTENT CONTROL file got updated - as well as the directory.. But since the design seems to be that DIRM DASD only manipulates the EXTENT CONTROL file - then maybe a separate DIRM RELABEL which updates the directory is warranted. Something like: DIRM DASD CHANGE VOLUME OLDVM1 NEWVM1 DIRM DASD CHANGE REGION OLDVM1 NEWVM1 DIRM RELABEL OLDVM1 NEWVM1 DIRM RLDE (put the extent control changes 'online') Scott Rohling On Fri, Oct 1, 2010 at 3:31 PM, Alan Altmark <[email protected]>wrote: > On Friday, 10/01/2010 at 05:08 EDT, Scott Rohling > <[email protected]> wrote: > > There are times when using DIRMAINT commands isn't practical.. for > example - > > doing DASD volume relabelling. I suppose you could do a bunch of > GET/REP > > commands -- or maybe DMDISK NOCLEAN and AMDISK using the same extents > and the > > new volid? But I have found the best thing to do is update the > monolithic > > directory with some simple plumbing and then give it back to DIRMAINT. > I > > concede the loss of an audit trail, but for most customers that can be > resolved > > by having a change record indicating what was done. > > I had thought of that case and would allow it with proper oversight and > change management as you suggest. Of course, I would turn around and > demand (nay, politely request with a tug on my forelock) a DIRM RELABEL > command. > > And I would probably remove class H from DIRM USER, or maybe even give it > its own class. It should be HARD to use that command, just as folks with > RACF should make it hard for a sysprog to issue the CP STORE HOST command. > > Alan Altmark > > z/VM and Linux on System z Consultant > IBM System Lab Services and Training > ibm.com/systems/services/labservices > office: 607.429.3323 > [email protected] > IBM Endicott >
