JPH07234740A - Job management method - Google Patents

Abstract

PURPOSE:To improve possibility that the execution of a job which a user having little remaining budget puts in completes and to prevent the occurrence of a loss owing to the execution interruption of the job. CONSTITUTION:A job usage charge estimate processing part 113 estimates a usage charge when the job whose execution is requested is executed in a designated job class or system. A job execution propriety judgment processing part 114 selects the job class or system having the high possibility that the usage charge is settled within the remaining budget when it judges that the remaining budget of the user putting in the job whose execution is requested is less than the estimated usage charge and indicates the transfer of the job whose execution is requested to a job transfer processing part 116. The job transfer processing part 116 transfers the job whose execution is requested based on an indication. Thus, it is reduced that the job is brought to an end during execution owing to the lack of the budget, and the occurrence of the loss owing to the execution interruption of the job can be prevented.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a job management method in a composite type computer system, and more particularly to a job management method suitable when an actual calculated value is close to a budget value.

[0002]

2. Description of the Related Art Generally, in a computer system, a "budget value" and a "calculated value" of a job are conventionally set and managed for each user in order to manage the usage status of the computer by the user. There is. The relationship between the budget value and the calculated value is as follows. The budget value is a constant value set by the system administrator prior to the execution of the job, and defines the upper limit of charging for evaluating the amount of computer resources used by each user. On the other hand, the calculated value is
It is a variable value having an initial value of zero, and indicates a cumulative value of charges used in the execution of individual jobs. That is, the value of the calculated value increases as the job is executed, and when the calculated value reaches the budget value, the user cannot execute the job.

Based on the above, the computer system constantly monitors the budget value and the calculated value of each user, and when the calculated value of a certain user exceeds the budget value, the execution by the user is being executed. A job management method that can charge the user a usage fee according to the computer resources used by the job by interrupting the job and controlling not to execute a new job submitted by the user Widely used (“Hitachi program product VOS3 integrated user management function TRUST E2
Introduction and operation "manual).

[0004]

In the conventional job management method described above, if the calculated value does not exceed the budget value at the start of execution of the job, execution of the job is unconditionally started. Therefore, if the calculated value of the user who submitted the job is slightly below the budget value, and when the calculated value of the user exceeds the budget value during the execution of the job, There is a problem that the execution of the job may be interrupted by the monitoring of the system, which wastes a part of the budget value given to the user.

By the way, in recent computer centers, it is becoming common to combine several types of computers to form a composite computer system. And
Especially in a research institute mainly engaged in non-standardized work, there is a computer center in which a user can arbitrarily specify any computer system to execute a job. In this case, if you execute the job on the computer system specified by the user, the execution of the job will be interrupted when the actual calculated value reaches the budget value, but if you execute the job on another computer system In some cases, the execution of the job is completed before the calculated value of the user reaches the budget value.

For example, in a computer center capable of arbitrarily specifying a general-purpose computer and a supercomputer to execute a job, a user "ZA1AN5" who currently has a difference between a budget value and an actual calculated value of 10 is a job "ZA1AN5J".
Consider the case of inputting B ”. At this time, if you execute the job“ ZA1AN5JB ”by specifying a super computer that can perform high-speed calculation and has a high billing rate, the actual calculated value of user“ ZA1AN5 ”will be the budget value after 3 minutes. Reached the job “ZA1AN5J
Execution of "B" will be interrupted. On the other hand, by specifying a general-purpose computer with a slow calculation speed but a low billing rate, the job "ZA1A
Run "N5JB" and after one hour the job "ZA1AN5JB"
Is completed, the difference between the budget value and the calculated value becomes 2.

Since the above may actually occur, the user always keeps track of his or her budget value and actual calculation value, and which computer system should be designated to submit a job to complete the job execution. Therefore, there is a problem that the user must be skilled in the system before the original work. In addition, if the execution of a job involving large-scale vector operations or large-capacity input / output data is interrupted by the above, it is necessary to re-execute all from the beginning, which results in economic and time loss. There was a problem that there was a great risk that it would become immeasurable.

Therefore, an object of the present invention is to solve the above problems and improve the possibility that the execution of a submitted job is completed when the calculated value of the user is close to the budget value, as compared with the prior art. And to provide a job management method capable of preventing the occurrence of loss due to interruption of job execution.

[0009]

[Means for Solving the Problems]

(1) In order to achieve the above object, the job management method of the present invention is a job for interrupting execution of the job when the actual value of the user who submits the job during execution of the job reaches a budget value. In the management method, based on a preset execution condition set in advance, the estimated charge used when executing the job is predicted, and the estimated calculated value obtained by accumulating the estimated charge to the calculated value is the budget. When it is determined that the estimated actual value based on the designated execution condition exceeds the budget value, it is determined whether the estimated actual value does not exceed the budget value. An alternative execution condition that replaces the execution condition is determined, and the execution of the job is started based on the alternative execution condition.

(2) In addition to (1), when the alternative execution condition cannot be determined so that the estimated actual value does not exceed the budget value, the estimated charge is minimized. It defines alternative execution conditions.

(3) In addition to (1) or (2), the designated execution condition and the alternative execution condition are information regarding a computer system or a job class in charge of executing the job, The data is transferred to the computer system or job class specified by the alternative execution condition.

(4) In addition to (3), the expected charging is predicted based on a computer system and a prediction database regarding a job class.

(5) Further, in addition to (4), the actual charge used when the job is executed is reflected in the prediction database.

(6) In addition to any of (1) to (5),
The actual billing used at the time of executing the job, the designated execution condition, and the alternative execution condition are notified to the user after the job is completed or interrupted.

[0015]

The operation based on the above configuration will be described.

(1) In the job management method of the present invention, when the actual value of the user who has submitted the job during execution of the job reaches the budget value, the execution of the job is interrupted in advance. Whether the estimated calculated value obtained by predicting the estimated charge used when the job is executed based on the specified execution condition and accumulating the estimated charge to the calculated value exceeds the budget value. If it is determined that the estimated actual value based on the designated execution condition exceeds the budget value, an alternative to the designated execution condition so that the estimated actual value does not exceed the budget value. By defining the execution condition and starting the execution of the job based on the alternative execution condition, it is possible to surely complete the execution of the job even when the calculated value of the user is close to the budget value,
It is possible to prevent the occurrence of loss due to interruption of job execution.

(2) In addition to (1), when the alternative execution condition cannot be determined so that the estimated actual value does not exceed the budget value, the estimated charge is minimized so that By defining alternative execution conditions, the probability that the execution of the submitted job will be completed when the calculated value of the user is close to the budget value is improved compared to the past, and the loss occurrence rate due to job execution interruption can be improved. It can be reduced.

(3) In addition to (1) or (2), the designated execution condition and the alternative execution condition are information relating to a computer system or a job class in charge of executing the job, and By transferring the job to the computer system or the job class designated by the alternative execution condition, it is possible to prevent the loss from occurring due to the interruption of the job execution or reduce the loss occurrence rate, and to effectively utilize the computer resources.

(4) Further, in addition to (3), the effective use of computer resources can be systematized by performing the prediction of the assumed charging based on the prediction database regarding the computer system and the job class.

(5) In addition to (4), by reflecting the actual billing used at the time of executing the job in the forecast database, effective use of computer resources according to the actual situation of the computer system. Can be optimized.

(6) In addition to any of (1) to (5),
By notifying the user of the actual billing used when the job was executed, the specified execution condition and the alternative execution condition after the job was completed or interrupted,
It is possible to let the user know how to set the designated execution condition according to the actual situation of the computer system so that the computer resources can be effectively used.

[0022]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS An embodiment of the job management method of the present invention will be described in detail below with reference to the drawings.

First, an outline of the job management method of the present invention will be described.

FIG. 1 is a diagram showing the overall construction of an embodiment of the job management method of the present invention. In the figure, 1 and 2 are independent computer systems, 3 is a job input device for inputting a job, 11 is a central processing unit of the computer system 1, and 12 is various computer resources (for example, an external storage device or a printing device). A device, etc., which may be specific to a specific computer system or shared between computer systems. 21 is a central processing unit of the computer system 2 41 is a usage charge prediction database (use charge prediction) Data corresponding to the forecast database in the claims.), 42 is a budget book for storing budget values for each user, which is set in advance by the system administrator, and 43 is executed in the past for each user. It is an actual account book that stores the cumulative value (actual calculation value) of the usage charge of computer resources by the jobs. Reference numeral 111 denotes an operating system in which a job reception processing unit 112, a job usage charge prediction processing unit 113, a job executability determination processing unit 114, a job execution control unit 115, and a job transfer processing unit 116 operate.

In FIG. 1, an execution request job (a job that has been submitted by the user and is waiting to be executed) input from the job input device 3 via the signal line 51 is first processed by the job acceptance processing unit 112 in the job class ( (For example, roughly specify the range and allowable amount of computer resources to be given to the job.) It is checked whether there is an error in the parameter specification, and if there is no error, the above-mentioned job was submitted. Is notified to the job usage fee prediction processing unit 113 via the signal line 57. The job usage fee prediction processing unit 113 refers to the usage fee prediction database 41 via the signal line 52 based on the specified job class and uses the usage fee when the execution request job is executed (the assumption in claims). (Equivalent to billing) is predicted, and the result is notified to the job executability determination processing unit 114 via the signal line 58. The job executability determination processing unit 114 receives the budget value of the user who submitted the execution request job from the budget book 42 via the signal line 54, and the actual book 43 to the signal line 5.
The actual calculation value of the user is read out via 5. Then, as a result of comparing the remaining budget with the predicted usage fee of the above-mentioned execution-requested job, when it is determined that the usage fee does not exceed the remaining budget, the job execution control 11 is performed via the signal line 59.
5 is informed that the execution process for the execution request job should be started. If it is determined that the usage charge exceeds the remaining budget, a computer system that can be executed within the remaining budget is selected from the usage charge prediction database 41 via the signal line 53, and the signal line 5a is used. Then, the job transfer processing unit 116 is requested to transfer the execution request job. The job transfer processing unit 116 transfers the execution request job to the selected computer system via the signal line 56.

Next, various data used in the job management method of the present invention will be described.

2 to 4 are diagrams showing the internal structure of the usage charge prediction database shown in FIG. In FIG. 2, the usage charge prediction database 41 includes a predicted usage charge table 411 for each job class for the computer system 1, a predicted usage charge table 412 for each job class for the computer system 2, and each computer system for each job class. Forecast usage charge table 4
It is composed of 13. In FIG. 3, the estimated usage charge table 411 for each job class for the computer system 1 shown in FIG.
And an item 41b in which an expected usage charge when a job is executed in the job class is stored. Although not shown, the predicted usage charge table 412 for each job class for the computer system 2 has the same configuration. In FIG. 4, the estimated usage charge table 413 of each computer system for each job class shown in FIG. 2 includes an item 41c in which the computer system name is stored and an estimated usage when the job is executed in the computer system. It is composed of an item 41d in which a charge is stored.

5 and 6 are views showing the internal structure of the budget book shown in FIG. In FIG. 5, the budget book 42 stores a user budget registration table 421. And FIG.
In the above, the user budget registration table 421 is composed of an item 42a in which a user name for identifying an individual user is stored and an item 42b in which a budget value determined in advance by the system administrator for the user is stored.

FIG. 7 and FIG. 8 are diagrams showing the internal structure of the actual account book in FIG. In FIG. 7, the user account management table 431 is stored in the account register 43. And FIG.
In the user calculation management table 431, an item 43a in which a user name for identifying an individual user is stored and a calculated value that is a cumulative value of the usage charges of computer resources by jobs of the user executed in the past are And 43b stored.

Next, details of each processing in the job management method of the present invention will be described.

FIG. 9 is a flow chart showing the operation of the job acceptance processing section in FIG. In the figure, the job reception processing unit 112 waits for a notification from the job input device 3 that the execution request job has been input (step 112).
a) Whether or not the designation of the job class in the execution request job is correct is checked depending on the contact (step 112b). If it is determined in step 112b that the job class has been specified incorrectly, a message indicating that the job class is invalid is output to the user who submitted the execution-requested job (step 112c), and then step 1
Return to 12a. If it is determined in step 112b that the job class is specified correctly, after notifying the job usage fee prediction processing unit 113 that the execution request job has been accepted together with the job class (step 112d),
Return to step 112a. Through the above processing, when the user submits the execution request job, it is possible to check the injustice of the job class which is the basis of the usage charge calculation in the usage charge prediction processing unit 113. In addition, even when the usage charge is predicted by a method other than the above-described job class prediction, it is possible to similarly check the incorrectness of the parameter specification that is the basis of the usage charge calculation.

FIG. 10 is a flow chart showing the operation of the job usage fee prediction processing section in FIG. In the figure, the job usage fee prediction processing unit 113 uses the usage fee prediction database 41 from the computer system 1 shown in FIGS. 2 and 3.
The predicted usage charge table 411 for each job class is read (step 113a). And step 113b
Waits for the notification of the execution request job reception from the job reception processing unit 112, and when the notification is received, reads the estimated usage charge 41b of the job class notified from the estimated usage charge table 411 for each job class for the computer system 1 Is performed (step 113c). Then, after the notified execution request job and its estimated usage charge are notified to the job executability judging processing unit 114 (step 113d), the step 1
Return to 13d. Through the above processing, it is possible to predict the usage fee of the execution request job submitted by the user before the execution fee is executed.

FIG. 11 is a flow chart showing the operation of the job executability judging processing section in FIG. In the figure, the job executability determination processing unit 114 is the budget book 4 shown in FIG.
The user budget registration table 421 shown in FIGS. 2 to 6 is read (step 114a). Then, it waits for notification of the execution request job and its estimated usage charge from the job usage charge prediction processing unit 113 (step 114b), and upon notification, the user who submitted the execution request job from the user budget registration table 421. The budget value 42b of is read (step 114c). Next, the actual account book 4 shown in FIG.
3 to the user actual calculation management table 431 shown in FIG. 8 (step 114d), and the actual calculated value 43b of the user is read from the user actual calculation management table 431 (step 114).
e). Then, by calculating the difference between the budget value 42b and the calculated value 43b, the remaining budget currently given to the user is calculated (step 114f), and then the prediction notified from the job usage charge prediction processing unit 113 is calculated. When the usage fee is compared with the remaining budget (step 114g) and it is determined that the remaining budget exceeds or is equal to the estimated usage fee, the job executability determination processing unit 114 executes the job execution control unit 115. After instructing to start the execution of the requested job (step 114n), the process returns to step 114b.
The job execution control unit 115 is a part conventionally provided in the operating system, and after step 114n, this execution request job is executed by the computer system 1.
And receive execution control as a normal job.

When it is determined in step 114g that the remaining budget is less than the estimated usage charge, the job executability determination processing unit 114 causes the usage charge prediction database 4 shown in FIG.
Predicted usage charge table 4 for each computer system corresponding to the job class specified at the time of submitting the above-mentioned submitted job
After reading 13 (step 114h), the computer system 4 capable of completing execution within the estimated usage charge.
1c is searched from the predicted usage charge table 413 (step 114i), and it is determined whether there is a computer system 41d capable of completing execution (step 114j). When it is determined in step 114j that there is a computer system 41d capable of completing execution, after the computer system 41c found first in the predicted usage charge table 413 is selected as the execution requesting computer system (step 114m), The process of step 114l is performed. When it is determined in step 114j that there is no computer system 41c that can complete execution, after selecting the computer system 41c that can be executed with the lowest budget from the predicted usage charge table 413 as the execution requesting computer system (step 114k). , Step 114
1 is processed. In step 114l, the job transfer processing unit 116 is notified of the execution request job notified from the job usage fee prediction processing unit 113 and the name of the computer system 41c selected in Step 114k or Step 114m, and then the process returns to Step 114b.

By the above processing, if the execution job is executed as it is in the computer system initially specified by the user, the actual value of the user reaches the budget value and the execution of the job is interrupted during execution. If it can be predicted, it becomes possible to automatically select another computer system capable of completing the execution. In step 114m, the computer system found first in the predicted usage charge table 413 is selected from among the computer systems capable of completing the execution, but a plurality of candidate computer systems are selected and other computer systems are selected. It is also possible to narrow down to one computer system among them by some standard.
As the above-mentioned criteria, for example, the execution speed, the charging rate, the distance from the computer system initially designated by the user, the number of jobs waiting to be executed, the priority of the job to be submitted, etc. can be considered. Alternatively, a plurality of computer systems may be designated first, and one computer system may be selected from among them in the priority order designated by the system administrator or the user.

FIG. 12 is a flow chart showing the operation of the job transfer processing section in FIG. In the figure, the job transfer processing unit 116 waits for the notification of the transfer request of the execution request job from the job executability determination processing unit 114 (step 116a), and when the notification is received, the transfer destination computer system name 41c is set. After reading (step 116b), the execution request job is transferred to the designated transfer destination computer system (step 116c), and step 11
Return to 6a. Through the above processing, it becomes possible to transfer the above-mentioned execution-requested job to the designated computer system, and it is possible to prevent the occurrence of loss due to interruption of job execution.

In the present embodiment, the usage charge is predicted only once before the execution of the execution job, but the job can be continued based on the remaining budget of the user calculated at any time during the execution of the job. If it is determined that the job cannot be continued, the job may be transferred to another computer system that can continue. In addition, although the usage fee of the job in the present embodiment is predicted based only on the content of the estimated price table prepared in advance in the usage fee prediction database 41, the actual usage fee (= (Charging) information can be reflected in the estimated charge table (either for each submitted job, for the specified computer system or for each job class),
By notifying the user or the system administrator, it is possible to more effectively prevent the occurrence of loss due to interruption of job execution.

[0038]

【The invention's effect】

(1) As described in detail above, according to the job management method of the present invention, when the actual value of the user who has submitted the job during execution of the job reaches the budget value, the execution of the job is suspended. In the job management method, an estimated calculated value obtained by predicting an estimated charge used when executing the job based on a preset designated execution condition and accumulating the estimated charge to the calculated value is It is determined whether or not the budget value is exceeded, and when it is determined that the estimated actual value based on the designated execution condition exceeds the budget value, the estimated actual value does not exceed the budget value. By defining an alternative execution condition that replaces the specified execution condition and starting execution of the job based on the alternative execution condition, it is possible to ensure that the job execution is completed even when the calculated value of the user approaches the budget value. J The effect that it is possible to prevent the occurrence of loss due to the interruption of job execution is obtained.

(2) In addition to (1), when the alternative execution condition cannot be determined so that the estimated actual value does not exceed the budget value, the estimated charge is minimized. By defining alternative execution conditions, the probability that the execution of the submitted job will be completed when the calculated value of the user is close to the budget value is improved compared to the past, and the loss occurrence rate due to job execution interruption can be improved. The effect that it can reduce is acquired.

(3) In addition to (1) or (2), the designated execution condition and the alternative execution condition are information relating to the computer system or job class in charge of executing the job, and By transferring to the computer system or job class instructed by the alternative execution condition, it is possible to prevent loss occurrence due to job execution interruption or reduce the loss occurrence rate, and to effectively utilize computer resources. To be

(4) Further, in addition to (3), it is possible to systematize the effective use of computer resources by predicting the assumed charging based on a prediction database regarding the computer system and the job class. The effect is obtained.

(5) In addition to (4), the actual billing used at the time of executing the job is reflected in the prediction database, so that the effective use of computer resources can be achieved according to the actual situation of the computer system. The effect that can be optimized is obtained.

(6) In addition to any of (1) to (5),
By notifying the user of the actual billing used when the job was executed, the specified execution condition and the alternative execution condition after the job was completed or interrupted,
It is possible to make the user aware of how to set the designated execution condition according to the actual situation of the computer system to effectively utilize the computer resource.

[Brief description of drawings]

FIG. 1 is a diagram showing an overall configuration of an embodiment of a job management method of the present invention.

FIG. 2 is a diagram showing an internal configuration of a usage charge prediction database in FIG.

FIG. 3 is a diagram showing details of the usage charge prediction database shown in FIG. 2 (No. 1).

FIG. 4 is a diagram showing details (No. 2) of the usage charge prediction database shown in FIG.

5 is a diagram showing an internal configuration of a budget book in FIG. 1. FIG.

FIG. 6 is a diagram showing details of the budget book shown in FIG.

FIG. 7 is a diagram showing an internal configuration of a real account in FIG.

8 is a diagram showing details of the actual account book shown in FIG. 7. FIG.

FIG. 9 is a flowchart showing an operation of a job reception processing unit in FIG.

10 is a flowchart showing an operation of a job usage fee prediction processing unit in FIG.

FIG. 11 is a flowchart showing an operation of a job executability determination processing unit in FIG.

FIG. 12 is a flowchart showing an operation of a job transfer processing unit in FIG.

[Explanation of symbols]

 1 First Computer System 2 Second Computer System 3 Job Input Device 11, 21 Central Processing Unit 111 Operating System 112 Job Reception Processing Unit 113 Job Usage Charge Prediction Processing Unit 114 Job Execution Possibility Determination Processing Unit 115 Job Execution Control Unit 116 Job transfer processing unit 12 Computer resources 41 Usage fee prediction database 42 Budget book 43 Actual book

Claims (6)

[Claims] 1. A job management method for interrupting the execution of a job when a calculated value of a user who has submitted the job reaches a budget value during execution of the job, based on preset designated execution conditions. , Predicting an estimated charge used when executing the job, determining whether an estimated calculated value obtained by cumulatively adding the estimated charge to the calculated value exceeds the budget value, and executing the designated execution When it is determined that the assumed calculated value based on the condition exceeds the budget value, an alternative execution condition that replaces the designated execution condition is determined so that the assumed calculated value does not exceed the budget value, and the alternative execution condition is set. A method for managing a job, wherein the execution of the job is started based on the following. 2. When the alternative execution condition cannot be determined so that the estimated actual value does not exceed the budget value, the alternative execution condition is determined so as to minimize the assumed charge. The job management method according to claim 1. 3. The specified execution condition and the alternative execution condition are information regarding a computer system or a job class in charge of executing the job, and the job is assigned to the computer system or the job class instructed by the alternative execution condition. It transfers, It is characterized by the above-mentioned.
Job management method described. 4. The job management method according to claim 3, wherein the estimated charging is predicted based on a prediction database regarding a computer system and a job class. 5. The job management method according to claim 4, wherein the actual charge used when the job is executed is reflected in the prediction database. 6. The actual charging used at the time of executing the job, and the specified execution condition and the alternative execution condition are notified to the user after completion or interruption of the job. 6. The job management method according to claim 5.