JPH05224910A - Program revision managing method - Google Patents

Abstract

PURPOSE:To prevent a fact that a module before its correction operates and executes incorrectly a processing, in the case where it is forgotten to generate a load module, in spite of a fact that the module is corrected. CONSTITUTION:An editor control part 4 actuates an editor 5 in order to correct a module whose correction becomes necessary, and updates the correction data and hour of a module management table 2, and its revision, when the correction is completed. A compiler control part 6 actuates a compiler 7 in order to translate a corrected source program to an object program, and updates the compile date and hour managed by the module management table 2. A linker control part 8 retrieves a load module which is using the generated object program, from a link management table 3, actuates a linker 9, when the load module is detected, generates the load modules, and updates the generation date and hour and the load module revision, managed on a load module management table 1.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a method for developing a business program in a computer system, and in particular,
Revision management method for developed programs.

[0002]

2. Description of the Related Art In the development of a business program, a program is modified by a program modifier using a source program modification function of an editor for each module constituting a program to be modified. When the modification of the program is completed, a compiler is used to translate the modified source program, and an object program is created from the modified source program. When the creation of the object program is completed, the program rectifier finds out all the programs that use the modified object program, and uses the linker to create the load module for each program.

[0003]

Since the above-mentioned conventional program revision management method is carried out manually, all programs using the modified module must be relinked and operated. When a program is executed due to forgetting to relink a part of the program, there is a drawback that the module in the state before correction is called from the executed program and the program operates abnormally.

[0004]

According to a program revision management method of the present invention, a creation date and time of a load module which is a program execution unit, and a load module management table in which all modules constituting the load module are registered. , The module management table in which the modification date, compilation date, and revision of the modules that make up the program are registered, the link management table in which which load module the module is configured in, and the editor that starts the editor A control unit,
A linker that has the function of activating the compiler that translates the source program into an object program and observing the end status, and the linker that combines the object program and creates the load module to monitor the end status. When a program corrector modifies a module using a control unit, the compiler control unit activates the compiler, and if compilation is normally completed, control is passed to the linker control unit and the linker control unit , The link management table is searched for which load module the compiled module constitutes, and the linker is started. The linker control unit monitors the end state of the link, and if it is normally completed, the module management table. , Link management table, load module management table And performing update processing of Le.

[0005]

DESCRIPTION OF THE PREFERRED EMBODIMENTS Next, the present invention will be described with reference to the drawings.

FIG. 1 is a block diagram of an embodiment of the present invention.
The editor control unit 4 has a function of activating the editor 5 in order to correct a module that needs to be corrected, and updating the correction date and revision of the module management table 2 when the correction is completed. The compiler control unit 6 has a function of activating the compiler 7 to translate the modified source program into an object program and updating the compile date and time managed by the module management table 2. The linker control unit 8 searches the link management table 3 for the load module that uses the created object program. If the load module is found, the linker 9 is activated, the load module is created, and the load module management is performed. It has a function of updating the creation date and time and the load module revision managed on the table 1.

The load module management table 1 has management information of the creation date and time and revision of the load module, and the module name of the load module.

The module management table 2 stores the modification date and revision of the source program for each module,
It holds the compile date and revision of the object program and the name of the corresponding link management table. The link management table 3 has information on the names of all programs calling the module and the corresponding load module management table names.

There is a source program that needs to be corrected, and the program corrector activates the editor control unit 4,
Try to modify the source program. The activated editor control unit 4 activates the editor 5 in order to modify the source program. The program modifier uses the source program modification function of the editor 5 to call the source program to be modified to the terminal device, selects the location to be modified, and modifies the source program. When the correction is completed, the corrector terminates the editor 5 and inputs the source program correction completion information to the editor control unit 4. Upon receiving the information, the editor control unit 4 searches the received information for the corrected module name,
The module management table 2 of the corresponding module is searched based on the module name. If the module exists in the module management table, the editor control unit updates the modification date and revision in the table with the received information. When the updating of the table is completed normally, the editor control unit 4 sends a completion of correction to the compiler control unit 6 to start the compiler control unit 6 in order to perform the compilation work.

The compiler control unit 6, which has received the information indicating that the modification has been completed, searches the modification completion information for the module name to be compiled. The compiler searches for the corresponding module in the module management table 2 based on the searched module name. The information necessary for compilation in the searched module management table 2 is taken out, and the compiler 7 is started based on this information. The started compiler 7 is
Based on the passed information, the process of translating the modified source program into an object program is performed. The compiler control unit 6 monitors whether the activated compiler 7 is executing or whether the normal termination is abnormal termination, and if the compilation is normally terminated, the compiler control unit 2 updates the compilation completion date and revision in the module management table 2. If it is an abnormal end, the program rectifier is notified of the abnormal end. The compiler control unit 6, which has completed the table update process with normal termination, sends compilation completion information to the linker control unit 8 in order to recreate all load modules that use the compiled object program, and The control unit 8 is activated.

The linker control unit 8 which has received the information indicating that the compilation is completed extracts the link management table information from the compilation completion information, and searches the link management table 3 based on the extracted information. From the searched link management table 3, the load module management table information is retrieved in order to search the load module name to be linked. The load module management table is searched based on the retrieved load module management table information. The information required for linking is retrieved from the retrieved load module management table information. Based on the extracted link information, the linker control unit 8 activates the linker 9 to create a load module. The activated linker 9 creates a load module based on the link information. The linker control unit 8 monitors whether the linker 9 normally ends or abnormally ends, and if the linker 9 is normal, updates the creation date and revision in the load module management table 1. If it is an abnormal end, the program modifier is notified of the abnormal end. When the linker 9 ends normally and the update processing of the load module management table 1 ends normally, the linker control unit 8 extracts the load module management table 1 of the load module to be linked next from the link management table 3 previously extracted. , The load module management table 1 is searched. Information necessary for linking is retrieved from the retrieved load module management table 1 and the linker 9 is activated. If the linker 9 ends normally, the information in the load module management table 1 is updated. The process is repeated until there is one load module management table to be linked on the link management table 3. When there is no load module to be linked, the linker control unit 8 notifies the program rectifier of normal termination and terminates the processing.

[0012]

As described above, according to the present invention, when a program revamper modifies one module, the program is translated by using the translated module of the corrected module and the target module. By automatically re-linking and creating a new load module, if the load module is forgotten to be created despite the modification of the module, the module before the modification does not work properly. This has the effect of preventing processing.

[Brief description of drawings]

FIG. 1 is a configuration diagram of an embodiment of the present invention.

[Explanation of symbols]

 1 load module management table 2 module management table 3 link management table 4 editor control unit 5 editor 6 compiler control unit 7 compiler 8 linker control unit 9 linker 10 program source file 11 object source file 12 load module file

Claims (1)

[Claims] 1. A creation date and time of a load module which is an execution unit of a program, a load module management table in which all modules constituting the load module are registered, a modification date and time and a compilation date and time of modules constituting the program, A module management table in which a revision is registered, a link management table in which which load module the module is configured in, a editor control unit that starts an editor, and a compiler that translates a source program into an object program Modify the program by using the compiler control unit that has the function of invoking the program and monitoring the end status, and the linker control unit that has the function of starting the linker that combines the object programs and creates the load module and monitoring the end status. Who is the module When the modification is performed, the compiler control unit starts the compiler, and if the compilation is normally completed, the control is passed to the linker control unit, and the linker control unit determines which load module is the compiled module. Whether or not the link management table is searched, the linker is started, and the linker control unit monitors the end state of the link and, if the link ends normally, updates the module management table, the link management table, and the load module management table. Program revision management method characterized by performing.