> I was so surprised by this that I had to go look. A spot check of > several z/OS messages books shows that many (perhaps most) messages > include "Module: [module name]" just as they always did. Maybe you were > "lucky" enough to have a tendency to work on exceptions, or on some > component or components for which the detecting modules were not documented. My guess is that I was unlucky enough to get all the exceptions. My spot check: IDA018 has Source: DFSMSdfp (which is evident from the prefix alone and hence redundant). IXZ0108E only has Source: JES2 (not that I ever worked on JES topics) IXGH006I has Source: n/a and is a logger health checker message (as indicated by the prefix).
Seems to me that a lot of the new components don't bother with that information anymore, while the 'old stuff' didn't get deleted from the books. > For system abends, there is a cross-reference table (Chapter 4 in the > 2.1 System Codes book) that provides detecting modules. I can't easily > tell whether all are represented there, but it's a fairly long table. > For Abend077, though, it's clear from reading the message that a > perhaps-significant number of modules are involved, and that someone > chose not to document all of them in Chapter 4. Abend026 is missing altogether in that table. And has the issuing module encoded in the reason code, *if* you have the appropriate mapping macro. I did a lot of XCF/XES stuff way back when. Barbara ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
