|
>4224 with green bar; 15cpi, 51FL, 48OF, FW198 >4224 with white; 15cpi, 51FL, 48OF, FW198 > >Is it best to make a unique print file for >each printer (ie: qsysprtp3)? >However, some jobs grab qsysprt anyway and >print in 10cpi default, etc. >or Is it best to make use of an override >print file? 1) You can't make these changes at the system level; there's no device config option that will allow you to do this. 2) If you set up separate printer files, say GREEN8 and WHITE8, then the HLL program that generates the output will have to be changed to use these two new printer files. 3) If you create a new printer file, no other job can possibly grab it as it wasn't in existence until you created it. 4) Overrides are great for this purpose and are generally done in the CL that directly calls the HLL pgm ovrprtf qsysprt outq(4224) formtype(green8) cpi(15) pagesize(051 198) ovrflw(048) call hllpgm /* program opens printer file QSYSPRT */ endpgm So the job stream looks like //bchjob call printcl //endjob If, in the future you get a different printer (say in a branch office) and need to send the same report to the new office, you change your job stream to issue another override: //bchjob ovrprtf qsysprt outq(branchoutq) call printcl //endjob This 'outer' override will supercede the inner one and send the 15 cpi report to the new outq. In any event, some small amount of programming is required. Which is 'best?' The answer depends entirely on the existing practices. If the business uses overrides for all it's other batch jobs, then that's the way to go. If it has separate printer files for all of it's other custom print, then I'd use that route. Hope this helps some. --buck
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.