Abstract:
The printing device is a printing device having a reception part receiving print data, a print job information storage storing print job information of the print data, an image data conversion part concerting the print data to image data, a print queue generation part generating print queue information administrating the print data on the basis of page upon conversion from the print data to image data, a print job ID storage storing the print job ID at the time of an order when job cancellation is ordered, and a control part comparing the print job ID stored in the print job ID storage with the print job ID at the time of execution in execution of job cancellation and cancelling the print job ID when the print job IDs are equal. The printing device allows job cancellation to be specified without multiple panel operations in ordering job cancellation order.

Description:
CROSS-REFERENCE TO RELATED APPLICATION 
       [0001]    This application claims the benefit of Japanese Patent Application No. 2011-218584, filed on Sep. 30, 2011, the entire disclosure of which is incorporated by reference herein. 
       FIELD 
       [0002]    This application relates to a printing device capable of canceling a print job once registered. 
       BACKGROUND 
       [0003]    Nowadays, printing systems in which a host device such as a host computer and a printing device such as a printer are connected via a network are used. In such printing systems, the printing device receiving print jobs sent from the host device and executing the printing in sequence often displays on the panel information on the job in the process of printing. Therefore, when multiple print jobs are received, the print job displayed on the panel is job information in the process of printing at the time. 
         [0004]    However, with a high speed printing device such as a page printer, multiple sheets of printing paper are conveyed in the device. For example, at the time of a sheet being about to be ejected, several new sheets have already been fed into the device from the paper feeder and conveyed within the device. If the printing device is paused in such a state, the sheets fed into the device are ejected according to a proper control; however, the device cannot be paused before the sheets are ejected. In other words, if an attempt is made to pause the printing device in the middle of continuous printing, the subsequent sheets fed into the device will jam within the device. Then, the printing device should be paused after the sheets being conveyed within the device are ejected. 
         [0005]    On the other hand, many printing devices are capable of canceling a print job. The function of cancelling a print job is a function to pause the ongoing print job through operation on the operation panel for no further output of sheets, for example, when some wrong print setting is found after the printing starts. 
         [0006]    Here, two panel operations are generally required for cancelling a print job. The first operation is an order to pause the printing device in operation and the second operation is an order to confirm job information and execute the job cancellation. The reason for requiring the two panel operations is that when an attempt is made to pause the aforementioned high-speed printing device at a specific moment, the printing device does not pause immediately and a print job different from the intended print job may be cancelled. Therefore, when the operator cancels a job, he/she confirms the job information after the printing device pauses and operates the panel to cancel the intended print job with no mistake. 
         [0007]    Unexamined Japanese Patent Application Kokai Publication No. 2008-36999 discloses an image forming device determining whether a reserved and registered print job satisfies preset cancelation conditions and executing a job cancelation procedure when the cancelation conditions are satisfied so as to cancel the print job without complicate operations. 
         [0008]    As mentioned above, two operations are conducted on the operation panel for cancelling a print job in the prior art. However, there may be the same print job at the time of the first panel operation and at the time of the second panel operation, for example, depending on the number of pages of print data. Some user who is familiar with the job cancelling operation may conduct the second panel operation without confirming the cancelation target job well. In such a case, a wrong print job may be designated as the cancellation target. 
         [0009]    Furthermore, two panel operations for canceling a job are a burden for the user. 
       SUMMARY 
       [0010]    Then, an exemplary object of the present invention is to provide a printing device eliminating the need of multiple panel operations in a job cancellation procedure to reduce the user workload and allowing the cancellation target job to be specified with no mistake. 
         [0011]    The printing device according to a first exemplary aspect of the present invention comprises a receiver receiving a print job sent from a host device; a print processor executing printing on at least one or more recording media based on print data included in the print job received by the receiver; a job table registering and storing administrative information of the print job received by the receiver; a controller registering, upon reception of a print job by the receiver, administrative information of the print job received by the receiver in the job table, and ordering the print processor to execute printing based on the registered print job, adding information indicating that the printing is in progress to the administrative information of the print job on which the execution is ordered, inquiring of the print processor whether ejection of a recording medium corresponding to the print job on which the execution of printing is ordered from the print processor is completed, and deregistering from the job table the print job registered in the job table if an ejection completion response is made; a job cancellation inputter through which the user inputs a job cancellation order to cancel the printing of a print job in the process of printing; and a job-ID-upon-cancel-operation storage storing the ID of the print job in the process of printing when a printing cancellation order is input from the job cancellation inputter, wherein the controller outputs an order to pause the ongoing printing to the print processor according to the job cancellation order input from the job cancellation inputter; the print processor completes the ordered pause of printing and makes a response indicating the completion of pause of printing to the controller; and the controller compares the ID of the print job registered in the job table as in the process of printing with the ID stored in the job-ID-upon-cancel-operation storage, and cancels the printing of the print job having the print job ID when the ID of the registered print job and the stored ID are equal in spite of time difference between the time the job cancellation inputter received the job cancellation order and the time the print processor received the response indicating the completion of pause of printing. 
         [0012]    The printing device according to a second exemplary aspect of the present invention comprises a receiver receiving a print job sent from a host device; a print processor executing printing on at least one or more recording media based on print data included in the print job received by the receiver; a job table registering and storing administrative information of the print job received by the receiver; a controller registering, upon reception of a print job by the receiver, administrative information of the print job received by the receiver in the job table, counting and storing the number of the registered print jobs, ordering the print processor to execute printing based on the registered print job, and adding information indicating that the printing is in progress to the administrative information of the print job on which the execution is ordered, 
         [0013]    inquiring of the print processor whether ejection of a recording medium corresponding to the print job on which the execution of printing is ordered from the print processor is completed, and deregistering from the job table the print job registered in the job table if an ejection completion response is made; a job cancellation inputter through which a job cancellation order for cancelling the printing of a print job in the process of printing is input; and a number-of-jobs-upon-cancel-operation storage storing the number of print jobs when a printing cancellation order is input from the job cancellation inputter, wherein the controller outputs an order to pause the ongoing printing to the print processor according to the job cancellation order input from the job cancellation inputter; the print processor completes the ordered pause of printing and makes a response indicating the completion of pause of printing to the controller; and 
         [0014]    the controller compares the number of print jobs registered in the job table as in the process of printing with the number stored in the number-of-jobs-upon-cancel-operation storage, and cancels the printing of the print job in the process of printing when the number of registered print jobs and the stored number are equal in spite of time difference between the time the job cancellation inputter received the job cancellation order and the time the print processor received the response indicating the completion of pause of printing. 
         [0015]    The printing method according to a third exemplary aspect of the present invention is a printing method in a printing device including a receiver receiving a print job sent from a host device; a print processor executing printing on at least one or more recording media based on print data included in the print job received by the receiver; and a job table registering and storing administrative information of the print job received by the receiver, wherein upon reception of a print job by the receiver, administrative information of the print job received by the receiver is registered in the job table, and the print processor is ordered to execute printing based on the registered print job, information indicating that the printing is in progress is added to the administrative information of the print job on which the execution is ordered, the print processor is inquired whether ejection of a recording medium corresponding to the print job on which the execution of printing is ordered from the print processor is completed, the print job registered in the job table is deregistered from the job table if an ejection completion response is made, “a job cancellation order for cancelling the printing of a print job in the process of printing” input from a job cancellation inputter is received, the ID of the print job in the process of printing when a printing cancellation order is input from the job cancellation inputter is stored in a job-ID-upon-cancel-operation storage, an order to pause the ongoing printing is output to the print processor according to the job cancellation order input from the job cancellation inputter, the print processor completes the ordered pause of printing and makes a response indicating the completion of pause of printing to the controller, the ID of the print job registered in the job table as in the process of printing is compared with the ID stored in the job-ID-upon-cancel-operation storage, and the printing of the print job having the print job ID is cancelled when the ID of the registered print job and the stored ID are equal in spite of time difference between the time the job cancellation inputter received the job cancellation order and the time the print processor received the response indicating the completion of pause of printing. 
         [0016]    The printing method according to a fourth exemplary aspect of the present invention is a printing method in a printing device including a receiver receiving a print job sent from a host device; a print processor executing printing on at least one or more recording media based on print data included in the print job received by the receiver; and a job table registering and storing administrative information of the print job received by the receiver, wherein upon reception of a print job by the receiver, administrative information of the print job received by the receiver is registered in the job table, the number of the registered print jobs is counted and stored, the print processor is ordered to execute printing based on the registered print job, information indicating that the printing is in progress is added to the administrative information of the print job on which the execution is ordered, the print processor is inquired whether ejection of a recording medium corresponding to the print job on which the execution of printing is ordered from the print processor is completed, the print job registered in the job table is deregistered from the job table if an ejection completion response is made, the administrative information of the next print job registered and stored is updated to in the process of printing, the print processor is ordered to execute the printing of the updated print job, a job cancellation order for cancelling the printing of a print job in the process of printing input from a job cancellation inputter is received, the number of print jobs when there is a printing cancellation order from the job cancellation inputter is stored in a number-of-jobs-upon-cancel-operation storage, an order to pause the ongoing printing is output to the print processor according to the job cancellation order input from the job cancellation inputter, the print processor completes the ordered pause of printing and makes a response indicating the completion of pause of printing to the controller, and the controller compares the number of print jobs registered in the job table as in the process of printing with the number stored in the number-of-jobs-upon-cancel-operation storage, and cancels the printing of the print job in the process of printing when the number of registered print jobs and the stored number are equal in spite of time difference between the time the job cancellation inputter received the job cancellation order and the time the print processor received the response indicating the completion of pause of printing. 
         [0017]    The non-transitory storage medium according to a fifth exemplary aspect of the present invention is a storage medium storing a program for a computer to realize a printing method of cancelling printing of a print job received from a host device, executing a process to receive a print job sent from the host device by mean of a receiver; a process to make print on at least one or more recording media based on print data included in the print job received by the receiver; a process to register, upon reception of a print job by the receiver, administrative information of the print job received by the receiver in a job table, and order the print processor to execute printing based on the registered print job, and add information on the printing being in progress to the administrative information of the print job on which the execution is ordered; a process to inquire of the print processor whether ejection of a recording medium corresponding to the print job on which the execution of printing is ordered from the print processor is completed, deregister from the job table the print job registered in the job table if an ejection completion response is made, update the administrative information of the next print job registered and stored to in the process of printing, and order the print processor to execute the printing of the updated print job; a process to receive a job cancellation order for cancelling the printing of a print job in the process of printing input from a job cancellation inputter; and a process to store the ID of the print job in the process of printing when there is a printing cancellation order from the job cancellation inputter in a job-ID-upon-cancel-operation storage, and allowing the computer to further execute a process in which an order to pause the ongoing printing is output to the print processor according to the job cancellation order input from the job cancellation inputter; the print processor completes the ordered pause of printing and makes a response indicating the completion of pause of printing to the controller; and the ID of the print job registered in the job table as in the process of printing is compared with the ID stored in the job-ID-upon-cancel-operation storage, and the printing of the print job having the print job ID is cancelled when the ID of the registered print job and the stored ID are equal in spite of time difference between the time the job cancellation inputter received the job cancellation order and the time the print processor received the response indicating the completion of pause of printing. 
         [0018]    The non-transitory storage medium according to a sixth exemplary aspect of the present invention is a storage medium storing a program for a computer to realize a printing method of cancelling printing of a print job received from a host device, executing a process to receive a print job sent from the host device by means of a receiver; a process to make print on at least one or more recording media based on print data included in the print job received by the receiver; a process to register, upon reception of a print job by the receiver, administrative information of the print job received by the receiver in a job table, count the number of the registered print jobs, order execution of printing, and add information on the printing being in progress to the administrative information of the print job on which the execution is ordered; a process to inquire of the print processor whether ejection of a recording medium corresponding to the print job on which the execution of printing is ordered from the print processor is completed, deregister from the job table the print job registered in the job table if an ejection completion response is made, update the administrative information of the next print job registered and stored to in the process of printing, and order the print processor to execute the printing of the updated print job; a process to receive a job cancellation order for cancelling the printing of a print job in the process of printing from a job cancellation inputter; and a process to store the number of print jobs when there is a printing cancellation order from the job cancellation inputter in a number-of-jobs-upon-cancel-operation storage, and allowing the computer to further execute a process in which an order to pause the ongoing printing is output to the print processor according to the job cancellation order input from the job cancellation inputter; the print processor completes the ordered pause of printing and makes a response indicating the completion of pause of printing to the controller; and the number of print jobs registered in the job table as in the process of printing is compared with the number stored in the number-of-jobs-upon-cancel-operation storage, and the printing of the print job in the process of printing is cancelled when the number of registered print jobs and the stored number are equal in spite of time difference between the time the job cancellation inputter received the job cancellation order and the time the print processor received the response indicating the completion of pause of printing. 
         [0019]    The present invention stores information on the job ID upon cancel operation when a job cancellation order is made, makes comparison with the job ID upon cancel operation in executing print job cancellation, and if they match, executes the job cancellation without further operation on the operation button, whereby job cancellation is executed without complicate operation. Furthermore, the present invention stores information on the number of jobs upon cancel operation, makes comparison with the number of print jobs upon execution of cancellation, and if they match, executes the job cancellation without further operation on the operation button, whereby job cancellation is executed without complicate operation. 
     
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
         [0020]    A more complete understanding of this application can be obtained when the following detailed description is considered in conjunction with the following drawings, in which: 
           [0021]      FIG. 1  is an illustration showing the basic system configuration of the embodiment; 
           [0022]      FIG. 2  is an illustration showing the job table structure; 
           [0023]      FIG. 3  is an illustration showing the conceptual relationship between the print queue state and print queue table; 
           [0024]      FIG. 4  is an illustration showing the print queue table structure; 
           [0025]      FIG. 5  is an illustration showing the data structure on the number of created print queues, writing position, and reading positions in the initial state; 
           [0026]      FIG. 6  is an illustration showing an exemplary job table storing specific data; 
           [0027]      FIG. 7  is an illustration showing an exemplary print queue table storing specific data; 
           [0028]      FIG. 8  is an illustration showing the data structure on the number of created print queues, writing position, and reading positions; 
           [0029]      FIG. 9  is a flowchart for explaining the processing of the reception part upon regular printing; 
           [0030]      FIG. 10  is a flowchart for explaining the processing of the control part upon regular printing; 
           [0031]      FIG. 11  is a flowchart for explaining the processing of the RIP part upon regular printing; 
           [0032]      FIG. 12  is a flowchart for explaining the processing of the transfer part upon regular printing; 
           [0033]      FIG. 13  is a flowchart for explaining the processing of the paper ejection part upon regular printing; 
           [0034]      FIG. 14  is a flowchart of the control part for explaining the printing process including job cancellation; 
           [0035]      FIG. 15  is a flowchart of the control part for explaining the printing process including job cancellation; 
           [0036]      FIG. 16  is a flowchart of the RIP part for explaining the printing process including job cancellation; 
           [0037]      FIG. 17  is a flowchart of the RIP part for explaining the printing process including job cancellation; 
           [0038]      FIG. 18  is a flowchart of the transfer part for explaining the printing process including job cancellation; 
           [0039]      FIG. 19  is a flowchart of the paper ejection part for explaining the printing process including job cancellation; 
           [0040]      FIG. 20  is a flowchart for explaining the processing of the display operation control part; 
           [0041]      FIG. 21  is an illustration showing the system configuration of Embodiment 1; 
           [0042]      FIG. 22  is a flowchart for explaining the processing of the control part in Embodiment 1; 
           [0043]      FIG. 23  is a flowchart for explaining the processing of the control part in Embodiment 1; 
           [0044]      FIG. 24  is a flowchart for explaining the processing of the display operation control part in Embodiment 1; 
           [0045]      FIG. 25A  is an illustration showing an exemplary regular display upon job cancellation; 
           [0046]      FIG. 25B  is an illustration showing an exemplary irregular display upon job cancellation; 
           [0047]      FIG. 26  is an illustration showing the system configuration of Embodiment 2; 
           [0048]      FIG. 27  is a flowchart for explaining the processing of the control part in Embodiment 2; 
           [0049]      FIG. 28  is a flowchart for explaining the processing of the control part in Embodiment 2; and 
           [0050]      FIG. 29  is a flowchart for explaining the processing of the control part in Embodiment 3. 
       
    
    
     DETAILED DESCRIPTION 
       [0051]    Embodiments of the present invention will be described hereafter with reference to the drawings. 
         [0052]      FIG. 1  is an illustration showing the basic system of this embodiment. In the figure, a printer  1  is connected to a host device  2  such as a personal computer (PC) via a network such as a LAN (local area network). The printer  1  is composed of a reception part  3 , a control part  4 , a RIP part  5 , a transfer part  6 , a printer engine (print processor)  7 , a paper ejection part (print processor)  8 , a reception buffer  9 , a job table  10 , a display operation control part  11 , a display panel  12 , and an operation button (job cancellation inputter)  13 . The RIP (raster image processor) part  5  command-analyzes and converts print data to image data, and in doing so, creates and stores a print queue in a print queue table  14 . The image data command-analyzed and created by the RIP part  5  are expanded in a not-shown image memory. 
         [0053]    The host device  2  converts the print data created according to the application to print data (PDL (page description language) data) by means of the printer driver and sends them to the printer  1 . The reception part  3  of the printer  1  receives the print data supplied from the host device  2  and notifies the control part  4  of information such as the job ID, document name, total number of print sheets included in the print data. Here, the print data further include information such as color/monochrome printing and double sided/single sided printing in addition to the above information. Furthermore, the reception part  3  writes the received print data in the reception buffer  9  in sequence. 
         [0054]    Receiving the notice from the reception part  3 , the control part  4  stores the above information in the job table  10 .  FIG. 2  is an illustration showing the structure of the job table  10 . The job table  10  consists of storage areas “job ID,” “document name,” “total number of print sheets,” “remaining number of print sheets,” “reception buffer address,” and “job status” under each record number. Information on the job ID, document name, and total number of print sheets is stored in the corresponding storage areas. 
         [0055]    Here, the storage area “job ID” stores, for example, an identification code given to each print job, the storage area “document name” stores information on the document name of the job ID, and the storage area “total number of print sheets” stores the total number of pages of the print data. Furthermore, the storage area “remaining number of print sheets” stores the remaining number of print sheets calculated by subtracting the number of sheets ejected from the total number of print sheets of the corresponding print data. 
         [0056]    Furthermore, the storage area “reception buffer address” stores information on the address in the reception buffer  9  where the corresponding print data are stored. Furthermore, the storage area “job status” stores the job status of the corresponding print job; the job status to be stored can be, for example, “receiving,” “printing,” or “in RIP (image data conversion in progress).” 
         [0057]    Here, in the initial state of the job table  10 , as shown in  FIG. 2 , the storage areas “job ID” are all reset to “empty,” the storage areas “document name” are all reset to “none,” the storage areas “total number of print sheets” are all reset to “0,” the storage areas “remaining number of print sheets” are all reset to “4,” the storage areas “reception buffer address” are all reset to “0,” and the storage areas “job status” are all reset to “none.” 
         [0058]    Receiving a reception start signal from the reception part  3 , the control part  4  searches the job table  10  in sequence from the record number 1 and writes information of the job ID, document name, and total number of print sheets of the print data in the storage areas of the first record number of which the storage area “job ID” is “empty.” 
         [0059]    The RIP part  5  reads the print data from the reception buffer  9  according to instruction from the control part  4 , and command-analyzes and converts them to image data. The image data converted by the RIP part  5  are expanded in a not-shown image memory. Furthermore, the print queue created concurrently is stored in the print queue table  14 .  FIG. 3  is a conceptual illustration of the print queue table  14  and  FIG. 4  is an illustration showing the data structure of the print queue table  14 . 
         [0060]    The print queue table  14  consists of storage areas “job ID,” “current page number,” “image memory address,” “drawing state,” and “job cancelation information” under each record number. 
         [0061]    The storage area “job ID” stores, for example, an identification code given to each print job as described above. Furthermore, the storage area “current page number” stores the page number in the process of RIP processing among the corresponding print data. Furthermore, the storage area “image memory address” stores information on the address of the image area where the image data of the corresponding page is expanded. 
         [0062]    Furthermore, the storage area “drawing state” stores the progress of drawing processing on the corresponding print data, such as “drawing” and “drawing completed.” Furthermore, the storage area “job cancelation information” stores information indicating that job cancellation is ordered. 
         [0063]    Here, as shown in  FIG. 4 , in the initial state of the print queue table  14 , the storage areas “job ID” are all reset to “empty,” the storage areas “current page number” and “image memory address” are all reset to “0,” and the storage areas “drawing state” and “job cancellation information” are all reset to “none.” 
         [0064]    Therefore, in the initial state, as shown in  FIG. 5 , the number of print queues created is “0,” the new print queue writing position is “1” (the record number 1), the print queue reading position for transfer is also “1” (the record number 1), and the print queue reading position for paper ejection is also “1” (the record number 1). 
         [0065]    Here, the transfer part  6  reads image data from the image memory and transfers the image data to the printer engine  7 . The printer engine  7  outputs image data to a storage medium (for example, paper) based on the image data transferred from the transfer part  6 . Furthermore, the paper ejection part  8  ejects the paper on which print is made by the printer engine  7  onto a not-shown paper tray and notifies the control part  4  that the paper is ejected. 
         [0066]    Specific processing/operation with the above configuration will be described hereafter. 
         [0067]    It is assumed in explaining the processing/operation of this embodiment that the job table  10  already has the information shown in  FIG. 6  stored. For example, the storage areas under the record number 1 store print job information of which the “job ID” is “J0004,” “document name” is “Price List,” and “total number of print sheets” is “9” (nine sheets). The “job status” of this print job is currently “printing.” The conversion to image data by the RIP part  5  has already been completed and the “remaining number of print sheets” is “7” (seven sheets). 
         [0068]    Furthermore, the storage areas under the record number 2 store print job information of which the “job ID” is “J0005,” “document name” is “Layout Diagram,” and “total number of print sheets” is “1” (one sheet). The “job status” of this print job is also “printing.” The conversion to image data by the RIP part  5  has already been completed and the “remaining number of print sheets” is “1” (one sheet); no printout has been made. 
         [0069]    On the other hand, the storage areas under the record number 3 store print job information of which the “job ID” is “J0006,” “document name” is “Meeting Material,” and “total number of print sheets” is “14” (14 sheets). The “job status” of this print job is “in RIP.” The conversion to image data by the RIP part  5  has started and the print data remains in the reception buffer  9 . More specifically, the print data are stored in the reception buffer  9  from the start address “0x8000A064” stored in the “reception buffer address.” 
         [0070]    Furthermore, the storage areas under the record number 4 store print job information of which the “job ID” is “J0007,” “document name” is “Budget Proposal,” and “total number of print sheets” is“5” (five sheets). The “job status” of this print job is “receiving”; the reception by the reception part  3  is in progress. More specifically, the print data are being stored in the reception buffer  9  from the start address “0x8000CB18” stored in the “reception buffer address.” 
         [0071]    Here, at the time of starting the processing of this embodiment, the other record (the record number 5) in the job table  10  is in the initial state. 
         [0072]    Like the above job table  10 , it is assumed that the print queue table  14  already has the data shown in  FIG. 7  stored. For example, the storage areas under the record number 1 store information on the page 9 (the “current page number” is “9”) of which the “Job ID” is “J0004.” The image data of the page 9 has been drawn from the information in the “drawing state,” and expanded in an image memory from the start address “0x8081012C” from the information in the “image memory address.” 
         [0073]    Furthermore, for example, the storage areas under the record number 2 store information on the page 1 (the “current page number” is “1”) of which the “Job ID” is “J0005,” which is completely drawn from the information in the “drawing state,” and expanded in an image memory from the start address “0x80C10140” from the information in the “image memory address.” 
         [0074]    Furthermore, for example, the storage areas under the record numbers 3 to 7 store information on the pages 1 to 5 (the “current page number” is “1,” “2,” . . . , and “5”) of which the “Job ID” is “J0006.” The pages 1 to 4 are completely drawn and the page 5 is currently in drawing from the information in the “drawing state.” They are expanded in an image memory from the start address “0x81010154” from the information in the “image memory address.” 
         [0075]    Here, the storage areas under the record numbers 8 and 9 are not used. The storage areas under the record number 10 store information on the page 8 (the “current page number” is “8”) of which the “job ID” is “J0004,” which is completely drawn from the information in the “drawing state” and expanded in an image memory from the start address “0x80400118” from the information in the “image memory address.” 
         [0076]    Therefore, in the above state of the print queue table  14 , as shown in  FIG. 8 , the number of print queues used is “8,” the next writing position is “7” (the record number 7), the next reading position for transfer is “1” (the record number 1), and the next reading position for paper ejection is “10” (the record number 10). 
         [0077]    First, the regular printing procedure with no job cancellation order when the job table  10  and print queue table  14  are in the above-described states will be described.  FIG. 9  is a flowchart for explaining the processing/operation of the reception part  3 .  FIG. 10  is a flowchart for explaining the processing/operation of the control part  4 .  FIG. 11  is a flowchart for explaining the processing/operation of the RIP part  5 .  FIG. 12  is a flowchart for explaining the processing/operation of the transfer part  6 .  FIG. 13  is a flowchart for explaining the processing/operation of the paper ejection part  8 . 
         [0078]    First, the reception part  3  determines whether print data are received from the host device  2  connected to the network (Step (abbreviated to S, hereafter)  1 ) according to the flowchart shown in  FIG. 9 . The reception part  3  waits until print data are received (NO in S 1 ). Receiving print data (YES in S 1 ), the reception part  3  extracts job information included in the print data (S 2 ). This process is a process to extract information such as the aforementioned job ID, document name, and total number of print sheets included in the received print data. 
         [0079]    Then, the reception part  3  notifies the control part  4  of print data reception start (S 3 ). In other words, the reception part  3  outputs a reception start notice for obtaining approval for reception start to the control part  4  and waits for a reception start approval response from the control part  4  (S 4 ). 
         [0080]    Receiving the reception start notice from the reception part  3 , the control part  4  starts the procedure according to the flowchart shown in  FIG. 10  and first determines whether there is a notice from an external source (S 5 ). In this case, receiving the reception start notice (YES in S 5 ), the control part  4  makes reservation in the reception buffer  9  (S 6 ) and conducts registration in the job table  10  (S 7 ). In other words, the control part  4  reserves a storage area for the print data in the reception buffer  9  and registers the job information extracted from the print data in the job table  10 . 
         [0081]    Subsequently, the control part  4  makes a reception start approval response to the reception part  3  (S 8 ). Receiving the reception start approval response from the control part  4  (YES in S 4 ), the reception part  3  starts receiving print data and stores the input print data in the reception buffer  9  in sequence (S 9 ). 
         [0082]    After making a reception start approval response to the reception part  3 , the control part  4  determines whether the RIP processing is available (S 10 ). This determination is made with reference to the storage area “job status” in the job table  10  shown in  FIG. 6 . For example, in the case of information “in RIP” being stored under the record number 3, no RIP processing is conducted on new print data (NO in S 10 ). On the other hand, in the case of the information “in RIP” not being stored in the storage area “job status” under any record number, the control part  4  updates the job table  10  (S 11 ) and notifies the RIP part  5  to start RIP processing (S 12 ). In such a case, the information “in RIP” is stored in the storage area “job status” under the record number on which the RPI processing starts. 
         [0083]    Notified from the control part  4  to start RIP processing (YES in S 13 ), the RIP part  5  sets the “current page” to 1 (S 14 ) and determines whether there are any unprocessed RIP data (S 15 ) according to the flowchart shown in  FIG. 11 . More specifically, the RIP part  5  determines whether there are any unread data (unprocessed RIP data). Here, if there are no unprocessed RIP data (NO in S 15 ), the RIP part  5  notifies the control part  4  that the RIP processing is completed (S 16 ). On the other hand, if there are any unprocessed RIP data (YES in S 15 ), the RIP part  5  reserves a print queue (S 17 ). 
         [0084]    In the example shown in  FIG. 6 , the print job stored under the record number 4 is in the process of receiving. Then, a print queue is reserved, an image memory is also reserved (S 18 ), the print queue table  14  is updated (S 19 ), the print data are read from the reception buffer  9 , and the RIP processing starts (S 20 ). Then, it is determined whether image data for one page are completed (S 21 ). If image data for one page are not completed (NO in S 21 ), the RIP processing is repeated (S 20  and S 21 ). 
         [0085]    Subsequently, if image data for one page are completed (YES in S 21 ), the print queue table  14  is updated (S 22 ) and the “current page” is incremented (+1) (S 23 ). Then, it is determined whether there are any unprocessed RIP data (S 15 ). It there are any unprocessed RIP data (YES in S 15 ), the above processing (S 17  to S 23 ) is repeated. If there is no print data left in the reception buffer  9  (NO in S 15 ), the control part  4  is notified that the RIP processing is completed (S 16 ). 
         [0086]    Receiving the RIP processing completion notice from the RIP part  5  (YES in S 5 ), the control part  4  releases the reception buffer  9  (S 24 ) and updates the job table  10  (S 25 ). 
         [0087]    For example, in the example shown in  FIG. 6 , receiving the notice of completion of RIP processing on the “job ID” of “J0006” under the record number 3, the control part  4  releases the storage area in the reception buffer  9  where the print data of the print job are stored and updates the “job status” to “printing.” Furthermore, receiving the notice of completion of RIP processing on the “job ID” of “J0007” under the record number 4, the control part  4  releases the storage area in the reception buffer  9  where the print data of the print job are stored and updates the “job status” to “in RIP” and to “printing” in turn. 
         [0088]    Then, it is determined whether there is any print job in the process of receiving (S 26 ). If there is any print job in the process of receiving (YES in S 26 ), the job table  10  is updated (S 27 ) and the RIP part  5  is notified to start RIP processing (S 28 ). For example, in the example shown in  FIG. 6 , as new print data are entered from the host device  2  and new print job information is entered in the available areas under the record number 5, the new print job information is written in the job table  10  and the RIP part  5  is notified to start RIP processing. 
         [0089]    As print information is created in the print queue table  14  and one or more print queues are created (YES in S 29 ), the transfer part  6  makes reference to the storage area “drawing state” in the print queue table shown in  FIG. 7  and determines whether it is “drawing completed” (S 30 ) according to the flowchart shown in  FIG. 12 . For example, in the example shown in  FIG. 7 , the storage area “drawing state” under the record numbers 1 to 6 is “drawing completed” (YES in S 30 ); then, the print queue table  14  is updated so that the corresponding storage area “drawing state” is updated to “transfer” (S 31 ). Then, the image data expanded in a not-shown image memory are transferred to the printer engine  7  (S 32 ), and the printer engine  7  makes printout on paper based on the image data. 
         [0090]    Subsequently, the transfer part  6  releases the image memory in which the corresponding image data are expanded (S 33 ), updates the print queue table (S 34 ), and updates the print queue state (S 35 ). 
         [0091]    On the other hand, as print information is created in the print queue table  14  and one or more print queues are created (YES in S 36 ), the paper ejection part  8  makes reference to the storage area “drawing state” in the print queue table shown in  FIG. 7  and determines whether it is set to “transfer” (S 37 ) according to the flowchart shown in  FIG. 13 . For example, as the transfer part  6  starts transfer and there is a print queue having the storage area “drawing state” set to “transfer” (YES in S 37 ), the paper ejection part  8  waits for a print paper ejection notice from the printer engine  7  (S 38 ). Subsequently, as the printer engine  7  completes printout on paper and a print paper ejection notice is issued (YES in S 38 ), the print queue table  14  is updated (S 39 ), the print queue state is updated (S 40 ), and the control part  4  is notified that the paper ejection is completed (S 41 ). 
         [0092]    Receiving the paper ejection completion notice from the paper ejection part  8  (YES in S 5 ), the control part  4  calculates the remaining number of sheets (S 42 ). This process is a process to calculate the remaining number of print sheets of the corresponding print job. 
         [0093]    The data in the “remaining number of print sheets” shown in  FIG. 6  are decremented (−1) and the corresponding storage area “remaining number of print sheets” is updated (S 43 ). For example, for the print data having the “job ID” of “J0004” shown in  FIG. 6 , the current data in the storage area “remaining number of print sheets” are decremented by 1 so as to update to “6” from a current value “7.” 
         [0094]    Subsequently, it is determined whether the remaining number of sheets is 0 as a result of the above processing (S 44 ). If the corresponding storage area “remaining number of print sheets” is “0” (YES in S 44 ), the print job of the corresponding recording number is deleted (S 45 ). For example, as the print data having the “job ID” of “J0004” shown in  FIG. 6  are further transferred and the data in the storage area “remaining number of print sheets” become “0,” the data of the print job of the record number 1 are deleted. 
         [0095]    The regular printing procedure is described above. The printing procedure in which a job cancelation order is made will be described hereafter. 
         [0096]      FIGS. 14 and 15  are flowcharts for explaining the processing/operation of the control part  4 .  FIGS. 16 and 17  are flowcharts for explaining the processing/operation of the RIP part  5 .  FIG. 18  is a flowchart for explaining the processing/operation of the transfer part  6 .  FIG. 19  is a flowchart for explaining the processing/operation of the paper ejection part  8 .  FIG. 20  is a flowchart for explaining the processing/operation of the display operation control part  11 . 
         [0097]    Here, it is assumed again that the job table  10  has the print job information shown in  FIG. 6  stored and the print queue table  14  has the print queue shown in  FIG. 7  created. 
         [0098]    As described above, the reception part  3  waits for reception of print data from the host device  2  connected to the network, extracts job information included in the print data upon receiving the print data, notifies the control part  4  of reception start, and waits for reception start approval from the control part  4 . 
         [0099]    Receiving the reception start notice from the reception part  3 , the control part  4  first determines whether there is a notice from an external source (Step (abbreviated to ST, hereafter)  1 ) according to the flowchart shown in  FIG. 14 . Here, receiving the reception start notice, the control part  4  make reservation in the reception buffer  9  (ST 2 ) and conducts registration in the job table  10  (ST 3 ) as described above. In other words, the control part  4  reserves a storage area for the print data in the reception buffer  9  and registers the job information extracted from the print data in the job table  10 . 
         [0100]    Subsequently, the control part  4  makes a reception start approval response to the reception part  3  (ST 4 ). Receiving the reception start approval response from the control part  4 , the reception part  3  stores the print data in the reception buffer  9  in sequence. 
         [0101]    After making a reception start approval response to the reception part  3 , the control part  4  determines whether RIP processing is available (ST 5 ). This determination is made with reference to the storage area “job status” in the job table  10  shown in  FIG. 6  as described above. For example, in the case of information “in RIP” being stored under the record number 3, no RIP processing is conducted on new print data (NO in ST 5 ). On the other hand, in the case of the information “in RIP” not being stored in the storage area “job status” under any record number, the control part  4  updates the job table  10  (ST 6 ) and notifies the RIP part  5  to start RIP processing (ST 7 ). 
         [0102]    The RIP part  5  determines whether there is a RIP pause notice from the control part  4  (C in the flowchart shown in  FIG. 16  and ST 8  in the flowchart shown in  FIG. 17 ). If there is a RIP pause notice (YES in ST 8 ), the RIP part  5  pauses the RIP processing and notifies the control part  4  that the RIP pause is completed (ST 9 ). The RIP pause notice is a notice output from the control part  4  when a job cancellation order described above is issued. The RIP part  5  pauses the ongoing RIP processing, conducts a series of processing described later (ST 10  to ST 12 ), and waits for a RIP unpause notice from the control part  4  (ST 13 ). 
         [0103]    Therefore, unless there is a RIP pause notice (unless a job cancellation order is issued), a RIP processing start notice from the control part  4  is waited (NO in ST 8 , ST 14 ), and if a RIP processing start notice is issued (YES in ST 14 ), the “current page” is set to 1 (ST 15 ) and it is determined whether there are unprocessed RIP data (ST 16 ) as described above. Here, if there are unprocessed RIP data (YES in ST 16 ), it is confirmed again that there is no RIP pause notice (job cancellation order) (NO in ST 8 ), the print queue table  14  is reserved (ST 17 ), and the area of the image memory for expansion is reserved (ST 18 ). 
         [0104]    Subsequently, it is determined whether to unpause the RIP (ST 19 ). If there is no RIP unpause (YES in ST 19 ), the storage area “job cancellation information” of the print queue table  14  is set to “none” (is maintained “none”) (ST 20 ), the print data are read from the reception buffer  9 , and the same RIP processing as described above is conducted (ST 21  to ST 25 ). Subsequently, after all unprocessed RIP data are converted to image data (NO in ST 16 ), the control part  4  is notified that the RIP processing is completed (ST 26 ). 
         [0105]    On the other hand, receiving the RIP processing completion notice from the RIP part  5  (YES in ST 1 ), the control part  4  releases the reception buffer  9  (ST 27 ) and updates the job table  10  (ST 28 ) as described above. Subsequently, the control part  4  determines whether there is a print job in the process of receiving (ST 29 ). If there is a print job in the process of receiving (YES in ST 29 ), the control part  4  updates the job table  10  (ST 30 ) and notifies the RIP part  5  to start RIP processing (ST 31 ). 
         [0106]    The transfer part  6  determines whether there is a printing pause notice from the control part  4  (ST 32 ). If there is a printing pause notice (YES in ST 32 ), the transfer part  6  pauses the printing, notifies the control part  4  that the printing pause is completed (ST 33 ), and waits for a printing unpause notice from the control part  4  (ST 34 ). This printing pause notice is also a notice sent from the control part  4  when a job cancellation order described later is issued. If there is no printing pause notice, as described above, printing information is created in the print queue table  14  and if one or more print queues are created (YES in ST 35 ), it is confirmed again that there is no printing pause notice from the control part  4  (NO in ST 36 ) and the storage area “drawing state” shown in  FIG. 7  is referred to determine whether it is set to the “drawing completed” (ST 39 ), which is followed by the same processing as described above (ST 40  to ST 45 ). 
         [0107]    The paper ejection part  8  determines whether a paper ejection completion response request is made by the control part  4  (ST 46 ). If a paper ejection completion response request is made (YES in ST 46 ), the paper ejection part  8  makes a paper ejection completion response to the control part  4  (ST 47 ). This paper ejection completion response request is made when a job cancellation order described later is issued. If no paper ejection completion response request is made, as described above, print information is created in the print queue table  14  and if one or more print queues are created (YES in ST 48 ), it is confirmed again that no paper ejection completion response request is made by the control part  4  (NO in ST  49 ), and the storage area “drawing state” shown in  FIG. 7  is referred to determine whether it is set to “transfer” (ST 51 ). Then, it is confirmed whether the storage area “job cancellation information” is not set to “execution” (ST 52 ). 
         [0108]    Then, as described above, a print paper ejection notice from the printer engine  7  is waited (ST 53 ). If there is a print paper ejection notice (YES in ST 53 ), the print queue table  14  is updated (ST 54 ), the print queue state is updated (ST 55 ), and the control part  4  is notified that the paper ejection is completed (ST 56 ) as described above. 
         [0109]    Receiving the paper ejection completion notice from the paper ejection part  8  (YES in ST 1 ), the control part  4  calculates the remaining number of sheets (ST 57 ), updates the job table  10  (ST 58 ), and determines whether the remaining number of print sheets is 0 (ST 59 ) as described above. Then, if the storage area “remaining number of print sheets” is “0” (YES in ST 59 ), the control part  4  deletes the print job of the corresponding record number (ST 60 ). 
         [0110]    On the other hand, if the user operates on the operation button (job cancellation inputter)  13  to issue a job cancellation order during the above processing, an operation signal is sent to the display operation control part  11 . 
         [0111]      FIG. 20  is a flowchart for explaining the processing of the display operation control part  11 . First, the display operation control part  11  determines whether there is a printer pause operation (Step (abbreviated to STP in  FIG. 20 , hereafter)  1 ). In other words, the display operation control part  11  receives an operation signal based on operation on the operation button (job cancellation inputter)  13 , acknowledges a job cancellation order, and determines that there is a printer pause operation (YES in STP 1 ). Then, the display operation control part  11  notifies the control part  4  to pause the printer based on the determination (STP 2 ). 
         [0112]    Receiving the printer pause notice (YES in ST 1 ), the control part  4  determines whether the number of print jobs is 1 or greater (ST 61 ). If the number of print jobs is not 1 or greater (NO in ST 61 ), in other words if the number of print jobs is “0,” there is no point of job cancellation and the control part  4  notifies the display operation control part  11  that the job cancellation is invalid (ST 62 ). The display operation control part  11  displays invalidity of the job cancellation based on the notification from the control part  4  (STP 5 ). 
         [0113]    On the other hand, if the number of print jobs is one or greater (YES in ST 61 ), the control part  4  notifies the RIP part  5  to pause the RIP processing, notifies the transfer part  6  to pause the printing, and requires a paper ejection completion response from the paper ejection part  8  (ST 63 ). 
         [0114]    Receiving the notice (YES in ST 8 ), the RIP part  5  pauses the ongoing RIP processing and notifies the control part  4  that the RIP pause is completed (ST 9 ) as described above. Subsequently, the RIP part  5  waits for a RIP unpause notice from the control part  4  (ST 13 ). 
         [0115]    Furthermore, receiving the printing pause notice from control part  4  (YES in ST 32  or YES in ST 36 ), the transfer part  6  pauses the image data transfer and notifies the control part  4  that the printing pause is completed (ST 33  or ST 37 ). Subsequently, the transfer part  6  waits for a printing unpause notice from the control part  4  (ST 34  or ST 38 ). 
         [0116]    Furthermore, receiving the paper ejection completion response request from the control part  4  (YES in ST 46  or YES in ST 49 ), the paper ejection part  8  confirms the print paper ejected and makes a paper ejection completion response to the control part  4  (ST 47  or ST 50 ). 
         [0117]    Receiving the above RIP pause completion response from the RIP part  5 , printing pause completion response from the transfer part  6 , and paper ejection completion response from the paper ejection part  8  (YES in ST 64 ), the control part  4  determines again whether the number of print jobs is one or greater (ST 65 ). If the number of print jobs is one or greater (YES in ST 65 ), the control part  4  updates the job table  10  (ST 66 ), and notifies the display operation control part  11  that the job cancellation is valid (ST 67 ). Here, it is determined again whether the number of print jobs is one or greater because the print job to be cancelled may be completed while the RIP part  5  executes the RIP pause procedure or the transfer part  6  executes the printing pause procedure. 
         [0118]    Notified from the control part  4  that the job cancellation is valid, the display operation control part  11  displays the job information on the display panel  12  (STP 4 ), and waits for an order for or against execution of the job cancellation (STP 6 ). In this case, the display operation control part  11  displays information of the document name of the print job under the record number 1 that is in the process of printing on the display panel  12 , and waits for an order to execute the job cancellation or an order to nullify the job cancellation from the user. 
         [0119]    Subsequently, if the operation button  13  is operated and an order to execute the job cancellation is issued (YES in STP 6 ), the display operation control part  11  notifies the control part  4  to execute the job cancellation (STP 7 ). On the other hand, if an order to nullify the job cancellation is issued (NO in STP 6 ), the display operation control part  11  notifies the control part  4  of nullify the job cancellation (STP 8 ). 
         [0120]    Notified from the display operation control part  11  to execute the job cancellation (YES in ST 68 ), the control part  4  notifies the RIP part  5  to update the print queue (ST 69 ). Receiving the print queue update notice (ST 10 ), the RIP part  5  updates the print queue table  14  (ST 11 ). 
         [0121]    Subsequently, the RIP part  5  notifies the control part  4  that the print queue update is completed (ST 12 ). Receiving the print queue update completion notice (YES in ST 70 ), the control part  4  further updates the job table  10  (ST 71 ). For example, the control part  4  clears the information under the record number 1 of the print job of the document name “Price List” of the “J0004” and moves up the record numbers one by one. 
         [0122]    Then, it is determined whether the “job status” under the record number 1 in the job table  10  is “in RIP” (ST 72 ). In this case, the print job information updated in the above processing is stored in the storage areas under the record number 1. If the “job status” of the print job stored under the record number 1 is in RIP (YES in ST 72 ), the RIP part  5  is notified to unpause the RIP (ST 73 ) and the transfer part  6  is notified to unpause the printing (STP 74 ). 
         [0123]    On the other hand, if the “job status” under the record number 1 is not in RIP (NO in ST 72 ), the job table  10  is searched (S 75 ). If there is any print job of which the “job status” is in RIP (YES in ST 76 ), the RIP part  5  is notified to unpause the RIP (ST 77 ) and the transfer part  6  is notified to unpause the printing (ST 74 ). 
         [0124]    With the above processing, the RIP processing and image data transfer of the print job under the record number 1 after the job cancellation procedure are conducted. In this case, the RIP part  5  updates the print queue table  14  based on the RIP unpause notice (YES in ST 19 ), and sets the storage area “job cancellation information” of the corresponding print job to execution (ST 22 ). 
         [0125]    On the other hand, for the print job to be cancelled, the transfer part  6  releases the image data in the image memory (ST 43 ) without transferring the image data of the print job from the image memory (YES in ST 41 ). 
         [0126]    Furthermore, for the print job to be cancelled, the paper ejection part  8  notifies the control part  4  that the paper ejection is completed (ST 54  to ST 56 ) without waiting for a print paper ejection notice from the printer engine  7  (YES in ST 52 ). 
         [0127]    The above processing is the basic processing to execute job cancellation. Embodiment 1 of this embodiment will be described hereafter. 
         [0128]      FIG. 21  is an illustration showing the system configuration of this embodiment, which is basically the same as the system configuration described with reference to  FIG. 1  except that a job-ID-upon-cancel-operation storage  15  is added. In other words, the printer  1  is connected to the host device  2  via a network such as a LAN, and composed of the reception part  3 , control part  4 , RIP part  5 , transfer part  6 , printer engine  7 , paper ejection part  8 , reception buffer  9 , job table  10 , display operation control part  11 , display panel  12 , operation button  13 , print queue table  14 , and job-ID-upon-cancel-operation storage  15 . The job-ID-upon-cancel-operation storage  15  stores information on the print job ID when the operation button  13  is operated for (operation for) job cancellation. Details will be given hereafter. 
         [0129]      FIGS. 22 and 23  are flowcharts for explaining the processing/operation of the control part  4 .  FIG. 24  is a flowchart for explaining the processing/operation of the display operation control part  11 . Here, the flowchart shown in  FIG. 22  is the above-described flowchart shown in  FIG. 14  plus the processing of this embodiment, the flowchart shown in  FIG. 23  is the above-described flowchart shown in  FIG. 15  plus the processing of this embodiment, and the flowchart shown in  FIG. 24  is the above-described flowchart shown in  FIG. 20  plus the processing of this embodiment. Therefore, the processes in  FIGS. 22 ,  23 , and  24  that are the same as those in the corresponding figure are referred to by the same reference numbers and their explanation will be omitted. 
         [0130]    As described above, as the operation button  13  is operated and an operation signal is entered into the display operation control part  11 , the display operation control part  11  acknowledges a job cancellation order based on the operation signal from the operation button  13  and notifies the control part  4  to pause the printer (YES in STP 1 , STP 2 ). 
         [0131]    Notified from the display operation control part  11  to pause the printer (YES in ST 1 ), the control part  4  determines whether the number of print jobs is one or greater (ST 61 ) and if the number of print jobs is one or greater (YES in ST 61 ), notifies the RIP part  5  to pause the RIP processing, notifies the transfer part  6  to pause the printing, and requests a paper ejection completion response from the paper ejection part  8  (ST 63 ) as described above. Furthermore, in this embodiment, the control part  4  stores information on the print job ID of which the printing is in progress in the job-ID-upon-cancel-operation storage  15  (ST 63 - 1 ). For example, if the print job ID of which the printing is in progress at the time is “J0004” (the document name “Price List”) shown in  FIG. 6 , the control part  4  stores the print job ID “J0004” in the job-ID-upon-cancel-operation storage  15 . Furthermore, if the print job ID of which the printing is in progress is “J0005” (the document name “Layout Diagram”), the control part  4  stores the print job ID “J0005” in the job-ID-upon-cancel-operation storage  15 . 
         [0132]    On the other hand, receiving the RIP pause notice, the RIP part  5  immediately notifies the control part  4  that the RIP pause is completed if there is no ongoing RIP processing. On the other hand, the RIP part  5  completes the ongoing RIP processing for a page and notifies the control part  4  that the RIP pause is completed if there is any ongoing RIP processing. Subsequently, the RIP part  5  waits for a RIP unpause notice from the control part  4 . 
         [0133]    Furthermore, notified from the control part  4  to pause the printing, the transfer part  6  pauses the image data transfer if there is no ongoing transfer, or completes the ongoing image data transfer if there is any ongoing transfer, and notifies the control part  4  that the printing pause is completed. Subsequently, the transfer part  6  waits for a printing unpause notice from the control part  4 . 
         [0134]    Furthermore, receiving a paper ejection completion response request from the control part  4 , the paper ejection part  8  makes a paper ejection completion response to the control part  4  when the paper ejection part  8  is not currently in wait for print paper ejection from the printer engine. On the other hand, the paper ejection part  8  makes a paper ejection completion response to the control part  4  after waiting for a print paper ejection notice from the printer engine for all queues of which the drawing state is “transfer” in the print queue when the paper ejection part  8  is currently in wait for print paper ejection. 
         [0135]    Receiving the RIP pause completion response from the RIP part  5 , printing pause completion response from the transfer part  6 , and paper ejection completion response from the paper ejection part  8  (YES in ST 64 ), the control part  4  determines again whether the number of print jobs is one or greater (ST 65 ). If the number of print jobs is one or greater (YES in ST 65 ), the control part  4  updates the job table  10  (ST 65 ), and determines whether the current print job ID is equal to the print job ID stored in the job-ID-upon-cancel-operation storage  15  (ST 67 - 1 ). Here, if the print job IDs are equal (YES in ST 67 - 1 ), the control part  4  notifies the display operation control part  11  that the job IDs are equal and the job cancellation is valid (ST 67 - 2 ). On the other hand, if the job IDs are not equal (NO in ST 67 - 1 ), the control part  4  notifies that the job cancellation is valid but the job IDs are not equal (ST 67 - 3 ). 
         [0136]    The display operation control part  11  waits for the above notice from the control part  4  (STP 3 ). Receiving the notice from the control part  4  (YES in STP 3 ), the display operation control part  11  displays invalidity of the job cancellation if the job cancellation is invalid (STP 5 ). 
         [0137]    On the other hand, receiving the notice that the print job IDs are equal and the job cancellation is valid from the control part  4 , the display operation control part  11  conducts regular job information display (STP 4 - 1 ) and waits for an order for or against execution of the job cancellation (STP- 6 ). 
         [0138]      FIG. 25A  shows an example of the above display, displaying information on the job ID and document name on which the job cancellation order is issued. For example, in the example of the figure, information on the print job “J0004” (the document name “Price List”) is displayed and “x cancel (reset)” is also displayed. Seeing this display, the user can easily confirm that the print job to be cancelled is the print job specified. Therefore, the user who saw the display presses a button “double-circle” to execute the print job (YES in STP 6 , STP 7 ) or presses a button “x” to cancel the print job (YES in STP 6 , STP 8 ). 
         [0139]    On the other hand, in the case of being notified from the control part  4  that the job cancellation is valid butnd the job ID stored in the job-ID-upon-cancel-operation storage  15  is not equal to the current job ID, the display operation control part  11  conducts irregular job information display on the display panel  12  (STP 4 - 2 ) and waits for an order for or against execution of the job cancellation (STP 6 ). 
         [0140]      FIG. 25B  shows an exemplary display of the above case, displaying the job ID and document name on which the job cancellation order is issued and a message to call attention. For example, in the example of  FIG. 25B , information on the print job having the job ID “J0004” and the document name “Price List” is displayed, “x cancel (rest)” is also displayed, and “[ATTENSION] Please confirm the job to cancel” is displayed. Seeing the display, the user can easily recognize from the display that the print job to be cancelled is not the print job specified. Then, the user who saw the display presses the button “x” if he/she wants to cancel the print job (YES in STP 6 , STP 8 ) 
         [0141]    The above-described processing can prevent, for example, the user who is familiar with the job cancellation operation from conducting the second panel operation without checking the job to be cancelled well. 
         [0142]    The above-described display shown in  FIG. 25B  is a display for announcing that the print job to be canceled does not match. Other than the above-described display, for example, display blinking or different in color can be used. Furthermore, display in boldface or in different font or the above-described display with attention-calling sound can be used. 
         [0143]    Embodiment 2 of the present invention will be described hereafter. 
         [0144]      FIG. 26  is an illustration showing the system configuration of this embodiment, which is basically the same as the system described with reference to  FIG. 1  except that a number-of-jobs-upon-cancel-operation storage  16  shown in the figure is added. In other words, the printer  1  of this embodiment is also connected to the host device  2  via a network such as a LAN, and composed of the reception part  3 , control part  4 , RIP part  5 , transfer part  6 , printer engine  7 , paper ejection part  8 , reception buffer  9 , job table  10 , display operation control part  11 , display panel  12 , operation button  13 , print queue table  14 , and number-of-jobs-upon-cancel-operation storage  16 . The number-of-jobs-upon-cancel-operation storage  16  used in this embodiment stores the number of print jobs stored in the job table  10  when the user operates the operation button  13 . 
         [0145]      FIGS. 27 and 28  are flowcharts for explaining the processing of this embodiment, explaining the processing of the control part  4 . Here, the flowchart shown in  FIG. 27  is the above-described flowchart shown in  FIG. 14  plus the processing of this embodiment and the flowchart shown in  FIG. 28  is the above-described flowchart shown in  FIG. 15  plus the processing of this embodiment. Therefore, the processes in  FIGS. 27 and 28  that are the same as those in the corresponding figure are referred to by the same reference numbers and their explanation will be omitted. 
         [0146]    As described above, as the operation button  13  is operated and an operation signal is entered into the display operation control part  11 , the display operation control part  11  acknowledges a job cancellation order based on the operation signal from the operation button  13  and notifies the control part  4  to pause the printer. 
         [0147]    Notified from the display operation control part  11  to pause the printer (YES in ST 1 ), the control part  4  determines whether the number of print jobs is one or greater (ST 61 ), and if the number of print jobs is one or greater (YES in ST 61 ), notifies the RIP part  5  to pause the RIP processing, notifies the transfer part  6  to pause the printing, and requests a paper ejection completion response from the paper ejection part  8  (ST 63 ) as described above. Furthermore, in this embodiment, the control part  4  stores information on the number of print jobs of which the processing is currently in progress in the number-of-jobs-upon-cancel-operation storage  16  (S 63 - 2 ). 
         [0148]    On the other hand, receiving the RIP pause notice, the RIP part  5  immediately notifies the control part  4  that the RIP pause is completed if there is no ongoing RIP processing. On the other hand, the RIP part  5  completes the ongoing RIP processing for a page and notifies the control part  4  that the RIP pause is completed if there is any ongoing RIP processing. Subsequently, the RIP part  5  waits for a RIP unpause notice from the control part  4 . 
         [0149]    Furthermore, notified from the control part  4  to pause the printing, the transfer part  6  pauses the image data transfer if there is no ongoing transfer, or completes the ongoing image data transfer if there is any ongoing transfer, and notifies the control part  4  that the printing pause is completed. Subsequently, the transfer part  6  waits for a printing unpause notice from the control part  4 . Furthermore, receiving the paper ejection completion response request from control part  4 , the paper ejection part  8  executes the necessary processing and makes a paper ejection completion response to the control part  4 . 
         [0150]    On the other hand, receiving the RIP pause completion response from the RIP part  5 , printing pause completion response from the transfer part  6 , and paper ejection completion response from the paper ejection part  8  (YES in ST 64 ), the control part  4  determines again whether the number of print jobs is one or greater (ST 65 ). If the number of print jobs is one or greater (YES in ST 65 ), the control part  4  updates the job table  10  (ST 66 ), and determines whether there is a record of which the job ID is not empty (ST 67 - 4 ). Here, if the determination (ST 67 - 4 ) results in YES, the control part  4  further determines whether the number of jobs stored in the number-of-jobs-upon-cancel-operation storage  16  is 1 (ST 67 - 5 ). 
         [0151]    Here, if the number of print jobs stored in the number-of-jobs-upon-cancel-operation storage  16  is 1 (YES in ST 67 - 5 ), execution of the job cancellation is immediately determined without executing the above-described processing (ST 67  and/or ST 68 ). In other words, if the number of current print jobs is 1 and the number of jobs stored in the number-of-jobs-upon-cancel-operation storage  16  is 1, the number of print jobs does not change and the job cancellation is executed without further operation by the user. 
         [0152]    With the above processing, the user does not need to operate the operation button  13  again and the target job information can be cancelled with one operation. 
         [0153]    Embodiment 3 of the present invention will be described hereafter. 
         [0154]    This embodiment utilizes the same system configuration as in the above-described  FIG. 21 . Therefore, the printer  1  of this embodiment is also connected to the host device  2  via a network such as a LAN, and composed of the reception part  3 , control part  4 , RIP part  5 , transfer part  6 , printer engine  7 , paper ejection part  8 , reception buffer  9 , job table  10 , display operation control part  11 , display panel  12 , operation button  13 , print queue table  14 , and job-ID-upon-cancel-operation storage  15 . 
         [0155]      FIG. 29  is a flowchart for explaining the processing/operation of the control part  4  in this embodiment. Here, the flowchart shown in  FIG. 29  is the above-described flowchart shown in  FIG. 15  plus the processing of this embodiment. Therefore, the processes in  FIG. 29  that are the same as those in the corresponding figure are referred to by the same reference numbers and their explanation will be omitted. 
         [0156]    As described above, as the operation button  13  is operated and an operation signal is entered into the display operation control part  11 , the display operation control part  11  acknowledges a job cancellation order based on the operation signal from the operation button  13  and notifies the control part  4  to pause the printer. Subsequently, the display operation control part  11  waits for confirmation notice from the control part  4 . 
         [0157]    If the number of print jobs is one or greater, the control part  4  notifies the RIP part  5  to pause the RIP processing, notifies the transfer part  6  to pause the printing, and requests a paper ejection completion response from the paper ejection part  8  as described above. Furthermore, in this embodiment, the control part  4  stores information on the job ID of which the printing is currently in progress in the job-ID-upon-cancel-operation storage  15 . 
         [0158]    On the other hand, receiving the RIP pause notice, the RIP part  5  immediately notifies the control part  4  that the RIP pause is completed if there is no ongoing RIP processing. On the other hand, the RIP part  5  completes the ongoing RIP processing for a page and notifies the control part  4  that the RIP pause is completed if there is any ongoing RIP processing. Subsequently, the RIP part  5  waits for a RIP unpause notice from the control part  4 . 
         [0159]    Furthermore, notified from the control part  4  to pause the printing, the transfer part  6  pauses the image data transfer if there is no ongoing transfer, or completes the ongoing image data transfer if there is any ongoing transfer, and notifies the control part  4  that the printing pause is completed. Subsequently, the transfer part  6  waits for a printing unpause notice from the control part  4 . Furthermore, receiving the paper ejection response request from control part  4 , the paper ejection part  8  executes the necessary processing and makes a paper ejection completion response to the control part  4 . 
         [0160]    On the other hand, receiving the RIP pause completion response from the RIP part  5 , printing pause completion response from the transfer part  6 , and paper ejection completion response from paper ejection part  8 , the control part  4  determines again whether the number of print jobs is one or greater. If the number of print jobs is one or greater, the control part  4  updates the job table  10  (ST 66 ), and determines whether the print job ID stored in the job-ID-upon-cancel-operation storage  15  and current print job ID are equal (ST 67 - 6 ). Here, if the determination (ST 67 - 7 ) results in YES, the control part  4  immediately determines execution of the job cancellation without executing the above-described processing (ST 67  and/or ST 68 ). In other words, the current print job ID and the print job ID stored in the job-ID-upon-cancel-operation storage  15  are equal, the print job to be cancelled does not change, and the job cancellation is executed without further operation by the user. 
         [0161]    With the above processing, the user does not need to operate the operation button  13  again and the target job information can be cancelled with one operation. 
         [0162]    The procedures shown in the flowcharts in the embodiments of the present invention are applicable to various devices by writing them on a storage medium such as a magnetic disc, optical disc, and semiconductor memory as recording control programs that can be realized by a computer. Alternatively, they are applicable to various devices through communication media transfer. The same efficacy as in the case of using the device of the embodiments can be obtained by storing the procedures described in the embodiments on a desired storage medium and executing the recording control programs on another computer or the like. Here, the computer is not confined to a computer installed in the device described in the embodiments and can be any computer capable of reading the recording control programs stored on a storage medium and comprising an operation device such as a CPU executing control operation according to the read recording control programs. 
         [0163]    Several embodiments of the present invention are described above. These embodiments are given by way of example and do not confine the scope of the invention. These novel embodiments can be realized in many different modes and various elimination, replacement, and change can be made without departing from the gist of the invention. These embodiments and their modification fall within the scope and gist of the invention and within the invention set forth in the scope of claims and the scope equivalent thereto. 
         [0164]    Having described and illustrated the principles of this application by reference to one (or more) preferred embodiment(s), it should be apparent that the preferred embodiments may be modified in arrangement and detail without departing from the principles disclosed herein and that it is intended that the application be construed as including all such modifications and variations insofar as they come within the spirit and scope of the subject matter disclosed herein.