On Friday, 10/01/2010 at 05:08 EDT, Scott Rohling <scott.rohl...@gmail.com> 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 alan_altm...@us.ibm.com IBM Endicott
