We use the GENIPLER program to create various CMS NSSes and map different
minidisks. For the other segments we give them unique names and update the
SYSTEM SEGID file. Then users can IPL CMS (current production), IPL CMS22TST
(test new code), IPL CMS22 (SFS and TCP/IP SVMs) and IPL CMS22OLD (just in
case).
samples:
Segment names used by the various CMS22 IPLers:
CMSFIL2A
INSTSGD2
SVM22
SCEE22
INSTSG22
SCEEX22
INSTSGB2
CMSFILB2
CMSPIP22
CMSVML2F
CMSVML22
CMSFILD2
SCEEX22E
CMSFIL22
GENSAVE EXEC extract:
select;
when iplername = 'CMS22TST' |,
iplername = 'CMS22' |,
iplername = 'CMS' then do
queue '/define console 009'
queue '/detach 190 19d 19e'
queue '/define reader 00c'
queue '&spool 00c class *'
queue '/define punch 00d'
queue '/define printer 00e'
queue 'defparm autocr'
queue 'SET IMSG OFF'
queue 'LINK $CMSLIVE 2F90 190 RR'
queue 'LINK $CMSLIVE 229D 19D RR'
queue 'LINK $CMSLIVE 2E9E 19E RR'
queue 'SET IMSG ON'
queue 'IPL CMS22F'
queue
'CONWAIT'
GENIPLER iplername function
end;
when iplername = 'CMS22OLD' then do
queue '/define console 009'
queue '/detach 190 19d 19e'
queue '/define reader 00c'
queue '&spool 00c class *'
queue '/define punch 00d'
queue '/define printer 00e'
queue 'defparm autocr'
queue 'SET IMSG OFF'
queue 'LINK $CMSLIVE 2E90 190 RR'
queue 'LINK $CMSLIVE 229D 19D RR'
queue 'LINK $CMSLIVE 2E9E 19E RR'
queue 'SET IMSG ON'
queue 'IPL CMS22E'
queue
'CONWAIT'
GENIPLER iplername function
end;
when iplername = 'CMS21TST' |,
I hope you get the idea.
-----Original Message-----
From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf
Of Colin Allinson
Sent: Thursday, May 10, 2007 11:11 AM
To: [email protected]
Subject: Testing new CMS / CMS components
When testing a new level of CMS (or one of its components) then we,
typically, need to test on one of our production systems for selected users
only before the full roll-out.
We already have a process to save the CMS into a specific name and a
SWAPCMS EXEC that will link in the correct CMS disks and IPL the matching level
of CMS.
Where we have already hit problems with this is the other saved
segments (VMLIB etc.).
I was thinking of trying to have them built with a release dependant
name and then extend the SWAPCMS exec to do the appropriate SEGMENT
RELEASE/ASSIGN commands.
The question I have is what is the best way to get the renamed segments
into place? Is it better to change the build to generate the release dependant
names or is it better to do this with, say, DCSSBKUP/DCSSRSAV?
Does anyone have a suggested procedure they would like to share with me
to save me rolling my own?
Thanks in advance.
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
--------------------------------------------------------
If you are not an intended recipient of this e-mail, please notify the sender,
delete it and do not read, act upon, print, disclose, copy, retain or
redistribute it. Click here for important additional terms relating to this
e-mail. http://www.ml.com/email_terms/
--------------------------------------------------------
