> Dirmaint hasn't been working well for me. Let's take just > one frustrating point. Here's my exclusion section of EXTENT CONTROL: > [..snip..] > 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.
One observation I'd share that's not really very explicit in the docs is this: Once DIRMAINT is enabled, you should use *only* the automated interfaces to change it's configuration. Shutting it down and doing direct file edits is like doing direct surgery on your own brain -- it works, but it's really hard to concentrate on doing a good job if it happens often enough, and you're not likely to be very alert when it happens. The approach that DIRME uses is the right one, because at least then DIRMAINT gets a chance to consciously know that the file has been changed and to do the right thing. > /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/ As Harry said, grab the PDFs and print one. This actually is one positive impact from the screaming mad dash IBM seems to be engaging in where they want to ship every product without paper books -- they've become a lot more liberal about making the PDFs easily available. This actually is a great excuse to a) set up RSCS LPR support to one of your high-speed LAN printers and b) convince someone to buy a duplexer unit for said printer..8-).
