The problem is I have to find and read every PTF / APAR one by one.. Determine if the fix does what I need (maybe all the causes are documented But hardly ever). Why ? SMPE claims to be the all knowing wizard but won’t do the resolution.
I’m with Phil on this issue. Just my 2 cents . On Nov 3, 2023, at 22:10, Paul Gilmartin <0000042bfe9c879d-dmarc-requ...@listserv.ua.edu> wrote: On Fri, 3 Nov 2023 20:51:44 -0400, Phil Smith III wrote: > > My understanding is: > > * PMR: represents a customer issue, which may end there. > This generally embeds tie ID of the reporting customer. > * APAR: represents a customer issue that at least seems to indicate a code > problem. Existence > Importantly, the APAR ID may appear as the REASON() of Error HOLDDATA. > * PTF: An actual fix > Now y�all are talking about �APAR fixes�, which I�ve never heard of. > The term appears at least here: <https://www.ibm.com/docs/en/zos/3.1.0?topic=process-researching-apply-check-reports> (The PTF keyword/phrase index was my friend.) <https://ibm-docs-static-content.s3.us.cloud-object-storage.appdomain.cloud/pdx/SSLTBW_3.1.0/zOS310-GA-Indexed-PDF-package-(2023-09-29).zip> -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
