I'm guessing you are using a dirm amd with an explicit start parm. I dont
usually bother with that. AutoV and G are much more convenient. Sounds like
you could have overlaps. A dirm free command will tell you what dirmaint
thinks is available. The diagnose freext file that gets put in your reader
with it will show overlaps. I like to use dirm used to see those instead
though.
In the extent control file in the regions area, I believe each entry should
have a unique name. Then list a string of these on whatever groups you
define.
Remember you have to do a "dirm rlde" or the file will not be reread! For
my release this does not get picked up even after forcing and xautologing
dirmaint.
"Nix, Robert P."
<[EMAIL PROTECTED]
edu> To
[email protected]
Sent by: VM/ESA cc
and z/VM
Discussions Subject
<[EMAIL PROTECTED] DirMaint Extent Control woes...
.UARK.EDU>
12/12/2005 02:30
PM
Please respond to
VM/ESA and z/VM
Discussions
<[EMAIL PROTECTED]
.UARK.EDU>
I've almost got my hand-edited directory converted to DirMaint... Except
for two userids. Each fails on add because there is no gap large enough for
one of its minidisks (No autoV/G involved). I looked in Extent Control, and
both look like all the other entries; one is a 3390-3 and one is a 3390-27,
and both of these are defined in :defaults. Dirm Dirmap shows each has
having 1113 cyl available, to me meaning that the directive in Extent
Control was ignored.
What might cause DirMaint to single out these two disks, yet work fine for
all the others? Their lines are identical to other working entries. They
aren't at the top or bottom of the list, nor are they next to one another
in the list. Where and what else should I be looking for?
--
Robert P. Nix Mayo Foundation
RO-OC-1-13 (new loc) 200 First Street SW
507-284-0844 Rochester, MN 55905
-----
"In theory, theory and practice are the same, but
in practice, theory and practice are different."
