Re: SMP/E - Pointing Existing TARG & DLIB Zones To New CSI's

2023-12-15 Thread Ross Vaughn
Thanks Kurt. This will be helpful as well. Ross > On Dec 15, 2023, at 9:52 AM, Kurt Quackenbush wrote: > >  >> >> If he clones the existing target and dlib zones, updates the DDDEFs and >> receives the new version, will SMPE try to delete the old FMID and/or the >> contents of the

Re: SMP/E - Pointing Existing TARG & DLIB Zones To New CSI's

2023-12-15 Thread Kurt Quackenbush
> If he clones the existing target and dlib zones, updates the DDDEFs and > receives the new version, will SMPE try to delete the old FMID and/or the > contents of the existing libraries? Typically a new release of a product does delete the prior releases. If you are careful to update all

Re: SMP/E - Pointing Existing TARG & DLIB Zones To New CSI's

2023-12-14 Thread Michael Babcock
I work with Ross and can explain what he is trying to accomplish. We have a Db2 v13 Global zone for Db2 along with its associated target and DLIB zones. We have several Db2 related products (Admin Tool, etc) installed into the Db2 global with their own target and dlib zones. He wants to

Re: SMP/E - Pointing Existing TARG & DLIB Zones To New CSI's

2023-12-14 Thread Jousma, David
This statement is very confusing to me?So for DB2V13 is installed in its own global zone, with target and dlib zones.It’s the next part of your statement “use my existing target and dlib zones and update ddefs…” that is confusing me. It sounds like you are trying to marry your V13

Re: SMP/E - Pointing Existing TARG & DLIB Zones To New CSI's

2023-12-14 Thread Mark Zelden
You might want to look at the sysres cloning example on my web site / CBT file 434 also as that clones the SMP/E ZONEs with it. I don't clone the DLIB volser(s) / zones these days (haven't in many years), but you can easily see how it is done. See URL below. Regards, Mark -- Mark Zelden -

Re: SMP/E - Pointing Existing TARG & DLIB Zones To New CSI's

2023-12-14 Thread Ross Vaughn
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 > <000a2a8c2020-dmarc-requ...@listserv.ua.edu> wrote: > > I should have added that when I clone zones, I like to

Re: SMP/E - Pointing Existing TARG & DLIB Zones To New CSI's

2023-12-14 Thread Tom Marchant
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 wrote: >Create a

Re: SMP/E - Pointing Existing TARG & DLIB Zones To New CSI's

2023-12-14 Thread Tom Marchant
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

SMP/E - Pointing Existing TARG & DLIB Zones To New CSI's

2023-12-14 Thread Ross Vaughn
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