Hi Simon, No, aliasing would not help: the original SMP/E datasets could then be updated via their aliases. I'm guessing that the CSI and its associated SMP/E datasets are for a production system. If the intention is only to read them, this can be done directly from the production CSI SMP/E environment without cloning. But if the intention is to update these datasets (e.g. by RECEIVE'ing, APPLYing APARs PTFs or USERMODs, or REJECTing them etc.) - without impacting the production system itself - then the production CSI and all its SMP/E datasets need to be cloned. This way any updates can be applied and 'run-time' checked via the cloned CSI and its SMP/E datasets, without 'hitting' the production system. Consider the following. Suppose that PTF001 to PTF500 have been applied in production. Applying PTF501 results in a QA regression test failure and is rejected. PTF501's code changes show it could not be causing the QA failure. Hence a previous PTF is in error (PE) but was not detected until PTF501 was applied. The objective now is not to fix PTF501, but to find which previous PTF introduces the error. A quick way to do this is to clone the production system's *original* CSI and SMP/E datasets, APPLY its PTFs (typically PTF001 to PTF250 first, etc.) until the PTF that introduces the error is found. It can then be marked PE in production. Next, create a HIPER to fix it, include PTF501 and, if QA-checked now all OK, apply and distribute. This works only if the cloned CSI and its datasets are physically separate from the original production ones - not aliases of them (or vice versa). Cheers, Chris Poncelet
On 04/05/2018 14:34, Wheeler, Simon wrote: > Hi, > > Maybe it would be possible to rename the datasets as desired and create > dataset aliases for the old names, so no SMP/E changes would be required? > > thanks, > Simon > > > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of CM Poncelet > Sent: 03 May 2018 16:27 > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: [EXTERNAL] Re: HLQ change of SMP/E files > > Hi Vignesh, > > Yes, all the existing datasets can be copied - i.e. 'cloned' - to new > datasets with new names. Both the DZONE and TZONE of the new CSI then need to > be renamed and pointed at each other, and all the new CSI's DDDEFs need to be > pointed at their new dataset names. It is all done via UCL. > > Bear in mind that a cloned CSI's GLOBAL zone is still pointing at the > original CSI's DZONE and TZONE, and this needs to be changed to point it at > the cloned CSI's DZONE and TZONE. > > Cheers, Chris Poncelet > > > > On 03/05/2018 05:17, Sankaranarayanan, Vignesh wrote: >> Hi Chris, >> >> Is it not possible to move the existing datasets into their new names >> (rename), and do the required UCL work. >> >> – Vignesh >> Mainframe Infrastructure >> >> -----Original Message----- >> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] >> On Behalf Of CM Poncelet >> Sent: Thursday 03-May-2018 09:06 >> To: IBM-MAIN@LISTSERV.UA.EDU >> Subject: Re: [EXTERNAL] Re: HLQ change of SMP/E files >> >> 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 >> >> ---------------------------------------------------------------------- >> 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 > > ****************************************************************** > SSE and associated brands: Southern Electric, Scottish Hydro, SWALEC and > Atlantic are all trading names of SSE Electricity Limited registered in > England and Wales number 04094263 (supply of electricity and Feed-In > Tariffs); Southern Electric Gas Limited registered in England and Wales > number 02716495 (supply of gas); SSE Retail Telecoms Limited registered in > England and Wales number 10086511 (supply of home phone and broadband); SSE > Home Services Limited registered in Scotland number SC292102 (boiler and > heating repair, servicing, cover, boiler Installations and electrical wiring > cover); SSE Energy Solutions Limited registered in Scotland number SC386054 > (energy efficiency installations and insulation products). All members of the > SSE Group. The registered office of SSE Electricity Limited, Southern > Electric Gas Limited and SSE Retail Telecoms Limited is No. 1 Forbury Place, > 43 Forbury Road, Reading, RG1 3JH. The registered office of SSE Home Services > Limited and SSE Energy Solutions Limited is Inveralmond House, 200 Dunkeld > Road, Perth, PH1 3AQ. SSE Electricity Limited is an appointed representative > of SSE Home Services Limited. SSE Home Services Limited is authorised and > regulated by the Financial Conduct Authority (FCA) under reference number > 695476. You can check this on the Financial Services Register by visiting the > FCA website. > ****************************************************************** > > > ---------------------------------------------------------------------- > 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
