|
Is the program that segments the output the spooler or the COBOL application? Yes your RPG can close the spool file and re-open it, thus creating multiple spool files. You can also start printing a spool file while it is still open, being generated by the application by changing the SCHEDULE from the default of *FILEEND to *IMMED. This can be a change by an operator or in a CL OVRPRTF statement or in the actual print file with a CHGPRTF. We used to do this for our monthly statement run when the program took 6 hours to generate and 8 hours to print. Christopher Bipes Information Services Director CrossCheck, Inc. -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Michael Rosinger Sent: Wednesday, January 03, 2007 12:32 PM To: midrange-l@xxxxxxxxxxxx Subject: segmentation of spooled output on the iSeries... List, I have another mainframe-to-iSeries question for you. On our VSE system, every night, we print tens of thousands of 1-page letters on our Xerox laser. The program on the VSE system creates 1 large "report" to the spooler containing all of the letters in a certain order. The program "segments" the output on a logical boundary, usually a combination of number of letters and form code/type. The reason this is done is so that printing of letters can be started (i.e. sent to the Xerox) BEFORE the program has completed processing of all the letters for the run. This saves time, allowing the operator to get a "jump" on the printing by not having to wait until the program has finished to be able to release the print. My questions: Is there a way to duplicate this process on the iSeries? Can a COBOL program interface with the system so that it can "segment" the print file output? Would it be as simple as closing and re-opening the print output file? What is the best way to handle this? As always, TIA! -- Regards, Michael Rosinger Systems Programmer / DBA Computer Credit, Inc. 640 West Fourth Street Winston-Salem, NC 27101 336-761-1524 m rosinger at cciws dot com -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx 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.