JP2000207229A - Resource occupancy management method - Google Patents

Abstract

(57) [Summary] Even when resources are occupied using different macros from different processes for the same resource, exclusive control is correctly performed, and resources occupied using different macros at the end of the process Provide a function to search for Even if exclusive control of the same resource is performed using different macros among a plurality of processes, exclusive control of the resource is correctly performed. In addition, since resource occupation information is centrally managed, by viewing this information at the end of the process, release omission can be detected even for resources occupied by different macros.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a resource occupancy management method, and more particularly to a multi-process environment and a computer system having a plurality of macros for occupying resources between processes.
The present invention relates to a resource occupancy management method characterized in that exclusive control is correctly performed even when the same resource is occupied by different macros from different processes.

[0002]

2. Description of the Related Art Conventionally, when issuing a macro for performing exclusive control between a plurality of processes, it is necessary to use the same macro between processes in order to perform exclusive control on the same resource. . Originally, exclusive control should depend not on the macro but on the resource, but in a conventional system, exclusive control of the same resource requires the user to use the same macro.

For this reason, when there are a plurality of processes interpreting that exclusive control is performed on the same resource by using different exclusive control macros, exclusive processing is not performed correctly, data is destroyed, or exclusive control is performed incorrectly. There was a problem that was not. In addition, it is difficult to collectively search for whether or not there is a resource release omission at the end of the process because the management information is distributed for each macro. It was also in charge of the pair and the management of the resources they occupied.

[0004]

[Problems to be Solved by the Invention] When a process occupies resources by one macro, it provides a means for verifying whether the occupied resources are occupied by other macros.

[0005] 2. When a process releases a resource by one macro, it provides a means for allowing a process waiting for the occupation of that resource by another macro to occupy the resource.

[0006] 3. Provided is a means for enabling the resource to be released normally even when the same resource is released by a release macro that is not paired with the occupation macro issued by the process.

[0007] 4. Provides a means to search for occupied resources at the end of the process.

[0008]

According to the present invention, in order to solve the above-mentioned problems, an occupied resource name, an occupied macro for occupying a resource, a resource release macro paired with the occupied macro, an occupied process ID, A resource information table having a pointer to a process queue waiting for the occupation of the resource is provided. Further, a waiting process table having an ID of a process waiting for resource occupation, an issued macro, and a pointer to a process waiting for the next resource is provided, and a waiting process queue including a linear list of the table is provided. An exclusive macro list that defines a resource occupation macro and its corresponding release macro is provided. Further, a macro handling process for handling the macro issued from the process is provided.

[0009]

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

FIG. 1 shows the configuration of a table according to the present invention.
The resource information table (100) has a resource name, an occupied macro, a release macro, an occupied process ID, and a pointer to a process queue (102) waiting for the occupied resource. The waiting process table (101) stores the ID of the waiting process,
The issued macro has a pointer to the waiting process table. The waiting process queue (102) comprises a linear list of waiting process tables. Also, an exclusive macro list (103) is defined which defines a resource occupation macro and a resource release macro that is paired with the macro.

FIG. 2 shows a macro handling process. A macro issued from a process is first linked to a macro handling process. In the macro handling process, the exclusive macro list (103) is searched (200), and it is determined whether the issued macro is an occupied macro, a released macro, or another macro (201). In the case of the occupied macro, the resource occupancy processing (202) is executed, in the case of the release macro, the resource release processing (204) is executed, and in the other cases, the designated macro is executed (203).

FIG. 3 shows the resource occupation process (202). In this process, first, the resource information table is searched (30).
0). As a result of the search, it is determined whether the occupied resource is in the resource information table (301). If the occupied resource is not in the resource information table, the resource information table (10
In 0), a resource name, occupied macro, and occupied process ID are newly set (302). Next, the exclusive macro list (10
3) to obtain a release macro to be paired (30)
3). The obtained release macro is stored in the resource information table (100).
Is set (304), and the designated macro is executed (30).
5).

On the other hand, if the resource to be occupied already exists in the resource information table, a new waiting process table (1) is newly added.
01) is created (306). Next, the resource information table (1
From (00), a search is made as to whether there is a waiting process table in the waiting process queue (307). If there is a waiting process table, the waiting process table is connected to the end of the waiting process queue (102) (308). Therefore, even when exclusive control is performed using different macros for the same resource, exclusive processing is performed correctly.

If there is no waiting process table, the address of the created waiting process table is set as a pointer to the waiting process queue of the resource information table (100) (309).

FIG. 4 shows the resource release processing (204). In the resource release processing, first, the resource information table (100) is searched (400). As a result of the search, it is determined whether the occupied resource is in the resource information table (100) (4.
01). If the occupied resource is in the resource information table (100), it is determined whether or not the occupied process ID in the resource information table (100) is the same as the process that has requested the release (402). The occupied resource is the resource information table (1
00), an attempt is made to release an unoccupied resource, and an error occurs (403). If the occupied process IDs do not match, an error occurs because a process other than the occupied process has unduly requested the release of resources (4).
03).

If the process IDs match, a release macro is obtained from the resource information table (100) (404) and the macro is executed (405). Therefore, even when a release request is issued from a process using a macro that is not paired, the release of resources is performed correctly.

Next, it is searched (406) whether there is a waiting process queue (102) in the resource information table (100).
If there is a waiting process queue (102), a waiting process table at the head of the waiting process queue (102) is acquired (407). A Next pointer is set as a pointer to the waiting process queue in the resource information table (100) (408). Next, the waiting process table at the head of the waiting process queue is deleted (409). Next, it is checked whether the waiting process table (101) still remains in the waiting process queue (102) (41).
0). When the waiting process queue (102) is empty, there is no process occupying the resource and all the resources are released. The pointer to is deleted (411). The same applies when there is no queue in the resource information table.

On the other hand, if there is still a waiting process table (101) in the waiting process queue (102), (4)
In step 412, the issuing macro of the waiting process table acquired in step 07) is set to the occupied macro of the resource information table 100, and the waiting process ID is set to the occupied process ID.
Next, the exclusive macro list (103) is searched, and a pair of released macros is set in the resource information table (413).
Finally, the issuing macro of the waiting process is executed (41).
4). As a result, even when a plurality of processes try to occupy the same resource using different macros, exclusive control is performed correctly. Further, by referring to the resource information table, it is possible to know which process is using which macro and is waiting for the occupation of the resource.

FIG. 5 shows a resource information table check process in the process end process. At the end of the process, the resource information table is referenced to search whether the occupied process ID matches the process ID to be terminated (50).
0). If they match, a warning message is output because there is no release of resources (501).

[0020]

According to the present invention, there are provided: Even if exclusive control of the same resource is performed using different macros among a plurality of processes, exclusive control of the resource is correctly performed.

2. Since the resource occupation information is centrally managed, the resource occupation information can be collectively collected. 3. By retrieving the ID of the occupied process at the end of the process, it is possible to detect a process that has omission of resources.

4. The exclusive control that the user has to perform by managing “macro + resource” does not depend on the macro, and only the “resource” needs to be managed.

[Brief description of the drawings]

FIG. 1 is a diagram showing the configuration and correlation of a resource information table, a waiting process table, a waiting process queue, and an exclusive macro list according to the present invention.

FIG. 2 is a flowchart showing a macro handling processing order.

FIG. 3 is a flowchart showing a resource occupation processing order.

FIG. 4 is a flowchart showing a resource release processing order.

FIG. 5 is a flowchart showing a resource information table check processing order;

[Explanation of symbols]

100: Resource information table, 101: Waiting process table, 102: Waiting process queue, 103: Exclusive macro list, 104: Macro handling process, 105 ...
Resource information table check processing.

 ────────────────────────────────────────────────── ─── Continuing on the front page (72) Inventor Masayoshi Oshiba 5-2-1 Omika-cho, Hitachi City, Ibaraki Prefecture F-term in the Omika Plant of Hitachi, Ltd. F-term (reference) 5B098 GA04 GB05 GB13 GD15 GD22

Claims (3)

[Claims] In a multi-process environment, in a resource occupation management method for a computer system having a plurality of macros having a process of occupying / releasing resources between processes, a resource name, an occupied macro and a corresponding release on a main storage device are provided. It has a resource information table having a macro, an occupied process ID, and a pointer to a waiting process queue in a structure. An exclusive macro list having a waiting process table having a pointer in a structure and a waiting process queue forming a FIFO by a linear combination of the waiting process table, and defining a list of a resource occupation macro and a resource release macro paired with the macro. Have
It is necessary to have a macro handling process for handling the macro issued from the process, and to perform exclusive control for the macro occupation / release of the resource issued / issued by a different macro if the macro is occupied by the same resource. Characteristic resource occupancy management method. 2. The resource occupancy management system according to claim 1,
2. A resource occupancy management method, wherein information on resources occupied by a process can be easily searched for by using the resource information table of claim 1 even in different macros. 3. The resource occupancy management system according to claim 1,
A resource information table check process is provided in the process termination process executed when the process is terminated, and a process having a resource release omission at the end of the process can be confirmed by retrieving the occupied process ID from the resource information table. Resource occupancy management method.