Thank you Carmen. -----Original Message----- From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of Carmen Vitullo Sent: Monday, June 22, 2020 10:12 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: SMP/e maintenance methodologies
This message was sent from an external source outside of Western & Southern's network. Do not click links or open attachments unless you recognize the sender and know the contents are safe. ________________________________________________________________________________________________________________________ I follow that methodology also, + as others have said receive holddata weekly and I will periodically run a MISSING FIX report remember to add the SMPPUCH DD to the JCL procedure //REPORT EXEC PGM=GIMSMP, // REGION=0M, // TIME=1439, // PARM='DATE=U,CSI=SMPE.ZOSV2R3.GLOBAL.CSI' //SMPHRPT DD SYSOUT=* //SMPPUNCH DD SYSOUT=* //* //SMPCNTL DD * SET BDY(GLOBAL). REPORT MISSINGFIX ZONES(MVST100) you can add a specific fix category if you need to focus on missing maint for a OS upgrade or a planned hardware upgrade. SET BDY(GLOBAL). REPORT MISSINGFIX ZONES(MVST100) FIXCAT(IBM.*). /* FIXCAT(IBM.TargetSystem-RequiredService.Enterprise-COBOL.V6R2). as an example Carmen Vitullo ----- Original Message ----- From: "David Jousma" <000001a0403c5dc1-dmarc-requ...@listserv.ua.edu> To: IBM-MAIN@LISTSERV.UA.EDU Sent: Monday, June 22, 2020 9:02:46 AM Subject: Re: SMP/e maintenance methodologies Yes. As Rex pointed out, the first part of the output in the SMPRPT DD statement will be the listing of what PTF's did NOT go on, and why. You'll want to review that, and make sure the only ones that did not go on were the ones with Errorhold. If a PTF you wanted to go on didn't, it will show here (MODID error for example if you have a usermod), or a space problem on a target dataset, etc. Here is an example of a APPLY I ran today. One PTF didn't not go on, because it is in error. CAUSER SYSMOD SUMMARY REPORT FOR APPLY PROCESSING CAUSER FMID MESSAGE ID PAGE ERROR DESCRIPTION AND POSSIBLE CAUSES UJ02757 HDZ2240 GIM35901I 1 ERROR HOLD CA59681 WAS NOT RESOLVED. PAGE 0003 - NOW SET TO TARGET ZONE MVSTZN DATE 06/22/20 TIME 07:43:25 SMP/E 37.05 SMPRPT OUTPUT UNRESOLVED HOLD REASON REPORT FOR APPLY PROCESSING NOTE: THE SYSMODS LISTED IN THIS REPORT ALSO APPEAR IN THE CAUSER SYSMOD SUMMARY REPORT. HOLD MISSING HELD RESOLVING RESOLVER TYPE FMID CLASS APAR SYSMOD SYSMOD STATUS ------ ------- ------- ------- ------- --------- -------- ERROR HDZ2240 PE CA59681 UJ02757 PAGE 0004 - NOW SET TO TARGET ZONE MVSTZN DATE 06/22/20 TIME 07:43:25 SMP/E 37.05 SMPRPT OUTPUT _____________________________________________________________________________________________________ Dave Jousma AVP | Manager, Systems Engineering Fifth Third Bank | 1830 East Paris Ave, SE | MD RSCB2H | Grand Rapids, MI 49546 616.653.8429 | fax: 616.653.2717 -----Original Message----- From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of Edgington, Jerry Sent: Monday, June 22, 2020 9:48 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: SMP/e maintenance methodologies **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails** Dave, So, if you get RC=8, you run the Apply anyway, just letting SMP/e determine what PTFs can be applied, correct? If that is the case, that would simplify the SMP/e apply process. Thanks, Jerry -----Original Message----- From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of Jousma, David Sent: Monday, June 22, 2020 7:57 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: SMP/e maintenance methodologies This message was sent from an external source outside of Western & Southern's network. Do not click links or open attachments unless you recognize the sender and know the contents are safe. ________________________________________________________________________________________________________________________ I do not attempt to get a RC0 or RC4 apply. What goes on goes on. Obviously review results to make sure that there wasn't an issue, but coding up a bunch of excludes to not select those with holderror just to get a RC0 is not necessary in my opinion. Here is one apply example APPLY CHECK SOURCEID ( SYSPLXDS XSYSTEM HIPER IBM.* RSU* SECINT ) GROUPEXTEND ( NOAPARS NOUSERMODS ) BYPASS ( HOLDSYSTEM) NOJCLINREPORT RETRY ( YES ) . _____________________________________________________________________________________________________ Dave Jousma AVP | Manager, Systems Engineering Fifth Third Bank | 1830 East Paris Ave, SE | MD RSCB2H | Grand Rapids, MI 49546 616.653.8429 | fax: 616.653.2717 -----Original Message----- From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of Edgington, Jerry Sent: Monday, June 22, 2020 7:42 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: SMP/e maintenance methodologies **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails** Hello everyone, I am looking for SMP/e methodologies about a couple of situations within SMP/e. Just looking for how people do SMP/e maintenance in certain situations. 1) What methodology is employed to get to a clean Apply Check, when you outstanding Error Holds? APARs without PTFs, local fix or work arounds? 2) For Apply check, what PARMs do you use? Select, FixCat, Bypass, etc? I was taught a SMP/e methodology, many years ago, but just wondering if there might be a better way. Thanks, Jerry Edgington ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails** 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 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 **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails** 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 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
