JP2570089B2 - Dependency consideration command interpreter - Google Patents

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

The present invention relates to an command interpreter of the computer, more particularly, to dependency consideration command interpreter apparatus can automatically generate the files needed for the execution of application programs executed instruction by the command .

[0002]

2. Description of the Related Art When a command including an application name of an application program to be executed and arguments and file names required for executing the application program is input, the conventional command interpreter simply passes the arguments and the file name to the application program. Met.

[0003]

As described above, the conventional command interpreter only passes arguments and file names included in the input command to the application program, and generates the arguments and file names before executing the application program. Because the execution conditions such as whether a file that must be executed has been generated and whether the application program that must be executed before executing the application program has been executed have been determined on the application program side, If a command to execute an application program whose execution conditions are not satisfied is issued,
There was a problem that it was difficult to return to the work.

[0004] It is an object of the present invention to provide a dependency-considering command interpreter apparatus which can reduce the number of cases where it is necessary to return to the work even when a command for executing an application program whose execution conditions are not satisfied is input. It is in.

[0005]

SUMMARY OF THE INVENTION In order to achieve the above object, the present invention provides a file dependency table in which a method of generating each file is registered in correspondence with a file name, and a file dependency table in which each application program is associated with an application name. and application-dependent relationship table the file name of the application name and the required files that must be generated prior to the execution of each application program of mandatory application program that must be executed before the execution is registered, and the execution history of the application program a history table generation record file is registered, by the command including the application name that is registered in the application dependency table is input, the application dependency table and the footwear A required file determination means for determining whether or not a required file for the application program instructed to be executed by the command with reference to the table has been generated; and determining that the required file has not been generated by the required file determination means. File automatic generation means for automatically generating an essential file according to a generation method registered in the dependency table; and determining whether or not the essential application program for the application program instructed to be executed by the command has been executed. A required application determining unit that determines based on the history table and outputs an error message by determining that the application has not been executed is provided.

[0006]

When a command including an application name registered in the application dependency table is input, the essential file determination means refers to the application dependency table and the history table to execute the application program instructed by the command. It is determined whether the required file for has been generated.

If it is determined that the essential file has not been generated, the automatic file generation means automatically generates the essential file according to the generation method registered in the file dependency table.

The essential application determining means determines whether or not the essential application program for the application program instructed to be executed by the command has been executed based on the application dependency relationship table and the history table, and judges that the application program has not been executed. Outputs an error message.

[0009]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Next, embodiments of the present invention will be described in detail with reference to the drawings.

[0010] Figure 1 is a block diagram of an embodiment of the present invention, the command interpreter device (hereinafter, command interface
1 ) , a program execution unit 2, and an input / output unit 3.

The command interpreter 1 includes a task setting unit 10, a registration determining unit 11, and an essential file determining unit 1.
2, an automatic file generation unit 13, an essential application determination unit 14, a task variable area 15, an application dependence table 16, a file dependence table 17, and a history table 18.

FIG. 2 is a diagram showing an example of the configuration of the application dependency relationship table 16. An application name field 16-1 in which an application name of an application program is registered, and if the application program is not executed before the application program is executed, An application-dependent field 16-2 in which an application name of an application program (essential application program) to be registered is registered, and a file name of a file (essential file) that must be generated before the application program is executed are registered. And a file dependent field 16-3. The application dependency table 16 includes, for example, a circuit diagram creation application program,
The application names of application programs related to each other, such as file conversion roots, placement application programs, and wiring application programs, the application names of essential application programs, and the file names of essential files are registered.

FIG. 2 shows an example of application name app1.
Before the application program is executed, a file whose file name ends with “.01” must be generated, and the application program with the application name app2 becomes the application program with the application name app1 before it is executed. Is executed, and a file whose file name ends with “.02” must be generated.
Note that * is a special character instructing to substitute a fixed file name.

FIG. 3 is a diagram showing an example of the configuration of the file dependency relationship table 17, in which a file name field 17-1 in which a file name of a file is registered and a file generation method field in which an automatic generation method of the file is registered 1
7-2.

In the example of FIG. 3, there is no automatic generation method for a file whose file name ends with ".01", and the file name is ".01".
A file ending with "02" indicates that the file can be automatically generated by executing the application program app1.

FIG. 4 is a diagram showing an example of the configuration of the history table 18, in which a task name field 18-1 in which a task name of a task is registered, an order field 18-2 in which an execution order is registered, an executed application It comprises an execution application field 18-3 in which the application name of the program is registered, and a generated file name field 18-4 in which the file name of the generated file is registered.

In the example of FIG. 4, the task with the task name user1 first executes the application program with the application name app1 to generate a file with the file name f1.02, and then displays the file name list (1s-1).
Has been executed.

FIG. 5 is a flowchart showing a processing example of the command interpreter 1. The operation of this embodiment will be described below with reference to the drawings. In FIG. 5, the solid line indicates the flow of processing, and the broken line indicates the flow of table reference.

First, a user inputs a task name of a task to be executed from the input / output unit 3.

When the task name is input, the task setting means 10 in the command interpreter 1 sets the task name in the task variable area 15 (step S1).

Thereafter, the user inputs from the input / output unit 3 a command including an application name of the application program to be executed, arguments required for executing the application program, and a file name.

When the registration judging means 11 in the command interpreter 1 detects that the command has been input (step S2), the application name included in the command is entered in the application name field 16-1 of the application dependency table 16. It is determined whether or not the information has been registered (step S3).

If the application is not registered (No in step S3), the registration judging unit 11 requests the program execution unit 2 to execute the application program of the application name included in the command.
(Step S11).

If it has been registered (step S3
If yes, the registration judging unit 11 passes control to the essential file judging unit 12.

When the control is passed from the registration judging means 11, the essential file judging means 12 determines whether all the essential files for the application program instructed to be executed by the input command have been generated or not, in the task variable area 15, the application dependent area. The determination is made based on the contents of the relationship table 16 and the history table 18 (step S
4). When it is determined that all the essential files have been generated, the control is performed by the essential application determination unit 14.
When it is determined that there is an indispensable file that has not been generated, the control is passed to the file automatic generation unit 13.

The process will be described in detail. First, the essential file determination unit 12 refers to the application name field 16-1 and the file dependence field 16-3 of the application dependence table 16 and determines the application program designated to be executed by the command. Get the file name of the required file for.

After that, the essential file determination means 12 acquires the task name set in the task variable area 15.

Further, the essential file judging means 12 refers to the task name field 18-1 and the generated file name field 18-4 of the history table 18 to determine the area of the task name field 18-1 where the task name is registered. It is determined whether or not all the file names acquired from the application dependency relationship table 16 are registered in the corresponding generated file name field 18-4, that is, whether or not all the essential files have been generated.

When it is determined that all the essential files have been generated (Yes in step S4), the control is passed to the essential application determination means 14, and it is determined that there is an essential file that has not been generated (step S4 determines No) passes control to the file automatic generation means 13. When transferring control to the automatic file generation means 13, the essential file determination means 12 notifies the automatic file generation means 13 of the file names of the essential files that have not been generated.

When the file name of an indispensable file that has not been generated is passed from the indispensable file judging means 12, the automatic file generating means 13 determines whether or not the conditions for automatically generating the file are satisfied. Judgment is made based on the contents of the relation table 16, the file dependence table 17, and the history table 18.
(Step S5). When it is determined that the conditions for automatic generation are not satisfied (No in step S5), an error message is output to the input / output unit 3 (step S10).
When it is determined that the file is complete (Yes in step S5), the essential file is automatically generated (step S6), and the control is passed to the essential application determination unit 14.

This processing will be described in detail as follows.

First, the file automatic generation means 13 refers to the file dependency table 17 and determines whether or not the generation method of an ungenerated essential file is registered in the file generation method field 17-2. If the generation method has not been registered, an error message is output to the input / output unit 3 assuming that the conditions for automatically generating the essential file are not satisfied (step S10).

If the file generation method is registered in the file generation method field 17-2 and the generation method instructs the execution of the application program, the application dependence table 16
To check whether there is an essential application program for the application program.

If the required application program does not exist, the file execution method field 17-
A request is made to execute the application program with the application name registered in Step 2 (Step S6). As a result, the application program is executed by the program execution unit 2, and an essential file is generated.

If an essential application program exists, the file automatic generation means 13 first
The task name set in the task variable area 15 is obtained.

[0036] Then, the automatic file generating unit 13 refers to the task name field 18-1 and execution application field 18-3 in the history table 18, the task
Execution application fields corresponding to the area of the task name field 18-1 metric name is registered 18-3
It is checked whether or not the application name of the essential application program is registered in the area of (1).

If not registered, that is, if the required application program has not been executed, an error message is output to the input / output unit 3 assuming that the conditions for automatically generating the required file are not satisfied (step S10). If the application has been registered, that is, if the essential application program has been executed, the program execution unit 2 is instructed to execute the application having the application name registered in the file generation method field 17-2 in order to generate the essential file. Request execution of the program
(Step S6). As a result, the application program is executed by the program execution unit 2, and an essential file is generated.

The essential application determining means 14 is the essential file determining means 12 or the automatic file generating means 13
When the control is passed from, it is determined based on the contents of the task variable area 15, the application dependence table 16 and the history table 18 whether or not all the essential application programs for the application program instructed to be executed by the command are executed ( Step S7).

When it is determined that all the programs have been executed (Yes in step S7), information on the application program to be executed this time is added to the history table 18 (step S8), and further executed in the program execution unit 2. Request execution of the application program (step S9). When it is determined that an unexecuted essential application program exists (step S7)
No) outputs an error message to the input / output unit 3 (step S10).

To explain this processing in detail, the essential application determining means 14 refers to the application name field 16-1 and the application dependence field 16-2 of the application dependence table 16,
It is determined whether or not there is an essential application program for the application program instructed to be executed by the command.

If the required application program does not exist, the contents related to the application program instructed to be executed by the command are added to the history table 18 (step S8), and thereafter, the execution of the application program is requested to the program execution unit 2. Yes (step S9).

When there is an essential application, first, the task name set in the task variable area 15 is obtained. Then, referring to the task name field 18-1 and the execution application field 18-3 of the history table 18, the area of the execution application field 18-3 corresponding to the area of the task name field 18-1 in which the task name is registered. It is checked whether or not all the application names of the essential application programs are registered.

If all the application names have been registered, that is, if all the essential application programs have been executed, the processing of steps S8 and S9 is performed. If not registered, that is, the unexecuted essential application has been executed. If exists, the process of step S10 is performed.

Each time a command instructing execution of an application program is input from the input / output unit 3, the above-described processing is repeated.

Now, for example, the contents of the application dependence table 16, file dependence table 17, and history table 18 are as shown in FIGS. 2, 3, and 4, respectively, and the task name user1 is set in the task variable area 15. Let's consider the case.

At this time, as can be seen from FIG. 4, the application program app1 has already been executed in the task having the task name user1, and the file f1.02 has been generated.

In this state, it is assumed that the user inputs a command including the application name app2 and arguments and file names required for executing the application program from the input / output unit 3.

The application name app2 contained in the above command is stored in the application dependency table 1
6 is registered in the application name field 16-1, so that the determination result in step S3 is yes,
Step S4 is performed.

In step S4, it is determined whether or not an essential file of the application program app2 has already been generated. In the case of this example, as can be seen from the file dependence field 16-3 of the application dependence table 16 shown in FIG. 2, the essential file of the application program app2 has the file name “.0”.
2 ". As shown in FIG. 4, the task name u in the generated file name field 18-4 is used.
A file name f1.02 ending in “.02” is registered in an area related to ser1. Therefore, step S
In step S4, it is determined that the essential file of the application program app2 has already been generated.
Step 7 is performed.

In step S7, it is determined whether or not all the essential application programs of the application program app2 have been executed. In this case, FIG.
As can be seen from the application dependency field 16-2 of the application dependency table 16 shown in FIG.
The essential application program for the application program app2 is the application name app
p1. As shown in FIG. 4, the task name user in the execution application field 18-3 is displayed.
The application name app1 is registered in the area related to 1. Therefore, in step S7, it is determined that all the essential application programs of the application program have been executed, and the process of step S8 is performed.

In this example, as described above, step S4
The processing of step S7 is performed subsequently to step S7. If the area related to the task name user1 in the generated file name field 18-4 of the history table 18, ".
02 is not registered, the application program app1 is executed based on the contents of the file generation method field 17-2 of the file dependency table 17 of FIG.
02 is generated, and then the process of step S7 is performed.

In the above-described embodiment, if the essential application determining means 14 determines that any of the essential application programs is not executed (step S7 is no), an error message is output. However, it is also possible to request the program execution unit 2 to execute an unexecuted application program, and then perform the processing in step S8. However, when an unexecuted essential application program is automatically executed, a huge application program is automatically executed, and a lot of resources and time may be consumed. It is desirable to have the user check the contents of the program in advance.

[0053]

As described above, according to the present invention, when an essential file for an application program instructed to be executed by a command is not generated, the automatic file generating means for automatically generating the essential file is provided. If the required application program for the performed application program has not been executed, an essential application determination unit that outputs an error message is provided. In addition, there is an effect that a framework which is difficult to be applied to other than the routine work can be applied to the irregular work.

[Brief description of the drawings]

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

FIG. 2 is a diagram illustrating a configuration example of an application dependency relationship table 16;

FIG. 3 is a diagram illustrating a configuration example of a file dependency relationship table 17;

FIG. 4 is a diagram showing a configuration example of a history table 18.

FIG. 5 is a flowchart illustrating a processing example of the command interpreter 1;

[Explanation of symbols]

 REFERENCE SIGNS LIST 1 command interpreter 2 program execution unit 3 input / output unit 10 task setting unit 11 registration determination unit 12 essential file determination unit 13 automatic file generation unit 14 essential application determination unit 15 task variable area 16 application Dependency table 17: File dependency table 18: History table

Claims (2)

(57) [Claims] 1. A file dependency table in which a generation method of each file is registered according to a file name, and an application of an essential application program which must be executed before execution of each application program according to an application name An application dependency table in which names and file names of essential files that must be generated before execution of each application program are registered; a history table in which application program execution histories and file generation histories are registered; When a command including the application name registered in the dependency table is input, the execution command is executed by the command with reference to the application dependency table and the history table. Required file determination means for determining whether a required file for the generated application program has been generated, and a generation method registered in the file dependency table by determining that the required file has not been generated by the required file determination means File automatic generation means for automatically generating an essential file in accordance with the following, and determining whether the essential application program for the application program instructed to be executed by the command has been executed based on the application dependency table and the history table, and executing dependency consideration command interpreter apparatus characterized by comprising an essential application determining means for outputting an error message by determining the no finished. 2. A method for generating the file dependencies considered command interpreter apparatus according to claim 1, characterized in that it comprises the application name of an application program for generating files.