Re: SMP/E maintenance best practice for z/OS

2024-12-15 Thread Luc Martens (KBC)
I do agree with Ed. If you never accept, you will have a lot of difficulties to restore a PTF or a usermod. We do a daily receive order of PTF's and Holddata. On a weekly base, we also do a receive of the information for the SECurity INTegrity PTFS. Before we start applying maintenance, we bac

Re: SMP/E maintenance best practice for z/OS

2024-12-15 Thread Ed Jaffe
On 12/15/2024 12:29 PM, Radoslaw Skorupka wrote: It is not a matter or RESTORE, but matter of way of restore. SMP/E RESTORE does not work in some cases, it is documented. One of solutions would be to clone/backup set of SMP/E volumes - I mean SMPE CSI, DLIB, TGT, etc. You may think about it as G

Re: SMP/E maintenance best practice for z/OS

2024-12-15 Thread Radoslaw Skorupka
W dniu 14.12.2024 o 18:35, Ed Jaffe pisze: On 12/11/2024 6:15 AM, Tom Longfellow wrote: I have never been a member of the 'Never ACCEPT' club. Which is the same as the 'Never RESTORE' club. Who would do that? Not being able to back off a bad APAR/PTF seems unacceptable to me. NOT a best prac

Re: SMP/E maintenance best practice for z/OS

2024-12-14 Thread David Spiegel
Hi Ed, My strategy is to take backups of CSIs and affected Target Datasets just before APPLYing maintenance (after RECEIVE and APPLY CHECK). This way, only a few Datasets need to be RESTored in case something  unwanted occurs. As far as IPL goes, my practice is not to use Target Datasets as ru

Re: SMP/E maintenance best practice for z/OS

2024-12-14 Thread Ed Jaffe
On 12/14/2024 3:49 PM, David Spiegel wrote: Hi Ed, I almost never ACCEPT maintenance, but, what makes "... A point-in-time restore of their CSIs and target library backups? ..." insane? I really never imagined anyone did that. It seems "insane" (to me at least) because doing that restores *A

Re: SMP/E maintenance best practice for z/OS

2024-12-14 Thread David Spiegel
Hi Ed, I almost never ACCEPT maintenance, but, what makes "... A point-in-time restore of their CSIs and target library backups? ..." insane? Regards, David On 12/14/2024 12:35, Ed Jaffe wrote: On 12/11/2024 6:15 AM, Tom Longfellow wrote: I have never been a member of the 'Never ACCEPT' club

Re: SMP/E maintenance best practice for z/OS

2024-12-14 Thread Seymour J Metz
...@listserv.ua.edu> Sent: Saturday, December 14, 2024 12:35 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: SMP/E maintenance best practice for z/OS External Message: Use Caution On 12/11/2024 6:15 AM, Tom Longfellow wrote: > I have never been a member of the 'Never ACCEPT' club.

Re: SMP/E maintenance best practice for z/OS

2024-12-14 Thread Ed Jaffe
On 12/11/2024 6:15 AM, Tom Longfellow wrote: I have never been a member of the 'Never ACCEPT' club. Which is the same as the 'Never RESTORE' club. Who would do that? Not being able to back off a bad APAR/PTF seems unacceptable to me. NOT a best practice. How do the members of that club do i

Re: SMP/E maintenance best practice for z/OS

2024-12-11 Thread Seymour J Metz
לֹ֥א יְשַׁקֵּ֖ר From: IBM Mainframe Discussion List on behalf of David Purdy <00ac4b1d56b3-dmarc-requ...@listserv.ua.edu> Sent: Tuesday, December 10, 2024 11:17 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: SMP/E maintenance best practice fo

Re: SMP/E maintenance best practice for z/OS

2024-12-11 Thread Tom Longfellow
We run a similar cloning system with full SMP support behind each SYSRES. sysres 0 is the target of all new maintenance. the other two sysres 1 and 2 alternate roles from being the 'next' and being the 'minus one' versions of maintenance. Sysres 0 is used to shake down new maint. Then it i

Re: SMP/E maintenance best practice for z/OS

2024-12-11 Thread Allan Staller
Purdy Sent: Tuesday, December 10, 2024 10:17 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: SMP/E maintenance best practice for z/OS [CAUTION: This Email is from outside the Organization. Unless you trust the sender, Don’t click links or open attachments as it may be a Phishing email, which can

SMP/E maintenance best practice for z/OS

2024-12-10 Thread David Purdy
We have had some spirited internal discussions on SMP/E best practice for applying z/OS maintenance while maintaining an environment for emergency PTFs as neededI upgrade z/OS version on a two year cycleCurrent process for a lot of maintenance with about a year's worth of RSUs      - ACCEP