Re: Updating L2 Parm Disks
You're right, of course, Kris ... mental lapse on my part. Scott Rohling On Tue, Oct 5, 2010 at 12:59 PM, Kris Buelens 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 > > 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 >> 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 < >>> george_he...@newyorklife.com> 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 >
Re: Updating L2 Parm Disks
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 > 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 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 < >> george_he...@newyorklife.com> 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
Re: Updating L2 Parm Disks
tyvm, Scott, Kris, Brian, and Frank: Looking good. I Detached 54XRES from MAINT L1 and from SYSTEM L1. Then on MAINT L1 Attached 54XRES just to SYSTEM. Then on my L2 "to be" guest, ZVM54SVM, linked, accessed, and updated, DF1, alias CF1, np. I believe I had Attached 54XRES and/or its DF1 md to MAINT as well as 54XRES to SYSTEM. When I Attached 54XRES to SYSTEM only and linked and accessed from my L2 "to be" guest, all was well. Once I get my extra Page and Spool disks and DDR them from L1 I should be able to IPL L2. I believe I need to IPL FORCED. Thank you all once again for all your help. "Frank M. Ramaekers" Sent by: The IBM z/VM Operating System 10/05/2010 01:33 PM Please respond to The IBM z/VM Operating System To IBMVM@LISTSERV.UARK.EDU cc Subject Re: Updating L2 Parm Disks This is what I do to access my 2nd level disks: (to access 2nd level directory (for update) MDISK F123 3390 END 54ARES MR (to access 2nd level MAINT 191 disk) MDISK F191 3390 0801 0800 54AW07 MR READ WRITEMULTIPLE (to access 2nd level SYSTEM CONFIG) MDISK FCF1 3390 0039 0120 54ARES MR READ WRITEMULTIPLE Frank M. Ramaekers Jr. From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of George Henke/NYLIC Sent: Tuesday, October 05, 2010 11:55 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Updating L2 Parm Disks 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. _ This message contains information which is privileged and confidential and is solely for the use of the intended recipient. If you are not the intended recipient, be aware that any review, disclosure, copying, distribution, or use of the contents of this message is strictly prohibited. If you have received this in error, please destroy it immediately and notify us at privacy...@ailife.com.
Re: Updating L2 Parm Disks
This is what I do to access my 2nd level disks: (to access 2nd level directory (for update) MDISK F123 3390 END 54ARES MR (to access 2nd level MAINT 191 disk) MDISK F191 3390 0801 0800 54AW07 MR READ WRITEMULTIPLE (to access 2nd level SYSTEM CONFIG) MDISK FCF1 3390 0039 0120 54ARES MR READ WRITEMULTIPLE Frank M. Ramaekers Jr. From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of George Henke/NYLIC Sent: Tuesday, October 05, 2010 11:55 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Updating L2 Parm Disks 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. _ This message contains information which is privileged and confidential and is solely for the use of the intended recipient. If you are not the intended recipient, be aware that any review, disclosure, copying, distribution, or use of the contents of this message is strictly prohibited. If you have received this in error, please destroy it immediately and notify us at privacy...@ailife.com.
Re: Updating L2 Parm Disks
This is another thing that would have been easier and beter to do from th e running 2nd level system -- and also not neccesary if you've DDR'd into minidisks. Be that as it may, you can use DEFINE MDISK from your 1st level system to create a temporary link to a 2nd level minidisk. You need to know the correct starting cylinder, length, and volser. Brian Nielsen On Tue, 5 Oct 2010 12:54:50 -0400, George Henke/NYLIC 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 update d >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.
Re: Updating L2 Parm Disks
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 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 < > george_he...@newyorklife.com> 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. >> >> >> >> >
Re: Updating L2 Parm Disks
Try this Q LINKS DF1 And you'll see by which address MAINT has this mdisk linked Then in MAINT DETACH 2010/10/5 George Henke/NYLIC > > 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
Re: Updating L2 Parm Disks
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 < george_he...@newyorklife.com> 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. > > > >
