Actually, I'm converting from zVM 4.4 to zVM 5.1, and I'm installing DirMaint for the first time. I'm trying to roll my hand-edited 4.4 directory into the zVM 5.1 system and into DirMaint, so all my MDISK entries are live extents that I want to have the same as on the 1st level 4.4 system.
Once we're up and running on zVM 5.1, we'll be using AUTOV and AUTOG very extensively.... They just don't work for the initial conversion. And I couldn't start DirMaint with the hand-edited 4.4 directory, because there's also a hand-edited 5.1 directory to be considered and that was the one I started DirMaint with. (Ah... The joys of upgrades...) -- 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." -----Original Message----- From: VM/ESA and z/VM Discussions [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Monday, December 12, 2005 2:03 PM To: [email protected] Subject: Re: DirMaint Extent Control woes... 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.
