On Thu, 26 Jan 2023 11:19:52 -0600, Paul Gilmartin <paulgboul...@aol.com> wrote:
>On Thu, 26 Jan 2023 14:32:47 +0000, Kurt J. Quackenbush wrote: >> >>Just to confirm what has already been mentioned, you're using ++RELEASE >>incorrectly. The fixing PTF will resolve the ++HOLD, so there is no need to >>generate a ++RELEASE. IBM only uses ++RELEASE in cases when a PE or HIPER >>has been flagged erroneously. >> > >But is there a way to undo a ++RELEASE that has been issued erroneously? Of course there is. Another HOLD. The HOLDDATA is processed sequentially. The RELEASE will remove the HOLDDATA entry and a subsequent HOLD will add one. > >If Ed wishes a notification of PTF availability to appear among the HOLDDATA, >he could >supplement his: > ++HOLD(fmid) ERROR FMID(fmid) REASON(aparnum) >with > ++HOLD(fmid) ERROR FMID(fmid) REASON(PTFnum) /* Available 2-23--01-26 */ He could do that, but IMO it would not provide any real benefit. It would add another hold on the function for reason PTFnum. It would not remove or supersede the hold for reason aparnum, nor would it make it clear what APAR the PTF resolverd. Better, he could add SMRTDATA to the hold, similar to the following, taken from the latest IBM enhanced holddata: ++HOLD(UJ09069) FMID(HBB77C0) REASON(CA64026) ERROR DATE(23018) COMMENT(SMRTDATA(FIX(UJ09743) CHGDT(230118))) CLASS(PE). Note that it is not necessary to edit the existing HOLDDATA entry. Just add the updated one to the end of the HOLDDATA file. The FIX in SMRTDATA is used by REPORT ERRORSYSMODS and REPORT MISSINGFIX. And include SUP(aparnum) in the resolving PTF. That tells SMP/E that the error hold is resolved when the PTF is applied. -- Tom Marchant ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
