Peter, CMS operating system doesn't have any mechanism to safely share an ACCESS-ed RW mdisk with another CMS user that has that same mdisk ACCESS-ed RW; think of it as wiring the same hard drive to 2 windozPC's. So yes there are serious CMS sharing issues, don't do it.
"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.?" You could do as you proposed: DETACH 6815 SYSTEM and then ATTACH 6815 guest53. On 2ndlevel guest do VARY ON 6815, ATTACH 6815 SYSTEM and update the 2nd-level directory with the 5.1 staff definitions. Or the staff definitions could be added before the ATTACH 6815. While 6815's attached to the guest none of its mdisks defined to the 5.1 system's directory will be available on 5.1: PACK NOT MOUNTED or some-such message if 5.1 user X062PEA logs on. If you have trouble with the DETACH 6815, try CP Q SYSTEM 6815 to see which currently logged on users have an mdisk/LINK-ed-mdisk on 6815. -------------------------------------------------------- This e-mail, including any attachments, may be confidential, privileged or otherwise legally protected. It is intended only for the addressee. If you received this e-mail in error or from someone who was not authorized to send it to you, do not disseminate, copy or otherwise use this e-mail or its attachments. Please notify the sender immediately by reply e-mail and delete the e-mail from your system. -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Peter E. Abresch Jr. - at Pepco Sent: Friday, May 23, 2008 11:25 AM To: LINUX-390@VM.MARIST.EDU Subject: z/VM 5.1 to 5.3 upgrade ( a little handholding requested) PART 2 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. 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. Are they any sharing concerns that I need to be aware of? 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? 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. 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 ---------------------------------------------------------------------- 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
