Fiery Command WorkStation

Hide or show navigationPrevious topicNext topicSharePrintPDF

Sequential Print

The Sequential Print feature allows the Fiery Server to maintain the job order on certain jobs sent from the network. The workflow is "First In, First Out" (FIFO).

This feature is used especially in the production print and CRD (Corporate Reprographics Department) environments because jobs are submitted in a specific record or report order. Usually each record is sent as a separate job, which may contain a few pages.

The Fiery Server needs to know which jobs are being submitted to the Sequential Print queue, and ensure that any other jobs submitted during a sequential run do not interrupt the sequential run, or end up printed in the middle of it.

Sequential printing can be configured on the Fiery Server. After it is turned on, the Sequential Print queue will be available through the following supported printing protocols:

  • Command WorkStation Import command

  • MyDocs WebTools

  • Hot Folders

  • Virtual Printers

  • SMB Printing

  • LPR or LPD

  • Port 9100 (when it is routed to the Sequential Print queue in Configure)

The Sequential Print feature is not available on integrated Fiery Servers.

Sequential Print run process

The sequential print run (burst) begins when the first file is spooled to the Sequential Print queue. The sequential print run is marked with a unique group ID.

The time-out interval defines the amount of time the Fiery Server should wait between jobs submitted to the same group ID. After the sequential print run begins, each job that is spooled before the time-out elapses will re-trigger the time-out to the initial settings. After the time-out period elapses, the Fiery Server considers the sequential run complete.

When specifying the time-out interval, consider the following:

  • Network traffic

  • Size of the jobs in the sequential print run

  • Spool time, which is the amount of time spent in preparing each job to ensure that time-out does not elapse before the entire sequential run is submitted

Setting the time-out for a long period may result in the Fiery Server locking the system from processing other files after the last file in the sequential run was spooled.

Jobs submitted in a sequential print run arrive at the Processing queue and wait until all jobs are received, then they are submitted to the Printing queue in the order that they were received.

Sequential Print run interruptions

The Fiery Server takes care to maintain the print order as long as you do not interrupt the printing order. The following actions, if applied, will cause printing disorder of the jobs:

  • Rush Print

  • Print Next

  • Process next

  • Re-order jobs processing and printing jobs in queue

  • Suspend on Mismatch

  • Preview

  • Hold

  • Sample Print

  • Cancel a job from the sequential printing group

Terms of Use