Printing from ODBC

[Buck Calabro <mcalabro@xxxxxxxxxxxx>]

I guess it's my week to be stumped.
We have an application that's being converted to GUI.  In essence, our PC
program is calling a stored procedure that prints a phone bill, then passes
the spooled file information (job/user/number spooled file name/number) back
to the caller which then uses system APIs and a 3rd party product to display
that AFP spooled file in GUI form.  If we call the stored procedure from
interactive SQL, the spooled file gets assigned to the calling job: 
            File                                
File        Nbr   Job         User        Number
QPPGMDMP       6  BUCK02      BUCK        576968


The stored procedure is running in subsystem QSERVER:
Job          User        Number
QZDASOINIT   QUSER       577137

If we call it from ODBC, the spooled file gets assigned NOT to the prestart
job in QSERVER (QZDASOINIT) but to some QPRTJOB:

            File                                
File        Nbr   Job         User        Number
QPPGMDMP      26  QPRTJOB     BUCK        530271

This is hosing up the stored procedure (CL program) because it can't
determine the spooled file's job name!  This is ODBC related because the
same statement works as expected from interactive SQL.

1. Can we tell the 400 NOT to spawn another job to catch the print?  Lazy
close has no effect.
2. Is there an easy way to find out which job got spawned to catch the
stored procedure print?

Buck Calabro
Billing Concepts Albany, NY
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---