JPH0782472B2 - Command analysis processor - Google Patents

Description

DETAILED DESCRIPTION OF THE INVENTION [Table of Contents] Outline Industrial field of application Conventional technology (FIGS. 9 and 10) Problems to be solved by the invention Means for solving problems (FIG. 1) Action Embodiment (1) Configuration of the present invention (FIGS. 2 to 4) (2) Operation of the embodiment (FIGS. 5 to 8) Effect of the invention [Overview] Command name table, operand table, With a flag table, when checking commands,
First, the command name is sequentially output from the command name table, the presence or absence of the command is checked, then the operand table of the command name is read, the operand of the command is compared with the operand name read from this operand table, and then the flag Read the table and check if it is in line with the field item.

[Industrial application field]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a command analysis processing device, and more particularly to a command analysis processing device that automatically checks whether or not an input command is accurate.

[Conventional technology]

Various commands are used to control the data processing device. As shown in FIG. 9, when the command type is broadly divided into (1) only the command name and no operand, (2) the operand 1 is indispensable, but the operand 2 can be omitted ( 3) When operand 1 is mandatory and there is a sub parameter after "=", and operand 2 is optional and there is a sub parameter, (4) There are four cases of the above mixture, and there are multiple operands. Have common command names.

One example of the command is shown in FIG.

In this case, if CREATE is CREATE or 10000REC is written when only 1000 records can be processed, an error will occur, so it is necessary to check this in advance.

[Problems to be solved by the invention]

In this way, there are multiple types of commands.In some commands, the existence of a keyword causes an error in the existence of another command, or when there is only a keyword and no sub-parameter exists. There are various types of cases, such as whether or not operands and subparameters can be omitted, and there are multiple subparameter formats for one keyword. Therefore, these cannot be automatically processed, and humans have visually checked them.

SUMMARY OF THE INVENTION It is an object of the present invention to provide a command analysis processing device for checking whether or not a command is correct when it is created in order to improve the above problems.

[Means for solving problems]

In order to solve the above problems, the present invention prepares a command name table 1, an operand table 2, and a flag table 3 as shown in FIG. Then, whether the CREATE) is correct or not is sequentially compared with the command names registered in the command name table 1. This allows you to check that there is a command error when you write something like CREATE. Next, the operand part (FSIZE to ID in the example of FIG. 10) is taken out, and the operands (FSIZE, TYPE) are entered one by one in the operand table 2 and compared with the available operands for the command. Check the format and generate an error if they do not match. Then flag the operand
Check if the subparameter length is as specified by checking with Table 3.
Check whether required parameters are included.

[Action]

According to the invention, the command is the command name table 1,
By checking the operand table 2 and the flag table 3 sequentially, the validity can be checked very easily.

〔Example〕

 (1) Configuration of the Invention The configuration of the invention will be described with reference to FIGS. 2 to 4.

FIG. 2 is a block diagram of an embodiment of the present invention, FIG. 3 is an explanatory diagram of a command name table, an operand table, and a flag table used for command analysis, and FIG. 4 is a structural relationship explanatory diagram of each table. .

In FIG. 2, the same parts as in FIG.
Is a memory, command name table 1, operand
Table 2, flag table 3, etc. provided,
5 is a command input section for inputting commands,
A processor 10 includes an input data holding unit 11, an access control unit 12, a command check unit 13, an operand check unit 14, a sub-parameter check unit 15, a control unit 16 and the like.

In the command name table 1, as shown in FIG. 3A, the command name and the addresses of the operand table and the flag table for the command are entered. This command name table 1 is 1-1, 1-2, 1-
It has three fields of 3 and the command name is set in the field of field 1-1 by field 1-2.
Is set to the operand table 2 and fields 1-3 are set to the flag table 3. The relationship between command name table 1, operand table 2 and flag table 3 is fourth
Shown in the figure.

As shown in FIG. 3B, the operand table 2 is a table having operand names and default values for the operands, and there is one table for each command. The operand table 2 has two fields 2-1 and 2-2, and an operand name is set in the field 2-1. In field 2-2, the default value of the operand, that is, the operand in the command. The default value is set if is not specified. If the operand is described, its value is
Set to 2. As will be described later, when executing a command, this command is executed while looking at this operand table.

The flag table 3 is a table in which information regarding operands during command analysis is set as flags.
The flag table 3 has five fields 3-1 to 3-5, an operand name is set in the field 3-1, and a designation flag, that is, an operand in the field 3-2 is assigned to the command. Flag is set to specify whether or not it can be described. An error will occur if this operand is described when this specification flag is off.

In the field 3-3, the subparameter length, that is, the maximum length of the subparameter equal to or less than "=" of the operand is set. When this value is "0", the sub parameter cannot be described in the operand.

The field 3-4 is a duplication flag, that is, a flag for determining whether or not the same operand is described more than once, and is used for making an error when more than one is described. A mandatory flag, that is, a flag indicating that the description of the operand is mandatory is written in the field 3-5. An error will occur if the operand with this mandatory flag is not described.

The input data holding unit 11 temporarily holds the command input from the command input unit 5.

The access control unit 12 is necessary for analyzing whether the command held in the input data holding unit 11 is correct,
The processing is to access the command name table 1, the operand table 2, the flag table 3 and the like.

The command check unit 13 checks whether the command name held in the input data holding unit 11 matches one of the command names written in the field 1-1 of the command name table 1. .

The operand check unit 14 checks whether or not the operand of the command held in the input data holding unit 11 is written in the field 2-1 of the operand table 2, and this field 2-1 Are sequentially read to check whether they match.

The sub-parameter check unit 15 checks whether the sub-parameter of the command operand held in the input data holding unit 11 corresponds to the flag written in the flag table 3.

The control unit 16 performs various controls for analyzing the command input from the command input unit 5. For example, the control unit 16 sequentially reads command names from the command name table 1 to the access control unit 12 and outputs the command names to the access control unit 12.・ Check section 13
To the input data holding unit 11 to check whether the command name held in the input data holding unit 11 is correct or not.

(2) Operation of Embodiment FIG. 5 shows the operation of the embodiment of the present invention shown in FIG.
Based on FIG. 8, an example of the command shown in FIG. 6 will be described with reference to other drawings. In addition, in FIG.
ADDPS is a command for registering data from one file to another file, EPFMEM indicates the member name of the file to be registered, REP indicates replacement, and CLASS indicates the EPFMEM member type. In this example, the type is data DAT. This shows the command to register in the DAT section of the ABC member name.

When performing command analysis for the first time, first
The field 2-2 of the table 2, that is, the default value area of the operand, and the field 3-4 of the flag table 3, that is, the overlap flag area are initialized. The operand table and the flag table are provided corresponding to the command names entered in the command name table. For ADDPS, the operand table 2 and the flag table 3 are initially set as shown in FIG. Be converted. operand·
In Table 2, blanks are entered for MEMBER and EPFMEM, LOD is entered for CLASS, and 0 is entered for CVT and REP. Note that blank here means that anything can be entered. The operand names of the flag table 3 are written in the same order as the operand names of the operand table, and 0 is written as an initial value in each of the duplicate flag areas.

By the way, the command name portion (ADDPS) of the command input from the command input unit 5 as shown in FIG.
Is transmitted to the command / check section 13. Further, the field 1-1 of the command name table 1 is read by the access control unit 12 and sequentially compared in the command check unit 13. At this time, if there is no command name held in the input data holding unit 11 that matches the command name written in the field 1-1, the command held in the input data holding unit 11 is determined to be an error, and control is performed. The unit 16 performs error handling. However, when a match is detected, the command check section 13 reports this to the control section 16, so that the control section 16 sends the matched field names 1-2 and 1-3 to the access control section 12. Read and know the addresses of operand table 2 and flag table 3.

Next, the control unit 16 causes the operand check unit 14 to operate, and the operand “MEMBER” up to the first “=” (if there is no “=”) from the input data holding unit 11 is input to the operand check unit 14. Output. If the command is in the format shown in FIG. 9 (1), or if the check for all operands is completed and there is no operand to be taken out, the control unit 16 shifts to the check end process and executes (executes) the command. It will be.

However, if there is an operand to be taken out, the control unit 16 reads the field 2-1 of the operand table 2 of the command to the access control unit 12 based on the address obtained above, and transfers it to the operand check unit 14. To do. Accordingly, the operand check unit 14 checks whether or not the operand of the command held in the input data holding unit 11 matches among the operands written in the field 2-1 of the operand table 2. The result is reported to the control unit 16. If there is no match, error processing is performed. If there is a match, the control unit 16 controls the field 3 of the flag table 3 obtained above.
-2 is read, error processing is performed if the designated flag for that operand is not on, and if it is on, the duplication flag of field 3-4 is read. At this time, if the duplicate flag for that operand has already been turned on, it means that the same operand existed earlier, so error processing is performed, and if it is not turned on, this is turned on.

Then, the field 3-3 of the flag table 3 is read to check whether the subparameter length of the operand is zero. For example, if the operand "REP" is zero, for example, "1" is set as information indicating that the operand is specified in the field 2-2 of the operand table 2 as shown in FIG. Also, the field 3-3
If is not zero, information below "=" of the operand (6th
In the example of the operand EPFMEM in the figure, "ABC"), that is, the subparameter is set to the field 2-2.

When the check on one operand is completed in this way, the control unit 16 marks the operands that have been checked, and checks the unchecked operands REP and CLASS.
The same process is sequentially performed on the. In this way, when the check for the command of FIG. 6 is completed, the operand table 2 and the flag table 3 are
The state is as shown in the figure.

At this time, when the field 3-5 of the flag table 3 is on but the field 3-4 is off, it is an error because an essential operand in the command is not described.

When it is determined that the command input from the command input unit 5 is normal, the processing of the command is performed with reference to the operand table 2.

In the above description, an example of checking whether or not the operands match with each other using the operand table 2 has been described, but it is also possible to use the flag table 3 as a matter of course.

〔The invention's effect〕

According to the present invention, error checking of commands can be easily performed by checking error checking, validity checking, etc. for a series of commands in each of the tables. Also, even if there is a change in the syntax of the command description,
This can be dealt with simply by manipulating the flags in the table.
Therefore, it is possible to easily perform analysis processing suitable for various commands. Further, since the subparameter information can be set in the default value information column of the operand table based on the input command, this operand table can be provided to the subsequent command execution processing.

[Brief description of drawings]

FIG. 1 is a diagram for explaining the principle of the present invention, FIG. 2 is a structural diagram of an embodiment of the present invention, and FIG. 3 is a command name table, an operand table,
Flag table explanatory diagram, FIG. 4 is an explanatory diagram of the configuration relationship of each table, FIG. 5 is an explanatory diagram of the command analysis operation of the present invention, and FIG. 6 is a command using each table of FIG. 7 and FIG. FIG. 7 is an explanatory diagram of the initialization state of each table, FIG. 8 is the state of each table after command analysis, FIG. 9 is an explanatory diagram of the command format, and FIG. 10 is an example of the command. 1 ... Command name table 2 ... Operand table 3 ... Flag table, 4 ... Memory 5 ... Command input section, 10 ... Processor 11 ... Input data holding section 12 ... Access control section 13 ... Command check section 14 …… Operand check section 15 …… Sub-parameter check section 16 …… Control section

 ─────────────────────────────────────────────────── ─── Continuation of the front page (72) Inventor Kuniko Ajiro 1015 Kamiodanaka, Nakahara-ku, Kawasaki-shi, Kanagawa Fujitsu Limited (56) Reference JP-A-58-70361 (JP, A)

Claims (1)

[Claims] 1. A command name table (1) holding a plurality of sets of command name information, address information to an operand table corresponding to the command name, and address information to a flag table corresponding to the command name. An operand table (2) that holds a plurality of sets of operand information and default value information of the operand, operand information, and designated flag information that designates whether or not the operand can be described in the corresponding command , Sub-parameter length information that specifies the maximum length of a sub-parameter associated with the operand, and duplication flag information for determining whether the operand is described redundantly,
A flag table (3) holding a plurality of sets of essential flag information indicating that the description of the operand is essential, command input means (5) for inputting a command, and whether the command name of the input command is valid A command check means (13) for checking whether or not an operand check means (14) for checking whether an operand portion of an input command is valid, and a subparameter portion for an input command are valid or not The sub-parameter check means (15) for checking whether or not is provided, and the validity of the inputted command is analyzed by checking at least the contents of the command name table (1) and the flag table (3). Set the subparameter information in the default value information column of the operand table (2) based on the entered command. Command analysis processing apparatus characterized by processing that allowed to provide the operand table (2) for subsequent command execution processing.