RE: qprtjob

[Peter Connell <peterc@xxxxxxxxxxxxx>]

Tim,
The spool files in QPRTJOB normally originate from server jobs that swap of
the user profile for the job to some other profile. While the profile is
swapped OS/400 defaults to assigning any generated spool files to a QPRTJOB
which in fact is not an active job but the spool files get mysteriously
added to it anyway. To avoid this behaviour you merely perform the
appropriate printer file override so that the owner of the spool file is the
user of the original job so that the spool file can be located as you would
normally expect.
eg OVRPRTF FILE(QSYSPRT) SPLFOWN(*JOB) OVRSCOPE(*JOB) 
 
Cheers, Peter
 

-----Original Message-----
From: Hatzenbeler, Tim [mailto:thatzenbeler@clinitech.net]
Sent: Thursday, December 07, 2000 8:44 AM
To: 'RPG400-L@midrange.com'
Subject: qprtjob



I have a program that generates a spool file. 

The problem is this, the report is being placed in a job called qprtjob. 

In the rpg, i have the infds setup, so I know the name, and file #, but I
can't seem to track the correct  qprtjob#  This user has multiple qprtjob's
so the list job api isn't going to get me the right one...

So the question is, how do I know the correct qprtjob# for the spool file
I'm writing, when it's going into the qprtjob.


Thanks in advance, 
tim 


This communication is confidential and may be legally privileged. 
If it is not addressed to you, you are on notice of its status. 
Please immediately contact us at our cost and destroy it.  
Please do not use, disclose, copy, distribute or retain any of it 
without our authority - to do so could be a breach of confidence. 
Thank you for your co-operation.  
Please contact us on (09) 356 5800 if you need assistance.
+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---