Hello Bert Would you please help with the sample JCL for maintenance roll out JCL you follow ?
My email: dbajava...@gmail.com On Mon, 7 Oct 2024, 18:35 Albertus de Wet, < 0000062595278496-dmarc-requ...@listserv.ua.edu> wrote: > Peter > > I have three "RESVOL complexes" and before I install maintenance I: > - copy the system datasets from the current, active resvol to the new > resvol. I do round-robin on them: (A -> B, B -> C, C -> A, etc). > - copy all the ZFS files from A to B, (with rename) that includes the new > complex name. My master-catalog does not live on the resvol, but a separate > volume, so do my PARMLIB and IODF-file. > - clone the SMP/e environment from the current resvol to the new resvol > (also not on resvol). > > I use the new SMP/e zone info to build the ORDER-list that I attach to the > IBM order. > Receive this order to the new resvol, apply and IPL. > > I have REXX, JCL and Assembler macro scripts that take care of all the JCL > generations to make it easy and consistent. > > Let me know If you want more details, and I'll be happy to share what I > have. > > Thanks > Bert > > > > On Sun, Oct 6, 2024 at 10:27 PM Peter < > 000005e4a8a0a03d-dmarc-requ...@listserv.ua.edu> wrote: > > > Hello > > > > It's been some time that i have done maintainance roll out. > > Just a few clarifications. In my previous shop for every maintenance we > > used to just copy the root files using FDR. > > > > How do you roll out root file system everytime. > > > > Do you always create a new one or you keep maintaining the same naming > > standards based on RES volume symbolic? > > > > Here we have two respack OSRESA and OSRESB. > > Either OMVS.OSRESB.ROOT gets created or OMVS.OSRESA.ROOT gets created > each > > time. > > > > It's a new Shop that I have inherited but just wanted to know how you > > are doing ? > > > > Could someone please be kind enough to share your best practice? > > > > Peter > > > > ---------------------------------------------------------------------- > > 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
