Colin, Also, CA's V/Seg-PLUS can help you with this ... it support transparent "aliasing" of segment names (user JOE says "IPL CMS" ... but a V/Seg alias say CMS for user JOE is really CMS22). <<< snip >>> LOGON JRTEST z/VM Version 5 Release 2.0, Service Level 0602 (64-bit), built on IBM Virtualization Technology There is no logmsg data FILES: NO RDR, NO PRT, NO PUN LOGON AT 06:57:08 EDT FRIDAY 05/11/07 VSPSGX1957I IPL of CMS replaced with CMSJR DMSACC724I 19E replaces Y (19E) DMSACP723I Y (19E) R/O z/VM V5.2.0 2006-12-15 14:31 Ready; <<< snip >>> JR (Steven) Imler CA Senior Software Engineer Tel: +1 703 708 3479 Fax: +1 703 708 3267 [EMAIL PROTECTED]
________________________________ From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Colin Allinson Sent: Friday, May 11, 2007 05:48 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Testing new CMS / CMS components Thanks to everyone (particularly James Stracka & Kris Buelens) for their help on this. Because, sort of like Kris, we have our CMS disks for each version separated - this was a lot easier than I thought. The first question was "should I save the segment under a new name or try to restore them with a new name?". The resounding answer to this was to save them with a new name - which is the way I have gone. Once I had done this then, what I had not appreciated but might have realised if I had thought about it, is that I need do nothing more because the SYSTEM SEGID on the 190 disk will pull in the correct segments automatically. I works a dream - all I had to do was copy the NSS's from my build system and restore them on production (at the same time as copying the CMS disks and saving CMSnn). For anyone who is interested - the way we do things is to have each set of CMS disks owned by a dummy user ($$CMSnn). We also save CMS as CMSnn. For initial testing the user can link to the appropriate disks and IPL the correct CMSnn. When we are ready for a general roll-out we just change MAINT links to the new CMS-level disks and resave as CMS. For between release testing we use alternate disks an the $$CMSnn owner. Anyway - thanks everyone - It works well for us. With best regards / mit den besten Grüßen, Colin G Allinson Technical Manager VM Amadeus Data Processing GmbH T +49 (0) 8122-43 49 75 F +49 (0) 8122-43 32 60 [EMAIL PROTECTED] http://www.amadeus.com IMPORTANT - CONFIDENTIALITY NOTICE - This e-mail is intended only for the use of the individual or entity shown above as addressees . It may contain information which is privileged, confidential or otherwise protected from disclosure under applicable laws . If the reader of this transmission is not the intended recipient, you are hereby notified that any dissemination, printing, distribution, copying, disclosure or the taking of any action in reliance on the contents of this information is strictly prohibited. If you have received this transmission in error, please immediately notify us by reply e-mail or using the address below and delete the message and any attachments from your system . Amadeus Data Processing GmbH Geschäftsführer: Eberhard Haag Sitz der Gesellschaft: Erding HR München 48 199 Berghamer Strasse 6 85435 Erding Germany
