Which implies that the best approach is to download and RECEIVE all
relevant new PTFs on a regular and timely basis. That way in the case
cited you would not have the superseding PTF without also having seen
and RECEIVED the superseded HIPER PTF. After all, If your objective is
to review and install all HIPER PTFs as soon as available, what more
reliable way is there to find what is available than to download
available PTFs and actually see which ones are marked HIPER?
If you don't download and RECEIVE all PTFs but manually request some
specific PTF with its co-requisite maintenance, you probably wouldn't be
shipped superseded PTF's, even if one of those is HIPER. That could get
you into the situation which I believe prompted the original question,
where you could have a PTF in house which may be your only in-house fix
for a HIPER error but don't know it fixes a HIPER error.
Joel C. Ewing
On 08/11/2014 06:48 PM, Jon Perryman wrote:
> HIPER is never carried forward to a superseding PTF. HIPER requests that you
> immediately install a PTF and ignore your PTF installation process. You apply
> this PTF to your production systems far sooner than typical. The superseding
> PTF fixes more than just the HIPER situation and possibly requires other
> PTF's. A HIPER PTF must change as little code as possible. Often, there will
> be 2 PTF's caused by a HIPER situation. The HIPER PTF eliminates the HIPER
> situation but may not be the complete solution. The second PTF fixes what the
> HIPER did not fix.
>
> Jon Perryman
>
> On Monday, August 11, 2014 8:17 AM, "Chase, John" <[email protected]> wrote:
>
>
>> It seems logical to me that a PTF which supersedes a HIPER PTF should itself
>> be ASSIGNed the HIPER SOURCEID flag, but in one current instance (UI19849,
>> which supersedes UI18382 whose APAR is flagged HIPER and DATALOSS) the
>> superseding PTF is not flagged HIPER.
>>
>> Is that perhaps an oversight by the team that created UI19849? It is
>> presumed that the fix in UI18382 is present in UI19849.
>>
--
Joel C. Ewing, Bentonville, AR [email protected]
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
