Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

APF Page Printer Driver Page Queue Manager

IP.com Disclosure Number: IPCOM000105824D
Original Publication Date: 1993-Sep-01
Included in the Prior Art Database: 2005-Mar-20
Document File: 2 page(s) / 87K

Publishing Venue

IBM

Related People

Condon, JB: AUTHOR [+4]

Abstract

AFP Page Printers must be supplied with high volumes of data in a timely manner to format and then print pages. To insure that the printer is adequately supplied with data to run at rated speed, the data converter must run ahead of the actual print driver. If the printer experiences any errors, the print driver program must be able to reposition the converter to reconvert the data, starting at any page boundary in the datastream. Disclosed is a design for Page Queue Manager, which aids in the repositioning of the conversion process.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 52% of the total text.

APF Page Printer Driver Page Queue Manager

      AFP Page Printers must be supplied with high volumes of data in
a timely manner to format and then print pages.  To insure that the
printer is adequately supplied with data to run at rated speed, the
data converter must run ahead of the actual print driver.  If the
printer experiences any errors, the print driver program must be able
to reposition the converter to reconvert the data, starting at any
page boundary in the datastream.  Disclosed is a design for Page
Queue Manager, which aids in the repositioning of the conversion
process.

      Page Queue Manager maintains a Page Queue which is a list of
Page Queue Entries (PQEs).  Each PQE contains information needed to
reset the various print driver components to reprocess a page of data
in the datastream.  This data includes:

o   information stored by the data Converter that it needs to reset
    its environment so that it can reprocess a page of data
o   a list of the (error/warning/informational) messages for the
    given page
o   a list of resources (fonts, etc.) needed for the given page
o   file offset in the datastream file where data for this page
    begins
o   the simulated printer page-id for this page
o   the page number of this page in the user's document
o   number of copies of this page to be printed
o   printer bin which should be used for this page
o   various flags that help manage this PQE
o   printfile-specific information, including
    -   what type of page is being processed, header page, trailer
        page, normal document page, etc.)
    -   type of data being converted (AFPDS, ASCII, etc.)
    -   file handle of this print file
o   job-specific information

    -   job accounting information

    -   job-level message list

    -   job-level print parameters

    -   job start/stop date/time

      This information is actually kept in a hierarchical form, and
the job-specific information and printfile-specific information are
kept in records referenced by each PQE, as illustrated in the figure.

      Each time a new print job is begun, Page Queue Manager creates
a new Job Record and initializes it to contain all pertinent
information.  Each time a new portion of the print job is begun
(header page, user's document, message page, trailer page, etc.) a
new Printf...