JP3509816B2 - Network system and printer server - Google Patents

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a network system and a printer server, and more particularly, it is constituted and includes at least a client terminal device and a printer device which are connected via a network or locally connected. A print job management unit that sequentially controls queuing of print jobs based on a print job request issued from the client terminal device and manages print information of the print job and print job information including print data. The present invention relates to a provided network system and printer server.

[0002]

2. Description of the Related Art Conventionally, a plurality of client terminal devices, a plurality of printers, and a printer server are connected via a network, and the print server controls queuing of print jobs requested by the plurality of client terminal devices. There has been proposed a network system in which the above-mentioned print jobs are executed in an appropriate order by a shared printer.

In addition to this, a high function printer capable of executing the print job queuing control processing by the printer server as described above has been proposed, and printing requested by a plurality of client terminal devices by the high function printer. A network system for controlling queuing of jobs has also been proposed.

[0004]

However, since a plurality of types of shared printers are usually connected to the network system as described above, an operator who issues a print job output request must use the plurality of shared printers. It was necessary to understand the characteristics of, and the load on the operator was heavy.

In order to avoid such a problem, in recent years, a function has been proposed in which a printer server automatically selects an optimum printer according to a print job attribute.

[0006] However, it is generally preferred that the operator selects the printer installed closest to the operator and prints out the printer, and eventually the operator prints to the nearest printer. It is necessary to set detailed information according to the job information and the characteristics of the printer. For this reason, the burden on the operator is increased, and illegal printing that does not suit the operator's intention may occur due to a setting error when setting detailed information in the printer.

On the other hand, in general, an operator who issues a print job often reissues the print job after recognizing a partial correction of information of the print job after the print job is issued. However, after issuing the print request (after the print job has been queued), the system administrator requests the print job to be canceled, or the operator cancels the print job himself and then partially corrects the information. It is necessary to request the output of the print job again. Therefore, the operation becomes complicated and the traffic volume on the network also increases.

Further, when the print job is reissued,
In the network system, since the print job is treated as a new job, there arises a disadvantage that a waiting time occurs again until the output of another job is completed.

For this reason, a priority output function for increasing the priority of a print job and processing it has been proposed, but generally, in order to use these priority print functions, a system administrator is requested to give priority. It is necessary for the operator and the system administrator to perform operations that increase the frequency, which is a troublesome task.

The present invention has been made to solve the above-mentioned problems, and it is possible to change the setting information of a print job requested by a setting error or an operation error even after the print job is queued. An object of the present invention is to provide a network system and a printer server capable of improving the operability of a print job and reducing illegal printing.

[0011]

In order to achieve the above-mentioned object, a network system according to claim 1 has at least a client terminal device connected via a network or locally connected, a printer, and the client terminal. A print job that sequentially controls queuing of print jobs based on a print job request issued by the device, and includes print information set by the client terminal device and print data to be printed by the printer device, which is included in the print job. A network system comprising a printer server for managing job information, wherein the client terminal device has an information displaying unit for displaying information, the print information managed by the printer server, and
Display control means for acquiring the print job information including the print data from the printer server and displaying the acquired print job information on the information display means, and changing the print job information displayed on the information display means And an information notifying unit for notifying the printer server of the changed print job information changed by the information changing unit. The printer server is notified by the information notifying unit. Changed print job information
According to the information , the corresponding print job information is changed.

A network system according to the present invention is
The printer includes a client device connected via a network or locally connected, a printer, and a printer server. The printer server sequentially controls queuing of print jobs based on a print job request issued from the client terminal device. The print job information including print information and print data of the print job is managed (that is, the printer server includes a print job management unit). As described above, when the network system is configured to include the printer server, it is generally desirable to provide the print job management unit in the printer server, and load distribution among the client terminal device, the printer device, and the printer server. Can be achieved.

The print information is information on the output paper size and the reduction / enlargement ratio set in the print job.
It means print control information such as information on the number of copies, print resource information such as form information and font information, and print data means data that is actually printed. The print job information includes both the print information and print data.

In the present invention, the display control means acquires print job information managed by the printer server from the printer server and causes the information display means to display the print job information. This print job information
The information includes print information and print data, and the operator views this print job information and changes it to desired print job information by the information changing means. Then, the changed print job information is notified to the printer server by the information notifying means.

In the printer server that receives the notification of the changed print job information , the information changing unit changes the corresponding print job information according to the changed data (the print job information desired by the operator). This completes the change to the desired print job information .

[0016] In the network system according to the way the present invention, already print request from the client terminal device, the print di- including print information of the print job are controlled queuing and print data in the printer server
The job information can be changed by the operator to desired print job information . As a result, the print information and print data of the print job requested due to a setting error or operation error can be changed even after the print job is queued.
It is no longer necessary to make a print job cancellation request and make a print job output request in which the print information and print data have been partially modified, making it possible to improve the operability of the print job and reduce unauthorized printing.

[0017]

[0018]

The information notifying means is used for printing after the change.
Regarding the print data, when the job information is notified , only the changed portion of the changed print data may be notified to the printer server. In this case, the amount of data transferred from the client terminal device to the printer server can be reduced, and the amount of traffic on the network can be reduced. Further, since the printer server only needs to change the notified changed portion, processing such as extraction of the changed portion from the entire print data becomes unnecessary, and the processing efficiency can be improved.

The above network system is a contract
This can be realized by using the printer server according to claim 5 or claim 6.

By the way, it is desirable that the print job for which the print job information is being changed is put in the output hold state so that the print processing is not executed.

For example, in the network system according to the present invention, the print job management section is further provided with a first hold control means, and the first hold control means outputs a print job whose print job information is being changed to a print hold state. Manage as. At this time, if another print job exists, control is performed so that the other print job is given priority and the processing is executed.

With this, it is possible to prevent the print job from being processed without changing the print job information and causing a print or an unauthorized print that does not suit the operator.

On the other hand, when the print job for which the print job information is to be changed is in the process of printing, it is desirable to immediately stop the print processing of the print job.

For example, in the network system according to the present invention, the print job management unit is further provided with a first stop control unit, and the print job whose print job information is to be changed is being processed by the first stop control unit. In some cases, the print processing of the print job is stopped, and after receiving the change request from the client terminal device, any one of canceling, re-outputting, and continuing the print processing of the print job is performed according to the content of the change request. Control is desirable.

Thus, when the print job for which the print job information is to be changed is under print processing, the print processing of the print job can be immediately stopped. further,
After that, it is possible to automatically and promptly perform the process (any one of canceling the print process, re-outputting, and continuing) according to the process request from the client terminal device.

[0027]

BEST MODE FOR CARRYING OUT THE INVENTION Embodiments of a network system according to the present invention will be described below.

[Configuration of Network System in this Embodiment] In the present invention described above, print information is stored in a non-volatile storage device or volatile according to a print request instruction issued from a plurality of client terminal devices (hereinafter abbreviated as clients). The present invention relates to a network system configured to include a client, a printer server, or a printer that can include a plurality of print job output control units using queuing control using a storage device. The various configurations shown in FIGS.

That is, in the configuration example 1 shown in FIG. 1, the queuing control of the print job is performed by the clients 20A and 20B.
Alternatively, it is executed by any one of the printers 40. When the client and the printer are locally connected to each other, the queuing control is usually performed on the client side.

The configuration example 2 shown in FIG.
This is a configuration example for sharing one printer 40 locally connected to 0 among a plurality of clients 20A and 20B. In such a case, print job queuing control is normally executed by the printer server 30. However, the queuing control can be performed by the clients 20A and 20B and the printer 40.

The configuration example 3 shown in FIG.
This is a configuration example for sharing a printer 40 connected via a plurality of clients 20A and 20B. In such a case as well, as in the configuration example 2, print job queuing control is normally executed by the printer server 30. To be done. However,
It is also possible to perform queuing control with the clients 20A, 20B and the printer 40.

In the embodiment described below, an example will be described in which the printer server 30 controls the queuing of print jobs in the configuration example 3 of FIG. 3 which is most frequently used.

[Structure of Each Device Constituting Network System] As shown in FIG. 4, in the network system 10 of the present embodiment, a plurality of clients 20 and
The printer server 30 and the plurality of printer devices 40 are
They are connected to each other via a local area network (LAN) 12.

(Configuration of Client 20) First, the configuration of the client 20 will be outlined. The client 20
Display 2 for displaying information to the client operator
4, a keyboard 25 for a client operator to select various functions and change information, and a display 24.
A job operation unit 22 that performs various control processes described below related to information display on the keyboard and information input from the keyboard 25, and control that outputs corresponding print data and print information to the printer server 30 in response to a request from the job operation unit 22. And a job output control unit 23 that receives information from the printer server 30 and notifies the job operation unit 22 of the information.
The job control unit 22 and the job output control unit 23 are included in the main control unit 21.

Here, the outline of the processing in the job operating section 22 will be described. The job operation unit 22 roughly executes three types of processing: (1) print data output processing, (2) information display and selection processing, and (3) print data editing processing.

(1) Print data output processing ・ Perform the print job output request acceptance process from the operator.

At the same time as the print job output request, a process of accepting attribute information to be set in the print job (paper size, reduction information, etc.) is performed.

At the same time as the print job output request, the resource information set in the print job is received (form, font information, etc.).

(2) Information display and selection processing-Processing for displaying job information queued in the printer server 30.

Control processing for selecting a job to be replaced, a job to be edited, or a job to be canceled from the displayed job information is performed.

(3) Processing for editing print data-Control processing for displaying and editing print data transferred from the printer server is performed.

1. Edit print attribute information (edit information such as paper size and reduction information) 2. Editing print resource information (editing forms, images, font information, etc.) 3. Editing Print Data (Editing Print Data to be Actually Printed) (Configuration of Printer Server 30) Next, the configuration of the printer server 30 will be outlined. As shown in FIG. 4, the printer server 30 includes a main control unit 31, a data input control unit 32, a data transmission / reception unit 33, a job management unit 34, a data output control unit 35, a data output unit 36, and a non-volatile storage device. It is configured to include a spool 3B and a memory (not shown) that stores various tables. The various tables may be stored in the spool 3B.

Of these, the main control unit 31 is a control unit for performing start / stop processing of other control units such as the data input control unit 32 and the job management unit 34, and the data input control unit 32 is
It is a control unit that performs start / stop processing of the data transmission / reception unit 33 corresponding to the request from the client 20 on a one-to-one basis. In the start / stop processing of the data transmitter / receiver 33,
A data transmission / reception unit management table 37 of FIG. 15 described later is used.

The data transmitter / receiver 33 is connected to the client 20.
17 is a control unit that performs communication control processing with the storage unit 3100 and stores print data in the spool 3B and manages / operates jobs in cooperation with the job management unit 34. File management table 3
Use 8. It should be noted that a plurality of the data transmission / reception units 33 are activated according to the number of requests from the client 20.

The job management section 34 includes a data transmission / reception section 33.
The information of each print job input by is collectively managed by the job management table 39 of FIG. 14 described later. That is, in the job management unit 34, the job management table 3
9 is used to perform print job output scheduling processing. The job management unit 34 also controls and manages the data output unit 36 as necessary.

The data output control unit 35 will be described later with reference to FIG.
The data output unit management table 3A is used to start / stop the data output unit 36. In addition, the data output unit 36
Outputs the print jobs scheduled by the job management unit 34 to the target printer 40 in sequence.
The data output unit 36 includes a data output control unit 3 for each printer 40 registered in advance in the printer server 30.
5, a plurality of them are activated.

[Outline of Various Management Tables] Here, the job management table 39 shown in FIGS.
The outline of the data transmitting / receiving unit management table 37, the data output unit management table 3A, and the file management table 38 will be described.

The job management table 39 shown in FIG.
This is a table used by the job management unit 34 to manage print jobs requested by the client 20.
Each information field shown in FIG. 14 will be described.

The job ID is a job number internally set for the job received by the printer server 30, and this job ID information is used as interface information when canceling the job from the client 20 or using the editing function. It

In the job input date / time field,
The date / time information when the print job is input to the printer server 30 is set.

Job status information in the printer server 30 is set in the job status field. Within the printer server 30, print jobs are managed in the following four states.

-Waiting for printing = Waiting for data output to the printer-During printing = Current status of the job being processed-Holding = Unable to output due to an error during the output processing of the job-Under editing = The job In the field of the status queue information currently edited on the client, for example, a lock (a status in which the job is not output in the output hold status) is set as the handling information on the output queue.

In the client information field, IP address information of the client 20 is set as information for identifying the client 20 that issued the print request.

In addition, the file name of the print data is set in the print file name field, and the date / time information when the print data file was created by the client 20 is set in the file creation date / time field. It Output page range information of print data is set in the output page range field, and paper size, print orientation, enlargement / reduction rate, N-up (= N pages) set in the print data are set in the print attribute information field. Minute data is reduced and recorded on one sheet), number of copies,
Attribute information such as double-sided single-sided printing, paper feed information, discharge port information, and color / monochrome information is set.

In the print resource information field, print resource information such as font information, form information, image / graphic information set in the print data is set, and in the process information field, the job status is held. The reason information for becoming is set.

The data transmission / reception unit management table 37 shown in FIG. 15 is a table used by the data input control unit 32 to perform start / stop management processing of the data transmission / reception unit 33, and data input in the process ID field. The process ID information obtained by the data transmission / reception unit activation process activated by the control unit 32 is set, and the time information of the activation of the data transmission / reception unit 33 is set in the field of the activation start time (however, activation start The time information is not used by the printer server 30).

Data output section management table 3 shown in FIG.
A is a table used by the data output control unit 35 for performing the start / stop management process of the data output unit 36, and the process ID field indicates the data output unit start process started by the data output control unit 35. The obtained process ID information is set, and the time information when the data output unit 36 is activated is set in the activation start time field (however, the activation start time information is the printer server 3).
0 is not particularly used).

The file management table 38 shown in FIG.
Is a table used by the data transmission / reception unit 33 and the data output unit 36 to manage the actual data of the print job managed in the printer server 30, and the job ID field is set by the job management unit 34 in the job ID field. The job ID information is set when the job is registered, and the start point of the actual data portion of the job ID is set in the start point field.

[Outline of data format when issuing various requests]
Here, the data formats at the time of issuing various requests shown in FIGS. 18 to 25 will be described.

FIG. 18 shows a data format at the time of issuing a request which is used for general purposes. Here, in the field of the request type flag, from the client 20 to the printer server 30
The following information is set to identify the request.

Print request: Set when the client 20 issues a print job.

Replacement request: This is set when a similar job is replaced with the same job.

Registration request ... Set when confirming the existence of a similar job and then registering the job as it is.

Cancel request ... Set when canceling the request of the job.

Job list request: This is set when acquiring the job list information registered in the printer server 30.

Edit request ... Set when editing a job registered in the printer server 30.

Edit data registration request ... Client 20
It is set when the data edited above is registered in the printer server 30.

Next, in the client information field, the IP address of the client 20 is set as information for identifying the client 20 that issues each request. The fields of the data section are set in different formats according to the above various requests (however, the data section does not exist at the time of requesting a job list).

FIG. 19 shows a data format when a print request is issued. Here, similar job search level information is set in the registration mode information field. Client 2
In 0, the information selected based on the following check items is set. However, when this function is used, the client information and the print file name information are always used, and all other information is used under the logical product (AND) condition.

Client: Information for identifying the client 20 is set (IP address).

Print file name ... The document name of the print job is set.

File creation date / time: This is set when it is regarded as a similar job when the file creation dates are the same.

Output page range ... This is set when it is regarded as a similar job when the output page ranges are the same.

Print attribute information: This is set when it is regarded as a similar job when the print attribute information is all the same.

Print resource information ... Set when it is considered as a similar job when the print resource information is all the same.

Next, in the print file name field,
The file name of the print job is set, and the print job is set to the client 2 in the file creation date / time field.
The file creation date / time created on 0 is set.

The print page range information of the print job is set in the output page range field, and the paper size, print orientation, enlargement / reduction rate, N-up set in the print data are set in the print attribute information field. , The number of copies, double-sided single-sided printing, paper feed information, discharge port information, and color / monochrome information are set.

In the print resource information field, print resource information such as font information, form information and image / graphic information set in the print data is set, and in the print data field, the substance of the print data is set. It

FIG. 20 shows a data format when a print job replacement request is issued. Here, information on the number of jobs to be replaced is set in the field of the number of replacement jobs (this information is the number of target job IDs below). Target job I
The job ID information to be replaced is set in the D field (a plurality of them are possible). The job ID is a job ID managed in the printer server 30. Further, the substance of print data is set in the data field.

FIG. 21 shows a data format when a print job registration request is issued. Here, the file name of the print job is set in the print file name field, and the file creation date / time when the print job was created on the client is set in the file creation date / time field.

The print page range information of the print job is set in the output page range field, and the paper size, print orientation, enlargement / reduction ratio, N-up set in the print data are set in the print attribute information field. , The number of copies, double-sided single-sided printing, paper feed information, discharge port information, and color / monochrome information are set.

Print resource information such as font information, form information, image / graphic information set in the print data is set in the print resource information field, and the substance of the print data is set in the print data field. It

However, this request format is set only when the job attributes are changed and registered. When registering with the same print information as when the print request is issued, this request data is not output.

FIG. 22 shows the data format when a print job cancellation request is issued. Here, information on the number of jobs to be canceled is set in the number of canceled jobs field (this information is the number of target job IDs below). In the target job ID field, the job I to be canceled is
D information is set (multiple items allowed). This job ID
Is a job ID managed in the printer server 30, and is set by arbitrarily selecting the job ID and the job ID regarded as a similar job existing in the printer server 30.

FIG. 23 shows the data format when a print job edit request is issued. Here, the edit type information of the edit job is set in the edit type field. In addition,
The following items are selected as the editing type here.

Data editing ... Set when editing print data and print information at the same time.

Edit print information ... Set when editing only print information.

Next, in the edit job ID field,
The job ID information to be edited is set.

FIG. 24 shows a data format at the time of registering edit data. Here, the job ID of the edited print job is set in the job ID field, and the output page range information of the print data is set in the output page range field. In the data type field, the following information for identifying the content of the edited data is set (select either one for all data change or some data change).

Change all data ... Set when replacing all data.

Partial data change ... Set when replacing only the edited data part.

Attribute change ... Set when print information is edited.

Next, in the field of the edit print attribute section,
The changed print attribute information is set. The print attribute information is set in the same format as the print attribute information and the print resource information stored in the job management table 39 of FIG.

Information on the number of times of repetition of data changed discontinuously is set in the change number field (1 is always set when the data type is all data change). In addition, the following information is set in the field of the edit data section according to the above-mentioned data type information.

Page range: The page range information of the set data is set.

Data ... The changed data is set.

The page range and data are set repeatedly by the number of information changes.

FIG. 25 shows the data format at the time of job list response. Here, the number of print jobs requested by the client is set in the target job number field.

The following target job information (job ID ~
Processing information) is set for the number of target jobs indicated at the beginning. The data information field indicates whether or not the last data part exists (the data part is set when a data edit request is received).

A job number registered in the printer server 30 is set in the job ID field, and date / time information when the print job is input to the printer server 30 is set in the job input date / time field. Is set.

In the job status field, job status information in the printer server 30 as described below is set.

Waiting for printing: means waiting for data output to the printer 40.

Printing ... Means that the job is currently undergoing output processing.

Hold: Means a state in which an error occurs during the job output process and output cannot be performed.

Editing ... The job is currently in the client 2
0 means that it is being edited.

Lock: Indicates that the job is regarded as a similar job and cannot be output.

Next, the IP address information of the client 20 is set in the client information field,
A file name of print data is set in the print file name field. In the file creation date field, date / time information when the print data file was created by the client 20 is set, and in the output page range field, page range information of print data output is set.

In the print attribute information field, the paper size, print orientation, enlargement / reduction ratio, N-up, number of copies, double-sided single-sided print, paper feed information, discharge port information, color set in the print data. / Attribute information such as monochrome information is set, and print resource information such as font information, form information, and image / graphic information set in the print data is set in the field of print resource information.

Further, in the processing information field, the reason information indicating that the job status is in the hold status is stored (this information is set only for the job in the hold status). The print data itself is set in the data field. In addition,
In the data field, when the client 20 makes a data edit request, the print data is set in order to transfer the target print data.

[Procedure of Basic Processing in Client and Printer Server] Next, as the basic processing in the client 20 and the printer server 30, each processing procedure of start processing, print request processing, and edit request processing will be described. .

Starting Process First, the starting process will be described as a basic process.

(1) Client-Side Activation Process In the client 20 shown in FIG. 4, the main control unit 21 that is activated first continues the process until it receives a stop request from the operator. The job operation unit 22 and the job output control unit 23 are respectively activated when the operator makes a print request or when various other request events occur, and the job operation unit 22 and the job output control unit 23 perform a series of control operations. When the processing is completed, the processing is stopped, and control is passed to the main control unit 21.

(2) Start-up process on printer server side In the printer server 30 shown in FIG.
The main control unit 31 which is first activated in the same manner as the configuration of
The process is continued until a stop request is received from the operator.

Each of the following control units for actually performing the input, management and output processing of the print job is started by the main control unit 31 at the same time when the main control unit 31 is activated, and the respective control units process in parallel. Is done.

Data input control unit 32 Job management unit 34 Data output control unit 35 In addition to this, data transmission / reception unit 33 and data output unit 36
Is a data input control unit 3 which is a higher-order control unit of each.
2 and the data output control unit 35.

Of these, the data transmission / reception section 33 is started by the data input control section 32 when a request event from the client 20 occurs, and ends the processing when a series of control processing with one client 20 is completed. To do.

One of the data output units 36 is activated in response to each printer 40 when the data output control unit 35 is activated, and a stop request from the main control unit 31 is sent via the data output control unit 35. Processing continues until it is accepted.

The processing of each of the control units mounted on the printer server 30 is performed in parallel so as to receive requests from a plurality of clients 20 and a plurality of printers 40.
The data output function to is realized.

Print request processing Next, the print request process will be described.

(1) Print request issuing process on client side When the client 20 receives a print request from the operator, the process waits until various print attribute information and print resource information are set, and the print attribute information and the print attribute information are printed. After the setting of the resource information is completed, a print request is issued to the printer server 30 in the data format shown in FIGS. 18 and 19.

At the client 20, after issuing this request,
The process waits until the response information from the printer server 30 is received, and the process according to the response information from the printer server 30 is performed in (3) described later.

(2) Print request acceptance processing on the printer server side When the print request is received from the client 20, the printer server 30 newly activates the data transmission / reception unit 33 for performing communication control processing with the client 20, The data transmission / reception unit 33 cooperates with the job management unit 34 to manage the job management table 39 in the printer server 30.
Is checked to check whether or not a similar job already exists. It should be noted that the check processing of similar jobs is performed only when the registration mode information in FIG. 19 is set.

As a result of this job check processing, similar job list information (see FIG. 2) is displayed only when similar jobs are detected.
5) is generated and information is transferred to the client 20.

Further, in the printer server 30, the job waiting for printing which is judged to be a similar job is put in the output hold state,
When there is a job being printed, a process of immediately suspending the output process is performed.

If there is no similar job, the normal job registration processing is performed, all print data input processing is performed, and then information indicating that the job is normally registered is sent to the client 20.
Transfer to. It should be noted that the normal registration processing includes processing for newly registering in the job management table 39 managed by the job management unit 34 in the printer server 30 and spooling all print data while registering in the file management table 38.
This is the process of storing in B.

(3) Response information check process and post-processing instruction on the client side The response information from the printer server 30 is checked, and if normally registered, the series of processes for the print request ends.

In addition, when it is notified that there is a similar job, the client 20 displays similar job list information (including print attribute information and print resource information) which is response information from the printer server 30, and operates it. Wait for further instructions from staff.

The operator checks the similar job list information, and selects registration (registration), replacement (replacement of the job and similar jobs), and processing cancellation request of the job and similar jobs as the processing of the print job. can do.

When a similar job is detected in the printer server 30, all the similar jobs are put in the output hold (locked) state and the output processing is not performed until the client 20 gives an instruction. Processing is performed. This control processing is performed by changing the queue information in the job management table 39 shown in FIG. 14 to the "locked state".

Further, when the print job which is a similar job target is undergoing the print processing, the temporary stop processing of the processing is immediately performed.

The client 2 for the same type of job is described below.
Various post-processing with 0 will be described.

(A) Registration request issuance process This request is a request issued when there is a similar job but the job is registered as it is. Client 2
In step 0, the registration request data in the data format shown in FIGS. 18 and 19 is generated, and the generated registration request data is issued to the printer server 30.

(B) Replacement Request Issuing Process This request is set when a similar job registered in the printer server 30 is replaced with the same job.

In this case, the client 20 shown in FIG.
The replacement request data having the data format shown in FIG. 20 is generated, and the generated replacement request data is issued to the printer server 30.

(C) Cancellation Request Issuing Processing This request is set when canceling any job from the job request and the similar job requested to the printer server 30 at the same time.

In this case, the client 20 shown in FIG.
Generate cancellation request data in the data format shown in FIG.
A process of issuing the generated cancellation request data to the printer server 30 is performed.

(4) Print job post-processing instruction acceptance processing on the printer server side The printer server 30 accepts the above-described various requests for similar jobs, and performs the following processing in response to each request.

(A) Registration request acceptance process When a registration request is accepted, the process for registering the job is performed, and the unlocking process for the print job in the print waiting state, which is determined to be a similar job, and the job being printed are performed. If it exists, the output processing that has been suspended is restarted.

(B) Replacement request When a replacement request is received, the replacement processing of the job information set in the highest output order among the plurality of similar job information set in FIG. I
D performs the existing setting value), and then performs the deletion (processing cancellation) process of the other replacement jobs, and the unlocking process of the other similar jobs. However, the deletion process is not performed when replacing one job.

Further, at this time, if the job to be replaced is being printed, the job is replaced with the job currently being printed, and the output process that has been temporarily stopped is restarted after the replacement process is completed.

(C) Cancellation request When a cancellation request is received, a batch deletion (processing cancellation) processing of a plurality of similar jobs set in FIG. 22 and the jobs concerned is performed.

Others Similar jobs not set in FIG. 22 are unlocked. Also, FIG.
When the job being printed is set among the jobs set to 2, the job being printed is immediately canceled.

Editing request processing Next, the edit request process will be described.

(1) Initial request (job list acquisition request) issuance processing by the client 20 When the client 20 receives an edit request from the operator, first, the job list request data in the data format shown in FIG. Process to transfer to.

At the client 20, after issuing this request,
The process waits until the response information from the printer server 30 is received, and the process corresponding to the response information from the printer server 30 is performed in (3) described later.

(2) Job list request acceptance process and response process in the printer server 30 When the printer server 30 accepts a job list request, all job information matching the client 20 that issued the request is listed in the job management table. 39 (FIG. 14), the process of transferring the job list response data shown in FIG. 25 to the client 20 is performed, and then the process waits until the client 20 gives another instruction.

(3) Job list information display process and edit check request process in the client 20 When the job list response is received from the printer server 30, if the target job does not exist, the process is terminated and the target job is If it exists, the job list response data shown in FIG. 25 received from the printer server 30 is displayed on the display 24.

After that, the process waits until the operator gives an instruction to edit the job arbitrarily selected from the job list.

When an editing request event by the operator occurs,
Further, in order to check whether or not the selected job is in the editable state, a process of generating an edit request in the data format of FIG. 18 and print job edit request data shown in FIG. 23 and transferring it to the printer server 30 is performed. The process waits until the response from the printer server 30 is received.

(4) Edit Check Acceptance Process and Response Process in Printer Server 30 When the printer server 30 receives an edit check request (edit request in the data format in FIG. 18 and print job edit request data in FIG. 23), When the target job is searched for in the job management table 39, if the target job is in the print waiting state, the lock process is performed to put it in the output hold state. If the print process is in progress, the output process is immediately suspended. After that, the job list response data shown in FIG. 25 is generated and transferred to the client 20.

When the job is deleted from the job management table 39 (when the selected job has already been output), a message to that effect is sent to the client 20.
Perform a process to notify.

(5) Job edit request issuance process in the client 20 When the client 20 is informed that editing is impossible in the above process, a message to that effect is displayed and the process is terminated, and when editing is informed The job information or print data information set in the job list response data in FIG. 25 is displayed on the display 24. For this information, the operator can use the following two editing functions for editing the job.

-Job information editing (print information, print resource information, other output page information) -Data editing The basic processing when each of the above functions is selected will be described below.

(A) Data edit request processing When the data edit request processing is accepted, the acceptance processing is performed by combining the changed print data and job information, and the edit data registration request in the data format of FIG. Processing for generating data and transferring it to the printer server 30 is performed.

When print data is set in the data shown in FIG. 24, it is possible to select either the changed data portion or the entire data transfer method.

(B) Job information change processing When a job information change request is received, the changed job information is received, and the edit data registration request in the data format of FIG. 18 and the data shown in FIG. 24 are generated. The process of transferring to the printer server 30 is performed. Note that FIG.
In the process of generating the data shown in FIG. 4, the format is different between when the job information is edited and when the data is edited and edited (the print data is not set in this request process).

(C) Edit Cancellation Process Upon receipt of the edit cancel request process, the cancel request data having the data format shown in FIG.
Then, the job edit is canceled and the job edit is canceled.

(6) Job edit request acceptance processing in the printer server 30 The printer server 30 performs the following processing in response to each request instructed by the client 20.

(A) Data edit request processing When a data edit request is accepted, the data type information in the data of FIG. 24 is checked, and when all data is changed, the information registered in the file management table 38 is deleted. After that, a process of updating with the information set in the edit data section in the data of FIG. 24 is performed.

In the case of partial data change, the information registered in the file management table 38 is updated according to the page range information in the data of FIG. File management table 3 when this partial data is changed
The information update processing of No. 8 will be described later with reference to FIG.

Note that the processing of the above-mentioned edit data section is as shown in FIG.
The process is repeated by the number set in the change number information in the data.

After the editing data update processing is completed,
A process of updating the information of the target job registered in the job management table 39 with the information set in the data of FIG. 24 is performed.

Further, when the target print job is in the process waiting state, the process of releasing the lock state is performed, and in the case of the job being printed, the suspension is released and the re-output process is performed according to the updated information. .

(B) Job information change processing When a job information change request is received, the job management table 39 is based on the information set in the data of FIG.
Update process.

Further, when the target print job is in the process waiting state, the process of releasing the lock state is performed, and in the case of the job being printed, the suspension is released and the re-output process is performed according to the updated information. .

(C) Editing cancellation processing When an editing cancellation request is received, if the target print job is in the processing waiting state, processing for canceling the locked state is performed, and if it is a printing job, the temporary stop is canceled. Perform processing.

[Detailed Procedure of Processes Performed by Control Units of Client and Printer Server] As an operation of this embodiment, the client 20 in the case where the print job requested by the client 20 is controlled by the printer server 30 will be described below. The communication control processing routine in each control unit of the printer server 30 will be described in detail.

(Detailed Description of Communication Control Process in Client 20) The client 20 executes the control routine shown in FIG. In step 102 of FIG. 5, the main control unit 21 controls the job output control unit 23 and the job operation unit 22.
Start in this order. When both the job output control unit 23 and the job operation unit 22 are activated, the next step 104
At the job operating unit 22, a request from the operator (either a print request, an edit request (= an edit request for a print job stored in the printer server 30), or an end request)
Wait for reception.

Here, when the request from the operator is received,
At the next steps 106 and 128, it is determined whether the request is a print request, an edit request, or an end request.

If the request from the operator is a print request, the process proceeds to step 108, where the job operation unit 22 sets print attribute information, print resource information, the number of output pages, etc. set in the requested print data. Is displayed, a print information setting screen for setting various information shown below in the print job or changing existing setting values is displayed on the display 24, and processing is performed until all print information setting by the operator is completed. Wait for

The print information set by the operator includes the following information.

Print Attribute Information This information includes paper size, print orientation, enlargement / reduction ratio, N-
Up, the number of copies, double-sided single-sided printing, paper feed information, discharge port information, color / monochrome information, etc. are included (see the print attribute information field of the job management table 39 in FIG. 14).

Print Resource Information This information includes font information, form information, image information, etc. (see the print resource information field of the job management table 39 in FIG. 14).

Output page range information In this information, output start page information and output end page information of print data are set. If not set, a value equivalent to full page output is set as full page output).

Registration Mode Information This information is for setting the search level of similar jobs, and is used when the printer server 30 performs job search processing similar to the print job that issued the print request. Is.

This information can be set by arbitrarily combining five types of information such as file name, file creation date / time, output page range, print attribute information, and print resource information. However, when the main registration mode information is set for the client information, it is automatically set by the job operating unit 22 (for detailed setting information, refer to FIG.
9 for the data format when the print request is issued). In the printer server 30, when performing similar job check processing based on the registration mode information, all of the above information is a logical product (A
The search process is performed under the ND) condition.

After the operator completes the setting of all the print information, in the next step 110, the job operation unit 22 refers to the set print information and print request issue data (FIGS. 18 and 19). ) Is created and a data transfer request is made to the job output control unit 23.

At the next step 112, the job output control section 23 causes the print request issuing data (see FIGS. 18 and 1).
After 9) is received and the transfer processing is performed to the printer server 30, the response information corresponding to this request is received from the printer server 30, and the job operation unit 22 is notified of the response information.

When the printer server 30 receives this request, when the registration mode information is not set in the print request issuance data of FIG. 19, or the result of performing a similar job search process based on the registration mode information. Only when there is no corresponding job, the data set in the print data field of the print request issuing data in FIG. 19 is received.

On the other hand, when performing the registration processing in which the same type of job exists, the print data set in the data (see FIG. 21) issued in the job registration request issuing processing described later is received.

At the next step 114, the job operating unit 2
2, it is determined whether the response information of the print request issuance data from the printer server 30 is the normal registration completion information (whether it is the similar job detection information). Here, if the response information is the normal registration completion information, a message indicating that the print job has been normally registered is displayed on the display 24, and the process returns to step 104 to wait for the next instruction from the operator. Examples of the case where the normal registration completion information is notified in this way include a case where a similar job is not detected in the printer server 30 and a case where the registration mode instruction is not set at the time of print request.

On the other hand, when it is determined in step 114 that the response information is not the normal registration completion information but the similar job detection information, it means that the similar job exists in the printer server 30, and the response from the printer server 30 is returned. 25 is received as information, the process proceeds to step 116, and the job operation unit 22 uses the job ID information, the job input date / time information, the job stored in the data shown in FIG. 25 as similar job information. The status information, the print file name, the file creation date, the print attribute information, the print resource information, and the processing information are displayed on the display 24 by the number of target jobs. Note that print data is not included in the response data shown in FIG. 25 received in this processing.

Then, the job operating unit 22 waits for the post-processing of the job and the similar job until the operator inputs one of a job registration request, a job replacement request, and a job cancellation request.

When a similar job is detected, the printer server 30 manages all the target print jobs in an output hold (locked) state and does not output them until any one of the above post-processing information is instructed. . Further, when there is a job being printed, the output processing is changed to the output hold (lock) state and the output process is immediately suspended.

Here, when a job registration request is given by the operator (in the case of affirmative judgment in step 118), the job output control section 23 shows the request data for registering the job as it is as shown in FIG. The request data and the job registration request data shown in FIG. 21 are generated, and these are transferred to the printer server 30. Note that the printer server 30 that has received this request performs a process of registering the print job as a new printing job, and then a process of releasing all the jobs in the corresponding output hold (lock) state.

Further, when a job replacement request is issued by the operator (in the case of affirmative determination in step 122), the job output control section 23 causes the job and any job (one or more of the similar jobs) to be selected. ) And request data shown in FIG.
The job replacement request data shown in 0 is generated and transferred to the printer server 30. The printer server 30 that has received this request replaces the job scheduled earliest among the print jobs to be replaced set in the job replacement request data of FIG. After deleting all the other jobs set in the job replacement request data of 20, all other similar jobs in the output hold (lock) state are released. ) Further, when a job cancellation request is given by the operator (in the case of negative determination in step 122), the job output control unit 23 simultaneously processes any job (one or more) of the same job as the job. Request data shown in FIG. 18 and FIG. 2 are shown as request data for canceling.
The job cancel request data shown in 2 is generated and transferred to the printer server 30. The printer server 30 that has received this request deletes all the jobs set in the job cancellation request data of FIG. 22 and then releases all other jobs in the output hold (lock) state. )
When the operator issues an edit request in step 104, the affirmative decision is made in step 128, the process proceeds to step 130, and the subroutine of the print job edit request process of FIG. 6 is executed. The edit request is a function of requesting edit of print data or print information (print attribute information, print resource information, output page setting information, etc.) of a print job stored in the printer server 30. It is roughly divided into data editing that requires editing and print information editing that requires editing of print information.

First, in step 152 of FIG. 6, the job operation unit 22 generates job list request data in the data format shown in FIG. 18, and job output control is performed so that the generated job list request data is output to the printer server 30. An output request is made to the section 23.

At the next step 154, the job output control section 23 transfers the job list request data to the printer server 30 and waits for response information from the printer server 30. In the printer server 30 that has received this request, the job management table 3
The job information registered in FIG. 9 (FIG. 14) is searched, the job list response data shown in FIG. 25 is generated, and transferred to the client 20 as the response information. If there is no target job, the number of target jobs in FIG. 25 is set to “0”.

The job output control section 23 notifies the job operation section 22 of the response result from the client 20 as described above.

At the next step 156, the job operating unit 2
2, the contents of the accommodation information (FIG. 25) are checked to determine whether or not the target job exists. Here, if the target job does not exist, the job is the printer server 30.
Display a message saying that it is not registered in
And terminates the subroutine of FIG. 6 (in this case,
Means there is no editable job).

On the other hand, when the target job exists in step 156, the process proceeds to step 158, and the job operating unit 2
2, the response information from the printer server 30 (see FIG.
5) is displayed on the display 24 as the job list information, and the data edit request or the print information edit request is received from the operator.

When a data edit request or print information edit request from the operator is accepted by the job operating section 22, the request data of FIG. 18 and the print of FIG. 23 are acquired in order to obtain the information of the print job in step 160. The job edit request data is generated, and the data output control unit 23 is requested to output these data to the printer server 30. The information set in the print job edit request data in FIG. 23 has a different format depending on whether the request from the operator is a data edit request or a print information edit request.

In the next step 162, the job output control section 23 transfers the request data (the edit request of FIG. 18 and the print job edit request data of FIG. 23) to the printer server 30, and the data is transferred from the printer server 30. Wait until processing is done. In the printer server 30,
When this request is accepted, it is checked whether or not the job can be edited. If the job is editable, the job is placed in the output hold state (locked), and then the information of the print job is displayed in the format shown in FIG. The process of transferring to the client 20 is performed. If a job that is undergoing printing is selected,
A process of immediately suspending the output request is also performed. The uneditable state means that the output process of the selected job has already been completed.

After that, the data output control section 23 receives the response information from the printer server 30, and then notifies the job operation section 22 of the response information.

At the next step 164, the job operating unit 2
2, the response information is checked, and it is determined whether or not the print job is currently editable based on whether or not the number of target jobs in the job list response data shown in FIG. 25 is “0”. That is, when the number of target jobs is “0”, the print job is considered to be currently in the uneditable state, and a message indicating that the print job is currently in the uneditable state is displayed on the display 24 in step 180, and then the screen of FIG. Finish the subroutine.

On the other hand, if the number of target jobs is 1 or more, the print job is considered to be currently in the editable state, and step 16
In step 6, it is determined whether the content of the edit request is a data edit request or a print information edit request. Here, if it is a data edit request, the process proceeds to step 168, and the acquired print data is displayed on the display 24 by the job operating unit 22. Then, the job operating unit 22 waits for processing until the operator issues an edit data registration request or an edit cancellation request.

If the operator requests editing data registration, the process proceeds to step 172, and the job operating unit 2
2, the change data acceptance process is performed, and the edit data registration request data shown in FIG. 18 (edit data registration request) and FIG. 24 is generated based on the accepted change data. Then, the data output control unit 23 is requested to transfer these data to the printer server 30.

The operator can select either of the following two as the transfer method of the change data.

All data transfer Corrected data transfer In the case of all data transfer, all data set in the output page range information is set in the data format shown in FIG. 24, only the modified one or more modified data parts, FIG.
Set the data format of and transfer. Normal,
Selecting the modified data transfer can reduce the transfer time and the processing time of the printer server 30.

At the next step 174, the job output control section 23 transfers the data requested by the job operating section 22 to the printer server 30. After receiving this request data, the printer server 30 performs a process of replacing the data part of the print job (described later).

On the other hand, after step 168, when an edit cancel request is issued by the operator, the job operation unit 22 sends a request to cancel all the edit modes as shown in FIG.
8 (cancel request) is generated, and the data output control unit 23 is requested to transfer the data to the printer server 30. Then, in the next step 178, the data output control unit 23 transfers the data requested by the job operation unit 22 to the printer server 30, and the control process relating to the main edit request is ended. When the printer server 30 receives this request, the output hold state of the job is canceled.

If the content of the edit request is the print information edit request in step 166, step 18
2, the job operating unit 22 displays various information such as job ID information, job input date / time, job status processing information, print file name, file creation date, print attribute information, print resource information, etc.
It is collectively displayed in 4, and the process is waited until an operator requests editing information registration or editing cancellation.

If the operator requests editing information registration, the process proceeds to step 186, and the job operating unit 22
By accepting the change information from the operator, the edit data registration request data shown in FIG. 18 (edit data registration request) and FIG. 24 is generated based on the change information. Then, the data output control unit 23 is requested to transfer these data to the printer server 30. In the case of this processing request, no information is stored in the edit data section of the data in FIG.

At the next step 188, the data output control section 23 transfers the data requested by the job operating section 22 to the printer server 30. After receiving this request data, the printer server 30 performs a process of updating print information of the print job (described later).

On the other hand, after step 182, if the operator requests editing cancellation, the process proceeds to step 190.
The job operation unit 22 generates the data shown in FIG. 18 (cancellation request) as a request for canceling all the edit modes, and requests the data output control unit 23 to transfer the data to the printer server 30. .

Then, in the next step 192, the data output control section 23 transfers the data requested by the job operating section 22 to the printer server 30, and the control processing relating to the main edit request is terminated. The printer server 3
In 0, the output hold state of the job is canceled when this request is accepted.

When an edit request is received in step 104 of the main routine of FIG. 5, the print job edit request processing subroutine shown in FIG. 6 is executed, and then the process returns to step 104 to wait for an event again. .

By the way, when the end request from the operator is received in step 104, the job operating section 22 notifies the main control section 21 of the end notification of the client system, and controls the main control section 21. hand over. Then, the main control unit 21 stops the job output control unit 23 (step 13
2) and stop processing of the job operation unit 22 (step 134)
After performing the above, all processing is terminated.

(Detailed Description of Communication Control Processing in Printer Server 30) Next, communication control processing in each control unit of the printer server 30 will be described. As described above, the printer server 30 includes the main control unit 31 and the data input control unit 3.
2. Six control units including a data transmission / reception unit 33, a job management unit 34, a data output control unit 35, and a data output unit 36 are mounted, and each control unit executes a communication control process described later.

Hereinafter, the process by the main control unit 31 (FIG. 7), the process by the data input control unit 32 (FIG. 8),
The processing by the data transmitting / receiving unit 33 (FIG. 9), the processing by the job management unit 34 (FIGS. 10 and 11), the processing by the data output control unit 35 (FIG. 12), and the processing by the data output unit 36 (FIG. 13) will be described in order. To do.

Details of Processing by Main Controller 31 The main controller 31 executes the control routine shown in FIG. In steps 202 to 206 of FIG. 7, in order to perform the input / output control process of the print job, the job management unit 34, the data input control unit 32, and the data output control unit 35 are activated in this order.

In the next steps 208 and 210, the control process relating to the print job is not particularly performed, and a stop request from the operator is waited for. All the control processing of the print job during this period is performed by another control unit.

When the print job is completed and the operator issues a stop request, in the next steps 212 to 216, the data input control section 32, the data output control section 35,
The stop processing of these control units is performed in the order of the job management unit 34. Then, the processing by the main control unit 31 also ends.

Details of Processing by Data Input Control Unit 32 The data input control unit 32 executes the control routine of FIG. First, in step 222 of FIG. 8, the main controller 31
The stop flag peculiar to the data input control unit 32 which is set to ON when the stop request is received is checked. Here, if the stop flag is on, the process proceeds to step 224, and the contents of the data transmission / reception unit management table 37 are checked to check whether all the data transmission / reception units 33 are stopped.

Thereafter, the check processing of step 224 is continuously performed until the processing of all the data transmitting / receiving sections 33 is completed, and when the processing of all the data transmitting / receiving sections 33 is completed, the control is passed to the main control section 31. . It should be noted that in the data transmission / reception unit management table 37, information on the data transmission / reception unit 33 is set every time one data transmission / reception unit 33 is activated.

On the other hand, if the stop flag is off in step 222, the process proceeds to step 228, waits for processing until any one of the three events of stop request, transmission / reception unit stop notification, and data reception occurs, and the event occurs. After that, the following processing is performed according to the event that has occurred.

When the stop request is received from the main control section 31 in step 228, the stop flag held in the data input control section 32 is turned on in step 232 (end mode).
After setting to, the process returns to step 222 and the stop flag is checked again.

When the processing of the data transmitting / receiving unit 33 activated to control the communication with one client is completed and the data transmitting / receiving unit stop notification is received, the process proceeds to step 236, and the data input is performed when this event occurs. After deleting the corresponding data transmitting / receiving unit information in the data transmitting / receiving unit management table 37 (see FIG. 15) held by the control unit 32, the process returns to step 222 and the stop flag is checked again.

Further, when a request event relating to a job operation newly occurs from one client 20 and a data reception event occurs, the process proceeds to step 238, and the on / off state of the stop flag at that time point is checked. here,
If the stop flag is on, the message indicating that communication cannot be performed because the printer server 30 is already in the end mode is transferred to the client 20, and then step 22 is executed.
Return to 2 and check the stop flag again.

On the other hand, if the stop flag is off in step 238, the data transmitting / receiving unit 33 is activated in step 242 to start the communication control process with the client 20, and then the data transmitting / receiving unit management is performed in step 244. The information of the data transmitting / receiving unit 33 is set in the table 37. Then, returning to step 222, the stop flag is checked again.

Details of Processing by Data Transmitting / Receiving Unit 33 The data transmitting / receiving unit 33 executes the control routine shown in FIG. First, in step 302 of FIG. 9, the client 2
The request identification flag information of the request data from 0 (see FIG. 18) is checked. At this point in time, the client 20 sends any one of three requests, a print request, a job list request, and a job edit request. Then, in the following, a control process according to each request content is performed.

If a print request is sent from the client 20, the process advances to step 304 to check the registration mode information of the print job request data (see FIG. 19). Here, if the registration mode information is not set in the print job request data, the process proceeds to step 338, the registration request process to the job management unit 34 is performed, and the print job ID information set in the job is acquired. In the next step 340, after the registration processing to the file management table 38 shown in FIG. 17 is performed based on the job ID information newly set by the job management unit 34, the data portion set in FIG. Is stored in the spool 3B. Then, in the next step 342, after notifying the client 20 that the job has been registered, the process is terminated and control is passed to the data input control unit 32.

On the other hand, if information is set in the registration mode information in step 304, the process proceeds to step 306,
In order to search for another job requested by the client 20 (search for a similar job), a similar job search request process is performed to the job management unit 34 (this similar job check process is shown in FIG. 19). Is done based on the registration mode information). In the next step 308, the processing result information from the job management unit 34 is checked to determine whether or not there is a similar job. Here, if there is no similar job, the process proceeds to step 338 and the processes of steps 338 to 342 are executed.

On the other hand, if there is a similar job in step 308, the process proceeds to step 310 and the client 20 receives the data shown in FIG. Then, the process waits until the client 20 sends a registration request, a replacement request, or a cancellation request in step 312. Note that the job management unit 34 manages all jobs in the print waiting state that are determined to be similar jobs as an output hold state until a request from the client 20 (in the case where a job being printed is included, output processing is performed). Will be suspended).

When a job registration request is made from the client 20 (when the data shown in FIGS. 18 and 21 is received), a registration request process to the job management unit 34 is performed in step 316, and the job is set to the job. Print job I
Acquire D information. In the next step 318, after the registration processing to the file management table 38 shown in FIG. 17 is performed based on the job ID information newly set by the job management unit 34, the data set in FIG. The part is stored in the spool 3B. Then, the next step 320
After notifying the client 20 that the job has been registered, the process is terminated and control is passed to the data input control unit 32.

When a job replacement request is issued from the client 20 while waiting for the request in step 312 (see FIG. 18).
When the data shown in FIG. 20 is received), the replacement process of the job is performed in the following procedure. The replacement process means replacing one or a plurality of jobs determined to be similar jobs with the job. Further, with respect to jobs that have not been selected as replacement targets among jobs that have been determined to be similar jobs, the job management unit 34 also dynamically performs processing for canceling the output hold state.

In this case, the process proceeds to step 324, and FIG.
The information set in the data is notified to the job management unit 34 and the replacement request process is performed. In the case of replacement processing, replacement processing with an existing job is performed, so the job management unit 3
In 4, the process of newly setting the job ID is not performed for the job.

After this, the job management section 34 notifies the replaced job number and the other job ID information to be deleted set in FIG. 20 as response information.

At the next step 326, all the data of the existing replacement job and the other replacement target job notified by the job management unit 34 in the above processing are deleted from the spool 3B. When deleting data from the spool 3B, an entry deletion process from the file management table 38 shown in FIG. 17 is also performed.

At the next step 328, the job management section 3
1 based on the job ID information newly set from No. 4.
After performing the registration process in the file management table 38 shown in FIG. 7, the data portion set in FIG. 21 is stored in the spool 3B. Then, in the next step 330, after notifying the client 20 that the job is registered,
The process is terminated and control is passed to the data input control unit 32.

In this replacement request processing, for example, as shown in FIG.
When a replacement request for a new job shown in the middle part of the figure and a job of JOB0003, JOB0006 is made, JOB0003 to be replaced,
The job information of JOB0006 is deleted from the job management table 39A, and the new job information is additionally registered in the job management table 39A with the job ID = JOB0003. At this time, the job status of the new job is changed from the failure to the print waiting, and the processing information is also deleted. As a result, the registration information of the job management table is
It becomes like B.

Further, while waiting for the request of step 312,
When a job cancellation request is made by the client 20 (see FIG. 1)
8 and the data shown in FIG. 22), step 3
In step 32, the job management unit 34 is notified of the information set in FIG. 22, and the job cancellation request process is performed. Note that it is possible to set one or a plurality of pieces of job ID information to be subject to processing cancellation in the field of the target job ID in FIG. 22, and in this function, any job that is judged to be a similar job including the job concerned can be set. Jobs can be canceled at the same time. Further, for jobs of the same type other than the processing cancel target, the job management unit 34 performs processing for canceling the output hold state.

At the next step 334, all the data of all the jobs indicated by the job ID information other than the job set in FIG. 22 are deleted from the spool 3B. When deleting data from the spool 3B, the entry deletion process from the file management table 38 shown in FIG. 17 is also performed at the same time as in the replacement process. Then, in the next step 336, after notifying the client 20 that one or a plurality of jobs instructed by the client 20 has been canceled, the process is terminated and control is passed to the data input control unit 32.

When a job list information request is sent from the client 20 in step 302, the following job list information request processing is performed in steps 346 and 348. The job list information request process is a process for returning the registered job information issued by the client 20 existing in the printer server 30. When the client 20 issues a job list information request, the data shown in FIG. 18 (job list request) is generated and output.

At step 346, the printer server 30
In order to acquire the job list information registered in
The job management unit 34 is notified of the client information stored in FIG. 18 and a job list information acquisition request is issued. Then, the process waits until the response information is acquired from the job management unit 34. In the job management unit 34, when a corresponding job exists as the response information of this request,
Notification is made in the data format shown in FIG.

When the response information is acquired from the job management section 34, the acquired information (see FIG. 25) is transferred to the requesting client 20 in the next step 348.
The process is terminated and control is passed to the data input control unit 32.

If a job edit request is sent from the client 20 in step 302, the following job edit request process (= actual data or print information of the job registered in the printer server 30 ( Print attribute information, print resource information, etc.) is edited).
Note that when the client 20 issues a job edit request, the data shown in FIG. 18 (edit request) and FIG. 23 are generated and output.

At steps 352 and 354, the job management section 34 is requested to check whether the edit target job ID set in FIG. 23 is editable. After the check process in the job management unit 34 is completed,
If the job is not editable (output-completed job), a process of notifying the client 20 of a message indicating that it is not currently editable is performed (step 356). If it is editable, the following process is continued. .

In step 358, the edit type information set in FIG. 23 is referred to, and it is determined whether or not the print data is the type to be changed. Here, if it is the type that changes the print data, both the print data and the print information are transferred to the client 20 in the format shown in FIG. 25 (step 360), and if the type that changes only the print information, the print data is changed. Not transferred and only print information client 2
0 (step 362).

After that, the processing is waited until there is a request from the client 20 for the response information, and the processing corresponding to each request is continued.

Here, if there is a cancellation request from the client 20, the job ID information to be edited is passed to the job management section 34 in step 368, and the editing cancellation request process for the job is performed. The job management unit 3
In 4, the processing for canceling the output hold state of the target job is performed. Then, in the next step 370, after the client 20 is notified that the editing of the job instructed by the client 20 has been canceled, the process is terminated and the control is passed to the data input control unit 32.

On the other hand, in step 364, the client 20
If there is an editing request from step 372, steps 372, 374
The data type information of FIG. 24 is attribute change, all data change,
Check whether it is a partial data change.

If the data type information is all data change, all the data of the job is set in the edit data section of FIG. 24. Therefore, referring to the file management table 38 shown in FIG. After deleting all the job data, the print data set in the edit data section of FIG. 24 is stored in the spool 3B (step 376). Thereafter, the job information regarding the edit job is also reset, so that the process proceeds to step 380 described later.

If the data type information is a partial data change, the edit data section of FIG. 24 stores print data of only the modified section, so refer to the file management table 38 shown in FIG. Then, the update processing to the data of the job is performed (step 378).

An example of this updating process will be described with reference to FIGS. As shown in FIG. 27, the start point information of the file management table 38 is set with the start address of data for each job, and is chained page by page for each job by the next page pointer information. ing. When the page pointer is 0, it means the end of data.

From such a state shown in FIG. 27, the JOB
FIG. 28 shows an example in which the second page of the 0003 data is changed and the third page is additionally edited. As shown in FIG. 28, JOB0003 was initially chained, but is changed to a chain by the edit request of the client. Then, the page data of is deleted from the spool 3B.

After such update processing, the job information relating to the edit job is also reset, so that
The process moves to step 380 described later.

If the data type information is attribute change, the edit data section of FIG. 24 has not been set, so the process proceeds to step 380, and the information of FIG.
The job management unit 3 delivers the output page range, print attribute information, and print resource information of the job to the job management unit 3.
Ask 4.

After the request processing is completed, the client 20 is notified that the edit request for the job instructed by the client 20 is completed, and then the processing is terminated and the control is passed to the data input control unit 32.

Details of Processing by Job Management Unit 34 The job management unit 34 executes the control routines shown in FIGS. First, in step 402 of FIG. 10, as the initialization process, the job management table 39 (see FIG. 14) and the file management retained in the spool 3B for resetting the state of the previous stop immediately after the startup process and the file management. The information in the table 38 (see FIG. 17) is read.

Then, the processing is waited until each of the following events occurs, and the process proceeds to the processing step corresponding to each event.

As an event from the data transmitter / receiver 33,
There are the following nine events.

-Similar job check request (in this case, proceed to step 406 in FIG. 10) -Normal registration request (in this case, proceed to step 424 in FIG. 10) -Job registration request (in this case, step 430 in FIG. 10)
Go to) -Job replacement request (in this case, step 442 in FIG. 10)
Job cancellation request (in this case, step 454 of FIG. 10)
Go to) -Job list request (in this case, step 464 in FIG. 10)
Job edit request (in this case, step 470 of FIG. 11)
Edit cancellation request (in this case, step 486 in FIG. 11)
Edit data registration request (in this case, step 4 in FIG. 11)
Further, as the event from the data output control unit 35, there are the following two events.

Job output request (in this case, proceed to step 506 in FIG. 11) Job output completion notification (in this case, step 5 in FIG. 11)
Further, as the event from the main control unit 31, there is the following one event.

Stop request (in this case, the process proceeds to step 524 in FIG. 11) The processing corresponding to each of the above events will be described in order below.

(1) When there is a similar job check request from the data transmitting / receiving unit 33, step 40 in FIG.
Go to 6. This similar job check request is notified from the data transmitting / receiving unit 33 when the data transmitting / receiving unit 33 receives the information shown in FIGS. 18 and 19 output from the client 20 as the print job request issuing process. However, if the registration mode information is not set in the print request issue data of FIG. 19, this process is not performed.

In step 406, the information shown in FIGS. 18 and 19 is acquired from the data transmission / reception unit 33 when the similar job check request is received, and the job management table 39 managed by the job management unit 34 is searched for. Check the job information that matches the similar job check request. In the next step 408, it is determined whether or not there is a similar job based on the check processing result. If there is no similar job, in step 410, the data transmitting / receiving unit 33 is notified that there is no similar job, and then step Return to 404.

On the other hand, if there is a similar job, information about the similar jobs is collected from the job management table 39 at step 412, and then all the jobs judged as similar jobs at step 414 are put into a temporary output hold state. Queue information in the job management table 39 (see FIG.
(See) is set to the locked state.

Then, in the next step 416, it is determined whether or not there is a job currently undergoing print processing among the jobs determined to be similar jobs, and the process proceeds to step 418 only when there is a job under print processing. , Data output unit 36
Sends a print job output process suspension request. As a result, the job being printed is temporarily stopped.

Thereafter, the process proceeds to step 420, where all the job information is created in the format shown in FIG. 25 based on the similar job information obtained at step 412, and the created job information is notified to the data transmitting / receiving unit 33. Then, step 404
Return to.

(2) If there is a normal registration request from the data transmitting / receiving unit 33, the process proceeds to step 424 in FIG.
This normal registration request is notified from the data transmitting / receiving unit 33 when the data transmitting / receiving unit 33 receives the data shown in FIG. 18 (registration request) and FIG. 19 or FIG. 21 from the client 20.

At step 424, a new job in FIG. 18 and FIG. 19 or FIG.
Various information set in the data shown in 1 is registered. The job ID information in the job management table 39 is newly assigned at this point. Next step 42
In step 6, the data transmission / reception unit 33 is notified together with the newly set job ID information that the registration processing of the new job in the job management table 39 is completed. Then step 4
Return to 04.

(3) When there is a job registration request from the data transmitting / receiving unit 33, the process proceeds to step 430 in FIG. This job registration request is sent from the client 20 as shown in FIG.
When the data transmitting / receiving unit 33 receives 8 (registration request) and the data shown in FIG. 21, the data transmitting / receiving unit 33 notifies.

At step 430, a new job is stored in the job management table 39 (FIG. 14) as shown in FIGS.
The various information set in the data shown in is registered. At the time of this request processing, the job ID information in the job management table 39 is newly allocated as in the case of the normal registration request. After the job registration process is completed, the next step 432 unlocks all print jobs that are already in the output hold state.

At the next step 434, it is judged whether or not the job judged as a similar job includes a printing job, and only when the printing job is included, the process proceeds to step 436, and the data output unit 36 Is notified to the effect that the suspension of the printing job is canceled and the printing process is continued.

At the next step 438, the fact that the registration processing of the new job in the job management table 39 is completed is notified to the data transmitting / receiving unit 33 together with the newly set job ID information. Then, the process returns to step 404.

(4) When there is a job replacement request from the data transmitting / receiving unit 33, the process proceeds to step 442 in FIG. This job replacement request is issued by the client 20 as shown in FIG.
When the data transmitting / receiving unit 33 receives 8 (replacement request) and the data shown in FIG. 20, the data transmitting / receiving unit 33 notifies.

At step 442, all the target jobs are deleted from the job management table 39 by referring to the information set in the data of FIG. 20, and the other jobs judged as similar jobs are in the output hold state. To cancel. However, the job ID information scheduled at the head of the deleted target jobs is the step 44 described later.
Retain it without deleting it for use in 4.

In the next Step 444, the above Step 4
Using the job ID information acquired in 42, the various information set in FIGS. 18 and 20 is set in the job management table 39. At this time, the job status in the job management table 39 is waiting for printing.

At the next step 446, it is judged whether or not the job judged to be a similar job includes a printing job, and only when the printing job is included, the routine proceeds to step 448 and the data output unit 36 In response to the instruction, the temporary stop of the printing job is canceled and the re-output process is instructed.
Then, in the next step 450, the data transmitting / receiving unit 33 is notified that the registration processing of the replacement job is completed. Then, the process returns to step 404.

(5) If there is a job cancellation request from the data transmitting / receiving unit 33, the process proceeds to step 454 in FIG. This job cancellation request is issued by the client 20 as shown in FIG.
When the data transmitter / receiver 33 receives 8 (cancel request) and the data shown in FIG. 22, the data transmitter / receiver 33 notifies the data.

At step 454, referring to the information set in FIG. 22, all the target jobs are deleted from the job management table 39, and the other jobs judged to be similar jobs are opened and the output hold state is set. To cancel.

At the next step 456, it is judged whether or not the job judged to be a similar job includes a printing job, and only when the printing job is included, the processing proceeds to step 458 and the data output unit 36 Is instructed to cancel the processing of the job. Then, in the next step 460, the data transmission / reception unit 33 is notified that the job cancellation processing is completed. Then, the process returns to step 404.

(6) If there is a job list request from the data transmission / reception unit 33, the process proceeds to step 464 in FIG. This job list request is sent from the client 20 as shown in FIG.
The data shown in 8 (job list request)
3 is notified by the data transmitting / receiving unit 33.

At step 464, all the corresponding job information is acquired from the job management table 39 shown in FIG. 14 based on the client information set in the job list request data of FIG. 18, and shown in FIG. The data is created and the information is passed to the data transmission / reception unit 33 which is the request source (however, the print data is not set in the data of FIG. 25 at this time).

At the next step 466, the data transmission / reception section 33 is notified that the job list information acquisition processing is completed together with the information (FIG. 25) created in the above processing. Then, the process returns to step 404.

(7) When there is a job edit request from the data transmitting / receiving unit 33, the process proceeds to step 470 of FIG. This job edit request is sent from the client 20 as shown in FIG.
8 (edit request) and the data shown in FIG. 23 are received by the data transceiver 33 when the data transceiver 33 receives the data.

At step 470, it is checked by referring to the job management table 39 whether or not the edit target job set in the data of FIG. 23 is currently in the editable state. If the result of this check processing is that the job is in the uneditable state (= when the job has already been output and does not exist), the process proceeds to step 474, and the edit job requested by the client 20 is currently in the uneditable state. Is notified to the data transmitting / receiving unit 33, and the process returns to step 404.

On the other hand, if the job is in the editable state, the flow advances to step 476 to change the state of the job to be edited in the job management table 39 to "locked" (this processing releases the job. Will not be treated as output target job).

At the next step 478, it is determined whether or not the edit job is being printed. Only when it is being printed,
Proceeding to step 480, the data output unit 36 is requested to suspend the output processing of the print job.

Then, in the next step 482, the job information searched in the above processing is set to the job management table 3
The data transmission / reception unit 33 is notified that the job edit request processing is completed together with the acquired job information. Then, the process returns to step 404.

(8) If there is an edit cancellation request from the data transmitting / receiving unit 33, the process proceeds to step 486 in FIG. This edit cancellation request is sent from the client 20 as shown in FIG.
When the data transmitting / receiving unit 33 receives the data indicated by 8 (cancel request), the data transmitting / receiving unit 33 notifies. When the data transmission / reception unit 33 notifies this request,
The edit target job ID information is notified.

At step 486, the data transmitter / receiver 33
The job status is “locked” by searching the job management table 39 using the edit target job ID information notified from
To “waiting for printing” (this job status change processing causes the job to be queued again in the output queue).

At the next step 488, it is determined whether or not the edit job is being printed, and only when it is being printed,
Proceeding to step 490, the data output unit 36 is requested to restart the output processing of the print job. Then, the next step 49
In 2, the data transmission / reception unit 33 is notified that the editing cancellation processing of the editing job is completed. And step 4
Return to 04.

(9) When there is an edit data registration request from the data transmitting / receiving unit 33, the process proceeds to step 496 in FIG. This edit data registration request is notified from the data transmitting / receiving unit 33 when the data transmitting / receiving unit 33 receives the data shown in FIG. 18 (edit data registration request) and FIG. 24 from the client 20.

At step 496, the edit target job search processing registered in the job management table 39 is performed, and all the existing data are updated with the information set in FIG. At this time, the job status information in the job management table 39 is changed from “lock” to “print waiting”.

At the next step 498, it is determined whether or not the edit job is being printed. Only when it is being printed,
In step 500, the data output unit 36 is requested to restart the print job.

At this time, in the case of an all data change request or an attribute change request, a process of issuing a re-output processing request (re-output instruction from the first page) of the job to the data output unit 36 is performed, and a partial data change request is issued. 24, all the changed page range information in the data of FIG. 24 is notified, and the data output unit 36 is notified to re-output the job according to the current processing status.

Then, in the next step 502, the data transmitting / receiving unit 33 is notified that the edit data registration processing is completed. Then, the process returns to step 404.

(10) If there is a job output request from the data output control section 35, the process proceeds to step 506 in FIG. The job output request is a request issued by the data output control unit 35 to search for a printable job.

At step 506, a job search process for waiting for printing is performed in the order registered in the job management table 39, and various information of the job registered in the job management table 39 is acquired. . If there is no job to be output, the process proceeds to step 514, the data output unit 36 is notified that there is no job to be output, and the process returns to step 404.

If a job to be output exists,
Proceeding to step 510, the job status of the job searched in the above processing is changed from “waiting for printing” to “printing”,
In the next step 512, the job information acquired in the process of step 506 is notified to the data output unit 36. Then, the process returns to step 404.

(11) If there is a job output completion notice from the data output control section 35, step 51 in FIG.
Go to 8. This job output completion notification is a request issued when the data output control unit 35 completes the output process.

At step 518, it is checked whether the output processing result of the job notified from the data output unit 36 is a normal end. If the output processing result of the job is normal end, the process proceeds to step 520, and all the entry information of the job is deleted from the job management table 39. Then, the process returns to step 404.

On the other hand, if the output processing result of the job is abnormally terminated, the job status is changed from "printing" to "pending" as the job information in the job management table 39, and the failure information is added to the processing information field. To store.
Then, the process returns to step 404.

(12) If there is a stop request from the main control unit 31, the process proceeds to step 524 in FIG. 11 to store the information of the job management table 39 and the file management table 38 in the spool 3B, and then the job management unit. All the processing of 34 is ended, and control is passed to the main control unit 31.

The main controller 31 to the job manager 34
When the stop request is issued to the other control unit (the data input control unit 32 and the data output control unit 35), it is already stopped. Therefore, in the stop processing in the job management unit 34, it is not necessary to confirm the synchronization with other control units.

Details of Processing by Data Output Control Unit 35 The data output control unit 35 executes the control routine shown in FIG. First, in step 552 of FIG. 12, a process of reading printer management information, which is registered in the printer server 30 in advance and in which output destination information is stored, is performed. In the next step 554, all the corresponding data output units 36 are activated based on the information acquired by the reading process.
When the data output unit 36 is activated, a process of setting information in the data output unit management table 3A shown in FIG. 16 is also performed.

After activating all the data output sections 36 in this way, the process proceeds to step 558 and waits until the main control section 31 issues a stop request.

When the stop request is issued from the main control unit 31, the process proceeds to step 562 and the stop request is issued to the activated data output unit 36 registered in the data output unit management table 3A shown in FIG. Then, the processing waits until the processing in all the data output units 36 is completed. Then, when the stopping process of all the data output units 36 is completed, the process of FIG. 12 is ended and the control is passed to the main control unit 31.

Details of Processing by Data Output Unit 36 The data output unit 36 executes the control routine shown in FIG. First, in step 602 of FIG. 13, a check process of a stop request issued from the data output control unit 35 is performed, and if a stop request is issued, an end process is immediately performed, and the data output control unit 35 is notified. Pass control

If the stop request has not been issued, the process proceeds to step 606, and a search request process is performed to the job management unit 34 to check whether or not there is a printable job.

Thereafter, the response information from the job management section 34 is checked, and if there is no job to be processed, the process returns to step 602. On the other hand, if there is a job to be processed, the process proceeds to step 610, various print information of the output target notified from the job management unit 34 is acquired, initial setting processing is performed, and output page range information check processing is performed. I do.

At the next steps 612 and 614, it is checked whether or not a temporary stop request (Wait request) or a process cancel request has been issued by the job management unit 34 (note that the process management request is issued).
This request check process is performed every page processing unit).

An event occurs in each of the above requests according to an instruction from the client 20. If the request is not issued by the job management unit 34, the process proceeds to step 628 described later.

When a process suspension request notification is received from the job management unit 34 in steps 612 and 614,
Proceeding to step 616, the current output process is immediately stopped, and the process is awaited until there is an instruction from the job management unit 34.

If a cancel instruction is accepted from the job management unit 34, the processing is immediately stopped and the job management unit 3
4 is notified that the processing has been normally performed (step 64).
0). Then, after deleting the job data from the spool 3B, the process returns to step 602.

Further, in step 616, the job management unit 34
When the re-processing instruction is received from step S61, the process is initialized from the initial setting process of the process of the print job.
Return to 0.

Further, in step 616, the job management unit 3
If the instruction to cancel the suspension is received from step 4, step 6
2 and 624 from the job management unit 34 at the same time.
It is checked whether the information shown in 4 has been notified. Figure 2
When the information of No. 4 is not notified (when the output-completed page is not included), the process proceeds to step 628 described below to continue the output process of the job. When the information of FIG. 24 is notified (including the output completed page),
Output page range setting information is compared with the information currently being processed, and if the specified page has already been output, the output page resetting process is performed to return to the specified page and perform re-output processing. (Step 626) and the process proceeds to step 628 described later.

When the processing cancel request is received from the job management unit 34 in the above steps 612 and 614, the process proceeds to step 638, the processing is immediately stopped, and the job management unit 34 is informed that the processing is normally performed. Notice. Then, after deleting the job data from the spool 3B, the process returns to step 602.

Furthermore, when a data output request is received from the job management unit 34 in the above steps 612 and 614,
In step 628, one page of the job data is read from the spool 3B based on the job information notified by the job management unit 34, and is output to the printer of the output destination device.

If any failure occurs in the data input / output processing of step 628, step 63
In step 6, the job management section 34 is immediately notified of the output completion together with the failure information. Then, after deleting the job data from the spool 3B, the process returns to step 602.

Before the data input / output process of step 628 is completed for all the print job data, the process returns to step 612, and the instruction content from the client 20 is checked again. If the data output request continues, the data input / output process of step 628 is performed again.

In this way, the print job data is output page by page, and when the data input / output process of step 628 is completed for all the print job data, the process proceeds to step 634, and the job management unit Notify that the processing has been completed normally to 34. Then, after deleting the job data from the spool 3B, step 60
Return to 2.

By the control processing routine in each control unit in the client 20 and the printer server 30 described above, the print control in the printer server 30 based on the print request from the client 20 and the edit request of the print data and the print information described above is performed. Editing of print data and print information is realized.

As a result, it becomes possible to change the print information and print data of a print job that has already been queued. Therefore, a cancel request for the print job is issued and a print job output request in which the print information and print data have been partially modified is issued. Therefore, it is possible to improve the operability of the print job and reduce the unauthorized printing.

Further, the similar job search function is used to newly register new print job information based on the print job information of the print jobs already registered in the job management table.
It is possible to easily perform processing such as replacement of existing print job information with new print job information, deletion of existing print job information (= cancellation of print job), and the like.

In the above embodiment, the configuration example 3 of FIG.
Although the example in which the printer server 30 controls the queuing of the print job has been described in the above, the present invention describes a case in which the client 20 and the printer 40 perform the queuing control of the print job in the configuration example 3, FIG. It is also applicable to the network system having the configuration shown in FIG.
The same effect as above can be obtained.

[0319]

As described above, according to the present invention,
Since the print information of the print job and which has been requested by the setting error and operation error and print data can be changed even after queuing of the print job, performs a cancellation request for the print job, and modify some of the print information and print data It is not necessary to request the output of the print job again, and it is possible to improve the operability of the print job and reduce the unauthorized printing.

[Brief description of drawings]

FIG. 1 is a diagram showing a first configuration example of a network system to which the present invention can be applied.

FIG. 2 is a diagram showing a second configuration example of a network system to which the present invention can be applied.

FIG. 3 is a diagram showing a third configuration example of a network system to which the present invention can be applied.

FIG. 4 is a schematic configuration diagram of a network system according to the present embodiment.

FIG. 5 is a flowchart showing a processing routine of print request issuing processing in the client.

FIG. 6 is a flowchart showing a subroutine of print job edit request processing.

FIG. 7 is a flowchart showing a processing routine of processing executed by a main control unit of the printer server.

FIG. 8 is a flowchart showing a processing routine of processing executed by a data input control unit of the printer server.

FIG. 9 is a flowchart showing a processing routine of processing executed by a data transmitting / receiving unit of the printer server.

FIG. 10 is a flowchart showing the first half of the processing routine of the processing executed by the job management unit of the printer server.

FIG. 11 is a flowchart showing the latter half of the processing routine of the processing executed by the job management unit of the printer server.

FIG. 12 is a flowchart showing a processing routine of processing executed by a data output control unit of the printer server.

FIG. 13 is a flowchart showing a processing routine of processing executed by a data output unit of the printer server.

FIG. 14 is a table showing an example of a job management table.

FIG. 15 is a table showing an example of a data transmission / reception unit management table.

FIG. 16 is a table showing an example of a data output unit management table.

FIG. 17 is a table showing an example of a file management table.

FIG. 18 is a diagram showing an example of a data format at the time of issuing various requests.

FIG. 19 is a diagram illustrating an example of a data format when a print request is issued.

FIG. 20 is a diagram illustrating an example of a data format when a print job replacement request is issued.

FIG. 21 is a diagram illustrating an example of a data format when a print job registration request is issued.

FIG. 22 is a diagram illustrating an example of a data format when a print job cancellation request is issued.

FIG. 23 is a diagram illustrating an example of a data format when a print job edit request is issued.

FIG. 24 is a diagram showing an example of a data format when editing data is registered.

FIG. 25 is a diagram showing an example of a data format at the time of responding to a similar job list.

FIG. 26 is a diagram showing changes in the contents of the job management table during job replacement processing.

FIG. 27 is a diagram showing an outline of a file management method using a file management table.

FIG. 28 is a diagram showing an outline of a file management method at the time of editing data.

[Explanation of symbols]

10 network system 12 networks 20 clients 30 printer server 34 Job Management Department 39 Job management table 40 printers

Continuation of front page (58) Fields surveyed (Int.Cl. ⁷ , DB name) G06F 3/12 B41J 29/00

Claims (6)

(57) [Claims] 1. At least a client terminal device connected via a network or locally connected,
A printer and a print job based on a print job request issued from the client terminal device are sequentially queued, and the print information set by the client terminal device included in the print job and printed by the printer device are printed. And a printer server that manages print job information including print data, wherein the client terminal device displays information, and the print information managed by the printer server. And the mark
Display control means for acquiring the print job information including print data from the printer server and displaying the acquired print job information on the information display means, and changing the print job information displayed on the information display means Changing means for changing the print job and the changed print job changed by the information changing means
An information notifying unit for notifying information to the printer server, wherein the printer server is the print job after the change notified by the information notifying unit.
Network system by the information, to change the print job information applicable, be characterized. 2. The information notifying means is a print job after the change.
2. The network system according to claim 1 , wherein, when the print information is notified , only the changed portion of the print data after the change is notified regarding the print data. 3. The printer server manages a print job whose print job information is being changed as an output hold state, and when another print job exists, gives priority to the other print job and executes the processing. 1 or claim 2 further comprising first holding control means for controlling
The network system described in. 4. The printer server, when a print job whose print job information is to be changed is in the process of printing, stops the print processing of the print job and, after receiving the change request from the client terminal device, changes the print job. 3. The network system according to claim 1, further comprising a first stop control unit that controls to cancel, re-output, or continue the print processing of the print job according to the request content. 5. A printer server, which is connected to a client terminal device via a network or locally connected, sequentially controls queuing of print jobs based on a print job request issued from the client terminal device, and prints the print jobs. contained in the job, and the job management unit that manages print job information including the print information has been set, and print data to be printed by the printer apparatus by the client terminal device, the printing managed by the print job manager Information and
The print data to acquire the print job information including the sending to the client terminal device, the print job that the transmission
Print information after the client device has changed the print information.
A data receiving unit for receiving a notification of the probe information, wherein the data transceiver is, when receiving the notification, changes the print job information corresponding to the print job information after the notified to the job managing unit changes The printer server, wherein the job management unit changes the corresponding print job information among the managed print job information in response to a request from the data transmission / reception unit. 6. A printer server for performing print processing based on a print job request issued by at least a client terminal device connected via a network or locally connected, wherein the print job request issued by the client terminal device is A print job including print information of a print job based on the print job and print data to be printed, and
The print job including the print information and the print data.
Printer server that when receiving the notification of the probe information, changing the appropriate print job information of the print job information managed by the print job information <br/> the changed characterized in that.