Xerox 6180N FreeFlow® Print Server IBM® IPDS User Guide - Page 41

IPDS User Guide Using Xerox FreeFlow® Print Server IPS Manager NOTE: The constraints are not applicable to multiple copies requested by the IPDS job. Copygroup and Copysubgroup processing is performed properly as per the IPDS specification. If job accounting on the host is to be accurate, multiple copy control should be done by the IPDS job and not by the output Quantity in the queue. Page Counting Constraints and Considerations There are a number of limitations and considerations that must be taken into account when saving, or concurrently printing and saving IPDS jobs: • When saving a job to a write-once target, such as CD-ROM, Xerox FreeFlow® Print Server Save Job processing can only write the data to the media when the job is complete. However, the IPDS host requires the printer to provide acknowledgements as each page is stacked. Therefore, Xerox FreeFlow® Print Server IPDS must report pages to the host as stacked as they are processed, even though they are not yet written to the output media. For this reason, Xerox FreeFlow® Print Server cannot support IPDS host recovery for jobs saved to write-once media. This limitation is not a concern when saving jobs to rewritable media, such as a local disk drive. • When a failure occurs while the print server is saving an IPDS job to a rewritable media, the IPDS host will send the remainder of the job from its latest checkpoint, based on the stacked page counts it has received from the printer. Xerox FreeFlow® Print Server is not able to automatically append this additional data to the original save job file. Therefore, to ensure that the remainder of the job does not overwrite the original data, before initiating recovery, the user must ensure that a different file name is used for the remainder of the job. This limitation also applies to the save job component of Print and Save jobs. • Xerox FreeFlow® Print Server supports simultaneous printing and saving of the same job, but the page counts reported to the host only reflect the status of pages being printed, not the status of pages being saved. Therefore, if a Print and Save job fails before completion, the number of pages saved may differ from the number of pages printed. • If a Print and Save job terminates abnormally, the host will base its recovery on the count of pages actually stacked at the printer, not on the number of pages saved. In most cases, recovery of the saved portion of the job will not be affected, since Xerox FreeFlow® Print Server will normally save pages faster than it can print them. However, there is a possibility that printing could get ahead of saving. If this occurs, and there happens to be a failure, the host could fail to retransmit some pages that were not saved before the failure. • During a Print and Save job, saving will usually progress faster than printing, while the stacked page counts provided to the 3- 19