JPH04333143A - Shared area control system - Google Patents

Abstract

PURPOSE:To attain a shared area control system where a shared area is acquired, initialized and released in order to omit a releasing control process and to utilize the file resources, etc., with higher efficiency. CONSTITUTION:Each processing execution means 10 carries out the processing at the same level in response to a request. A processing request means 12 starts each means 10 to ask the execution of processing. A shared area offering means 14 offers an area which is shared by the started means 10. Then each means 10 contains a means 16 which tries to acquire the shared area at start up, a means 18 which initializes the shared area when this area is acquired, a means 20 which writes the use start information on the shared area, a means 22 which writes the use end information on the shared area, a means 24 which reads all information out of the shared area when the use end information on the shared area is written, a means 26 which decides whether all means 10 are using the shared area or not, and a means 28 which releases the shared area all means 10 are through with use of the shared area.

Description

[Detailed description of the invention]

0001

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a shared area management system for acquiring, initializing, and releasing a shared area.

Processes for controlling devices connected to a terminal are prepared for each device and exist at the same level.

[0003] These processes are dynamically activated as needed, share the same area, and execute device control processing.

0004

2. Description of the Related Art In addition to a device control process, a shared area management process is provided, and this management process acquires a shared area, initializes the acquired area, and releases the acquired area.

[0005]

[Problem to be Solved by the Invention] Since a process is prepared to manage the shared area, file resources and memory resources are required for this purpose.

The present invention has been made in view of the above circumstances, and its purpose is to provide a method that makes it possible to reduce file resources and memory resources.

[0007]

[Means for Solving the Problems] In order to achieve the above object, the present invention adopts the system shown in FIG. The processing requesting means 12 dynamically activates each processing execution means 10 and requests the processing, and the shared area providing means 14 provides an area shared by each activated processing execution means 10.

[0008] Each processing execution means 10 includes a shared area acquisition unit 16 that attempts to acquire a shared area when activated, and a shared area initialization unit 18 that initializes the area when the shared area has been successfully acquired. area use start information writing means 20 for writing information indicating the start of use of the shared area into the area; area use end information writing means 22 for writing information indicating the end of use of the shared area into the area; Usage end information reading means 24 that reads out all of the information from the shared area when information indicating the end of use of the shared area is written.
and area use end determination means 26 for determining whether or not all the processing execution means 10 have finished using the shared area, based on the read information, and all the processing execution means 10 have finished using the shared area. shared area release means 28 for releasing the area when the shared area is being used.

[0009]

In the present invention, each processing execution means 10 (device control process) acquires, initializes, and releases a shared area.

0010

DESCRIPTION OF THE PREFERRED EMBODIMENTS Preferred embodiments of the shared area management system according to the present invention will be described below with reference to the drawings.

In FIG. 2, the terminal 30 includes a display section 32, an input section 43, a processing section 36, a file section 38, and a memory section 40.
The processing unit 36 includes devices 42A, 42B,
It controls 42C.

FIG. 3 explains the operation of shared area acquisition and initialization by the processing unit 36, in which the devices 42A, 42 are activated by the start declaration of the requesting process (application) 50.
B, 42C device control process 52A, 52B, 52C
are started dynamically in sequence and terminated in that order.

These processes 52A, 52B, and 52C exist at the same level, and first perform acquisition processing for the shared area 54 using a predetermined identifier.

Since the process 52A is started first, it successfully acquires the shared area 54 and initializes the shared area 54 with initialization data.

Furthermore, the processes 52B and 52C are notified that the shared area 54 has already been acquired, and therefore the process of initializing the shared area 54 is omitted.

However, if the shared area 54 has a specific value (described later)
If the shared area 54 has been written, the initialization process for the shared area 54 is performed even if it is notified that the shared area 54 has already been acquired.

Furthermore, the processes 52A, 52B, and 52C each write their own process states into the shared area 54.

Note that the shared area 54 is allocated by an area allocation unit 56, and its control is carried out by processes 52A (52B, 52B,
52C) in response to an acquisition request.

FIG. 4 explains the action of releasing the shared area by the processing unit 36, and processes 52A, 52B, 52
When C receives the termination declaration from the requesting process 50, it writes information indicating its own process state (termination information) into the shared area 54.

[0020] Processes 52A, 52B, 52C
reads information on each process state from the shared area 54,
Only when it is confirmed that all processes (processes 52A, 52B, 52C) have ended, a specific value (described later) is written to the shared area 54, and a request is made to the area allocation unit 56 to delete the shared area 54 ( In this embodiment, the request for area deletion is made in consideration of the case where the user does not have the authority to delete the shared area.)

In FIG. 5, the procedure for acquiring and initializing a shared area is explained, and the start declaration is made by the requesting process 5.
0, the processes 52A, 52B, and 52C are activated (step 500), and the area allocation unit 56 is requested to acquire the shared area 54 (step 502).

[0022] If the shared area 54 is successfully acquired (YES in step 504), this shared area 54
Initialization data is set in (step 506).

Further, if the shared area 54 is not successfully acquired (NO in step 504: the shared area 54 already exists), specific data XXXX (data indicating permission for initialization) is stored in the shared area 54. It is determined whether the data XXXX is stored (step 508), and when it is confirmed that the data XXXX is stored (YES in step 508), initialization data is set in the shared area 54 (step 506).
).

Further, data indicating the own process state is written to the shared area 54 (step 510), and a start declaration is sent to the corresponding devices 42A, 42B, 42C (
Step 512).

FIG. 6 explains the processing procedure for releasing the shared area. When the reception of the termination declaration sent by the requesting process 50 is confirmed (step 600), the data indicating the termination status of the own process is shared. It is written to area 54 (step 602).

[0026] The shared area 54 is then referred to and it is checked whether all processes 52A, 52B, and 52C are in a terminated state (step 604).

At this time, all processes 52A and 52B
, 52C is in the finished state (step 604
(NO: Either one is running), the above data XXX
X is written in the shared area 54 (step 606), and the area allocation unit 56 is requested to delete the area 54 (step 608).

Furthermore, processes 52A, 52B, 52C
If one of the devices 42A, 4 is not in the completed state (YES in step 604), or if a request for area deletion is made (step 608), the corresponding device 42A, 4
A completion declaration is sent to 2B and 42C (step 610
).

Note that if the shared area 54 cannot be deleted, since the above data XXXX is stored there, the area 54 can be initialized and used next time.

FIG. 7 illustrates the operation of acquiring and initializing the shared area by the process 52A. When the process 52A is first activated by a start request from the requesting process 50, it acquires an identifier (identifying the shared area 54). A request to acquire the shared area 54 is issued using the code (code).

[0031] When successful acquisition of the shared area 54 is confirmed, a request for allocation of the address area indicated by the received identifier is issued.

At this time, the allocation of the address area is notified, so initialization data is set in that area (shared area 54), and the state of the own process 52A (running ) is written.

Furthermore, a start declaration is sent to the device 42A, and the requesting process 50 is notified of the completion of the process.

In FIG. 8, the operation of acquiring and initializing a shared area by the process 52B is explained. When the process 52B is activated by a start request from the requesting process 50, the shared area is acquired in the same way as the process 52A. A request to acquire the area 54 is issued.

[0035] When it is confirmed from the content of the notification that the shared area 54 could not be acquired, a request for notification of a shared area identifier is issued, and it is confirmed by the notification of the identifier that the shared area 54 has already been acquired. Ru.

[0036] Furthermore, an address allocation request is issued,
When the allocation is notified, it is determined whether data XXXX is stored at an address that is α apart from the beginning of the area.

At this time, if the existence of data XXXX is confirmed, initialization data is set in the shared area 54, and as a result, the shared area 54 (which remained without being able to be deleted) becomes usable.

In addition, the state of the own process (starting) is written to the address Y apart from the beginning of the area, and the initial value 42B
, the requesting process 50 is notified of the start declaration and the completion of the processing.

In FIG. 9, the operation of deleting a shared area by the process 42A is explained. When a termination request is notified from the process 50, data indicating the termination status of the own process is stored at an address X away from the beginning of the area. written.

[0040] When it is confirmed that other processes 42B and 42C have been started, a termination declaration is sent to the device 52.
A is sent to A, and the requesting process 50 completes the process.
will be notified.

In FIG. 10, the operation of deleting a shared area by the process 52C is explained. When a termination request is notified from the process 50, data indicating the termination of the own process is written at an address Y apart from the beginning of the area. be included.

Next, when the completion status of the other processes 42A and 42B is confirmed, data XXXX is written to an address spaced by α from the beginning of the area.

Furthermore, a request to release the area 54 (request to delete)
When this is performed (ignoring any errors that occur), a completion declaration is sent to the device 42C, and the requesting process 50 is notified of the completion of the process.

As explained above, according to this embodiment, since the dynamically activated processes 52A, 52B, and 52C individually perform processing related to acquisition, initialization, and release of the shared area 54, the management process for this Therefore, file resources and memory resources can be reduced and used more effectively.

[0045]

[Effects of the Invention] As explained above, according to the present invention, there is no need for a management process to acquire, initialize, and release a shared area, so the file resources and memory resources required for this can be reduced. can be used more effectively.

[Brief explanation of drawings]

FIG. 1 is a diagram explaining the principle of the invention.

FIG. 2 is an explanatory diagram of the configuration of the embodiment.

FIG. 3 is an explanatory diagram of the acquisition and initialization of a shared area by the processing unit of the embodiment.

FIG. 4 is an explanatory diagram of a shared area release operation by the processing unit of the embodiment.

FIG. 5 is a flowchart illustrating a shared area acquisition and initialization processing procedure.

FIG. 6 is a flowchart illustrating a process procedure for releasing a shared area.

FIG. 7 is a time chart illustrating the operation of acquiring and initializing a shared area.

FIG. 8 is a time chart illustrating the operation of acquiring and initializing a shared area.

FIG. 9 is a time chart illustrating the action of releasing a shared area.

FIG. 10 is a time chart illustrating the action of releasing a shared area.

[Explanation of symbols]

30 Terminal 32 Display section 34 Input section 36 Processing section 38 File section 40 Memory section 42A, 42B, 42C Device 50 Request source process 52A, 52B, 52C Device control process 54 Shared area 56 Area allocation section

Claims (1)

[Claims] Claim 1: A plurality of processing execution means (10) that perform processing at the same level in response to a request, and each processing execution means (10).
Processing requesting means (1) that dynamically starts processing
2), and a shared area providing means (14) for providing an area shared by each activated processing execution means (10), wherein each processing execution means (10) provides a shared area when activated. Shared area acquisition means (16) attempts to acquire an area; shared area initialization means (18) initializes the area when acquisition of the shared area is successful; Area use start information writing means (2
0), an area use end information writing means (22) for writing information indicating the end of use of the shared area into the area, and an area use end information writing means (22) for writing information indicating the end of use of the shared area into the area; Use end information reading means (24) for reading information from the shared area; and area use end determining means for determining whether all processing execution means (10) have finished using the shared area based on the read information. (26); and shared area release means (28) for releasing the shared area when all the processing execution means (10) have finished using the shared area. method.