|
Any adopted-authorization over there ? Sincerely Domenico Finucci Fiditalia , Milano, 02- 4301-2494 -----Messaggio originale----- Da: rbaird@esourceconsulting.com [mailto:rbaird@esourceconsulting.com] Inviato: luned́ 6 maggio 2002 16.09 A: midrange-l@midrange.com Oggetto: Authority to a spool file hey all, I've got a situation where I have an RPG CGI program that creates a spool file, closes the printer file and then tries to manipulate the spool. I'm trying to convert the spool file to a PDF file, using spool-o-matic by gumbo. the spool file is created, and completed, and closed. but the convert command is bombing because it says it the job doesn't have authority to the spool file. my problem with this is that the job trying to access the spool is the same one that created it. I do an override to the printer file splfown(*job), and I've double checked that the spool IS listed with the attributes of the job that created it (i.e. job name, user and number) The convert spool command uses JOB(*) for 'current' job and SPLNBR(*LAST) to identify the spool file i'm trying to convert. So, my question(s) are: Under what circumstances would a job NOT have authority to a spool file that it created? I hate to give the QTMHHTTP user more authority than it needs, is it advisable to give QTMHHTTP *splctl authority? would it even help my situation? any insight would be appreciated. Thanks, Rick _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l or email: MIDRANGE-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
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.