Hi Valerie, I hope not to add to your confusion, and I have held off because I am not on z/VM 5.4 but z/VM 5.3, plus there is always lots of expert advice from this list.
A couple of things though. If you have the MAINT extents, and others, listed in the EXTENT CONTROL file, that is good, but you also need to say "DIRM DIRMAP EX" - it is the EXCLUDE parameter that tells the DIRMAP to pay attention to the excluded items. And then the excluded items are left off your USER MDISKMAP entirely. Also, I left my MDISK statements for things like MAINT 123 as they came from IBM - with the END used - MDISK 0123 3390 000 END 530RES MR There is another spot in EXTENT CONTROL called :DEFAULTS, where you get to say how big a 3390 is. If all your volumes are 3390-9, I would have something like this in EXTENT CONTROL: :DEFAULTS. 3390 10017 DECLARE ALL 3390'S TO BE MOD 9 3390-01 1113 3390-02 2226 3390-03 3339 3390-09 10017 :END. The comment after the "3390 10017" line is mine, and is ignored by DIRMAINT. On my system I have nothing but 3390-3 but when my company took over, the previous service provider had been using nothing but 3390-2. Took me some time to find this little line. And, I expect many of the R/W links that are so scary are in fact other MAINT links to different smaller extents on 540RES - all those bits and pieces of MAINT that make up VM. The CP command "Q SYS cuu" will tell you who has those R/W links, you just have to know the real address of the 540RES volume to plug in where the "cuu" is. And if you are not sure, then the command Q DA 540RES would tell you the real address of 540RES. Ron On Thu, Apr 16, 2009 at 7:52 AM, Le Grande Valerie <valerie.legra...@sentry.com> wrote: > With all the information I have been given, I am still unsure I know how > to fix this. > Here is some more information: > Today when I logged on to MAINT, I noticed I got error message HCPLNM103E > DASD 123 forced R/O; R/W by 48 R/o by 97 users Stable by 3 > > MAINT has MDISK 0123 3390 000 10016 540RES MR > > > I DID save copies of what I changed. First of all, here is what was listed > on the DIRM DIRMAP report I was concerned about: > > on 540RES (a 3390 MOD9): > > 3390 $ALLOC$ 0A01 * 0 0 1 Overlap > MAINT 0123 * 0 1112 1113 Overlap > SYSDUMP1 0123 * 0 1112 1113 Overlap > .DRCT. 30E5 * 1 20 20 Overlap > (30E5 being the real volume) > $DIRECT$ 0A04 * 1 20 20 > : > : > I was concerned about the overlaps, and also that the sizes for MAINT and > SYSDUMP1 0123 was not really the full volume. Same true for $PAGE$, > $SPOOL$ and MAINT 0122 (Spool) - they were overlaps, but also did not > match the volume size. > I did not change $ALLOC$ as I had been taught about that in the one class > I have taken. > > Changed MAINT 0122, 0123 and 0124 MDISK statements in MAINT DIRECT to have > a hard coded 10016 coded instead of END, and also modified $PAGE$, $SPOOL$ > as I did not think these were correct as showing END of 1112 in the report. > > 540RES after on the DIRM DIRMAP looks like: > > 3390 $ALLOC$ 0A01 * 0 0 1 Overlap > MAINT 0123 * 0 10115 10116 > SYSDUMP1 0123 * 0 10115 10116 > .DRCT. 30E5 * 1 20 20 Overlap > (30E5 being the real volume) > $DIRECT$ 0A04 * 1 20 20 > > Also the Overlaps were gone for $PAGE$, $SPOOL$, and MAINT 0122. I > noticed that .DRCT. still had Overlap, but it worked before, so I was not > concerned. > > I DO have in EXTENT CONTROL: > > :EXCLUDE. > * USERID ADDRESS > MAINT 012* > SYSDUMP1 012* > :END. > (added per Getting Started with Linux on System Z) > > > With those details, what is suggested to get things back in order? I now > assume that having the smaller definitions for $xx$ and MAINT 012x MDISKS > is the way it SHOULD be and I should not have messed with that? > > Thanks for trying to help a confused newbie. > > >
