>>> On 2/17/2011 at 1:31 PM, in message <20110218155212.223c0f58...@smtp.patriot.net>, "Shmuel Metz (Seymour J.)" <shmuel+ibm-m...@patriot.net> wrote: > In <4d5bfc54.6f0f.008...@efirstbank.com>, on 02/16/2011 > at 04:30 PM, Frank Swarbrick <frank.swarbr...@efirstbank.com> said: > >>Let me give a very specific example. A change to a program has been >>made to access a new file. The JCL with the new DD for whatever >>reason was not implemented. When the program runs and attempts to >>open the file the open fails. What kind of automatic recovery can >>resolve this issue? None, of course. > > There is no "of course". The new file might not be mandatory. > >>So what are the somethings? > > 5.) Raise an exception. If the exception handler determines that the > condition is not fatal, it can request continuation.
Right! That's what I'm getting at. Exceptions, signaled from where the exception occurs, is very often the way to go. -- Frank Swarbrick Applications Architect - Mainframe Applications Development FirstBank Data Corporation - Lakewood, CO USA P: 303-235-1403 The information contained in this electronic communication and any document attached hereto or transmitted herewith is confidential and intended for the exclusive use of the individual or entity named above. If the reader of this message is not the intended recipient or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any examination, use, dissemination, distribution or copying of this communication or any part thereof is strictly prohibited. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy this communication. Thank you. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
