JPH0581010A - Patch execution method - Google Patents

Abstract

PURPOSE:To automatically execute patching without stopping a system and without affecting the system operation of a user on the correction (patching) method of software such as OS operating on the computer system. CONSTITUTION:Patch data P is previously fetched into a patch data storage file 2a while the system is operated (1)-(3). Patching is executed (4) in a system stop sequence after the system operation terminates. When an error occurs in the execution of patching (4), patching is restored and error information is saved in a file storage device 2. Error information is displayed at the time of the subsequent start-up of the system.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a method of modifying (patching) software such as an OS operating on a computer system.

The importance and scale of software for operating a computer system are increasing, and as the scale of software increases, the number of software bugs also increases.

For this reason, software patches have become indispensable. However, it is necessary to avoid shutting down the computer system for that purpose, to minimize the influence on the user's system operation, and to execute the patches automatically. There is a need.

[0004]

2. Description of the Related Art FIGS. 3 to 5 and 6 are views for explaining a conventional patch execution method, in which (a) shows an operation flow and (b) shows actual patch execution. It is shown schematically.

The conventional patch implementation method has been implemented by the following method. (1) Manually execute the patch with the system stopped. That is, as shown in FIG. 3A, in a state where the system is stopped, for example, the system maintenance mode is set, and the patch is executed in the meantime. {Processing step 10 of FIG.
15} Specifically, by executing the patch program, as shown in FIG. 3 (b), the file storage device
The patch data P stored in the patch data file 2a of the (disk) 2 is overwritten on the software files (A file, B file) 2b, 2c, to be modified in the same file storage device 2 (shown with diagonal lines). By doing, patch.

(2) Manual or automatic patching is performed during system operation. That is, as shown in FIG. 4A, the patch program is executed during system operation. {Fig. 4
Refer to processing step 20 of (a)} (3) Prepare patch data during system operation (acquire it in advance), and at the next (or scheduled) system startup, for example, system initialization ( IMPL) automatically patch. {Steps 30-34 of Fig. 5 (a)
reference}

[0007]

The above patch implementation method has the following problems. (1) A running system, such as an online system,
As described with reference to FIG. 3A, it is difficult to stop due to a patch, and there is a problem that a patch execution schedule must be set up in accordance with the stop of the system.

(2) In order to execute the patch during the system operation described with reference to FIG. 4, the patch process becomes very complicated, such as considering the time difference when the program is modified, and the operation is guaranteed. Becomes difficult.

A specific example of the problem will be described with reference to FIG. In the patch data file 2a of the file storage device (disk) 2, the patch data P stored from the remote maintenance center, patch floppy disk, etc. is executed during the system operation of the patch program {processing step 20 of FIG. 4 (a) 20.
Then, the software is modified by overwriting (indicated by diagonal lines) on the software files 2b and 2c to be modified, but since the patches are executed in a certain order, The software (for example, A file 2a) before being executed is loaded and executed in the main storage unit (MSU) (memory) 3, and the software for which the patch is executed (for example, B file) But,
The main memory (MSU) (memory) 3 and the one that is being executed will coexist, and among multiple programs, one will be patched but the other will not be patched. Due to this, a logical contradiction occurs.

(3) The method described in FIG. 5 and FIG. 6 in which patch data is fetched during system operation and the patch is automatically executed at the next system startup does not require human intervention. Although the effect on the operation is small, since the patch is performed in the middle of the startup sequence, the program loaded after the patch is executed (for example, A,
Although the B file) is patched, the program loaded before the patch is executed (for example, operating system (OS)) is not patched, so there is a risk of inconsistent program operation.

This problem will be specifically described with reference to FIG. 6 (b). That is, in order to execute the patch program,
The operating system (OS) needs to be loaded, but if a patch is required for the operating system (OS), first, when the operating system (OS) is loaded at system startup, The operating system (OS) has not been patched, and the patch program is executed in this state, for example, a certain application program (A file, B
When a patch of a file) is executed and the application program is executed, the operating system (OS) is still unpatched, so there is a risk of causing inconsistency in the execution of the application program.

Of course, when the operating system (OS) gives top priority to the execution of the patch program at system startup, the above problem can be avoided, but a plurality of application programs (patch Controlling the submission of (including programs) to the dispatch queue becomes complicated.

For this reason, in FIG. 5 (a), the method for restarting the startup sequence of the system after the execution of the patch during the startup of the system is finished, It takes extra time, affects the system start-up time, and degrades the service to the user.

In view of the above-mentioned conventional drawbacks, the present invention is directed to an operating system (O) operating on a computer system.
To carry out software modifications (patches) such as (S),
It is an object of the present invention to provide a patch execution method that can automatically perform a patch without stopping the system and without affecting the user's system operation.

[0015]

FIG. 1 illustrates the principle of the present invention. The above problems are solved by the patch implementation method configured as follows.

(1) A method of modifying software (programs and data) in a computer system 1, wherein the patch data P is fetched into a file storage device 2 while the computer system 1 is operating, and the computer data is stored. Configure to automatically perform the patch during the system shutdown sequence after the operation of System 1 is completed.

(2) When an error occurs during patch execution in the system stop sequence after the operation of the computer system 1 is finished, the patch in which the error occurred is restored and the error information is displayed. The file storage device (system disk) 2 is saved, and the error information is displayed at the next system startup.

[0018]

According to the present invention, in order to solve the above-mentioned problems, the patch data P is loaded into the file storage device (system disk) in advance during the system operation, and in the system stop sequence after the system operation is completed. By automatically performing the patch, the patch is implemented without affecting the operation system.

If an error occurs during the patch execution in the system stop sequence after the system operation ends, the patch is restored based on the execution of the patch in which the error occurred, and the error information is returned. The file is stored in the file storage device and the error information is displayed at the next system startup.

Therefore, it is not necessary to stop the system, which has caused a problem in the conventional patch execution method, and the patch is not executed when the system is started up. Therefore, the problem of the time difference of the program correction can be avoided. It is possible to minimize the influence on the operation of the user's system.

Further, when an error occurs during execution of the patch during the system stop sequence, the patch having the error is restored and the error information is notified at the next system startup. There is an effect that the error can be dealt with without causing a problem in operation.

[0022]

Embodiments of the present invention will now be described in detail with reference to the drawings. FIG. 1 described above is an explanatory view of the principle of the present invention.
FIG. 4 is a flowchart showing an embodiment of the present invention.

According to the present invention, means for automatically fetching patch data during system operation and automatically executing patch in the system stop sequence after the system operation is finished, and patch in the system stop sequence When an error occurs during execution, a means for saving the error information in a file storage device (system disk: magnetic disk device) and displaying the error information at the next system startup, It is a necessary means for carrying out the present invention. The same reference numerals denote the same objects throughout the drawings.

The patch execution method of the present invention will be described below with reference to FIG. 2 while referring to FIG. 1 and FIGS. As a method for fetching patch data during system operation, there are methods shown by ,, and in FIG.

, Sets an external medium (magnetic tape, floppy disk, etc.) storing patch data in the input / output device of the customer's computer system, and sets its contents (patch data P) to the patch data of the magnetic disk device 2. It is a method to drop it in file 2a.

The patch data file 2a of the magnetic disk device 2 is fetched via a line from a remote maintenance center that manages the distribution of patch data.
It is a method to drop it in.

Next, when a system stop such as power-off is instructed, condition determination is performed in the system stop sequence as shown in the flowchart of FIG. 2, and the patch execution condition (patch execution mode and unexecuted patch Exists)
When the processing (see processing steps 50 and 51 in FIG. 2) is completed, the patch data P captured in the patch data file 2a is converted into the target file (A in FIG. 3, FIG. 4, FIG. 6) as shown by in FIG. File, B file).

If there is an error in executing the patch during the system stop sequence, the process step 53, FIG.
As indicated by 54, after restoring the patch with the error, the error information is stored in a specific area (not shown) of the magnetic disk unit 2 and the error is generated at the next system startup. Display information (process step 55 of FIG. 2,
By doing so, it is possible to provide the user with the presence or absence of abnormality and the abnormality information.

As described above, the present invention is a modification (patch) of software such as an OS operating on the computer system.
In the method, when the patch data is previously captured in the patch data storage file during the system operation, the patch is executed in the system stop sequence after the system operation is completed, and an error occurs during the execution of the patch. Is characterized in that the patch is restored, the error information is saved in the file storage device, and the error information is displayed at the next system startup.

[0030]

According to the present invention, the patch is executed in the power-off sequence after the system work is completed, so that the influence on the operation of the user system can be minimized as shown below.

(1) It is not necessary to stop the operating system. (2) Since the patch is executed while the system is stopped, there is no need to perform complicated control for patch execution, such as considering the time difference of modification between programs.

(3) In the method of executing the patch during system operation or system startup, the programs loaded after the patch execution are patched.
Since the program loaded before the patch execution is not patched, there is a risk of causing inconsistency in the program operation.However, in the present invention, since the patch is executed during the system stop process, the next power-on There is no risk of causing inconsistency in program operation because all patches are started up in a file.

(4) If there is an error in executing the patch while the system is stopped, error information is notified at the next system startup, and the error can be dealt with by the information.

[Brief description of drawings]

FIG. 1 is an explanatory diagram of the principle of the present invention.

FIG. 2 is a flowchart showing an embodiment of the present invention.

FIG. 3 is a diagram (part 1) illustrating a conventional patch implementation method.

FIG. 4 is a diagram (part 2) for explaining a conventional patch implementation method.

FIG. 5 is a diagram (part 3) for explaining a conventional patch implementation method.

FIG. 6 is a diagram (part 4) for explaining a conventional patch implementation method.

[Explanation of symbols]

1 Computer system or system 2 File storage device (disk, system disk) or magnetic disk device 10-15, 20, 30-34, 50-56 Processing step-Storing patch data To the target file of patch data Application (Patch execution) P Patch data

Claims (2)

[Claims] 1. A method for modifying software (program and data) in a computer system (1), comprising patch data during operation of the computer system (1).
Import (P) into the file storage device (2) (,
,) Every other time, the patch is automatically executed () during the system stop sequence after the operation of the computer system (1) is finished. 2. A patch implementation in a system shutdown sequence after the operation of the computer system (1) is completed.
In (), when an error occurs, the patch in which the error occurred is restored and the error information is saved in the file storage device (2). The patch execution method according to claim 1, wherein the patch is displayed.