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: http://www.mzelden.com/mvsutil.html ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
