Charles Mills wrote:
Well, I see that it says "This exit can be taken any time an abend condition occurs during the process of opening, closing, or handling an end-of-volume condition for a DCB associated with your task."
My guess is that this is a subtle attempt to inform the reader not to rely on register contents in the exit. About eight years ago I was assigned to do maintenance on an existing commercial product, and kept getting weird 0Cx abends on some tests. The program had DCB and SYNAD exits, in which the original coder assumed that the base registers were the same in the exits as in the code requesting the I/O. That's true (by poor design?) in general, but not when a problem occurs during O/C/EOV processing, causing the exit to be taken with O/C/EOV registers.
Gerhard Postpischil Bradford, VT ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
