DIRME is part of the DRM package: http://www.vm.ibm.com/download/packages/descript.cgi?DRM
The native way to update DIRMAINT files is not by stopping DIRMAINT can copying files on its disks. When not using tools like DIRME you can do: DIRM SEND EXTENT CONTROL RECEIVE update with XEDIT DIRM FILE EXTENT CONTROL DIRM RLDE DIRME executes almost these commands, only instead of DIRM SEND and RECEIVE it LINKs to DIRMAINT's disk to grab the control file. After any update of a Dirmaint file with DIRM FILE (even execs) you need to issue some DIRM RLDxxx command. Kris, IBM Belgium, VM customer support VM/ESA and z/VM Discussions <[email protected]> wrote on 2005-11-21 05:42:58: > Dirmaint hasn't been working well for me. Let's take just one > frustrating point. Here's my exclusion section of EXTENT CONTROL: > :EXCLUDE. > * USERID ADDRESS > $SYSVOL$ * > MAINT 0121 > MAINT 0123 > MAINT 0124 > MAINT 0125 > MAINT 0126 > MAINT 0127 > MAINT 0128 > MAINT 0129 > MAINT 012A > .SPOOL. * > .PAGE. * > .DIRECT. * > :END. > Yet even though I make sure that both copies of EXTENT CONTROL are > the same (1DF and 1DB - 1DF seems to have primacy, because if I > change only 1DB I find that periodically my changes are lost) and > that I have issued the DIRM RLDEXTN command, when I do a DIRM DIRMAP > volumes like Maint's 127 still show up on the map, preventing all > gaps on the volume from being shown. > By the way, how do I get DIRME? It's supposed to help with updating > EXTENT CONTROL, among other things. Kris wrote about it. I looked > for it on the VM home page's package download section and couldn't > find it. And if I don't have DIRME, which minidisk's version of > EXTENT CONTROL am I supposed to change? Am I supposed to change > 1DF? Is the one on 1DB simply a copy of the one on 1DF? When is it > copied? When a "backup" is done? > I have given up using $EOV$ because I've discovered that DIRMAP (from > the old CUF) bases its determination of the size of a volume from the > mdisk with the highest extent, and that works reasonably > well. However, I have a 100 cylinder 3390 (carved out of left-over > space on a Shark) and I've been unable to make either Dirmaint or > Dirmap believe me that it's only 100 cyllinders. > /gripe on/ > The frustration isn't helped by the fact that I don't have a printed > Dirmaint manual. The CDRom is fine for looking things up, but it's > not good for an initial read-through. > /gripe off/ > - Tom. > At 04:00 PM 11/20/2005, you wrote: > > > I'm trying to implement the $EOV$ userid discussed earlier - > > > a single cylinder at the top of each volume - in order to get > > > better reporting of end-of-volume gaps. I'm using Dirmaint, > > > which is new to me. (I plan to use the CMS DIRMAP command, > > > not Dirmaint's dirmap function, but I still need to populate > > > the directory with the $EOV$ minidisks.) > > > >I guess I don't understand why you need DIRMAP if you are running Dirmaint. > >Agreed, DIRMAINT's command set is one of the less intuitive items to appear > >in Western Civilization, but if you're constantly second-guessing your > >resource manager, it would seem that you're spending a lot of time and > >effort duplicating what DIRM already does mechanically. > > > >Could you elaborate on what it is that causes you to want to circuvent > >DIRMAINT? > > > >-- db > Tom Cluster > County of Sonoma > Santa Rosa, CA > (707) 565-3384 (Tuesdays and Wednesdays only)
