Abstract:
Print jobs are automatically and transparently spooled in a device-independent format, such as an enhanced metafile format. The enhanced metafile format provides a format into which documents are readily converted and which occupies a minimal amount of storage space. Each spooled print job is asynchronously printed relative to a program that requested the print job. Such spooled print jobs are de-spooled in a background processor mode. An operating system provides the resources for converting a print job into enhanced metafile format and spooling the print job in the enhanced metafile format.

Description:
CROSS-REFERENCE TO RELATED APPLICATION 
     This application is a continuation of U.S. patent application Ser. No. 08/318,069 filed Oct. 5, 1994, now U.S. Pat. No. 5,602,974. 
    
    
     TECHNICAL FIELD 
     The present invention relates generally to data processing systems and, more particularly, to the spooling of documents in a device independent fashion in a data processing system. 
     BACKGROUND OF THE INVENTION 
     Certain conventional computer systems allow documents to be spooled in a raw data format. When spooling is completed, the raw data for the document is stored on a storage device in a spool file. The spooled document may then later be &#34;de-spooled&#34; to retrieve the data for the document from the storage and forward the data to the target printer. 
     One disadvantage of spooling in the raw data format is that the raw data format is device specific. The raw data must be sent to the target printer. If the target printer becomes unavailable, the whole process must be repeated again. Another drawback of spooling in the raw data format is that documents that are spooled in such a format typically occupy a large amount of storage space. Such spooling in the raw data format also suffers the additional drawback in that the conversion from abstract printer commands to the raw data format is often time-consuming. 
     SUMMARY OF THE INVENTION 
     In accordance with a first aspect of the present invention, a method is practiced in a computer system, such as a portable computer, having printers for printing documents and a storage device. In this method, a request from a requesting party to print a document on a selected one of the printers is received. The document is spooled so that it is stored on the storage device in a device-independent format. The document is then later de-spooled to print the document on the selected printer. Thus, where the computer system is a portable computer, the document may be spooled while the portable is disconnected from the printers and then later de-spooled when the portable computer is again connected to the printers. 
     In accordance with another aspect of the present invention, a method is practiced in a computer system having a storage device, printers for printing documents and a processor running an operating system and at least one other program. The operating system includes functions that the program may call to print documents on the printers. In this method, a request from a selected one of the programs to print a document on a selected one of the printers is received. The calls to the functions the programs may call to print documents on the printers are received from the selected program in order to print the document on the selected printer. The received calls are converted into information that is held in at least one enhanced metafile. This enhanced metafile is stored on the storage device. The enhanced metafile is retrieved and played back to print the document on a selected printer. 
     In accordance with a further aspect of the present invention, a method is practiced on a computer system having a workstation, printers for printing documents, and a print server that is responsible for controlling the printers. The workstation runs an operating system and an application program. A separate storage device is provided for the print server. In this method, a request is made by the application program to print a document on the selected one of the printers. The document is then spooled on the storage device of the print server in an enhanced metafile format. 
     In accordance with yet another aspect of the present invention, a computer system includes printers for printing documents, as well as a storage device for storing information. The computer system also includes a processor that runs an operating system and an application program. The operating system includes an interface through which the application program may request to print a document. The operating system also includes an enhanced metafile recorder for recording the request to the interface to print the document as a set of enhanced metafiles. The operating system additionally provides a spooler for causing the document to be spooled in a spool file that holds the set of enhanced metafiles produced by the enhanced metafile recorder. 
     In accordance with another aspect of the present invention, a distributed system includes printers for printing print jobs and a print server for controlling access to the printers. The print server includes a first spooler for spooling the print jobs and a storage device for storing the spooled print jobs. The distributed system also includes a workstation that runs an application program and an operating system. The operating system provides an enhanced metafile converter and a second spooler. The enhanced metafile converter converts a print job into an enhanced metafile format when the application program requests to print the print job on a selected one of the printers. The second spooler cooperates with the first spooler at the print server to spool the print job after it has been converted into the enhanced metafile format by the enhanced metafile converter. 
    
    
     BRIEF DESCRIPTION OF THE DRAWINGS 
     FIG. 1 illustrates the format of an enhanced metafile. 
     FIG. 2 is a block diagram illustrating a computer system that is suitable for practicing a preferred embodiment of the present invention. 
     FIG. 3 is a block diagram illustrating components that play a role in enhanced metafile spooling in the preferred embodiment of the present invention. 
     FIG. 4 is a flowchart that provides a overview of the steps performed in enhanced metafile spooling in the preferred embodiment of the present invention. 
     FIG. 5 is a flowchart illustrating the steps that are performed to convert a print job into enhanced metafile format in the preferred embodiment of the present invention. 
     FIG. 6 is a flowchart illustrating the steps that are performed in processing function calls made by an application program to print a print job in the preferred embodiment of the present invention. 
     FIG. 7 illustrates the format of a spool file in accordance with the preferred embodiment of the present invention. 
     FIG. 8 illustrates a sequence of records that occurs in the metafile sequence of the spool file of FIG. 7. 
    
    
     DETAILED DESCRIPTION OF THE INVENTION 
     The preferred embodiment of the present invention facilitates spooling of print jobs in a device independent format. In particular, the preferred embodiment of the present invention spools print jobs in the enhanced metafile format. Print jobs are easily and quickly converted into the enhanced metafile format for spooling. The enhanced metafile format has the additional advantage that it occupies substantially less space than typical raw data formats. 
     An enhanced metafile as used herein refers to the enhanced metafile format that is employed in the Microsoft WINDOWS NT Operating System, sold by Microsoft Corporation of Redmond, Wash. An enhanced metafile is a file that stores information for displaying or printing a picture in a device independent format. Metafiles are typically contrasted with bitmaps in that metafiles typically hold metadata that specify how to draw the associated picture rather than bitmaps of the associated picture. 
     Before discussing how print jobs are spooled as enhanced metafiles, it is helpful to review the format of an enhanced metafile 10 (shown in FIG. 1). Each enhanced metafile 10 includes a header 12 and may optionally include a description string 14. The remainder of the enhanced metafile 10 is formed by metafile records 16 and an optional palette 18. 
     The enhanced metafile header 12 holds a number of different types of information, including dimension information, resolution information, version information and size information. Specifically, the enhanced metafile header is defined as follows (in C++ code): 
     
         __________________________________________________________________________typedef struct tagENHMETAHEADER  DWORD  iType;  // Record type EMR.sub.-- HEADER.  DWORD  nSize;  // Record size in bytes. This may be greater            // than the size of (ENHMETAHEADER).  RECTL  rclBounds;            // Inclusive-inclusive bounds in device units.  RECTL  rclFrame;            // Inclusive-inclusive Picture Frame of            // metafile in .01 mm units.  DWORD  dSignature;            // Signature. Must be ENHMETA.sub.-- SIGNATURE.  DWORD  nVersion;            // Version number.  DWORD  nBytes; // Size of the metafile in bytes.  DWORD  nRecords;            // Number of records in the metafile.  WORD   nHandles;            // Number of handles in the handle table.            // Handle index zero is reserved.  WORD   sReserved;            // Reserved. Must be zero.  DWORD  nDescription;            // Number of chars in the unicode description string.            // This is 0 if there is no description string.  DWORD  offDescription;            // Offset to the metafile description record.            // This is 0 if there is no description string.  DWORD  nPalEntries;            // Number of entries in the metafile palette.  SIZEL  szlDevice;            // Size of the reference device in pixels.  SIZEL  szlMillimeters;            // Size of the reference device in millimeters.}   ENHMETAHEADER;__________________________________________________________________________ 
    
     The optional description field 14 of the enhanced metafile 10 is used to hold a written description that identifies what is contained within the enhanced metafile. 
     The enhanced metafile records 16 form the core of the enhanced metafile 10. Each enhanced metafile record 16 corresponds to a graphics device interface (GDI) function (which will be described in more detail below) for drawing the picture associated with the metafile. Each enhanced metafile record 16 has the following format. 
     
         ______________________________________typedef struct tagENHMETARECORD  DWORD    iType;   // Record type EMR.sub.-- XXX  DWORD    nSize;   // Record size in bytes  DWORD    dParm 1!;               // DWORD Array of parameters} ENHMETARECORD;______________________________________ 
    
     The iType field of the enhanced metafile record 16 holds a value that specifies the type of enhanced metafile record. Listed below is a sampling of the types of enhanced metafile records and their corresponding iType values. 
     
         __________________________________________________________________________Record             Value                 Record             Value__________________________________________________________________________EMR.sub.-- ABORTPATH              68 EMR.sub.-- FILLPATH                                    62EMR.sub.-- ANGLEARC              41 EMR.sub.-- FILLRGN 71EMR.sub.-- ARC     45 EMR.sub.-- FLATTENPATH                                    65EMR.sub.-- ARCTO   55 EMR.sub.-- FRAMERGN                                    72EMR.sub.-- BEGINPATH              59 EMR.sub.-- GDICOMMENT                                    70EMR.sub.-- BITBLT  76 EMR.sub.-- HEADER  1EMR.sub.-- CHORD   46 EMR.sub.-- INTERSECTCLIPRECT                                    30EMR.sub.-- CLOSEFIGURE              61 EMR.sub.-- INVERTRGN                                    73EMR.sub.-- CREATEBRUSHINDIRECT              39 EMR.sub.-- LINETO  54EMR.sub.-- CREATEDIBPATTERNBRUSHPT              94 EMR.sub.-- MASKBLT 78EMR.sub.-- CREATEMONOBRUSH              93 EMR.sub.-- MODIFYWORLDTRANSFORM                                    36EMR.sub.-- CREATEPALETTE              49 EMR.sub.-- MOVETOEX                                    27EMR.sub.-- CREATEPEN              38 EMR.sub.-- OFFSETCLIPRGN                                    26EMR.sub.-- DELETEOBJECT              40 EMR.sub.-- PAINTRGN                                    74EMR.sub.-- ELLIPSE 42 EMR.sub.-- PIE     47EMR.sub.-- ENDPATH 60 EMR.sub.-- PLGBLT  79EMR.sub.-- EOF     14 EMR.sub.-- POLYBEZIER                                    2EMR.sub.-- EXCLUDECLIPRECT              29 EMR.sub.-- POLYBEZIER16                                    85EMR.sub.-- EXTCREATEFONTINDIRECTTW              82 EMR.sub.-- POLYBEZIERTO                                    5EMR.sub.-- EXTCREATEPEN              95 EMR.sub.-- POLYBEZIERTO16                                    88EMR.sub.-- EXTFLOODFILL              53 EMR.sub.-- POLYDRAW                                    56EMR.sub.-- EXTSELECTCLIPRGN              75 EMR.sub.-- POLYDRAW16                                    92EMR.sub.-- EXTTEXTOUTA              83 EMR.sub.-- POLYGON 3EMR.sub.-- EXTTXTOUTW              84 EMR.sub.-- POLYGON16                                    86EMR.sub.-- POLYLINE              4  EMR.sub.-- SETBRUSHORGEX                                    13EMR.sub.-- POLYLINE16              87 EMR.sub.-- SETCOLORADJUSTMENT                                    23EMR.sub.-- POLYLINETO              6  EMR.sub.-- SETDIBITSTODEVICE                                    80EMR.sub.-- POLYLINETO16              89 EMR.sub.-- SETMAPMODE                                    17EMR.sub.-- POLYPOLYGON              8  EMR.sub.-- SETMAPPERFLAGS                                    16EMR.sub.-- POLYPOLYGON16              91 EMR.sub.-- SETMETARGN                                    28EMR.sub.-- POLYPOLYLINE              7  EMR.sub.-- SETMITERLIMIT                                    58EMR.sub.-- POLYPOLYLINE16              90 EMR.sub.-- SETPALETTEENTRIES                                    50EMR.sub.-- POLYTEXTOUTA              96 EMR.sub.-- SETPIXELV                                    15EMR.sub.-- POLYTEXTOUTW              97 EMR.sub.-- SETPOLYFILLMODE                                    19EMR.sub.-- REALIZEPALETTE              52 EMR.sub.-- SETROP2 20EMR.sub.-- RECTANGLE              43 EMR.sub.-- SETSTRETCHBLTMODE                                    21EMR.sub.-- RESIZEPALETTE              51 EMR.sub.-- SETTEXTALIGN                                    22EMR.sub.-- RESTOREDC              34 EMR.sub.-- SETTEXTCOLOR                                    24EMR.sub.-- ROUNDRECT              44 EMR.sub.-- SETVIEWPORTEXTEX                                    11EMR.sub.-- SAVEDC  33 EMR.sub.-- SETVIEWPORTORGEX                                    12EMR.sub.-- SCALEVIEWPORTEXTEX              31 EMR.sub.-- SETWINDOWEXTEX                                    9EMR.sub.-- SCALEWINDOWTEXTEX              32 EMR.sub.-- SETWINDOWORGEX                                    10EMR.sub.-- SELECTCLIPPATH              67 EMR.sub.-- SETWORLDTRANSFORM                                    35EMR.sub.-- SELECTOBJECT              37 EMR.sub.-- STRETCHBLT                                    77EMR.sub.-- SELECTPALETTE              48 EMR.sub.-- STRETCHDIBITS                                    81EMR.sub.-- SETARCDIRECTION              57 EMR.sub.-- STROKEANDFILLPATH                                    63EMR.sub.-- SETBKCOLOR              25 EMR.sub.-- STROKEPATH                                    64EMR.sub.-- SETBKMODE              18 EMR.sub.-- WIDENPATH                                    66__________________________________________________________________________ 
    
     Each enhanced metafile record 16 also includes an nSize field that specifies the size of the enhanced metafile record in bytes and a dParm field that holds an array of parameters. 
     The optional color palette field 18 of the enhanced metafile 10 holds a palette sequence for a foreground palette to be used when the picture associated with the enhanced metafile is drawn. 
     FIG. 2 is a block diagram of an environment suitable for practicing the preferred embodiment of the present invention. This environment includes a workstation 20 that may communicate with a print server 22. The print server 22 is responsible for printers 24A, 24B, and 24C and includes its own secondary storage 39. A logical port is associated with each of the printers 24A, 24B, and 24C. Those skilled in the art will appreciate that the configuration shown in FIG. 2 is merely illustrative and that the present invention may be practiced in other environments as well. 
     The workstation 20 includes a central processing unit (CPU) 26 that has access to a memory 28 and a secondary storage 30. The memory 28 holds a copy of an operating system 32 and an application program 33 that may be run on the CPU 26. In the preferred embodiment of the present invention, the operating system 32 includes the Win32 API, such as found in Microsoft WINDOWS NT operating system. Moreover, the operating system 32 includes code for implementing enhanced metafile spooling as described herein. The workstation further includes input/output devices, such as a mouse 34, a keyboard 36 and a video display 38. 
     In the preferred embodiment of the present invention, a program, such as application program 33, initiates a request to print a document on one of the printers 24A, 24B, or 24C. Instead of the document being converted into a format specific to the selected printer, the document is converted into the enhanced metafile format and spooled. The application program 33 and the user believe the document has been printed in conventional fashion when the document has, instead, been spooled. The spooling of the document as an enhanced metafile is entirely transparent to the application program 33 and to the user. The spool file is then used to print the document as a background thread. 
     FIG. 3 is a block diagram showing some of the software components and structures that play a role in the preferred embodiment of the present invention. The application program 33 is the program that initiates a printing request. Those skilled in the art will appreciate that the application program may be any type of program that is capable of initiating a printing request. The application program 33 initiates a printing request by making calls to functions in the graphical device interface (GDI) 40. The GDI 40 is part of the operating system 32 that serves as an interface between the application program 33 and lower level functions. The GDI 40 provides functions that the application program 33 may call to display graphics and formatted text. In the preferred embodiment of the present invention, the GDI 40 includes the 16-bit GDI and 32-bit GDI found in the Microsoft WINDOWS NT Operating System, as well as additional components. The GDI interacts with a printer driver 41 during creation of a spool file and during playback of the enhanced metafile records of the spool file. 
     The GDI 40 interacts with a spooler process 42, that is part of the operating system 32 run on the workstation 20. The spooler process 42 interacts with a router 44 to send print data and information to its appropriate destination. The router 44 is a printing component that locates the printer requested by the application program 33 and sends information from the workstation spooler 42 to the appropriate print server spooler. As the workstation 20 may be connected both to a local print server 22 (as shown in FIG. 2) and to other networks that include additional print servers for remote printers, the router 44 must decide where the requested printer is located. The router 44 sends information initially from the spooler 42 to the appropriate net provider 46 and 48 or local spooler process 50. For purposes of simplicity, in the example shown in FIG. 3, it is assumed that the information is passed to a local spooler 50. The local spooler 50 is responsible for creating the spool file 52 that holds the enhanced metafiles that are created for the document. 
     FIG. 4 is a flowchart showing the steps that are performed to print a document when enhanced metafile spooling is used in the preferred embodiment of the present invention. Initially, the application begins to print a document (step 54). In order to print a document, the application 33 must create a device context. The device context is a data structure that holds information about a graphics output device, such as a printer. These attributes determine how the functions of the GDI 40 work on the target printer. The application program 33 must first obtain a handle to a device context for the printer to which the application wishes to print. In addition, the window manager sets the visible region to be empty so that no output is produced when a GDI function is called. The window manager is part of the operating system 32 that is responsible for managing windows and the visible region is a structure maintained by the window manager to determine what is visible to a user in a window. 
     In step 56, the document is converted into enhanced metafile format and stored in the spool file 52. FIG. 5 is a flowchart of the steps that are performed to store the document as a set of enhanced metafiles. Initially, a device context for the enhanced metafile is created by calling the CreateEnhMetaFile() function. This function creates a device context for an enhanced format metafile. This function is passed a number of parameters, including a handle to a reference device for the enhanced metafile. A handle is a numerical identifier that uniquely identifies a reference device. In this case, the handle to the reference device is a handle to the device context of the target printer. 
     The handle to the enhanced metafile device context returned by the function is then passed as a parameter to each of the GDI function calls that the application program 33 issues to print the document (step 66). The operating system 32 converts each GDI function into an enhanced metafile record and appends the record to the end of the enhanced metafile (step 68). The operating system 32 includes an enhanced metafile recorder for converting the GDI function calls to enhanced metafile records. Each page of the document is stored as a separate enhanced metafile as will be discussed in more detail below. 
     The operating system 32 has a means for differentiating between GDI function calls that are to be spooled in an enhanced metafile and those that are to be directly executed. FIG. 6 shows a flowchart of the steps that are performed in the preferred embodiment of the present invention to differentiate such GDI function calls and to record function calls in enhanced metafiles as required. Initially, the application program makes a GDI function call that passes the device context of the enhanced metafile as a parameter (step 70). Like other GDI function calls, this GDI function call is passed to a validation layer of the operating system 32 (step 72). The validation layer is responsible for examining the parameters of the function call to make sure that they are correct. The preferred embodiment of the present invention embellishes the validation layer to check whether the device context passed as a parameter to the GDI function call refers to an enhanced metafile (step 74). As described above, if the device context is an enhanced metafile, the enhanced metafile recorder is called to convert the GDI function call into an enhanced metafile record (step 76). Next, in order to maintain transparency of the enhanced metafile spooling, the preferred embodiment of the present invention is designed to call the GDI function so that the application program believes that the document is printing. The complication, however, is that the system does not desire for the GDI functions to produce output. Accordingly, the visible region used by a window manager is set to be empty so that no output is produced as discussed above. In step 80, the GDI function is called. If the device context is not for an enhanced metafile as checked in step 74, the GDI function is simply called directly (step 80). 
     Returning to FIG. 4, step 56 involves recording the commands in the metafiles and storing the metafiles in a spool file. Two separate recorders are used to create the enhancement metafiles and the spool file. In particular, the spool file recorder is used to create the spool file and the spool file records contained therein. In contrast, the second recorder is responsible for converting graphics API calls into enhanced metafile records that are stored within the enhanced metafiles. FIG. 7 shows the format of such a spool file 82. The spool file 82 includes an identifier 84 that is 8 bytes in length. The spool file recorder is responsible for opening a new spool file, recording the identifier 84 and creating a SF --  STARTDOC record in response to a STARTDOC command from the application program. The SF --  STARTDOC record 86 has the following format: 
     
         ______________________________________typedef struct.sub.-- SR.sub.-- STARTDOCULONG      iType;     // SF.sub.-- STARTDOCULONG      cj;        // Record length in bytes.ULONG      iOffDocName;                 // Offset to DocName StringULONG      iOffOutput;                 // Offset to Output String} SR.sub.-- STARTDOC, *PSR.sub.-- STARTDOC, FAR *LPSR.sub.-- STARTDOC;______________________________________ 
    
     This record designates the start of the document within the spool file. 
     The SF --  STARTDOC record 86 is followed by an SF --  MODECHANGE record 88. The SF --  MODECHANGE record 88 is followed by a DevMode structure that holds information such as paper orientation, paper size, paper length, paper width, color information and the like, which enables the document to properly be printed on the target printer. 
     The spool file 82 also includes a metafile sequence 90 that is created by the recorders. FIG. 8 shows an example of a series of records that are repeated within the metafile sequence 90. In particular, this sequence is repeated for each page of the document to be printed. The SF --  STARTPAGE record 94 is created by the spool file recorder in response to the STARTPAGE command from the application program. An enhanced metafile is created in response to the STARTPAGE command to receive the contents of the page. The SF --  STARTPAGE record 94 designates the start of a page of the document and has the following format: 
     
         ______________________________________typedef struct.sub.-- SR.sub.-- STARTPAGEULONG      iType;    // SF.sub.-- STARTPAGEULONG      cj;       // Record length in bytes.USHORT     iPhysPage;                // Page number in the file. (1-N)USHORT     iFormat;  // Data format. (SFF.sub.-- JOURNAL)ULONG      iLogPage; // Page number according to the app.} SR.sub.-- STARTPAGE;______________________________________ 
    
     The SF --  STARTPAGE record 94 is followed by an SF --  METAFILE record 96 that holds the name of the metafile that has the information for the associated page. The metafiles are created by the second recorder, as discussed above. Specifically, the GDI graphics API calls are converted into metafile records that are held within the metafiles. 
     The SF --  METAFILE record 96 is followed by an SF --  ENDPAGE record that designates the end of the page. The SF --  ENDPAGE record 96 is created by the spool file recorder in response to an ENDPAGE command from the application program. The ENDPAGE command indicates that the application is done drawing. The metafile is then closed and the name of the metafile is recorded in the SF-METAFILE record 94. The SR --  ENDPAGE record has the following format: 
     
         ______________________________________typedef struct.sub.-- SR.sub.-- ENDPAGEULONG iType; //SF.sub.-- ENDPAGEULONG cj;} SR.sub.-- ENDPAGE;______________________________________ 
    
     The metafile sequence 90 (FIG. 7) is followed by an SF --  ENDDOC record that is created in response to an ENDDOC command for the application. This record designates the end of the document and has the following format: 
     
         ______________________________________typedef struct.sub.-- SR.sub.-- ENDDOCULONG iType; // SF.sub.-- ENDDOCULONG cj;} SR.sub.-- ENDDOC;______________________________________ 
    
     As shown in FIG. 4, after the commands have been recorded in the metafiles and the metafiles stored in the spool file in step 56, the application program 33 is advised that it is done spooling the document (step 58). A background thread at the print server 22 for the port associated with the target printer is kicked off to print the spooled document (step 60). The background thread queues print jobs and then causes the document to be de-spooled and printed on the target printer (step 62). The operating system 32 includes functions for playing back enhanced metafiles so as to generate the picture on the printer that is associated with the enhanced metafiles. The PlayEnhMetaFile() function plays back the enhanced metafile records so as to produce the corresponding image. This function is one of those provided by the GDI. 
     The preferred embodiments of the present invention described herein provides several benefits. First, the turnaround time experienced by application programs is much faster because the application program is told that it is done spooling more quickly than in conventional systems. As was described above, print jobs may be quickly and easily spooled as enhanced metafiles. Moreover, the printing may occur asynchronously relative to the application program. The preferred embodiment of the present invention also provides device independence that allows a user to print pages at random, to print pages out of order, and to view the contents of the document on the screen without the necessity of the device driver for a target printer being installed. The device independence also allows a user to select any of a number of printers for printing a document. For example, the user may select a draft printer which is less expensive to use to print the document and proof the document. After the document has been proofed, the user may then request to print the document on a more expensive printer. 
     While the present invention has been described with reference to a preferred embodiment thereof, those skilled in the art will appreciate that various changes in form and detail may be made without departing from the intended scope of the claims as defined in the appended claims.