On Mon, 11 Aug 2014 15:17:25 +0000, Chase, John 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.
I've been away, hence the late reply. While we often talk about a HIPER PTF, I think that what we are really talking about is a PTF that resolves a HIPER error. That is, a SYSMOD is found to be in error, and the HOLDDATA is marked HIPER because the error is High Impact or PERvasive. When PTF A is issued to resolve the APAR that the HOLDDATA lists as the reason, it will SUP that APAR number. If PTF B is later issued that SUPersedes PTF A, there is not another HOLD issued, unless PTF A introduced a new error. PTF B will, however, also SUP the original APAR number in that case. -- Tom Marchant ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
