JPH05265741A - On-site replacement method for software - Google Patents

Abstract

PURPOSE:To provide the replacement method which can surely and easily replace the software and also can change the modules on site by producing a suspend file in an office and carrying it to the actual site when the software is largely to be corrected. CONSTITUTION:The processing procedures for replacement of the software are identified based on a fact whether the software amount to be corrected is large or small and also whether the software can be corrected by the maintenance function of a system or not. If the software amount to be corrected is large, the software is replaced with replacement of the suspend files. When a program is changed, the same program stored in an office is corrected (S1) and a new suspend file is produced (S2). This file is carried to the actual site, and the registered item name data, the KDL rules, and the equipment rules are stored in a file on the spot (S3). Then, the file is loaded into the suspend file which undergone the correction of a program (S4). Furthermore an external file is used for production of new suspend file (S5).

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a method for on-site replacement of software in a computer system.

[0002]

2. Description of the Related Art A centralized supervisory control system for a substation is a computer for a central integrated control station and a computer for a local transmission substation or distribution substation connected by a remote supervisory control device to display and measure information. Is performed and online processing is performed by transmitting control information.

In the online system as described above, software such as an automatic substation operation procedure creating system is prepared in the local computer.
Such software needs to be replaced with newly created software due to modification of the operation procedure program or change of substation equipment.

Conventionally, in order to replace the local software, a plurality of processes matching the data file and the version are copied onto a magnetic tape, and the magnetic tape is carried to the site,
Replace process units. In this replacement, if the computer system is divided into a main system and a slave system, the two systems are alternately replaced.

[0007] Software replacement requires link processing to change modules, so that the system is stopped for a long time, and at least process units are replaced.

[0006]

In the conventional software replacement method, when many corrections are required, many processes are brought to the site, and the process and data file versions are replaced at the site, which results in work load. Will grow.

When the amount of correction is small or when the maintenance function attached to the software is used, the process and data in the field are tested and replaced. At this time, however, there may be a difference with the environment in the field. ..

It is an object of the present invention to provide a replacement method that surely and easily replaces the local software including the modification of the module.

[0009]

SUMMARY OF THE INVENTION In order to solve the above problems, the present invention relates to a computer system in which a local system is operated by a computer using the LISP language. Create a suspend file that changes the rule data that will not be changed by, bring the suspend file to the site, save the rule data that is changed locally in the file, and load this save file in the suspend file Then, a new suspend file is created from this loaded file.

[0010]

The computer uses the LISP language, and the software is modified by replacing the suspend file.

[0011]

DESCRIPTION OF THE PREFERRED EMBODIMENTS FIG. 1 shows a processing procedure of a software replacement method according to an embodiment of the present invention. A distinction is made between cases where there is a large amount of software modification and cases where there is a small amount of software modification and cases where the software can be modified with the maintenance function of the system.

If the amount of modification is large, the software is replaced by replacing the suspend file. As for the suspend file, in a computer using the LISP language, as shown in the file structure of the automatic substation operation procedure creation system in FIG. 2, the data A changed in the local operation, the rule data B for this business, and this business program Of C, it corresponds to rule data B and program C that are not changed by local operation.

Similarly, the suspend file for rule maintenance is, as shown in FIG. 3, rule E and program F of rule data D and rule E and rule maintenance program F that can be changed by main work or maintenance.
Is equivalent to

For such a suspend file, when the program is changed, the same program stored in the company is modified (S1 in FIG. 1), and a new suspend file is created (S2).

This suspend file is brought to the site, and the data A such as the registered subject data and the KDL rules and equipment device rules are saved in a file at the site (S3), and this file is loaded into the program-modified suspend file (S4). ), The external file is further dropped into a file to create a newly created suspend file (S5).

The replacement of the suspend file by changing the program described above is as shown in FIG. 4. The suspend file modified in-house is brought to the site, the data modified by the user is dropped to the file, and the suspended file brought in. And create a suspend file again.

Therefore, the program and the data can be integrated except for the data that has been changed locally, and it is not necessary to match the versions of a plurality of processes.

Next, to change the suspend file for rule maintenance, bring back the local suspend file (S6), change the KDL rules and equipment data (S7), and reflect the correction rules and data in the brought-back suspend file. Then, the corrected suspend file is obtained (S8).

This suspend file is brought to the site, and a new suspend file is created by the same procedure (S3 to S5) as when changing the program. The replacement of the suspend file by the change of the rule maintenance is shown in the mode diagram shown in FIG. 5, and only the take-out of the local suspend file is different from that when the program is changed.

Next, a program change with a small correction amount is
The program of this portion is modified (S9), this partial program is brought to the site, the modified program is loaded into the local suspend file (S10), and a new suspend file is created (S11).

For the correction using the maintenance function, the rule data is corrected locally using the maintenance function (S12), and a new suspend file is created (S13).

In these cases as well, it is possible to operate without a version shift by creating a suspend file.

[0023]

As described above, according to the present invention, since the computer uses the LISP language and the suspend file is replaced when the software is replaced, the data changed locally is excluded. Bringing in and modifying a suspend file that integrates the program and data makes it easy to replace the software. In addition, there is an effect that the software replacement is surely made by eliminating the need to change the module and the process version.

[Brief description of drawings]

FIG. 1 is a processing procedure diagram showing an embodiment of the present invention.

FIG. 2 is a file configuration diagram of this work.

FIG. 3 is a file configuration diagram of rule maintenance.

FIG. 4 is a diagram showing how a suspend file is replaced for this job.

FIG. 5 is a diagram showing how a rule maintenance suspend file is replaced.

[Explanation of symbols]

Claims (1)

[Claims] 1. In a computer system in which a local system is operated by a computer using the LISP language, when a large amount of software is modified, a suspend file in which a program is changed internally or rule data that is not changed locally is used. Create, bring the suspend file to the site, save the rule data that is changed locally in the file, load this saved file into the suspend file, and create a new suspend file from this loaded file. How to replace the featured software locally.