JPH07129407A - Version managing method - Google Patents

Abstract

PURPOSE:To reduce man-hour and cost for version up by performing update processing for transferring the program of the latest version from a server and a client terminal and for storing it in a program data base. CONSTITUTION:A server 30 reads version information from a version managing data base 33 and transmits it to a client terminal 35. A version decision part 36 at the client terminal 35 compares that version information with version information stored in a version managing data base 39 and decides whether a program preserved at the client terminal 35 is updated or not when the information is not matched and when it is judged not to update that program, conventional processing is performed. When it is judged to update the program, the update processing is performed to transfer the program of the latest version from the server 30 to the client terminal 35 and to store it in a program data base 38 of the client terminal 35.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a version management method for managing a system version of a terminal device in a computer system using a network by distributing a program via the network.

[0002]

2. Description of the Related Art In recent computer systems, downsizing is becoming more popular due to the demand of society. In conventional computer systems centered on mainframes, software version upgrades (updating programs such as adding functions and changing functions) were sufficient only by updating the program on the host computer, but the computer system was a server. In a so-called server / client type system composed of a client terminal and a client terminal, a system program is required for both the server and the client terminal, and it is necessary to give due consideration to their maintenance.

Therefore, in order to install or upgrade the system program, the software shipping source directly installs it on the hardware and ships it to the user, or an engineer stores the system program on a floppy disk or Bring the data cartridge to the user and install it at the user, or when the user has a specialized SE,
The method is carried out by sending the medium storing the system program to the user and installing it in the user's SE.

[0004]

The above-mentioned conventional method of maintaining a system program in a computer system of a server / client type system is used when there is a version upgrade of the system program or a bug correction / revision. Since it is not possible to install all at once at the shipping source, the user who is the shipping destination of the computer system must perform the version upgrade work of the system program. In the case of being deployed nationwide, there is a problem that enormous work man-hours are required and the cost therefor is also large. Further, when the SE is installed in the user's SE, there is a problem in that there is a concern in terms of reliability because the technical capabilities of the user's SE vary.

[0005]

The version management method of the present invention performs line processing for connecting a server and a client terminal, and inputs a user identifier and a password so that a user is qualified to use the network. It is determined whether or not, and when the system version information is transferred from the server to the clerant terminal, whether or not the program version in the system version information matches the program version held by the client terminal However, when the program version in the system version information matches the program version held by the client terminal, the conventional process of performing processing according to various menus such as mail and electronic bulletin board is performed, and the program version in the system version information is The above When the program version held by the client terminal does not match, it is judged whether or not the program held by the client terminal is updated, and when it is judged that the program held by the client terminal is not updated, the conventional processing is performed. And then
When it is determined that the program held by the client terminal is to be updated, the update process of transferring the latest version of the program from the server to the client terminal and storing the program in the program database of the client terminal is included. .

[0006]

Embodiments of the present invention will now be described with reference to the drawings.

FIG. 1 is a flow chart showing an embodiment of the present invention, FIG. 2 is a block diagram showing a relationship between a server and a client terminal in the embodiment of FIG. 1, and FIG. 3 is a diagram showing update processing in the embodiment of FIG. It is explanatory drawing which shows the content.

In the embodiment shown in FIG. 1, first, line processing for connecting the server 30 and the client terminal 35 (see FIG. 2) is performed in step 10, and then in step 11,
The user identifier (identification code: ID) and password (PW) entered by the user are checked. Entered user identifier (identification code: ID) and password (PW)
If is valid, the process proceeds to step 12 and the version determination process is performed.

In step 12, as shown in FIG. 2, the server 30 reads the version information from the version management database 33 and sends it to the version transmission section 31.
To the client terminal 35. The version determining unit 36 of the client terminal 35 compares the sent version information with the version information stored in the version management database 39, and determines that the version information stored in the version management database 39 is the latest version. If it is determined, the process proceeds to step 14 to perform the conventional process. If it is determined that the version information stored in the version management database 39 is old, the process proceeds to step 13 to perform the conventional process at step 14. Performs processing according to various menus such as emails and electronic bulletin boards.

In step 13, the user is notified that the version information currently stored in the version management database 39 of the client terminal 35 is old, and the user is urged to make a decision as to the subsequent processing. This notification is issued to the user every time when the version information sent from the server 30 is different from the version information stored in the version management database 39 of the client terminal 35, so that there is an effect of preventing forgetting to update. is there. The determination for the post-processing is either one of determination to continue the processing without updating the version and determination to update the version. If it is determined that the version is not updated, the process proceeds to step 14, and if it is determined that the version is updated, the process proceeds to step 15.

The update processing in step 15 has the following three update modes, and is processed according to the usage status of the user.

(1) Mode in which all programs are updated (2) Mode in which only new programs are updated according to the version information of the client terminal 35 (3) Mode in which the user updates only specific programs These modes For example, use the mode (1) when most programs are to be updated, when a transfer error occurs during the update, or when you want to store them in another directory all together. To do. If you want to finish updating the target program in a short time, use mode (2). If a specific program is destroyed or erased for some reason during operation,
The mode of (3) is used.

The processing in the mode (1) is performed by the server 30.
Transmits a list of all programs from the list to the client terminal 35, and the client terminal 35 issues a program transmission request in order from the list and stores the program received from the server 30 in the client program database 38. To do. When the storage of the requested program ends, as shown in FIG. 3, the client side version management table 55 stored in the version management database 39 of the client terminal 35.
The server side version management table 5 in which the contents of a are stored in the version management database 33 of the server 30.
It rewrites the contents of No. 1 and updates the client side version management table 55b.

In the processing in the mode (2), the client terminal 35 transmits the update date / time information to the server 30, and the server 30 selects only the program newer than the information based on the update date / time information and lists it. Is transmitted to the client terminal 35. The client terminal 35 issues a program transmission request in order from the list and stores the program received from the server 30 in the client program database 38 accordingly. When the storage of the requested program is completed, the client side version control table is updated as in the case of (1).

In the process in the mode (3), the client terminal 35 transmits a request for transmitting a specific program to the server 30, receives the program, and stores it in the client program database 38. In this case, the client side version control table is not updated.

When the updating process in step 15 is completed, the process proceeds to step 16 to make a verify decision.

The verification judgment in step 16 is as follows.
In step 15, a message for prompting the user to select whether or not to perform an operation for checking whether or not the program that has undergone the update processing is normal is output to prompt the determination. When it is determined that the verification is performed, the process proceeds to step 17, and when it is determined that the verification is not performed, step 17 is skipped and the process proceeds to step 18.

In step 17, the program updated in step 15 is received again from the server 30, and the client program database 3 is received first.
Compare with the program stored in 8. This work is performed based on the list used in step 15.
When the processing in step 17 ends, step 18
Move to.

At step 18, a message for prompting the user to select whether or not to perform the conventional processing by the updated new program is output to prompt the judgment. When it is determined that the conventional process is performed, the process proceeds to step 14, and when it is determined that the conventional process is not performed, the process proceeds to step 19 to end the process.

In step 19, line processing for disconnecting the connection between the server 30 and the client terminal 35 is performed, and a series of processing is ended.

[0021]

As described above, according to the version management method of the present invention, the system version information is transferred from the server to the clerant terminal, and the program version in the system version information is different from the program version held by the client terminal. If the program version sent from the server does not match the program version held by the client terminal, it is judged whether or not the program held by the client terminal is updated, and if it is judged that the program version is updated Performs the update process of transferring the latest version of the program from the server to the client terminal and storing it in the program database of the client terminal. It has the effect that it becomes possible, thus there is an effect that can be saved and working steps for upgrading and cost. Further, since it is not necessary to have the SE installed in the user's SE, the reliability can be improved.

[Brief description of drawings]

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

FIG. 2 is a block diagram showing a relationship between a server and a client terminal in the embodiment of FIG.

FIG. 3 is an explanatory diagram showing the contents of update processing in the embodiment of FIG.

[Explanation of symbols]

10 to 19 steps 30 server 31 version transmission unit 33/39 version management database 34/38 client program database 35 client terminal 36 version determination unit 51 server side version management table 55a / 55b client side version management table

Claims (1)

[Claims] 1. A line process for connecting a server and a client terminal is performed, and a user identifier and a password are input to determine whether or not a user has a qualification to use the network. When the system version information is transferred to the terminal, it is determined whether the program version in the system version information matches the program version held by the client terminal, and the program version in the system version information is the When it matches the program version held by the client terminal, the conventional processing of performing processing according to various menus such as mail and electronic bulletin board is performed, and the program version in the system version information is the program version held by the client terminal. When it is determined that the program held by the client terminal is not updated, the conventional process is performed when it is determined that the program held by the client terminal is not updated. When it is determined that the program held by the client is to be updated, it includes an update process of transferring the latest version of the program from the server to the client terminal and storing the program in the program database of the client terminal. Version control method.