>> For those interested: I found an entry in LOGREC that matched in >> time and STC name (SMSVSAM). I've opened a PMR since I consider an >> error if a system component tries to document a problem via ABEND >> dump instead of an SVC dump. > > SMSVSAM does not initiate an "ABEND dump". RTM2 does that when there > is a SYSUDUMP, SYSABEND, or SYSMDUMP DDname allocated. > SMSVSAM uses proc IEESYSAS. As supplied by IBM, the IEESYSAS > proc does not contain a DD statement for any of those DDnames. > If your installation modified the IEESYSAS proc to add one of > those DDnames, then the attempt to take that kind of dump is your > doing, not SMSVSAM's doing.
I guess I did not choose good wording for what I meant. I was assuming that system code should establish appropriate recovery routines to handle unexpected situations. I was further assuming that this code should document the failure via SVC dump, then retry. This doesn't not seem to be the case since RTM2 was trying to document via abend dump (maybe based on the fact that we indeed added a "dump" DD statement. I will chek if this is the case.) Am I still on the wrong track? -- Peter Hunkeler ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
