Re: ODBC (?) Problem - Finished Job Producing Output

["Michael Naughton" <mnaughton@xxxxxxxxxxxx>]

Thanks, Rob - this is a nice tip. Didn't have anything to do with my
problem, but I think I'll make a habit of doing it anyway - it seems like
a good idea. And I learned something new about jobs that never die . . . .
:-)

Thank you and Ed for your suggestions. After a certain amount of detective
work, we tracked down the problem, and it turned out to be one of those
things you kick yourself for. Happily, there was absolutely nothing wrong
with my program (this time :-): it turns out that the web development guy
had two versions of the stored procedure -- one pointing to the production
version of my program and one (for some reason) pointing to the one in our
test system (which, of course, I didn't change because I naively assumed
that the users weren't touching that one). Once we fixed that, everything
started working perfectly. . . .

Thanks for all your help.

Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> writes:
>To reset this 
>is quite easy.  If you ENDJOB *IMMED DLTSPLF(*YES) then it will delete
>all 
>spool files associated with that job and use a different job number the 
>next time.  And it will free up some spool file storage if that job has 
>thousands of spool files; deleted or still active.


Mike Naughton
Senior Programmer/Analyst
Judd Wire, Inc.
124 Turnpike Road
Turners Falls, MA  01376
413-863-4357 x444
mnaughton@xxxxxxxxxxxx