Method for organizing files in a library in a network printing system

[0002] This application is related to the following co-pending and commonly-assigned applications:

[0003] Application Ser. No. 08/924,609, filed on same date herewith, by Chris Samuel Goertz, Leonard Corning Lahey, Robert Curt Nielsen, Dwight Ross Palmer, and Luana Vigil, entitled “A Method For Creating And Organizing A Job Ticket In A Network Printing System,” (now U.S. Pat. No. 6,732,295);

[0004] Application Ser. No. 08/932,065, filed on same date herewith, by Leonard Corning Lahey, Deborah Elisabeth Neuhard, and Dwight Ross Palmer, entitled “A Method For Organizing Files Associated With A Job Ticket In A Network Printing System,” (now U.S. Pat. No. 5,999,945);

[0005] Application Ser. No. 08/929,997, filed on same date herewith, by Deborah Elisabeth Neuhard, Robert Curt Nielsen, Dwight Ross Palmer, and Luana Vigil, entitled “A Method For Organizing Raster Image Processor Files Associated With a Job Ticket Used in a Network Printing System,” (now U.S. Pat. No. 6,052,198);

[0006] Application Ser. No. 08/932,066, filed on same date herewith, by Deborah Elisabeth Neuhard, Robert Curt Nielsen, Dwight Ross Palmer, and Luana Vigil, entitled “Method For Customizing Print Attribute Choices Based On Selected Model, Media, And Printer,” (now U.S. Pat. No. 6,335,795);

[0007] Application Ser. No. 08/929,844, filed on same date herewith, by Leonard Coming Lahey, entitled “Method for Real Time Customization of a Dialog Box for Accessing a Library Within a Network Printing System,”

[0008] Application Ser. No. 08/929,637, filed on same date herewith, by Kate Goes In Center, Deborah Elisabeth Neuhard, Robert Curt Nielsen, and Dwight Ross Palmer, entitled “A System, Method, and Program for Using Animations to Show Page Layout Combinations in a User Interface for Submitting Print Jobs,” (now U.S. Pat. No. 5,953,007); and

[0009] Application Ser. No. 08/929,627, filed on same date herewith, by Coming Lahey, Deborah Elisabeth Neuhard, and Dwight Ross Palmer, entitled “A System, Method, and Program for Including Within a User Interface Having File Menu Options an Ability to Make a New File Like a Pre-Existing File Wherein Any Pre-Existing File Can Be a Template for a New File,” (now U.S. Pat. No. 6,239,802);

[0010] all of which applications are incorporated herein by reference.

[0011] 1. Field of the Invention

[0012] The present invention relates to the management of print files associated with a job ticket and, in particular, to a method, apparatus, and article of manufacture for managing print files by managing a backup storage device to store accumulated print files.

[0013] 2. Description of the Related Art

[0014] Network printing systems generally comprise an assemblage of different printers, client computers, servers, and other components connected over a network. A print job is assembled at a client computer and transmitted over the network to a server linked to a variety of printers. The printers may have different printing capabilities. Thus, for a given submitted print job, some printers in the network may not be able to process the print job. To route print jobs through a network printing system, International Business Machines Corporation (IBM) provides Printing Systems Manager (PSM) products that provide centralized and distributed management of a network printing system. The IBM PSM systems manage the flow of print jobs and insure that a print job is routed to a printer that can handle the job.

[0015] A print job is comprised of one or more electronically-stored files and the print attributes therefor. The print attributes inform the printer how to process the files. To assemble print jobs, prior art systems include software installed on the client computer that displays a graphical user interface (GUI). Using a mouse, keyboard, etc., the user selects from a menu of options displayed in the GUI the components and print attributes for a print job. The client computer, under control of the installed software, would then create an electronically-stored job ticket based on the information entered by the user.

[0016] Job tickets typically only define the print attributes for a single file. However, a document may be comprised of multiple files, each having one or more print attributes. In the prior art, an user putting together a document comprised of multiple files would have to manually keep track of the location of the different files and manually assemble the files for printing. In some instances, a library of print files is maintained.

[0017] However, library storage is often inadequate to manage print files because the print files are usually rather large and rapidly consume the available space in the library. In the prior art, to free up space in the library, the user typically manually transfers files from the library to a backup unit. Still further, the user often compresses files removed from the library to the backup unit. Such prior art systems prove cumbersome when the user needs to access a print file in the backup unit because the user must first manually go to the backup location to access the desired print file, decompress the print file, and then relocate the print file to the library. Accumulation of additional print files over time only increases the complexity of the user's library management responsibilities. Thus, there is a need in the art for network printing systems that eliminate these problems and facilitate the printing of complex documents comprised of multiple files stored throughout the network printing system.

[0018] To address the requirements described above, the present invention discloses a method, apparatus, and article of manufacture for managing print files associated with a job ticket describing a plurality of print files included in a print job. The print files include data representing graphical images. A first storage device stores print files. When space usage in the first storage device has exceeded a predetermined limit, print files from the first storage device are migrated to a second storage device. A stub file is generated that includes information on a migrated file. The stub file is stored where the migrated print file was located in the first storage device. A print file is selected to include in the print job described in the job ticket. Upon selection of a print file represented by a stub file stored in the first storage device, the stub file is accessed. When the stub file is accessed, the stub file is replaced with the selected print file from the second storage device. The selected print file is transmitted from the first storage device to a printer when the print job including the selected print file is submitted to a printer.

[0019] In further embodiments, an index describing a job ticket and associated print files is created. The index is then communicated to a database for storage therein. The job ticket and the associated print files described in the index are transferred to a location in the first storage device.

[0020] In still further embodiments, the print file is selected by first searching the database and selecting a print file or job ticket described in an index located during the search of the database.

[0021] In yet further embodiments, a server provides communication between the first and second storage devices, migrates print files, generates the stub file, accesses the stub file, and replaces the stub file. Further, a computer networked to the server is used to select the print files to add to the job ticket.

[0022] It is an object of the present invention to provide ostensibly unlimited storage in a library which stores job tickets and print files.

[0023] It is still a further object that print files stored in the library be migrated to a backup storage device when the library reaches a storage usage threshold.

[0024] It is yet a further object that any programs used to create a job ticket can access a stub file in the library which represents the print file stored in the backup storage device. The stub file provides location, name, and size information on the file the job ticket is accessing.

[0025] It is still another object that when the stub file is accessed, the print file represented by the stub file is recalled from the backup storage device to replace the stub file in the library. The recalled print file is now accessible when processing the job ticket.

[0026] It is yet a further object that a database program in the server manage index files describing the job ticket and print files stored in the library and that the client computer include a database program to search the indices in the server database to locate a print file or job ticket.

[0027] It is also an objective to include in the computer a GUI to create job tickets and allow the GUI to interface with the server database and library to perform searches therein.

[0028] Referring now to the drawings in which like reference numbers represent corresponding parts throughout:

[0029] FIG. 1 is a block diagram illustrating an exemplary hardware environment for a network printing system in accordance with the present invention;

[0030] FIG. 2 is a block diagram illustrating a preferred embodiment of a job ticket data structure in accordance with the present invention;

[0031] FIGS. 3, 4a, 4b, 4c, 5a, 5b, 6a, 6b, 6c, 7a, 7b, 8, 9, and 10 illustrate a embodiment of a graphical user interface (GUI) displayed on a monitor in accordance with the present invention; and

[0032] FIG. 11 is a flowchart that illustrates the general logic of a message or event-driven operating system and application program performing the steps of the present invention.;

[0033] FIG. 12 is a flowchart that illustrates the general logic for a preferred embodiment of a routine performing the steps of the present invention.

[0034] FIG. 13 is a block diagram illustrating a preferred embodiment of the software and hardware structure of the present invention.

[0035] FIG. 14 is a flowchart that illustrates the general logic for organizing files in a library in accordance with the present invention.

[0036] FIG. 15 illustrates a preferred embodiment of a dialog box used to search for job ticket files in accordance with the present invention.

[0037] FIG. 16 illustrates a preferred embodiment of a dialog box used to search for print files in accordance with the present invention.

[0038] FIG. 17 illustrates a preferred embodiment of a dialog box used to customize the display of the dialog box used to search for files in accordance with the present invention.

[0039] FIG. 18 is a flowchart that illustrates the general logic for building a print job with a customizable search dialog box in accordance with the present invention.

[0040] In the following description, reference is made to the accompanying drawings which form a part hereof, and which is shown, by way of illustration, several embodiments of the present invention. It is understood that other embodiments may be utilized and structural changes may be made without departing from the scope of the present invention.

[0041] FIG. 1 shows a preferred embodiment of a network printing system 2 adapted to incorporate the present invention. The network printing system 2 comprises a plurality of client computers 4a, b, cthat are connected to an InfoPrint Multiple Printer Controller (MPC) server 6 via a network 8 (e.g., Token-ring, LAN, Ethernet, WAN, TCP/IP, etc.).

[0042] In the preferred embodiment, the client computers 4a, b, ccomprise personal computers that execute under the control of an operating system, such as the WINDOWS operating system. However, those skilled in the art will recognize that the client computers 4a, b, ccould comprise any type of computer such as a workstation, mainframe, etc., and the operating system could comprise any operating system, such as OS/2, OS/390, MVS, VM, AIX, MACINTOSH, LNIX, etc. Installed on each client computer 4a, b, cis InfoPrint Submit software 10. The InfoPrint Submit software 10 configures the client computers 4a, b, cto allow the user to create and submit a job ticket in accordance with the present invention. Attached to each client computer 4a, b, cis an input device 12a, b, c(e.g., keyboard, mouse pointing device, voice activated input device, touch sensitive display, etc.), monitor 14a, b, c(e.g., CRT, LCD displays, etc.), as well as a data communication device 16a, b, c(e.g. modems, network interfaces, etc.) to interface with the network 8.

[0043] In the preferred embodiment, the InfoPrint MPC server 6 is an RS/6000 workstation that executes under the control of an AIX operating system. However, those skilled in the art will recognize that the InfoPrint MPC server 6 could be comprised of any type of computer such as a personal computer, workstation, server, minicomputer, mainframe, etc., and the operating system could comprise any operating system, such as OS/390, MVS, VM, OS/2, WINDOWS, MACINTOSH, UNIX, etc. Installed in the InfoPrint MPC server 6 is a spooler/scheduler 20, a Print Services Facility (PSF) device specific subsystem (DSS) 22, an AIX DSS 24, and an IC70 DSS 26.

[0044] The spooler/scheduler 20 is comprised of the InfoPrint executable code and includes a suite of applications. The spooler/scheduler 20 receives print jobs from the client computers 4a, b, cand generates printer files that are transmitted to a printer 28, 30, 31 or 32 that can appropriately handle the print job. In this way, the user may elect to not specify a printer in the network printing system 2 and let the spooler/scheduler 20 select an appropriate printer 28, 30, 31 or 32.

[0045] After processing the print job and selecting a destination printer 28, 30, 31 or 32 for the job, the spooler/scheduler 20 sends the print job to one of the device specific subsystems PSF DSS 22, AIX DSS 24, and IC70 DSS 26. The DSS programs 22, 24, and 26 are device drivers for driving printers 28, 30, 31, 32 attached to the InfoPrint MPC server 6, wherein the PSF DSS 22 drives printers 28 and 30, the AIX DSS 24 drives printer 31, and the IC70 DSS 26 drives printer 32. In the preferred embodiment shown in FIG. 1, the printers attached to the InfoPrint MPC server 6 include an InfoPrint/60 printer 28, an InfoPrint/4000 printer 30, and an InfoColor/70 printer 32.

[0046] Also connected to the network printing system 2 is a library server 34 storing an InfoPrint library 36 of files and job tickets. The client computers 4a, b, cmay directly access, store, view and retrieve files and job tickets from the InfoPrint library 36. The hardware and software arrangement of the library server 34 and InfoPrint library 36 is described in detail below.

[0047] It should be appreciated that, in alternative embodiments, the network printing system 2 may be comprised of components and products other than those discussed above. Moreover, the network printing system 2 can be implemented on different operating systems and hardware. For instance, hardware and software from manufacturers other than IBM may be used to perform the functions of the InfoPrint MPC server 6, the spooler/scheduler 20 and DSS drivers 22, 24, and 26, the library server 34, and the InfoPrint library 36. Printers having printing capabilities different from the disclosed printers 28, 30, and 32 may be used. Further, in alternative embodiments, any number of client computers 4a, b, chaving alternative user interfaces may be used. Still further, the client computers 4a, b, cmay connect to the InfoPrint MPC server 6 via multiple networks and remote lines. Those skilled in the art will recognize that other alternative hardware and software environments may be used without departing from the scope of the present invention. As such, the exemplary environment in FIG. 1 is not intended to limit the present invention.

[0048] The present invention includes the data structure of an electronically-stored job ticket and the computer-implemented method, apparatus, and article of manufacture used to create the job ticket. The job ticket of the present invention maintains information on print attributes and the location of the print files which comprise the print job.

[0049] FIG. 2 shows a preferred embodiment of the hierarchical tree structure arrangement of data within a job ticket 40 as stored in a data structure in a memory or as stored as a file in a data storage device. The first record in the job ticket 40 is a job ticket attribute record 42, which includes identification information, such as the file name containing the job ticket 40, a job ID, the customer name, etc.

[0050] Within each job ticket 40 are also one or more document records, wherein FIG. 2 shows two document records 44 and 46. The document records 44, 46 include all the information the InfoPrint MPC server 6 needs to print a document included in the print job.

[0051] Each document record 44, 46 is associated with one or more part records. Document record 44 is associated with two part records 48 and 50. A part is the smallest component submitted to the printer for printing. For instance, if the document is comprised of a black and white text body with a color cover, one part 48 would be the black and white text and another part 50 would be the color cover.

[0052] Each part record 48, 50 is a grouping of one or more item records. Part record 48 is a grouping of two item records 52 and 54. An item record includes information on a component of the print job. In preferred embodiments, item records 52, 54 may include information on the following item types: a file item; a hardcopy item; a library file item; variable data; and an inventory item.

[0053] A file item is a print image file, such as a TIFF, PostScript, RIP, PDF or PCL file. Included in the item records 52, 54 is information on the location of the item, e.g., the location of the print image file within the network printing system 2 and the location of the source file from which the print image file item was generated. The user may want to know the location of the source file to modify the contents of the print image. The location information included in the item records 52, 54 is used to access the print image files for printing.

[0054] A hardcopy item is a list of scanned TIFF files.

[0055] A library file item is a file archived in the library 36. The library file item may include information on the location of the library file within the library 36.

[0056] Variable data includes files used to create customized print settings to add to the print job, e.g., adding the name and address of the customer to the printed document.

[0057] The inventory item includes information on an item to be packaged with the document 44, 46 which is not printed, such as a diskette, CD-ROM, etc.

[0058] Thus, an “item” includes print image files comprised of data representing graphical images that are associated with the file item, hardcopy item, library file item or variable data item. The item records 52, 54 also include information on files associated with the print image files for the item. Such associated files may include a source file from which the file item was generated, a Raster Image Processor format of the file item, and a viewable version of the format item. For instance, if the file item is a PostScript file, then the viewable version would be in the PDF file format. Other file types may also be associated with the items.

[0059] In the present invention, the job ticket 40 stores print attribute information, such as information on the layout of the printed page, the printer selected, the alignment of the page, and the look of the page, for each element included in the job ticket 40. As used herein, the term “element” means any of the document records 44, 46, part records 48, 50, and item records 52, 54 included in the job ticket 40. Any print attribute information set for an element at a higher hierarchical level in the tree applies to the elements at the lower hierarchical levels which branch from that higher element. For instance, print attribute information set at the document record 44 level automatically applies to the part records 48, 50 and the item records 52, 54 which branch from the document record 44. Print attribute information set at the part record 52 level likewise applies to the items 52, 54 branching therefrom. In this way, the lower level elements inherit the print attributes of the higher level elements from which they branch.

[0060] The print submission attribute record 56 includes information on the print job, such as scheduling options, priority, difficulty, etc. The information in the print submission attribute record 56 does not affect what is printed, but instead concerns the work flow of the print job.

[0061] In preferred embodiments, print attribute information is stored as key/value pairs. The key is the mode or name of the attribute and the value is the value for the operation. For instance, to indicate a selection of a media type for a print job, the print attribute information would be stored as Input Bin/Tray 1. The key is the input bin containing the selected media, and the user selected value is the first tray. This key/value method for representing print attribute information is readily extendible. To add additional values for specific print attribute types, the new value would be described with reference to its key. Thus, when the InfoPrint Submit software 10 and print driver programs 22, 24, 26 are processing the print attribute information, they immediately recognize the operation the value represents.

[0062] The job ticket 40 may be created on the client computer 4a, b, cusing the InfoPrint Submit software 10 installed thereon. The InfoPrint Submit software 10 includes a graphical user interface (GUI) displayed on the monitor 14a, b, cthat the user may use to create the job ticket 40. The InfoPrint Submit software 10 then translates the job ticket 40 created thereby to a format compatible with the InfoPrint MPC server 6.

[0063] The client computer 4a, b, ctransmits this translated job ticket 40 along with the items identified in the item records 52, 54 to the InfoPrint MPC server 6 over the network 8. The InfoPrint MPC server 6 uses the information in the translated job ticket 40 to process the transmitted items 52, 54 and generate printer files based thereon. The InfoPrint MPC server 6 then selects an appropriate printer 28, 30, 31 or 32, to print the print job and transmits the printer files to the selected printer 28, 30, 31 or 32 for printing.

[0064] When printing copies of the items or a part including a group of items, the InfoPrint MPC server 6 prints a cover sheet on top of each set of copies including the information in the job ticket attribute record 42 to identify the set of copies. The user can then gather the copies generated at different printers throughout the network printing system 2 and assemble the final document using the information on the cover sheet for guidance.

[0065] In this way, the present job ticket invention maintains information on all the documents included in a customer order and all information needed by the InfoPrint MPC server 6 to print the different documents within a customer order.

[0066] FIGS. 3, 4a, 4b, 4c, 5a, 5b, 6a, 6b, 6c, 7a, 7b, 8, 9, and 10 are illustrations of the graphical user interface (GUI) 60 provided by the InfoPrint Submit software 10. The user creates the job ticket 40 by entering information into different fields and selecting specific options presented in the GUI 60. Standard user interface mechanisms are preferably implemented in the GUI 60 to provide the user with the necessary functionality and ease of use.

[0067] FIG. 3 shows the GUI 60 presented to the user upon selecting the job ticket option via an icon or command. At the upper portion of the GUI 60 is a main menu item bar 62 that includes main menu items Ticket, Edit, Item, Options, and Help. Selecting one of the main menu items with a mouse or keyboard command, invokes a further submenu of functions available to the user. Table 1 shows the submenus for each main menu item and functions included therein. Table 2 shows all the functions associated with each main menu item and provides a description of the behavior of each of the functions. Below the main menu item bar 62 is a tool bar 64 comprised of icons that represent certain functions. Below the tool bar 64 is an area presenting six fields labeled Name, Description, Customer, Job ID, Copies, and Library. These six fields comprise the information in the job ticket attribute record 42. The user places the cursor in one of the fields with the mouse and then enters the identification information.

[0068] The GUI 60 further includes a tree section 66 for displaying the elements (document records 44, 46 and item records 52, 54) associated with the job ticket 40. FIG. 3 shows only a single document element, Document 1. Associated with each element in the tree section 66 are print attribute page tabs 68a, b, c, d, e, which in the preferred embodiment are radio buttons displayed on the GUI 60. The user can cause the display of a Layout, Print, Align, Look, and Advanced print attribute page 70a, b, c, d, or eby selecting one of the corresponding print attribute page tabs 68a, b, c, d, e. FIG. 3 illustrates the Advanced print attribute page 70e, which includes fields in which the user may specify a transform option to override any conflicting attributes and to build a new document object.

[0069] FIGS. 4a, 4b, 4c, 5a, 5b, 6a, 7b, 7c, 8a, and 8bshow the print attribute pages 70a b, c, dassociated with Document 1 in the tree section 66. Table 3 provides the print attribute pages 70a, b, c, d, eavailable for each type of element. FIGS. 4a, 4b, and 4cillustrate a preferred embodiment of the Layout attribute page 70a, in which the user may specify the layout of the printed pages. FIGS. 4a, bshow drop down menus 72a, b, respectively, of layout options, e.g., whether the pages are printed side by side, booklet style, etc. FIG. 4cshows a drop down menu 74 of side options, e.g., to print on two sides, one side, etc. Table 4 provides a description of the values in the Layout attribute page 70aand the behavior of the Layout attributes.

[0070] FIGS. 5a, billustrate a preferred embodiment of the Print attribute page 70b. FIG. 5ashows a drop down menu for a Printer type 76 field in which the user can specify any printer or a specific printer 28, 30, 31 or 32 to print the Document 1. If the user selects a specific printer 28, 30, 31 or 32, then the InfoPrint Submit software 10 modifies the range of print attribute values available in pages 70a, b, c, d, eto include only those print attribute values supported by the selected printer 28, 30, 31 or 32. FIG. 5bshows a drop down menu for a Paper type 78 field in which the user may select a paper type. Table 5 provides a description of the attributes in a preferred embodiment of the Print attribute page 70band the behavior of the attributes.

[0071] FIGS. 6a, 6b, and 6cillustrate the Align attribute page 70c, which allows the user to specify the orientation and placement of the of the page. Table 6 provides a description of the attributes in a preferred embodiment of the Align attribute page 70cand the behavior of the Align attributes.

[0072] FIGS. 7aand 7billustrate the Look attribute page 70dand accompanying drop down menus. The Look attribute page 70dincludes fields in which the user can set the look of the printed output, e.g., standard, dark, etc., and identify the printer that will receive rasterized data. Table 7 provides a description of the attributes in a preferred embodiment of the Look attribute page 70dand the behavior of the Look attributes.

[0073] FIG. 8 shows a submenu 80 displayed when the user selects the Ticket item from the main menu item bar 62. The functions included in the submenus of the main menu items may be represented as an icon or alphanumeric string displayed in the GUI 60. The submenu 80 represents the functions as alphanumeric strings describing the function. The Ticket submenu 80 includes functions which allow the user to open a previously created job ticket (Open), create a new job ticket (New), save a job ticket the user has modified (Save or Save as), print the opened job ticket 40 (Print Ticket) or submit the job ticket to the InfoPrint MPC server 6 for printing (Submit Job). The Ticket submenu 80 further includes the Submit function which allows the user to enter the information for the print submission attribute record 56. The Submit function allows the user to select a File and Schedule pages into which the user may enter scheduling priority setting information for the job ticket 40. Tables 8 and 9 provide a description of a preferred embodiment of the fields and behavior of such fields in the File and Schedule pages.

[0074] Once the user creates a job ticket, the user may save the job ticket 40 or submit the job ticket 40 to the printing services manager 6 using the Save and Submit Job functions displayed in the Ticket submenu 80.

[0075] FIG. 9 shows an Open dialog box 82 that appears when the user selects the Open function from the Ticket submenu 80 (FIG. 8). The user may select and open one of the previously saved tickets displayed in the Open dialog box 82.

[0076] FIG. 10 shows the tree section 66 with two hardcopy items (Hardcopy 1 and Hardcopy 2) and two file items in PostScript format (alignbox.ps and 6×9.ps). The user may add, modify or delete elements from the tree section 66 using functions included in the Item and Edit main menu items. The Item submenu, shown in Table 1, includes functions which allow the user to add items, including files, hardcopies, library files, and variable data, and add documents. The user adds the hardcopy items using the Insert Hardcopy function and the PostScript file items using the Insert File function within the submenu of the Insert main menu item. The Edit submenu includes functions, shown in Table 1, which allow the user to modify the arrangement of the elements within the tree section 66, i.e., Move Up, Move Down, Remove, Delete.

[0077] FIG. 10 also shows a File attribute page 84 that appears when the user selects a particular file item with the mouse pointer. In FIG. 10, the user has selected the alignbox.ps file item. The file attribute page 84 allows the user to add information to the job ticket 40 on the location of the file item alignbox.ps and a source file from which the file item was generated. A file to print area 86 includes a File field 88 in which the user enters the location of the file item selected in the tree section 66, which in FIG. 8 is the directory path for the file “alignbox.ps.” The user may enter the file location with a keyboard attached to the client computer 4a, b, cor the Browse radio button in the File to Print 84 area. The Browse radio button invokes a file manager GUI, such as is provided with the Microsoft Windows File Manager or Explorer programs. A file format field 90 indicates the format of the file item. This file format may be sniffed from the file name in the File field 88 or entered by the user. A source file field 92 provides the location of the original file from which the file item was generated. The user may enter the directory path for the source file in the source file field 84 using the keyboard or the Browse radio button.

[0078] Using the preferred embodiment of the present invention discussed above, the user may create a job ticket including documents and items, and set print attributes for the documents and items by selecting options in the print attribute pages 70a, b, c, d, e. As discussed, any setting at the document level within the tree section 66 applies to lower level items that branch from the document. There are primarily three ways to change the print attribute values available in the print attribute pages 70a, b, c, d, e. First, as discussed above, when a user selects a printer 28, 30, 31 or 32, the print attribute values reset to the values supported by the selected printer 28, 30, 31 or 32. Second, the InfoPrint Submit software 10 may occasionally query the InfoPrint MPC server 6 to obtain information on all the installed printers and printing options available. The InfoPrint Submit software would then modify the range of attribute values the user may select based on the information received from the InfoPrint MPC server 6 during the query. This process of querying the InfoPrint MPC server 6 to update printing options available on the client computer 4a, b, cis described in detail in the co-pending and commonly-assigned Application Ser. No. 08/932,066, filed on same date herewith, by Deborah Elisabeth Neuhard, Robert Curt Nielsen, Dwight Ross Palmer, and Luana Vigil, entitled “Method For Customizing Print Attribute Choices Based On Selected Model, Media, And Printer,” which application was incorporated by reference above. Still further, the InfoPrint Submit software includes the feature of allowing attribute fields to be added, deleted or modified in the print attribute pages 140. Third, the user may modify, delete, and add print attribute fields to the print attribute pages 70a, b, c, d, e.

[0079] In the preferred embodiment of the GUI 60 as set forth in Tables 1-9, the GUI 60 does not include a function to create the part record 48, 50 discussed above. Users can only create document records 44, 50 and item records 52, 54. However, in alternative embodiments, the job ticket 40 could include part elements. In such case, one of the submenus for the main menu items would include a function for adding parts records to the job ticket 40, such as the parts 48, 50 discussed above with respect to the job ticket 40 embodiment of FIG. 2. Alternatively, a submenu may include a function for grouping items into a named part. Associated with each part record 48, 50 would be print attribute pages 70a, b, c, d, ewhich would include fields for the user to enter print attribute information for the part records 48, 50. As discussed, any print attribute information entered for the part records would apply to any item records grouped in the part record.

[0080] FIG. 11 is a flowchart that illustrates the general logic of the InfoPrint Submit software 10 according to the present invention. The InfoPrint Submit software 10 is event or message drive software, wherein operations are performed when transitions are made, based upon the receipt of messages or events, from present or current states to new states.

[0081] The general logic 100 begins by waiting at block 102 for an event (e.g., a mouse button click). It should be appreciated that during this time, other operating system tasks, e.g., file, memory, and video tasks, etc., may also be carried out. When an event occurs, control passes to block 104 to identify the event. Based upon the event, as well as the current state of the client computer 4a, b, cdetermined in block 106, a new state is determined in block 108. In block 110, the routine 60 transitions to the new state and performs any actions required for the transition. In block 112, the current state is set to the previously determined new state, and control returns to block 102 to wait for more input events.

[0082] The specific operations that are performed by block 100 when transitioning between states will vary depending upon the current state and the event. The various operations required to implement and maintain the present invention represent particular events handled by routine 100. However, it should be appreciated that these operations represent merely a subset of all of the events handled by any applications program or operating system.

[0083] FIG. 12 is a flowchart that illustrates more specific logic performed by the InfoPrint Submit software 10 when the GUI 60 is displayed as indicated at 114. The logic begins by waiting at block 116 for an event (e.g., a mouse button click signifying selection of a menu item). When an event occurs, control passes to blocks 118-139 to identify the events and perform associated functions.

[0084] Block 118 is a decision block that represents the client computer 4a, b, cdetermining whether a main menu item displayed on a main menu item bar 62 (FIG. 3) was selected and SingleClicked. If so, control transfers to Block 129; otherwise control transfers to block 122. Block 120 represents the client computer 4a, b, cdisplaying in the GUI 60 a submenu for the selected main menu item. From block 120, control transfers to block 124, which is a decision block that represents the client computer 4a, b, cdetermining whether a displayed function within the submenu was selected. If so, control transfers to block 126; otherwise control transfers to block 128. Block 126 represents the client computer 4a, b, cperforming the selected submenu function. After performing the selected submenu function, control transfers to block 130, which represents the client computer 4a, b, cremoving the display of the submenu. Block 128 is a decision block that represents the client computer 4a, b, cdetermining whether the user SingleClicked on an area of the GUI 60 outside of the displayed submenu. If so, control transfers to block 130, which represents the client computer 4a, b, cremoving the display of the submenu; otherwise control transfers back to block 116.

[0085] Block 122 is a decision block that represents the client computer 4a, b, cdetermining whether an element (document, part or item) displayed in a tree section 66 of the GUI 60 (FIG. 3) is selected with a SingleClick. If so, control transfers to block 132; otherwise control transfers to block 139. Block 132 represents the client computer 4a, b, chighlighting the selected element to indicate its selection. From block 132, control transfers to block 134, which represents the client computer 4a, b, cdisplaying print attribute page tabs 68a, b, c, d, e(FIG. 3) associated with the element highlighted at block 132. From block 134, control transfers to block 136, which is a decision block that represents the client computer 4a, b, cdetermining whether a print attribute page tab 68a, b, c, d, ewas selected. If so, control transfers to block 138; otherwise control transfers back to block 116. Block 138 represents the client 4a, b, cdisplaying a print attribute page for the selected print attribute page tab 68a, b, c, d, e, which in the case of FIG. 3 is the Advanced print attribute page 70e. Block 139 represents the client computer 4a, b, cperforming other processing.

[0086] The various functions associated with a SingleClick event are determined by the current state of the InfoPrint Submit software 10. In many instances, the current state is represented visually on the monitor connected to the client computer 4a, b, c.

[0087] It should be appreciated that there are a large number of states, events and operations that are associated with the InfoPrint Submit software 10. Generally, these various operations performed by the InfoPrint Submit software 10 can be classified within certain categories:

[0088] while in any mode, selecting a main menu item from the main menu item bar 62 to display a submenu of functions;

[0089] after selecting an element (document, part or item) within the tree section 66 of the GUI 60, selecting the Item or Edit main menu items to modify or edit the tree structure arrangement of elements;

[0090] after selecting an element within the tree section of the GUI 60, selecting a print attribute page tab 68a, b, c, d, efor the selected element; or

[0091] after selecting a print attribute page tab 70a, b, c, d, e, entering print attribute information on the displayed print attribute page 70a, b, c, d, e.

[0092] In preferred embodiments, the various operations described above are specifically related to the InfoPrint Submit software 10. Of course, those skilled in the art will recognize that the use of the present invention with computer programs may result in different operations (or potentially the same operations).

[0093] Also in the preferred embodiment, the identifier SingleClick is intended to indicate a default single click action, which uses the left mouse button. Other mouse buttons are indicated through the use of appended identifiers, such as (RightMouseButton), etc.

[0094] Of course, those skilled in the art will recognize that the use of any mouse button, keyboard sequence, voice command, or other user input is merely a design choice, and the functions performed by the present invention could be invoked by any number of different combinations of mouse buttons, keyboard sequences, voice command, or any other user input.

[0095] The present invention further includes a method, apparatus, and article of manufacture for archiving and storing files in a library. As discussed with respect to FIG. 1, the network printing system 2 includes an InfoPrint library 36 stored in a server 34. FIG. 13 is a block diagram showing in greater detail the components of the InfoPrint library 36 for storing shared network files and the client computers 4a, b, c.

[0096] FIG. 13 shows the arrangement of software programs in the client computers 4a, b. This software arrangement would also apply to client computer 4cand any other client computers attached to the network printing system 2. Installed on the client computers 4a, bis a database program, which in the preferred embodiment is the IBM Database2 Client Application Enabler (DB2/CAE) 150 product, a Microsoft Foundation Class Library (MFC) 152, a library dynamic link library DLL 154, and the InfoPrint Submit software 10.

[0097] The InfoPrint library 36 is a complete document storage system that archives printing files, application source data, fonts, images, TIFF data, etc. The InfoPrint library 36 is installed in the library server 34. The library server 34 includes hierarchical storage management software, which in the preferred embodiment of FIG. 13 is the IBM ADSTAR Distributed Storage Manager (ADSM) 156, and database software, which in the preferred embodiment is the IBM DB2/6000 (DB2/6000 database) 158 database product. In preferred embodiments, the hardware platform for the library server 34 is comprised of the IBM RISC System/6000 that executes under the AIX operating system. A backup device 160 provides supplemental storage capacity for the InfoPrint library 36. The backup device 160 may be an optical, magnetic or tape storage medium, or any other non-volatile storage medium known in the art for storing large amounts of data.

[0098] In FIG. 1, the library server 34 is illustrated as located external to the InfoPrint MPC server 6. However, in alternative embodiments, the InfoPrint MPC server 6 could function as the library server 34. Moreover, those skilled in the art will appreciate that the preferred embodiment of the library server 34, database program, hierarchical storage management program, etc., could be substituted with other similar hardware and software products known in the art that perform the functions of the software in the preferred embodiment. For instance, the library server 34, client computer 4a, b, c, and InfoPrint MPC server 6 could be implemented in a personal computer, workstation, mainframe, etc., and the operating system could comprise OS/2, WINDOWS, UNIX, OS/ 390, MVS, VM, etc.

[0099] In the client computers 4a, b, the DB2/CAE program 150 enables the client computer 4a, bto access the DB2/6000 database 158. The DB2/CAE program 150 provides Open DataBase Connectivity (ODBC) drivers to interface with the operating system on the client computers 4a, b. On top of the DB2/CAE program 150 is the MFC library 152 which provides object classes to interface the DB2/CAE program 150 with the WINDOWS user interface and the GUI 60 for the InfoPrint Submit software 10 installed in the client computer 4a, b. The DB2/6000 database 158 maintains indexes for all files that are maintained in the InfoPrint library 36, including job tickets and print image files. Through the GUI 60 in the InfoPrint Submit software 10, which interfaces with the DB2/CAE program 150, the user could search the DB2/6000 database 158 and database indexes included therein to access job tickets and print image files in the InfoPrint library 36.

[0100] The InfoPrint Submit software 10 accesses files in the InfoPrint library 36 by invoking the library DLL 154. The library DLL 154 provides an interface between the InfoPrint Submit software 10 and the InfoPrint library 34. The library DLL 154 may be included in the InfoPrint Submit software 10.

[0101] In the library server 34, ADSM 156 controls the migration of files from the InfoPrint library 36 to the backup device 160. In preferred embodiments, the ADSM 156 migrates files from the InfoPrint library 36 to the backup device 160 when space usage in the InfoPrint library 36 reaches a predetermined high threshold level. Migration ceases when space usage in the InfoPrint library 36 reaches a low threshold level. ADSM determines which files to migrate to the backup device 160 based on parameters such as file size, date, last accessed. Typically, the older and larger files are subject to migration to the backup device 160. In the InfoPrint library 36, ADSM 156 replaces migrated files with a stub file. The stub file is a small file that contains all of the information needed to locate and recall a file in the backup device 160. A reference to the stub file operates as a reference to the migrated file itself. Thus, when the job ticket references the stub file, all information the job ticket needs to locate and recall the file is provided by the stub file.

[0102] When a stub file is accessed, the operating system of the library server 34 alerts ADSM 156 and ADSM 156, in response thereto, replaces the stub file in the InfoPrint library 36 with the file in the backup device 160 represented by the stub file. The client computer 4a, bcan access the file after it is transferred from the backup device 160 to the InfoPrint library 36. In most cases of initial file access, the user or job ticket only needs reference information on the file, such as location and size, and does not need to immediately access the contents of the file. The file itself is not likely needed until the print job is submitted to the printer. Therefore, by the time the actual file is needed to process the print job, the ADSM 156 will have already transferred the file from the backup device 160 to the InfoPrint library 36.

[0103] To store job tickets and the associated files in the InfoPrint library 36, the user would select the Archive function displayed in the Ticket submenu 80 (FIG. 8). During archiving, the information in the job ticket is stored in a database index which is maintained in the DB2/6000 database 158. The job ticket file and all related files referenced in the database index are stored in the InfoPrint library 36. Still further, the job ticket and all related files may be stored in a subdirectory in the InfoPrint library 36 using the Package function in the Ticket submenu 80. The use of the Package function to store a job ticket and related files in a single location is discussed in Application Ser. No. 08/932,065, filed on same date herewith, by Leonard Corning Lahey, Deborah Elisabeth Neuhard, and Dwight Ross Palmer, entitled “A Method For Organizing Files Associated With A Job Ticket In A Network Printing System”, which was incorporated herein by reference above.

[0104] FIG. 14 is a flowchart illustrating a preferred embodiment of logic to manage job tickets and related files in the InfoPrint library 36. Block 164 represents the client computer 4a, bor library server 34 waiting for an event. Block 166 is a decision block representing the client computer 4a, bdetermining whether the user requested to archive a job ticket with the GUI. If so control transfers to block 168; otherwise 170. Block 168 represents the client computer 4a, bgenerating a database index describing the parameters of the job ticket and the files referenced therein for storage in the DB2/6000 database 158. Control then transfers to block 172 which represents the client computer 4a, btransferring the job ticket and related files to the InfoPrint library 36 for storage in a subdirectory therein.

[0105] Block 170 is a decision block representing the client computer 4a, bdetermining whether the user has opened a job ticket referencing files stored in the InfoPrint library 36. If so control transfers to block 172; otherwise 176. Block 172 is a decision block representing the client computer 4a, baccessing the files referenced in the job ticket that are stored in the InfoPrint library 36. Control then transfers to block 174 which represents the library server 34 determining if the accessed file is a stub file. If so, control transfers to block 178; otherwise back to block 164. Block 178 represents the client computer 4a, baccessing file information from the stub file, such as file name, location, and size. Control transfers to block 180 which represents the ADSM 156 recalling the file in the backup device 160 represented by the stub file and replacing the stub file in the InfoPrint library 36 with the file recalled from the backup device 160. Block 176 is a decision block representing the client computer 4a, bdetermining whether the user has accessed or referenced a file stored in the InfoPrint library 36. If so, control transfers back to block 172; otherwise block to 182.

[0106] Block 182 is a decision block representing the ADSM 156 determining whether the space usage in the InfoPrint library 36 has reached a predetermined high threshold level. If so, control transfers to block 184; otherwise back to block 164. Block 184 represents the ADSM 156 migrating files from the InfoPrint library 36 to the backup device 160 until space usage in the InfoPrint library 36 reaches a low level threshold. Control then proceeds to block 186 which represents the ADSM 156 creating a stub file and storing the stub file in the location in the InfoPrint library 36 where the migrated file was previously stored. From block 186, control transfers back to block 164.

[0107] In this way, the present invention provides an InfoPrint library 36 of ostensibly unlimited size because the backup device 160 provides practically unlimited supplemental storage for the InfoPrint library 36. Still further, the user is never aware of the transfer of files between the InfoPrint library 36 and the backup device 160 because the ADSM 156 handles such tasks in the background of InfoPrint Submit software 10 operations and without the need for user intervention. Still further, the migration of files between the InfoPrint library 36 and the backup device 160 does not affect the performance of InfoPrint Submit software 10 and job ticket operations. Performance is not adversely affected because when the client computer 4a, binitially accesses a file in the InfoPrint library 36 which has been migrated to the backup device 160, the client computer 4a, bobtains all the information it initially needs on the file from the stub file to continue processing. By the time the client computer 4a, bneeds to access the contents of the file, the present invention will have recalled the file from the backup device 160 to the location in the InfoPrint library 36 where the stub file was located.

[0108] The present invention further includes a method, apparatus and article of manufacture for customizing a dialog box that is used to search for job tickets and files in the InfoPrint library 36. To search the InfoPrint library 36 for job tickets, the user would select the Retrieve function from the Ticket submenu 80 (FIG. 8). FIG. 15 illustrates a job ticket search dialog box 190 displayed in the GUI 60 when the user selects the Retrieve function. The job ticket search dialog box 190 displays a column 194 of search fields such as Customer, Job ID, Keys, File name, etc. A search operator column 196 provides a field for each search field in which the user may select a search operator such as equal, like, greater than, etc, using drop down menu 192. A search value column 198 provides a field in which the user enters the value which is searched for in the search fields.

[0109] After the user enters search operators and values, the user can invoke the search by selecting the Search button displayed in the job ticket search dialog box 190. Selection of the Search button causes the client computer 4a, b, c, operating under control of the DB2/CAE 150, to search indexes in the DB2/6000 database 158 based on the search operators and values the user entered in the dialog box 190. The job tickets located in the DB2/6000 database 158 that match the search criteria and search values are listed in a search result window 200 labeled “Items Matching Search Criteria.” The user would open one of the job tickets listed in the search result window 200 into the GUI 60 shown in FIGS. 3-10 by highlighting a job ticket in the search result window 200 with the input device 12a, b, cand then selecting the Retrieve button in the dialog box 190.

[0110] When the GUI 60 shown in FIG. 10 is displayed, the user would select the Insert Library file function from the Item submenu (Table 1) to add a files stored in the InfoPrint library 36 into one of the documents in the job ticket, as displayed in the tree section 66. FIG. 16 illustrates a file search dialog box 202 invoked when the user selects the Insert Library file function. The file search dialog box 202 is very similar to the job ticket dialog box 190 in FIG. 15. The file search dialog box 200 has different search fields 194, reflecting the different information included in an index of the print files as opposed to a job ticket, such as a File Type, Document, and Item fields. When the user initiates a search from the file search dialog box 202, the client computer 4a, b, c, operating under control of the DB2/CAE 150, would search the database indexes in the DB2/6000 database 158 for all files matching the entered search operators and values. The files resulting from the search are displayed in a search result window 204.

[0111] The user may customize the search dialog boxes 190, 202 with the default option and a customization dialog box 210 shown in FIG. 17. By selecting the Set Default button in the dialog box 190, 202, the user saves the present search operators and values entered for subsequent searches. When the search dialog box 190, 202 is later invoked, those default search operators and values appear. The user may further customize and modify the dialog boxes 190, 202 in real time with the customization dialog box 210 (FIG. 17) invoked when the user selects the Customize button in dialog boxes 190, 202. The Customization dialog box 210 is used to modify search fields in the dialog boxes 190, 202. The customization dialog box displayed for the job ticket search dialog box 190 would have the same customization options but include different search fields than the search fields for the job ticket.

[0112] In the customization dialog box 210, a first column 212 lists the search fields included in the dialog box 190, 202. Columns 214, 216, 218, 220 present the customize options for the search fields. The second column 214 labeled “Column Alias” includes fields in which the use enters a new name of the search field displayed in the dialog boxes 190, 202. The third column 216 labeled “Order” allows the user to specify the order in which the search fields appear in the dialog boxes 190, 202. The fourth column 218 labeled “Hide” 214 allows the user to inhibit the display in the dialog box 190, 202 of a selected search field and its corresponding search operator and value. The fifth column 220 labeled “Read Only” allows the user to render the search field read only. In read only mode, the search operator and value currently entered for a field are displayed but cannot be modified from the dialog boxes 190, 202. The user would select the OK button to immediately apply the settings entered in the customize dialog box 210 to the dialog boxes 190, 202. The customization settings would immediately apply to any search operator and value information the user had previously entered into the dialog box 190, 202. The customized settings entered with the customize dialog box 210 are stored and apply to later instances in which the user invokes the customize dialog box 210. Moreover, in networked systems with multiple users, the customized settings the user creates with the default option and the customized dialog box 210 would be saved on a per user basis in the system. Thus, when a user logs on to the system, the user's customized dialog boxes 190, 202 would be displayed. In this way, each user can continue using individualized dialog boxes 190, 202 independently of what other users in the system are using.

[0113] Those skilled in the art of computer user interface design will appreciate that certain commands implemented as buttons displayed in the dialog boxes 190, 202, 210, such as the buttons which are used to invoke the customize dialog box 210, invoke a search from the dialog boxes 190, 202, and redraw the dialog box 190, 202 from the customize dialog box 210, could be invoked by other input means known in the art, e.g., a command directly entered by selecting a pattern of keys from a keyboard, a voice entered command, etc. Moreover, the above commands could be invoked from buttons displayed outside of the dialog boxes 190, 202, 210.

[0114] FIG. 18 is a flowchart showing a preferred embodiment of logic for implementing certain operations in the file search dialog box 202. The logic for the corresponding operations in the job ticket search dialog box 190 is very similar to the logic illustrated in FIG. 18. However, certain steps would differ. For instance, the search fields displayed in the dialog boxes 190, 202 differ. Further, the Retrieve button causes different results in the dialog boxes 190, 202. When Library files are retrieved, information on the file is inserted in the current open job ticket to include the file in the job ticket. Whereas when a job ticket is retrieved, the retrieved job ticket is opened into the GUI 60. Otherwise, the logic steps of FIG. 18 would apply to the operations of the job ticket search dialog box 190.

[0115] The logic illustrated in FIG. 18 is implemented in the InfoPrint Submit software 10 installed in the client computers 4a, b, c. Step 230 represents the client computer 4a, b, cwaiting for the user to SingleClick the Retrieve function. Control transfers to block 232 which represents the client computer 4a, b, cdisplaying the file search dialog box 202. Control then transfers to block 234 which is a decision block representing the client computer 4a, b, cdetermining whether the user has SingleClicked the Search button in the dialog box 202. If so, control transfers to block 236; otherwise block 238. Block 236 represents the client computer 4a, b, c, operating under control of the DB2/CAE 150, searching the indexes in the DB2/6000 database 158 using the search operators and search values entered in the file search dialog box 202. Control transfers to block 240 which represents the client computer 4a, b, cdisplaying the search results in the search result window 204 and then to block 242 which represents the client computer 4a, b, cenabling the Retrieve button in the dialog box 202.

[0116] Block 238 represents the client computer 4a, b, cdetermining if the user SingleClicked the Retrieve button. The Retrieve button can only be selected if it was enabled at step 242 following a search. If the Retrieve button was selected, control transfers to block 244; otherwise block 246. Block 244 represents the client computer 4a, b, caccessing file information from the InfoPrint Library 36 on the retrieved library file to include in the job ticket presently opened in the GUI 60. Control then transfers to block 248, which is a decision block representing the library server 34 determining whether a stub file was opened when the client computer 4a, b, cobtained information on the retrieved file. If so, control transfers to block 250, otherwise block 252. Block 250 represents the ADSM 156 moving the retrieved file from the backup device 160 to the InfoPrint library 36 to replace the stub file. Control then transfers to block 252. Block 252 represents the client computer 4a, b, cclearing the file search dialog box 202 from the monitor 14a, b, c. From block 252, control transfers back to block 230.

[0117] Block 246 is decision block representing the client computer 4a, b, cdetermining whether the user has SingleClicked the Customize button in the dialog box 202. If so control transfers to block 254; otherwise block 256. Block 254 represents the client computer 4a, b, cdisplaying the customize dialog box 210 (FIG. 17). Control transfers to decision block 258 representing the client computer 4a, b, cdetermining whether the user has SingleClicked the OK button in the customize dialog box 210. If so, control transfers to block 260; otherwise block 262. Block 260 represents the client computer 4a, b, credrawing the file search dialog box 202 in accordance with the customize information the user entered in the columns 214, 216, 218, 220 of the customize dialog box 210. From there, control proceeds to block 264 which represents the client computer 4a, b, cclearing the customize dialog box 210. From block 264, control transfers back to block 234. Block 262 is a decision block representing the client computer 4a, b, cdetermining whether the user SingleClicked the Cancel button. If so control transfers to block 264; otherwise back to block 258.

[0118] This concludes the description of the preferred embodiments of the invention. The following describes some alternative embodiments for accomplishing the present invention.

[0119] For example, the client computer 4a, b, cand InfoPrint MPC server 6 may be any type of computer, such as a mainframe, minicomputer, work station, personal computer or combinations thereof operating under any suitable operating system. In addition, the client computer 4a, b, cmay include any software program, application or operating system having a graphical user interface and performing the operations of the present invention. Still further, some or all of the functions described above as being performed by the client computer 4a, b, ccould, in alternative embodiments, be performed by the InfoPrint MPC server 6, and vice versa.

[0120] Those skilled in the art will also recognize that the GUI and data structure may be modified to accommodate different types of print attributes other than those described above. Still further, the GUI may have a different appearance, layout and design then the GUI described above.

[0121] Still further, those skilled in the art will recognize that in the flowcharts set forth in FIGS. 11, 12, 14, and 18, programming steps may be added, modified, deleted or performed in an order different than the order set forth in the preferred embodiments.

[0122] In summary, the present invention discloses a method, apparatus, and article of manufacture for managing print files associated with a job ticket describing a plurality of print files included in a print job. The print files include data representing graphical images. A first storage device stores print files. When space usage in the first storage device has exceeded a predetermined limit, print files from the first storage device are migrated to a second storage device. A stub file is generated that includes information on a migrated file. The stub file is stored where the migrated print file was located in the first storage device. A print file is selected to include in the print job described in the job ticket. Upon selection of a print file represented by a stub file stored in the first storage device, the stub file is accessed. When the stub file is accessed, the stub file is replaced with the selected print file from the second storage device. The selected print file is transmitted from the first storage device to a printer when the print job including the selected print file is submitted to a printer.

[0123] The foregoing description of the preferred embodiment of the invention has been presented for the purposes of illustration and description. It is not intended to be exhaustive or to limit the invention to the precise form disclosed. Many modifications and variations are possible in light of the above teaching. It is intended that the scope of the invention be limited not by this detailed description, but rather by the claims appended hereto. The above specification, examples and data provide a complete description of the manufacture and use of the composition of the invention. Since many embodiments of the invention can be made without departing from the spirit and scope of the invention, the invention resides in the claims hereinafter appended.