× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



On 30-Jan-2012 12:52 , Michael Naughton wrote:
I have run into something that I don't understand (not all that
rare), and my boss doesn't understand it, either (pretty rare).

I'm calling a stored procedure from a web page. The procedure is in a
service program, written in RPG, and it basically produces a
printout. I want to grab the spool file when it's done and do some
things with it, but I'm having trouble because the job number on the
spool file is different from the job number on the stored procedure.
The stored procedure is running in QUSRWRK as a QZDASOINIT job, and
I've been able to look at it in debug and confirm that it has the job
number that I think it has. I've tried running the routine that
produces the printout as a separate program, and I've tried calling
it as a module using CALLB, but every time it produces a spool file
with the same job number, which is different from the job number of
the QZDASOINIT job. Interestingly, the job number on the spool file
has been the same since last week (when I started working on this),
even though we IPLed the system over the weekend.

Does anyone have a clue as to what might be going on? And/or does
anyone know how I might be able to determine in my program what that
the spool file's job number is after it's been created?


Review first, the SPLFOWN() parameter for the printer file or in an override [scoped to affect] the spooling request. That determines what job and user "owns" the spool file. When running in a server job that has effected a "switch" to the user for a client requester causes the SPLFOWN(*CURUSRPRF) attribute\setting to create the spool file for the JOB(*n/UsrPrf/QPRTJOB) instead of for the JOB(*). Either an override to, or the printer file having the SPLFOWN(*JOB) established, will cause the spool file to be associated with the current job.

Ignoring that... There is the possibility to instead, obtain the identity of the spool file that was just created using the QSPRILSP API with the SPRL0100 Format:

_i # Retrieve Identity of Last Spooled File Created (QSPRILSP) API i_
" ...
The Retrieve Identity of Last Spooled File Created (QSPRILSP) API returns the complete spooled file identity of the last spooled file created for the current job or thread.
...
"

Regards, Chuck

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.