JP2000357097A - Program managing method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To specify a relation among a source program, an object program and a run unit program. SOLUTION: According to an object program name, a compiler name, a compile option, a compiler version and compile date/time information as compile information 23 extracted from an object program 21 of an investigation object, a source program 11 is compiled, an object program 12 of the output result provided by compiling is compared with the object program 21 of the investigation object and it is discriminated whether the object program 21 of the investigation object is compiled from the source program 11 or not.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

[0001] The present invention relates to a program management method for associating a source program, an object program, and a run unit program.

[0002]

2. Description of the Related Art The result of converting a source program into a machine language through a compiler is an object program. Since the source program and its object program are managed in independent files,
In order to manage the association, save the execution report and translation list output at the time of compilation, and save the source program name and source program file name, object file name, object name, compilation date and time, and version that exist on the report They use information as clues to identify correspondences (list management).

[0003] In addition to managing source programs and object programs by the above method, as a conventional technique, when compiling or linking, management information is automatically registered in a dictionary file, and the dictionary information is viewed. There is also a way to manage programs (dictionary management).

[0004]

However, these conventional management methods have the following problems.

First, the (list management) method includes, when a compile list or a link map is lost, which of the original source program of the object program, which of the run unit program is
There is a problem that there is no means for investigating and associating them.

The first reason is that the source program itself has no management information such as a file name and a compilation date and time relating to the output object program. Even if it is described as a comment, the comment itself may not be renewed or inadequate and cannot be trusted, and the object program itself has an association with the input source program. This is because there is no information such as a source file name and a source program text that can be generated.

Secondly, in addition to the case where the compile list is lost, the association between the source program and the object program is lost in the following cases.

An object may be moved from a file to which an object program is first output to another object file and used. This is because the user moves to an environment that is easy to use for testing, etc., but the movement is performed by the object program librarian, and at that time, the original source program, object program, run unit program management system and In some cases, the user forgets to leave the association as information and releases the program to the production system using a method outside the operator management standards. The production system may be changed by such means especially when dealing with an emergency trouble. Programs that violate these management rules
There are many very large existing program assets that are 20 to 30 years old.

Third, since the object program may be used by being linked to various run unit files, the run unit file name itself is not included in the object program. This means that there was no way to know if it was generated from a program.

Next, in the (dictionary management) method,
There is a problem that it is difficult to apply dictionary management to existing program assets that have already existed before the introduction of (dictionary management).

For a newly developed program, a program management system is newly defined, a (dictionary management) environment is created, and a program can be developed on the environment. Therefore, the transition to the (dictionary management) can be made relatively easily. Although it is possible, for existing programs, it is necessary to change the existing program development environment to a development environment that allows (dictionary management).

When a program development environment is changed, a program closed in an individual system is duplicated with another system.
It is necessary to set new standard rules so that they do not conflict with each other, and to modify, change, and newly register them.

In this case, the management information of the source program and the object program may be lost, the names of the program assets may be duplicated, or the same program may be individually modified and used. Will be organized. To do so, search all library files, identify all that are considered to be the same program, use duplicate source programs and object files that are used in the production system and those used during testing, It is necessary to reexamine the specifications and program comments one by one, such as temporary corrections to the troubles of the above and forgetting to erase them at the development stage. There are also cases where a new specification is created and the program registration management is redone.

When a change occurs in the program name, not only the name change but also the name of the run unit program operating on the production system is changed. Specifically, (dictionary management) After recompiling and linking, a run unit program is created, evaluated, and a series of enormous man-hours are required to perform a run unit program change operation on the production system.

[0015] (Dictionary management) prevents the loss of program management data after the introduction of (Dictionary management) so that the relationship only between source programs, object programs, and run unit programs incorporating the mechanism is not lost. This is a system intended to perform the above-mentioned operations, and is invalid in a state where the relationship between the object program and the run unit program is already unknown.

[0016] An object of the present invention is to complete program management information by making it possible to specify an association between a source program, an object program, and a run unit program when the association has already been lost. To provide a method for managing programs.

[0017]

According to the present invention, in a program management method for managing correspondence between a source program and an object program, a source program is compiled according to compilation information extracted from an object program to be investigated, and an output result of the source program is compiled. Is compared with the object program to be checked to determine whether the object program to be checked is compiled from the source program.

Further, according to the present invention, in a program management method for managing the correspondence between an object program and a run unit program, the run unit program is read, the object information included in the run unit program is extracted, and the object information is to be investigated. It is characterized in that it is compared with object information of an object program to determine whether or not the run unit program is linked from the object program to be investigated.

According to the present invention, it is possible to uniquely determine from the information of only the source program, the object program, and the run unit program body whether or not they are associated as a product from the same source program.

[0020]

Next, an embodiment of a program management method according to the present invention will be described with reference to the drawings.

FIG. 1 shows an embodiment of the present invention and is a diagram for explaining a processing procedure for specifying the association between a source program and an object program.

The outline of the determination method for specifying the association between the programs is as follows. The object program 12 obtained by compiling the source program 11 is compared with the object program 21, and they are products of the same source program 11. Prove that there is.

The objects generated from the same source program differ depending on the type of compiler, compile option, and compiler version, and cannot be simply compared. Therefore, the compile information 30 is extracted from the object program 21 before compiling.
According to the information, the object program 12 is compared with the object program 12 output after the compilation.

The compile information 30 is generally held as information in an object because the maker providing the compiler responds to an error relating to the compiler or because the object needs to be managed in a library.

Next, the object program 21 and the compiled object program 12 are dump edited and output, and the edited data is compared in units of records, and records having differences are output. As a result of the comparison,
If only the compile date and time are different, the objects can be regarded as coincident, and the object program 21
Can be determined to be an object obtained by compiling the source program 11.

Next, the processing operation of the embodiment of the present invention will be described in detail with reference to FIGS. FIG. 2 is a diagram illustrating a processing procedure for extracting compile information from an object program.

First, a procedure for extracting compile information from an object program will be described. In FIG. 2, through the processing procedures of steps 201 to 207, the object program 21 is input, and the object program name, the compiler name, the compiler version, and the compilation date and time information are extracted from the object program. Then, the compile option table 42 in the memory is compared with the data corresponding to the compile option in the object program, and the compile information 23 is output to the compile information extraction file 25 as a compile option for the compiler that can be specified by the user.

The purpose of the processing procedure shown in FIG. 2 is to clarify the compilation information because the output object differs in instruction and object size depending on the type of compiler, compiler option, and compiler version.

After clarifying the compilation information on the object program, it is necessary to generate an object program from the source program and use it for comparison with other object programs.

Next, step 101, step 1 in FIG.
02 will be described.

With the source program 11 as input, FIG.
In accordance with the compiler name, the compiler version, and the compile option, the corresponding compile (step 101) is executed and the object program 12 is output. It is then dumped into the object program (step 10
In 2), the data is edited and output to the object program dump file 13.

In the object program dump processing,
The object program is divided into a data section and a code section, and the used segment name information is edited and added, and output to a sequential file.

The reason why the object programs are not directly compared with each other but compared with those edited and output to a sequential file in the object program dump process is as follows.
This is to make it easier for a user to compare different data when there is.

Next, the processing procedure of step 103 in FIG. 1 will be described.

An object program dump process (step 103) is executed on the object program 21 to create an object program dump file 22.

The two dump files 13 and 2 created by the processing procedures of steps 101 to 103 are shown.
2 are sequentially compared in a record unit in step 104, and records that do not match are output in a list side by side to compare the record images of the two object program dumps. In the process of step 104, the compile date and time do not match. If the other data match, it is determined that the original source program of the object program 21 is the source program 11.

Next, a processing procedure for determining whether or not the run unit program is a product of the object program will be described. FIG. 3 is a diagram illustrating a processing procedure for specifying an association between a run unit program and an object program.

As an outline of the determination method for specifying the association between the programs, the run unit program 3
In FIG. 1, since the object image of the object program is taken in at the time of linking, the object program name and the compilation date and time, which are the object information included in the object, are compared with the object information in the object program 32 to be investigated. If they match, the run unit program 31 determines that the product is a product created by linking from the object program 32.

Steps 301 to 304 in FIG. 3 are processing procedures for confirming whether or not the original object program before linking the run unit program 31 is the object program 32. The purpose of this procedure is that if there is more than one object program and it is not possible to determine which is the master, then it will not be possible to match the object program with the source program later, so the run running on the production system will not be possible. This is to specify an object program based on a unit program.

In step 301, the run unit program 31 is used as an input to extract the object program name and the compile date and time included in the run unit program.

Next, a compile information extracting process is performed on the object program 32 (step 302), and an object program name and a compile date included in the object program are extracted.

The two object program names and the compile date are read (step 303), and whether or not the object program name and the compile date match is compared in step 304. If they match, the run unit program 31 executes the object program It can be determined that the original object program is an original object program before linking.

If they do not match, the name of the object program in the run unit program, the compile date and time, the name of the object program of the object program, and the compile date and time are output as user reference information.

[0044]

As described above, according to the present invention, the association between a source program, an object program, and a run unit program can be completely guaranteed even if their management information has been lost. As a result, the program development environment can be organized,
Problems caused by development using an incorrect source program or object program do not occur.

For example, if there is only one run unit program and there are a plurality of object programs and source programs, and it is not known which is the original object program and original source program for the run unit program, this method is used. An object program is specified from the run unit program, and a source program can be specified from the object program.

A situation in which the past existing assets are reviewed on a large scale, such as the year 2000 problem, has occurred, and it is no longer possible to associate source programs, object programs, and run unit programs with program assets 10 to 30 years ago. When there are many programs, it is possible to significantly reduce the number of man-hours required for organizing and developing the programs.

In addition, since the development environment of existing assets without management information can be organized, the source program, the object program, and the run unit program could not be related to each other, so that (dictionary management) could not be applied to the program. Then, (dictionary management) can be applied, so that future program asset management can be facilitated.

[Brief description of the drawings]

FIG. 1 is a diagram illustrating a processing procedure for specifying an association between a source program and an object program.

FIG. 2 is a diagram illustrating a processing procedure for extracting compile information from an object program.

FIG. 3 is a diagram illustrating a processing procedure for specifying an association between a run unit program and an object program.

[Explanation of symbols]

DESCRIPTION OF SYMBOLS 11 Source program 12, 21, 32 Object program 13, 22 Object program dump file 23 Compilation information 24 Compilation option table 25 Compilation information extraction file 31 Run unit program 101-104, 201-207, 301-304

Claims (6)

[Claims] 1. A program management method for managing a correspondence between a source program and an object program, comprising: compiling a source program according to compilation information extracted from an object program to be investigated; And comparing the object program to be checked with the object program to determine whether the object program to be checked is compiled from the source program. 2. The program management method according to claim 1, wherein the compile information is an object program name, a compiler name, a compile option, a compiler version, and a compile date. 3. The method according to claim 1, wherein the object program to be examined and the object program output by compiling the source program are edited and output as dump files, respectively, and the dump files are compared with each other. The described program management method. 4. The program management method according to claim 3, wherein the dump files are sequentially compared in record units. 5. A program management method for managing a correspondence between an object program and a run unit program, wherein the run unit program is read, object information included in the run unit program is extracted, and an object of the object program to be investigated is read. A program management method for comparing the information with information to determine whether the run unit program is linked from the object program to be investigated. 6. The program management method according to claim 5, wherein said object information is an object program name and a compilation date.