JPH04246731A - Software system - Google Patents

Abstract

PURPOSE:To obtain the software system which simplifies trouble at the time when each process obtains resources from a kernel, and also, can grasp the status of each process. CONSTITUTION:The software system is provided with plural pieces of processes 11-1n for constituting the system, a kernel 21 connected to each process thereof, a system management process 31 having generating and managing functions of each process and an obtaining function of resources, a process management table 32 for recording a status of each process generated and managed by this system management process, and a resources management table 33 for recording the resources which the system management process obtains in a lump from the kernel together with its key.

Description

[Detailed description of the invention]

0001

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a software system, and more particularly to a software system that can implement processes for efficiently managing a software system built on a multitasking operating system such as UNIX.

0002

2. Description of the Related Art In a conventional software system, as shown in FIG. 2, a plurality of individual processes 11 to 1n are each connected to a kernel 21, and each of the individual processes 11 to 1n issues a request to the kernel 21 independently. The kernel 21 is configured so that the individual processes 11 to 1n acquire resources (semaphores, shared memory, etc.) by confirming the keys (identification data) of the individual processes 11 to 1n.

0003

SUMMARY OF THE INVENTION In such conventional software systems, each process independently acquires resources from the kernel, which requires time and effort for each process to acquire resources. Furthermore, it is necessary to set unique keys among individual processes in order to share resources between them. Furthermore, if a non-resident process that is generated irregularly exists in the system, it is difficult for other processes to obtain the status of whether or not that process has been generated. Furthermore, when an abnormality occurs in the system and individual processes terminate abnormally, there is a problem in that it is difficult to discover the abnormality and start abnormal processing. An object of the present invention is to provide a software system that solves these problems.

0004

[Means for Solving the Problems] The software system of the present invention includes a system management process having a function of creating and managing individual processes and a function of acquiring resources, and a status of each process created and managed by this system management process. and a resource management table that records resources collectively acquired from the kernel by the system management process together with their keys.

[0005]

[Operation] According to the present invention, each process can refer to the process management table and the resource management table so that other processes can obtain the status information of each process, and the resources can be shared. It is possible to obtain the key.

[0006]

DESCRIPTION OF THE PREFERRED EMBODIMENTS Next, the present invention will be explained with reference to the drawings. FIG. 1 is a configuration diagram of the software system of the present invention. In the figure, 11 to 1n are a plurality of individual processes, and 21 is a kernel. These individual processes 11
~1n and the kernel 21 are provided with a system management process 31, a process management table 32, and a resource management table 32.

[0007] The system management process 31 starts up the individual processes composing the system first among the individual processes 11 to 1n, and records the status in the process management table 32. When the status of the generated process changes, such as when it ends normally or abnormally, it is recorded in the process management table 32. It shall be recorded in a table that can be referenced by all processes that make up the system. This allows each process that makes up the system to refer to the status of processes other than itself, allowing it to check whether a certain process has started or whether any process has terminated abnormally.

Next, an example of resource acquisition will be shown. First, the system management process 31 receives resources (semaphores,
shared memory, etc.) and obtain the keys necessary to use it. Next, the system management process 31 records the key in the resource management table 33. This shall be recorded in a table that can be referenced by all processes that make up the system. As a result, the individual processes 11 to 1n that make up the system use the keys recorded in the resource management table 33 when using resources, without the need for coding to acquire resources from the kernel 21. Resources can be used. In addition, when multiple non-resident processes use the same resource, the system management process 31 solves the problem of which process acquires the resource first and which process releases the resource last.
can be avoided by acquiring resources first and releasing them last. Note that the circled numbers in FIG. 1 indicate the order of the steps. Here, the present invention is not limited to the above-mentioned embodiments, but includes various modifications in its constituent elements and forms.

[0009]

As described above, the present invention includes a system management process, a process management table that records the status of individual processes, and a resource management table that records resources acquired from the kernel together with their keys. Therefore, by referring to the process management table, the status of each process can be grasped, and if one of them terminates abnormally, other processes can confirm the abnormality. Additionally, by referring to the resource management table, keys for using resources can be obtained, which has the effect of simplifying the effort required for individual processes to acquire and release resources.

[Brief explanation of the drawing]

FIG. 1 is a configuration diagram of an embodiment of the present invention.

FIG. 2 is a configuration diagram of a conventional software system.

[Explanation of symbols]

11-1n Individual processes 21 Kernel 31 System management process 32 Process management table 33 Resource management table

Claims (1)

[Claims] Claim 1: A system management system having a function of creating and managing individual processes and a function of acquiring resources in a software system comprising a plurality of individual processes constituting the system and a kernel connected to these individual processes. A process management table that records the status of processes and individual processes generated and managed by this system management process, and a resource management table that records resources acquired collectively from the kernel by the system management process together with their keys. A software system characterized by: