JPH09160759A - Management method of computer system operation definition information table - Google Patents

Abstract

(57) Abstract: A computer system having an operation definition information table on a memory of a main body device and capable of connecting a maintenance terminal, and making it possible to safely change the contents of the table on the main body device, It is an object to shorten the operation stop time of the main body device and improve the development efficiency of the table changing function. A table changing unit 10 in a maintenance terminal 112.
Reference numeral 5 executes a change operation for the table file in the table file unit 101. The table content indicated by the changed table file is transferred to the main body device 113 by the table transmission unit 102. The table management unit 108 in the main body device 113 writes the table contents transferred from the maintenance terminal 112 in the table area 111. In this way, by managing the table contents as a table file on the maintenance terminal 112, it becomes possible to perform a table changing operation or the like in a place (office or the like) where there is no main body device.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a computer system having an operation definition information table in a memory of a main unit and capable of connecting a maintenance terminal.

[0002]

2. Description of the Related Art Recent computer systems, particularly online real-time systems used as social systems, require continuous operation for a long time. I cannot use the equipment I have. Therefore, the operation definition information of the device needs to be stored as a table on a storage medium having no driving unit such as a memory.

In this case, how to safely update the table of operation definition information becomes a problem. FIG. 23 is an explanatory diagram of a conventional technique.

A table area 230 on the main unit 2308
To change the table contents of No. 6, the operator
The main body device 2308 and the maintenance terminal 2307 are connected, and the table changing unit 2301 on the maintenance terminal 2307 is activated.
The table contents changed by the table changing function of the table changing unit 2301 are immediately transferred to the main body device 2308 via the communication unit 2302 with the main body.

In the main unit 2308, the table contents received via the communication unit 2303 with the maintenance terminal are stored in the table area 2306 via the memory storage unit 2304.

The table conversion unit 2301 in the maintenance terminal 2307 also has a function of displaying the current table, which is the memory acquisition unit 230 in the main unit 2308.
5 is realized by acquiring the table contents in the table area 2306 and transmitting it to the maintenance terminal 2307.

However, in the above-mentioned conventional technique, the maintenance terminal 2
If the 307 is not directly connected to the main body apparatus 2308, the table contents cannot be changed, the operator cannot prepare the table contents in advance, and there is a problem that the safety of the table changing work is hindered. . Many of the table data stored in the table area 2306 are highly important and highly confidential, and the work in a single time is required as much as possible, so remote maintenance is difficult.

Further, in the above-mentioned conventional technique, the maintenance terminal 23
The function of the table conversion unit 2301 in 07 was realized as a program logic. On the other hand, the screen image and the table structure of the table changing function may be frequently modified based on the customer's request and the like, so that there is a problem that the development efficiency and modification efficiency of the function of the table modifying unit 2301 are poor. Had.

Further, the function of the table conversion unit 2301 mounted on the maintenance terminal 2307 needs to be created in association with the locate address of the table data stored in the table area 2306 in the main unit 2308. Therefore, conventionally, the programmer had to develop the function of the table conversion unit 2301 while referring to the source program and the locate map file corresponding to the main body device 2308. For this reason, the development efficiency of the above functions is poor, and bugs frequently occur due to the difference in recognition between the above functions and the table structure of the main body device.

Further, conventionally, the function of displaying the table contents and the device status in the table area 2306 of the main body device 2308 also had to be created as a new program logic, so the development efficiency was poor.

Furthermore, conventionally, the operator himself has to manage the information indicating how the table stored in the table area 2306 of the main body apparatus 2308 has been changed, and management errors frequently occur. .

Further, conventionally, in order to change the table contents in the table area 2306 of the main body apparatus 2308, as shown in FIG. 24, the state of the main body apparatus 2308 is changed from the apparatus operation state to the apparatus operation stop state. It was necessary to change the contents of the table above and then return the state of the main body device 113 from the device operation stop state to the device operation state again. For this reason, the maintenance mode must be implemented in the main body device 113, and when the table change takes a long time, the operation of the main body device 2308 also stops for a long time, resulting in a decrease in the device operating rate. Had the problem.

Apart from the above-mentioned conventional technique, a conventional table arrangement technique in a tightly coupled multiprocessor system having a shared memory will be described with reference to FIG. In a multiprocessor system, it is desirable to connect the maintenance terminal 2505 to only one processor (system management CPU 2506) in order to simplify the cost and the operation.

In the prior art, another processor (individual function C
The tables necessary for the PU 2507) are arranged in the table area 2504 on the shared memory 2508.
In an online real-time system or the like, many applications 2503 must frequently refer to the table contents during operation. However, in general, access to the shared memory 2508 occupies more processor execution time than access to the local memory in each processor, resulting in a heavy load on each processor, resulting in an increase in the number of processors. , Was inviting an increase in the cost of the entire system.

Further, since the access load to the shared memory 2508 also increases, there is a problem that the access to the shared memory 2508 from other processors is hindered and the response of the system is deteriorated.

An object of the present invention is to enable the contents of a table on the main body device to be safely changed, shorten the operation stop time of the main body device, and improve the development efficiency of the table change function. .

[0017]

According to a first aspect of the present invention, there is provided:
It is premised on a computer system having an operation definition information table on the memory of the main body and capable of connecting a maintenance terminal.

Then, in the maintenance terminal, a table file management means for managing the operation definition information table for the main body device as a table file and the table contents indicated by the table file managed by the table file management means are stored in the main body device. Table transmission means for transmitting.

Further, the main body device has a table updating means for receiving the table contents from the table transmitting means in the maintenance terminal and replacing the table contents held by the main body device with the table contents.

In the first aspect of the present invention having the above configuration, the table contents are managed as the table file on the maintenance terminal, so that the table changing work etc. in the place (the office etc.) where there is no main unit can be performed. This enables the operator to prepare the table contents in advance, which improves the safety of changing the table.

In the configuration of the first aspect of the present invention described above, the main body device further includes table transmitting means for transmitting the table contents held by the main body device to the maintenance terminal, and manages the table file in the maintenance terminal. The means can be configured to include table receiving means for receiving the table contents transmitted by the table transmitting means as a table file. Further, the table file management means is configured to include a table comparison means for comparing the contents of the table file held by the table file management means with the contents of the table file received by the table reception means in the table file means. be able to. Also, the table file management means can be configured to include table changing means for changing the contents of the table file.

Further, the table changing means changes the contents of the table file based on the contents of the screen definition file which defines the display format of the screen and the contents of the attribute definition file which defines the structure of the operation definition information table. Can be configured to.

With the configuration having such a definition file, the system developer can easily provide the table changing function by only creating the definition file of the screen image and the table structure, and the development efficiency is improved. .

Next, in the above configuration in which the table changing means has the screen definition file and the attribute definition file,
A definition file generating means for generating a screen definition file and an attribute definition file based on table source information for generating the operation definition information table and locate map information for storing the operation definition information table in the main body device is further provided. Can be configured to.

With the configuration having such a definition file generating means, the system developer can provide the table changing function with almost no work, and the development efficiency can be improved. Further, since the occurrence of a bug due to the difference in recognition of the table structure between the table structure of the main body device and the function of the table changing unit of the maintenance terminal is eliminated, the reliability of the function of the table changing unit can be improved.

Next, in the constitution of the present invention so far,
The main body device further includes table transmitting means for transmitting the table contents or the device state held by the main body device to the maintenance terminal, and the table file management means in the maintenance terminal is
The table changing means in the table file managing means has a function of opening the table file in the read-only mode, including table receiving means for receiving the table contents or the device status transmitted by the table transmitting means as a table file. The table receiving means in the file managing means and the table changing means operating in the read-only mode cooperate to display the table contents or the apparatus status of the main body apparatus.

By simply operating the table receiving means and the table changing means having the read-only mode in cooperation with each other, the display function of the table contents and the apparatus state of the main body apparatus can be easily realized.

Then, in the configuration of the present invention so far, the table update history holding means for holding the update history of the operation definition information table updated by the table updating means and the table update history holding means are provided in the main body apparatus. The maintenance terminal receives the update history of the operation definition information table transmitted by the table update history transmitting means in the main body device, and the table update history transmitting means for transmitting the update history of the retained operation definition information table to the maintenance terminal. It can be configured to include a table update history display means for displaying the table.

With such a structure capable of managing the update history, it is possible to improve the safety of the table version number management. Next, in the configuration of the present invention up to this point, the table updating means in the main body device includes the table content holding means for receiving the table contents from the maintenance terminal and holding the table contents, and the table content holding means for resetting the main body device. It is possible to include a table conversion unit that converts the held table contents and replaces the table contents held by the main body device with the converted table contents.

With the configuration including such table conversion means, it is not necessary to stop the operation of the main body device when the changed table contents are transferred from the maintenance terminal to the main body device, and the main body device is reset after the transfer is completed. Since it is possible to update the table contents of the main body device by itself, it is not necessary to mount a maintenance mode or other maintenance mode on the main body device, and it is possible to prevent a decrease in the operating rate of the main body device.

Next, the second aspect of the present invention is premised on a multiprocessor system to which a maintenance terminal can be connected, which operates based on the contents of the operation definition information table, and which has a shared memory.

Then, in the maintenance terminal, a table file management means for managing the operation definition information table for the main unit as a table file and the table contents indicated by the table file managed by the table file management means are stored in the multiprocessor system. And a table transmitting means for transmitting the table to a predetermined processor.

Further, the predetermined processor includes a table transfer means for receiving the table contents from the table sending means in the maintenance terminal and transferring the table contents to each processor constituting the multiprocessor system.

Then, each of the processors includes a table updating means for receiving the table contents from the table transferring means in a predetermined processor and replacing the table contents held locally by the respective processors.

According to the configuration of the second aspect of the present invention described above,
Since the table contents are held locally in each processor, the execution time of the processor that accesses the table contents can be shortened. Further, it is possible to avoid concentration of access to the shared memory and improve the response of the entire system.

[0036]

Embodiments of the present invention will be described below in detail with reference to the drawings. First Embodiment FIG. 1 is a configuration diagram of a first embodiment of the present invention, and FIG. 2 is an operation flowchart thereof.

The first embodiment is characterized in that the contents of the table area 111 on the main device 113 side are retained as a table file in the table file section 101 on the maintenance terminal 112 side.

When the operator uses the maintenance terminal 112 to change the contents of the table area 111 of the main body device 113, first, the table receiving unit 1 of the maintenance terminal 112 is first in advance.
By activating 03, the table contents are transferred from the table area 111 in the main body device 113 to the maintenance terminal 112 (step 201 in FIG. 2). Specifically, the table management unit 108 in the main body device 113 causes the memory acquisition unit 1 to
By starting 10, the table contents of the table area 111 are read. The contents of this table are stored in the communication unit 107 for communicating with the maintenance terminal in the main body device 113 and the maintenance terminal 1.
It is transferred to the table receiving unit 103 via the communication unit 106 with the main body in 12. The table receiving unit 103 stores the table contents in the table file unit 101 as a table file.

Next, the operator operates the table comparison unit 10
4 is started, the new table file on the maintenance terminal 112 stored in the table file unit 101 is compared with the old table file transferred from the main body device 113 (step 202 in FIG. 2).

As a result, when the operator continues the table changing process, the operator changes the contents of the new table file stored in the table file unit 101 by activating the table changing unit 105 (see FIG. 2). Step 203). Then, the table comparison unit 104 is activated again to compare the changed new table file with the old table file (step 203 → 202 in FIG. 2). When continuing the table changing process, the operator activates the table changing unit 105 again.

The operator repeats the above table changing process, and when the table changing process is completed, the table transmitting unit 102 is activated and the contents of the new table file in the table file unit 101 are transferred to the main body device 113 (see FIG. 2 step 202 → 204). Specifically, the table transmission unit 102 reads the new table file in the table file unit 101, and reads it out from the maintenance terminal 112.
The data is transferred to the table management unit 108 in the main body device 113 via the communication unit 107 with the maintenance terminal in the main body device and the communication unit 106 with the main body in the main body device 113. Table management unit 108
Stores the content of the new table file in the table area 111 by activating the memory storage unit 109.

According to the above first embodiment, the table file can be changed only by the maintenance terminal 112, so that the operator can save the table file in advance in a place (office or the like) where the main body device 113 is not present. It becomes possible to prepare, and the safety of changing the table is improved. Second Embodiment FIG. 3 is a configuration diagram of a second embodiment of the present invention.

The second embodiment is a mode in which the table changing unit 105 in the first embodiment of FIG. 1 is realized. In the second embodiment, the table file unit 304
The screen image and table structure required to change the table for the internal table file are displayed in the screen definition file 302
By being converted into a file in the attribute definition file 303, it is separated from the main body of the table changing program 301. As a result, it becomes easy to develop and modify the table changing unit.

First, the screen definition file 302 is a file that defines the screen image necessary for changing the table. An example of the contents of this file is shown as 305 in FIG. In 305, the character string “$$$$” indicates an item (item in the table structure) to be input by the operator.

Next, the attribute definition file 303 is a file that defines the items of the table structure to be input by the operator. An example of the contents of this file is shown as 306 in FIG. In 306, “$ 1” and the like correspond to “$$$$” (see 305) in the screen definition file 302. That is, the first "$" in the screen definition file 302
“$$$” corresponds to “$ 1” in the attribute definition file 303, and the next “$$$$” in the screen definition file 302 corresponds to “$ 2” in the attribute definition file 303. In 306, for each input item, a memory address of the input item on the main unit, a conversion format (decimal / hexadecimal format, etc.), a display color on the screen, and a data format (1 byte /
2 bytes) is defined.

When the table changing program 301 is executed on the basis of these pieces of information, a table changing screen as shown at 307 in FIG. 3 is displayed on a display device (not shown) so that the table can be changed. . The inverted part on the screen is the input item by the operator.

4 and 5 are flowcharts showing the operation of the table changing program 301. When the execution of the table change is started, the contents of the screen definition file 302 (see 305 in FIG. 3) are first read into the screen area of the table change program 301 (step 401 in FIG. 4).

Next, the contents of the attribute definition file 303 (see 306 in FIG. 3) are the contents of the table change program 301.
Is read into the attribute area (step 402 in FIG. 4).
Next, from the table file section 304, the contents of the table file to be changed are
Data area (step 40 in FIG. 4).
3).

Subsequently, the contents of the table file read in the data area (see 307 of FIG. 3) are displayed according to the contents of the screen area and attribute area (step 404 of FIG. 4). FIG. 5 is an operation flowchart showing the details of step 404 in FIG.

First, of the data read from the screen area, characters other than "$" are displayed (step 501 in FIG. 5). Next, the attribute information is extracted from the attribute area element by element (step 502 in FIG. 5).

Then, the data corresponding to the address which is the attribute information is acquired from the data area (step 503 in FIG. 5). Further, the acquired data is displayed in the "$" portion of the screen area according to the attribute information of the attribute area (step 504 in FIG. 5).

The above-described processing of steps 502 to 504 of FIG. 5 is repeated until the last attribute information of the attribute area is extracted (step 505 → 502 of FIG. 5). As described above, after the table change screen is displayed in step 404 of FIG. 4, the processes of steps 405 to 410 of FIG. 4 are repeated, whereby the processes corresponding to the various keys operated by the operator are executed. .

That is, in the key input waiting state (step 405 in FIG. 4), when the operator presses the cursor key, the determination in step 406 becomes YES and the cursor moving process is executed (step in FIG. 4). 407).

When the operator inputs data in the key input waiting state (step 405 in FIG. 4), the determination in step 408 becomes YES, and the process of changing the contents of the data area is executed (FIG. 4). Step 40 of 4
9).

Waiting for key input (step 40 in FIG. 4)
In 5), when the operator presses the end key, the determination in step 410 becomes YES, the contents of the data area are written in the corresponding table file in the table file section 304 (step 411 in FIG. 4), and the table The change process ends.

According to the second embodiment described above, the system developer only needs to create the screen definition file 302 and the attribute definition file 303 necessary for changing the table, and the system developer can create the screen definition file 302 and the attribute definition file 303 in each main unit when changing the table. Since it is possible to display the corresponding table, it is possible to improve the development efficiency of the table changing program 301. Third Embodiment FIG. 6 is a configuration diagram of a third embodiment of the present invention.

In the third embodiment, when the function of the table changing unit in the second embodiment of FIG. 3 is realized, the screen definition file and the attribute definition file are stored in the table loaded in the main unit. It can be automatically generated from the corresponding load module file and its source program source file.

The configuration of FIG. 6 is realized on a development device that develops a table loaded in the main device. In FIG. 6, first, a table source file 602 is a source file that defines a table area of the main body device and is a part of a program of the main body device. An example of the contents of this file is shown as 604 in FIG. 6, in which the structure of the table area is described in a predetermined programming language.

Next, the locate map file 603 is
A table source file 6 is a file that is automatically generated by a generally known locator function when a table area program is located in the main unit.
The memory address of each element in 02 is included.

By executing the table change file automatic generation program 601 based on these information, the screen definition file 6 required for the table change is automatically generated.
05 and the attribute definition file 606 are generated. These correspond to the screen definition file 302 and the attribute definition file 303 of FIG. 3 in the second embodiment, respectively.

FIG. 7 is an operation flowchart of the table changing file automatic generation program 601 shown in FIG.
First, the contents of locate map file 603 are read into the locate map area in the program (step 701).

Next, while the contents of the table source file 602 are being read line by line into the work data area in the program (step 702), the end of the file is detected (the judgment in step 703 is YES). Up to), the processing of the following steps 704 to 709 is repeatedly executed.

That is, first, it is judged whether or not a symbol which is a table element exists in the current row (step 70).
4). If there is no symbol in the current line and the determination in step 704 is NO, steps 705 to 708 are not executed, and the content of the current line is simply written in the screen definition file 605 in step 709.

If there is a symbol (table element) in the current line and the determination in step 704 is YES, the following steps 705 to 709 are executed. That is, first, the character string "$" is added to the right side of the symbol in the current line on the work data area in accordance with the data type (see 604 of FIG. 6) (step 705).

Next, the symbol name (table element name)
Is retrieved from the locate map area and its address is obtained (step 706). Then, the data for one element of the attribute definition file 606 including the address and the data type is created corresponding to the symbol (table element) (step 707). Then, the created one element is written in the attribute definition file 606 (step 708).

Finally, the contents of the current line modified in step 705 are written in the screen definition file 605 (step 709). According to the above third embodiment,
Since the screen definition file and the attribute definition file can be automatically generated from the load module file corresponding to the table loaded in the main unit and the program source file that is the source of them, the system developer needs almost no work. It is possible to provide the function of the table changing unit without doing so and improve the development efficiency of the table changing program 301.

Further, since the occurrence of a bug due to the difference in recognition of the table structure between the table structure of the main unit and the function of the table changing unit of the maintenance terminal is eliminated, the reliability of the function of the table changing unit can be improved. it can. Fourth Embodiment FIG. 8 is a configuration diagram of the fourth embodiment of the present invention. This configuration is almost the same as that of the first embodiment of the present invention in FIG.

In the fourth embodiment, a read-only mode is provided in the table changing function realized by the table changing unit 105 in the first embodiment, and the operation of the table receiving unit 103 and the operation of the table changing unit 105 are performed. Are batch-processed and executed as a series of operations, the function of simply displaying the table of the main body device and the function of displaying the device state can be easily added.

When the above batch processing for displaying the table contents of the table area 111 in the main body device 113 is started, first, the table receiving unit 103 of the maintenance terminal 112.
Is activated, the table contents are transferred from the table area 111 in the main body device 113 to the maintenance terminal 112. Specifically, the table management unit 108 in the main body device 113 activates the memory acquisition unit 110 to read the table contents of the table area 111. The contents of this table are stored in the communication unit 106 with the main body in the main body device 113 and the communication unit 10 with the main body in the maintenance terminal 112.
6 to the table receiving unit 103. The table receiving unit 103 stores the table contents in the table file unit 101 as a temporary table file. Then, the table changing unit 105 is activated to display the table contents, which are the contents of the temporary table file in the table file unit 101, in the read-only mode.

On the other hand, the device status area 8 in the main device 113
When the above-mentioned batch process for displaying the contents of 01 is activated, first, the table receiving unit 103 of the maintenance terminal 112 is activated, so that the device status is transferred from the device status area 801 in the main body device 113 to the maintenance terminal 112. Is transferred.
Specifically, the table management unit 108 in the main body device 113
However, the device status in the device status area 801 is read by activating the memory acquisition unit 110. This device state is transferred to the table receiving unit 103 via the communication unit 106 with the main body in the main body device 113 and the communication unit 106 with the main body in the maintenance terminal 112. Table receiving unit 103
Stores the device status in the table file unit 101 as a temporary table file. Since the table contents and the device status are data arranged in the memory area, the device status can be stored as a temporary table file. Then, the table changing unit 10
5 is started, the table file unit 101
The device status, which is the contents of the above-mentioned temporary table file, is displayed in the read-only mode.

According to the above-described fourth embodiment, the main unit 11 can be provided only by adding the read-only mode to the function of the table changing unit 105 in the configuration of the first embodiment.
The table display function and the device status display function of 3 can be easily realized. Fifth Embodiment FIG. 9 is a block diagram of the fifth embodiment of the present invention. This configuration is based on the configuration of the first embodiment of the present invention in FIG.

The fifth embodiment is characterized in that the maintenance terminal 112 can manage the change history of the table contents in the table area 111 in the main body unit 113. First
When the content of the new table file in the table file unit 101 changed on the maintenance terminal 112 based on the method of the embodiment is transferred to the main body device 113 by the table transmission unit 102 in the maintenance terminal 112, the new The contents of the table file are first received by the table management unit 108 in the main body device 113.

The table management unit 108 stores the contents of the received new table file in the table change history management unit 902.
Hand over to The table change history management unit 902 first
The contents of the old table in the table area 111 are read, the contents of the new table file received from the table management unit 108 are compared with the contents of the old table, and the differences between the two are stored in the change history area 902 in the main device 113. After that, the contents of the new table file are stored in the table area 111 via the memory storage unit 109.

On the other hand, when the operator operating the maintenance terminal 112 issues a request to display the table change history, the table change history display unit 901 is activated. The table change history display unit 901 first acquires the table change history in the change history area 902 of the main body device 113. Specifically, the table change history management unit 902 in the main body device 113
Reads the table change history in the change history area 902 and transfers it to the table management unit 108. The table management unit 108 stores the table change history in the main unit 1.
Communication unit 107 with maintenance terminal in 13 and maintenance terminal 112
The data is transferred to the table change history display unit 901 via the communication unit 106 with the main body.

The table change history display unit 901 converts the table change history received from the main body device 113 into a format that is easy for the operator to see and displays it on a display device (not shown).

According to the above fifth embodiment, the main body device 113 automatically manages the modification date and time and modification contents of the table contents in the table area 111, so that the safety of the table version management can be improved. It will be possible. Sixth Embodiment FIG. 10 is a configuration diagram of the sixth embodiment of the present invention.

The sixth embodiment is characterized in that it is not necessary to stop the main unit while the table is being changed. First, as shown in FIG. 11, in the operating state of the main body device 1007, the table file is changed on the maintenance terminal 1006 side in the same manner as in the first embodiment, and the table file unit 1 in the maintenance terminal 1006 is changed.
The new table file in 001 is transferred to the main body device 1007. The contents of this new table file are stored in the first table area 1002 in the main body device 1007.
During this time, each application 10 in the main device 1007
05 continues the operation while referring to the second table area 1004.

Next, at a proper timing, the main unit 10
07 is restarted, and as shown in FIG. 11, the main body device 1007 is in the operation stop state only during this restart. In the restart sequence described above, the table conversion unit 1003 in the main body device 1007 determines that the first table area 1002
If the contents of the new table file are written in the table, the contents are converted into a format that can be easily referred to by each application 1005, and the converted table contents are written in the second table area 1004.

After the restart sequence, the main unit 10
When 07 resumes operation, each application 1005
Restarts the operation according to the new table contents written in the second table area 1004 (see FIG. 11).

According to the sixth embodiment described above, since each application 1005 in the main body device 1007 does not refer to the table contents in the first table area 1002 before conversion, the main body device 1007 is in the operating state. At some time, the new table file can be transferred from the maintenance terminal 1006 to the main body device 1007. Therefore, when changing the table, the operator need only transfer the new table file from the maintenance terminal 1006 to the main body device 1007 and then restart (reset) the main body device 1007, which greatly simplifies the operation when changing the table. Can be converted.

Further, the operation stop time of the device can be shortened and the device operating rate can be improved. Also,
The converted table contents are stored in each application 1005.
Has a format that is easy to refer to, so that the execution time of the processor for each application 1005 can be shortened.

Furthermore, the system developer uses the main unit 10
It is not necessary to mount a maintenance mode or other maintenance mode on the 07 side, and development efficiency can be improved. Seventh Embodiment FIG. 12 is a configuration diagram of the seventh embodiment of the present invention.

The seventh embodiment is characterized in that, in the multiprocessor system, the table commonly used by all the processors is not arranged in the shared memory.

In FIG. 12, first, the system management CP
The table conversion unit 1203 in U1212 is similar to the case of the sixth embodiment in that the maintenance terminal 12 is reset at the time of reset.
The new table contents received from No. 11 in the first table area 1202 are converted into a format easily referred to by the application 1205, and the converted table contents are written in the second table area 1204.

Further, the table distribution unit 1206 in the system management CPU 1212 uses the inter-CPU communication function to send the new table contents written in the second table area 1204 to the individual function CPU 1213.

Upon receiving the new table contents from the system management CPU 1212, the table receiving unit 1207 in each individual function CPU 1213 stores the new table contents in the local table area 1208 in the own device and starts the operation of the own device.

Each application 1205 in the system management CPU 1212 starts operation according to the new table contents written in the second table area 1204. In addition, each application 1209 in the individual function CPU 1213 uses the local table area 12 in its own device.
The operation is started according to the new table contents written in 08.

According to the above seventh embodiment, the table contents are the local table area 1208 of each processor.
Since it is arranged (on the local memory), the execution time of the processor that accesses the table can be shortened.

Further, it is possible to avoid the concentration of access to the shared memory 1210 and improve the response of the entire system.

[0090]

EXAMPLE FIG. 13 is a block diagram of an example of a system for realizing the first to seventh embodiments. In this embodiment, the present invention is applied to an online real-time system having an HDLC (high level data link procedure) line control function using a tightly coupled multiprocessor device having a shared memory and an individual output function.

This system includes a system management CPU 13
20, an HDLC line control CPU 1321, and an individual output control CPU 1322. The software running on the system shown in FIG. 13 (hereinafter, also referred to as the main body device) is assumed to be developed on the software development personal computer 1408 having the configuration shown in FIG.

The system (main unit) shown in FIG. 13 has a function of connecting to the maintenance terminal 1518 shown in FIG. In the software development personal computer 1408 shown in FIG. 14, the software operating on the main body apparatus shown in FIG. 13 is developed. The program source of the software is roughly divided into the program executed on the main body apparatus. Source file 1401 and a table source file 1402 placed on the main unit.

These files are compiled, linked,
When located, a main unit load module file 1403 and a locate map file 1404 are generated. Main unit load module file 1403
Is a file that is loaded and used in the main unit.
The locate map file 1404 is a file containing each program executed by the main body device, locate addresses of symbols in the table, and the like.

The table change file automatic generation program 1405 in the software development personal computer 1408 is based on the table source file 1402 and the locate map file 1404, and the screen definition file 1406.
And an attribute definition file 1407.

FIG. 16 shows the table source file 140.
2 shows an embodiment. In this embodiment, this file is C
Written in language. It can be seen from FIG. 16 that the main unit shown in FIG. 13 has a system definition table, an HDLC line definition table, and an individual output definition table.

FIG. 17 shows the locate map file 140.
4 shows an example. This file contains the locate address of the symbol name of each table element in the table source file 1402 shown in FIG.

FIG. 18 shows an example of the screen definition file 1406. This file is a file automatically generated from the table source file 1402 shown in FIG. 15 and the locate map file 1404 shown in FIG. "$$" in this file indicates an item to be input when the table is changed.

FIG. 19 shows an example of the attribute definition file 1407. This file is a file automatically generated from the table source file 1402 shown in FIG. 15 and the locate map file 1404 shown in FIG. As the attributes of each input item in the screen definition file 1406 shown in FIG. 18, the main body device memory address, the input format, the display color, and the data type are included.

Next, the maintenance terminal 1518 shown in FIG.
In the software development personal computer 1 shown in FIG.
A screen definition file 1501 (corresponding to the screen definition file 1406 of FIG. 14) and an attribute definition file 1502 (attribute definition file 14 of FIG. 14) copied from 408.
(Corresponding to 07), the table changing program 1503 operates to realize the table changing function and generate a table file in the table file unit 1504.

FIG. 20 shows an example of a table change screen realized by this table change function. The reverse item is the input item. In this way, the table changing function can be automatically provided from the program file of the main unit.

The table file generated in the table file section 1504 by the above-mentioned table changing function is
The table transmitting unit 1505, the table receiving unit 1506, and the table comparing unit 1507 realize the operation of transmitting, receiving, and comparing the table file with the main body device shown in FIG.

Further, based on the screen definition file 1501 and the attribute definition file 1502 copied from the software development personal computer 1408, the table changing program 1
503 operates in the read-only mode, and the table changing program 1503, the receiving function of the table receiving unit 1510, and the temporary table file unit 1509 operate in cooperation to realize the display function of the internal device table.

Further, based on the screen definition file 1511 and the attribute definition file 1512, the table changing program 1513 operates in the read-only mode, and the table changing program 1513 and the table receiving unit 151
The reception function of No. 5 and the temporary table file unit 1514 operate in cooperation with each other to realize the display function of the internal device state.

On the other hand, by providing the table change history display section 1516 in the maintenance terminal 1518, it becomes possible to display the change date and time and the changed portion of the table in the main body.

FIG. 21 shows an embodiment of the table change history area 1308 in the main unit shown in FIG. A plurality of change histories can be stored in this area. When the change history area is full, the latest change history is overwritten with the oldest history, so that the latest n history is always stored in this area. Each change history includes a change date and time, the number of changed addresses, and (a set of changed addresses, old data, and new data).

FIG. 22 shows an example of the table change history display screen. The table change history display unit 1516 in the maintenance terminal 1518 receives the table change history in the table change history area 1308 in the main body apparatus shown in FIG. 13, translates the content, and displays it. As shown in FIG. 22, only the changed date and time and the changed portion are displayed.

In the main unit shown in FIG. 13, the table management unit 1302 receives the table file received from the maintenance terminal 1518 shown in FIG. 15 via the maintenance terminal communication unit 1301 as the table change history management unit 1303. The first table area 130 via the memory storage unit 1304
6 is stored. The table management unit 108 also displays the device status acquired from the device status area 1307 via the memory acquisition unit 1305 and the table change history management unit 1303.
The maintenance terminal 1518 is transmitted via the communication unit 1301 with the maintenance terminal.
Send to

When the contents of the new table file received from the maintenance terminal 1518 are written in the first table area 1306, the table change history management unit 1303 makes the first table
The table change history is automatically saved in the table change history area 1308 by acquiring the old table content from the table area 1306 via the memory acquisition unit 1305 and comparing the content of the new table file with the old table content. Also, the table change history management unit 1303 receives the table change history area 1 when requested by the maintenance terminal 1518.
The table change history stored in 308 is transmitted to the maintenance terminal 1518 via the table management unit 1302 and the maintenance terminal communication unit 1301.

The table conversion unit 1309 in the system management CPU 1320 is configured to reset the first table area 1 when reset.
The contents of the new table in 306 are set in the system management unit 131.
1, HDLC line control unit 1315, and individual output unit 13
18 is converted into a format that can be easily referenced by each application, and the converted table contents are converted into the second table area 1
Transfer to 310.

Further, the table distribution unit 1312 in the system management CPU 1320 uses the mailbox via the shared memory 1319 to make the HDLC line control CPU 13
21 and the contents of the individual output definition table to the individual output control CPU 1322, respectively.

Upon receiving the table contents from the system management CPU 1320, the table receiving unit 1313 in the HDLC line control CPU 1321 stores the table contents in the HDLC table area 1314 on the local memory in the own device,
Start operation of own device.

Upon receiving the table contents from the system management CPU 1320, the table receiving unit 1316 in the individual output control CPU 1322 stores the table contents in the individual output table area 1317 on the local memory in the own device and starts the operation of the own device. To do.

The system management section 1311 of the system management CPU 1320 starts the system management operation according to the new table contents written in the second table area 1310. Also, the HCLC line control system 1321
The HDLC line control unit 1315 in the
The HDLC line control operation is started according to the new table contents written in the C table area 1314. Similarly, the individual output unit 13 in the individual output control CPU 1322
18 starts the operation of the individual output operation according to the new table contents written in the individual output table area 1317 in the own device.

[0114]

According to the first aspect of the present invention, the table contents are managed as the table file on the maintenance terminal, so that the table can be changed in a place (office or the like) where the main unit is not present. Therefore, the operator can prepare the table contents in advance, and the safety of changing the table is improved.

Next, by using the definition file for the table change function, the system developer can easily provide the table change function by only creating the definition file of the screen image and the table structure. Efficiency is improved.

Next, with the configuration having the definition file generating means, the system developer can provide the table changing function with almost no work, and the development efficiency can be improved. Further, since the occurrence of a bug due to the difference in recognition of the table structure between the table structure of the main body device and the function of the table changing unit of the maintenance terminal is eliminated, the reliability of the function of the table changing unit can be improved.

Next, the table receiving means and the table changing means having the read-only mode are operated in cooperation with each other, whereby the display function of the table contents and the apparatus state of the main body apparatus can be easily realized.

Next, with the configuration capable of managing the update history,
The safety of table version management can be improved.
Next, with the configuration including the table conversion means, it is not necessary to stop the operation of the main body device when the changed table contents are transferred from the maintenance terminal to the main body device, and the main body device is simply reset after the transfer is completed. Since the table contents of the apparatus can be updated, it is not necessary to mount a maintenance mode or other maintenance mode on the main body apparatus, and it is possible to prevent a decrease in the operating rate of the main body apparatus.

According to the second aspect of the present invention, the table contents are held locally in each processor.
It is possible to reduce the execution time of the processor that accesses the table contents. Further, it is possible to avoid concentration of access to the shared memory and improve the response of the entire system.

[Brief description of the drawings]

FIG. 1 is a configuration diagram of a first embodiment.

FIG. 2 is an operation flowchart of the first embodiment.

FIG. 3 is a configuration diagram of a second embodiment.

FIG. 4 is an operation flowchart of a table changing program according to the second embodiment.

5 is an operation flowchart showing details of step 404 in FIG. 4. FIG.

FIG. 6 is a configuration diagram of a third embodiment.

FIG. 7 is an operation flowchart of a table changing file automatic generation program according to the third embodiment.

FIG. 8 is a configuration diagram of a fourth embodiment.

FIG. 9 is a configuration diagram of a fifth embodiment.

FIG. 10 is a configuration diagram of a sixth embodiment.

FIG. 11 is a diagram showing a table changing procedure according to the sixth embodiment.

FIG. 12 is a configuration diagram of a seventh embodiment.

FIG. 13 is a block diagram of an embodiment of the system.

FIG. 14 is a configuration diagram of an embodiment of a software development personal computer.

FIG. 15 is a configuration diagram of an embodiment of a maintenance terminal.

FIG. 16 is a diagram showing an example of a table source file.

FIG. 17 is a diagram showing an example of a locate map file.

FIG. 18 is a diagram showing an example of a screen definition file.

FIG. 19 is a diagram showing an example of an attribute definition file.

FIG. 20 is a diagram showing an example of a table change screen.

FIG. 21 is a diagram showing an example of a table change history area.

FIG. 22 is a diagram showing an example of a table change history display screen.

FIG. 23 is an explanatory diagram of a conventional technique.

FIG. 24 is a diagram showing a table changing procedure in the conventional technique.

FIG. 25 is an explanatory diagram of a conventional table arrangement technique in a multiprocessor system.

[Explanation of symbols]

 101 table file 102 table transmitting unit 103 table receiving unit 104 table comparing unit 105 table changing unit 106 communication unit with main body 107 communication unit with maintenance terminal 108 table management unit 109 memory storage unit 110 memory acquisition unit 111 table area 112 maintenance terminal 113 Main unit

Claims (13)

[Claims] 1. A computer system having an operation definition information table on a memory of a main body device and capable of connecting a maintenance terminal, wherein the operation definition information table for the main body device is managed as a table file in the maintenance terminal. Table transmitting means for transmitting the table content indicated by the table file managed by the table file managing means to the main body device, and transmitting the table in the maintenance terminal to the main body device. An operation definition information table management system comprising: a table updating unit that receives the table contents from the unit and replaces the table contents held by the main body device with the table contents. 2. The main body device further includes table transmitting means for transmitting the table contents held by the main body device to the maintenance terminal, and the table file managing means includes the table transmitted by the table transmitting means. The operation definition information table management system according to claim 1, further comprising a table receiving unit that receives contents as the table file. 3. The table file management means includes table comparison means for comparing the contents of the table file held by the table file management means with the contents of the table file received by the table reception means in the table file means. The management method of the operation definition information table according to claim 1, wherein 4. The operation definition information table management system according to claim 1, wherein the table file management means includes table modification means for modifying the contents of the table file. 5. The table changing means changes the contents of the table file based on the contents of a screen definition file that defines the screen display format and the contents of an attribute definition file that defines the structure of the operation definition information table. The operation definition information table management method according to claim 4, wherein the operation definition information table is changed. 6. The screen definition file and the attribute definition file are generated based on table source information for generating the operation definition information table and locate map information for storing the operation definition information table in the main body device. The operation definition information table management system according to claim 5, further comprising a definition file generation unit for generating. 7. The main body device further includes table transmitting means for transmitting table contents or device status held by the main body device to the maintenance terminal, and the table file managing means transmits by the table transmitting means. The table changing means in the table file managing means has a function of opening the table file in a read-only mode. 7. The table contents of the main body device or the device status is displayed by linking the table receiving device in the managing device and the table changing device operating in the read-only mode with each other. The management method of the operation definition information table described in item 1 above. 8. A table update history holding means for holding an update history of an operation definition information table updated by the table update means, and an operation definition information table held by the table update history holding means in the main body apparatus. Table update history transmitting means for transmitting update history to the maintenance terminal, wherein the maintenance terminal receives and displays the update history of the operation definition information table transmitted by the table update history transmitting means in the main device. 8. The operation definition information table management method according to claim 1, further comprising a table update history display means for performing the operation. 9. The table updating means in the main body device receives the table contents from the maintenance terminal and holds the table contents, and the table contents holding means holds the table contents when the main body device is reset. 9. Table conversion means for converting the table contents and replacing the table contents held by the main body device with the converted table contents, the table conversion means according to any one of claims 1 to 8. Management method of operation definition information table. 10. A multiprocessor system which is connectable to a maintenance terminal, operates based on the contents of an operation definition information table, and has a shared memory, wherein an operation definition information table for the main unit is provided in the maintenance terminal. A table file managing unit that manages as a table file; and a table transmitting unit that transmits the table content indicated by the table file managed by the table file managing unit to a predetermined processor that constitutes the multiprocessor system. In the processor of the, including the table transfer means for receiving the table content from the table transmission means in the maintenance terminal, and transferring the table content to each processor constituting the multiprocessor system, in each processor, Table in the given processor An operation definition information table management system comprising: a table updating unit that receives the table contents from a transfer unit and replaces the table contents held locally by each processor. 11. A maintenance terminal used in the system according to claim 1. 12. A main unit used in the system according to claim 1. 13. A processor constituting the multiprocessor system according to claim 10.