|
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?
As an Amazon Associate we earn from qualifying purchases.
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.