JPH06325054A - Multiplex degree management control system for business job - Google Patents

Abstract

PURPOSE:To reduce load to a system by utilizing a business job equally for any user and to immediately judge whether the business job can be executed or not at an execution request source. CONSTITUTION:A multiplex degree registering means 1 prepares a multiplex degree managing file 2 and performs the initialization and change of a multiplex degree managing table 4. When the execution of the business job is requested, multiplex degree inspection means 5a and 5b inspect whether the execution request of the business job can be accepted or not by retrieving the multiplex degree managing table 4, and when the execution request can not be accepted, the execution request is ignored, and error notice is returned to a terminal at the execution request source. When the start request of the business job is issued from business start requesting means 6a and 6b, a multiplex degree managing means 3 starts the business job and updates the multiplex degree state of the business job in the multiplex degree managing table 4, and when the end notice of the business job is received from business end notice means 8a and 8b, the multiplex degree state of the business job in the multiplex degree managing table 4 is updated.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a business job activation control system, and more particularly to a business job multiplicity management control system that can be executed simultaneously.

[0002]

2. Description of the Related Art In order to execute a large number of business jobs (programs) within a unit time, it is common practice to process business jobs in parallel using a multiplicity management function provided by an operating system ( JP 63-8
5938, Japanese Patent Laid-Open No. 1-116844, etc.).

For example, four times an hour (15 times per processing)
For the executable job job X, the maximum multiplicity that can be executed at the same time is set to 5, so that the operating system performs parallel processing at the same time, and a maximum of 20 jobs can be executed within one hour.
It can be executed up to once.

However, the multiplicity management function manages and controls business job execution requests in the order in which they are received. That is,
Since a business job execution request becomes valid only after it is registered in the operating system, when the user makes a business job execution request, it was not possible to immediately determine whether the business job could be executed.

For example, if a user at the branch A makes an execution request for the business job X 20 times and then a user at the branch B makes an execution request for the same business job X, the business for the user at the branch B is executed. The execution result of the job X will be obtained at least one hour after all the execution of the business job X for the user of the branch A is completed, and only the operating system multiplicity management function requests execution of the business job. Depending on the operation method of users, it was not possible for all users to use business jobs equally.

Further, the multiplicity management function accepts all business job execution requests, and when the load on the computer system is high, the multiplicity management function cannot complete the processing, and as a result cancels the business job execution requests that could not be processed. It must be done, and the load of the computer system is further aggravated by the acceptance processing and the cancellation processing of the cancellation request.

Particularly, it is preferable for a business job which can be processed immediately like an online program, but in the case of a business job which takes a long processing time once such as a batch program, it is given to the entire computer system depending on its utilization. The load was also heavy.

[0008]

In the multiplicity management function provided by the conventional operating system described above, all execution requests for business jobs are accepted, and business jobs that cannot be processed in parallel are kept waiting. When not all business job users can use business jobs equally and the number of business job execution requests received is large, the time from receiving the execution requests until the execution result is output becomes the load state of the computer system. There was a problem that it changed and could not be predicted.

Further, how long a business job is kept waiting can be checked by an operator command provided by the operating system. For example, branch A
However, there is a problem in that it is not possible to check how long the business job requested to be executed will be kept waiting, and the operation of the operator command is not as simple as the end user can do.

In view of the above points, an object of the present invention is to perform management control of the multiplicity (the number of business jobs that can be simultaneously accepted) that can be simultaneously executed in units of business job execution request sources (eg, branch offices, terminals, etc.). In order to prevent a business job from being used only by a specific user, a multiplicity management control method for business jobs is provided.

It is another object of the present invention to ignore an execution request when an execution request for a business job is issued in excess of the maximum multiplicity and issue an error notification indicating that the execution request cannot be accepted. It is to provide a business job multiplicity management control method capable of immediately determining whether or not a business job can be executed by a business job execution request source.

[0012]

SUMMARY OF THE INVENTION A business job multiplicity management control method according to the present invention includes a multiplicity management file for storing the maximum executable multiplicity of a business job in units of job job execution request sources, and a business job. Multiplicity management table that stores the multiplicity status of the business job that is currently being executed for each execution request source, and the multiplicity registration means that creates the multiplicity management file and initializes and changes the multiplicity management table When the execution request of the business job is requested, the multiplicity management table is searched to check whether the execution request of the business job can be accepted based on the multiplicity state of the business job, and the execution request cannot be accepted. It is said that the multiplicity inspection means for ignoring the execution request and the execution request for the business job can be accepted by this multiplicity inspection means. When a business job start request is issued from the business start request means, a business start request means for making a business job start request, a business job end notification means for giving a business job end notification when the operation of the business job ends When a business job is started, the multiplicity status of the business job in the multiplicity management table is updated, and when the end notification of the business job is notified from the business end notification means, the multiplicity status of the business job in the multiplicity management table And a multiplicity management means for updating. Furthermore, the multiplicity inspection means,
When the business job execution request cannot be accepted, the business job execution request is ignored and an error notification is returned to the business job execution request source.

[0013]

The present invention will be described in detail with reference to the drawings.

FIG. 1 is a block diagram showing the configuration of a business job multiplicity management control system according to an embodiment of the present invention. The multiplicity management control method for business jobs according to the present embodiment includes a multiplicity management function 10 including a multiplicity registration unit 1, a multiplicity management file 2, a multiplicity management unit 3 and a multiplicity management table 4, and a multiplicity inspection unit. Business instruction program I including 5a and 5b and business activation requesting means 6a and 6b
X and IY and business jobs (programs) X and Y including business end notification means 8a and 8b constitute a main part thereof. The multiplicity management function 10, the work instruction programs IX and IY, and the work job X
And Y are provided on the side of a host computer (not shown), and branch offices A and B at remote locations are connected to a terminal 7a connected to the host computer via a communication line,
7b, 7c and 7d are installed. A console 7e is installed in the host computer.

The multiplicity registering means 1 creates the multiplicity management file 2 and dynamically initializes and changes the multiplicity management table 4 on the main memory (not shown).

The multiplicity management means 3 is a business activation request means 6
When there is a business job activation request from a and 6b, the business job that received the execution request is activated and the multiplicity status of the business job in the multiplicity management table 4 is updated.
Further, the multiplicity management unit 3 updates the multiplicity status of the business job in the multiplicity management table 4 when the business job completion notification is issued from the business completion notification units 8a and 8b.

The multiplicity checking means 5a and 5b search the multiplicity management table 4 at the time of requesting the execution of the business job, and check whether the execution request of the business job can be accepted based on the multiplicity state of the business job. If the execution request cannot be accepted, the execution request is ignored and an error notification is returned to the business job execution request source. Further, when the execution request of the business job can be accepted, the multiplicity checking means 5a and 5b activate the business activation request means 6a and 6b.

The job activation requesting means 6a and 6b make a request to activate the job jobs X and Y to the multiplicity managing means 3.

The business end notification means 8a and 8b notify the multiplicity management means 3 of the end of the business jobs X and Y.

FIG. 2 is a diagram showing an example of the contents of the multiplicity management file 2. In FIG. 2, A, B, C, ..., D indicate execution request source codes (for example, branch identification code, terminal number, etc.). Further, X, Y, ..., Z represent business job identification codes. The multiplicity management file 2 is composed of a two-dimensional table of execution request source codes and business job identification codes, and the content thereof is a column showing the maximum multiplicity of each business job that can be simultaneously executed for each execution request source. .

FIG. 3 is a diagram showing an example of the contents of the multiplicity management table 4. In FIG. 3, A, B, C, ..., D indicate execution request source codes. Further, X, Y, ..., Z represent business job identification codes. This multiplicity management table 4
Consists of a two-dimensional table of execution request source codes and business job identification codes, the content of which is a column showing the maximum multiplicity of each business job that can be simultaneously executed for each execution request source.
It is composed of a column showing the remaining number of multiplicity indicating how many business jobs can be executed simultaneously in units of execution request sources.

Next, the operation of the multiplicity management control system for business jobs of the present embodiment thus constructed will be described.

When the host computer is started up, the multiplicity registration means 1 reads the maximum multiplicity of each business job in the execution request source unit from the multiplicity management file 2 and stores each job in the execution request source unit in the main memory. The multiplicity management table 4 is created by expanding the maximum multiplicity and the remaining multiplicity of jobs.

The multiplicity registration means 1 is started from the console 7e on the host computer side, and inputs the multiplicity management information (execution request source code, business job identification code and maximum multiplicity) for which registration / modification is instructed. The registration / update of the maximum multiplicity of the multiplicity management file 2 and the initialization / change of the maximum multiplicity of the multiplicity management table 4 are dynamically performed.

For example, when changing the maximum multiplicity of the business job X of the branch A from 10 to 15, the multiplicity registration means 1 is started from the console 7e, and the branch identification code "A" and the business job identification code "X". Using the and keys as an instruction to change the maximum multiplicity of the corresponding business job X to 15, the multiplicity management file 2 and the multiplicity management table 4
The maximum multiplicity of can be updated.

From the terminal 7b of the branch A, the business job X will be described below.
A case will be described as an example where a request to execute is issued.

When an execution request for the business job X is issued from the terminal 7b of the branch A, the host computer activates the multiplicity checking means 5a of the business instruction program IX.

The multiplicity checking means 5a searches the multiplicity management table 4 by using the branch identification code "A" and the business job identification code "X" as keys, and when the remaining multiplicity number in the corresponding column is 1 or more. It is checked whether or not the execution request of the business job X can be accepted based on the existence. If the execution request for the business job X cannot be accepted, the multiplicity checking means 5a ignores the execution request for the business job X and issues an error notification indicating that the execution request cannot be accepted to the branch office of the execution request source. Terminal 7b of A
To return. As a result, the user of the terminal 7b of the branch A is
It is possible to immediately know that the business job X cannot be executed.

On the other hand, when the execution request of the business job X can be accepted, the business activation request means 6a of the business instruction program IX operates, the activation request of the business job X is issued, and the multiplicity management means 3 operates. Is activated.

The multiplicity management means 3 searches the multiplicity management table 4 using the branch identification code "A" and the business job identification code "X" as keys, and subtracts 1 from the remaining multiplicity in the corresponding column. Then, the business job X is activated.

When the job job X finishes its execution and the job end notification means 8a issues an end notification, the multiplicity management means 3 is activated.

The multiplicity management means 3 searches the multiplicity management table 4 by using the branch identification code "A" and the business job identification code "X" as keys, as in the case of the processing of the activation request, and applies it. Add 1 to the remaining multiplicity in the column.

In this way, the multiplicity management table 4 updates the corresponding multiplicity remaining number each time a business job is started / finished, so that the multiplicity check means 5a and 5b of the business instruction programs IX and IY correspond. By checking the remaining multiplicity of the business job, it is possible to determine whether the business job can be executed.

For example, looking at the contents of the multiplicity management table 4 shown in FIG. 3, the business job X can be executed because the remaining multiplicity of the business job X at the branch A is 3. It is understood that the business job Y cannot be executed because the remaining multiplicity of the business job Y at the branch B is 0.

In the above embodiment, the multiplicity management table 4 stores the remaining number of multiplicity indicating the number of business jobs that can be executed. Instead, the multiplicity management table 4 stores the number of business jobs currently being executed. The multiplicity may be stored. Needless to say, the present invention can be easily realized in this way as well.

[0036]

As described above, according to the present invention, a multiplicity management file, a multiplicity management table, a multiplicity checking means, a business start requesting means, a business end notifying means and a multiplicity managing means are provided to execute a business job. By managing the multiplicity status of business jobs on a request source basis and controlling acceptance of business job execution requests, all users can use business jobs equally and the load on the computer system is increased. The effect is that it can be reduced. In addition, the provision of the multiplicity registration means has an effect that the maximum multiplicity of the business job can be changed by a simple operation in accordance with the daily operation of the business.

Furthermore, when an execution request for a business job is issued in excess of the maximum multiplicity, an error notification indicating that the execution request cannot be accepted is returned to the execution request source, so that the execution request source can be used. This has the effect that a person can immediately determine whether or not a business job can be executed.

[Brief description of drawings]

FIG. 1 is a block diagram showing a configuration of a business job multiplicity management control system according to an embodiment of the present invention.

FIG. 2 is a diagram illustrating an example of contents of a multiplicity management file in FIG.

FIG. 3 is a diagram showing an example of the contents of a multiplicity management table in FIG.

[Explanation of symbols]

 1 multiplicity registration means 2 multiplicity management file 3 multiplicity management means 4 multiplicity management tables 5a, 5b multiplicity checking means 6a, 6b business activation requesting means 7a, 7b, 7c, 7d terminal 7e console 8a, 8b business end notification Means 10 Multiplicity management function A, B Branch (execution request source) IX, IY Business instruction program X, Y Business job

Claims (4)

[Claims] 1. A multiplicity management file that stores the maximum executable multiplicity of a business job for each execution request source of a business job, and a multiplicity status of the currently executing business job for each execution request source of the business job A multiplicity management table to be stored, a multiplicity registration means for creating the multiplicity management file and initializing and changing the multiplicity management table, and searching the multiplicity management table at the time of requesting execution of a business job. Based on the multiplicity status of the business job, a multiplicity checking means for inspecting whether the execution request of the business job can be accepted, and ignoring the execution request when the execution request cannot be accepted; A job activation requesting means for issuing a job job activation request when the inspection means can accept the job job execution request; A business end notification means for notifying the end of a business job at the end of a job operation, and for starting a business job when a business job start request is issued from the business start request means and for checking the number of business jobs in the multiplicity management table. And a multiplicity management means for updating the multiplicity status of the business job in the multiplicity management table when a business job completion notification is sent from the business completion notification means. Job multiplicity management control method. 2. The business job according to claim 1, wherein the multiplicity checking unit ignores the business job execution request and returns an error notification to a business job execution request source when the business job execution request cannot be accepted. Multiplicity management control method. 3. The business job multiplicity management control method according to claim 1, wherein the multiplicity management table stores the maximum multiplicity and the remaining multiplicity number. 4. The business job multiplicity management control method according to claim 1, wherein the multiplicity management table stores a maximum multiplicity and a current multiplicity.