You're right, of course, Kris ... mental lapse on my part. Scott Rohling
On Tue, Oct 5, 2010 at 12:59 PM, Kris Buelens <[email protected]>wrote: > Wrong: a R/W link to a **fullpack** MDISK will not prevent write links to > non-fullpack minidisks. How else could you LINK to for example MAINT 190 > (probably located on xxxRES) while DIRMAINTfor example has xxRES R/W linked > as 123. > > 2010/10/5 Scott Rohling <[email protected]> > > I should have said that I assume you defined a DF1 on MAINT pointing to >> 54XRES parm disk. If MAINT has the whole 54XRES already in R/W (as when >> you put up the directory) - then no minidisks on it will be able to be >> linked R/W. Just a guess that's what's happening.. >> >> Scott Rohling >> >> >> On Tue, Oct 5, 2010 at 11:11 AM, Scott Rohling >> <[email protected]>wrote: >> >>> Do you still perhaps have 54XRES as your 123 disk? Do a Q LINKS DF1 to >>> see which disk MAINT has it R/W as... >>> >>> Scott Rohling >>> >>> >>> On Tue, Oct 5, 2010 at 10:54 AM, George Henke/NYLIC < >>> [email protected]> wrote: >>> >>>> >>>> There is plenty in the manuals about updating CF Parm disks at the same >>>> level, but any ideas about how to update L2 parm disks from L1? >>>> >>>> I have cloned the L1 directory, changed all 540 to 54X disks, and >>>> updated the L2 directory from L1, getting the expected RC=5. >>>> >>>> But when I try to link to CF1 on my L2 54XRES from L1, I get: >>>> >>>> LINK * DF1 DF1 WR >>>> HCPLNM102E DASD 0DF1 forced R/O; R/W by MAINT >>>> Ready(00102); T=0.01/0.01 12:36:00 >>>> >>>> DF1 is an attempt to try to "fake out" L1, but it looks like it is still >>>> sensitive to it. >>>> >>>> >>>> >>>> >>> >> > > > -- > Kris Buelens, > IBM Belgium, VM customer support >
