On Wed, 25 Jan 2023 22:04:39 -0800, Ed Jaffe wrote:
> ...
>One of our products had a bug in the base that was fixed by an APAR for
>which we added a ++HOLD(fmid) ERROR FMID(fmid) REASON(aparnum) statement
>to our HOLDDATA. Once the APAR was validated in the field and ready for
>PTF creation, a ++RELEASE(fmid) ERROR FMID(fmid) REASON(aparnum)
>statement was added to the HOLDDATA.
>
Why? Has this been your custom? Normally, I'd expect the hold to be removed
by APPLYing the corrective PTF -- RELEASE is superfluous.
in: z/OS SMP/E Reference, SA23-2276-50, I read:
REASON
identifies the HOLD reason ID that is to be removed from the SYSMOD.
This field is required.
• An error reason ID is the number of the APAR that caused the SYSMOD to be
placed in exception status.
...
• ++RELEASE statements unconditionally remove a SYSMOD from exception
status and should, therefore, be used with caution. To install a SYSMOD
that is currently in exception status, you should probably not create and
process a ++RELEASE statement, but rather use the appropriate BYPASS
operand of the APPLY or ACCEPT command.
Note the word "unconditionally"; not contingent on the availability of the
corrective PTF. I have never coded a ++RELEASE.
--
gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
