|
Hi Alan I know this email is slightly salesy (and if you are not interested just ignore and delete). I use to work at a bank where I had similar problems. In the end I wrote a suite of programs to deal with the most common SPLF management issues. Now I work with a software house and we have enhanced the original SPLF management into a product called Report Management/400 (RMF/400), which take of all these sort of problems. I you want to know more please contact me or have a look at our web site: http://www.technocrats.co.uk/ (click on Product and Report Management/400 on the sidebar). Best regards Jacob Christiansen -----Original Message----- From: alan shore [mailto:SHOREA@dime.com] Sent: 24 May 2000 13:39 To: MIDRANGE-L@midrange.com Subject: Re: Bundling Spool Files I may be mistaken, but I think the original request was NOT strictly bundling the spool files together, but sorting the contents of those spool files so that customer A has statements/invoices/bills from spool 1,2,3 and 4, followed by customer B from spool 2 and 4 followed by customer C from spool 1 and 3. I hope that my interpretation is correct as I am in the process of analyzing the same problem, and if anyone has an answer, obviously, I would be very interested. TIA >>> Dave Murvin <davem@drme.com> 05/23 9:13 PM >>> If the programs you are using use the same printer file, such as QSYSPRT, you could use OVRPRTF FILE(QSYSPRT) SHARE(*YES), then all the printer files after the override (assuming they are the same file name and in the same job) will be bundled into the one spool file. I have used this process in the past to connect cover page info to a report so when you print two copies, the cover pages are attached to the reports. At 06:39 PM 5/23/00 +0200, you wrote: >Is there an "easy" way to programmatically bundle the spool files together, >so that the contents of the spool files will be printed in the correct >sequence? Dave Murvin DRM Enterprises, Inc. davem@drme.com +--- | 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 +--- +--- | 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 +--- +--- | 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 +---
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.