JPH03192947A - Software patch mis-input prevention system - Google Patents

Abstract

PURPOSE:To revise the version number of a system file without mistake by collating version number history information with version number information with patch applied thereto and controlling the execution of a man-machine interface command inputted to the exchange system in response to the result of collation. CONSTITUTION:An exchange system consists of a controller 1, a main memory 2, an input terminal equipment 3 and a floppy disk 4. In order to apply version number management of a system file, the history of the generation of the system file and of version number information of a software patch entered and publicated as a software revision notice sheet is recorded. Then the system file to which the software patch commanded by the exchange system with the command is applied is collated with the version number information in the system and the execution of the command inputted from the floppy disk 4 is controlled in response to the result of collation. Thus, the system file version number of the exchange system is revised by the software patch without error.

Description

DETAILED DESCRIPTION OF THE INVENTION (Industrial Application Field) The present invention relates to an electronic exchange system controlled by stored programs, in which a software patch is input from a floppy disk medium to update the version number of a system file without error. Regarding the JC error input prevention method.

(Prior Art) When updating the system file version number of an exchange system using a software patch, the software patch input method must be able to prevent erroneous input, and be easy and quick.

Conventionally, this was accomplished by giving a version number to a software patch as a unit for updating system files, recording it in a command format on a floppy disk medium as a patch file, and instructing the exchange system with a servile command. are doing.

As a result, it is common practice to execute commands on a floppy disk and install patches without the intervention of a maintenance person.

(Problem to be Solved by the Invention) The above-mentioned conventional method of inputting software patches from a floppy disk is such that by instructing the exchange system using a dedicated command, the fixed commands are recorded on the floppy disk medium and the fixed commands are sent without the intervention of a maintenance person. , are sequentially input into the exchange system and executed.

Normally, a new load module file is applied to the exchange system by adding a new function that cannot be supported by a software patch to the system file of the exchange system. Due to this method, the system files of the exchange system have multiple generation versions. (9) When adding functions to a certain generation of system files using software patches, or making changes or bug fixes, it is necessary to manage the status of software patches that have been applied to the system files. Furthermore, it is essential to manage the application status of software patches applied to system files in case a problem occurs in the exchange system later, or in order to add functions such as VR.

as a means of trying to solve these challenges.

Apart from the system file generation information, a software patch (for example, the addition of one function) is assigned a version number as a unit of revision, issued as a software change notification, and submitted to the exchange system as a batch. It is common to manage revisions of system files.

In this way, if the system files of the exchange system have multiple generations and multiple batch versions, when a software patch issued as a software change notification by the conventional method is introduced, the system to which the software patch is applied A batch may be erroneously submitted to a system file of a different generation than the file, or there may be duplicate batch addresses between batches of software change notifications with different issue dates, and software changes may occur regarding batch submission. If there is an order among the notifications, there is a drawback that they are input in the reverse order.

Furthermore, in order to avoid duplication of batch addresses and to manage revisions, software change notifications issued for revision management are submitted in the order in which they are issued, so that software change notifications issued later can be
has the disadvantage that previously issued software change notifications cannot be input, and software change notifications that apply only to exchange systems with different station conditions also apply to exchange systems that use the same generation of system files. It degrades the quality of system files because of the need,
6g, there is a drawback that it causes.

Among the above drawbacks, the biggest drawback is that batch input depends on the system maintainer.

The purpose of the present invention is to record the entire history of system file generations and version information of software patches issued and installed as software change notices in order to manage the versions of system files. The system file to which the software patch is applied, as instructed by The object of the present invention is to provide a method for preventing erroneous input of software patches so that software patches can be introduced into an exchange system without the need for judgment.

(Means for solving the problem) The software patch erroneous input prevention method according to the present invention includes a floppy disk medium, an input terminal means, a recording means,
The device is configured to include a control means.

The floppy disk medium is for recording in the form of patch man-machine interface commands for adding, changing, and modifying software functions in electronic exchanges.

The input terminal means is for reading out the "man-machine interface commands" in order 11 according to instructions from the electronic exchange and inputting them to the electronic exchange.

The recording means is the ninth one for recording the version history information of the system file in the exchange system of the electronic exchange.

The control means is for collating the version number history information and the version number information to which the batch is applied, and controlling the execution of the man-machine interface command input to the exchange system according to the verification result.

(91, example) Next, the present invention will be explained with reference to the drawings.

FIG. 1 is a block diagram showing the configuration of an exchange system in a software patch erroneous input prevention method according to the present invention.

In FIG. 1, 1 is a control device, 2 is a main memory, and 3 is a control device.
is an input terminal, and 4 is a 70-tube disk.

FIG. 2 is a block diagram of a memory used to check and record the version number of a system file.

In the M2 diagram, Pi is the first parameter in Table 1 shown at the end of "81 Detailed Description of the Invention."

No. 1 is the second to fifth parameters in Table 1, and S is the state of Pi. The command format in Table 1 consists of a function name and first to fifth parameters.

FIG. 3 is an explanatory diagram showing the conflict relationship between the command being executed, which is used in the 59th command execution control line, and the input command.

In the third factor, F N Ox is the salt of the command function being executed, i;'Noy is the salt of the command function input from the input terminal, and Rxy is the salt of the command function being executed.
This is a race condition with y.

FIG. 4 is an explanatory diagram showing the relationship in the input order of commands recorded on a floppy disk medium.

In FIG. 4, parts B) and (C) indicate nine parts added to the system according to the present invention. Part (a) checks the version number of the system file, and controls the execution of commands in part (b). The part (b) shows the software patch in the form of commands, and these commands rewrite programs and data in system files in batch mode. Part (c) sets a new version number in the system file, and controls the execution of commands in part (b).

Next, the operation of the present invention will be explained.

The first parameter in Table 1 specifies the generation number of the system file, and the second to fifth parameters specify the version number of the system file revised by the software patch.

When the command shown in Table 1 is input to the exchange system, the system indexes the table shown in Fig. 2 by all parameters 1 to 5, determines the state of each parameter,
ANL) Depending on the conditions, the first parameter is used to check whether the version number specified in the second to fifth parameters is recorded for the system file, and if it is recorded, it is considered normal. Or output abnormal status.

This state is assumed to be 1 (ESULTI).

The commands shown in Table 2 at the end of "81 Detailed Description of the Invention" use the complement condition to specify the version number specified by the second to fifth parameters for the system file specified by the first parameter. Check whether it is recorded or not.
Outputs all normal and abnormal states, assuming that no data is recorded. In this state, if R, ESUI, T2
shall be.

When the execution results of the commands in Tables 1 and 2 are both determined to be normal, the third
Index the table shown in the figure. That is, by indexing the table in FIG. 3 with the command in table 3, the command t'' on the floppy disk medium can be stored. In the table in FIG. and the first of Table 3
FNCy specified by the parameter is used as the index. By the above operation, the restricted state of axy is released.

The table in FIG. 3 is checked by the command analyzer 14F: of the exchange system when a command is input, and if Rxy is in a restricted state, the input command becomes an error.

The command shown in the fourth item at the end of "81 Detailed Description of the Invention" indexes the table of FIG. 2 using the first and second parameters, and records all new board numbers in the system file. In the fourth edition, the data is the new edition number revised by the batch.

The commands shown in Table 5 listed in page B at the end of ``81 Detailed Description of Inventions'' are indexed using the parameters of table 1 shown in FIG. 3, and set up the regulation status of foxy.

(Effects of the Invention) As explained above, the present invention records the generation of system files and the history of version information of software patches issued and introduced as software change notices in order to manage system file versions. At the same time, by checking the system file to which the software patch applied, which is instructed by the command to the exchange system, with the version information in the system, and controlling the execution of the command input from the floppy disk according to the verification result. For an exchange system that has many generations of system files and versions due to software patches, it is possible to submit a batch without going through the judgment of the system maintainer. This has the effect of eliminating the error p.

In addition, it was necessary to manage the number of versions of system files for all stations in the exchange system regarding batch application.
It is said that the revision management of software patches can be easily performed because it is only necessary to manage the number of released versions of patches issued for each generation, and there is no need to manage the number of installed versions.

[Brief explanation of drawings]

FIG. 1 is a block diagram of a hardware configuration showing an embodiment of the software patch erroneous input prevention method according to the present invention. FIG. 2 is an explanatory diagram showing the configuration of a memory that performs version number checking and version number recording of system files. FIG. 3 is an explanatory diagram showing a competitive relationship between a command being executed and an input command used to control command execution. FIG. 4 is an explanatory diagram showing the relationship in the input order of commands recorded on a floppy disk medium. 1... Control unit ff12... Main memory 3... Input terminal 4... Floppy disk 11 Figure 2 Figure P+ 23

Claims (1)

[Claims] a floppy disk medium for recording patches in the form of man-machine interface commands for adding or changing software functions and fixing bugs in an electronic exchange; and a floppy disk medium for recording patches in the form of man-machine interface commands for adding or changing software functions and fixing bugs in an electronic exchange; an input terminal means for sequentially reading and inputting the information to the electronic exchange; a recording means for recording version history information of the system file in the exchange system of the electronic exchange; and control means for controlling the execution of man-machine interface commands input to the exchange system according to the verification result. Prevention method.