Abstract: Systems and methods are provided for scheduling high priority print jobs with minimal paper waste. One embodiment is a printing system that includes a print controller having a print data path with intermediate queues and a last queue to store print ready bitmap data. The print controller monitors the last queue to determine an estimate time for printing the print ready bitmap data stored in the last queue, determines whether the estimate time exceeds a time threshold, and determines whether a high priority print job is detected in the job storage system. In response to determining that the estimate time exceeds the time threshold and detecting the high priority print job, the print controller halts processing of at least one of the plurality of print jobs that is not the high priority print job, and advances processing of the high priority print job on the print data path.

Abstract: The present invention efficiently directs the flow of print jobs and efficiently controls the spooling and printing of print jobs. The multiplexer system analyzes jobs received from client systems through print channels. The multiplexer determines the attributes of the incoming job and the attributes associated with the print channel. If the attributes of the print job and the attributes of the print channel dictate an output path (either MUST PRINT or MUST SPOOL), then the multiplexer examines the state of the selected path. If the designated output path (printer or spooler) is busy, then the multiplexer decision is to signal a Stop_Flow to the print channel. The print channel is signaled to Start_Flow at a later time, when the output path becomes available. If the attributes of the print job and the attributes of the print channel do not dictate an output pith, then the multiplexer examines a User Output Selection setting to control spooling and printing of print jobs.

Abstract: Provided are a method, system, and program for processing requests for data sinks in a logical printer. A request is received to process a print job from one of a plurality of protocol components. A determination is made of one of a plurality of data sinks for the print job and whether the determined data sink is available. A return code is returned to the component initiating the request. A data sink available message is returned to the component initiating the request in response to determining that the determined data sink is available after returning the return code. Additional asynchronous operations are performed before returning the data sink available message.