JPH0728633A - Method and device for program group generation management, program update processing method, and decentralized processing system - Google Patents

Abstract

PURPOSE:To provide an automated generation management system for the program group of a large-scale system which changes the generation of the program group with high efficiency and high reliability. CONSTITUTION:A generation management control means 4 refers to a history management table 5 wherein the mutual relation between a system generation and a program generation is defined, and generates a file generation or program registration information generation different from current generation system information 1 by actuating a file registration management means 3 when the change destination system generation is registered in history information 2, thereby substituting the generated generation for the current generation system information 1. When the change destination system generation is an unregistered new generation, it is registered in the current generation system information 1 and history information is generated by the means 3 and registered. For a generation change of only program registration information, a program update means 6 updates only files and programs which need to be registered again.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a program group management system including a large number of files, and more particularly to a generation management method for managing system generations and file generations in a unified manner and a method for updating a generation-changed file. .

[0002]

2. Description of the Related Art Software generation (version) management is generally performed on a file-by-file basis, and history information is reduced by managing difference information between generations.

In a large-scale system such as a network system in which a large number of computers are connected, a large number of files are registered, and some files are updated or combinations of used files, that is, software system changes are often performed. Be seen.

However, since the correspondence between the file generation and the system generation is not managed only by the history information in file units, the generation change is left to the manual processing of the user.

As a countermeasure against this, there is a method of updating all files in synchronization with a change in system generation. However, even source files that have not changed are unconditionally regenerated and reregistered, and further update processing is executed. To be done. Therefore, in a system having a large number of files, it is difficult to apply it to a full operation system in which the overhead of generation change is large and the maintenance stop time is short.

As a method for efficiently changing generations, version management of files configured for each system generation is performed, and when installing a new system, the same files as those in the old system are passed, and different files are updated by the user. A management method for making an inquiry is proposed in Japanese Patent Laid-Open No. 2-41523.

On the other hand, the update of the program accompanying the generation change is started by the change of the source file, and the files and programs that need to be re-registered due to the difference in the registration date of each stage of the object, the execution file and the execution program. I have decided.

[0008]

However, the above-mentioned proposal is limited to installation, and the system configuration of the current generation and the generation to be changed to be reconfigured are not managed in synchronization, so that the user's labor for changing the generation is reduced. However, there is a problem in reliability.

Further, in the conventional update method, the update is not executed only by changing the program registration information. Therefore, for example, when there is a change in the compilation information, the user needs to re-instruct the corresponding object file to be re-registered. For this reason, in a large-scale system, the burden on the user is large, and this also causes a decrease in reliability due to omission of instructions.

A first object of the present invention is to provide a program that overcomes the drawbacks of the prior art and manages the system generation including the change-destination generation and the file generation in a unified manner to reduce the automation of generation change and the processing overhead. It is to provide a group generation management method.

A second object of the present invention is to provide a program update method for automating re-registration of a program due to a change in program registration information.

A third object of the present invention is to provide a distributed processing system in which the system of other computers in the system can be changed all at once by one system change information distributed from the master computer.

Other objects of the present invention will be clarified through the following description.

[0014]

[Means for Solving the Problems] The first object is to manage a group of programs that manages system changes by registering history information of programs that compose the system of the current generation and generations (versions) of each program. In the method, a mutual relationship between the system of the current generation or a plurality of programs registered in the history information and a plurality of systems is defined in advance by an ID of a program generation, and the system is changed from the current generation according to a system change request. The previous systems are compared for each program based on the mutual relationship, and when the program generation IDs of the two do not match, a changed program generation is generated from the history information, and the generated program is generated as the program of the current generation. This is achieved by replacing the corresponding program in the group and changing the generation of the system.

The second object corresponds to a source file in a program update processing method for re-registering an object file, an executable file and an executable program in this order when the source file is updated. In the case where only the program registration information to be changed is changed, it can be achieved by re-registering the items in the order of re-registration and those affected by the change.

A third object of the present invention is that in a distributed processing system in which a master computer having a generation management function and another computer group not having a generation management function are connected via a network, the master computer has a plurality of source files and their programs. Current generation system information storage means for storing registration information, and system change information for updating the source file and / or program registration information and including at least one of the updated source file or program registration information or file name to be deleted A program registration management means for generating the system change information, a transmitting means for distributing the system change information to another computer, the other computer receiving means for receiving the system change information from the master computer, and its own current generation system. Information storage means and received source file or program registration It is achieved by providing a program registration management means for updating the current generation system information storage means of said self accordance with information or the file name to be deleted.

[0017]

According to the first aspect of the invention, the file generation IDs of the current generation and the change destination generation of the generation management table can be instantly compared,
When they match, the generation of the file can be omitted, and when they do not match, the change destination file is generated based on the history information. Therefore, generation change including file generation can be automated simply by instructing the change destination generation ID, and Overhead can be significantly reduced.

According to the second invention, when only the program registration information is changed without changing the source file, the changed contents are, for example, an object file if the information is compilation information and an execution file if the information is link load information. If it is the execution program registration information, the program update process is executed with each execution program as the re-registration start position.

As a result, it is possible to realize a completely automatic program update process, save the labor of updating the date of the corresponding source file due to the change check of the program registration information, which has been conventionally performed by the user, and re-register error due to omission of check. Can also be prevented. Furthermore, it is possible to reduce the interruption of the computer for the generation change and improve the processing efficiency of online business.

According to the third aspect of the invention, the system change information is transmitted from the master computer only once, and the other computers in the system do not have a special function for changing the generation, and the system can be used for a short time. Online generation change can be realized by interruption, and the operation rate of the distributed processing system can be improved.

[0021]

Embodiments of the present invention will now be described in detail with reference to the drawings. FIG. 2 shows the configuration of a distributed system suitable for changing the generation of a program group according to the present invention. A plurality of computers 101a to 101d are connected to the network, and the program group of each computer and its change are stored in the master computer 101a.
Is managed by.

The master computer 101a reads out registered software such as programs and data stored in the magnetic disk (MD) 109 or the like through the input / output unit 107, and combines the currently used programs or the like (hereinafter, referred to as a current combination). Referred to as a generation system).
Managed by the communication device 1
It is transmitted to each computer via 02. It should be noted that the user instructs or inputs from the terminal 110 the generation change and the new registration of the system.

FIG. 1 is a functional block diagram of the generation management device 104 provided in the master computer 101a. The solid line shows the control information and the dotted line shows the data flow. The current-generation system information storage means 1 stores a source file group 1a that constitutes the current-generation application software and its program registration information 1b. The history information storage unit 2 stores source file history information 2a between generations (versions) and registration information history information 2b for each registered file for each file and program registration information in order of generation. These storage means 1 and 2 have a storage area on the magnetic disk 109.

The file registration management means 3 registers, updates, and deletes the current generation storage means 1 and the history information storage means 2, and obtains the difference information of the internal data between generations of files and program registration information, History information 2a, 2b is created. In addition, the desired current-generation file group 1 based on this history information
a and the program registration information 1b are generated and registered in the storage means 1 and files unnecessary for the current generation are deleted.

When newly registering, the program updating means 6 sequentially registers the object file in the storage means 7, the execution format file in the storage means 8 and the execution program in the memory 9 (main memory) based on the source file. To do. The storage unit 7 and the storage unit 8 each have a storage area on the magnetic disk 109.

On the other hand, when updating based on the updated source file, it is executed in a chained manner by comparing old and new of the registration dates of the files / programs at each stage. That is, when the registration date of the source file 1a is updated, the date of the object file 1a 'becomes older,
The source file 1a is compiled and the object file 1a 'is reregistered. Then, since the date of the executable file 1a ″ stored as a library becomes old, the changed object file 1a ′ is link-loaded to re-register the executable file 1a ″. As a result, the registration date of the execution program 1a becomes old, and some or all programs of the updated execution format file 1a ″ are re-registered.

The generation management control means 4 changes the generation of the system while referring to the generation management table 5 shown in FIG. The generation management table 5 includes system generation IDs (SYS1, SYS2, ...) In system units and file generation IDs (V1, V2, V3, file units (A to F) registered in the history information storage unit 2). ...) is registered, and is used to synchronize the files that compose the system of each generation.

In FIG. 3, the symbol ".fwdarw." Indicates that the file generation has not changed in the relevant system generation, and the same file generation as the previous system generation is adopted. The symbol "-" means
It indicates that the file is not used in the system generation. For example, although the file C is registered in the history information 2a, the SYS5 is used for the first time.

The SYS 6 in FIG. 2B is blank in FIG. 1A, and this system is a new generation system including files or fill generations not registered in the history information storage means 2. The “category” item indicates the current status of the system generation, and CUR is the current generation system, C
HG is an identifier representing a change-to generation system.

The generation management table 5 also defines the correspondence between the system generation and the program registration information generation (V1, V2, ...). 4A to 4D show a program registration information table 51 defined as ancillary information of the generation management table 5, which shows a compile option, a link load option, and a program load information for an arbitrary program, for example, program A. The example of an execution program option and the whole deletion is shown.

In order to simplify the explanation, the programs corresponding to the source files of FIG. 3 and the program information of FIG. 4, such as file A and program A, are one-to-one below.
It corresponds to, but is not limited to. For example, when the program A is generated from a plurality of files A to C, it is well known that the program update process is performed based on the program configuration information, and it is also applicable in this embodiment.

Next, the management of the program group in the generation management control means 4 accompanying the system generation change will be described with reference to FIGS.
Will be described with reference to. It should be noted that the system generation change here is generation of history information 2 such as a source file constituting the change destination system and registration in the current generation system information 1, and further, source file or program registration updated by the generation change. This is re-registration of an executable file and an executable program which are dynamic information and updated based on the information.

FIG. 5 is a processing flow showing an outline of generation management. In step S10, the system change request is accepted from the terminal 110 by the change-destination system generation ID,
In step S20, it is determined whether the received system generation ID is registered in the generation management table 5. In the case of a generation change request to the registered generation ID, for example, SYS5, CHG is set in SYS5 of the generation management table 5, and the generation change process in step S30 described later is performed.

On the other hand, if the unregistered generation ID SYS6 is accepted in steps S10 to 20, the ID of the SYS6 is added to the generation management table 5 in step S40 to set the category to CHG, and the unregistered file is unregistered. The file registration means 3 receives an input from the terminal 110.
To register in the current generation system information storage means 1. In the example of FIG. 3B, V5 of file A, V4 of file D, V1 of file F and V3 of registration information are newly registered. After that, in the new generation registration processing S50, the history information described later is registered.

After the generation change process, step S described later
Program update processing is performed in step 60, and in step S70, the generation management table 5 as shown in FIG.
Is updated, and the new generation division CHG is changed to the current generation division CU.
The file generation ID is changed to R, each file generation ID that constitutes the new generation system SYS6 is registered, and is used for subsequent management. In addition,
The generation management table 5 is updated in steps S30 and S50.
You may go in.

FIG. 6 is a flowchart showing the generation changing process of step S30 described above. Here, from the current system generation SYS4 shown in FIG.
An example of changing the generation to YS5 will be described.

In step S301, the file generation ID of SYS4 and the file generation ID of SYS5 are compared for each file from file A to registration information by referring to the generation management table 5. Since the file ID generations of the files A and F are the same, the subsequent generation change processing is passed.

For other files whose file generation IDs do not match, it is determined in step S302 whether or not there is the file in the changed generation. In the case of "none", that is, SYS
The file E which is in 4 but not in SYS5 is in step S3.
At 05, the file registration management means 3 is operated to delete from the file group 1a of the storage means 1.

On the other hand, regarding the files B and D and the registration information which are determined to be “present” in step S302, the file registration management means 3 is instructed to generate the file generation of SYS5 from the history information 2a and 2b, and the storage means 1 The file D of the current generation file group 1a and the registration information 1b are replaced. Similarly, the file C (V1) determined to be “present” is not used in the current generation SYS4, but is registered in the history information 2a, so it is generated from the history information 2a and added to the current generation file group 1a. To be done.

The above process is repeated for each file until all files of SYS4 and SYS5 are completed (step S
306), the update of the current generation system information 1 ends. The generation management table 5 may be updated immediately after this.

According to this, the generation change from the current generation to the change-destination system generation is automated, and the processing of file generation and replacement is minimized, so that the overhead in the generation change can be reduced.

Next, the new generation registration processing of step S50 described above will be described with reference to the flowchart of FIG. It is assumed that the current generation system information 1 has been updated to each file of SYS5 to SYS6 shown in FIG. 3B in step S40.

First, in step S500, the presence or absence of history information is checked for each file of the current generation system information 1 (SYS6). If there is history information, step S5
At 01, the latest generation file is generated from the history information 2a and 2b. Next, in step S502, the latest generation file and the corresponding file of the current generation system information are collated. The collation is performed on the internal data of both files. When both files match (files B and C), the history information registration process is passed in step S503.

When the data in both files do not match (files A, D, G and registration information), the latest file ID of each file is updated (S504), and history information based on the difference between the internal data of both files is updated. Created by the file registration management means 3 and registered in the history information storage means 2 (S
505). In addition, “→” is set in the corresponding file column of SYS6 of the generation management table 5 when the data is not changed, a new file ID is set when the data is changed (S506), and then the latest generation file generated in S501 is set. It is deleted (S507). The file G is new registration information, and all the data of V1 is registered in the history information.

According to this, since registration of history information is automated, highly reliable version management is possible even in the case of a system having a large number of files. Also, the update overhead can be reduced.

In this way, the source file of the current generation system information 1 whose generation has been changed or registered for the new generation has its registration date updated at the same time. Therefore, the update process of step S60 causes the dynamic file or program of each stage to be updated. Will be re-registered.

By the way, in the generation changing process described above, the program registration information may be changed although the source file is not changed. Step S60 includes an update process that is automatically executed even in such a case, and the program registration information from the current generation SYS4 to the change destination generation SYS5 shown in FIG. 4 is taken as an example and according to the flowchart of FIG. explain. The process of step S613 shown in the figure corresponds to the conventional program update, and S600 to S612 are the pre-processes thereof.

First, in step S600, the destination SYS is changed.
The generation management table 5 is checked to see if the registration information ID 5 has been changed (changed and deleted). Since V1 has been changed to V2, the process proceeds to step S601, and a check is made in Table 5 to see whether the target source program (here, files correspond to programs one-to-one) has been changed. If the source program, that is, the source file has been changed, the process proceeds to step S613 and the normal update process is performed.

On the other hand, in the case of the file A shown in FIG.
Since there is no generation change between 4 and SYS, the following processing is performed in this case. In step S602, the program registration information management table 51 is referred to, and it is determined whether the source program A has all the registration information deleted. Figure 4 (a)
(D) shows an example of changing the program registration information for the program A, and (d) is an example of all deletion. In this case, in steps S603 to S605, the file / program at each stage of the file A (V4) of SYS4 is deleted, and unnecessary information remaining in each storage unit is removed.

Next, in step S606, it is checked whether the compile option is changed. If the optimize level is changed as in the example of FIG. 4A, the registration date of the source file A is updated in step S607. .
If the compile information is not changed, it is checked in step S608 whether the link load option is changed. If the compile information is changed (including deletion) as shown in FIG. 7B, the object file date is updated in step S609. . Next, in step S610, the execution program registration option is checked for changes, and if there is a change in execution priority as shown in FIG. 7C, the execution date file registration date is updated.

When the above processing is completed for all programs of SYS5 (S612), normal program update (S613) is executed. In the case of FIG. 7A, the date of the source file A has been updated, so S
It is compared with the date of the object file A registered in YS4. As a result, since the date of the source file is newer, the object file A compiled at the changed optimization level 2 is re-registered, and thereafter, re-registration of the execution format file and the execution program is also chained.

In the case of FIG. 9B, since the object file date has been updated, based on the object file A registered in SYS4, re-registration of the execution format file according to the standard link load specification and re-execution of the execution program are performed. Registration is performed.

In the case of FIG. 6C, since the registration date of the execution format file has been updated, the object file A and the execution format file A remain SYS4, and the execution format file A to the execution program A with the priority 60. Will be re-registered.

FIG. 9 shows a modification of the above-described S606 to S611, which corresponds to S607, S609, and S611.
In each of 07A, S609A, and S611A, instead of updating the date, the date of the file or program one step lower is deleted. With this, the update process of S613 becomes the same as that of FIG.

FIG. 10 is a diagram conceptually explaining the program update processing based on the program registration information, including the execution means. The compiler 61, the linker loader 62, and the process registration means 63 (one function of the control device 106).
Is activated by an instruction from the program update means 6.

According to the program update processing of this embodiment, a predetermined preprocessing based on the program registration information is executed prior to the execution of the normal update, so that even if only the program registration information is changed or deleted, Necessary update processing will be performed automatically. This saves a great deal of time and effort conventionally required by the user, and improves the reliability of the change system. further,
Since the interruption of work due to generation change processing can be greatly shortened, the operating rate of the continuous operation system can be improved by promptly restarting online work.

Next, a second embodiment of the present invention for changing the system of another computer from the master computer of the distributed system will be described.

FIG. 11 shows the configuration of the distributed system and the display screen 20 of the terminal 110 connected to the master computer 101a.
1 is shown. The in-system generation information 202 being displayed indicates the system generation, computer type, and management system generation for each computer (name) in the system. There are two types of computers in this example, TCS and HBS, and the same type has the same software configuration.
01a) and the HBS are managed by the node E (101e) serving as a master computer.

The master computer 101a generates information necessary for changing the system of another computer along with its own generation change described in the first embodiment and collects it in the system change information storage means 11 shown in FIG. This information is distributed to other nodes 101b to 101d of the same type in the system to change the system of each computer, and FIG. 12 shows its schematic flow.

When the system change request from the terminal 110 is accepted in step S701, the generation management control means 4
Is the current in-system generation information 20 in step S702.
1 is collected and displayed (S703). On this screen 201, an operation command input screen for the changed computer type 203 and the changed system generation 204 is displayed.
The user's instruction is accepted in 04 and S705. In the following, a case where the type is TCS and the system generation is SYS5 will be described as an example, and the system generation change of the master 101a and the other nodes 101b to 101d will be described as an example.

In step S706, the system change information is collected and stored in the storage means 11. When this collection ends (master change ends), steps S707 to S70
At 9, the change information is sequentially delivered to the nodes B, C and D to make a system change request. This delivery is performed later by the information delivery / transmission / reception means 10 editing the system change information into a predetermined data format according to an instruction from the generation management control means 4.

FIG. 13 shows the process of generating and collecting the system change information 11 in the generation change process according to step S706. This is the replacement of the generated file with the current generation information 1 in step S304 of the generation change process of FIG.
This is executed in response to the deletion of the current generation file 305.
That is, the names of generated files and generated files are transferred to the system change information storage means 11 in steps S304A and B, and the names of deleted files are transferred to step S305A.
These processes are performed by the file registration management means 3 according to the instructions of the generation management means 4.

FIG. 14 shows a process of collecting the system change information 11 in the program update process. That is, steps S607, S609 and S in FIG.
Corresponding to the date update processing of 611, the compile point, the link load point, and the program registration point, which are the starting points of the program update, are stored as the program update information 11b.

FIG. 15 shows the data format of the system change information. (A) is the transfer file name information 11a,
(B) shows the program update information 11b.

The system change information 11 is distributed by the information distribution transmitting / receiving means 10 to another computer via the communication device 102. The other computer that is not the master takes the received change information into the system change information storage means 11 by its own information distribution transmission / reception means 10.

Further, the file registration management means 3 updates the current generation system information storage means 1 in response to a system change request from the master. That is, the generated file name 11a of the change information 11 and its source file and registration information 1
1c is replaced or added to 1a and 1b of the current generation system information, and the current generation information 1a is added according to the deleted file name 11a.
Delete unnecessary source files from. Furthermore, regarding the file / program corresponding to the program update information 1b, from the designated update start position,
Re-registration by the program update means 6 is executed.

In the above example, the computer type to be changed is TC.
Although it is one type of S, a plurality of types of system changes can be continuously executed. The master computer that manages generations in the system is not fixed and can be replaced by another computer. FIG. 16 shows a processing flow in such a case.

When each computer receives the changed computer type from its own terminal or network, step S8 is performed.
In 01, it is determined whether the type is the same as the own computer. If they are the same, it is determined in S802 whether or not the own computer is the master.
If it is not the master, a system change request is made to the master computer in S803. If it is a master computer, S804 ~
In step S806, system change information is generated and collected, and distributed to other computers to make a system change request. This is repeated until all computer types subject to system change are completed (S807).

According to this embodiment, it is only necessary to generate change information once for multiple computers operating in the same system generation.
It can process generation changes in the system at high speed with little overhead. Moreover, except for the master computer, the current generation of program groups need only be managed, and history information management is unnecessary.

If the online system changes are frequent and it is desired to reduce the amount of transfer information between computers, the computers other than the master may be provided with history information and the change information 11 may be sent as difference information. . Further, it is possible to install the information necessary for system change into another computer by using an external storage device, regardless of the network.

[0071]

According to the program group generation management method of the present invention, the generation change of the system can be automated only by instructing the change destination generation, and the file is generated only when the file generations of the current generation and the change destination generation do not match. Is generated, the processing overhead can be reduced.

According to the program update method of the present invention, even when only the program registration information is changed, the program update can be completely automatically processed.
The labor and time of the user can be greatly saved, and the reliability of program group management can be improved.

According to the distributed processing system of the present invention, generation change of a large number of computers can be executed by generating change information once, so that interruption of the computer for generation change is short and processing efficiency of online work is improved. it can.

[Brief description of drawings]

FIG. 1 is a functional block diagram showing a configuration of a generation management device that is an embodiment of the present invention.

FIG. 2 is a configuration diagram of a distributed processing system as an application example of the present invention.

FIG. 3 is a generation management table that defines a mutual relationship between a system generation and a file generation.

FIG. 4 is a program registration information table defining system generation program registration information.

FIG. 5 is a general flowchart showing an outline of program group generation management.

FIG. 6 is a flowchart showing details of generation change processing.

FIG. 7 is a flowchart showing details of new generation registration processing.

FIG. 8 is a flowchart showing details of program update processing.

FIG. 9 is a flowchart showing another example of the program update process.

FIG. 10 is an explanatory diagram illustrating a configuration of a program update processing unit.

FIG. 11 is a screen showing in-system generation information of the distributed processing system according to the second embodiment of this invention.

FIG. 12 is a flowchart showing the processing of the master computer in changing the system of another computer.

FIG. 13 is a flowchart showing collection of transfer files of system change information.

FIG. 14 is a flowchart showing collection of program update information of system change information.

FIG. 15 is a data format showing the configuration of system change information.

FIG. 16 is a flowchart showing another processing example of system change.

[Explanation of sign]

1 ... Current generation system information storage means, 2 ... History information storage means, 3 ... File registration management means, 4 ... Generation management control means, 5 ... Generation management table, 6 ... Program update means, 7 ... Object file storage means, 8 ... execution format file storage means, 9 ... execution program storage means,
10 ... System change information transmission / reception means, 11 ... System change information storage means, 101 ... Calculator, 102 ... Communication device, 1
03 ... Network, 104 ... Generation management device, 106 ...
Control device, 107 ... Input / output means, 109 ... Magnetic disk, 110 ... Terminal device, 201 ... Display screen of terminal device.

 ─────────────────────────────────────────────────── ─── Continuation of the front page (72) Inventor Naoki Miwa 5-2-1 Omika-cho, Hitachi-shi, Ibaraki Hitachi Ltd. Omika factory

Claims (13)

[Claims] 1. A program group generation management method for registering a program group constituting a system of the current generation and generation history information for each program, and managing a system change, wherein the system is registered in the current generation system or the history information. The relationship between multiple programs and multiple systems
It is defined in advance by the ID of the program generation, and according to the system change request, the current generation and the system of the change destination are compared for each program based on the mutual relationship. A program group generation management method, wherein a program generation is generated from the history information, and the generated program is replaced with a corresponding program in the program group of the current generation to change the generation of the system. 2. The program according to claim 1, wherein the program is a source file, and an object file obtained by compiling the source file updated by the replacement, an executable file obtained by link-loading the object file, and an on-memory file A program group generation management method characterized in that update processing is performed by sequentially re-registering the execution programs stored in. 3. The method according to claim 1, wherein when the system of the change destination includes a new generation program that is not registered in the history information, a latest program of the history information corresponding to the new generation program is generated, A program group generation management method characterized in that a new generation program is collated with the latest program to generate new history information. 4. A program group generation management device for managing generation change of each program and generation change of a system composed of a combination of a plurality of programs, and history information storage means for storing history information of each program. A current generation system information storage means for storing a program group consisting of a plurality of source files constituting the current generation system, and a predetermined source file generated from predetermined history information, and registered in the current generation system information storage means or According to the file registration management means to be replaced, the generation management table that defines the mutual relationship between the program and the system registered in the history information by the program generation ID, and the change request from the input means that indicates the change destination system. , The current generation and the system generation of the change destination are referenced by referring to the generation management table. Generation management control for operating the file history management means to generate a change-destination program generation from the history information and replacing the program generation ID of the current generation system with the corresponding program of the current generation system. A program group generation management device comprising: 5. The program registration information of the source file is registered in the current generation system information storage means, and the history information regarding the program registration information of each program generation is stored in the history information storage means. , The generation management table shows the mutual relationship between the system generation and the program registration information, the program registration information generation ID
A program group generation management device characterized by being defined by. 6. The object file, the execution format file, or the execution program according to claim 5, when the program registration information registered in the current generation system information storage means is changed. A program group generation management device comprising program update processing means for starting re-registration from the program group generation management device. 7. A program update processing method for re-registering an object file, an executable file, and an execution program in the order of the program registration information when the source file is updated, and only the program registration information corresponding to the source file. The method for updating a program is characterized in that, when the number is changed, the items in the order of re-registration, and the items affected by the change are re-registered. 8. The program registration information according to claim 7, wherein the program registration information includes at least one of a compile option, a link load option, and an execution program option. When the compile option is changed, the program is reregistered from the object file and the link load is performed. A program update processing method characterized in that when an option is changed, it is re-registered from an executable file, and when an execution program option is changed, an execution program is re-registered. 9. The program according to claim 7 or 8, wherein the registration date of the one immediately preceding the one affected by the change is updated according to the change of the program registration information. How to update. 10. The program update method according to claim 7, wherein the current registration date after the one affected by the change is deleted according to the change content of the program registration information. 11. In a distributed processing system in which a master computer having a generation management function and another computer group not having a generation management function are connected via a network, the master computer stores a plurality of source files and their program registration information. Current generation system information storage means,
Program registration management means for updating the source file and / or program registration information, and generating system change information including at least one of the updated source file or program registration information or file name to be deleted; and the system change information. Is provided to another computer, the other computer is a receiving means for receiving the system change information from the master computer, its own current generation system information storage means, the received source file or program registration information Alternatively, the distributed processing system is provided with a program registration management unit that updates the current generation system information storage unit of its own according to the file name to be deleted. 12. The program according to claim 11, wherein the program registration management means of the master computer executes an object file, an execution format file, and an execution program in this order for each corresponding source file according to the changed contents of the program registration information. Program update processing means for adding the start position of update processing to the system change information, and the other computer performs update processing of the source file corresponding to the program registration information changed from the file / program indicated at the start position. A distributed processing system comprising: 13. The method according to claim 11 or 12,
A distributed processing system in which the same type of computer in the distributed processing system is simultaneously changed in generation with the master computer that manages it.