Batch Printing and the Popup and Hold/Release print queues
Last modified on 14 August 2020 10:33 AM
Printing large batches of print jobs is common in many organizations. Examples include:
Many of these batch printing applications work by sending a large amount of small individual jobs to the print queue. It is usually desirable for these batch print jobs to print in a predefined order. For example the jobs may be printed in alphabetical order and this order used to match up with a separate batch of printed envelopes.
PaperCut can affect batch printing order if an account selection or confirmation popup is enabled.
Normally a print queue will print jobs in the order they are received, but this logic cannot be applied if a popup is used. The reason for this is that if a single user failed to acknowledge their popup, they would hold up the queue for other users/jobs.
The order of jobs can also be affected if different jobs within the batch are significantly different sizes. This is because it can take longer to process larger jobs, allowing smaller jobs to print earlier.
Enable hold/release on the printer. Jobs will be held in a queue from which they can be released using PaperCut’s web based or standalone release stations.
Jobs released all-at-once using the release station’s “Release All” function will be printed in their original order, so when printing batches, send off the whole batch to the printer for holding in the release queue and then release all at once using the release station’s “Release All” function.
For more details on enabling hold/release and using release stations please see the manual.
Organizations often employ the following solution:
Set up a separate dedicated print queue for the reporting application. This is often a new queue on the server that points to an existing physical printer. Give the queue a name such as “Batch Printing Queue”. Exclude this queue from the popup using one of two methods:
Organizations also often: