Mike, As soon as I changed from
USER LNXMAINT LXPSEGLI 64M 128M G INCLUDE TCPCMSU LINK TCPMAINT 592 592 RR MDISK 0191 3390 0001 0020 VM1090 MR READ WRITE MULTIPLE MDISK 0192 3390 0021 0500 VM1090 MR ALL WRITE MULTIPLE To USER LNXMAINT LXPSEGLI 64M 128M G INCLUDE TCPCMSU LINK TCPMAINT 592 592 RR MDISK 0191 3390 0001 0020 VM1090 MR PASSWORD PASSWORD PASSWORD MDISK 0192 3390 0021 0500 VM1090 MR PASSWORD PASSWORD PASSWORD * It works. Ray -----Original Message----- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Michael MacIsaac Sent: Friday, December 12, 2014 6:44 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: Question on The Virtualization Cookbook for IVM z/VM V6.3 Email sent from outside of PSEG. Use caution before using links/attachments. Ray, When I wrote: > Yes, each Linux system will need its own disk. Sorry, I meant that for LNXADMIN (the sysadmin's Linux on each member LPAR), not LNXMAINT (the CMS machine designed for a common 191 disk on all Linux virtual machines). If you make LNXMAINT an IDENTITY, you will have to maintain four common disks, not just one. Why make things more complex? I would recommend going back to the original USER directory entry. If you are getting an error on the other members, post the error message(s) here and we'll figure it out. -Mike On Thu, Dec 11, 2014 at 3:37 PM, Chu, Raymond <raymond....@pseg.com> wrote: > > Mike, > > This is how I modified the user direct file and it worked but I would > like your assistance to confirm what and how to make it better. > > Step 1 - modified the LNXMAINT from > > USER LNXMAINT PASSWORD 64M 128M G > INCLUDE TCPCMSU > LINK TCPMAINT 592 592 RR > MDISK 0191 3390 0001 0020 VM1090 MR READ WRITE MULTIPLE MDISK 0192 > 3390 0021 0500 VM1090 MR ALL WRITE MULTIPLE > > > To > > IDENTITY LNXMAINT PASSWORD 64M 128M G > INCLUDE TCPCMSU > BUILD ON NAVY USING SUBCONFIG LNXMNT-1 > BUILD ON AIRFORCE USING SUBCONFIG LNXMNT-2 > BUILD ON ARMY USING SUBCONFIG LNXMNT-3 > BUILD ON MARINES USING SUBCONFIG LNXMNT-4 > SUBCONFIG LNXMNT-1 > LINK TCPMAINT 592 592 RR > MDISK 0191 3390 0001 0020 VM1090 MR PASSWORD PASSWORD PASSWORD > MDISK 0192 3390 0021 0500 VM1090 MR PASSWORD PASSWORD PASSWORD > SUBCONFIG LNXMNT-2 > LINK TCPMAINT 592 592 RR > MDISK 0191 3390 0001 0020 VM1526 MR PASSWORD PASSWORD PASSWORD > MDISK 0192 3390 0021 0500 VM1526 MR PASSWORD PASSWORD PASSWORD > SUBCONFIG LNXMNT-3 > LINK TCPMAINT 592 592 RR > MDISK 0191 3390 0001 0020 VM149F MR PASSWORD PASSWORD PASSWORD > MDISK 0192 3390 0021 0500 VM149F MR PASSWORD PASSWORD PASSWORD > SUBCONFIG LNXMNT-4 > LINK TCPMAINT 592 592 RR > MDISK 0191 3390 0001 0020 VM1528 MR PASSWORD PASSWORD PASSWORD > MDISK 0192 3390 0021 0500 VM1528 MR PASSWORD PASSWORD PASSWORD > * > Step 2 - Shutdown the LNXADMIN (Linux image) with halt command Step 3 > - Make sure LNXADMIN be logged off from the current LPAR let's day > zVM3 > Step 4 - Logon to zVM2 LPAR as LNXADMIN and start up the Linux image > Step 5 - Logon to the LNXADMIN in Linux and run the famous "clone" script. > It picks the expected specified range of macprefix. > > It works. > > Here is the question. It seems the LNXADMIN and RH65GOLD are only be > picked up from the first zVM1 (DISK VM10901) and other disks (VM1526, > VM149F and VM1528) are not used at all. I would like to save some > DASDs and use them for something else. It there a way to work around them. > > Thanks, > > Ray > > > -----Original Message----- > From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of > Michael MacIsaac > Sent: Thursday, December 11, 2014 2:27 PM > To: LINUX-390@VM.MARIST.EDU > Subject: Re: Question on The Virtualization Cookbook for IVM z/VM V6.3 > > Email sent from outside of PSEG. Use caution before using > links/attachments. > > > Ray, > > > But I am unable to use zVM2, zVM3 and zVM4 to do any cloning at all. > What error are you getting? > > The golden image is a USER, not an IDENTITY, right? If the minidisk > volume(s) of the golden image are available to all member systems, > then you should be OK. > > -Mike > > On Thu, Dec 11, 2014 at 12:14 PM, Chu, Raymond <raymond....@pseg.com> > wrote: > > > Mike, > > > > I actually have the following set up shown below: > > > > IDENTITY LNXADMIN PASSWORD 256M 1G BG INCLUDE LNXDFLT > > BUILD ON zVM1 USING SUBCONFIG LNXADM-1 > > BUILD ON zVM2 USING SUBCONFIG LNXADM-2 > > BUILD ON zVM3 USING SUBCONFIG LNXADM-3 > > BUILD ON zVM4 USING SUBCONFIG LNXADM-4 > > OPTION LNKNOPAS > > SUBCONFIG LNXADM-1 > > MDISK 0100 3390 0001 10016 VM1091 MR PASSWORD PASSWORD PASSWORD > > MDISK 0101 3390 0521 9496 VM1090 MR PASSWORD PASSWORD PASSWORD > > SUBCONFIG LNXADM-2 > > MDISK 0100 3390 0001 10016 VM1525 MR PASSWORD PASSWORD PASSWORD > > MDISK 0101 3390 0521 9496 VM1526 MR PASSWORD PASSWORD PASSWORD > > SUBCONFIG LNXADM-3 > > MDISK 0100 3390 0001 10016 VM149E MR PASSWORD PASSWORD PASSWORD > > MDISK 0101 3390 0521 9496 VM149F MR PASSWORD PASSWORD PASSWORD > > SUBCONFIG LNXADM-4 > > MDISK 0100 3390 0001 10016 VM1527 MR PASSWORD PASSWORD PASSWORD > > MDISK 0101 3390 0521 9496 VM1528 MR PASSWORD PASSWORD PASSWORD > > > > It works great to use the zVM1 to do cloning and I can create zLinux > > z Images from the zVM1 LPAR. But I am unable to use zVM2, zVM3 and > > zVM4 to do any cloning at all. > > > > I also cloned MDISK 100 (VM1091) of zVM1 to VM1525, VM149E and > > VM1527 and MDISK 101 (VM1090) of zVM1 to VM1526, VM149F and VM1528. > > Understood that the MISK 101 started at 521 because 1 to 520 were > > used by LNXMAINT for two virtual mode A and D for SWAPGEN, RH65GOLD > > and LNXADMIN parameters and configurations and so on. > > > > I have been communicating with IBM Link to figure how to create > > Linux on System z from zVM2, zVM3 and zVM4 and I am kind of out of resource. > > Since you were the Master of the RedBook and you still are. Could > > you please show and tell me what went wrong? > > > > The reason that I am looking for this particular configuration is > > because I want to configure zLinux images from a particular LPARs to > > pick up particular range of predefined mac prefix. > > > > Thanks, > > > > Ray > > > > -----Original Message----- > > From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf > > Of Michael MacIsaac > > Sent: Friday, November 14, 2014 2:43 PM > > To: LINUX-390@VM.MARIST.EDU > > Subject: Re: Question on The Virtualization Cookbook for IVM z/VM > > V6.3 > > > > Email sent from outside of PSEG. Use caution before using > > links/attachments. > > > > > > Ray, > > > > Yes. The idea here is to have one administrative Linux per LPAR (SSI > > member). With an IDENTITY, all four can/should be running at the > > same > time. > > > > We had 100 and 101 minidisks in an earlier Cookbook so as to have > > two 3390-3s. In the current cookbook we split a 3390-9 in half which > > may not make the most sense, but it still works. If you have the > > disk space, you might want to make both 100 and 101 full mod-9s to > > leave a little more room for growth. > > > > -Mike > > > > On Fri, Nov 14, 2014 at 1:28 PM, Chu, Raymond <raymond....@pseg.com> > > wrote: > > > > > Hi, > > > > > > I have already configured a z/VM SSI cluster with 4 LPARs. When I > > > revisited the Cookbook at Section 2.8.5 z/VM DASD used in this book. > > > Table 2-8, I can see DASD are reserved for LNXMAINT(191-192), > > > LNXADMIN (101), LNXADMIN (100) for member 1 LNXADMIN (100) and > > > LNXADMIN (100) for member 2 > > > > > > Our system has 4 z/VM LPARs. Should I also reserve DASDs > > > LNXADMIN(100) and (101) for member 3 and 4 ? They should have the > > > same setting as the member? Please advise. > > > > > > Thanks, > > > Ray > > > > > > > > > > > > ----------------------------------------- > > > > > > The information contained in this e-mail, including any > > > attachment(s), is intended solely for use by the named addressee(s). > > > If you are not the intended recipient, or a person designated as > > > responsible for delivering such messages to the intended > > > recipient, you are not authorized to disclose, copy, distribute or > > > retain this message, in whole or in part, without written > > > authorization from PSEG. This e-mail may contain proprietary, > > > confidential or privileged information. If you have received this > > > message in error, please notify the sender immediately. This > > > notice is included in all e-mail messages leaving PSEG. Thank you for > > > your cooperation. > > > > > > ------------------------------------------------------------------ > > > -- > > > -- For LINUX-390 subscribe / signoff / archive access > > > instructions, send email to lists...@vm.marist.edu with the > > > message: INFO > > > LINUX-390 or visit > > > http://www.marist.edu/htbin/wlvindex?LINUX-390 > > > ------------------------------------------------------------------ > > > -- > > > -- For more information on Linux on System z, visit > > > http://wiki.linuxvm.org/ > > > > > > > -------------------------------------------------------------------- > > -- For LINUX-390 subscribe / signoff / archive access instructions, > > send email to lists...@vm.marist.edu with the message: INFO > > LINUX-390 or visit > > http://www.marist.edu/htbin/wlvindex?LINUX-390 > > -------------------------------------------------------------------- > > -- For more information on Linux on System z, visit > > http://wiki.linuxvm.org/ > > > > > > ----------------------------------------- > > The information contained in this e-mail, including any > > attachment(s), is intended solely for use by the named addressee(s). > > If you are not the intended recipient, or a person designated as > > responsible for delivering such messages to the intended recipient, > > you are not authorized to disclose, copy, distribute or retain this > > message, in whole or in part, without written authorization from > > PSEG. This e-mail may contain proprietary, confidential or > > privileged information. If you have received this message in error, > > please notify the sender immediately. This notice is included in all > > e-mail messages leaving PSEG. Thank you for your cooperation. > > > > ---------------------------------------------------------------------- > For LINUX-390 subscribe / signoff / archive access instructions, send > email to lists...@vm.marist.edu with the message: INFO LINUX-390 or > visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 > ---------------------------------------------------------------------- > For more information on Linux on System z, visit > http://wiki.linuxvm.org/ > > > ----------------------------------------- > The information contained in this e-mail, including any attachment(s), > is intended solely for use by the named addressee(s). If you are not > the intended recipient, or a person designated as responsible for > delivering such messages to the intended recipient, you are not > authorized to disclose, copy, distribute or retain this message, in > whole or in part, without written authorization from PSEG. This > e-mail may contain proprietary, confidential or privileged > information. If you have received this message in error, please notify > the sender immediately. This notice is included in all e-mail messages > leaving PSEG. Thank you for your cooperation. > ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/ ----------------------------------------- The information contained in this e-mail, including any attachment(s), is intended solely for use by the named addressee(s). If you are not the intended recipient, or a person designated as responsible for delivering such messages to the intended recipient, you are not authorized to disclose, copy, distribute or retain this message, in whole or in part, without written authorization from PSEG. This e-mail may contain proprietary, confidential or privileged information. If you have received this message in error, please notify the sender immediately. This notice is included in all e-mail messages leaving PSEG. Thank you for your cooperation.
