You also need to the new target zone to the global zone :
SET BDY(GLOBAL)
/* ADD THE ADDITIONAL ZONE */
/* TO THE GLOBAL ZONE */
.
UCLIN .
ADD GLOBALZONE
ZONEINDEX(
(cloned-tgzone,new.taget.zone.dsn)
) .
ENDUCL .
*
And copy the original zone into the newzone before doing the replace dddefs to
pick up all the maint:
ZONECOPY (Tgtzone)
INTO (cloned-tgzone)
RELATED (DLIBZONE)
OPTIONS(OPTS)
.
When applying maintenance to the new zone,
The ACCEPT step needs to relate the DLIB with the current target:
//SMPCNTL DD *
SET BDY(Dlibzone).
UCLIN. 000693
REP DZONE(Dlibzone)
000693
RELATED(cloned-tgtzone) SREL(ssss) OPTIONS(optos).
ENDUCL.
ACCEPT
.....
/*
//
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of
Walter Marguccio
Sent: Thursday, April 07, 2011 9:21 AM
To: [email protected]
Subject: Re: Multople zone in SMPE
> Can anybody help me, how to setup multiple zone to follow above concept.
Once I receive a new z/OS with the ServerPac or SystemPac, I use this steps
to clone the delivered target zone:
//COPYSMP EXEC PGM=ADRDSSU
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
COPY DATASET( -
INCLUDE( -
SMPE11.tgtzone_name.*, -
)) -
RENUNC( -
(SMPE11.tgtzone.*,SMPE11.cloned_tgtzone.*) -
) -
OUTDYNAM(myvol) -
TOL(ENQF) CATALOG
Above step clones the target zone's CSI, along with its SMPxTS.
The datasets' 2nd qualifier equals to the "tgtzone" or "cloned_tgtzone" names.
//ADDZINDX EXEC PGM=GIMSMP
//SMPCSI DD DISP=SHR,DSN=my.GLOBAL.CSI
//SYSPRINT DD SYSOUT=*
//SMPLOG DD DUMMY
//SMPOUT DD SYSOUT=*
//SMPCNTL DD *
SET BDY(GLOBAL) .
ZREN(tgtzone) TO(cloned_tgtzone) NEWDATASET(SMPE11.cloned_tgtzone.CSI).
SET BDY(cloned_tgtzone) .
ZEDIT DDDEF .
CHANGE VOLUME(sysres,cloned_sysres) .
ENDZEDIT .
UCLIN.
REP DDDEF(SMPLTS) DA(SMPE11.cloned_tgtzone.SMPLTS) .
REP DDDEF(SMPMTS) DA(SMPE11.cloned_tgtzone.SMPMTS) .
REP DDDEF(SMPSCDS) DA(SMPE11.cloned_tgtzone.SMPSCDS).
REP DDDEF(SMPSTS) DA(SMPE11.cloned_tgtzone.SMPSTS) .
ENDUCL.
The above step adds the "cloned_tgtzone' to the GLOBAL zone index, changes the
sysres to every DDDEFs belonging to "cloned_tgtzone", and changes the dataset
names of allSMPxTS accordingly.
I don't clone the DLIB zone, nor the DLIB volumes, since I leave one DLIB
zone/volume(s)
for x Target zones/volume(s) (where 'x' can be 2, 3, or 4)
HTH
Walter Marguccio
z/OS Systems Programmer
BELENUS LOB Informatic GmbH
Munich - Germany
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html