This sounds intriguing. What do you mean about link to a full pack mini disk? Take the following statement from my directory entry for example:
MDISK 0191 3390 11 5 VMUSR0 MR Currently, VMUSR0 looks like the following under the first level z/VM v5.1: CP Q SYSTEM 6815 DASD 6815 ATTACHED SYSTEM 0012 VMUSR0 VMTESTSV 0191 R/W , VMTESTSV 2CF1 R/W , VMTESTSV 22CC R/W VMTESTSV 2222 R/W , LINUXD01 0191 R/O , LINUXP01 0191 R/O LINUXM03 0191 R/O , LINUXYOU 0191 R/O , LINUXYUM 0191 R/O VSWCTRL1 0191 R/W , OPERATOR 0199 R/O , MAINT 0199 R/O Of course, VMTESTSV is my second level z/VM 5.3 system. What exactly do I need to do to have a full pack link? Thanks. Peter Stephen Frazier <[EMAIL PROTECTED]> Sent by: Linux on 390 Port <LINUX-390@VM.MARIST.EDU> 05/23/2008 01:38 PM Please respond to Linux on 390 Port <LINUX-390@VM.MARIST.EDU> To LINUX-390@VM.MARIST.EDU cc Subject Re: z/VM 5.1 to 5.3 upgrade ( a little handholding requested) PART 2 So far your approach is good. See some comments below. Peter E. Abresch Jr. - at Pepco wrote: > Thanks to everyone that responded to my original hand holding request. > With everyone?s response we were able to install z/VM 5.3 as a second > level guest to our z/VM V5.1. We also applied the latest RSU maintenance > and have performed backups of our 5.3 system. > > We are now looking to migrate our users (system programmers). Remember, we > only use z/VM for Linux guest only. I was going to migrate (cut and paste) > our z/VM 5.1 guest directory entries into our z/VM 5.3 user direct and > perform a DIRECTXA which should work. We only have about 20. But. . . . we > have some sharing concerns. Yes, copy the user entries from the old directory to the new directory. > > For example: I want to cut the following entry from user direct on z/VM > 5.1 and paste it in user direct on z/VM 5.3 and put it online. > > USER X062PEA ******** 64M 100M ABCDEFG > INCLUDE IBMDFLT > ACCOUNT 1 SYSPROG > IPL CMS > MACH XA > OPTION MAINTCCW LNKS LNKE LNKNOPAS > LINK TCPMAINT 0592 0592 RR > MDISK 0191 3390 11 5 VMUSR0 MR > MDISK 0199 3390 31 100 VMUSR0 RR > > Volume VMUSR0 looks like the following under our current 5.1 system: > > DASD 6815 CP SYSTEM VMUSR0 13 > > Here are the questions. > > Can I attach 6815 to my second level z/VM 5.3 guest and then logon with > x062pea or do I need to detach it to our first level z/VM 5.1 system. I would use a link to a full pack minidisk to give your second level guest access to the disk. If you use link then both first and second level users can access different minidisks on the disk at the same time. If you use detach and attach then you can not have users on both systems at the same time. > > Are they any sharing concerns that I need to be aware of? Do not have the same user log on to both first and second level at the same time. Two users should not have write access to a minidisk at one time. In your example minidisk 0199 is read only so it doesn't matter how many users have it. However, minidisk 0191 is set so that it will get a write access to the minidisk if no one else has one when it logs on. But, it will get read only access if someone else (at the same level on this lpar) has write access. If you are an experienced VM systems programmer you would have set up your machine to propagate the protection across lpars and levels. If you are not experienced enough to do this then be careful not to have two write links at the same time. > > Our final z/VM 5.3 test will be ipling it in a separate LPAR. Are their > additional sharing concerns I have to worry about? If you followed my advice to use link instead of attach then there is no change in sharing concerns when you run both VMs in lpars instead of one under the other. If you were using attach when running in one lpar when you bring it up in a second lpar you will have the disk attached to both VM at the same time. That introduces all the concerns that you would have if you used link. > > Anthing that will get us on the right track is appreciated. We want to > make sure that we do not cause problems with our production z/VM, > especially over the long holiday. > > Thanks as always. > > Peter > > Remember, we are old MVSers but very young VMers. Go slow. Right, that is why I didn't try to explain how to set up cross domain data sharing. -- Stephen Frazier Information Technology Unit Oklahoma Department of Corrections 3400 Martin Luther King Oklahoma City, Ok, 73111-4298 Tel.: (405) 425-2549 Fax: (405) 425-2554 Pager: (405) 690-1828 email: stevef%doc.state.ok.us ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 This Email message and any attachment may contain information that is proprietary, legally privileged, confidential and/or subject to copyright belonging to Pepco Holdings, Inc. or its affiliates ("PHI"). This Email is intended solely for the use of the person(s) to which it is addressed. If you are not an intended recipient, or the employee or agent responsible for delivery of this Email to the intended recipient(s), you are hereby notified that any dissemination, distribution or copying of this Email is strictly prohibited. If you have received this message in error, please immediately notify the sender and permanently delete this Email and any copies. PHI policies expressly prohibit employees from making defamatory or offensive statements and infringing any copyright or any other legal right by Email communication. PHI will not accept any liability in respect of such communications. ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
