JPH11120050A - Version managing method for management object stored on computer - Google Patents

Abstract

PROBLEM TO BE SOLVED: To accurately manage version information on a management object stored on a terminal computer. SOLUTION: This method performs version management wherein version information on the management object which is transmitted from a management computer 10 and stored on a different-area computer 20 is registered in a management data base 2 on the management computer 10. In this case, the management computer 10 sends the management object having the version information to the different-area computer 20 and registers the version information that the management object has in the management data base 2 and the different- area computer 20 receives and stores the management object and sends the version information that the management object has to the management computer 10, which receives and matches the management information against the version information in the management data base 2 to manage the version information.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a management computer connected to one or a plurality of terminal computers via a communication line, wherein the management computer manages the version number of a management target stored in the terminal computer. This is related to a version number management method for a managed object.

[0002]

2. Description of the Related Art In a conventional method of managing the version number of a management target stored in a computer, a management computer has a management database (hereinafter, referred to as a management DB).
B, the version number information is registered, and the management computer transmits the management target to one or more terminal computers, and registers the version number of the management target at the time of transmission in the management DB of the management computer. Manages the version information of the management object in the terminal computer only in the terminal computer, or has a management DB in both the management computer and the terminal computer, the management computer transmits the version information to the terminal computer, and The version information in the management DB and the version information in the management DB of the terminal computer are collated by the terminal computer, and the version information is managed in both the management computer and the terminal computer.

[0003]

However, as described above, in the method of managing the version information only by the management computer, the version information in the management DB of the management computer and the actual management target in the terminal computer are not stored. The version number cannot be checked. In the method of transmitting the version information to the terminal computer and managing the version information, the version number can be checked with the version information in the management DB of the management computer and the terminal computer. It is not possible to check the version information of the managed object and the actual version of the managed object. For this reason, for example, when only the version information is revised and the actual version of the managed object is not revised, the version information in the management DB of the management computer becomes erroneous information. there were.

[0004] In view of the above, it is necessary to check the version information of the management DB and the actual version number of the managed object in the terminal computer, and to accurately manage the version information of the managed object in the terminal computer. There has been a demand for a method of managing the version number of a managed object stored in a computer.

[0005]

According to the present invention, there is provided a method for managing the version number of a managed object stored in a computer, wherein the version number information of the managed object is transmitted from the management computer to the terminal computer and stored in the terminal computer. In the version management method for registering and managing the management object in the management database of the management computer, the management computer transmits the management target having the version information to the terminal computer, and stores the version information of the management target in the management database. Register, the terminal computer receives and stores the management object, sends the version information of the management object to the management computer, the management computer receives the version information, and the version information and the version of the management database The information is collated with the information to manage the version number information.

In the present invention, the version number information of the managed object is registered in the management DB, and the management DB and the version number of the managed object stored in the terminal computer transmitted from the management computer to the terminal computer. The information is compared with the information, and version number information is managed.

[0007]

DESCRIPTION OF THE PREFERRED EMBODIMENTS The present invention relates to a method for managing the version number of a managed object stored in a computer. As a specific example of the managed object, in this embodiment,
This will be described as a program. Also, a case will be described in which a plurality of terminal computers are installed in a district different from the district where the management computer is installed. Therefore, a case where the version numbers of the programs stored in the terminal computers in a plurality of districts are managed will be described below as an example. That is, in this embodiment, the management computer manages the version numbers of the programs of the terminal computers in a plurality of districts (hereinafter, referred to as other district computers), and obtains the version information of the management computer and the actual program version number in the other district computers. The check is performed.

FIG. 2 is a diagram showing a system configuration according to the first embodiment of the present invention. The management computer 10 in FIG. 2 and the other district computer 20 are connected by the communication line 1. The management computer 10 transmits the program 3 to the other district computer 20, records the transmitted district name and date in the management DB 2 each time the program 3 is transmitted, and manages the version number of the program 3 on the management computer 10 and the other district computer 20. I do. FIG. 3 is a diagram showing a database structure of the management DB2. As shown in FIG. 3, the database of the management DB2 includes
The program name, the version number of the program 3, the creation date when the program 3 was created, the registration date (the date when the program 3 was registered in the management DB 2), and the registration directory (the directory where the program 3 is registered) for each program 3. , The name of the district that transmitted the program 3 and the date thereof are recorded.

FIG. 4 is a diagram showing the structure of a directory for registering programs. As shown in FIG. 4, a program directory is created for each program 3 under the storage directory, a version number directory is created under the program directory, and the registered programs 3 are managed for each program 3 and version number. You. That is, the version number directory is recorded in the registration directory of FIG.
FIG. 5 is a diagram showing a data structure of version number data, and FIG. 6 is a diagram showing a method of creating version number data. The version number data includes a program name, a version number, and a creation date. The source program of program 3 (execution program after compilation) to be version-managed has (describes) version data, and executes program 3 by specifying the "vf" option and the version file name. Then, coding is performed in advance so that version number data is created in the version number file. For this reason, as shown in FIG.
If you specify the option "f" and specify a file name after that, the version data will be created in the specified version file.

FIG. 1 is a flowchart showing an outline of processing according to one embodiment, FIG. 7 is a view showing a flow when a program is registered in a management computer, and FIG. 8 is a view showing a flow when a program is transmitted to a computer in another district. FIG. 9 and FIG. 9 are diagrams showing the flow at the time of version number confirmation. 7 and 8, a thin arrow indicates a flow of processing, and a thick arrow indicates a flow of the program 3 and version number data. 1 correspond to FIGS. 7 and 8 respectively.
Next, the operation of the present embodiment will be described with reference to FIGS. 1 and 7 to 9.

(1) Program Registration (See FIGS. 1 and 7) In the management computer 10, a program 3 to be registered is specified (S1). If the specified program 3 does not exist in the management DB 2 (S2), a program directory for storing the program 3 is created in the storage directory (S3). The specified program 3 is executed by specifying an option (S4), and version number data is created (S5). If there is no version directory of the version indicated in the created version data (S6), a version directory is created (S7), and the program 3 is copied to this version directory (S8). Then, the version number indicated in the version number data in the management DB 2,
Creation date, registration date, registration directory (Program 3
Is registered (S9).

(2) Transmission to Computers in Other Districts (See FIGS. 1 and 8) The management computer 10 indicates the name of the district to which the program 3 is to be transmitted, the name of the program to be transmitted, and the version number of the program 3 to be transmitted. (S10). The program 3 of the designated version is transmitted to the computer in the designated area via the communication line 1 (S1).
1). If the designated district name does not exist in the program name designated in step S10 in the management DB 2 (S12), the district name and the update date are registered in the designated edition number (S13). If so, the district name,
The update date is deleted, and the district name and the update date are registered in the designated edition number (S14).

(3) Version number confirmation (see FIGS. 1 and 9) Then, a command to output version number data is transmitted from the management computer 10 to the other district computer 20 (S1).
5), the other district computer 20 receiving the command executes the program 3 by specifying the option "vf", creates version data, transmits this version data to the management computer 10, and the management computer issues the version number. Receiving data (S
16). The received version number data is compared with the management DB 2 to determine whether or not the program 3 in another area matches the version number in the management DB 2 (S17). If not, step S1 is performed.
Returning to step 3, the district name and the update date are registered again in the designated version number in the management DB 2, and if they match, the process is terminated.

As described above, in the present embodiment, the program 3 itself to be version-managed has version number information, so that the actual program version numbers of the management DB 2 and the other district computers 20 can be reliably checked. It can be carried out.

The order of FIG. 1 may be reversed. That is, the program may be transmitted after registration in the management DB 2.

In the above embodiment, the management target is described as the program 3, but the management target of the present invention is not limited to the program 3. For example, library data describing the symbol shape and component shape of an IC, a resistor, a capacitor, and the like are to be managed, and the library data has version number data such as a version number and a creation date as in the present invention. The present invention can be applied to version number data (version number information) of library data. Also, an example in which a plurality of computers in other districts are installed has been described, but the present invention can be applied to a single computer. The library data is included in the database.

[0017]

As described above, in the present invention, the version number information of the managed object itself is registered in the management database,
This management database is compared with the version information of the object to be managed, which is transmitted from the management computer to the terminal computer and stored in the terminal computer, and manages the version information. The version number of the managed object in the computer can be reliably checked and the version information of the managed object in the terminal computer can be accurately managed. It is not possible to check the actual version number of the object, and the inconvenience that the version numbers do not match is eliminated.

[Brief description of the drawings]

FIG. 1 is a flowchart showing an outline of processing according to an embodiment of the present invention.

FIG. 2 is a diagram illustrating a system configuration according to an embodiment of the present invention.

FIG. 3 is a diagram showing a database structure of a management DB.

FIG. 4 is a diagram showing a configuration of a directory in which a program is registered.

FIG. 5 is a diagram showing a data structure of version number data.

FIG. 6 is a diagram showing a method of creating version number data.

FIG. 7 is a diagram showing a flow when registering a program.

FIG. 8 is a diagram showing a flow when transmitting a program.

FIG. 9 is a diagram showing a flow at the time of version number confirmation.

[Explanation of symbols]

 1 communication line 2 management DB 3 program 10 management computer 20 other area computer

Claims (3)

[Claims] 1. A version management method for registering and managing version information of a managed object transmitted from a management computer to a terminal computer and stored in the terminal computer in a management database of the management computer, the management computer comprising: The management object having the version information is transmitted to the terminal computer, the version information possessed by the management object is registered in a management database, and the terminal computer receives and stores the management object, and the management object is The management computer receives the version information, compares the version information with the version information of the management database, and manages the version information. A method for managing the version number of a management target stored in a computer. 2. The management computer according to claim 1, wherein a plurality of terminal computers are installed, and the management computer registers information specifying a terminal computer to which the management object is to be transmitted and the version information in association with each other in a management database. 1. A method for managing a version number of a management target stored in a computer according to 1. 3. The method according to claim 1, wherein the object to be managed is a program or a database.