JP3344150B2 - Job scheduling device - Google Patents

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a job scheduling apparatus for scheduling a plurality of print jobs, and more particularly, to a job scheduling apparatus capable of easily changing print attributes of a received print job.

[0002]

2. Description of the Related Art Conventionally, in a printing system such as a printing system and a copying system, printing attributes (hereinafter referred to as "attribute information") including a paper size, a tray number, the presence or absence of double-sided printing, and the like for print data. There is known a technique for performing a printing process based on the attribute information.

For example, when print data or copy data is output, attribute information such as a paper size to be output, the number of pages, and the presence or absence of double-sided printing is set, and the attribute information is sent to an output device together with document data or copy data. By transmitting the data, the data is output in a desired format.

[0004] As described above, when a print request is made, the printing process is performed based on the attribute information, and thus handling of the attribute information is important.

[0005]

However, according to the prior art, a user who makes a print request or a terminal device used by the user adds attribute information. Is accepted as a print job, it is not permitted to modify the attribute information.

Therefore, when the user specifies the attribute information by mistake, or when the terminal device gives the default attribute information because the user forgets to specify the attribute information,
It is necessary to cancel the print job once and make a print request to which desired attribute information is added again.

For this reason, there has been a problem that the load on the user is increased and the network use efficiency is reduced due to the re-registration of the print request, and that a time delay occurs before the print output is obtained.

That is, when such attribute information is specified incorrectly, it is important to increase the burden on the user, decrease the network use efficiency, and reduce the print waiting time.

In order to solve the above-mentioned problems, the present invention provides a method for reducing the burden on the user, reducing the network use efficiency, and reducing the print waiting time, even if the attribute information is specified incorrectly. It is an object of the present invention to provide a job scheduling device capable of easily changing information.

[0010]

In order to achieve the above object, the invention of claim 1 comprises print data for which a processing request has been received from a terminal device and attribute information for outputting the print data in a desired format. When a job scheduling device that sequentially stores print jobs in a queue and sequentially processes the print jobs held in the queue using a job execution unit based on the attribute information, when an instruction to change the attribute information of the print job is received. And an attribute changing means for changing the attribute information. According to another aspect of the invention, a print job including print data for which a processing request has been received from a terminal device and attribute information for outputting the print data in a desired output format is sequentially stored in a queue and held in the queue. And a plurality of queues provided corresponding to the status of the print job, and the plurality of queues, the plurality of queues being provided in correspondence with the status of the print job. Scheduling means for scheduling a job, when the instruction to change the attribute information of the print job is received, the print job can change the attribute information, and the instruction to change the attribute information is correct. Attribute changing means for changing the attribute information only in the case. According to a third aspect of the present invention, in the first or second aspect, the attribute information includes at least one of a sheet size to be output, a tray number, and whether or not double-sided printing is performed.

[0011]

According to the first aspect of the present invention, when an instruction to change attribute information for outputting print data of a print job in a desired format is received, the designated attribute information is changed. According to the second aspect of the present invention, when an instruction to change attribute information for outputting print data of a print job in a desired format is received, whether the print job is in a state where the attribute can be changed is determined. Of the attribute information to be corrected and whether there is any error in the instruction to change the attribute information to be corrected. As a result of these checks, the print job is in a state where the attribute can be changed, and the instruction to change the attribute information to be corrected is incorrect. Only when it is determined that there is no attribute information, the designated attribute information is changed.

Thus, according to the first aspect of the present invention, even if the user erroneously specifies the attribute information for outputting the print data in a desired output format, the burden on the user, the reduction in network use efficiency, and The attribute information can be easily changed while reducing the print waiting time. Also,
According to the second aspect of the present invention, even if the user erroneously designates attribute information for outputting print data in a desired format, it is possible to reduce the burden on the user, decrease network use efficiency, and reduce print waiting time. In addition, it is possible to easily change the attribute information while preventing a situation in which matching cannot be achieved after the attribute information is changed.

[0013]

An embodiment of the present invention will be described below with reference to the drawings.

FIG. 1 is a block diagram showing the overall configuration of a job processing system used in the first embodiment and the detailed configuration of a job scheduling device.

As shown in FIG. 1, the job processing system includes terminal devices 11a and 11
b, a job scheduling device 1 that performs scheduling when processing a job using the job execution unit 13
2 is connected to the network 10.

In this embodiment, the job execution unit 13
Consists of two printers that perform print processing and one converter that performs format conversion and the like.

The job scheduling device 12 includes a request control unit 12a, a job scheduling unit 12b,
A job execution unit control unit 12c, a queue management unit 12d,
It comprises a spool queue q1, a hold queue q2, a weight queue q3, a pause queue q4, printer queues q5 and q6, and terminate queues q7 and q8.

The request control unit 12a is a processing unit that requests the job scheduling unit 12b to schedule a job when receiving a job processing request from the terminal devices 11a and 11b.

The jobs received by the request control unit 12a include a one-job one-document job in which one job includes only one document, and a one-job multi-document job in which one job includes a plurality of documents. There is.

A one-job multi-document job includes a job of a post-reception completion processing method (After Complete J).
ob: Hereinafter referred to as “AC job”. ) And a job of a pre-reception completion processing method (Before Complete Job: hereinafter referred to as a “BC job”).

The AC job is to output the job to the job scheduling unit 12b after receiving all the documents included in the job, and the BC job sequentially receives the documents included in the job as soon as the documents are received. This is output to the job scheduling unit 12b.

The job scheduling unit 12b stores the job received from the request control unit 12a in the queue management unit 12b.
A processing unit that performs scheduling by performing queue operation using d.

Specifically, print data and attribute information included in a received job are stored in a master file (not shown), and information for performing queue management based on the attribute information of the job (hereinafter referred to as “job information”). ") And perform job queue operations.

The job scheduling unit 12
b includes an attribute change processing unit 12e that changes attribute information in response to a request to change attribute information of a job.

The attribute change processing unit 12e confirms whether or not the job is in a state in which the attribute can be changed when the request for changing the attribute of the job is received. A processing unit that changes the attribute information after checking whether or not the attribute information to be used is appropriate.

The job execution unit control unit 12c is a processing unit that outputs a job processing request from the job scheduling unit 12b to the job execution unit 13.

The queue management unit 12d has a spool queue q
1. A management unit that manages a job queue by holding job information in any one of a hold queue q2, a weight queue q3, a pause queue q4, a printer queues q5 and q6, and a terminating queues q7 and q8.

The job managed by the queue management unit 12d belongs to any one of the eight queues unless the job is deleted by the user or the system.

The spool queue q1 is a queue for queuing the job information of the AC job. The job information is held in the spool queue q1 until all the documents included in the job are received. Then, when all the documents are collected, the job information is transferred to a printer queue provided for the printer to be used.

The hold queue q2 is a queue for queuing job information of a non-scheduled job that is not scheduled, and the job information held in the hold queue q2 can be edited by a user.

The job information held in the hold queue q2 waits in this queue until there is an instruction from the user, and responds to the user's instruction in response to the spool queue q
1 or transferred to the printer queue q5 or q6.

The wait queue q3 is a queue for queuing the job information of the job waiting for the password input when the job times out. The job information held in the wait queue q3 stores the password information by the password input by the user. Is held in this queue until the state is released. When the password is released, the job information is transferred to a queue located when a timeout occurs.

The pause queue q4 is a queue for queuing job information of a job instructed to be temporarily stopped by a user's instruction. The job information held in the pause queue q4 is stored until a restart instruction is issued by the user. During this time, it is held in this queue. When a restart instruction is given by the user, the job information is transferred to the assigned printer queue.

The printer queues q5 and q6 are queues provided corresponding to the printers for queuing the job information of the jobs waiting to be printed, and only the job information of the job assigned to each printer corresponds to the corresponding printer queue. Queued in the queue.

In the present embodiment, one of the two printers provided in the job execution unit 13 corresponds to the printer queue q5, and the other printer corresponds to the printer queue q6.

For a job whose job information is held in the printer queue q5 or q6, if the printer is ready for processing and there is a processable document in the first job of the printer queue q5 or q6, the processing request is issued. Is made. When the printing process by the printer is completed, the job information of the job is transferred to the terminating queue q7 or q8.

The terminating queues q7 and q8 are queues provided corresponding to the printers for queuing the job information of the printed jobs. Only the terminating queues corresponding to the job information of the jobs assigned to each printer are provided. Queued to.

By using the job scheduling device 12 having the above-described configuration, it is possible to perform queue management according to the status of a job and to change the attribute of the job if possible by checking the status of the job as appropriate. Become.

In this embodiment, the case where the job execution unit 13 has two printers will be described. However, the number of printer queues and terminating queues is determined by the number of registered printers held in the job execution unit 13. Determined in response to.

Next, the structure of job information queued in each queue will be described.

FIG. 2 is an explanatory diagram showing the structure of job information queued in each queue.

As shown in FIG. 2, the job information includes a job ID indicating a job identification number and a docsecNum used for document identification of a one-job multi-document.
And currentDocN in which docsecNum that issues a print request is set
um and status (status) 20a indicating the status of the job
And prevQID indicating the queue ID held previously
, JobCopyCount indicating the number of copies, and requestCou indicating how many times the document is requested to be printed to the job execution unit
nter and co indicating how many times the document has been processed
mpleteCounter, abortedCounter indicating the number of times aborted as an error during document processing, collateFlag indicating whether to perform collation, resumeFlag indicating whether or not to resume, and prev indicating previous status
iousStatus, retry indicating a retry counter when rejected by the job execution unit, complete indicating whether or not the last document, and ID of the request converter
ConvertID indicating how many pages the job has output, ohPagesComp indicating how many pages the document has output, ohDocPagesComp indicating how many pages the document has output, and ohCu indicating the current job status
rJobState and ohPrevJobStat indicating previous job state
e and ohJobStateRea indicating the reason for transition of the current job state
It consists of a son, an ohAssignJEID indicating the ID of the printer assigned by the printer selection, a retryCounter indicating the number of retries after recovery, and a processingFlag indicating whether or not printing is in progress.

The status (status) 20a includes: a status indicating that the printer is waiting for processing at the pending printer; a requesting print request is being made; a printing print process is being performed; an aborting cancel process is being performed; suspended pause processing ・ startwaiting waiting for start ・ passwordwaiting waiting for password input ・ endwaiting end waiting ・ convert_pending waiting for conversion request ・ convert_requesting waiting for conversion request response ・ converting being converted ・ convert_end conversion end ・ passwd_release password release ・ passwd_timeout password timeout ・ terminated output End ・ convert_failed Conversion processing failure ・ job_aborted print processing abort ・ interrupted interrupt waiting ・ convert_aborting conversion cancel processing in progress ・ convert_canceled conversion cancellation Exit · none there is a state of indefinite, and the like.

By performing job status management using the job information including the above members, detailed scheduling of jobs becomes possible.

Next, the job attribute change processing performed by the attribute change processing unit 12e shown in FIG. 1 will be described.

The attribute change processing unit 12e checks (1) whether or not the job is in a state in which the attribute can be changed;
(2) It is checked whether the attribute information to be corrected is appropriate, and if the attribute information can be changed, the attribute information of the job is changed.

Specifically, in the check (1) for checking whether or not the attribute can be changed, (1a) whether the job information of the job for which the attribute change is specified exists in the hold queue q2 (1b) The job information of the job whose attribute change is specified exists in the printer queue q5 or q6,
Whether or not the job is not currently being processed and has never been processed in the past is determined. (1c) The job information of the job for which the attribute change is specified exists in the pause queue q4, and the job has not been processed in the past. It is checked whether or not processing is in progress.

Hereinafter, each of them will be described.

(1a) The job information is a hold queue q2
The job whose job information is queued in the hold queue q2 is a non-scheduling job specified by the user as described above, and the user waits for an instruction from the beginning.

Therefore, the job information is stored in the hold queue q
If the job exists in No. 2, it means that no processing has been performed yet since the job was accepted, so that the attribute of the job can be changed.

Incidentally, for this hold queue q2,
Waiting for start (startwaiting), Waiting for end (endwai
ting) and waiting for password input (passwordwaiting)
In the case where the job is held, it may be configured not to allow the change of the attribute information in consideration of the waiting process. However, in this embodiment, for the sake of convenience, the non-scheduling specified by the user is performed. The explanation focuses on the job.

(1b) Job information is stored in the printer queue q5
Or, check whether or not the job exists in the printer queue q6 and has not been processed at least once in the past or in the past. Is not performed, so the attribute can be changed.

However, if a pause instruction is given while the job is being processed, and the job temporarily transferred to the pause queue exists in the printer queue q5 or q6 due to the resume instruction, the print processing has already been completed. No attribute change is allowed in order to match the document with the document to be processed.

(1c) Check Whether Job Information Exists in the Pause Queue q4 and Whether the Previous Job State is Under Processing The job whose job information is held in the pause queue q4 is
Since it is out of the processing target because of receiving the suspension instruction, it is possible to change the attribute information in principle.

However, among the jobs whose job information is held in the pause queue q4, a job whose printing is instructed to be suspended is included in the job being printed, so that the attribute information of the job whose printing has been stopped is changed. If this is done, it will not be possible to match a document that has already undergone print processing with a document that will undergo print processing later.

For this reason, if the previous job state is being processed, no attribute change is permitted.

As described above, the attribute change processing unit 12e checks the queue in which the job information of the job whose attribute is specified to be changed exists, and permits the attribute change when the job exists in the hold queue q2. And the job is a printer queue q5 and q6 or a pause queue q4.
, The attribute change is permitted on condition that the previous job state is not being processed.

Next, a description will be given of a procedure for confirming the job status performed by the attribute change processing section 12e.

FIG. 3 shows the attribute change processing unit 12e shown in FIG.
9 is a flowchart showing a procedure for checking a job state performed by the user.

As shown in FIG. 3, when an instruction to change the attribute information of a job is received, it is checked in which queue the job information of the specified job exists (step 3).
01), if the job information does not exist in any of the queues, an error notification is sent to the user (step 3).
02, 303).

On the other hand, if the job information exists, it is checked whether or not the job is being processed (step 3).
04) If the job is being processed, the attribute information cannot be changed (step 309), and the process ends.

On the other hand, if the job is not being processed, it is confirmed whether or not the job information of the job is held in the hold queue q2 (step 305). Is considered to be possible.

The job information is stored in the printer queue q
5 or q6 or in the pause queue q4 (step 306), it is further checked whether or not the previous job state is being processed (step 307).

Specifically, it is checked whether or not the previous job state (previous_job_state) of the job information is being processed (processing), thereby checking whether or not the job has been processed before.

As a result, if the previous job state is not being processed, it is considered that the attribute information can be changed (step 308). If the previous job state is being processed, the attribute information is not changed (step 308). 309).

The job information is stored in the hold queue q2, the pause queue q4, the printer queue q5 or q6.
If the job exists in a queue other than, the change of the attribute information of the job is not permitted (step 309).

That is, if the job information exists in the terminating queue q7 or q8, the processing of the job has already been completed, and the job information is stored in the spool queue q7.
1, if the AC job has not been accepted, and if the job information is in the wait queue q4, the job is waiting for a password input. This is because the information should not be changed.

By performing the above series of processing, when an instruction to change the attribute information of a job is received, it is possible to confirm whether or not the attribute information can be corrected based on the job status of the job.

Next, the attribute change processing section 12e performs (2)
Checking whether the attribute information to be corrected is appropriate will be described.

When the job is in a state in which the attribute information can be modified, the attribute information can be modified in principle. However, when the user tries to add erroneous attribute information, such modification is permitted. Should not be.

Therefore, here, regarding the attribute information to be modified specified by the user, whether (2a) an attribute not supported as an attribute by the job scheduling apparatus 12 is specified or (2b) a single value (Single_Value) Where multiple values (Multi_Valu
e) is not added, or (2c) the attribute information of the job of the second and subsequent documents is not specified. That is, in the case of using a one-job multi-document, the attribute information of the job is provided for each document. If the attribute information of the first document must be changed in order to change the attribute information of the job, the attribute information of the job of the second and subsequent documents Check three points to see if you have specified.

FIG. 4 is a flowchart showing a procedure for confirming the attribute information performed by the attribute change processing unit 12e.

As shown in FIG. 4, upon receiving the modified attribute information specified by the user, it is first checked whether the attribute information includes an attribute not supported by the job scheduling device 12 (step 401). If an unsupported attribute is included, an error notification is made (step 402), and the process ends.

On the other hand, when the job scheduling device 12 consists of only the attributes supported, a single value (Si
(ggle_Value) as an attribute value was checked to see if multiple values (Multi_Value) were assigned (step 403), and if multiple values were assigned, an error notification was issued. Later (step 402), the process ends.

On the other hand, if a plurality of values have not been assigned, it is confirmed whether or not job attribute information of the second and subsequent documents has been specified for one job multi-document (step 404). If the second and subsequent documents are specified, the process is terminated after an error notification is made (step 402).

On the other hand, when the attribute information of the job of the first document is specified, it is checked whether or not a document number (document_sequencial_number) is specified.

As a result, if the document number is specified, only the specified document is changed in the attribute information (step 406). If the document number is not specified, all the documents included in the job are deleted. After the attribute information is changed (step 407),
Assuming that the attribute information can be changed (step 40)
8) End the process.

By performing the above-described series of processes, it is possible to reduce the possibility that the user attempts to assign erroneous attribute information.

Next, a description will be given of a procedure for changing the attribute information performed after the attribute change processing unit 12e completes the confirmation of the job status shown in FIG. 3 and the confirmation of the attribute information shown in FIG.

When the user changes the attribute information, a modify operator (modify operator) and an attribute value (v
alue). At that time, qualifier (qualifie
r) can also be specified at the same time. Modify operator without specifying attribute value
And qualifiers can also be specified.

The qualifier is a parameter indicating either true or false. When a job is executed, an attribute for which the qualifier is set to true must always be processed with the specified attribute value. If the qualifier cannot process the attribute set to true with the specified attribute value, the job is processed as an error.

For example, if true is specified for the qualifier of the attribute for specifying the paper size of a certain job and A4 is specified for the attribute value of the attribute, the job is always printed on A4 paper when the job is executed. Must print, A4
If the job cannot be printed on the sheet, the job is processed as an error.

Also, a modify operator (modify o)
perator) includes replace, add, remove value, or default setting (set_to_defaul
t) can be specified.

Note that this modify operator (modi
The case where the default setting (set_to_default) is specified in (fy operator) will be described in a second embodiment described later.

FIG. 5 shows the attribute information changing unit 12e shown in FIG.
9 is a flowchart showing a processing procedure when changing attribute information.

As shown in FIG. 5, first, it is checked whether or not a modify operator (modify operator) has been designated (step 501). If the modify operator has not been designated, an error occurs. The process is performed (step 502), and the process ends.

On the other hand, a modify operator (modify o)
If the qualifier has been designated, it is further confirmed whether or not the qualifier has been designated (step 503). If the qualifier has been designated, the qualifier is designated as instructed. The value is corrected (step 504), and if the qualifier is not designated, the flow directly proceeds to step 505.

Next, it is checked whether or not an attribute value (value) is specified (step 505). If no attribute value is specified, a modify operator (modify operator) is further determined.
It is determined whether or not (tor) is the default setting (set_to_default) (step 506).

As a result, when the attribute value is specified and when the attribute value is not specified but the default setting is made, the attribute value is corrected (step 507), and the attribute value is specified. If no default setting has been made, the process ends.

By performing the above series of processing, it is possible to confirm whether or not the qualifier and the attribute value have been modified according to the status of the modify operator and the setting status of the qualifier or attribute value. it can.

The first embodiment has been described above.

By the way, in the first embodiment, the case where the user sets the attribute value by himself / herself is described, and the description about the case where the default value is used is omitted. In addition, a description will be given of a second embodiment capable of performing attribute change using a default value.

FIG. 6 is a diagram showing the overall configuration of a job processing system used in the second embodiment.

As shown in FIG. 6, the job scheduling apparatus 12 has an attribute change processing section 60a that allows the user to set an attribute value by himself / herself and change an attribute using a default value.

When the attribute change processing unit 60a receives an attribute change instruction using a default value, the attribute change processing unit 60a can appropriately extract default attribute information from the default profile 60b storing default attribute information.

More specifically, the user sets the modify operator (modify operator) to the default setting (set_to_de
fault), and if the attribute change processing unit 60a receives the default setting (set_to_default), a necessary default value is extracted from the default profile 60a.

The default profile 60a is a storage unit for storing default attribute information, and can prepare a plurality of default profiles in which different default values are set. When the user sets a default, it is possible to select a default profile having desired attribute information and input the file name to change the default profile to the desired attribute information.

Next, specific examples of the case where the attribute is changed without using the default attribute information and the case where the attribute is changed using the default attribute information will be described.

FIG. 7 is a diagram showing an example of a case where the attribute is changed without using the default attribute information and a case where the attribute is changed using the default attribute information.

As shown in FIG. 7A, job attribute information 70a includes five attributes A (= a1), B (= b1),
In the case of C (= c1), D (= d1) and E (= e1), an instruction 70b from the user to change the attribute B to b2
Upon receiving the attribute information, the attribute change processing unit 60a generates new attribute information 70c in which the attribute B designated by the user has been changed from b1 to b2 among the five attributes.

On the other hand, as shown in FIG.
If there are three types of profiles, default profiles X, Y, and Z, and an instruction 71b for changing the attribute B using the default profile X is received, the value b3 of the attribute B from the default profile X
The attribute information 70a is changed using the attribute value b3.

Thus, new attribute information 71c in which the attribute value of the attribute B has been changed to b3 can be obtained.

In the case of a one-job multi-document, the number of documents included in the job differs for each job. For this reason, when an attribute change instruction using the default is specified by designating a job instead of a document, a default value is set to the attribute information of the job of all documents included in the job. .

However, if the user knows the number of documents included in one job, the attributes of the default profile X are applied to documents 1 and 2, and the attributes of the default profile Y are applied to documents 3 and 4. Can be specified.

Next, the processing procedure performed by the attribute change processing section 60a will be described.

FIG. 8 shows the attribute change processing unit 60a shown in FIG.
5 is a flowchart showing an attribute change processing procedure performed by the user.

As shown in FIG. 8, first, when an instruction to change attribute information is received, it is checked whether or not an attribute value has been designated by the user (step 80).
1) If the attribute value is specified, the attribute value is used (step 802). If the attribute value is not specified, the attribute value held in the default profile is used (step 803).

Here, when there are a plurality of default profiles, if a default profile is specified, the attribute value of the default profile is used. If no default profile is specified, the first profile is used. Use attribute values.

Then, it is confirmed whether the job is a one-job multi-document (step 804). If the job is one-job one-document, the attribute information is corrected using the attribute value (step 805). .

On the other hand, if the job is a one-job multi-document, it is confirmed whether or not a profile having an attribute to be changed is specified for a document (step 806). If not, the attribute information is corrected for all documents with the same attribute value (step 807).

On the other hand, if the document correspondence is specified, the attribute information is corrected with the attribute value specified for each document (step 808), and the process ends.

By performing the above series of processing, the attribute information can be changed using not only the attribute value designated by the user but also the attribute value stored in the default profile.

As described above, in the first embodiment,
If a print request for a print job is received from the terminal device 11a or 11b, the job scheduling unit 12b
Performs the scheduling of the print job while transferring the queue storing the print job according to the state of the print job. Then, if an instruction to change the attribute information of the print job is received during the scheduling of the print job, the attribute change processing unit 12e is in a state where the print job can change the attribute information and the attribute information is changed. Since the attribute information is changed only when there is no error in the instruction, it is possible to reduce the burden on the user, decrease the network use efficiency, and reduce the print waiting time even when the attribute information is specified incorrectly. The attribute information can be easily changed.

In the second embodiment, the attribute change processing unit 60a is configured to take out the default attribute value from the default profile 60b and correct the attribute information when the default is specified. Can correct the attribute information without specifying the attribute value itself.

In the first and second embodiments, the case where the attribute change processing unit 12e is provided in the job scheduling unit 12b has been described. However, it is also possible to provide the attribute change processing unit 12e independently of the job scheduling unit. is there.

[0116]

As described above in detail, according to the first aspect of the present invention, when a change instruction of attribute information for outputting print data of a certain print job in a desired format is received, the instruction is given. The attribute information is changed, so that even if the user incorrectly specifies the attribute information for outputting the print data in a desired output format, the burden on the user, the reduction in network use efficiency, and the print waiting time Attribute information can be easily changed while reducing the number of attributes.
According to the second aspect of the present invention, when a change instruction of attribute information for outputting print data of a certain print job in a desired format is received, whether the print job is in a state where the attribute can be changed. The print job is checked whether there is any error in the change instruction of the attribute information to be corrected, and as a result of the check, the print job is in a state where the attribute can be changed, and the change instruction of the attribute information to be corrected is performed. The attribute information specified is changed only when it is determined that there is no error, so that even if the user incorrectly specifies the attribute information for outputting the print data in the desired format, Attribute information can be changed easily while reducing the burden on the network, lowering network usage efficiency, and reducing the printing wait time, and preventing situations in which matching cannot be achieved after changing the attribute information. It can be carried out.

[Brief description of the drawings]

FIG. 1 is a block diagram showing an overall configuration of a job processing system used in a first embodiment and a detailed configuration of a job scheduling device.

FIG. 2 is an explanatory diagram showing a configuration of job information queued in each queue shown in FIG. 1;

FIG. 3 is a flowchart showing a job status confirmation procedure performed by an attribute change processing unit shown in FIG. 1;

FIG. 4 is a flowchart showing a procedure for checking attribute information performed by an attribute change processing unit shown in FIG. 1;

5 is a flowchart showing a processing procedure when the attribute information changing unit shown in FIG. 1 changes attribute information.

FIG. 6 is a block diagram illustrating an overall configuration of a job processing system used in a second embodiment.

FIG. 7 is a diagram illustrating an example of a case where the attribute change processing unit illustrated in FIG. 6 performs attribute change without using default attribute information, and a diagram illustrating an example of a case where attribute change is performed using default attribute information.

FIG. 8 is a flowchart showing an attribute change processing procedure performed by an attribute change processing unit 60a shown in FIG. 6;

[Explanation of symbols]

10 network, 11a, 11b terminal device, 1
Reference numeral 2 denotes a job scheduling device, 13 denotes a job execution unit, 12a denotes a request control unit, 12b denotes a job scheduling unit, 12c denotes a job execution unit control unit, 12d a queue management unit, 12e denotes an attribute change processing unit, and q1 denotes a spool queue. ... hold queue, q3 ... wait queue, q4 ... pause queue, q5, q6 ... printer queue, q7, q8 ... terminate queue, 60a ... attribute change processing section, 60b ... default profile

Claims (3)

(57) [Claims] 1. A print job comprising print data for which a processing request has been received from a terminal device and attribute information for outputting the print data in a desired format are sequentially stored in a queue, and the print job held in the queue is stored in the queue. A job scheduling device that sequentially processes using a job execution unit based on attribute information, comprising: an attribute changing unit that changes the attribute information when an instruction to change the attribute information of the print job is received. Job scheduling device. 2. A print job, comprising print data for which a processing request has been received from a terminal device and attribute information for outputting the print data in a desired output format, is sequentially stored in a queue, and the print job held in the queue is stored in the queue. In a job scheduling device that sequentially processes using a job execution unit based on the attribute information, a plurality of queues provided corresponding to a state of the print job; and a scheduling of the print job using the plurality of queues. Scheduling means for performing, when receiving an instruction to change the attribute information of the print job, the print job is in a state in which the attribute information can be changed, and only when there is no error in the instruction to change the attribute information, A job scheduling apparatus comprising: an attribute changing unit that changes attribute information. 3. The job scheduling apparatus according to claim 1, wherein the attribute information includes at least one of an output paper size, a tray number, and whether or not double-sided printing is performed.