JP3800801B2 - 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 a conventional client-server printing system, a spool file generated on the client side is transferred to a server, and actual printing is executed by a printer managed by the server.
[0003]
FIG. 5 is a block diagram showing a configuration of a conventional client server printing system. In FIG. 5, a plurality of clients 61 a to 61 c and a plurality of printers 63 a to 63 c are connected to the server 62. When the clients 61a to 61c receive printing from the application 71, a spool file 72 is generated in each of the clients 61a to 61c. The spool file 72 generated by these clients 61a to 61c is transferred to the server 62. When the server 62 receives the spool file 72 from each client 61a to 61c, the spool file 72 corresponds to the transfer 73a to 73d from each client 61a to 61c. Spool files 74a to 74c are generated on the server 62 side. The spool control unit 75 of the server 62 controls the spool files 74a to 74c, and causes the printers 63a to 63c to execute printing 76a to 76d for the spool files 74a to 74c. By executing the printing 76a to 76d, the printers 63a to 63c perform printer printing 77, and print documents 78a to 78c corresponding to the spool files 74a to 74c.
[0004]
As described above, in the conventional client server printing system, the spool file 72 generated as a result of the print execution by the plurality of clients 61a to 61c is sent to the server 62, and the control of printing to the plurality of printers 63a to 63c is performed. By performing this on the side, centralized management as a print server has been performed.
[0005]
[Problems to be solved by the invention]
However, in the conventional client-server printing system, each spool file 74a to 74c is based on information (print target, print start to end page, number of copies, etc.) related to printing obtained from the spool file 72 sent to the server 62. The actual prints 76a to 76d are realized by transferring the contents of the above to the print control (for example, Windows GDI (graphical device interface function)) of the system that controls printing. For this reason, the server 62 cannot centrally manage the contents of the spool file 72 as a result of one print execution in each of the clients 61a to 61c. As a result, information such as the target printer, printing start / end pages, number of copies, and the like cannot be changed on the server 62 side, and spools generated by the clients 61a to 61c are used to change and print these information. There was a problem that the file 72 had to be sent back to the server 62.
[0006]
When printing from one spool file 72 to a plurality of printers 63a to 63c (distributed printing, etc.), a print queue is generated for each printer 63a to 63c for one spool file 72. The operation relating the file 72 and these print queues could not be performed. Therefore, when canceling the print queue for one spool file 72, it is necessary to cancel the print queue for each printer, and the print queue must be canceled for one spool file 72 many times. There was also a problem.
[0007]
Accordingly, a first object of the present invention is to provide a printing system capable of processing a spool file and a print queue in association with each other.
A second object of the present invention is to provide a printing system capable of managing the contents of a spool file as a print execution result at a client on the server side.
[0008]
[Means for Solving the Problems]
In order to solve the above-described problem, according to the present invention, related information in which a spool file generated by printing execution from an application and a print queue derived from the spool file are associated is generated.
[0009]
As a result, when a spool file information operation is performed, a print queue derived from the spool file can be easily detected. By simply operating the spool file information, Since it is also possible to automatically perform operations on derived print queue information, the same operation is performed for each print queue even when multiple print queues are generated from one spool file. It can be made unnecessary to repeat it many times.
[0010]
According to another aspect of the present invention, a spool file receiving unit that receives a spool file transferred from a client, a print control information acquisition unit that acquires information necessary for print control from the spool file, and the spool file Print control information operating means for operating information necessary for print control acquired from the above, and print execution means for executing print on the spool file based on the operated information.
[0011]
This makes it possible to operate information necessary for print control generated on the client side on the server side. For the spool file generated on the client side, the target printer, print start / end pages, number of copies, etc. Since the information can be changed on the server side, it is not necessary to resend the spool file from the client side even when the information is changed, and the printing process can be performed efficiently.
[0012]
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. FIG. 1 is a block diagram showing the configuration of a printing system according to an embodiment of the present invention. In FIG. 1, the spool file 5 is generated in the local machine as the client 1 by executing printing of the application 4. When the generated spool file 5 is transferred to the remote server 2, spool files 7a to 7c are generated on the server 2 side corresponding to the transfers 6a to 6d of the spool file 5 generated by the client 1. .
[0013]
When the spool files 7a to 7c are generated on the server 2 side, the spool control unit 8 acquires information necessary for printing from the spool files 7a to 7c. Then, the spool control unit 8 requests the print control unit 10 that controls the prints 9a to 9d for each actual printer 3 to perform processing in units of queues, and the print control unit 10 performs the prints 9a to 9d to the printer 3 in units of queues. It is possible to obtain the print results 11a to 11c by executing the above.
[0014]
Here, in a normal operation, the spool files 7a to 7c that are deleted after printing are deleted from the server 2 when the printing 10a to 10d is completed by obtaining the printing results 11a to 11c. In addition, when the file is stored after printing or printing is not completed, the spool files 7 a to 7 c exist in the server 2.
[0015]
In the embodiment of FIG. 1, in order to manage the spool files 7a to 7c existing in the server 2 and the print queue derived from the spool files 7a to 7c, the spool file management table 12, the spool queue management table 13, and the print queue A management table 14 is provided. Further, a logical queue control unit 15 and a physical queue control unit 16 are provided for operating the spool files 7a to 7c existing in the server 2 and a print queue derived from the spool files 7a to 7c.
[0016]
The spool file management table 12 stores information related to the spool files 7a to 7c. For example, information related to printing such as a print page range to the output destination printer 3 is stored. The spool file management table 12 is generated when the spool file 5 is transferred to the server 2, and is independent of the direct operation on the spool files 7a to 7c by the logical queue control unit 15, and is stored in the spool file management table 12. You can manipulate the contents.
[0017]
By referring to the spool file management table 12, the spool control unit 8 can manage information related to printing (print page range to the output destination, etc.) for each of the spool files 7a to 7c.
[0018]
The print queue management table 14 stores information indicating the status of the print queue generated from the spool files 7a to 7c requested to be printed 9a to 9d. For example, the current information such as the queue order and the page for which printing has been completed is stored. Information indicating the state is stored. The print queue management table 14 adds information indicating the status of the print queue when printing is requested, and the physical queue control unit 16 directly accesses the print queue independently of operations on the spool files 7a to 7c. Can be operated. In addition, by displaying the contents of the print queue management table 14, it is possible to display information on only print queues waiting for printing without depending on the state of the spool files 7a to 7c.
[0019]
By referring to the print queue management table 14, the print control unit 10 can manage the current state of the queue order and pages for which printing has been completed for each print queue requested to be printed. it can.
[0020]
The spool queue management table 13 stores information on the print queue for the printer 3 to be printed that can be assumed at the present time from the information in the spool file management table 12. By referring to the spool queue management table 13, the spool files 7a to 7c under the spool file management table 12 and the print queue under the print queue management table 14 can be associated with each other. Therefore, it is possible to operate the print queue in units of spool files 7a to 7c regardless of whether there is a print request, and it is also possible to manage a plurality of print queues derived from one spool file 7a to 7c to a plurality of printers 3. It becomes. Further, the spool files 7a to 7c and the print queue can be managed independently.
[0021]
The logical queue control unit 15 has a man-machine interface with the user and operates the spool file management table 12 and the spool queue management table 13. Since the information of the spool files 7a to 7c existing in the server 2 is stored in the spool file management table 12, the spool file can be displayed by displaying and operating the information of the spool file management table 12 from the logical queue control unit 15. Information about 7a to 7c can be displayed and operated.
[0022]
In addition, by reflecting the information change of the spool files 7a to 7c generated by the user operation in the logical queue control unit 15 to the spool file management table 12 and notifying the spool control unit 8, these synchronized operations are performed. Is possible. When the information change of the spool files 7a to 7c also affects the contents of the spool queue management table 13 and the print queue management table 14, the information change of the spool files 7a to 7c is changed to the spool queue management table 13 and It can also be reflected in the print queue management table 14.
[0023]
The physical queue control unit 16 has a man-machine interface with the user, and operates the spool queue management table 13 and the print queue management table 14. Since the information indicating the current state of the print queue generated from the spool files 7a to 7c requested to be printed is stored in the print queue management table 14, the information in the print queue management table 14 is received from the physical queue control unit 16. By displaying and operating this, it is possible to display and operate the current information regarding the print queue.
[0024]
In addition, the print queue state change caused by the user operation in the physical queue control unit 16 is reflected in the print queue management table 14 and notified to the print control unit 10 or the spool control unit 8, thereby synchronizing these changes. Operation becomes possible. When the information change of the spool files 7a to 7c affects the contents of the spool file management table 12 and the spool queue management table 13, the information change of the spool files 7a to 7c is changed to the spool file management table 12 and It can also be reflected in the spool queue management table 13.
[0025]
In this way, by associating the spool files 7a to 7c with the print queue, respectively, the operations for the spool files 7a to 7c can be reflected in the print queue and the operations for the print queue can be reflected in the spool files 7a to 7c in both directions. In simultaneous printing of one spool file 7a to 7c to a plurality of printers 3 and the like, it is possible to operate a print queue generated for each printer 3 only by operating one spool file 7a to 7c.
[0026]
FIG. 2A is a diagram showing the configuration of the spool file management table 12 according to an embodiment of the present invention. The spool file management table 12 is information composed of one entry for one spool file 7a to 7c, and has as many entries as the number of spool files 7a to 7c. In FIG. 2A, the job identifier is an identifier that links the entity of the spool files 7a to 7c and one entry information. The total number of pages is the number of pages of the spool file 5 as a result of one printing execution. The print page order is the order of print pages such as sort / stack. The operation mode is information indicating a printing method such as normal / distribution / distribution. The output mode is information indicating printing start timing such as immediate printing / time designation / date designation / no printing. The save mode is information indicating the timing of automatic deletion of the spool files 7a to 7c after completion of printing, such as deletion after printing and date / time deletion. The spool file status is information indicating the current status of the spool files 7a to 7c, such as the presence / absence of a print queue that has been subjected to printing. The number of queues is the number of queues to be derived from one spool file 7a to 7c.
[0027]
FIG. 2B is a diagram showing the configuration of the spool queue management table 13 according to an embodiment of the present invention. The spool queue management table 13 is information composed of one entry for one queue derived from the spool files 7a to 7c, and has as many entries as the number of queues. For example, for normal printing, one spool file = 1 queue, and for distributed printing, one spool file = multiple queues.
[0028]
In FIG. 2B, the job identifier is an identifier that links the spool queue management table 13 and the spool file management table 12, and this job is displayed while the spool files 7a to 7c exist regardless of whether or not printing is performed. There is also an identifier. The queue identifier is an identifier that links the spool queue management table 13 and the print queue management table 14, and is empty if there is no printing. The printer name is the name of the printer into which one queue is to be input. The queue status is information indicating the status of the queue at the time of non-printing / non-throwing / throwing / printing completed.
[0029]
FIG. 2C is a diagram showing the configuration of the print queue management table 14 according to an embodiment of the present invention. The print queue management table 14 is information composed of one entry for one queue having a print request derived from a spool file, and has entries for the number of queues waiting for printing. In FIG. 2C, the queue identifier is an identifier that links the print queue management table 14 and the spool queue management table 13. The print start page is a page number for the original spool files 7a to 7c for starting printing of one queue. The print end page is a page number for the original spool files 7a to 7c to finish printing of one queue. The print page order is information indicating the order of print pages such as sort / stack. The print queue status is information indicating the status (error or the like) of a print queue that is printing or waiting to be printed. The print completion page is information indicating the page number of the paper discharged from the printer 3 at this time if it can be controlled as detailed information of the print queue being printed.
[0030]
Note that the information in the spool file management table 12 and the spool queue management table 13 is deleted when there is no spool file, and the information in the print queue management table 14 is deleted when print waiting is canceled and there is no entry.
[0031]
FIG. 3 is a block diagram showing the operation of the printing system according to the embodiment of the present invention. 3, when the modules of the logical queue control unit 15 and the physical queue control unit 16 in FIG. 2 are activated, information is acquired from the spool file management table 12, the spool queue management table 13, and the print queue management table 14. Further, the job identifier stored in the spool file management table 12 is referred to, and information is acquired from the spool files 7a to 7c linked by this job identifier. When the logical queue control unit 15 and the physical queue control unit 16 acquire these pieces of information, the management information display 21 is performed on each screen. If all the information of the spool files 7a to 7c is registered in the spool queue management table 13, the information from the spool files 7a to 7c is not acquired.
[0032]
Next, control is given to the Windows event handler 22 and waits until an event occurs. For example, when printing is completed, a change 27 in the spool file management table 12, a change 28 in the spool queue management table 13, and a change 29 in the print queue management table 14 are performed. The spool control unit 8 updates the screen information display 21 when notified to the control unit 8.
[0033]
Also, when an operation 23 from the user occurs, the event handler 22 is exited, and the spool file information change 24, the queue information change 25, and the print queue information change 26 are performed.
[0034]
In the spool file information change 24, when an operation to change the spool file information operable on the disk or an operation to delete the spool files 7a to 7c itself is performed, the entry change 27 in the spool file management table 12 and The entry change 28 of the spool queue management table 13 is performed. If the operation also affects the print queue waiting to be printed, the entry change 29 in the print queue management table 14 is also performed.
[0035]
For example, when an operation to delete the spool files 7a to 7c is performed, entry information having a job identifier associated with the spool files 7a to 7c is deleted from the spool file management table 12. Further, the job identifier associated with the deleted spool file 7 a to 7 c is searched from the spool queue management table 13, and the entry information having the job identifier is deleted from the spool queue management table 13. Further, the queue identifier included in the entry information deleted from the spool queue management table 13 is searched from the print queue management table 14, and the entry information having the queue identifier is deleted from the print queue management table 14.
[0036]
As described above, the user follows the spool file management table 12, the spool queue management table 13, and the print queue management table 14 while referring to the job identifier and the queue identifier, thereby allowing the user to delete the spool files 7a to 7c. It is possible to delete the print queue generated by deriving from the spool files 7a to 7c only by performing this.
[0037]
In the queue information change 25, when an operation such as a print cancel operation during input for changing the queue state or an uninput print request is performed, an entry change 28 in the spool queue management table 13 is performed. If the operation also affects the print queue waiting to be printed, the entry change 29 in the print queue management table 14 is also performed.
[0038]
In the change 26 of the print queue information, when an operation for changing the output destination printer of the queue waiting for printing, the print start to end pages, or the like is performed, the entry change 29 of the print queue management table 14 is performed.
[0039]
When the change 27 of the spool file management table 12, the change 28 of the spool queue management table 13, or the change 29 of the print queue management table 14 is performed, these information changes 27, 28, 29 are notified to the spool control unit 8. The Upon receiving notification of information changes 27, 28, and 29, the spool controller 8 keeps the consistency of the management information and notifies the higher level that the management information has been changed. As a result, even when a plurality of modules serving as user interfaces are activated, each process receives this notification, so that the contents of management information changed by other processes can be reacquired.
[0040]
As described above, the queue information derived from the information obtained from the spool file 5 sent to the server 2 is managed as a logical queue, and the print queue information input from the logical queue to the system print control 10 is managed as a physical queue. As a result, the logical queue and the physical queue can be associated with each other depending on the situation, or can be handled independently, so that not only the normal print queue management but also a document that is one print result from the spool file 5 Can also be managed.
[0041]
In addition, information that associates logical queues with physical queues is gathered as a spool queue management table 13 so that consistency can be maintained even when operated from a plurality of clients 1, so that the operation results for the logical queues are also reflected in the physical queues. And the operation result for the physical queue can be reflected in the logical queue. Even in user operations in different scenes, it is conscious of processing from other processes for each module and control of synchronization. It can be made unnecessary to do in
[0042]
In addition, by managing information on logical queues, physical queues, and their associations at different levels, print queues derived from a single spool file can be managed in the same way as with a normal one spool file and one queue. It is possible to perform operations on all queues derived from a single operation on the original spool file.
[0043]
In the above-described embodiment, the management tables 12, 13, and 14 of the three layers are controlled based on the information of the spool files 7a to 7c and the information of the print queue of the system. The management table may be added to the control target in addition to another hierarchy. In addition, a control mechanism that can manage the transfer of print data to other print servers may be added to the same hierarchy as the print queue management mechanism to perform management under a network that spans multiple domains.
[0044]
FIG. 4 is a block diagram showing the system configuration of the printing apparatus according to an embodiment of the present invention. In FIG. 4, 41 is a central processing unit (CPU) that performs overall processing, 42 is a read only memory (ROM), 43 is a random access memory (RAM), 44 is a communication interface, 45 is a communication network, 46 is Bus, 47 is an input / output interface, 48 is a display for displaying a print image, 49 is a printer for outputting print results, 50 is a keyboard, 51 is a mouse, 52 is a driver for driving a storage medium, 53 is a hard disk, 54 is An IC memory card, 55 is a magnetic tape, 56 is a floppy disk, and 57 is an optical disk such as a CD-ROM or DVD-ROM.
[0045]
A program for performing print processing, a spool management control program, print data, and the like are stored in a storage medium such as the hard disk 53, the IC memory card 54, the magnetic tape 55, the floppy disk 56, and the optical disk 57. The printing process can be performed by reading a program for performing the printing process from these storage media to the RAM 43. Further, spool management can be performed by reading the spool management control program from these storage media into the RAM 43. Note that a program for performing a printing process and a spool management control program can be stored in the ROM 42.
[0046]
Furthermore, a print processing program, a spool management control program, print data, and the like can be taken out from the communication network 45 via the communication interface 44. As the communication network 45 connected to the communication interface 44, for example, a LAN (Local Area Network), a WAN (Wide Area Network), the Internet, an analog telephone network, a digital telephone network (ISDN: Integrated Service Digital Network), a PHS (Personal Handy System). ) And satellite communication can be used.
[0047]
When a program for performing a printing process is started, the CPU 41 stores drawing data input by the keyboard 50, the mouse 51, and the like on a storage medium such as the hard disk 53, the IC memory card 54, the magnetic tape 55, the floppy disk 56, and the optical disk 57. Store. Then, the drawing data stored in these storage media is sent to the printer 49 for printing, or sent to another server or printer via the communication network 45.
[0048]
In addition, when the spool management control program is started, the CPU 41 manages the spool file and the print queue in association with each other, operates the spool file and the print queue according to the related information between the spool file and the print queue, The contents of the file and the contents of the print queue are displayed on the display 48.
[0049]
【The invention's effect】
As described above, according to the present invention, by generating related information that associates a spool file generated by printing execution from an application and a print queue derived from the spool file, information on the spool file can be stored. When an operation is performed, it is possible to easily detect a print queue derived from the spool file, and an operation on the information of the print queue derived from the spool file can be performed simply by operating the information of the spool file. Can be automatically performed, and even when a plurality of print queues are derived from one spool file and generated, it is not necessary to repeat the same operation for each print queue many times. be able to.
[0050]
Further, according to one aspect of the present invention, the information necessary for print control generated on the client side is manipulated on the server side, so that the spool printer generated on the client side, It is possible to change information such as the number of copies on the server side, and even when changing this information, it is not necessary to resend the spool file from the client side, and the printing process can be performed efficiently. Become.
[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.
2A is a diagram showing a configuration of a spool file management table according to an embodiment of the present invention; FIG. 2B is a diagram showing a configuration of a spool queue management table according to an embodiment of the present invention; (C) is a diagram showing the configuration of a print queue management table according to an embodiment of the present invention.
FIG. 3 is a block diagram illustrating an operation of a printing system according to an embodiment of the present invention.
FIG. 4 is a block diagram illustrating a system configuration of a printing system according to an embodiment of the present invention.
FIG. 5 is a block diagram illustrating a configuration of a conventional client server printing system.
[Explanation of symbols]
1 client
2 servers
3 Printer
4 Application
5, 7a-7c Spool file
8 Spool controller
10 Print controller
11a-11c Print result
12 Spool file management table
13 Spool queue management table
14 Print queue management table
15 Logical queue controller
16 Physical queue controller
41 CPU
42 ROM
43 RAM
44 Communication interface
45 Communication network
46 bus
47 I / O interface
48 display
49 Printer
50 keyboard
51 mice
52 drivers
53 Hard disk
54 IC memory card
55 magnetic tape
56 floppy disk
57 optical disc

Claims (3)

Spool file generating means for generating a spool file by executing printing from an application , generating print management information for the spool file, and creating a spool file management table for storing the print management information ;
A print queue generating means for generating a print queue management table for storing the state management information and generates state management information of the print queue and generates at least one or more print queues that derives from the spool file,
Related information generating means for generating related information associating the spool file with the print queue and creating a soup queue management table for storing the related information;
Spool file operating means for operating the print management information of the spool file;
Print queue detection means for detecting at least one print queue associated with a spool file on which the operation of the print management information has been performed by referring to the related information;
And a print queue control unit configured to collectively control the print management information of the at least one detected print queue based on an operation result of the print management information of the spool file. A spool file receiving means for receiving a spool file transferred from a client;
Print control information acquisition means for acquiring information necessary for print control from the spool file and creating a spool file management table for storing the information;
Print queue generation means for generating a print queue derived from the spool file and generating print queue status management information and storing the status management information;
Related information generating means for generating related information associating the spool file with the print queue and creating a soup queue management table for storing the related information;
Print control information operating means for operating information necessary for print control acquired from the spool file;
Print that refers to the previous period related information, updates the status management information of the print queue based on the information necessary for the operated print control, and performs printing on the spool file based on the updated status management information And a printing system. A function of generating print management information of a spool file generated by printing execution from an application and creating a spool file management table for storing the print management information ;
And the ability to create and print queue management table for storing the state management information and generates state management information of one or more print queues generated derived from the spool file,
A function of generating related information associating the spool file with the print queue, and creating a soup queue management table for storing the related information ;
A function for operating print management information of the spool file;
A function of detecting at least one or more print queues associated with a spool file on which the operation of the print management information has been performed by referring to the related information;
A computer-readable program storing a program for causing a computer to execute a function of collectively controlling the status management information of at least one or more detected print queues based on an operation result of print management information of the spool file. Storage medium.

Images