Thanks for the info Tom. 
I had planned to use the ZONEEDIT to update my DDDEFs as well, so thanks for 
that confirmation.

Ross 


> On Dec 14, 2023, at 12:44 PM, Tom Marchant 
> <[email protected]> wrote:
> 
> I should have added that when I clone zones, I like to copy the SMPLOG as 
> well, so that the full history is preserved. Don't forget to define the 
> disposition for SMPLOG as MOD or the SMPLOG will be useless.
> 
> -- 
> Tom Marchant
> 
> On Thu, 14 Dec 2023 12:31:15 -0600, Tom Marchant <[email protected]> 
> wrote:
> 
>> Create a new ZONEINDEX in the Global zone for each new zone (target and 
>> DLIB), and relate them to each other.
>> 
>> If each zone is in its own CSI you can copy with IDCAMS REPRO. Otherwise use 
>> ZONECOPY.
>> 
>> You can use ZONEEDIT to change the DDDEFs in your new zone(s). Don't forget 
>> that the target zone needs the DLIB data sets, must have their own SMPLTS, 
>> SMPMTS, SMPSTS, SMPSCDS. These can also be defined to your DLIB zone. IIRC, 
>> only the SCDS is required in the DLIB zone.
>> 
>> Your target and DLIB zones will need DDDEFs for the SMPPTS
>> 
>> Be careful that you have not left any DDDEFs pointing to the previous zone's 
>> data sets.
>> 
>> -- 
>> Tom Marchant
>> 
>> On Thu, 14 Dec 2023 11:27:16 -0600, Ross Vaughn <[email protected]> 
>> wrote:
>> 
>>> I’m upgrading a product in my DB2v13 global zone.  I plan to use my 
>>> existing target & DLIB zones and just update my DDDEFs to point to my new 
>>> dataset names.  
>>> My question is - if I want to create new CSI’s (copied from my existing 
>>> CSIs) for the target & DLIB what’s the best way to point the target & DLIB 
>>> to those new CSI’s?   My thought is using new CSI’s would allow me to keep 
>>> the previous FMID around if I needed it for any reason.
>>> 
>>> Thanks,
>>> Ross Vaughn
>>> OneMain Financial
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> ----------------------------------------------------------------------
>>> For IBM-MAIN subscribe / signoff / archive access instructions,
>>> send email to [email protected] with the message: INFO IBM-MAIN
>> 
>> ----------------------------------------------------------------------
>> For IBM-MAIN subscribe / signoff / archive access instructions,
>> send email to [email protected] with the message: INFO IBM-MAIN
> 
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to [email protected] with the message: INFO IBM-MAIN

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to