JPH11134178A - Interrelated check system by information on number of versions of load module and program storage medium - Google Patents

Abstract

PROBLEM TO BE SOLVED: To previously check a load module before installation in the case of installing the new load module in a new function and correction on the load module constituting OS and AP in a computer system. SOLUTION: Dependence information 26 is contained in information of the number of versions in all load modules except for the number of the versions of a self-load module 25. When the self-load module uses a partial function of the other load module, the load module name of the other load module and the number of versions are set in dependence information 26. A function for checking whether the load module to be installed has dependence information or not when the new load module where the function is added and bug is corrected is installed on the computer system, and checking whether the load module in the depending relation is previously installed on the computer system or not when it has information is provided.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a method of checking version number information of a load module, and more particularly to a method of checking version number information between load modules.

[0002]

2. Description of the Related Art When upgrading the software of a computer system, especially when adding, changing, or correcting a bug of a software function, a part of a load module constituting the software is updated or newly loaded. The revision of the software may be performed by adding a module.

When making such a revision,
The load module to be newly installed is compared with the already installed load module. At this time, it is determined whether or not the load module to be newly installed is the upper version, so that the lower version is installed and the corresponding software does not operate abnormally.

As a means for comparing load modules in this case, version number information added when a load module is created is used. The version number information usually describes data indicating the source of the load module (eg, creation date, version, creator). In the case of comparing the same load module, the version existing in the load module is described. It is determined whether or not the load module can be updated by extracting and comparing the number information.

[0005]

In a method of upgrading software as in the prior art, only the versions of load modules to be updated are compared.

The reason is that when a load module to be installed uses a function of another load module, and the other load module using the function does not exist in the installation destination, the load module to be installed is not installed. This is because the computer system at the installation destination does not operate normally even if it is normally installed.

[0007] An object of the present invention is to provide a revision upgrading method for preventing abnormal operation of software due to revision of software in order to solve the above-mentioned problems.

[0008]

In order to achieve the above object, the present invention comprises a computer, a storage medium connected to the computer, and a first load module written on the storage medium. In the cross-relationship checking method based on version number information when installing on the computer, if the first load module exists in the computer, the first version name of the first load module and the first And a comparing means for comparing the second version name of the second load module with the second version number. If the first version number name is higher in the comparing means, one of the dependency information of the first load module is compared. Searching means for searching whether a third load module indicated by a load module name as a part exists in the computer; Checking means for checking whether the version name, which is a part of the dependency information, matches the version name of the third load module if the third load module name exists in the computer. It is characterized by having.

Further, each of the first, second, and third load modules includes a program section and a version number information section. The version number information section includes a version number of its own, and dependency information. And the dependency information includes a plurality of dependent load module names and dependent version numbers.

Further, if the version numbers match in the checking means, the load module is installed in the computer.

Further, the checking means notifies that the version numbers do not match unless the version numbers match,
The first load module is installed in the computer.

[0012]

DESCRIPTION OF THE PREFERRED EMBODIMENTS First, the operation will be described below.

All load modules (corresponding to files) in the computer system have version information of the load modules to which their own load module has a dependency in addition to their own version information. When updating a certain load module due to addition, change, bug fix, etc. of software functions, the version information of the load module to be updated is included in the version information of other load modules not to be updated. Check whether it is registered as a dependent load module. As a result of inspection, if there is a load module with a dependency,
When updating the load module, the user can be warned that a load module having a dependency exists. In addition, it is possible to verify in advance whether the load module operates normally before actually operating the load module by using the dependency information in the version number information of the load module.

Next, embodiments of the present invention will be described in detail with reference to the drawings.

FIG. 1 is a block diagram of a hardware configuration according to an embodiment of the method for checking the mutual relation of the version numbers of load modules according to the present invention.

Referring to FIG. 1, the hardware comprises:
A central processing unit 2, a computer 1 having an auxiliary storage device 3, a storage medium 7 storing a load module,
And a recording medium 10 on which a control program 11 for controlling version information of the load module is recorded.

The storage medium 7 and the recording medium 10 may be a magnetic disk, a semiconductor memory, or any other storable medium. The control program 11 is read from the recording medium 10 into the auxiliary storage device 3, and controls operations relating to version number information of the load module.

The auxiliary storage device 3 stores load modules constituting an operating system and application programs of the computer 1.
The load module A4, the load module B5, and the load module C6 on the auxiliary storage device 3 are load modules used in the computer 1.

The load module B'8 and the load module D9 on the storage medium 7 storing the load module are load modules to be installed in the computer 1. The load module B'8 is an upper version in which a bug has been corrected or a function of the load module B5 has been added. The load module D9 is a load module that operates using some functions of the load module B5.

In the example of FIG. 1, the load module B5 on the auxiliary storage device 3 is updated to the load module B'8 on the storage medium 7, and the load module D9 is newly installed on the auxiliary storage device 3. I have.

FIG. 2 is a diagram showing a data structure of each load module.

In general, a load module comprises a program section in which program codes and data are stored, and a version information section in which version information of the load module itself is stored. The version number information part is added when the load module is generated, and includes a date when the load module is created and a version name of the load module. According to the present invention, the correlation between load modules can be checked by newly adding dependency information to the version number information section.

Referring to FIG. 2, the load module comprises:
It comprises a program section 21 and a version number information section 22. The version number information section 22 is composed of a creation date 24, a version number name 25 of itself, and dependency information 26. The dependency information 26 stores information on load modules necessary for the own load module to operate.
The dependency relationship information 26 is composed of a plurality of records.
The record is composed of two pieces of data: a dependent load module name which is a dependent load module, and a dependent version number which is a version number of the dependent load module.

The dependency information 26 is used to check in advance whether a load module required for the operation of the own load module is already installed in the computer system before installing the own load module in the computer system. use. If the load module to be installed can operate by itself, it is not necessary to set the dependency information 26.

Further, regarding the load module name and the version number of the load module existing in the dependency information, if a load module having the same load module name already exists in the computer system to be installed, the version number If only the names do not match, the computer system user is notified that the version numbers do not match, and the process continues. This is because it is assumed that the functions of the load module are compatible even when the version numbers do not match.

Next, the operation of the embodiment of the present invention will be described with reference to FIG. 1, FIG. 2, FIG. 3, and FIG.

The dependency of the load module A4, load module B5, and load module C6 existing in the auxiliary storage device 3 of FIG. 1 and the load module B'8 and the load module D9 existing in the storage medium 7 is dependent on the five load modules. Is shown in FIG. Each dependency is determined by the dependency information 26 of each load module.

Referring to FIG. 3, the load module A4
Is independent of any other load module. A load module B5 and a load module C6 exist as load modules having a dependency relation to the load module A4. Both load modules have a dependency only on the load module A4. The load module B'8 is a higher version load module having the same load module name as the load module B5. The load module D9 is
It has a dependency on the load module B.

Therefore, as dependency information 26 (see FIG. 2) between the load module B5 and the load module C6,
Version number information of the load module A4 is set. In the dependency information 26 of the load module D6 (see FIG. 2), version number information of the load module B5 is set.

Now, the load module B'8 and the load module D9 in the storage medium 7 of FIG.
To be installed in the auxiliary storage device 3.

Since the load module B'8 has the same load module name as the load module B, the installation into the auxiliary storage device 3 means the revision of the load module B5.

In the case of the load module D9, since no load module having the same load module name exists in the auxiliary storage device 3, it means that a new installation is performed.

A procedure for installing the two load modules in the storage medium 7 into the auxiliary storage device 3 will be described with reference to a flowchart.

FIG. 4 is a flow chart showing the operation of updating the load module according to an embodiment of the present invention, showing the operation of the control program 11. Here, the load module B'8 and the load module D9 will be described separately.

First, when installing the load module B'8, the load module B'8 in the storage medium 7 is installed.
Of the load module and the version number information section 22 are obtained (step S1).

Next, it is checked whether a load module having the same load module name exists in the auxiliary storage device 3 (steps S2 and S3).

In this case, since the load module B5 having the same load module name already exists, it is next checked which of the load module B5 and the load module B'8 is the higher version. This is performed by comparing their own version number names 25 in the version number information section 22 of FIG. 2 of both load modules. If the result of the comparison indicates that the load module B'8 is a higher version, the installation processing proceeds to the next step S7. Otherwise, since the higher version has already been installed, the revision upgrade process ends without installing (steps S4, S5, S6).

Here, since the load module B'8 is an upper version, the process proceeds to step S7.

Next, when the load module B'8 is installed, whether the load module registered in the dependency information 26 of the load module B'8 (see FIG. 2) already exists in the auxiliary storage device 3. It is checked whether it is (step S8). The load module to which the load module B'8 has a dependency is the load module A4, like the load module B5. Since the load module A4 already exists in the auxiliary storage device 3, there is no problem even if the load module B'8 is installed (steps S10, S11, S1).
3).

If there is no load module in the auxiliary storage device 3 that has a dependency on the load module on the storage medium, the process of updating the target module is interrupted (step S9).

Next, consider the load module D9. First, the load module name of the load module D9 in the storage medium 7 and the version number information section 26 are obtained. Since there is no load module having the same load module name in the auxiliary storage device 3, it means a new installation. In the case of a new installation, the dependency of the load module D9 is checked (step S10).

As shown in the dependency relationship between the load modules in FIG. 3, the load module D9 has a dependency relationship with the load module B5. Here, if the load module B'8 has already been installed in the auxiliary storage device 3, the load module B5 having a dependency relationship with the load module D9 matches the load module name, but does not match the version number name. Will be. However, since the load module B'8 is an upper version of the load module B5, the function is likely to be upwardly compatible. Therefore, the user of the computer 1 is notified of the version mismatch as a warning, and the installation process itself proceeds. Then, the load module D9 is installed in the auxiliary storage device 3 (steps S11, S12, S13).

As a method of giving a warning when the version numbers do not match in the above description, a warning is given by displaying the version number on a CRT not explicitly shown in FIG. This allows the user to know that the state of the system has not been updated with respect to the system update.

[0044]

As described above, the effect of the present invention is as follows.
When updating a load module or installing a new load module in a computer system, before actually operating the load module,
The dependency information in the version number information of the load module makes it possible to verify in advance whether the load module operates normally.

The reason is that the information as to whether or not the own load module uses the function of another load module is stored as the dependency information in the version number information of all load modules, so that the information is already stored in the computer system. This is because the functional consistency of the load module is confirmed in advance by mutually checking the dependencies between the installed load module and the load module to be installed.

[Brief description of the drawings]

FIG. 1 is a block diagram of a hardware configuration according to the present invention.

FIG. 2 is a configuration diagram of version number information in a load module.

FIG. 3 is a diagram illustrating a dependency relationship between load modules.

FIG. 4 is a flowchart showing an operation of upgrading a load module according to an embodiment of the present invention.

[Explanation of symbols]

 DESCRIPTION OF SYMBOLS 1 Computer 2 Central processing unit 3 Auxiliary storage device 4 Load module A 5 Load module B 6 Load module C 7 Storage medium 8 Load module B '9 Load module D 10 Recording medium 21 Program part 22 Version information part 24 Creation date 25 Self Own version number 26 Dependency information

Claims (7)

[Claims] 1. A check method in a computer for managing a version number of a load module, wherein the version information of the load module includes first version information of its own,
Second version information of a plurality of load modules having a dependency relationship with the load module, wherein the first version information and the second version are used when installing the load module stored in the computer. A mutual relation check method based on version number information of a load module, wherein load module dependency information is checked using the number information. 2. A cross-correlation checking method using version information when installing a first load module written in the storage medium into the computer, comprising a computer and a storage medium connected to the computer, If the first load module exists in the computer, the first version name of the first load module and the second version name of the second load module to be updated
Comparing means for comparing the version number of the first load module with the version name of the first load module if the first version name is a higher version in the comparing means. Searching means for searching whether the indicated third load module is present in the computer; and, if the third load module name is present in the computer, the search means searches for a part of the dependency information. Checking means for checking whether or not a certain version number matches the version number of the third load module. 3. The first, second, and third load modules include a program section and a version number information section, wherein the version number information section has its own version name, and dependency information. 3. The mutual relation check method according to version information of a load module according to claim 2, wherein the dependency information includes a plurality of dependent load module names and dependent version numbers. 4. A method according to claim 2, wherein said load module is installed in said computer if the version numbers match in said checking means. 5. The method according to claim 2, wherein the checking means notifies the user that the version numbers do not match if the version numbers do not match, and installs the first load module in the computer. 3. A mutual checking method based on the version number information of the load module described in 3. 6. The computer obtains version information of the first load module from a storage medium, and if the load module is present in the computer, obtains version information of the first load module obtained from the version information. And a second version name of a second load module to be updated, and comparing the first version number with the first version name of the second load module to be updated.
If the version name of the first load module is a higher version, a search process for searching whether the third module indicated by the load module name which is a part of the dependency information of the first load module exists in the computer, If the third load module name exists in the computer in the search processing, it is checked whether a version number that is a part of the dependency information matches the version number of the third load module name. The check processing to be performed and the installation processing for installing the first load module from the storage medium into the storage device if they match in the comparison processing are performed based on the version number information of the load module storing the program for executing the program. Related check program recording medium. 7. A program according to claim 6, further comprising a program for executing, when the version numbers do not match in the checking process, notifying that the version numbers do not match. Recording medium for correlation check program.