I don't see the need to define a $EOV$ minidisk. To make DIRMAINT work, correctly define all volumes in EXTENT CONTROL. To make DIRMAP happy, define all volumes -with correct- size in a user like our FULLPACK. Define FULLPACK's minidisks as excluded in your backup SW and in DIRMAINT's EXTENT CONTROL.
Kris, IBM Belgium, VM customer support > On: Fri, Nov 18, 2005 at 08:53:28PM -0800,Tom Cluster 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 find that if I try to add such single volume mdisks I get the > } following message: > } > } DVHALC3297E No gap of sufficient size found in candidate area(s). > } > } I've dug around and I've found an EXTENT CONTROL file. If a volume > } (for example, 390A09) is defined in this file in the following manner: > Tom, > I am not certain this will work, but you could try it. Do a DIRM USER > WITH which will get you a copy of the complete directory. Manually add > your $EOV$ user, and do the steps for inporting a new directory. > Haven't done that in a while, but ISTR it involves moving some files > about and doing a DIRM INITLZ command. Dirmaint may barf on this but it > may well work. > -- > Rich Greenberg N6LRT Marietta, GA, USA richgr atsign panix.com + 1 > 770 321 6507 > Eastern time zone. I speak for myself & my dogs only. VM'er since CP-67 > Canines:Val, Red & Shasta (RIP),Red, husky Owner:Chinook-L > Atlanta Siberian Husky Rescue. www.panix.com/~richgr/ Asst Owner:Sibernet-L
