JPH09171469A - Method and system for controlling program operation - Google Patents

Abstract

PROBLEM TO BE SOLVED: To easily change between the permanent station or non-permanent station of an application program in a real-time processing system on a computer. SOLUTION: This system has plural task programs 3 constituted while containing application programs 2, processing request waiting part 6 for waiting processing requests to the respective application programs 2, and managing table 5 for storing operation specification information showing whether or not the application programs 2 are permanently stationed for operation. The task programs 3 acquire the operation specification information of application programs 2 consisting of the task programs 3 from the managing table 5 and switch the procedure of application program execution corresponding to the acquired operation specification information.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a program operation control method and a program operation control system for operating a program with high real-time and reliability on a multitasking operating system of a computer.

[0002]

2. Description of the Related Art In a multitasking operating system such as UNIX operating system,
Generally, application programs are processed in process units.

A program on the operating system is basically stored in the file system as a load module file.
When the program is operated, a process for performing the process is newly generated, the contents of the program are expanded in the main memory (hereinafter referred to as loading), and then the process of the program is started. Then, when the processing of the program ends, the main memory used is released and the process disappears.

When operating in such a procedure, the program operates nonresidently in the main memory. Therefore, conventionally, when operating a program non-residently, the program was started by the processing procedure as described above.

However, when a real-time processing system is constructed on an operating system, in order to secure the responsiveness of the system, a program requiring a high real-time property was made to reside in the main memory and operate. .

Next, a processing procedure of a conventional program for resident operation will be described. FIG. 16 shows, for example, Japanese Patent Laid-Open No. 6-
It is a flow chart of the conventional resident operation | movement program shown by 332724 publication. As shown in FIG. 16, the resident operation program is roughly divided into an application program section 2 for performing the originally intended processing and a program operation control section 1 for performing the resident operation.

Next, the processing procedure of the conventional resident program will be described with reference to FIG. The resident program starts processing as part of the system initialization processing when the system is started up, and the program operation control unit prepares the program (S71). After S71, the process request of the application program unit 2 is waited by waiting for the acquisition of a message or a semaphore (S7).
2).

When a processing request is issued to the application program section 2, the processing request waiting is released, and the processing shifts to the processing in the application program section 2 (S73). When the processing in the application program section 2 is completed, the processing moves to the program operation control section 1 again and waits for the processing request of the application program section again (S72). When the end of the processing system is detected, the program is cleaned up (S
74) The program ends.

By this operation, the processing of the entire program does not end unless the processing system ends, so that the program remains resident in the main memory and the process continues to exist. As a result, the resident operation of the application program unit 2 Will be realized.

However, when constructing a real-time processing system, not all programs are required to have a high real-time property, and there are many programs that operate infrequently and may be slow in response. For this reason, when building a real-time processing system, the number of processes that operate simultaneously and the required main memory capacity should be reduced.
Each application program is created so that programs requiring high real-time performance are resident operations and other programs are non-resident operations.

[0011]

As described above, in the conventional program operation control method, since the program activation method of the program that performs the resident operation differs from the program activation method of the program that performs the non-resident operation, for example, the operation of a certain program changes from the non-resident operation to the resident operation. When changing to, there is a drawback that the processing configuration of the program needs to be changed and the operation of the program on the side that starts the program must also be changed.

Further, in the case of a non-resident program, if the programs are continuously started at intervals shorter than the processing time, there is a problem that a plurality of the same programs temporarily run in parallel to cause a problem. .

When a large number of programs that are not particularly important for the behavior of the real-time processing system operate,
Due to the limitation of the number of processes that can run simultaneously in the operating system, there is a problem that a non-resident program cannot be started.

The present invention has been made to solve the above problems and has the following objects. An object of the present invention is to obtain a program operation control method and a program operation control system that can easily cope with changes in program processing. It is also intended to improve the stability or certainty of the program processing.

[0015]

According to a first aspect of the present invention, there is provided a program operation control method, wherein, as a processing of a task program having an application program to be activated, an operation regulation indicating whether the application program is resident or non-resident. An operation regulation information acquisition step of acquiring information, and a program execution step of executing the application program, wherein the program execution step is performed when the operation regulation information acquired in the operation regulation information step indicates resident. This is executed after the processing request for the application program is issued, and when the operation regulation information acquired in the operation regulation information step indicates non-resident, it is executed after the operation regulation information acquisition step.

A program operation control method according to a second aspect of the present invention includes a read step of reading the above-mentioned operation regulation information from a file and using it as information in a management table, and the above-mentioned operation regulation information acquisition step comprises the above-mentioned operation regulation from the management table. By obtaining the information, the operation regulation information is obtained.

In the program operation control method according to the third aspect of the present invention, an operation specification information acquisition step of acquiring operation specification information indicating whether the application program to be activated is resident operation or non-resident operation, and the operation specification information acquisition step. If the operation regulation information acquired in step 2 indicates non-resident,
After the processing request is issued to the application program, the first activation step of activating the task program having the application program and the operation regulation information acquired in the operation regulation information acquisition step indicate resident In addition, after the operation regulation information acquisition step, there is a second activation step of activating the task program having the application program.

According to a fourth aspect of the present invention, there is provided a program operation control method, wherein after a preset number of processes, a loading process program activating step of activating a loading process program, and the loading process program activating step, A loading request step for issuing a loading request for requesting the loading processing program to load the task program, and the loading processing program receiving the loading request executes loading of the task program specified in the loading request. And a loading execution step.

In the program operation control method according to the fifth aspect of the present invention, the loading processing program starting step creates a new process and starts the loading processing program when one of the processes disappears. It is a call.

The program operation control method according to the sixth aspect of the present invention is the same as the fifth aspect of the present invention, further including operation status information indicating whether or not the application program is being processed when one of the above processes disappears. From the search step for searching the operation status information of the application program that was started in the disappeared process from, and when the operation status information of the application program searched in the search step indicates that it is in process, start in the disappeared process And a second loading request step for issuing a loading request to the loading processing program activated in the second loading processing program activation step so as to load the task program having the applied program. is there.

According to a seventh aspect of the present invention, there is provided a program operation control method, wherein a request issuing step for issuing a processing request for an application program and, in the case where a plurality of processing requests for the application program are issued, a processing content of the application program. An erasing step of erasing a predetermined processing request from the plurality of processing requests.

A program operation control method according to an eighth aspect of the present invention is the same as that of the seventh aspect, in which a method of erasing a processing request issued to the application program is defined in accordance with the processing content of the application program. The operation characteristic acquisition step of acquiring from
The predetermined processing request among the plurality of processing requests is deleted according to the operation characteristic acquired in the operation characteristic acquisition step.

A program operation control system according to a ninth aspect of the present invention is a task program including an application program, processing request waiting means for waiting a processing request for the application program, and the application program is resident or non-resident. And a management table in which operation regulation information indicating whether to perform is set, wherein the task program acquires operation regulation information of an application program which constitutes the task program from the management table,
The procedure for executing the application program is switched according to the acquired operation regulation information.

A program operation control system according to a tenth aspect of the present invention holds a processing request for an application program and sets an operation characteristic indicating a method of erasing the processing request for the application program according to the processing content of the application program. It has a processing request holding means and an application program that executes processing in the order of processing requests held by the processing request holding means, and the processing request holding means is provided when a plurality of processing requests for the application program are issued. The processing request held in the processing request holding means is deleted according to the operation characteristic.

[0025]

BEST MODE FOR CARRYING OUT THE INVENTION

Embodiment 1 FIG. This embodiment relates to a task program 3 for operating a program based on program definition information 51 stored in the management table 5 and indicating whether each application program is a resident program or a non-resident program, Hereinafter, description will be given with reference to FIGS. 1 and 2.

FIG. 1 is a block diagram of a program operation control system in this embodiment. In FIG. 1, reference numeral 3 is a task program controlled by the program operation control system, which is composed of a program operation control unit 1 and an application program unit 2.

Reference numeral 5 is a management table which holds the program operation regulation information 51 corresponding to each application program section 2. The management table 5 is realized as a predetermined storage area on the main memory (not shown). The information stored in the management table 5 is composed of a program name 50 indicating each application program section 2 and program operation regulation information 51 indicating whether the application program section 2 is resident or non-resident. Reference numeral 6 is a processing request waiting unit corresponding to each of the application program units 2.

Next, the operation of the task program 3 in this embodiment will be described with reference to FIG. When the task program 3 starts its processing, the processing first moves to the program operation control unit 1. The program operation control unit 1 makes settings for referring to the management table 5 (S1). As a specific processing content, for example, processing for checking the memory address of the recording area in which the management table 5 is stored corresponds.

Then, based on the program name 51 in the management table 5, preparation is made for acquiring the program operation regulation information 4 corresponding to the application program section 2 (S).
2). As a specific process, for example, a process of checking the information of the application program unit 2 itself to be operated from the information in the management table 5 is applicable.

Next, the program operation regulation information 4 corresponding to the self application program section 2 is acquired (S3), and if the obtained program regulation information 4 is a resident operation, the processing request waiting section 6 causes the self application program section 2 to operate. After waiting for the generation of the processing request for (S4), the processing of the application program unit 2 is started after the waiting is released.
This queuing is released by issuing a processing request.

If the program definition information 4 obtained in S3 is a non-resident operation, the processing of the application program section 2 is started without waiting for the generation of a processing request.

When the processing of the application program section 2 is completed (S5), the program operation regulation information 4 corresponding to the own application program section 2 is acquired again (S6), and if it is the resident operation, the processing request is waited again. (S4). On the other hand, if it is a non-resident operation, the program is cleaned up (S7), and then the processing of the task program 3 is ended. Even if it is a resident operation, if the end of the processing system is detected, the program is immediately cleaned up (S
7), the process ends.

When activating the processing of the application program section 2, it is necessary for the activating side to perform the following processing similar to the conventional one. Specifically, when the application program unit 2 to be activated is recognized as a resident operation in advance by the activation side, the processing request is notified. On the other hand, when the application program unit 2 to be activated is recognized by the activation side as a non-resident operation, the corresponding task program 3 is activated.

By this operation, even if the task program 3 is not changed, only by changing the setting of the program operation regulation information 51 in the management table 5, the application program section 2 is switched to the resident operation or the non-resident operation. be able to.

In this operation, the program operation definition information 5 corresponding to the self-application program section 2 is based on the program name.
1 was searched, but instead of the program name 50, the program argument corresponding to each application program section 2 and its own process ID
Other information may be used.

Further, as for the waiting of the occurrence of the processing request using the processing request waiting unit 6, it is possible to adopt the same method as the conventional technique such as the waiting of the reception of the message queue and the waiting of the semaphore acquisition.

In this operation, the processing request waiting unit 6 is used to wait for the occurrence of a processing request only when the application program unit 2 is resident. However, even when the application program unit 2 is nonresident, the processing using the processing request waiting unit 6 is performed. You may decide to wait for the request generation. In this case, the same effect is obtained in that the resident operation and the non-resident operation can be realized without changing the task program 3 only by changing the operation starting method for the application program unit 2. The change of the operation starting method for the application program unit 2 is different from the case of the resident operation in that when the non-resident operation is performed, the application program 2 needs to be activated and the processing request is issued at the same time.

Further, when a processing request is generated after the processing of the application program section 2 is completed, the same effect can be obtained even if the processing is shifted to the processing of the application program section 2 regardless of the resident operation or the non-resident operation. . The program operation control methods in this embodiment and the following embodiments can be applied not only to the UNIX operating system but also to other operating systems.

Embodiment 2 In this embodiment, the execution of the application program is controlled according to the operation priority set for each application program unit 2, and will be described below with reference to FIG.

As shown in FIG. 3, the management table 5 in this embodiment comprises a program name 50, program operation regulation information 51 and operation priority 52. The operation priority 52 is set for each application program section 2 and indicates the priority of the corresponding application program section 2. The priority shown in FIG. 3 indicates that the larger the number, the higher the priority.

On the activation side, when activating the processing of the application program section 2, the following processing is performed. When the application program unit 2 to be activated is recognized as a resident operation by the activation side in advance, the processing request is notified. On the other hand, when the application program unit 2 to be activated is recognized by the activation side as a non-resident operation, the corresponding task program 3 is activated. Before the notification of the generation of the processing request or the activation of the corresponding task program 3 is performed, the operation priority 52 of the corresponding application program unit 2 is searched, and the activation side sequentially activates the operation priority 52 in descending order. To do.

Alternatively, when the operation priority of the own process is set according to the operation priority indicated in the processing request, either the process generation or the program loading necessary for starting the task program 3 or both processes are executed. It may be performed according to the operation regulation priority. In this case, the process generation and the program loading process can be matched with the operation priority of the application program unit 2, and the real-time designability of the processing system can be improved.

Embodiment 3 This embodiment relates to a program operation control system in which the information in the management table 5 is stored in the definition file 7 and a program operation control system in which the information in the management table 5 can be changed by a user operation unit.

FIG. 4 is a block diagram of the program operation control system in this embodiment. In the figure,
The program operation control unit 1, the application program unit 2, the task program 3, the management table 5, the program operation regulation information 51, and the processing request waiting unit 6 are the same as those in FIG. Reference numeral 7 is a definition file that describes the operation rules for each application program unit 2, and 8 is a file reading unit 8 that reads the contents of the definition file 7.
Reference numeral 9 denotes a user operation unit capable of changing the contents once set in the management table 5.

In this program operation control system, the file reading unit 8 reads the contents of the definition file 7 prior to the operation of all the application program units 2 included therein.
By setting as the program operation regulation information 51 of the management table 51, it is possible to easily determine the resident operation or the non-resident operation of each application program unit 2 in accordance with the description content of the definition file 7, and change it. It will be easy. Further, by changing the program operation regulation information 51 by the user operation unit 9, the operation of any application program unit 2 can be reset to resident or non-resident while the processing system is operating. The change of the program operation regulation information 51 by the user operation unit 9 is effective in that it can be performed while observing the operation status of the program operation control system.

Generally, in order to develop an application program for a real-time processing system, it is necessary to use a program environment for the real-time processing system. Therefore, it takes a long time to change the program operation and confirm the operation. Although labor is required, the need is eliminated by changing the definition file or the management table 5 by the user operation unit 9.

Embodiment 4 This embodiment relates to a program operation control system that suppresses duplicate operation of the same application program unit 2 when the application program unit 2 is operating using the program operation status information 53.

FIG. 5 is a block diagram of the program operation control system in this embodiment. In the figure,
The program operation control unit 1, the application program unit 2, the task program 3, the program operation regulation information 4, the management table 5, and the processing request waiting unit 6 are the same as those in FIG. However, in the management table 5, program operation status information 53 indicating the operation status of each of the application program units 2 is added and configured.

Next, the operation of this program operation control system will be described. The task program 2 on the started side is shown in FIG.
The same processing is performed, but the state "processing in progress" is set in the program operation status information 53 corresponding to the application program section 2 between S4 and S5 in FIG. Then, between S5 and S6 in FIG. 2 (including when the task program 3 in the non-resident operation is not started), the program operation status information 1
Set the state "unprocessed" to 0. That is, while the application program section 2 is being executed, the state "processing" is set in the program operation status information 53.

Next, the operation on the starting side of the application program section 2 will be described with reference to FIG. On the starting side, first, the program operation status information 53 corresponding to the application program section 2 is acquired based on the program of the target application program section 2 (S11). If the operation status acquired in S11 is the status "unprocessed" (S12), the information is set to the status "processing reserved" (S13), and then the program operation definition information corresponding to the application program unit 2 on the activated side is set. 51 is acquired (S14).

If the program operation regulation information 51 acquired in S14 is a resident operation, the application program section 2
To the processing request waiting unit 6 (S15), and if it is a non-resident operation, the corresponding task program 3 is activated (S16). On the other hand, if the operation status obtained in S11 is not the state "unprocessed", the target application program 2 is already started or will be started and the operation on the starting side is interrupted (S
17).

By this operation, the processing of each application program section 2 is not executed by a plurality of processes at the same time, and it is possible to avoid the application program section 2 from operating in parallel by a plurality of processes outside the processing system design. Therefore, the behavior as designed can be taken.

Further, in this operation, since the judgment whether the application program section 2 on the activated side is the resident operation or the non-resident operation is obtained from the program operation regulation information 51, the application program section 2 on the activated side is Even if the operation is reset from resident to non-resident or vice versa, the advantage is that it does not affect the invoking program.

In this embodiment, the program operation status information 53 corresponding to the application program section 2 on the activated side among the operations on the activated side is searched based on the program name of the activated type. It is also possible to use an identifier corresponding to each application program such as a program number and a character string instead of the name.

Embodiment 5. This embodiment relates to a program operation control system having a loading processing unit that operates to wait for a processing request even for the application program unit 2 that operates non-residently. FIG.
FIG. 3 is a block diagram of a program operation control system in this embodiment.

In the figure, the program operation control unit 1, the application program unit 2, the task program 3, the program operation definition information 4, the management table 5, and the processing request waiting unit 6 are the same as those in FIG. A loading processing unit 11 loads the application program unit 2 into the main memory by activating the task program 3 corresponding to the application program unit 2 when the application program unit 2 needs to be loaded. .

Next, the operation of the program operation control system in this embodiment will be described. FIG. 8 is a flowchart showing the operation procedure of the loading processing unit 11. The operation of the loading processing unit 11 is as shown in FIG. 8. First, when the system starts up, the program operation definition information 51 for all the application program units 2 is searched (S21,
S22), each application program unit 2 that is resident
The task program 3 corresponding to is activated (S23, S
24). S21 to S24 are executed for all the application program units 2 that are resident.

Next, the loading processing unit 11 uses the processing request waiting unit 6 to wait for a processing request to be issued to any of the non-resident application program units 2 (S25), and when the processing request is issued. , The application program section 2 until the processing of the task program 3 is completed.
After setting so as not to wait for the processing request corresponding to (S26), the target application program unit 2
The task program 3 corresponding to is activated (S27).

After S27, when the task program 3 is finished, the process request waiting of the application program unit 2 is returned to the waiting state (S28). When the end of the processing system is detected, the processing is immediately ended. The operation of the task program 3 is the same as that shown in FIG. 2, and when its execution is started, the corresponding application program section 2 performs a resident operation or a non-resident operation as defined by the program operation definition information 51.

According to this embodiment, unlike the first embodiment, the processing of the application program unit 2 is started regardless of whether the application program unit 2 on the activatable side operates residently or non-residently. It is only necessary to issue a request, and there is an advantage that the operation on the starting side can be made the same.

Since a new process necessary for starting the task program 3 is generated by the loading processing unit 11, it is necessary to perform process generation processing on the starting side when starting the application program unit 2 for non-resident operation. The time required to start the process is shortened and the performance is improved.

Also in the non-resident application program section 2, it is possible to prevent the same application program section from operating in parallel by a plurality of processes as in the resident operation, and the reliability of the system operation is improved.

In this embodiment, the management table 5 is made to store system state information indicating whether the operation state of the loading processing unit 11 is the "initial state" or the "steady state". May be processed.
The operation state of the loading processing unit 11 referred to here is a state before S25 in FIG. 7 and a "steady state" is a state after S25 in FIG.

The loading processing unit 11 sets the operation status of the loading processing unit 11 to the "initial state" in advance. After activating all the task programs 3 corresponding to the application programs 2 that are in the resident operation (S2
5)), the system state information is set to the state “steady state”. By not issuing the processing request of the application program unit 2 until the system state information is set to “steady state”, the operation start timing of the resident application program unit 2 can be matched, and the program operation can be performed. The certainty of operation of the control system is improved.

Further, in this embodiment, the operation priority 5 of each application program section 2 is the same as in the second embodiment.
2 is set, and either the process generation or the program loading, which is a process required when the task program 3 is started by the loading processing unit 11, is executed, the operation priority indicated by the program operation regulation information 51 or It may be performed according to the operation priority indicated in the processing request. In this case, the process priority of the application program unit 2 is 5 for the process generation and the program loading process.
3 and can improve the real-time designability of the processing system.

Sixth Embodiment The present embodiment relates to a program operation control system in which the loading processing unit 11 creates a process for executing the task program 3 so as to constantly suppress the number of processes created in the program operation control system. .

FIG. 9 is a block diagram of the program operation control system in this embodiment. In the figure,
The program operation control unit 1, the application program unit 2, the task program 3, the program operation regulation information 4, the management table 5, and the processing request waiting unit 6 are the same as those in FIG.

A loading processing unit 11 requests the loading processing program 13, which will be described later, to start the task program 3 corresponding to the application program unit 2 when the application program unit 2 needs to be loaded. To issue. A loading processing program 13 waits for a loading request to be issued, and loads the task program 3 into the main memory when the loading request is issued.

Reference numeral 12 is a process for continuously executing the processing of any of the task programs 3 or the loading processing program 13. In the management table 5, the number of simultaneously operating processes that defines the number of processes 12 is preset.

Next, the operation of the program operation control system in this embodiment will be described with reference to FIGS. 10 is a flowchart showing the processing procedure of the loading processing unit 11, and FIG. 11 is a flowchart showing the processing procedure of the loading processing program 13 and the task program 3.

First, the operation of the loading processing section 11 will be described. As shown in FIG. 10, the loading processing unit 11 first activates so that the processes 12 corresponding to the number of simultaneously operating processes preset in the management table 5 execute the loading processing program 13 (S31). Next, the program operation regulation information 4 for all the application program units 2 is searched (S32, S33), and a loading request is issued for the task program 3 corresponding to each application program unit 2 which is in the resident operation (S34, S33).
S35). This loading request is processed by the loading processing program 13. The operation of the loading processing program 13 will be described later.

Next, the loading processing section 11 uses the processing request waiting section 6 to wait for a processing request to be issued to any of the application program sections 2 that operate non-residently (S36). And when the processing request is issued,
After setting the processing request waiting corresponding to the application program section 2 until the processing of the task program 3 is completed (S37), the task program 3 corresponding to the application program section 2 which has made the processing request is set. Loading processing program 13 to load
A loading request is issued to (S38). Loading processing program 13 after issuing the loading request
The operation of will be described later. When the end of the processing system is detected, the process is immediately ended.

Next, the operation of the loading processing program 13 will be described. Loading processing program 1
As shown in FIG. 11, when the process 3 starts, the process waits for the loading request for the task program 3 (S41).

Next, the loading processing program 13
When the loading process request is acquired, the new process 12 is not generated so that the task program 3 to be loaded is executed by the current process 12.
The task program 3 is loaded into the main memory in a form of replacing the currently operating loading processing program 13, and the current process 12 re-creates the task program 3 again.
Is started (S42). When the end of the processing system is detected, the process is immediately ended.

The operation of the task program 3 is shown in FIG.
Although it is almost the same as (S51 to S56), after the processing of the application program section 2 is terminated by the non-resident operation, the processing of the task program 3 is not terminated, but the application program section 2 corresponding to the own task program 3 is terminated. After returning to the target of the processing request waiting in the loading processing unit 11 (S57), the loading processing program 13 is stored in the main memory by replacing the task program 3 which is currently operating without creating a new process 12. Loading is started, and execution of the loading processing program 13 is started (S58).

By executing S58, the loading processing program 13 waits again for the acquisition of the loading request for the task program 3 (S41). When the end of the processing system is detected, the program is cleaned up (S59) and the processing is immediately ended.

According to this embodiment, since the number of processes executing the task program 3 is limited to the maximum number of simultaneously operating processes set in the management table 5, the program operation control system limits the number of executing processes. By suppressing the dynamic process generation while the system is operating, it is possible to prevent the number of processes operating on the operating system from increasing easily. Therefore, the certainty of the operation of the program operation control system is improved.

Further, by making the size of the loading processing program 13 sufficiently smaller than that of the task program 3, the operation of the processing system can be performed as compared with the case where the task programs 3 corresponding to the number of simultaneously operating processes are made resident. It is possible to reduce the main memory capacity required for the main memory and improve the efficiency of main memory utilization.

Further, in this embodiment, similarly to the second embodiment, by setting the operation priority 52 of each application program section 2, the program can be executed according to the operation priority. Further, the loading process of the task program 3 performed by the loading process program 13 may be performed according to the operation priority 52. In this case, the process generation and the program loading process can be matched with the operation priority 52 of the application program unit 2, and the real-time designability of the processing system can be improved.

Embodiment 7. This embodiment relates to a program operation control system having a loading processing unit 11 that creates a new process even when the process executing the application program unit 2 or the loading processing program 13 disappears. FIG.
It is a block diagram of the program operation control system in this embodiment.

In the figure, the program operation control section 1, application program section 2, task program 3, program operation definition information 4, management table 5, processing request waiting section 6, loading processing section 11, loading processing program 13, and process 12 are shown. The description is omitted because it is the same as FIG. 9. The management table 5 in this embodiment stores program operation status information 53 indicating the operation status of the application program section 2 and a process ID 54 corresponding to each process.

Next, the operation of the program operation control system according to this embodiment will be described with reference to FIGS. 11 and 13. The operation of the loading processing program 13 in this embodiment is the same as that in FIG.

The operation of the task program 3 is the same as that of FIG. 11, but the program operation status information 10 corresponding to the application program section 2 between S54 and S55 in FIG.
A process is added so that the state “processing in progress” and its own process ID are set in, and the state “unprocessed” is set in the program operation status information 53 between S55 and S56. The operation of the loading processing unit 11 is as shown in FIG. Where S3
1 to S38 are the same as those in FIG.

When the loading processing unit 11 detects the disappearance of the process 12, the process 12 is activated again to execute the loading processing program 13 (S6).
1). The process ID 54 of the process 12 that disappeared next
The program operation status information 53 is searched based on (S6
2) Do it. As a result of the search, when the operation status of the application program unit 2 of the process 12 is “processing”, the abnormal termination of the application program unit 2 is notified to another application program unit 2 or outside the program operation control system ( S6
3).

Further, the program operation regulation information 51 is searched (S64), and if the application program section 2 is a resident operation, a loading request is issued to load the task program 3 corresponding to the application program section 2 (S65). On the other hand, if the operation is a non-resident operation, the processing request waiting of the application program section 2 is returned to the loading processing section (S66).

According to this embodiment, since a new process is created even if the process 12 disappears, the stability of the processing system is increased by keeping the number of processes constant.
Further, since the application program section 2 notifies that the application program has ended abnormally, and the application program section 2 that is resident is reloading, the reliability of the program operation control system is improved.

It is not always necessary to reload the application program section 2 that has abnormally terminated, and the stability of the program operation control system is improved by taking appropriate measures depending on the process extinction factor, the number of times, and the frequency. .

Embodiment 8 FIG. This embodiment relates to a program operation control system that appropriately thins out a message 14 indicating a processing request generated at an interval shorter than the processing time of the application program section 2 according to the processing content of the application program section 2. FIG. 14 is a block diagram of the program operation control system of this embodiment.

In the figure, the program operation control unit 1, the application program unit 2, the task program 3, and the processing request waiting unit 6 are the same as those in FIG. In this embodiment, the processing request is handled as a message 14, and the processing request waiting section 6 has a message queue 15 corresponding to each application program section 2.

In the message queue 15, the number of messages 14 to be stored and the number of messages 14 after the queue full occurs
Is set for each message queue, such as the action method when a message is sent. The above-mentioned operation characteristics are set at system startup by a processing system initialization program (not shown). In the following description, in each case, the message queue 15 has the message 14
It is assumed that the operating characteristics are defined so that up to two can be stored.

Next, the operation of the program operation control system according to this embodiment will be described with reference to FIG. Note that the operation of the task program 3 is the same as that of FIG. 2, and if it is a resident operation, the processing request waiting unit 6 waits for the processing request generation to the application program unit 2 and then waits until the application program unit 2 is released. Move to processing.

First, when one message 14MSG1 indicating a processing request is sent to the resident application program section 2, the application program section 2 is immediately activated and starts its processing (FIG. 15 (A)). After that, if messages 14MSG2 and MSG3 indicating two more processing requests are sent before the processing of the application program section 2 is completed, both messages will be accumulated in the message queue 15 (FIG. 1).
5 (B)).

At this stage, when messages 14MSG4 and MSG5 indicating two more processing requests are sent (FIG. 15C), the following will be performed according to the operation characteristics of the message queue 15 that are predetermined for each message queue. The content of the message held in the message queue 15 changes.

That is, when the operation of the message queue 15 is determined to be the normal FIFO type, the message queue 15 overflows by receiving the messages 14MSG4 and MSG5, so that the message queue 1
5 holds the messages 14MSG2 and MSG3 (FIG. 15 (D1)), but on the other hand, when it is determined that the two latest messages 14 should be held, the message queue 15 has the messages 14MSG4 and MSG5.
Will be held (FIG. 15 (D2)). Further, if it is determined that the last message 14 in the queue is updated when the message queue 15 is full, the message queue 15 has messages 14MSG2 and MSG2.
5 is held (FIG. 15 (D3)).

After that, when the processing of the application program section 2 is completed by the processing of the task program 3, the process returns to the waiting for the generation of the processing request, and the message queue 15 stores the message 14
Since the two are stored, the application program section 2 performs the processing twice again. At this time, the content of the message 14 to be processed is the normal FIFO as described above.
If it is the O type, it is MSG2 and MSG3, and if it is the operation of holding the latest message 14, MSG4 and MSG.
5 and the operation of updating the last message 14 in the queue differs depending on the operation of MSG2 and MSG5 and the operation of the message queue 15.

That is, according to this embodiment, the operating characteristic of the message queue 15 which is the processing request waiting unit 6 is appropriately determined when the message queue 15 is generated, so that the processing time is shorter than the processing time of the application program unit 2. The message 14 indicating the generated processing request can be appropriately thinned according to the processing content of the application program unit 2, and as a result, the number of processing times of the application program unit 2 is reduced, and the load on the processing system is temporarily increased. The effect that the operation is automatically suppressed is obtained in the case of the failure, and the stability and reliability of the operation of the processing system are improved.

In this embodiment, the processing request waiting unit 6 uses the message queue 15 that can store up to two processing requests, but the number of processing requests to be stored need not be limited to two, and the processing is not limited to two. The same effect can be obtained by using another method, such as the method of thinning out the request, which is determined according to the degree of importance of the processing request as shown in the present embodiment. Furthermore, the method of waiting for processing requests is also message queue 1.
It is not necessary to limit the number to 5, and the same effect can be obtained by using other methods such as a binary semaphore, a counter semaphore, and a method of waiting for the matching of bit patterns.

Embodiment 9 FIG. In this embodiment, a message queue 15 provided for each application program unit 2
The present invention relates to a program operation control system that stores the operation characteristics of the above as information in the management table 5.

FIG. 15 is a block diagram of the processing system in this embodiment. In the figure, the program operation control unit 1, the application program unit 2, the task program 3, the program operation regulation information 4, and the processing request waiting unit 6 are the same as those in FIG. 1, and the message 14 and the message queue 15 are the same as those in FIG. Therefore, the description is omitted.

The management table 5 stores the operation characteristics 55 of the message queue corresponding to each application program. As the operation characteristics 55 of the message queue, the number of stored messages and the thinning method of the message are set. There is. In FIG. 15, as the message thinning method,
Although designated as D1, D2, and D3, these D1 to D3 correspond to D1 to D3 in FIG.

In this embodiment, the processing request is handled as the message 14 as in the case of the above-described eighth embodiment, but the processing request waiting unit 6 corresponding to each application program unit 2 is used.
For each application program unit 2, operating characteristics such as the number of messages 14 to be stored and the action to be taken when the message 14 is sent after a queue full occurs are set. The set operating characteristics are stored in the management table 5 for each program, similarly to the above-mentioned program operation defining information 51.

By adopting this configuration, the operation characteristics of the processing request waiting unit 6 corresponding to each application program unit 2,
For example, in the case of the message queue 15, since the length of the queue and the thinning method of the message 14 indicating the processing request can be determined by the program operation regulation information 4, the processing is easier than in the eighth embodiment. The operation characteristics of the request waiting unit 6 can be changed.

Further, by setting the operation characteristic of the message queue 15 in the definition file 7 as in the third embodiment or by changing it from the user operation unit 9, the operation characteristic setting cannot be set more easily. It can be changed, and the efficiency of the development and maintenance work of the program operation control system can be improved.

[0104]

Since the present invention is configured as described above, it has the following effects. According to the first aspect of the invention, the task program processing includes an operation regulation information acquisition step, and the execution procedure of the application program is changed according to the operation regulation information acquired in the operation regulation information acquisition step. Therefore, it is not necessary to change the contents of the task program when changing the resident / non-resident operation of the application program, and it is possible to easily deal with the change in the program processing.

According to the second aspect of the invention, the operation regulation information is held as the description content of the file, and the operation regulation information held in the file is read in the reading step to be the information of the management table. The operation regulation information can be easily rewritten by changing the description content of the file.

In the third invention, even when the application program is set as the non-resident operation, the application program to be activated is activated after the processing request is issued to the application program. The activation side can activate the application program by issuing a processing request regardless of whether it is set to non-resident.

In the fourth aspect of the present invention, the processes of the preset number of processes activate the loading processing programs, and the loading processing programs execute the loading of the task programs. The number of processes can be limited to a certain number, and the certainty of operation of the program operation control system is improved.

According to the fifth aspect of the present invention, even if a process disappears, a new process is created, so that the number of processes in the program operation control system can be secured at a fixed number. The stability of operation is improved.

In the sixth invention, when the process disappears, the operation status of the application program started in the disappeared process is searched, and the task program having the application program started in the disappeared process is loaded. To issue a loading request to do
The reliability of the program operation control system is improved.

In the seventh invention, when a plurality of processing requests for the application program are issued, a predetermined processing request among the plurality of processing requests is deleted according to the processing content of the application program, so that the processing load is eliminated. And the stability of the operation of the program operation control system is improved.

According to the eighth aspect of the present invention, since the operation regulation defining the method of erasing the processing request issued to the application program is set in the management table, the operation regulation can be set easily and the program operation can be performed. It can flexibly respond to the operating status of the control system.

In the ninth invention, the task program acquires the operation regulation information of the application program forming the task program from the management table, and switches the application program execution procedure according to the obtained operation regulation information. It is not necessary to change the contents of the task program when changing the resident / non-resident operation of the application program, and it is possible to easily cope with changes in the program processing.

In the tenth aspect, the processing request holding means erases the processing request according to the operation characteristic set according to the processing content of the application program when a plurality of processing requests for the application program are issued. In order to
The processing load can be suppressed, and the operation stability of the program operation control system is improved.

[Brief description of the drawings]

FIG. 1 is a block diagram showing a configuration of a program operation control system according to a first embodiment.

FIG. 2 is a flowchart showing the operation of the task program according to the first embodiment.

FIG. 3 is a diagram showing a configuration of a management table 5 according to the second embodiment.

FIG. 4 is a block diagram showing a configuration of a program operation control system according to a third embodiment.

FIG. 5 is a block diagram showing a configuration of a program operation control system according to a fourth embodiment.

FIG. 6 is a flowchart showing the operation on the startup side in the fourth embodiment.

FIG. 7 is a block diagram showing a configuration of a program operation control system according to a fifth embodiment.

FIG. 8 is a loading processing unit 1 according to the fifth embodiment.
2 is a flowchart showing the operation of the first embodiment.

FIG. 9 is a block diagram showing a configuration of a program operation control system according to a sixth embodiment.

FIG. 10 is a flowchart showing the operation of the loading processing unit 11 in the sixth embodiment.

FIG. 11 is a flowchart showing operations of the loading processing program 13 and the task program 3 according to the sixth embodiment.

FIG. 12 is a block diagram showing the configuration of a program operation control system according to the seventh embodiment.

FIG. 13 is a flowchart showing the operation of the loading processing unit 13 in the seventh embodiment.

FIG. 14 is a block diagram showing a configuration of a program operation control system according to an eighth embodiment.

FIG. 15 is a conceptual diagram showing the operation of the message queue 15 of the processing request waiting unit 6 in the eighth embodiment.

FIG. 16 is a block diagram showing the configuration of a program operation control system according to the ninth embodiment.

FIG. 17 is a flowchart showing the operation of a conventional resident operation program.

[Explanation of symbols]

1 program operation control section, 2 application program section, 3
Task program, 5 management table, 6 processing request waiting section, 7 definition file, 8 file reading section, 9 user operating section, 11 loading processing section,
12 processes, 13 loading processing programs,
14 messages, 15 message queues, 51 program operation regulation information, 52 priority, 53 program operation status information, 54 process ID, 55 message queue operation characteristics.

Claims (10)

[Claims] 1. As a process of a task program having an application program to be activated, an operation regulation information acquisition step of acquiring operation regulation information indicating whether the application program is resident or non-resident, and the application program. A program executing step to be executed, the program executing step is executed after a processing request for the application program is issued when the operation specifying information acquired in the operation specifying information acquiring step indicates resident, and A program operation control method, which is executed after the above-mentioned operation regulation information acquisition step when the operation regulation information acquired in the operation regulation information acquisition step indicates non-resident. 2. A step of reading the operation regulation information from a file and using it as information of a management table, wherein the operation regulation information acquisition step obtains the operation regulation information from the management table. 2. The program operation control method according to claim 1, wherein 3. An operation regulation information acquisition step of acquiring behavior regulation information indicating whether an application program to be activated is resident or nonresident, and the behavior regulation information acquired in the operation regulation information acquisition step is nonresident. In this case, after the processing request is issued to the application program, the first activation step of activating the task program having the application program and the operation regulation information acquired in the operation regulation information acquisition step are A second activation step of activating the task program having the application program after the operation regulation information acquisition step when indicating resident. 4. A first loading processing program starting step of activating a loading processing program by a preset number of processes, and the loading processing program after the first loading processing program starting step. A first loading request step for issuing a loading request requesting that the task program be loaded by means of a first loading request program; and a first loading request program for loading the task program specified by the loading request. A program operation control method comprising a loading execution step. 5. A second loading processing program activating step of generating a new process and activating the loading processing program when one of the processes disappears. 4. The program operation control method described in 4. 6. The operation status information of the application program started in the disappeared process from the operation status information indicating whether or not the application program is being processed when one of the processes disappears. And a loading step of the task program having the application program started in the disappeared process when the operation status information of the application program searched in the searching step indicates that the processing is in progress. 6. The program operation control method according to claim 5, further comprising a second loading request step of issuing a loading request to the loading processing program activated in the second loading processing program activation step. 7. A request issuing step of issuing a processing request for an application program, and when a plurality of processing requests for the application program are issued, a predetermined one of the plurality of processing requests is given according to the processing content of the application program. And a erasing step of erasing a processing request. 8. An operation characteristic acquisition step of acquiring, from a management table, an operation characteristic that defines a method of erasing a processing request issued to an application program according to the processing content of the application program, the erasing step comprising: 8. The predetermined processing request of the plurality of processing requests is deleted according to the operation characteristic acquired in the operation characteristic acquisition step.
The described program operation control method. 9. A task program including an application program, and a management table in which operation definition information indicating whether the application program is resident or non-resident is set, and the task program includes: A program operation control system, characterized in that operation specification information of an application program constituting the task program is acquired from the management table, and the application program execution procedure is switched according to the acquired operation specification information. 10. A processing request holding unit for holding a processing request for an application program and setting an operation characteristic indicating a method of erasing the processing request for the application program according to the processing content of the application program, and the processing request. An application program that executes processing in the order of the processing requests held by the holding means, and the processing request holding means holds the processing request holding means in the processing request holding means when a plurality of processing requests are issued to the application program. A program operation control system characterized by erasing a processing request to be performed according to the above operation characteristics.