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

Michael Naughton wrote:

> Today, I made a change to program A so that it will write a log record
> every time it's called. After I put it into production, I found that
> printouts were being produced, but no log records were being written.
> There's (always) the possibility of a program bug, but it's a pretty
> simple program, and it writes the log right before calling program B.
>
> Looking into it further, I discovered that the spool files that program B
> is producing all think they're coming from a job that started back on
> January 9th. This job is running under the profile that is used for the
> ODBC connection. Most of the spool files are gone - printed & deleted -
> but a few are still around (including today's), and they clearly go back
> several months. So my first thought was that this is an active job that
> was using the old version of program A, and if I simply ended and
> restarted it everything would be fine.
>
> Now comes the part that has me stumped: the job isn't active. It doesn't
> have a job log, because it thinks it ended (although WRKJOB shows a start
> time but no end time). It doesn't show up in work active jobs, and when I
> try to end it it says it's already ended.  But, clearly, it continues to
> produce spool files, as it has been doing for many months. We IPL every
> weeek, so it's survived multiple IPLs (apparently). ...
>
> Does anyone have any clues? Any ideas about how I might debug this? Any
> thoughts will be greatly appreciated!

Mike,

I can not help with the missing log records but I think I can explain why the
spooled files are placed in a job that is not active. My guess is that the job
has a name of QPRTJOB. Jobs with names of QPRTJOB are used to store spooled
files when the SPLFOWN parameter is used for the printer file or when a swap
user profile API is used to swap the user profile of the thread to some other
user profile before the spooled file is created. Chapter 3 of the Printer
Device Programming book has a section called Working with a QPRTJOB has a
detailed description of these jobs. The bottom line is that QPRTJOB jobs are
just used to own the spooled files.

Ed Fishel