Re: [EXTERNAL] Re: HLQ change of SMP/E files
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() etc. and then" >> "DEL/REP/ADD DDDEF() DA() 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? >&g
Re: [EXTERNAL] Re: HLQ change of SMP/E files
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() etc. and then" >> "DEL/REP/ADD DDDEF() DA() 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:
Re: [EXTERNAL] Re: HLQ change of SMP/E files
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() etc. and then" > "DEL/REP/ADD DDDEF() DA() 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 >
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() etc. and then" > "DEL/REP/ADD DDDEF() DA() 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. >> >&
Re: [EXTERNAL] Re: HLQ change of SMP/E files
On 5/2/2018 1:26 PM, Sankaranarayanan, Vignesh wrote: 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? Each target and dlib zone has its own ZONEINDEX, and each ZONEINDEX points to the CSI data set that contains that zone. Therefore, if you change the name of the CSI data set that contains a particular zone, then you need to update the ZONEINDEX for that zone. 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
Re: [EXTERNAL] Re: HLQ change of SMP/E files
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() etc. and then" "DEL/REP/ADD DDDEF() DA() 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
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() etc. and then" "DEL/REP/ADD DDDEF() DA() 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
Re: [EXTERNAL] Re: HLQ change of SMP/E files
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
Re: [EXTERNAL] Re: HLQ change of SMP/E files
feels like a friday :( sorry I intended to respond to this POST : z/OS 1.13 maintenance concern.May 2, 2018 7:56 AM Carmen Vitullo - Original Message - From: "Carmen Vitullo" <cvitu...@hughes.net> To: IBM-MAIN@LISTSERV.UA.EDU Sent: Wednesday, May 2, 2018 7:54:01 AM Subject: Re: [EXTERNAL] Re: HLQ change of SMP/E files In a case like this I'd like to use the fixcat's like FIXCAT(IBM.Coexistence.z/OS.V2R1 FIXCAT + (IBM.Coexistence.z/OS.V2R2) that are available now, it may produce a lot of required PTF's but SHOPZ + fixcats for required service for 2.1 and 2.2 ? or choose the upgrade option in the PSP buckets ? Carmen Vitullo - Original Message - From: "Kurt Quackenbush" <ku...@us.ibm.com> To: IBM-MAIN@LISTSERV.UA.EDU Sent: Wednesday, May 2, 2018 7:41:07 AM Subject: Re: [EXTERNAL] Re: HLQ change of SMP/E files On 5/1/2018 9:53 AM, Sankaranarayanan, Vignesh wrote: > Ooh... almost forgot the other question - is there a way to test run > this, equivalent of ADRDSSU's TYPRUN=NORUN? No, no CHECK operand on ZONEEDIT. Frankly its a pretty safe operation, but if you're concerned then make a copy of your CSI data set(s) that contain the target and dlib zones and try it out on the copy first. 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 -- 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
Re: [EXTERNAL] Re: HLQ change of SMP/E files
In a case like this I'd like to use the fixcat's like FIXCAT(IBM.Coexistence.z/OS.V2R1 FIXCAT + (IBM.Coexistence.z/OS.V2R2) that are available now, it may produce a lot of required PTF's but SHOPZ + fixcats for required service for 2.1 and 2.2 ? or choose the upgrade option in the PSP buckets ? Carmen Vitullo - Original Message - From: "Kurt Quackenbush" <ku...@us.ibm.com> To: IBM-MAIN@LISTSERV.UA.EDU Sent: Wednesday, May 2, 2018 7:41:07 AM Subject: Re: [EXTERNAL] Re: HLQ change of SMP/E files On 5/1/2018 9:53 AM, Sankaranarayanan, Vignesh wrote: > Ooh... almost forgot the other question - is there a way to test run > this, equivalent of ADRDSSU's TYPRUN=NORUN? No, no CHECK operand on ZONEEDIT. Frankly its a pretty safe operation, but if you're concerned then make a copy of your CSI data set(s) that contain the target and dlib zones and try it out on the copy first. 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 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: [EXTERNAL] Re: HLQ change of SMP/E files
On 5/1/2018 9:53 AM, Sankaranarayanan, Vignesh wrote: Ooh... almost forgot the other question - is there a way to test run this, equivalent of ADRDSSU's TYPRUN=NORUN? No, no CHECK operand on ZONEEDIT. Frankly its a pretty safe operation, but if you're concerned then make a copy of your CSI data set(s) that contain the target and dlib zones and try it out on the copy first. 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
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
Re: [EXTERNAL] Re: HLQ change of SMP/E files
Yes, and there is more to it than that. ZONEEXPORT, UCLIN, ZONEDELETE, DEL/ADD/REP ZONEINDEX GZONE/DZONE/TZONE, ENDUCL, ZONEIMPORT ... RELATED() etc. and then DEL/REP/ADD DDDEF() DA() SHR to point at the DDDEF 'WHYNOT' DSNs in the GZONE/DZONE/TZONE. Chris Poncelet (retired sysprog) On 01/05/2018 17:03, retired mainframer wrote: > There are always other things to be mindful of. Think of other places the > HLQ WHYNOT could appear. > > Do any of the SYSMODs for this product contain ++JCLIN statements? Did the > vendor supply any JCLIN commands? > > Do any of the product elements that contain text, such as MAC, SRC, or DATA, > contain dataset names (some products include sample JCL procedures)? > >> -Original Message- >> From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf >> Of Sankaranarayanan, Vignesh >> Sent: Tuesday, May 01, 2018 6:53 AM >> To: IBM-MAIN@LISTSERV.UA.EDU >> Subject: Re: [EXTERNAL] Re: HLQ change of SMP/E files >> >> Thanks John. Hope you're doing alright. >> >> So will a ZONEEDIT be all, or are there other things to be mindful of? >> >> – Vignesh >> Mainframe Infrastructure >> >> -Original Message- >> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On >> Behalf Of John McKown >> Sent: Tuesday 01-May-2018 18:46 >> To: IBM-MAIN@LISTSERV.UA.EDU >> Subject: [EXTERNAL] Re: HLQ change of SMP/E files >> >> On Tue, May 1, 2018 at 7:44 AM, Sankaranarayanan, Vignesh < >> vignesh.v.sankaranaraya...@marks-and-spencer.com> wrote: >> >>> Hello All, >>> >>> A scenario for your consideration... >>> >>> Let's assume I have SMPE.* as the usual location for my SMP/E files >>> (CSI, SMP*, DIST and TARG files). >>> There is now a product installed elsewhere... at WHYNOT.* >>> >>> If I am to move everything from WHYNOT.* to SMPE.*, will DDDEFs be the >>> only thing to fully list out and modify? >>> Both the HLQs just go to different VOLSER, i.e., they're not SMS managed. >>> >>> Thoughts... ? Is this possible, is this worth trying? >>> >> I'm a bit light headed today due to a medical procedure yesterday. But if >> my brain is not >> lying to me, you want to do a "mass rename" of the DDDEFs in SMP/E. If so, >> then look at >> the SMP/E ZONEEDIT command. >> >> SET BOUNDRY(...) >> ZONEEDIT DDDEF >> CHANGE DATASET(WHYNOT.*,SMPE.*) >> ENDZONEDIT >> > -- > 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
Re: [EXTERNAL] Re: HLQ change of SMP/E files
On Tue, 1 May 2018 09:03:56 -0700, retired mainframer wrote: >Do any of the SYSMODs for this product contain ++JCLIN statements? >Did the vendor supply any JCLIN commands? That shouldn't matter. JCLIN processing only looks at the low level qualifiers. As John pointed out, ZONEEDIT can be used to change many DDDEFs with one command. I have used it and found that it works quite well. Of course, you would also have to rename the data sets. AFAIK, there is no ZONEEDIT CHECK, but if you want to try it out, you could always install a product into a throw-away zone and experiment there. Or define some new DDDEFs with data set names that may not even exist, and that are named differently than your existing data set names. You could define DDNAMEs FOO1, FOO2, etc, with DSNAMEs FOO.FOO1, FOO.FOO2, etc, and use ZONEEDIT to change the DSNAMES to BAR.FOO1, BAR.FOO2, etc. When you are done delete those DDDEFs -- Tom Marchant -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: [EXTERNAL] Re: HLQ change of SMP/E files
There are always other things to be mindful of. Think of other places the HLQ WHYNOT could appear. Do any of the SYSMODs for this product contain ++JCLIN statements? Did the vendor supply any JCLIN commands? Do any of the product elements that contain text, such as MAC, SRC, or DATA, contain dataset names (some products include sample JCL procedures)? > -Original Message- > From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf > Of Sankaranarayanan, Vignesh > Sent: Tuesday, May 01, 2018 6:53 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: [EXTERNAL] Re: HLQ change of SMP/E files > > Thanks John. Hope you're doing alright. > > So will a ZONEEDIT be all, or are there other things to be mindful of? > > – Vignesh > Mainframe Infrastructure > > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of John McKown > Sent: Tuesday 01-May-2018 18:46 > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: [EXTERNAL] Re: HLQ change of SMP/E files > > On Tue, May 1, 2018 at 7:44 AM, Sankaranarayanan, Vignesh < > vignesh.v.sankaranaraya...@marks-and-spencer.com> wrote: > > > Hello All, > > > > A scenario for your consideration... > > > > Let's assume I have SMPE.* as the usual location for my SMP/E files > > (CSI, SMP*, DIST and TARG files). > > There is now a product installed elsewhere... at WHYNOT.* > > > > If I am to move everything from WHYNOT.* to SMPE.*, will DDDEFs be the > > only thing to fully list out and modify? > > Both the HLQs just go to different VOLSER, i.e., they're not SMS managed. > > > > Thoughts... ? Is this possible, is this worth trying? > > > > I'm a bit light headed today due to a medical procedure yesterday. But if my > brain is not > lying to me, you want to do a "mass rename" of the DDDEFs in SMP/E. If so, > then look at > the SMP/E ZONEEDIT command. > > SET BOUNDRY(...) > ZONEEDIT DDDEF > CHANGE DATASET(WHYNOT.*,SMPE.*) > ENDZONEDIT > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: HLQ change of SMP/E files
On Tue, 1 May 2018 12:44:58 +, Sankaranarayanan, Vignesh wrote: > >Let's assume I have SMPE.* as the usual location for my SMP/E files (CSI, >SMP*, DIST and TARG files). >There is now a product installed elsewhere... at WHYNOT.* > >If I am to move everything from WHYNOT.* to SMPE.*, will DDDEFs be the only >thing to fully list out and modify? >Both the HLQs just go to different VOLSER, i.e., they're not SMS managed. > >Thoughts... ? Is this possible, is this worth trying? > Ih the past, for a new installation, I have relied on tailoring the JCL, both DD statements and SMPCNTL, that creates the CSI. Nowadays, "DD *,SYMBOLS=..." could facilitate this. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: [EXTERNAL] Re: HLQ change of SMP/E files
On Tue, May 1, 2018 at 8:54 AM, Sankaranarayanan, Vignesh < vignesh.v.sankaranaraya...@marks-and-spencer.com> wrote: > Ooh... almost forgot the other question - is there a way to test run this, > equivalent of ADRDSSU's TYPRUN=NORUN? > My suggestion is to first read the documentation that I pointed you to. I'm not an expert. I haven't used this very much at all. > > – Vignesh > Mainframe Infrastructure > > -- We all have skeletons in our closet. Mine are so old, they have osteoporosis. Maranatha! <>< John McKown -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: [EXTERNAL] Re: HLQ change of SMP/E files
Ooh... almost forgot the other question - is there a way to test run this, equivalent of ADRDSSU's TYPRUN=NORUN? – Vignesh Mainframe Infrastructure -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Sankaranarayanan, Vignesh Sent: Tuesday 01-May-2018 19:23 To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: [EXTERNAL] Re: HLQ change of SMP/E files Thanks John. Hope you're doing alright. So will a ZONEEDIT be all, or are there other things to be mindful of? – Vignesh Mainframe Infrastructure -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of John McKown Sent: Tuesday 01-May-2018 18:46 To: IBM-MAIN@LISTSERV.UA.EDU Subject: [EXTERNAL] Re: HLQ change of SMP/E files On Tue, May 1, 2018 at 7:44 AM, Sankaranarayanan, Vignesh < vignesh.v.sankaranaraya...@marks-and-spencer.com> wrote: > Hello All, > > A scenario for your consideration... > > Let's assume I have SMPE.* as the usual location for my SMP/E files > (CSI, SMP*, DIST and TARG files). > There is now a product installed elsewhere... at WHYNOT.* > > If I am to move everything from WHYNOT.* to SMPE.*, will DDDEFs be the > only thing to fully list out and modify? > Both the HLQs just go to different VOLSER, i.e., they're not SMS managed. > > Thoughts... ? Is this possible, is this worth trying? > I'm a bit light headed today due to a medical procedure yesterday. But if my brain is not lying to me, you want to do a "mass rename" of the DDDEFs in SMP/E. If so, then look at the SMP/E ZONEEDIT command. SET BOUNDRY(...) ZONEEDIT DDDEF CHANGE DATASET(WHYNOT.*,SMPE.*) ENDZONEDIT ref: https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.1.0/com.ibm.zos.v2r1.gim1000/chpzed.htm (start of doc) ref: https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.1.0/com.ibm.zos.v2r1.gim1000/zedex2.htm (example) > > - Vignesh > Mainframe Infrastructure > > > MARKSANDSPENCER.COM > > -- We all have skeletons in our closet. Mine are so old, they have osteoporosis. Maranatha! <>< John McKown -- 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
Re: [EXTERNAL] Re: HLQ change of SMP/E files
Thanks John. Hope you're doing alright. So will a ZONEEDIT be all, or are there other things to be mindful of? – Vignesh Mainframe Infrastructure -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of John McKown Sent: Tuesday 01-May-2018 18:46 To: IBM-MAIN@LISTSERV.UA.EDU Subject: [EXTERNAL] Re: HLQ change of SMP/E files On Tue, May 1, 2018 at 7:44 AM, Sankaranarayanan, Vignesh < vignesh.v.sankaranaraya...@marks-and-spencer.com> wrote: > Hello All, > > A scenario for your consideration... > > Let's assume I have SMPE.* as the usual location for my SMP/E files > (CSI, SMP*, DIST and TARG files). > There is now a product installed elsewhere... at WHYNOT.* > > If I am to move everything from WHYNOT.* to SMPE.*, will DDDEFs be the > only thing to fully list out and modify? > Both the HLQs just go to different VOLSER, i.e., they're not SMS managed. > > Thoughts... ? Is this possible, is this worth trying? > I'm a bit light headed today due to a medical procedure yesterday. But if my brain is not lying to me, you want to do a "mass rename" of the DDDEFs in SMP/E. If so, then look at the SMP/E ZONEEDIT command. SET BOUNDRY(...) ZONEEDIT DDDEF CHANGE DATASET(WHYNOT.*,SMPE.*) ENDZONEDIT ref: https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.1.0/com.ibm.zos.v2r1.gim1000/chpzed.htm (start of doc) ref: https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.1.0/com.ibm.zos.v2r1.gim1000/zedex2.htm (example) > > - Vignesh > Mainframe Infrastructure > > > MARKSANDSPENCER.COM > > -- We all have skeletons in our closet. Mine are so old, they have osteoporosis. Maranatha! <>< John McKown -- 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
Re: HLQ change of SMP/E files
On Tue, May 1, 2018 at 7:44 AM, Sankaranarayanan, Vignesh < vignesh.v.sankaranaraya...@marks-and-spencer.com> wrote: > Hello All, > > A scenario for your consideration... > > Let's assume I have SMPE.* as the usual location for my SMP/E files (CSI, > SMP*, DIST and TARG files). > There is now a product installed elsewhere... at WHYNOT.* > > If I am to move everything from WHYNOT.* to SMPE.*, will DDDEFs be the > only thing to fully list out and modify? > Both the HLQs just go to different VOLSER, i.e., they're not SMS managed. > > Thoughts... ? Is this possible, is this worth trying? > I'm a bit light headed today due to a medical procedure yesterday. But if my brain is not lying to me, you want to do a "mass rename" of the DDDEFs in SMP/E. If so, then look at the SMP/E ZONEEDIT command. SET BOUNDRY(...) ZONEEDIT DDDEF CHANGE DATASET(WHYNOT.*,SMPE.*) ENDZONEDIT ref: https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.1.0/com.ibm.zos.v2r1.gim1000/chpzed.htm (start of doc) ref: https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.1.0/com.ibm.zos.v2r1.gim1000/zedex2.htm (example) > > - Vignesh > Mainframe Infrastructure > > > MARKSANDSPENCER.COM > > -- We all have skeletons in our closet. Mine are so old, they have osteoporosis. Maranatha! <>< John McKown -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
HLQ change of SMP/E files
Hello All, A scenario for your consideration... Let's assume I have SMPE.* as the usual location for my SMP/E files (CSI, SMP*, DIST and TARG files). There is now a product installed elsewhere... at WHYNOT.* If I am to move everything from WHYNOT.* to SMPE.*, will DDDEFs be the only thing to fully list out and modify? Both the HLQs just go to different VOLSER, i.e., they're not SMS managed. Thoughts... ? Is this possible, is this worth trying? - Vignesh Mainframe Infrastructure 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
