> On Fri, 28 Dec 2007 18:46:05 -0800, Paul Knudsen > <[EMAIL PROTECTED]> wrote: > > >>Judicious use of DISPLAY statements can tell the programmer, for > example, > >>exactly which record to pull from the input file. Yes, you can also > figure > >>that out from the dump, but it takes longer. > > > >Don't you have a debugger, fergodsake? > > Yep, we have a debugger. And after copying the data to a test environment, recompiling the program with TEST options turned on, I *may* be able to re-create the problem..... Of course, by then the batch window will be long over and I'll be too busy updating my resume to care about the problem any more. :-)
On call support is *not* the time to exercise your debugging skills. Finding the logic error and fixing the program is #4 on my list of priorities at a time like this. 1. Bypass the failing job. 2. Bypass the failing step and proceed with the rest of the job. 3. Pull record from input file or take some other action to bypass the problem record. 4. Fix the offending program. 5. Recover the data base and abandon the entire batch run. Update resume. A well chosen DISPLAY message can make #3 very easy to do. ---------------------------------------------------------------------- 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
