There is more to it than that if you are cloning (copying) a CSI into
another CSI. E.g.  
 
"ZONEEXPORT, UCLIN, ZONEDELETE, DEL/ADD/REP ZONEINDEX GZONE/DZONE/TZONE,"
"ENDUCL, ZONEIMPORT ... RELATED(<whatever zone>) etc. and then"
"DEL/REP/ADD DDDEF(<whatever>) DA(<WHYNOT.whatever else>) SHR to point at"
"the DDDEF 'WHYNOT' DSNs in the GZONE/DZONE/TZONE."

You need also to relate your cloned DZONE and TZONE to each other in the
cloned CSI, as in e.g.

SET BOUNDARY(DZONE)
.
ZONEIMPORT (DZONE) INFILE(IMPORTDZ) INTO(DZONE) RELATED(TZONE)
.
SET BOUNDARY(TZONE)
.
ZONEIMPORT (TZONE) INFILE(IMPORTTZ) INTO(TZONE) RELATED(DZONE)
.

All the original CSI's SMP/E datasets should be IEBCOPY'd or IEBGENER'd
to 'WHYNOT.*' datasets - and the cloned CSI's DDDEFs then updated to
point at the 'WHYNOT.*' datasets in its GLOBAL, DZONE and TZONE.
(Otherwise any RECEIVE, APPLY and ACCEPTs would be applied to the
original CSI's SMP/E datasets.)
 
Chris Poncelet (retired sysprog)
 
 


On 02/05/2018 18:27, Sankaranarayanan, Vignesh wrote:
> Hi Kurt,
>
> Thanks for this; the product is in its own target and dlip zones, product has 
> its own CSI.
> So the ZONEINDEX is for consideration only when TGT and DLIB have their own 
> zones, or even if they're all in a single product CSI?
>
> PS: Big fan of getting replies from various IBM development teams!!
>
> – Vignesh
> Mainframe Infrastructure
>
> -----Original Message-----
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On 
> Behalf Of Kurt Quackenbush
> Sent: Wednesday 02-May-2018 18:03
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: [EXTERNAL] Re: HLQ change of SMP/E files
>
> On 5/1/2018 9:51 AM, Sankaranarayanan, Vignesh wrote:
>
>> So will a ZONEEDIT be all, or are there other things to be mindful of?
> ZONEEDIT is all you need to update the data set names in the DDDEF entries 
> for the target and dlib data sets.  However, is this product installed in its 
> own target and dlib zones?  Are those zones in their own CSI data sets?  If 
> you'll be renaming the CSI data sets too, then you'll need to update the 
> ZONEINDEX subentries in the global zone, like
> this:
>
> SET BDY(GLOBAL).
> UCLIN.
> DEL GZONE ZONEINDEX((tgtzonename)).
> ADD GZONE ZONEINDEX((tgtzonename,WHYNOT.dataset.name.CSI,TARGET)).
> DEL GZONE ZONEINDEX((dlibzonename)).
> ADD GZONE ZONEINDEX((dlibzonename,WHYNOT.dataset.name.CSI,DLIB)).
> ENDUCL.
>
> Kurt Quackenbush -- IBM, SMP/E Development
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
> lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>
> MARKSANDSPENCER.COM
> ________________________________
>  Unless otherwise stated above:
> Marks and Spencer plc
> Registered Office:
> Waterside House
> 35 North Wharf Road
> London
> W2 1NW
>
> Registered No. 214436 in England and Wales.
>
> Telephone (020) 7935 4422
> Facsimile (020) 7487 2670
>
> www.marksandspencer.com
>
> Please note that electronic mail may be monitored.
>
> This e-mail is confidential. If you received it by mistake, please let us 
> know and then delete it from your system; you should not copy, disclose, or 
> distribute its contents to anyone nor act in reliance on this e-mail, as this 
> is prohibited and may be unlawful.
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Reply via email to