I did read that Mark, but didn’t provide enough detail., or skimmed over it.
So, for my ISV extension volume a few things occur at the beginning of
maintenance rollout time:
1. All ISV products get maintained via vendor provided processes with
datasets that contain a ver/release qualifier
2. Clone old master volume to new master volume as new baseline
3. When cloning updated ISV libraries to master, the datasets get scratched
via IEHPROGM on the new master volume, and then updated libraries are copied
with RENAMEU to remove the ver/release info.
4. FDREPORT job is run to generate/re-generate indirect catalog entries (to
pickup any possibly new datasets that were added), and IDCAMS step to create.
TOL(ENQF) is honored for both source and target datasets with a few exceptions
(mostly for the things you mentioned already, reallocating, etc).
COPY DS(INC(SYSV.IDP.FDREPORT.V5490SP2.CLIST)) -
RENUNC((SYSV.IDP.FDREPORT.V5490SP2.CLIST, -
SYSV.IDP.FDREPORT.CLIST)) -
LIDY(VND005) ODY(VSM02A) BYPASSACS(**) NSC REPLACEU -
ALLDATA(*) TOL(ENQF) SPHERE ALLX SHARE
Dave Jousma
Vice President | Director, Technology Engineering
From: IBM Mainframe Discussion List <[email protected]> on behalf of
Mark Zelden <[email protected]>
Date: Monday, October 16, 2023 at 12:53 PM
To: [email protected] <[email protected]>
Subject: Re: DFDSS RFE - Please read / vote
On Sun, 15 Oct 2023 00: 31: 20 +0000, Jousma, David <David. Jousma@ 53. COM>
wrote: >Mark, > >I have the same cloning process as you logically. I know
exactly the problem you face. Your rfe makes sense. > >I get around it by
On Sun, 15 Oct 2023 00:31:20 +0000, Jousma, David <[email protected]> wrote:
>Mark,
>
>I have the same cloning process as you logically. I know exactly the problem
>you face. Your rfe makes sense.
>
>I get around it by cloning at the volume level, but there is always the
>outlier that needs to be cloned by itself, or the once in awhile fix that
>needs to be made. When I run into that I either rename then delete the
>enqueued dataset via ispf, and then reload, or if the dataset is actually in
>use validly, I use idcams to delete all members, compress, then reload via
>iebcopy.
>
Re-read what I wrote though. I have no problem cloning the sysres set since
that is also done on the volume level. The problem is ISV or IBM program
products that get "added" to the maintenance sysres in preparation for cloning.
Around 40 different products that get copied to the volume at any given time
after maintenance to one of those products. Then I clone the IBM sysres
volumes and the program product volumes as one set using full volume copies
(except for zFS files that are logically copied and have the sysres name as
part of the dataset name).
Best Regards,
Mark
--
Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS
ITIL v3 Foundation Certified
mailto:[email protected]
Mark's MVS Utilities:
https://urldefense.com/v3/__http://www.mzelden.com/mvsutil.html__;!!MwwqYLOC6b6whF7V!l5PVMhb0Ho14o2qfG-4mGoh8trURMMwWV_3J4TJPFXbbuOn6CL5M0mzwZaqcjU4LMJ1WEu-fzBOtjPk$<https://urldefense.com/v3/__http:/www.mzelden.com/mvsutil.html__;!!MwwqYLOC6b6whF7V!l5PVMhb0Ho14o2qfG-4mGoh8trURMMwWV_3J4TJPFXbbuOn6CL5M0mzwZaqcjU4LMJ1WEu-fzBOtjPk$>
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
This e-mail transmission contains information that is confidential and may be
privileged. It is intended only for the addressee(s) named above. If you
receive this e-mail in error, please do not read, copy or disseminate it in any
manner. If you are not the intended recipient, any disclosure, copying,
distribution or use of the contents of this information is prohibited. Please
reply to the message immediately by informing the sender that the message was
misdirected. After replying, please erase it from your computer system. Your
assistance in correcting this error is appreciated.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
