|
Ken, I find that the simplest way to locate the spool file in QPRTJOB is to WRKJOB QPRTJOB and page thru the entries until found or else temporarily (or permanently) set the USRDTA attribute for the printer file so that it can easily be located using the same USRDTA via the WRKSPLF command. Peter -----Original Message----- From: Sims, Ken [mailto:KSIMS@SOUTHERNWINE.com] Sent: Thursday, December 07, 2000 2:37 PM To: rpg400-l@midrange.com Subject: RE: qprtjob Hi Peter and 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) ... >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... If you need to have the spooled file going to the different user profile so that Peter's method cannot be used, there is a PTF that provides support to find out the information about what job actually owns the spooled file. V4R2 - SF61083 V4R3 - SF60837 V4R4 - SF61082 V4R5 - SF62350 With the PTF installed, you can set an environment variable to tell the operating system to put an entry in a data queue for each spooled file created in the job. [This is a totally separate thing from a data queue attached to an outq that receives an entry whenever a spooled file goes to Ready in the outq.] See the PTF cover letter for details including the layout of the data queue entries. Ken Southern Wine and Spirits of Nevada, Inc. Opinions expressed are my own and do not necessarily represent the views of my employer or anyone in their right mind. +--- | 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 +--- 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 +---
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.