Multople zone in SMPE
Hello, By the time of server pac installation, we just defined one target and one distribution zone. But if we create two RES volume, for applying maintenance then in this we case we would require two target and distribution zone. And in this way we always apply maintenance not on running RES volume. We always do on another RES volume. Can anybody help me, how to setup multiple zone to follow above concept. Regards Saurabh Khandelwal -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
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 lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Multople zone in SMPE
Thanks For help. Now I will try creating multiple target CSI and update you, I encountered any error. Regards Saurabh Khandelwal On 4/7/2011 6:50 PM, Walter Marguccio wrote: 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 lists...@bama.ua.edu 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 lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Multople zone in SMPE
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 * SETBDY(Dlibzone). UCLIN. 000693 REP DZONE(Dlibzone) 000693 RELATED(cloned-tgtzone) SREL() OPTIONS(optos). ENDUCL. ACCEPT . /* // -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Walter Marguccio Sent: Thursday, April 07, 2011 9:21 AM To: IBM-MAIN@bama.ua.edu 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 lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm
Re: Multople zone in SMPE
-snip--- Can anybody help me, how to setup multiple zone to follow above concept. -unsnip What I always did was this: 1. Target zones was named to reflect the IPL folume set that it represented. For example, if my IPL volume was IPL001, that was the name of the target zone. 2. DLIB zones were named to reflect the first volume of the DLIB set. 3. The DLIB set for the IPL volumes were related in SMP/E. 4. ONLY one DLIB set was maintained. Once a new release appeared in shop, the old DLIB set was replaced and the new IPL set was defined. At that point, maintenance, other that critical stuff, was ceased on the existing IPL set. 5. The IPL set was defined using actual VOL-SER information, whereas the DLIB set was defined using a separate UCAT; HLQ's were changed such that the UCAT was used, rather than the MCAT. 6. In most cases, though not always, IPL set vol-ser information was altered to the new set using a ZONEEDIT under SMP/E. It may sound complicated but in our shop, no VOLSER is used twice in a release or between releases for an IPL set. Releawse 1.10 was named IP110a, IPL110B and IPL11C, and release 12 is being named IPL12A, IPL12B and IPL12C. VOLSER substitutions in PARMLIB and cataloging with VOL(**) DEVT(3390) save a LOT of pain. If a DSNAME is changed or added, we include both the new and old names in the catalog during the transition and our users are ABSOLUTELY FORBIDDEN from referring to datasets on the IPL volumes except by name. On rare occaissions, we'll install an alias for a dataset to make the transition between releases but since SYSTEMS controls the compile/link procs, we get those updated as soon as possible to reflect any changes and the dsname aliases go away. Our management is very inflexible; we are not allowed to make changes that require the applications staff to change anything. When System Determined Blocksize became availabe, the SYSTEMS staff had to update all the procs, both ours and applications', to take advantage of this. I know, parts of this are short-sighted and overly stupid, but that's the way it works here. Rick -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Multople zone in SMPE
Assuming your target/dlib zones are in a separate VSAM datasets: 1) Copy/rename them using DF/DSS. You'll also need to make copies of the related SMP/E datasets (ie, SMPLTS, SMPMTS, SMPSCDS, SMPSTS, maybe SMPLOG and SMPLOGA depending on how you are set up) and the target and distribution libraries. 2) Rename the new zones using SMP/e: SET BDY(GLOBAL). ZONERENAME (old target zone name) TO(new target zone name) NEWDATASET(new target zone VSAM dataset name). ZONERENAME (old dlib zone name) TO(new dlib zone name) NEWDATASET(new dlib zone VSAM dataset name). 3) Link the new target/dlib zones SET BDY(new target zone name). UCLIN. REP TZONE(new target zone name) RELATED(new dlib zone name) ZDESC(new description if needed). ENDUCL. SET BDY(new dlib zone name). UCLIN. REP DZONE(new dlib zone name) RELATED(new target zone name) ZDESC(new description if needed). ENDUCL. 4) Update the DDDEFs in the new zones to point to the new datasets that the copied SMP/e environment reflects. Use SMP/e ZONEEDIT DDDEF. Don't forget the new SMP* files. SET BDY(new target zone name). /* For IPL-resident files */ ZONEEDIT DDDEF. IF (VOLUME=old IPL volser). CHANGE VOLUME(*,new IPL volser). ENDZONEEDIT. /* For other (non-IPL volume files */ ZONEEDIT DDDEF. CHANGE DATASET(old dsn prefix*,new dsn prefix*). ENDZONEEDIT. SET BDY(new dlib zone name). ZONEEDIT DDDEF. CHANGE DATASET(old dsn prefix*,new DSN prefix*). ENDZONEEDIT. For a simple example, if you copied you dlib's from, say, SYS1.A* to SYS1.MAINT.A* and copied the SMPLTS, SMPMTS etc. from SMPE.SMP* to SMPE.MAINT.SMP* then above for the dlib zone would look like: SET BDY(new dlib zone name). ZONEEDIT DDDEF. CHANGE DATASET(SYS1.A*,SYS1.MAINT.A*). CHANGE DATASET(SMPE.SMP*,SMPE.MAINT.SMP*). ENDZONEEDIT. You'll also need to cater for OMVS pathnames. The root filesystem for the maintenance system (and any ancilliary filesystems) would be mounted under a 'service' mountpoint on the system installing maintenance, usually called /service. So you'll need to ZONEEDIT DDDEF PATH as well: ZONEEDIT DDDEF. CHANGE PATH(*,'/service'*). ENDZONEEDIT. Cheers, Ant. Northern Territory Govt., Australia -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of SAURABH KHANDELWAL Sent: Thursday, 7 April 2011 7:59 PM To: IBM-MAIN@bama.ua.edu Subject: Multople zone in SMPE Hello, By the time of server pac installation, we just defined one target and one distribution zone. But if we create two RES volume, for applying maintenance then in this we case we would require two target and distribution zone. And in this way we always apply maintenance not on running RES volume. We always do on another RES volume. Can anybody help me, how to setup multiple zone to follow above concept. Regards Saurabh Khandelwal -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu 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 lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
