Without wanting to start a war, Im interested in how this works. Ive worked with IBM stuff for over four decades, but mostly with VM until the last 15 or so years.
My understanding is: * PMR: represents a customer issue, which may end there. * APAR: represents a customer issue that at least seems to indicate a code problem. Existence of an APAR does not guarantee a fix will ever be created; its more a recognition that theres more to it than just customer needs an existing fix, is doing something dumb, etc. One APAR might thus map to multiple PMRs, if multiple customers have the same problem. * PTF: An actual fix Now yall are talking about APAR fixes, which Ive never heard of. And I know theres more to APARs than I wrote, just cant remember it. Having worked for vendors for the last 37 years means Ive been out of the normal flow of such things, toowhen I was at UofWaterloo, we had a backlog of a couple of hundred things that wed fixed in IBM code; we had an agreement with our PSRthe sort of level 1 ½ that customers have [had, then, anyway] that wed only have 5 open at once. That was always fun: call IBM, I want to open five problems. FIVE PROBLEMS???! Well, I have a couple of hundred, but Im only opening five today. Oh, ok. ISTR that if a problem appears in multiple supported releases, one APAR might result in multiple PTFs, one per release. Im also interested in a definitive list of APAR closings. Ive never seen one, and the lists Ive seen have been conflicting and often included different interpretations of the same closing. None of this matters a ton, of course, but it *works* when done right, which is more than I can say for many customer problem workflows! I dont see this as particularly sensitive info, but perhaps IBM will disagree, in which case Ill STFU. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
