Hi Jon,
"... REWORK replaces a PTF (or APAR) in SMPMTS. ..." Do you mean SMPPTS?
Regards, David
On 2025-12-06 15:58, Jon Perryman wrote:
On Sat, 6 Dec 2025 15:10:50 +0100, Radoslaw Skorupka<[email protected]>
wrote:
can we also assume the REWORK is never changed in PTF?
I only worked for vendors but for released PTF's (IBM or vendor), REWORK should
never change for the PTF.
Understand REWORK replaces a PTF (or APAR) in SMPMTS. Nothing more. If it's
been applied using an older REWORK, then APPLY REDO is required but can be
risky if applied PTFs prereq this PTF.
REWORK for APARs is simple because the PTF SUPs (supersedes) the APAR which
will fix any possible changes made by the APAR at any customer site.
REWORK for PTFs should only be allowed when APPLY REDO is unnecessary (e.g.
comment changes in the PTF header).
In case of error it is marked as hold and new PTF is released, which
fixes the error inside previous one.
HOLD ERROR is not a requirement for a PTF that introduces an error. This is a
choice we make when we understand the error.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email [email protected] with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
