JPH10269062A - Version management method of terminal-side user program in CSS system - Google Patents

Abstract

(57) [Summary] [PROBLEMS] In a CSS system, it automatically checks whether the version of a user program, a form, and screen information distributed to a terminal side is the latest generation. Always guarantee consistency with the program. Also, if the latest generation is not used, the system automatically replaces the latest generation with the latest generation, and further groups the modules to be version-controlled according to the system environment, and reduces the number of modules to easily manage the version information. A mainframe-side version management table that manages version information of the latest generation, a terminal-side version management table that manages the current version, a function for checking matching of the tables, and a terminal-side user -It is achieved by having a function to replace the program with the latest generation when it is not the latest generation.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a version management system for a user program, a form, and screen information on a terminal in a CSS system.

[0002]

2. Description of the Related Art Conventionally, in an environment of CSS system, application programs such as terminal-side program products have version information, and version management can be performed centrally. However, since the terminal-side user program does not have version information, version management in a human system by a terminal-side system administrator is generally performed.

[0003]

In the above prior art, no consideration is given to version management for a user program on the terminal side. For example, the mainframe and the terminal are connected online, and the user
In a CSS-based environment in which a program exists and a mainframe-side user program and a terminal-side user program perform processing while associating with each other, version management of the terminal-side user program is performed by the terminal. The version of the mainframe user program and the terminal user program may be inconsistent for some reason during the version upgrade because the system program is performed by the system administrator on the side. However, there is a problem in that the processing does not match and an unauthorized process is performed.

[0004] An object of the present invention is to improve the above-mentioned problems by having version information of the user program on the mainframe side and the terminal side, transmitting the version information on the terminal side to the mainframe when the terminal is started, A check is made against the version information on the mainframe, and if they do not match, the business process is not continued and the user
An object of the present invention is to provide a method for performing a process of replacing a program with the latest generation.

[0005]

In order to achieve the above object, a version control method for a user program according to the present invention comprises a version control table on a mainframe side for managing version information of a latest generation, and a current version control table on a terminal side. This is achieved by having a version management table for managing versions, a function of checking the matching of each table, and a function of replacing the user program on the terminal side with the latest generation when the user program is not the latest generation.

[0006]

FIG. 1 is a system configuration diagram showing the configuration of an embodiment of the present invention. 1 is a main frame, and 2 is a version management table file storing the latest version information. Reference numeral 3 denotes a terminal device, and reference numeral 6 denotes a version management table file storing version information on the terminal side.

The outline of the operation will be described below with reference to FIG. When upgrading the terminal-side user program, the contents of the user program file 5 are transmitted to the terminal-side user program file 4 of the terminal device 3 via the communication line 7 by the transmission program 9. At this time, the contents of the version management table file 2 are also transmitted to the terminal-side version management table file 6 of the terminal device 3.

As a pre-process for upgrading the user program on the terminal side, the user program to be upgraded is stored in the user program file 5 and the corresponding version information is also stored in the version management table file 2. Is stored.

When the terminal device 3 is activated, a session with the mainframe 1 is established, and at the same time, the contents of the version management table file 4 are transmitted to the mainframe 1 via the communication line 7 by the transmission program 10. The mainframe 1 that has received the contents of the version management table file 4 uses the version check program 8
A check is made against the contents of the version management table file 2. If the contents are the same, it can be said that the version on the terminal side is the latest generation, so that the processing is continued, and thereafter the system performs the business processing or the like originally intended.
If the contents do not match, it can be said that the user program on the terminal side is an old version, so control is passed to the transmission program 9 and the latest generation user program and the version management table file are transmitted to the terminal side.

FIG. 2 shows a version management table file 2
And FIG. 4 are diagrams showing record formats. Reference numeral 21 denotes a type code assigned to a group of objects whose version is to be managed and assigned to the group. For example, when two subsystems exist on the terminal side, the group of the user program of one subsystem is set to 'SUBA', and the other group is set to 'SUBB'. Also, when distributing forms and screen information to the terminal side, the screen information groups are managed by grouping the form information groups as "MAPA" and the form information groups as "MAPB". In this way, by grouping and reducing the number of modules whose version is to be managed, it is possible to reduce the performance degradation at the time of matching check and the load on the human system that manages the contents of the version management table file itself. The "type code" is a key item for matching check.

Reference numeral 22 denotes version information. By comparing the contents, it is determined whether the user program on the terminal side is the latest generation.

FIG. 3 is a flow chart showing the flow of processing for transmitting a user program and version management information from the mainframe 1 to the terminal device 3.

The latest version of the user program to be transmitted to the terminal is registered in the user program file 5 (step 31). The version information of the user program registered in step 31 is registered in the version management table file 2 (step 32). Step 3
The user program registered in steps 1 and 32 and the version management information are transmitted to the terminal device 3 (step 33).
The terminal device 3 receives the user program and the version management information transmitted from the mainframe 1 (steps 34 and 35). If the transmission has not been completed normally, the processing from step 33 is repeated. If the transmission has been completed normally, the user program is stored in the user program file 6 (step 36), and the version management information is stored in the version management table file 4 (step 37).

FIGS. 4 and 5 show the flow of a process for checking whether the version of the user program of the terminal device 3 is the latest generation and a flow of a transmission process from the mainframe 1 to the terminal device 3 when the version is not the latest generation. It is a flowchart.

The power of the terminal device 3 is turned on by the terminal operator and the terminal device is activated (step 41). The terminal device 3 reads the contents of the version management table file 4 (step 42) and transmits it to the mainframe 1 (step 4).
3). The mainframe 1 receives the version management information transmitted from the terminal device 3 (step 44), and stores the contents of the version management table file 2 and the 'type code'.
Is used as a key to check the matching of 'version information' (step 45). As a result of the matching, if they match (the latest generation), this processing is terminated, and control is passed to the program that performs the original business processing. In the case of inconsistency (not the latest generation), the user program and the version management information are transmitted to the terminal device 3 (step 4).
7), the terminal device 3 receives it (steps 48 and 4).
9). If the transmission is not completed normally, step 47
Is repeated. If the transmission was successful,
The user program is stored in the user program file 6 (step 50), and the version management information is stored in the version management table file 4 (step 51).

[0016]

As described above, according to the present invention, C
In the SS system, since the version of the user program, form, and screen information distributed to the terminal is automatically checked for the latest generation, consistency with the user program on the mainframe is always maintained. Dripping. This allows
The content of the processing result by cooperation between the terminal side and the mainframe side can be guaranteed. In addition, if it is not the latest generation, it is automatically replaced with the latest generation, so that efficient and reliable version management can be performed without the intervention of human work. Furthermore,
Since the modules to be version-controlled can be grouped and reduced according to the system environment, version information can be easily managed.

[Brief description of the drawings]

FIG. 1 is a system configuration diagram in version management of a terminal-side user program according to the present invention.

FIG. 2 is a data configuration diagram showing a record format of a version management table file.

FIG. 3 is a flowchart showing a flow of processing for transmitting a user program and version management information from a mainframe to a terminal device.

FIG. 4 is a flowchart illustrating a flow of a process of checking whether the version of a user program of the terminal device is the latest generation, and a flow of a transmission process from the mainframe to the terminal device when the version is not the latest generation.

FIG. 5 is a flowchart showing a flow of a process of checking whether the version of the user program of the terminal device is the latest generation, and a flow of a transmission process from the mainframe to the terminal device when the version is not the latest generation.

[Explanation of symbols]

DESCRIPTION OF SYMBOLS 1 ... Mainframe, 2 ... Mainframe side version management table file, 3 ... Terminal device, 4 ... Terminal side version management table file, 5 ... Mainframe side user program file, 6 ... Terminal side user program File, 7: communication line, 8: program for checking the version of the user program on the mainframe side and terminal side, 9 ... transmission program on the mainframe side, 10 ... transmission program on the terminal side.

Claims (1)

[Claims] In a CSS system, a mainframe has a version management table for managing version information of the latest generation, and a terminal has a version management table for managing a current version.
It includes a step of distributing programs, forms, and screen information, a step of checking whether the version is the latest generation, and a step of replacing the version with the latest generation when the version is not the latest generation. A method that can be managed.