JP2001134424A - System parameter creation method, system parameter creation device, computer readable recording medium recording system parameter creation program, and computer readable recording medium storing system parameter creation data - Google Patents

Abstract

(57) [Summary] A GUI for creating parameters such as system definition information and commands cannot create parameters for different systems. And when the system is upgraded,
The GUI had to be changed. A description is provided for a system parameter description rule and a menu displayed on a hierarchical display GUI in a metadata table and a candidate value table of a repository DB, and created parameter information is stored in an instance table of the repository DB.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

TECHNICAL FIELD The present invention relates to a computer GU.
Using I, the program inputs (in a program that functions by reading parameters made of characters,
The program refers to parameters stored in datasets and files.) The present invention relates to a technique for creating and managing system parameters.

[0002]

2. Description of the Related Art Conventionally, parameters used by a system, such as system definition information and commands, have been created using a GUI. At this time, a unique parameter creation GUI was used for each system. For example, JP-A-4-2601
No. 49 is a method of creating definition information using a GUI and distributing the definition information to each computer. Here, since the GUI for creating the system definition information is unique to the system, it is necessary to create a GUI for each system. Also,
Even in the same system, when the description format of the system definition information is changed, it is necessary to correct the GUI.

Japanese Patent Laid-Open Publication No. 3-278128 discloses a GUI for starting a command program, but does not disclose any specific means for realizing the GUI.

[0004]

In the above prior art,
No consideration is given to creating parameters for different systems, and there is a problem that a program and a GUI for creating system parameters must be created for each individual system. Moreover, when the system parameters increase due to the system version upgrade, it is necessary to recreate the parameter creation program and the GUI. Also,
Since the GUI differs for each system, there is also a problem that the user must remember the operation of the GUI for each system.

A first object of the present invention is to not specialize a program, a GUI, and data for creating system parameters for only one system. A second object of the present invention is that even if the number of system parameters to be created increases or the description format is changed, it is not necessary to modify the parameter creation program or the GUI. A third object of the present invention is to provide a unified user interface even if the systems for which parameters are created are different. A fourth object of the present invention is to make it possible to reuse previously created parameter information without re-creating system parameters when the system is upgraded.

[0006]

The above object is achieved by the following method. The description rules of the system parameters are not stored in the parameter creation program or the GUI, but are stored in the database. The GUI displays a parameter name and a specifiable value as a menu.

That is, the GUI structure is common, and the system parameter creation program is also common. Then, the description rules of the system parameters are separated and stored in the database as some tables.

The user reads the GU from the database and
By selecting a menu on the GUI displayed on I, a target system parameter is created.
The menu displayed on the GUI is not fixed, but is changed according to the description rules of the system parameters registered in the database. As a result, various system parameters can be constructed without changing the GUI. The created system parameter information is stored in the database according to certain rules regardless of the system.

For example, when the parameter description rule of the A system is registered in the database, the user can use the GUI
The system A parameters are created by selecting the system A parameters displayed as a menu above.
To create parameters for system B, add the parameter description rules for system B to the database,
Create the parameters of the B system without changing the UI.

[0010]

DESCRIPTION OF THE PREFERRED EMBODIMENTS The system parameters represent the configuration of a computer system in a text format, and cause a program to recognize the initial state of the configuration information of the computer system. In other words, the configuration information is a definition of an environment in which the program runs, and for example, in the case of online connection, the configuration information includes a terminal name, a terminal type, a communication path, a communication procedure, and the like.

FIG. 1 shows an apparatus configuration for creating such system parameters (the system parameters created here are used in a computer system (not shown)). In FIG. 1, reference numeral 1 denotes a client PC, in which a system configuration management program 2 is stored.
The hierarchical display GUI 3 schematically shows a GUI created and displayed by the GUI creation program. The text generation program 5 includes definition information as illustrated,
Generate commands. The repository API (application program interface) 4 is an interface for sending requests from the GUI creation program and the text generation program to a database described later and receiving data from the database.

On the other hand, a repository database 12 is stored in the server 11. The repository DB 12 stores a metadata table 13, an instance table 14, and a candidate value table 15, which will be described later.

The repository API 4 is a repository DB 12
SQL (DB operation language) instead of sending a request directly to
And pass it to ODBC6. The ODBC 6 is an interface for connecting to a DB machine on a network. Therefore, the definition information distributed to each machine can be collected in one repository DB 12 via the ODBC 6. Further, the use of the standard SQL that is common throughout the world does not limit the DB system that manages the repository DB 12. The use of the ODBC interface is an example, and the present invention is not limited to this.

In the present embodiment, the repository DB is located on the server 11, but may be provided on the client PC 1.

The outline of the present invention will be further described with reference to FIG. Interaction with the user is performed interactively using the hierarchical display GUI3. The metadata table 13 and the candidate value table 15 in the repository DB 12 have system definition information and rules of command parameter description format. The parameter description format rule is information such as what parameters the definition statement or command is composed of and what values can be specified.

The hierarchical display GUI 3 is a metadata table 1
The menu to be displayed changes according to the rules of No. 3 and the candidate value table 15. The user has a hierarchy display GUI3
By selecting appropriate items from a menu displayed by the user, definition information and a command structure can be created. The created definition information and command structure are stored in the instance table 14.

The text generation program 5 generates system definition information and commands 31 based on the definition information and command structures stored in the instance table 14.
Therefore, various system definition information and commands can be created by adding parameter description rules in the metadata table 13 and the candidate value table 15 without changing the hierarchy display GUI 3.

Storing the table in the database has the following effects. One is high reliability. In other words, it is difficult to repair a broken file if it is stored in a local file. Another is that the search is easy. There is no need to create a new search function because the existing index function can be used.

Hereinafter, the construction of the definition information 31 will be described as an example. In the present embodiment, the definition sentence is constructed by the hierarchical display GUI3. Therefore, the hierarchical expression of the definition sentence will be described. Every definition statement consists of a statement name, statement identifier, parameter name, and parameter value. The statement name indicates what definition statement, and the statement identifier identifies which definition statement when there are multiple same definition statements.
The parameter name indicates what the following parameter value is for.

FIG. 2 shows the structure of the definition sentence. For one definition statement, the statement name and statement identifier are 1.
There are a plurality of parameter names and parameter values, such as parameter names A and C and parameter values B, D and E. Also, as in parameter values D and E for parameter name C, 1
There are also multiple parameter values for one parameter name.

Based on these, one definition statement is expressed in a hierarchy as shown in FIG. The top level is the statement name and statement identifier representing the definition statement. The parameter names and parameter values that make up the definition statement are displayed below. As in the case of the parameter name A and the parameter value B, one layer is usually composed of one name and one value. When one parameter name has a plurality of parameter values, such as the parameter name C and the parameter values D and E, it can be expressed by making the layer deep and creating a layer with only parameter names and a layer with only parameter values. In the case of a command, a statement name can be used as a command name and a statement identifier can be used as a command identifier. Therefore, all definition statements and commands can be expressed hierarchically.

FIG. 4 shows the relationship between the hierarchical display GUI 3 and the definition sentence. This is a schematic conceptual diagram. For example, “AC” is displayed below the folder DB definition 111 of the hierarchical display GUI 3.
When the “TIVITY DEFINE” statement icon 112 is placed, the definition information 31 includes “ACTIVI DEFINE”.
A “TYPE DEFINE” statement 115 will be generated.
Similarly, when the “ENTRY DICTIONARY” statement icon 113 is arranged, “ENTRY D
The "ICTIONARY" sentence 116 becomes "DEFINER".
When the “DAREA” statement icon 114 is placed, a “DEFINE RDAREA” statement 117 is generated in the definition information 31. Therefore, the user can freely place the statement icon corresponding to the definition statement on the hierarchical display GUI 1 to obtain the definition information. 31. These are performed under the operation of the text generation program 5.

FIG. 5 shows the details of the hierarchical display GUI 3. This corresponds to a detailed GUI of FIG. The hierarchical display GUI 3 includes a root icon 121, a folder icon 122, a statement icon 123, and a parameter icon 124. The root icon 121 is only an icon indicating the top of the hierarchy, and cannot be added or deleted.
The folder icon 122 is an icon for organizing a large number of statement icons 123, and can be freely added or deleted.

The root icon 121 and the folder icon 122 are not generated in the definition information 31. The statement icon 123 is an icon representing the statement name and statement identifier of the definition statement, and can be added or deleted according to the definition statement rules of the metadata table 13. The parameter icon 124 is an icon indicating the parameter name and the parameter value of the definition sentence. When the statement icon 123 is added, the parameter icon 124 belonging to the statement icon 123 is automatically added.

Here, each icon is a picture 125 and a name 12
6, consisting of the value 127. The picture 125 is a picture imagining the type of the icon. The name 126 indicates a statement name or a parameter name. The value 127 indicates a statement identifier or a parameter value. When the icon is right-clicked with the mouse, the operation content for the icon is displayed as a menu 128. The menu 128 includes addition, deletion, and editing, but the menu content differs depending on the icon. Which menu is displayed follows the rules shown in the metadata table 13.

The information held by the metadata table 13 is shown in FIG.
As shown, type ID 611, parent ID 612, name 6
13, a prefix 614, a repeatable 615, a required 616, and an editable 617. The prefix indicates a fixed part at the beginning of the statement identifier. One row of the metadata table 13 corresponds to one statement or parameter rule. The type ID 611 is an ID representing a statement or parameter in the metadata table 13, and differs for each statement or parameter.
The parent ID 612 has a higher-level statement or parameter type ID 611 on the hierarchy, and indicates the hierarchical relationship of the hierarchy. The statement or parameter to be added is the parent ID 61
2 can be added only below the statement or parameter of the type ID 611 corresponding to 2.

For example, the name 61 whose type ID 611 is 2
3 "ACTIVITY SYSTEM OPTION"
Is the name 613 “ACTIVITY DEFINE% 1” whose parent ID 612 is 1 and whose type ID 611 is 1.
Can only be added to Also, the parent ID 612 is changed to the type ID 6
By searching at 11, it is possible to find what can be added below. For example, the name 613 "ACTIVI
Type ID 611 of "TY SYSTEMOPTION"
Is 2, so by searching for the parent ID 612 with 2,
Name 613 “RECOVERY TASK% 1”, “
JOURNAL READ BUFFER% 1 ","
CPDUMP GET EXCLUSIVE%
1 ", UAPRBACK EXCLUSIVE%
It can be seen that “1” can be added at a lower level. The name 613 is the name of the statement or parameter.
Is used in the hierarchical display GUI 1 and the definition information 31 to be generated. “% 1” in the name 613 indicates that the corresponding statement or parameter has a value. Also, the name 613
Is only "% 1", it means that there is no value. When the value of the statement or parameter is a variable character string, the prefix 614 specifies the prefix part of the character string. For example, if the prefix 614 is "ACTDEF"
, The values to be added are “ACTDEF001”, “AC
It changes automatically like TDEF002 "," ACTDEF003 ".

A repeatable 615 indicates that a plurality of statements and parameters can be added. For example, type ID
611 is the name of 7 613 "ACTIVITY SET
% 1 "is parent ID 6 because repeatable 615 is TRUE
Name "ACTIVITY DEFINE% 12"
A plurality of IDs can be added below “1”.
1 is the name of 2 613 "ACTIVITY SYSTEM
The name “ACTIVITY DE” indicated by the parent ID 612 is “OPTION” because the repeatable 615 is FALSE.
Only one can be added to the bottom of FINE% 1 ".

The mandatory 616 indicates that at least one corresponding statement or parameter is required. That is, 1
Required statements and parameters that exist only 61
If 6 is TRUE, the corresponding statement or parameter cannot be deleted. For example, the name 613 “ACTIVITY SET% 1” whose type ID 611 is 7 is required 61
Since 6 is TRUE, the name “ACT” indicated by the parent ID 612
If there is only one at the bottom of "IVITY DEFINE% 1", it cannot be deleted. Also, type ID 611
Is the name of 613 "ACTIVITY SYSTEM
OPTION is required because 616 is FALSE, so parent I
The name “ACTIVITYDEFINE” indicated by D612
% 1 "can be deleted even if there is only one below. The editable 617 indicates that the value is a variable character string or a number and can be edited. For example, the type 611 has a name of 613" ACTIVITY DEFINE% 1 ". Since the editable 617 of TRUE is TRUE, the value can be edited, and the type ID 611 is the name of 5 613 "CPDUMP.
GET EXCLUSIVE% 1 "editable 61
7 cannot be edited because it is FALSE. Name 613
Has "% 1" (with value) and editable 617 is FALS
Statements and parameters with E (not editable) have a value of "
The fixed values such as "YES" and "NO" indicate that the value can be selected but cannot be edited, and the fixed value for such selection is held in the candidate value table 15.

FIG. 7 shows the candidate value table 17. The type ID 811 is the type ID 61 of the metadata table 13
This is the same ID as 1. The candidate value 812 is “YES”, “
This parameter is specified when only a fixed value such as "NO" can be specified or when a default parameter value is required. When there are a plurality of the same type IDs 811, a plurality of candidate values are selected as value selection candidates in the menu of the hierarchical display GUI 1. 812 is displayed.

When there are a plurality of the same type IDs 811, the default value is the leading candidate value 812. For example, the type ID 611 in FIG.
Icon corresponding to TJF% 1 "is displayed in a hierarchical display GUI1
When right-clicking on, the selection candidate value displayed on the menu is a candidate value 812 ″ whose type ID 811 is 8 in FIG.
USE "," NOUSE "," NOUSE JNLPU
T MSG YES "," NOUSE JNLPUT
MSG NO ”. Type ID 811
Is "USE", which is a higher rank among the eight candidate values 812, as a default value.

With the candidate value table 8, the user does not need to check what parameter value is specified (corresponding) to the parameter name. Also, since it can have a default value, it is not necessary to specify a parameter value for each. Not all candidate values are necessarily covered in the candidate value table. In this case, it is necessary to input directly. The candidate value table serves to assist in the entry of values.

According to the rules of the metadata table 13 and the candidate value table 15, the hierarchical display GUI 3 controls the construction of the definition information. Therefore, when constructing new definition information or changing the rule of the definition information, it is only necessary to change the metadata table 13 and the candidate value table 15 without changing the hierarchical display GUI 3.

The definition information constructed by the hierarchical display GUI 3 is stored in the instance table 14 shown in FIG. One row of the instance table 14 corresponds to one icon in the hierarchical display GUI. The instance table 14 has paths and values in the form of icons rewritten in text. That is, the instance table 14 includes a type ID 711, a path 712, and a value 713.

The path is necessary to specify which row of the icon specified by the GUI in the instance table. Multiple rows can be created in the instance table for one row in the meta table. The row of the instance table can be added or deleted by adding or deleting the icon. By looking at the path of the instance table, it is determined whether or not to create the corresponding line in text. Thus, GU
The operability of creating system parameters using I is good.

The type ID 711 is the metadata table 1
This is the same ID as the type ID 611 of No. 3. A path 712 indicates a hierarchical position of a statement or parameter. In this format, the value 713 specified in each layer is separated by “/”. The path 712 becomes larger as the hierarchy becomes deeper. Value 713
Is the value specified for the statement or parameter. By referring to the instance table 14, which statement or parameter is specified at which position in the hierarchy,
You can see what value it has.

Layer display GUI 3 and metadata table 1
FIG. 9 shows the relationship between 3 and the instance table 14. When the hierarchy display GUI 3 arranges the icons, it refers to the stored instance table 14. The hierarchical position for arranging the icons is obtained by a path 712. The name 126 displayed on the icon is the type I of the instance table 14.
Name 61 of metadata table 13 corresponding to D711
Find from 3. The value 127 to be displayed is obtained from the value 713 of the instance table.

Next, the relationship among the text generation program 5, the metadata table 13, and the instance table 14 is shown in FIG. The text generation program 5 has the definition information 31
Is generated, the instance table 14 is referred to.
The position for arranging the definition sentence is obtained by the path 712. The statement name and parameter name of the definition statement are obtained from the name 613 of the metadata table 13 corresponding to the type ID 711 of the instance table 14. The statement identifier and the parameter value are obtained from the value 713 of the instance table. Conversely, when the definition information 31 is read and the instance table 14 is created, the instance table 14 is created by analyzing the definition information 31 with the name 613 of the metadata table 13.

The hierarchical display GUI 1 is added by the user.
The deleted information is stored in the instance table 14. The next time the hierarchy display GUI 1 is started, the icons are arranged and the hierarchy is restored according to the information held in the instance table 14. The text generation program 5 defines the definition information 31 according to the information held by the instance table 14.
Generate Therefore, when the metadata table 13 or the candidate value table 15 is changed for adding or changing the definition information rule, the definition information (instance table 14) constructed before can be used without being changed.

If there is a request to increase the number of definition statements or to create a definition statement for a completely different computer system, the columns of the metadata table 13 and the instance table 14 are increased, and new data Can be realized by creating That is, a definition sentence of a system parameter can be created only by adding a parameter according to the same description rule.

Next, FIG. 11 shows the flow of the hierarchy display GUI and the instance table when a definition statement is added. Hierarchical display GU
Right-click the mouse on the folder icon 141 to which the definition sentence is to be added in I3. The hierarchy display GUI 1 displays a menu 142 corresponding to the folder icon. The menu 142 displays “Add statement”, “Add folder”, “Delete”, and “Edit”. The user selects "Add statement" from the menu. Hierarchical display G
The UI 11 displays a statement addition dialog 143. Since the type ID 611 of the folder is 0, a name 613 whose parent ID 612 is 0 is searched from the metadata table 6 and displayed as a statement list in the statement addition dialog 143.

The user selects "ACTIVITY" from the statement list in the statement addition dialog box 143.
Selecting “DEFINE” closes the statement addition dialog 143. “A” is displayed in the hierarchy display GUI1.
Also, a statement icon 144 of “CTIVITY DEFINE” is added. In addition, the name 613 “ACTIVITY” is specified by the parent ID 612 of the metadata table 6.
DEFINE "is added as a parameter icon. At this time, information corresponding to the added icon is also added to the instance table 14. From the state of the instance table 721 before the change to the state of the instance table 722 after the change. The above is the flow when one definition sentence is added. By repeating this on the hierarchical display GUI 3, the instance table 14 having the parameter information of the target system definition is created.

When the user requests text generation, the text generation program 5 changes the “ACTIVITY DEFINE” statement 311 based on the “ACTIVITY DEFINE” information 723 of the changed instance table to the “ACTI DEFINE” statement of the changed instance table.
Parameter 3 of “ACTIVITY DEFINE” based on information 724 lower than “VITY DEFINE”
12 is generated. Thereby, the parameter information 31 of the target system definition is completed.

FIG. 12 shows a flow of a method of changing a value using the candidate value table 15. The user right-clicks the parameter icon “ACT JF” 151 with the mouse in the hierarchical display GUI 3. From the name 613 of the metadata table 13, the hierarchical display GUI 3 is a type I “ACT JF”.
D611 is obtained. Type ID 61 of "ACT JF"
Since 1 is 8, the type ID 81 is obtained from the candidate value table 15.
A candidate value 812 where 1 is 8 is obtained. “ACT JF” candidate values 812 “USE”, “NOUSE”, “NOUSE”
JNLPUT MSG YES "," NOUSE J
"NLPUT MSG NO" is displayed in the menu 152. From the displayed menu 152, the user can select "NOUS
When "E" is selected, the parameter icon "ACT JF"
The value of 153 changes to "NOUSE".

At this time, “A” in the instance table 7
CT JF value from “USE” 731 to “NOUS
E "732. With this, the user can change only by selecting without inputting a value to be specified in the parameter.

FIGS. 13 to 19 show the flow of the definition information creation processing in PAD (Problem Analyzed Des).
(ign) diagram. First, FIG. 13 will be described. The system is started, and the process enters a definition information creation start 901. When the user right-clicks on the icon 125 in the hierarchical display GUI 3, the process is triggered (902).

Information of the metadata table 13 corresponding to the icon 125 right-clicked is obtained (904).
The menu 128 to be displayed is changed according to the information in the metadata table 13. If the type ID 611 is 0 (905), the menu “Add statement” (906) and “Add folder” (90
7) is added to the menu 128. If repeatable 615 is TRUE (908), "Add Copy" is added to menu 128 (909).

If the editable 617 is TRUE (91
0), “edit” is added to the menu 128 (91)
1). If the essential 616 is FALSE (912), “delete” is added to the menu 128 (913). The created menu 128 is displayed on the hierarchical display GUI 1 (91
4). The user selects a menu to be executed from the displayed menu 128. Each process is called according to the menu selected by the user (915).

Next, the processing when the statement addition processing is selected will be described with reference to FIG. When "Add statement" is selected (916), the statement addition process 921 is called to add a statement icon and a parameter icon belonging to the relevant statement. In the statement addition process 921, the loop is performed for the number of rows of the metadata table 6 (922), and a row having a parent ID 612 of 0 is searched (923). If the parent ID 612 is 0, there is only a statement, so the name 613 is added to the statement list list (924). The statement list is displayed on the dialog 143 to allow the user to select (925). A row of the metadata table 6 corresponding to the statement selected by the user is obtained (926). Repeatable 615 is FALSE and path 7 of instance table 14 corresponding to the right-clicked folder icon
12 has the same type ID 711 (92
7) Since an error cannot be added, an error is displayed (928).

If the condition of 927 is not met, it can be added, so the name 613 of the metadata table 13 is set to the icon name 126 (929), and the metadata table 13
A unique number is added to the prefix 614 to make the icon value 127 (930), and a statement icon is added below the right-clicked icon of the hierarchical display GUI 1 (931). The path 712 and the value 713 corresponding to the added icon are added to the instance table 14 (932).

Next, the parameter addition processing will be described with reference to FIG. First, call 935 (FIGS. 14 and 9).
33), a parameter icon is created below the statement icon. In the parameter addition processing 935, the type ID of the statement added as the initial setting of the loop
611 is set to the work type ID (936). Looping occurs while the addition of the parameter occurs (937). Loop for the number of rows in the metadata table 13 (938), and
It is checked whether D612 matches the type ID of the work (939). If they match, the metadata table 13
Since the line corresponding to the loop is information below the work type ID, an additional process is performed.

The icon name 126 sets the name 613 of the metadata table 13 (940). The value 127 of the icon is (94
1), a unique number is added to the prefix 614 to obtain a value (942). If there is no prefix 614, the process loops over the number of rows in the candidate value table 15 (946),
A candidate value 812 in which the type ID 611 of the metadata table 13 matches (947) the type ID 811 of the candidate value table 15 is set as a value (948). A parameter icon is added to the hierarchical display GUI 1 with the obtained name 126 and value 127 (943). The path 712 and the value 713 of the added icon are added to the instance table 14 (94
4), (945).

After looping with the current work type ID for the number of rows of the metadata table 6 (938), the type ID 611 corresponding to the added parameter is set to the work type ID (949), and the processing from 938 to 945 is performed again. Execute. By executing this until all the parameters have been added (937), all the parameters located below the added statement can be added.
If there is no more parameter addition, the process returns to 903.

Next, the case where the user selects "add folder" at 915 will be described with reference to FIG. A folder addition process 951 is called, and a folder icon is added below the right-clicked icon. In the folder addition process 951, the name is obtained from the name 613 of the metadata table 6 (952) (Folder). The value adds a unique number to the prefix 613 of the metadata table 13 (953) (FOLDERn).

The name (Folder) 126 and the value (F) obtained below the right-clicked icon of the hierarchical display GUI 1 are displayed.
OLDern) 127 to add a folder icon (954). The path 712 and the value 713 corresponding to the added folder icon are added to the instance table 14 (955), and the process returns to 903 (956). Thus, the folder icon is added to the hierarchy display GUI 3 and the instance table 14.

Next, the case where the user selects "copy addition" in step 915 will be described with reference to FIG. Copy addition processing 957
And add a new icon with the same definition information as the right-clicked icon. Copy addition processing 957
Then, the name 612 corresponding to the right-clicked icon is obtained from the metadata table 13 (958). A unique number is added to the prefix 614 of the metadata table 13 to obtain a value (959).

An icon with the determined name 126 and value 127 is added to the same position as the right-clicked icon in the hierarchical display GUI 1 (960). The path 712 and the value 713 corresponding to the added icon are added to the instance table (961). Looping is performed for the number of icons below the right-clicked icon (962).

Referring to the path 712 of the instance table 14, the type ID 711 and the value 713 of the icon lower than the right-clicked icon are obtained (963). An icon is added to the hierarchical display GUI 1 with the obtained name 126 and value 127 (964). The path 712 and the value 713 corresponding to the added icon are added to the instance table 14 (965). After the steps 963 to 965 are repeated for the number of lower icons of the right-clicked icon, the process returns to 903 (966).

As a result, the right-clicked icon and all of its lower icons can be copied and added as new definition information.

Next, the case where the user selects "edit" at 915 will be described with reference to FIG. The edit processing 967 is called to directly edit the value. In the editing process 967,
A value 713 corresponding to the right-clicked icon is obtained from the instance table 14 (968).

The obtained value 713 is set and displayed in the editing dialog box where the user can directly change the value (96).
9). The value 713 of the instance table 14 and the value 127 of the hierarchy display GUI 3 are changed with the value specified by the user in the editing dialog (970), and the process returns to 903 (971). As a result, the user can directly edit an arbitrary value.

Next, the case where the user selects “delete” at 915 will be described with reference to FIG. Call delete processing 972 to delete the right-clicked icon and all lower-level icons. In the deletion process 972, a path 712 corresponding to the icon right-clicked is obtained from the instance table 7 (973). The process loops while an icon exists below the right-clicked icon (974). The line corresponding to the lower-level icon of the right-clicked icon is obtained from the instance table 14 (975). The corresponding icon is deleted from the hierarchy display GUI 3 (976). Delete the relevant line from the instance table 14 (97
7).

The steps 975 to 977 are repeated, and if there is no longer the right-clicked icon and its lower icons, the process returns to 903 (978). This deletes the right-clicked icon and all lower-level icons.

After executing the processing corresponding to each menu selected by the user at 915, the process proceeds to 903. At 903, it is determined whether the user has closed the screen of the hierarchical display GUI1. If the hierarchy display GUI 1 is not closed, the process proceeds to step 902 to continue the definition information creation. If the hierarchy display GUI 1 is closed, the process proceeds to 9031 to end the definition information creation.

From the embodiments of the invention described above, the present embodiment has the following effects. Since the database has rules for describing system parameters and menus to be displayed on the GUI, the program and GUI for creating system parameters are not specialized to only one system. Even if the system is upgraded, programs and G
There is an effect that only the data in the database needs to be changed without recreating the UI.

Further, since the parameter configuration is created on one GUI for hierarchical display, there is an effect that a unified user interface can be provided even if different system parameters are created. Furthermore, by storing the information of the created system parameters in the database and being able to use the parameters saved in the database again, the created system parameter information can be applied to the upgraded system, and other parameters with similar parameter description format can be used. This has the effect of facilitating reuse in the system.

[0067]

According to the present invention as described above, various system parameters can be constructed without changing the GUI.

[Brief description of the drawings]

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

FIG. 2 is a configuration example of a system definition sentence.

FIG. 3 is a diagram expressing a system definition sentence in a hierarchy.

FIG. 4 is a diagram showing a relationship between a hierarchical display GUI and a system definition sentence.

FIG. 5 is a display example of a hierarchical display GUI.

FIG. 6 is an example of a metadata table.

FIG. 7 is an example of a candidate value table.

FIG. 8 is an example of an instance table.

FIG. 9 shows a metadata table, an instance table,
It is a figure showing relation of hierarchy display GUI.

FIG. 10 is a diagram illustrating a relationship among a metadata table, an instance table, and text generation.

FIG. 11 is a diagram showing a flow at the time of adding a definition sentence.

FIG. 12 is a diagram showing a flow of a value change based on a candidate value table.

FIG. 13 shows a flow of processing of the present invention as a PAD (Probe
(AnalyzedDesign).

FIG. 14 is a process flowchart of a statement addition process.

FIG. 15 is a processing flowchart of parameter addition processing.

FIG. 16 is a processing flowchart of folder addition processing.

FIG. 17 is a processing flowchart of copy addition processing.

FIG. 18 is a processing flowchart of an editing process.

FIG. 19 is a processing flowchart of a deletion process.

[Explanation of symbols]

1: Client PC, 2: System configuration management program, 3: Hierarchical display GUI, 4: Repository API, 5:
Text generation program, 11: server, 12: repository DB, 13: metadata table, 14: instance table, 15: candidate value table, 31: definition information and command file, 611 to 617: components of metadata table, 711 to 713: components of the instance table, 811, 812: components of the candidate value table

 ──────────────────────────────────────────────────の Continuation of the front page (54) [Title of Invention] System parameter creation method, system parameter creation device, computer readable recording medium recording system parameter creation program, and computer reading storing system parameter creation data Possible recording media

Claims (10)

[Claims] A system parameter creation device for generating a system parameter of a computer using a GUI, wherein a common GUI is used irrespective of system differences.
And a system parameter creation unit that is standardized irrespective of the difference between systems, and a table format description rule for system parameters stored in a database. 2. The system according to claim 1, wherein the GUI is a hierarchy of statement or command definition statements, and the description rules of the system parameters are a hierarchical structure, the presence or absence of a name and a value for each hierarchical structure, and a rule for each name. A system parameter creation device having a description attribute. 3. A metadata table indicating what parameter a statement or command is composed of and what value it takes, a candidate value table showing candidates of possible parameter values, definition information and command A method of creating a system parameter of a system parameter creating device having an instance table for storing a structure of a statement, wherein a GUI in which the structure of a statement or a definition statement of a command is hierarchized is formed; Registering a value selected from the created menu in the instance table, and creating a definition statement of a system parameter by combining the value of the instance table and the name of the metadata table based on each row of the instance table. How to create the characteristic system parameters. 4. A metadata table that indicates what parameters a statement or command is composed of and what values are taken, and has one column for each type ID, and possible parameter values that can be taken. A method of creating a system parameter of a system parameter creation device comprising a candidate value table indicating the type of a parameter and an instance table storing definition information and a command structure and having one column for each type ID. Forming a GUI in which a sentence structure is hierarchized, registering a value selected from a menu created from the candidate value table on the GUI in the instance table, and the metadata corresponding to a type ID of the instance table Combine the table name and the value of the instance table with the system parameters. The method of creating system parameters, characterized in that to create a definition statement. 5. A metadata table indicating what parameter a statement or command is composed of and what value it takes, a candidate value table showing possible parameter value candidates, definition information and command An instance table for storing the structure of a statement or a command, and means for forming a GUI in which the structure of the definition statement of a statement or a command is hierarchized, and a value selected from a menu created from the candidate value table on the GUI. And a means for creating a system parameter definition statement by combining the value of the instance table and the name of the metadata table based on each row of the instance table. Creating device. 6. The system parameter creating apparatus according to claim 5, wherein said metadata table, said candidate value table, and said instance table are stored in a database. 7. A metadata table that indicates what parameters a statement or command is composed of and what values are taken, and has one column for each type ID, and possible parameter values. Table that stores the structure of the candidate information and the definition information and the command, and has one column for each type ID, and the GUI in which the structure of the statement and the definition statement of the command is hierarchized
Means for registering a value selected from a menu created from the candidate value table on the GUI in the instance table; and a name of the metadata table corresponding to a type ID of the instance table. Means for creating a definition sentence of a system parameter in combination with the value of the instance table. 8. A metadata table indicating what parameter a statement or command is composed of and what value it takes, a candidate value table showing possible parameter value candidates, and a definition information or command A GUI display method of a system parameter creation device having an instance table for storing a structure, wherein a structure of a statement or a command definition statement is hierarchized, a name is displayed based on the metadata table, and a value is defined by the auxiliary table. A GUI for displaying a selection menu and displaying a value according to a selection value selected by the menu and registered in the instance table.
Display method. 9. A metadata table indicating what parameter a statement or command is composed of and what value it takes, a candidate value table showing possible parameter value candidates, definition information and A recording medium recording a program in a system parameter creation device having an instance table for storing a command structure, wherein a GUI in which a structure of a statement or a command definition statement is hierarchized is formed, and the candidate value is displayed on the GUI. Register the value selected from the menu created from the table in the instance table, and create a system parameter definition statement by combining the value of the instance table and the name of the metadata table based on each row of the instance table Program for creating system parameters A computer-readable recording medium. 10. A computer-readable recording medium recording data for generating a system parameter of a computer system, comprising: an instance table having a system definition statement and a value in which one type ID is assigned to one column; A metadata table in which a statement and a parameter name, and an identifier indicating whether or not a value is given to the statement and the parameter, have one type ID assigned to one column; Data for creating a system parameter, wherein a correspondence is established between the type ID of the metadata table based on the type ID of the instance table so that the statement, the name of the parameter, and the value of the instance table are combined. Recorded computer read A recording medium that can be.