|
I had to do something similar once to keep backup copies of spool files in a second outq. I created the output on hold, once the report was finished I called a CL program that did a SNDNETSPLF to a fictitious user that had the second outq as the default. Once the spool file was sent I released the original. It only took a couple of lines of code for the CL, and I only had to add a call to my cl in the original program. ************************************************************************ From: Ed.Doxtator@ssa.co.uk To: MIDRANGE-L@midrange.com Date: Fri, 24 Oct 1997 13:58:19 +0100 Subject: Re: PRTF query? Tim: > How can I use this one PRTF within the ONE program to generate a fax > onto our fax printer server and also a report onto the users outq. My > main question is how do I have the one PRTF output to 2 different outq's > in the same program? Off the top of my head, I think you'd have to -create a duplicate object of the print file. (You could call it "FAXPRTF" or something.) OR -do an OVRPRTF from your original print file to FAXPRTF. In your RPG program, you'd -code a seperate F-spec for the fax print file -rename all the record formats in the fax print file -for each EXCPT, you duplicate the EXCPT, and use the name of the renamed fax record format in the EXCPT -in the O-specs, create duplicate printer output specs for all the EXCPT-s you've duplicated in your code I know it seems a long way around, and I'm sure there's a better way to do it, but I dunno what it is off the top of my head programatically. Alternately, there may be a way of duplicating the completed spool file INTO the fax output queue. It'd be so tasty if OS/400 had a CRTDUPSPLF command. I seem to recall a similar program being written years ago, and it being published in News 3X/400. HTH -Doc +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to "MIDRANGE-L@midrange.com". | To unsubscribe from this list send email to MAJORDOMO@midrange.com | and specify 'unsubscribe MIDRANGE-L' in the body of your message. | Questions should be directed to the list owner/operator: david@midrange.com +--- ---- End of mail text Additional SMTP headers from original mail item follow: Received: from Kitten.mcs.com by E-MAIL.COM (IBM VM SMTP V2R3) with TCP; Fri, 24 Oct 97 10:19:38 EDT Received: from Uucp1.mcs.net (root@Uucp1.mcs.net [192.160.127.93]) by Kitten.mc s.com (8.8.5/8.8.2) with SMTP id JAA26636; Fri, 24 Oct 1997 09:19:03 -0500 (CDT ) Received: by Uucp1.mcs.net (/\==/\ Smail3.1.28.1 #28.17) id <m0xOkZe-000Qpna@Uucp1.mcs.net>; Fri, 24 Oct 97 09:18 CDT Sender: mcsnet!midrange.com!midrange-l-owner@Mcs.Net Received: (from majordom@localhost) by midrange.com (8.7.5/8.7.3) id IAA16884 f or midrange-l-outgoing; Fri, 24 Oct 1997 08:30:14 -0500 Received: from mcsnet.UUCP (uucp@localhost) by midrange.com (8.7.5/8.7.3) with UUCP id IAA16865 for MIDRANGE-L; Fri, 24 Oct 1997 08:17:02 -0500 Received: by Uucp1.mcs.net (/\==/\ Smail3.1.28.1 #28.17) id <m0xOjJx-000QpbC@Uucp1.mcs.net>; Fri, 24 Oct 97 07:58 CDT Received: by mailhost.ssa.co.uk(Lotus SMTP MTA v1.1 (385.6 5-6-1997)) id 80256 53A.00477D34 ; Fri, 24 Oct 1997 14:00:51 +0100 X-Lotus-FromDomain: SSAOT@SSA_EUROPE Message-ID: <8025653A.0045E7CF.00@mailhost.ssa.co.uk> Mime-Version: 1.0 Content-type: text/plain; charset=US-ASCII Sender: owner-midrange-l@midrange.com Precedence: bulk Reply-To: MIDRANGE-L@midrange.com X-List-Name: Midrange Systems Mailing List (MIDRANGE-L@midrange.com) +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to "MIDRANGE-L@midrange.com". | To unsubscribe from this list send email to MAJORDOMO@midrange.com | and specify 'unsubscribe MIDRANGE-L' in the body of your message. | 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-2025 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.