JP3823534B2 - Printing system - Google Patents

Description

[0001]
BACKGROUND OF THE INVENTION
The present invention relates to a printing system, and is particularly suitable for application to a client-server printing system.
[0002]
[Prior art]
In recent years, the use of Microsoft Windows as a computer operating system for office work and mission-critical work has been remarkable.
[0003]
However, when Windows is used as the operating system, since Windows is a personal-oriented operating system, there is a point unsuitable for mass printing in core business. For example, in Windows, it is not possible to simultaneously print on a plurality of printers with a single printing action. For this reason, when distributing materials, it takes time to repeatedly start printing, manually sort the printed matter, and distribute it by mail or the like.
[0004]
In addition, due to the recent spread of mail, small and fixed documents created by word processors can be replaced by mail. However, printing of management forms such as aggregated data by application operation and printing of a large number of documents, etc. Cannot be replaced by mail. Furthermore, when a large amount of printing is performed, it is impossible to perform printing distributed to a plurality of printers, and it is necessary to repeatedly specify a start page, an end page, and an output destination printer for each printer.
[0005]
Conventionally, in order to solve these problems, a dedicated API (application interface function) for printing a basic business form is prepared, and the API is used to make up for deficiencies in print control of an operating system such as Windows. was there.
[0006]
FIG. 12 is a block diagram for explaining a conventional distributed printing method. In FIG. 12, the application 201 calls the API 203 as a dedicated print control function. Here, the API 203 is provided with an interface that can receive a plurality of sets of printer names, start pages, and end pages. By providing this interface in the API 203, distributed printing is possible. When the API 203 receives a plurality of sets of the printer name, start page, and end page as the parameter 202 and also receives drawing data from the application 201, the received parameter 202 and drawing data are passed through the operating system 204 and the file driver 205. And stored in the spool file 206.
[0007]
On the other hand, the spool writer 207 polls a predetermined directory (spool directory). When the spool writer 207 detects a completed spool file 206, the spool writer 207 starts reading the spool file 206 and stores the parameter 202 stored in the spool file 206. Take out. In addition, the drawing data of each page is sequentially read from the spool file 206, and the GDI 208 is called to cause the designated printers 211a and 211b to print the designated page according to the information of the parameter 202. The GDI 208 is a function group for drawing a graphical device that is closely connected to the operating system 204.
[0008]
For example, in order to equally distribute and print 100 pages of print data stored in the spool file 206 to the two printers 211a and 211b, the printer name of the printer 211a, start page = 1, end page = 50, Assume that the printer name of the printer 211b, start page = 51, and end page = 100 are given as parameters 202. In this case, since the GDI 208 handles rendering in units of printers, the spool writer 207 first designates the printer 211a and calls the GDI 208. Then, the print data from page 1 to page 50 is output to the spool queue dedicated to the printer 211a, and a spool file 209a is generated. Next, the spool writer 207 designates the printer 211b and calls the GDI 208. Then, print data from page 51 to page 100 is output to a spool queue dedicated to the printer 211b, and a spool file 209b is generated.
[0009]
When the spool files 209a and 209b are generated, they are converted into physical command codes of the printers 211a and 211b by the printer drivers 210a and 210b dedicated to the printers 211a and 211b, and then output to the printers 211a and 211b for printing. Is done.
[0010]
[Problems to be solved by the invention]
However, the conventional method of providing the API 203 can be applied only to the dedicated application 221 that can call the API 203. For this reason, there is a problem that it cannot be applied to a general-purpose package application such as a word processor that does not have a function of calling the API 203. There is also a problem that the printing application 201 must be constructed using the provided API 203.
[0011]
When a document requested to be printed from one application 201 is simultaneously distributed to a plurality of printers 211a and 211b and printing is performed, a queue (hereinafter referred to as a printer) in which drawing data is sorted for each printer 211a and 211b. In this case, the drawing data is stored in the printer queue in units of pages. For this reason, in order to change the distribution of pages to be printed to the printers 211a and 211b after they are stored in the printer queue, it is necessary to read the drawing data from the spool file 206 and store the drawing data again for each printer queue. There is a problem that it becomes very difficult to change the distribution of pages to be printed.
[0012]
In addition, after the drawing data output by the application 201 is stored in the spool file 206, the drawing data stored in the spool file 206 is re-stored in the spool files 209a and 209b separate from the spool file 206. There was also a problem that the spool processing took time.
[0013]
In addition, in the method of providing the conventional API 203, printing is performed in units of documents output by one application 201. Therefore, one document document (hereinafter referred to as a virtual document) is configured by documents output by a plurality of applications. In this case, it is necessary to start a plurality of applications 201 and specify a start page and an end page to perform a printing operation, which causes a problem that the operation becomes complicated.
[0014]
SUMMARY OF THE INVENTION Accordingly, a first object of the present invention is to provide a printing system capable of efficiently performing print data spool processing.
A second object of the present invention is to provide a printing system that can handle documents output by a plurality of applications in a unified manner.
[0015]
[Means for Solving the Problems]
In order to solve the above-described problem, according to the present invention, a drawing data storage unit that stores drawing data, an output request storage unit that stores an output request for the drawing data for each output destination of the drawing data, Drawing data transfer means for transferring the drawing data from the drawing data storage means to the output destination based on the drawing data output request.
[0016]
This allows the drawing data stored in the drawing data storage means to be read directly from the drawing data storage means without re-storing the drawing data corresponding to the output destination of the drawing data, and stored again. It is possible to transfer to the output destination, and when drawing data is transferred to the output destination, it is possible to omit the process of re-storing the drawing data for each output destination, thereby speeding up the spool processing. It becomes possible.
[0017]
According to another aspect of the invention, the output request includes identification information for identifying the drawing data and page information for designating a print page of the drawing data.
As a result, when changing the print page of the drawing data to be output, it is only necessary to change the page information stored in the output request storage means, and there is no need to re-store the drawing data corresponding to the change of the print page. Therefore, spool processing can be performed efficiently.
[0018]
According to another aspect of the present invention, a virtual document is generated based on drawing data storage means for storing drawing data created by a plurality of applications, and drawing data created by the plurality of applications. Virtual document generation means, output request storage means for storing the virtual document output request for each output destination of the virtual document, and the virtual document output request based on the virtual document output request. Drawing data transfer means for transferring drawing data included in the document from the drawing data storage means to the output destination;
[0019]
This makes it possible to integrate drawing data created by multiple applications and handle the integrated drawing data in an integrated manner, without having to repeatedly specify the printing for each application. Since it is possible to print drawing data created by a plurality of applications with only one print designation for a virtual document, it is possible to efficiently perform print processing that handles a plurality of applications. It becomes possible.
[0020]
Also, drawing data contained in a virtual document can be stored as drawing data based on a virtual document output request without configuring the drawing data of the virtual document corresponding to the output destination of the drawing data. It is possible to sequentially read out from the means and transfer it to the output destination, and omit the process of storing the drawing data for each virtual document when transferring the drawing data of the virtual document to the output destination. Therefore, it is possible to speed up spool processing that handles a plurality of applications.
[0021]
DETAILED DESCRIPTION OF THE INVENTION
Hereinafter, a printing system according to an embodiment of the present invention will be described with reference to the drawings. In the following embodiments, an output device operation support (hereinafter referred to as CAPCAL) control method under an operating system by Windows will be described.
[0022]
FIG. 1 is a block diagram showing the configuration of a printing system according to an embodiment of the present invention. In FIG. 1, a client 100 and a server 103 are connected via communication networks 101 and 102, and the server 103 is connected to a printer 9. Here, the communication network 102 is, for example, a LAN (local area network), and the communication network 101 is, for example, a LAN, a WAN (wide area network), or the Internet. The client 100 is provided with an application 1, GDI 2, Windows print control unit 3 and client control unit 4, and the server 103 is provided with a Windows print control unit 5, server control unit 6, GDI 7 and printer output control unit 8. ing. Here, GDI 2 and 7 are interfaces (APIs) used when a Windows program performs screen display or printing to the printer 9.
[0023]
When performing printing processing using Windows, processing by the Windows print control units 3 and 5 is performed, and print data generated on the client 100 side is sent to the server side via the communication line 102. On the other hand, when CAPCAL control is performed, processing by the client control unit 4 and the server control unit 6 is performed, and print data generated on the client 100 side is sent to the server side via the communication line 101. When selecting CAPCAL control, the CAPCAL driver provided for CAPCAL control is designated by the application 1 to call GDI2.
[0024]
FIG. 2 is a block diagram illustrating the configuration of the client control unit 4 of FIG. 2, the client control unit 4 includes a CAPCAL driver 14, a CAPCAL driver property control thread 15, an output control information file 17, a job description file 18, EMF files 19, 24, a CAPCAL client definition file 20, a CAPCAL print processor 21, A CAPCAL job description file 23, a CAPCAL transfer destination definition file 25, a CAPCAL client main process 26, and a CAPCAL job transfer thread 27 are provided. The Windows print control unit 3 is provided with a spooler process 11, a local print provider 12, and a print processor 13. Here, the client control unit 4 controls the processing until the print data drawn by the application 1 running on the Windows operating system is loaded into the CAPCAL processing environment and transferred to the server 103.
[0025]
When processing the print data drawn by the application 1 in the CAPCAL environment, the application 1 designates the CAPCAL driver 14 provided as a virtual driver and calls GDI2. Note that the CAPCAL driver 14 is a virtual device provided separately from the driver corresponding to the actual printer, and is independent of the Windows printer driver.
[0026]
When GDI2 is called, the drawing function is acquired from the CAPCAL driver 14, the drawing primitive requested by the application 1 is converted into the drawing function of the CAPCAL driver 14, and spooled in the system spool queue 16. In the system spool queue 16, a job description file 18 that stores the name of a user who requested printing, an application name, and the like, and an EMF file 19 that stores drawing information in a formatted format are created. EMF is an abbreviation for Enhanced Meta-File, and is a logical storage format of drawing data in Windows. Note that the formats of the job description file 18 and the EMF file 19 are completely the same as the standard Windows format. For this reason, the job description file 18 and the EMF file 19 can be generated by a default function provided in Windows.
[0027]
Further, the CAPCAL driver 14 writes CAPCAL-specific output control information in the system spool queue 16 as an output control information file 17. This output control information can be set by opening a dialog screen from the CAPCAL driver 14 side and causing the operator to specify printing conditions such as distribution and distribution.
[0028]
When the spooling of all drawing data of the application 1 is completed, the CAPCAL print processor 21 is called. The CAPCAL print processor 21 is called by designating the CAPCAL driver 14 in the application 1. Note that when another driver is designated by the application 1, the print processor 13 provided in Windows is called, and printing processing by Windows can be performed.
[0029]
The CAPCAL print processor 21 takes in the contents of the job description file 18 and the output control information file 17 from the system spool queue 16 and writes them in the CAPCAL spool queue 22 as a CAPCAL job description file 23. Here, the default value of the output control information is defined in the CAPCAL client definition file 20. If the output control information is not stored in the output control information file 17, the output control information is obtained from the CAPCAL client definition file 20. take in.
[0030]
The CAPCAL print processor 21 writes the EMF file 19 in the system spool queue 16 into the EMF file 24 in the CAPCAL spool queue 22 as it is. When the CAPCAL job description file 23 and the EMF file 24 are written to the CAPCAL spool queue 22, the CAPCAL print processor 21 notifies the CAPCAL job transfer thread 27 of this fact.
[0031]
The CAPCAL job transfer thread 27 transfers the contents of the CAPCAL job description file 23 and the EMF file 24 to the server 103 based on a predefined transfer means. The transfer means and the server name of the transfer destination are stored in the CAPCAL transfer destination definition file 25, and the CAPCAL job transfer thread 27 specifies the transfer means and the transfer destination server 103 according to the contents of the CAPCAL transfer destination definition file 25. decide. As a transfer means, a communication network 28 using a file transfer protocol (ftp) or a communication network 29 using a mail attachment file can be used. Also, transfer means other than these may be used.
[0032]
As described above, the CAPCAL driver 14 as a virtual driver is provided in the client control unit 4, and the output information control file 17 is spooled in the system spool queue 16 by the CAPCAL driver 14. The CAPCAL driver 14 is provided virtually, and does not depend on a specific printer model or manufacturer. Therefore, the CAPCAL driver 14 has functions that cannot be realized by the printing function provided in advance in Windows on the CAPCAL driver 14. It is possible to construct it independently, and it is possible to easily realize document distribution processing, distributed printing processing, distribution destination automatic detection processing, printer error and print completion notification processing, and the like.
[0033]
In addition, the job description file 18 and the EMF file 19 are spooled in the system spool queue 16 by using the GDI2 on Windows, so that the format of the job description file 18 and the EMF file 19 matches the format of the Windows standard. For all applications that run on Windows including general-purpose package software without changing any Windows application interface, document distribution processing, distributed printing processing, distribution destination automatic detection processing, printer errors, and print completion Notification processing and the like can be easily realized.
[0034]
FIG. 3 is a block diagram illustrating the configuration of the server control unit 6 of FIG. In FIG. 3, the server control unit 6 includes a mail CAPCAL reception thread 30, an ftp CAPCAL reception thread 31, a CAPCAL server main process 32, a CAPCAL job description file 34, an EMF file 35, a job control file 36, and distribution distribution. A processing thread 37, an output control file 39, a CAPCAL server-side definition file 40, output threads for printers 41 and 42, and a CAPCAL job transfer thread 43 are provided.
[0035]
When the CAPCAL reception threads 30 and 31 are activated by the CAPCAL server main process 32, the CAPCAL reception threads 30 and 31 receive the CAPCAL job description file 23 and the EMF file 24 transmitted from the CAPCAL job transfer thread 27. Then, the contents of the received CAPCAL job description file 23 and EMF file 24 are written into the CAPCAL job description file 34 and EMF file 35 of the CAPCAL spool document queue 33. Here, the CAPCAL reception threads 30 and 31 perform management so that file names (job IDs) do not overlap. When the writing to the CAPCAL spool document queue 33 is completed, the CAPCAL server main process 32 starts the distribution distribution processing thread 37 and notifies the distribution distribution processing thread 37 of the completion of writing to the CAPCAL spool document queue 33.
[0036]
The distribution distribution processing thread 37 takes in output control information from the CAPCAL job description file 34. The contents of the CAPCAL server-side definition file 40 are read in advance. The distribution distribution processing thread 37 detects the output printer and the start and end pages to be output from the output control information and the contents of the server-side definition file 40, and generates a job control file 36. The job control file 36 stores a printer name and a CAPCAL print job ID. Here, the CAPCAL print job ID is an ID uniquely given to each CAPCAL spool print queue 38. Further, when the distribution distribution processing thread 37 detects the output printer and the start page and the end page to be output, it sends a print request to the CAPCAL spool print queue 38 provided for each output printer 9.
[0037]
The distribution distribution processing thread 37 generates an output control file 39 when a print request is input to the CAPCAL spool print queue 38. The output control file 39 stores a CAPCAL job ID, a start page, an end page, and a Win job ID. Here, the CAPCAL job ID is a management ID uniquely created by the CAPCAL system, and by specifying the CAPCAL job ID, the CAPCAL job description file 34 stored in the CAPCAL spool document queue 33 is specified. The contents and the contents of the EMF file 35 can be specified.
[0038]
The CAPCAL server-side definition file 40 stores the correspondence between the distribution destination name and the printer name (or server name), and the CAPCAL server-side definition file 40 even when the distribution destination is specified by a logical name. The output printer can be determined by referring to FIG. When the input of the print request to the CAPCAL spool print queue 38 is completed, the printer-specific output thread 41 that specializes in the printer 9 that has made the print request is notified.
[0039]
The output thread 41 for each printer refers to the CAPCAL job ID stored in the output control file 39 of the CAPCAL spool print queue 38, so that the CAPCAL job description file 34 and the EMF file 35 stored in the CAPCAL spool document queue 33 are referred to. Is identified. Of the contents of the specified CAPCAL job description file 34 and EMF file 35, the portion from the start page to the end page specified by the output control file 39 is taken out from the CAPCAL spool document queue 33 and GDI 7 is called. The drawing data is passed to the Windows print control 5.
[0040]
When a printer other than the printer 9 managed by the server 103 is designated as an output printer by the output control information and the contents of the CAPCAL server-side definition file 40, the distribution distribution processing thread 37 is a CAPCAL job transfer thread. A print request is sent from the server 43 to the server managing the designated printer via the communication network 44.
[0041]
As described above, the contents of the CAPCAL job description file 34 and the EMF file 35 are not written in the CAPCAL spool print queue 38, but the contents of the CAPCAL job description file 34 and the EMF file 35 stored in the CAPCAL spool document queue 33 are written. Write identifying information. When the printer-specific output threads 41 and 42 send the drawing data to the GDI 7, the drawing data is not taken out from the CAPCAL spool print queue 38, but in accordance with the information specified in the output control file 39. The drawing data is taken out from.
[0042]
This eliminates the need to write drawing data to the CAPCAL spool print queue 38, thereby enabling the spool processing to be speeded up. Further, when changing the print page, it is only necessary to rewrite the print page of the output control file 39, and it is not necessary to rewrite the drawing data to the CAPCAL spool print queue 38. Can be done.
[0043]
FIG. 4 is a block diagram illustrating the configuration of the printer output control unit 8 of FIG. In FIG. 4, the printer output control unit 8 is provided with a Centroport monitor 48 and a printer output management unit 50, and the server control unit 6 is provided with a CAPCAL server main process 32, an EMF file 35, and a printer-specific output thread 41. The Windows print control unit 5 is provided with a Raw spool file 46, a print processor 47 and a spooler process main 49, and the client 100 is provided with a CAPCAL client main process 26.
[0044]
The output thread 41 for each printer retrieves the EMF file 35 from the CAPCAL spool document queue 35 and calls the GDI 7 to send drawing data to the Windows print control unit 5. The GDI 7 communicates with the printer driver 45 for the printer 9 designated for printing, and converts the EMF file 35 into a command (ESC sequence) dedicated to the printer 9 designated for printing. The ESC sequence obtained by the conversion is stored in the Windows system spool queue. This is called the Raw spool file 46. The raw spool file 46 is composed of pure printer commands (ESC sequence) only. The raw spool file 46 is read by the print processor 47 by the Windows spooler process main 49 and sent to the centroport monitor 48 in units of drawing data for one page.
[0045]
When the interface between the printer 9 and the server 100 is a LAN, it is sent to a LAN port monitor, and when it is another interface, a port monitor for that interface is sent. Note that the processing up to this point is the same as the data processing by the Windows print control unit 5.
[0046]
The Centro port monitor 48 outputs the command data of the printer 9 received via the spooler process main 49 to the Centro port. If an error occurs in the printer 9 and command data cannot be output, the centroport monitor 48 notifies the printer output management unit 50 of the printer name, error code, and job ID for identifying the original document. . Also, when an error occurs in the printer connected to the other port monitor 51, the other port monitor 51 notifies the printer output management unit 50 of the printer name, error code, and job ID for identifying the original document. To do. Here, the job ID is an ID for specifying a print job that exists in the Windows print control mechanism, and the printer output management unit 50 notifies the printer output management unit 50 of the job ID so that the original document name, The client host name and user name that requested printing can be acquired.
[0047]
Upon receiving the printer name, error code, and job ID from the Centroport monitor 48, the printer output management unit 50 notifies the CAPCAL server main process 32 of these pieces of information.
[0048]
The CAPCAL server main process 32 detects the name of the client host that issued the print request from the acquired job ID, and notifies the CAPCAL client main process 26 operating on the client host of the document name, user name, and error code. Further, the screen call 52 is performed to display these pieces of information.
[0049]
When the CAPCAL client main process 26 receives a document name, a user name, and an error code from the CAPCAL server main process 32, the CAPCAL client main process 26 displays a user name, a document name being printed, and an error message by performing a screen call 53.
[0050]
The Centroport monitor 48 notifies the printer output management unit 50 of the printer name and job ID when the output of one job is completed. Upon receiving the printer name and job ID from the Centroport monitor 48, the printer output management unit 50 notifies the CAPCAL server main process 32 of these pieces of information.
[0051]
The CAPCAL server main process 32 detects the client host name that issued the print request from the acquired job ID, and notifies the CAPCAL client main process 26 running on the client host of the document name and user name. Further, the screen call 52 is performed to display these pieces of information.
[0052]
When the CAPCAL client main process 26 receives the document name and the user name from the CAPCAL server main process 32, the CAPCAL client main process 26 displays a message indicating that the printing of the document is completed by performing a screen call 53.
[0053]
As described above, the Centroport monitor 48 notifies the printer output management unit 50 of the job ID for identifying the original document, so that the printer output management unit 50 can recognize the name of the client host that requested the printing. Since it is possible to notify the client 100 that has made a print request of a print error or print completion, it is possible to recognize the print status of the document on the client 100 side.
[0054]
Hereinafter, the document management control method according to the first embodiment of the present invention will be described in more detail.
FIG. 5 is a block diagram showing a document management control method according to the first embodiment of the present invention. In FIG. 5, when one application 1 is printed and executed, the CAPCAL job description file 34 and the EMF file 35 pass through the modules of the CAPCAL client control unit 4 and the CAPCAL spool document queue 33 of the CAPCAL server control unit 6. Is generated.
[0055]
Here, the file name formats of the CAPCAL job description file 34 and the EMF file 35 are expressed as follows.
"Nnnnnn.csdh" ... CAPCAL job description file
・ "Nnnnn.cspl" ... EMF file
However, the part “nnnnn” is called a CAPCAL job ID, and is a management ID uniquely created by the CAPCAL system. A CAPCAL job description file 34 and an EMF file 35 having the same CAPCAL job ID constitute one spool job.
[0056]
When the distribution distribution processing thread 37 detects the actual output destination (printer name), output start page, and output end page, it writes the printer name and CAPCAL print job ID into the job control file 36. Here, when printing results are output to a plurality of printers, the printer name and the CAPCAL print job ID for each printer are written in the job control file 36.
[0057]
In addition, CAPCAL spool print queues 39a, 39b,... Corresponding to the number of printers to be output are generated corresponding to the CAPCAL print job ID written in the job control file 36. The distribution distribution processing thread 37 generates output control files 39a, 39b,... Corresponding to the respective CAPCAL spool print queues 38a, 38b,..., And outputs the output control files 39a, 39b,. For CAPCAL job ID, start page, end page, and Win job ID are written.
[0058]
For example, when the output control file 39a is generated, the distribution / distribution processing thread 37 activates the output thread 41 for each printer that handles the printer designated by the job control file 36. The output thread 41 for each printer captures the portion of the contents of the CAPCAL job description file 34 and the EMF file 35 stored in the CAPCAL spool document queue 33 from the start page to the end page specified by the output control file 39a. The data is taken out from the spool document queue 33, GDI7 is called, and drawing data is sent to the Windows print control 5.
[0059]
When the output control file 39b is generated, the distribution / distribution processing thread 37 activates the output thread 42 for each printer that handles the printer designated by the job control file 36. The output thread 42 for each printer uses the CAPCAL job description file 34 and the EMF file 35 stored in the CAPCAL spool document queue 33 to capture the portion from the start page to the end page specified by the output control file 39b. The data is taken out from the spool document queue 33, GDI7 is called, and drawing data is sent to the Windows print control 5.
[0060]
FIG. 6A shows an example of the contents of the job control file 36 shown in FIG. 6A, in the job control file 36, printer names and CAPCAL print job IDs for the number of output printers are written. Here, the CAPCAL print job ID is a unique five-digit numeric character string for each CAPCAL spool print queue 38a, 38b,. If this 5-digit numeric character string is one entry and there are a plurality of printers to output, a plurality of entries are written. The file name of the job control file 36 can be “(CAPCAL job ID) .jctI”.
[0061]
FIG. 6B is a diagram showing an example of the contents of the output control file 39a of FIG. In FIG. 6B, the CAPCAL job ID, the start page, the end page, and the Win job ID are written in the output control file 39a. Here, the CAPCAL job ID is an ID for identifying the substance of the spool file on the CAPCAL spool document queue 33. The Win job ID is a management ID for identifying a Windows spool job when the printer-specific output thread 41 outputs drawing data to the GDI 7. The reason why the Win job ID is stored in the output control file 39a is that it is necessary to store the Win job ID in order to delete the Windows spool job when an instruction to cancel printing is given later. The file name of the output control file 39a can be “(CAPCAL print job ID). PctI”. The configuration of the output control file 39b in FIG. 5 is the same.
[0062]
FIG. 7 is a flowchart showing a document management control method according to the first embodiment of the present invention. In FIG. 7, when the distribution distribution processing thread 37 generates the CAPCAL job description file 34 and the EMF file 35 in the CAPCAL spool document queue 33 and detects the actual output destination (printer name), output start page, and output end page, A job control file 36 is generated in the CAPCAL spool document queue 33 (step S1).
[0063]
Next, output control files 39a, 39b,... Are generated in correspondence with the respective CAPCAL spool print queues 38a, 38b,... (Step S2), and printer-specific output threads 41, 42 dedicated to the printer to be used. Is notified by an event (step S3).
[0064]
When notification to the output threads 41 and 42 by printer is performed, the corresponding CAPCAL spool print queues 38a, 38b,... Are read, and the CAPCAL job ID, start page, and the lower output control files 39a, 39b,. The end page is recognized (step S11). Next, the start page read from the output control files 39a, 39b,... Is stored in the variable N (step S12), and the CAPCAL specified by the CAPCAL job ID read from the output control files 39a, 39b,. The Nth page of the EMF file 35 under the spool document queue 33 is read (step S13) and output to the GDI 7. .
[0065]
Next, while increasing the value of the variable N by 1 (step S14), until the value of the variable N exceeds the end page read from the output control files 39a, 39b,... (Step S15), the CAPCAL spool document queue 33. Repeat reading of the Nth page of the lower EMF file 35.
[0066]
When the value of the variable N exceeds the end page read from the output control files 39a, 39b,..., It is determined whether processing for the number of output printers has been performed (step S4), and processing for the number of output printers is performed. Is not completed, the process returns to step S2, and the creation of the output control files 39a, 39b,... And the job input processing of the output threads 41 and 42 for each printer are repeated.
[0067]
As described above, according to the first embodiment of the present invention, the entity of the drawing data, which is the spool file output by the application 1, is uniquely present in the system, and the drawing data is stored in the CAPCAL spool print queues 38a, 38b,. Instead of spooling the entity, a print request file is created in the CAPCAL spool print queue 38a, 38b,... And the page information to be printed by the printer in the EMF file 35 is stored in the print request file. Thus, the spool process can be performed at high speed.
[0068]
In addition, even when the number of pages to be printed on the printer is changed after the print request file is created in the CAPCAL spool print queue 38a, 38b,..., The start in the output control file 39a, 39b,. It is only necessary to rewrite the page and the end page, and it is not necessary to re-spool the print data of the CAPCAL job description file 34 and the EMF file 35, so that the number of pages to be printed on the printer can be easily changed. Become.
Next, a virtual document management control method according to a second embodiment of the present invention will be described with reference to the drawings.
[0069]
FIG. 8 is a block diagram showing a virtual document management control method according to the second embodiment of the present invention. In FIG. 8, the server control unit 6 is provided with a virtual document editor 60. The virtual document editor 60 is a utility application that provides a man-machine interface for constructing a virtual document with an arbitrary page configuration based on a spool file group output by a plurality of applications.
[0070]
The virtual document editor 60 reads spool files output from a plurality of applications and displays them in page units. Then, in accordance with an operation instruction, document data output by a plurality of applications is extracted in units of instruction pages to create a virtual document. Thereafter, printing to a specific printer, copy printing, simultaneous printing with a plurality of printers, etc. are executed in units of created virtual documents.
[0071]
Specifically, a plurality of CAPCAL job description files 34 a,..., 34 b and EMF files 35 a,..., 35 b are stored in the CAPCAL spool document queue 33 corresponding to the document data output from a plurality of applications. If it is generated, the virtual document editor 60 creates a job control file 36 ′ in the CAPCAL spool document queue 33. Here, the job control file 36 ′ created by the virtual document editor 60 is equivalent to the job control file 36 created by the distribution distribution processing thread 37 of FIG. That is, the printer name and the CAPCAL print job ID are written in the job control file 36 ′, and when the print result is output to a plurality of printers, the printer name and the CAPCAL print job ID for each printer are stored in the job control file 36. Written to '.
[0072]
In addition, CAPCAL spool print queues 38a ′, 38b ′,... Are generated for the number of printers to be output corresponding to the CAPCAL print job ID written in the job control file 36 ′. Then, the virtual document editor 60 generates output control files 39a ′, 39b ′,... Corresponding to the respective CAPCAL spool print queues 38a ′, 38b ′,. CAPCAL job ID, start page, end page, and Win job ID are written into 39b '. Here, when the virtual document generated by the virtual document editor 60 is an integrated document data output from a plurality of applications, each output control file 39a ′, 39b ′,. Each CAPCAL job ID, start page, end page, and Win job ID are stored.
[0073]
For example, when the output control file 39a ′ is generated, the virtual document editor 60 activates the output thread 41 for each printer that handles the printer specified in the job control file 36 ′. The printer-specific output thread 41 first refers to the first CAPCAL job ID stored in the output control file 39a ′, so that the CAPCAL job description file 34a stored in the CAPCAL spool document queue 33,. , 34b and EMF files 35a,. For example, when the first CAPCAL job ID stored in the output control file 39a ′ designates the CAPCAL job description file 34a and the EMF file 35a, among the contents of the CAPCAL job description file 34a and the EMF file 35a, The part from the start page to the end page specified by the output control file 39a ′ is taken out from the CAPCAL spool document queue 33, GDI7 is called, and drawing data is sent to the Windows print control 5.
[0074]
Next, the output thread 41 for each printer refers to the second CAPCAL job ID stored in the output control file 39a ′, so that the CAPCAL job description file 34a stored in the CAPCAL spool document queue 33,. ., 34b and EMF files 35a,..., 35b are identified. For example, when the second CAPCAL job ID stored in the output control file 39a ′ designates the CAPCAL job description file 34b and the EMF file 35b, among the contents of the CAPCAL job description file 34b and the EMF file 35b, The part from the start page to the end page specified by the output control file 39a ′ is taken out from the CAPCAL spool document queue 33, GDI7 is called, and drawing data is sent to the Windows print control 5.
[0075]
The per-printer output thread 41 performs the above processing for all CAPCAL job IDs stored in the output control file 39a ′.
When the output control file 39b ′ is generated, the virtual document editor 60 activates the output thread 42 for each printer that handles the printer designated by the job control file 36 ′. The printer-specific output thread 42 first refers to the first CAPCAL job ID stored in the output control file 39b ′, so that the CAPCAL job description file 34a stored in the CAPCAL spool document queue 33,. , 34b and EMF files 35a,. For example, when the first CAPCAL job ID stored in the output control file 39b ′ designates the CAPCAL job description file 34a and the EMF file 35a, among the contents of the CAPCAL job description file 34a and the EMF file 35a, The part from the start page to the end page specified by the output control file 39b ′ is taken out from the CAPCAL spool document queue 33, GDI7 is called, and drawing data is sent to the Windows print control 5.
[0076]
Next, the output thread 42 for each printer refers to the second CAPCAL job ID stored in the output control file 39b ′, so that the CAPCAL job description file 34a stored in the CAPCAL spool document queue 33,. ., 34b and EMF files 35a,..., 35b are identified. For example, when the second CAPCAL job ID stored in the output control file 39b ′ designates the CAPCAL job description file 34b and the EMF file 35b, among the contents of the CAPCAL job description file 34b and the EMF file 35b, The part from the start page to the end page specified by the output control file 39b ′ is taken out from the CAPCAL spool document queue 33, GDI7 is called, and drawing data is sent to the Windows print control 5.
[0077]
The printer-specific output thread 42 performs the above processing for all CAPCAL job IDs stored in the output control file 39a ′.
As a result, it is possible to perform distributed printing of a virtual document by a plurality of printers without forming drawing data of a virtual document created by a plurality of applications in a printer queue.
[0078]
As described above, the virtual document editor 60 virtually generates a document in which the CAPCAL job description files 34a,..., 34b and the EMF files 35a,. Then, instead of writing the virtually generated drawing data of the virtual document to the CAPCAL spool print queues 38a ′, 38b ′,..., The virtual document print request is sent to the CAPCAL spool print queues 38a ′, 38b ′. Write to ... As a result, even when documents created by a plurality of applications are integrated and printed, the spool processing can be performed at a high speed, and the application to be used and the designated page can be easily changed. It becomes possible.
[0079]
FIG. 9A shows an example of the contents of the job control file 36 ′ of FIG. In FIG. 9A, printer names and CAPCAL print job IDs for the number of output printers are written in the job control file 36 ′. Here, the CAPCAL print job ID is a unique five-digit numeric character string for each CAPCAL spool print queue 38a ', 38b',. If this 5-digit numeric character string is one entry and there are a plurality of printers to output, a plurality of entries are written. The file name of the job control file 36 ′ can be “(CAPCAL job ID) .jctI”.
[0080]
FIG. 9B shows an example of the contents of the output control file 39a ′ of FIG. In FIG. 9B, the CAPCAL job ID, the start page, the end page, and the Win job ID are written in the output control file 39a ′. Here, the CAPCAL job ID is an ID for identifying the substance of the CAPCAL job description files 34a,..., 34b and the EMF files 35a,. That is, a different CAPCAL job ID is assigned to each CAPCAL job description file 34a,..., 34b and each EMF file 35a,. The Win job ID is a management ID for identifying a Windows spool job when the printer-specific output thread 41 outputs drawing data to the GDI 7. When a plurality of CAPCAL job description files 34a,..., 34b and EMF files 35a,..., 35b are specified, a plurality of CAPCAL job IDs, start pages, end pages, and Win job IDs are set as one entry. The entry information is written in the output control file 39a ′. The file name of the output control file 39a ′ can be “(CAPCAL print job ID). PctI”. The configuration of the output control files 39b ′,... In FIG.
[0081]
FIG. 10 is a flowchart showing a virtual document management control method according to the second embodiment of the present invention. 10, the virtual document editor 60 generates CAPCAL job description files 34a,..., 34b and EMF files 35a,..., 35b in the CAPCAL spool document queue 33, and outputs the actual output destination (printer) of the virtual document. If a name is detected, a job control file 36 'is generated in the CAPCAL spool document queue 33 (step S21).
[0082]
Next, output control files 39a ′, 39b ′,... Are generated in correspondence with the respective CAPCAL spool print queues 38a ′, 38b ′,... (Step S22), and the spool files ( CAPAL job description files 34a,..., 34b and EMF files 35a,..., 35b) are looped (step S23), and entry information (CAPCAL) corresponding to the number of spool files included in the virtual document is obtained. Job ID, start page, end page).
[0083]
Next, when the entry information (CAPCAL job ID, start page, end page) has been written to the output control files 39a ′, 39b ′,..., An event is sent to the printer-specific output threads 41, 42 dedicated to the printer to be used. (Step S24).
[0084]
Next, the output threads 41 and 42 for each printer output the output control files 39a ′, 39b ′,... From the CAPCAL spool print queues 38a ′, 38b ′,. .. Are read (step S31). Then, one entry information (CAPCAL job ID, start page, end page) is extracted from the output control files 39a ′, 39b ′,... (Step S32), and one job printing process is performed (step S33).
[0085]
In the one-job printing process, the start page in one entry information of the output control files 39a ′, 39b ′,... Is stored in the variable N (step S41), and the output control files 39a ′, 39b ′,. The Nth page of the EMF files 35a,..., 35b under the CAPCAL spool document queue 33 specified by the CAPCAL job ID in one entry information is read (step S42) and output to the GDI 7.
[0086]
Next, while increasing the value of the variable N by 1 (step S43), until the value of the variable N exceeds the end page in one entry information of the output control files 39a ′, 39b ′,... (Step S44). The reading of the Nth page of the EMF files 35a,..., 35b under the CAPCAL spool document queue 33 is repeated.
[0087]
When one job printing process is completed, it is determined whether or not there is a next entry in the output control files 39a ′, 39b ′,... (Step S34), and the output control files 39a ′, 39b ′,. If there is an entry, the process returns to step S32 to repeat the extraction of entry information (CAPCAL job ID, start page, end page) and one job printing process.
[0088]
When there is no next entry in the output control files 39a ′, 39b ′,..., It is determined whether processing for the number of output printers has been performed (step S25), and processing for the number of output printers has been completed. If not, the process returns to step S22 to repeat the creation of the output control files 39a, 39b,.
[0089]
As described above, in the second embodiment of the present invention, the virtual document editor 60 that integrates drawing data output from a plurality of applications is provided, and the virtual document generated by the virtual document editor 60 is managed as one document file. By simply specifying a virtual document, drawing data output from multiple applications can be handled as a whole and printed any number of times, making it easy to perform print processing using multiple applications. It becomes possible. Also, because it can be output from the printer in units of virtual documents, printing using multiple applications without sorting the printed matter printed using multiple applications or adding page serial numbers by handwriting It is possible to automatically perform a printing process such as printing a serial number on the printed matter.
[0090]
FIG. 11 is a block diagram showing a system configuration of a printing system according to an embodiment of the present invention. In FIG. 11, 151 is a central processing unit (CPU) that performs overall processing, 152 is a read only memory (ROM), 153 is a random access memory (RAM), 154 is a communication interface, 155 is a communication network, 156 is Bus 157, an input / output interface, 158 a display for displaying a print image, 159 a printer for outputting a print result, 160 a keyboard, 161 a mouse, 162 a driver for driving a storage medium, 163 a hard disk, 164 An IC memory card, 165 is a magnetic tape, 166 is a floppy disk, and 167 is an optical disk such as a CD-ROM or DVD-ROM.
[0091]
Programs for performing printing processing, print data, and the like are stored in a storage medium such as the hard disk 163, the IC memory card 164, the magnetic tape 165, the floppy disk 166, and the optical disk 167. Then, the printing process can be performed by reading a program for performing the printing process from these storage media to the RAM 153. In addition, a program for performing a printing process can be stored in the ROM 152.
[0092]
Further, a program for performing a printing process, print data, and the like can be taken out from the communication network 155 via the communication interface 154. Examples of the communication network 155 connected to the communication interface 24 include a LAN (Local Area Network), a WAN (Wide Area Network), the Internet, an analog telephone network, a digital telephone network (ISDN), and a PHS (Personal Handy Network). System) and satellite communication.
[0093]
When a program for performing a printing process is started, the CPU 151 stores drawing data input by the keyboard 160 and the mouse 161 on a storage medium such as the hard disk 163, the IC memory card 164, the magnetic tape 165, the floppy disk 166, and the optical disk 167. Store. Then, the drawing data stored in these storage media is sent to the printer 159 for printing, or sent to another server or printer via the communication network 155.
[0094]
【The invention's effect】
As described above, according to the present invention, drawing data to be transferred to an output destination can be drawn without re-storing the drawing data stored in the drawing data storage means in association with the drawing data output destination. By directly reading from the data storage means and transferring it to the output destination, when transferring the drawing data to the output destination, it becomes possible to omit the process of re-storing the drawing data for each output destination. The spool processing can be speeded up.
[0095]
Further, according to one aspect of the present invention, print information for drawing data to be output is stored by storing identification information for identifying drawing data and page information for designating a print page for drawing data instead of drawing data. Is changed, it is only necessary to change the page information without re-storing the contents of the drawing data, so that the spool process can be performed efficiently.
[0096]
In addition, according to one aspect of the present invention, it is possible to integrally handle drawing data created by a plurality of applications by generating a virtual document that integrates drawing data created by a plurality of applications. It is possible to print drawing data created by a plurality of applications by performing print designation for an integrated virtual document only once without performing print designation for each application many times. Can be performed efficiently.
[0097]
In addition, the drawing data included in the virtual document is sequentially read out from the drawing data storage unit based on the virtual document output request without configuring the drawing data of the virtual document in correspondence with the output destination of the drawing data. Since it is possible to transfer to the output destination, it is possible to omit the process of storing the drawing data for each virtual document when transferring the drawing data of the virtual document to the output destination. Can be speeded up.
[Brief description of the drawings]
FIG. 1 is a block diagram illustrating a configuration of a printing system according to an embodiment of the present invention.
FIG. 2 is a block diagram illustrating a configuration of a client control unit in FIG. 1;
FIG. 3 is a block diagram illustrating a configuration of a server control unit in FIG. 1;
4 is a block diagram illustrating a configuration of a printer output control unit in FIG. 1. FIG.
FIG. 5 is a block diagram showing a document management control method according to the first embodiment of the present invention.
6A is a diagram illustrating an example of the contents of the job control file in FIG. 5; FIG. 6B is a diagram illustrating an example of the contents of the output control file in FIG. 5;
FIG. 7 is a flowchart showing a document management control method according to the first embodiment of the present invention.
FIG. 8 is a block diagram showing a virtual document management control method according to a second embodiment of the present invention.
9A is a diagram illustrating an example of the contents of the job control file in FIG. 8, and FIG. 9B is a diagram illustrating an example of the contents of the output control file in FIG. 8;
FIG. 10 is a flowchart showing a virtual document management control method according to a second embodiment of the present invention.
FIG. 11 is a block diagram illustrating a system configuration of a printing system according to an embodiment of the present invention.
FIG. 12 is a block diagram illustrating a conventional distributed printing method.
[Explanation of symbols]
100 clients
103 servers
101, 102, 28, 29, 44 Communication line
1 Application
2,7 GDI
3, 5 Windows printing control unit
4 Client control unit
6 Server controller
8 Printer output controller
9 Printer
11 Spooler process
12 Provider
13, 47 Print processor
14 Virtual drivers
15 CAPCAL driver property control thread
16 System spool queue
17 Output control information file
18 Job description file
19, 24, 35, 35a, 35b EMF file
20 CAPCAL client definition file
21 CAPCAL print processor
22 CAPCAL spool queue
23, 34a, 34b CAPCAL job description file
25 CAPCAL destination definition file
26 CAPCAL Client Main Process
27 CAPCAL job transfer thread
30, 31 CAPCAL reception thread
32 CAPCAL server main process
33 CAPCAL spool document queue
36, 36 Job control file
37 Distribution distributed processing thread
38, 38a, 38b, 38a ', 38b' CAPCAL spool printer queue
39, 39a, 39b, 39a ′, 39b ′ output control file
40 CAPCAL server-side definition file
41, 42 Output thread by printer
43 CAPCAL job transfer thread
45 Printer driver
46 Raw spool file
48 Centroport Monitor
49 Spooler process main
50 Printer output manager
51 port monitor
52, 53 Screen call
60 Virtual Document Editor
151 CPU
152 ROM
153 RAM
154 Communication interface
155 communication network
156 bus
157 I / O interface
158 display
159 Printer
160 keyboard
161 mouse
162 drivers
163 hard disk
164 IC memory card
165 magnetic tape
166 floppy disk
167 optical disc

Claims (4)

A client device that generates drawing data ;
The drawing data received from the client device and the drawing data storing means for store,
Based on the drawing data print request received from the client device, an output request including information for specifying the contents of the drawing data is generated, and the output request is stored for each output destination of the drawing data Request storage means;
Based on the output request stored in the output request storage means, the drawing data having the content specified by the output request is read from the drawing data storage means and transferred to the output destination corresponding to the output request. A printing system comprising a server device including transfer means. The printing system according to claim 1, wherein the output request includes identification information for identifying the drawing data and page information for designating a print page of the drawing data. Drawing data storage means for storing drawing data created by a plurality of applications;
Virtual document generation means for generating a virtual document in which drawing data created by the plurality of applications is integrated ;
An output request storage means for the generating the output request including information for specifying the contents of the virtual documents, and stores the output request for each destination of said virtual documents,
Based on the output request stored in the output request storage means, the drawing data included in the virtual document having the content specified by the output request is read from the drawing data storage means , and the output request is handled. And a drawing data transfer means for transferring to an output destination. A function of storing drawing data received from a client device independently of an output destination of the drawing data;
A function of generating an output request including information for specifying the content of the drawing data based on the drawing data print request received from the client device , and storing the output request for each output destination of the drawing data When,
Based on the output request for the drawing data, the computer has a function of reading the drawing data having the contents stored independently of the output destination and specified by the output request and transferring the drawing data to the output destination corresponding to the output request. A computer-readable storage medium storing a program to be executed.

Images