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:
:REGIONS.
390A09 390A09 0001 3338 3390-03
:END.
:GROUPS.
VMUSRGRP 390A09
:END.
then I can define the minidisk. My problem is that most DASD on our
system is not so defined, and I don't feel like going to all the
trouble of defining each 3390-03 separately. There must be a way to
set a default for 3390's, so that Dirmaint doesn't think they're all 3390-1's.
In the bottom of EXTENT CONTROL I see the following:
:DEFAULTS.
* IBM supplied defaults are contained in the DEFAULTS DATADVH file.
* The following are customer overrides and supplements.
*
*DASDType Max-Size
3380-500 500
3390-03 3339
:END.
I made an entry of "3390 3339", but it made no difference. I figure
I'm not supposed to change DEFAULT DATADVH (even if I knew where it
is), and I'm reluctant to use the EXTNCHK OFF command.
Is there an easy way to make Dirmaint understand that all of my
3390's are mod 3's, with 3339 cylinders?
- Tom.
Tom Cluster
County of Sonoma
Santa Rosa, CA
(707) 565-3384 (Tuesdays and Wednesdays only)
