JP2003140889A - System for managing program construction - Google Patents

Abstract

PROBLEM TO BE SOLVED: To effectively use resources by deleting a compile unit of an intermediate file that is not updated or reused anymore in management of a program. SOLUTION: This system comprises a translation means for obtaining a compile unit of a source unit; a coupling means for obtaining a load module from the compile unit; a load module execution means for executing a load module; a relational resource information gain means for obtaining translation management information from the translation means, coupling information from the coupling means, and execution results from the load module execution means; a relational resource information registration means for storing the relational information in a program construction management database; a compile unit deletion judging means for judging deletion conditions of the compile unit by the relational information of the program construction management database; and a compile unit deletion means for deleting the compile unit and deleting the management information of the compile unit.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to program configuration management for managing translation, combination, and execution of programs,
In particular, the present invention relates to a program configuration management system that determines the deletion condition of a compilation unit of an intermediate file and automatically deletes it from the library to save the library capacity.

[0002]

2. Description of the Related Art In conventional program management, since the entire program resources created in a series of steps of a source program, a compilation unit, and a load module are collectively managed, a compilation unit that cannot be used again in an intermediate file is It is normally held as part of the program resources until the program or load module is destroyed.

According to Japanese Patent Laid-Open No. 03-098118, it is possible to standardize a source program, a compile unit, and a load module that compose a program from a source program to an execution program by using a program management system for unified management. It is explained. According to the present invention, unified management enables development and maintenance of a large-scale program without confusion. However, the intermediate generation file generated in a series of steps remains held until the entire program is deleted, resulting in waste of resource use.

Japanese Patent Application Laid-Open No. 04-328632 describes that compile units are collectively managed by generations. Therefore, as long as the generation is valid, the compilation unit is possessed even though it is unlikely to be used again. Since the compile unit is an intermediate file, it can be played back while the source program is valid. Therefore, when the compile unit is no longer used, it is not necessary to retain the intermediate file.

Japanese Unexamined Patent Publication No. 11-154079 describes that software assets having a fixed retention period are integrated and managed. In the present invention, the management table includes JCL, load module, compile unit,
The source units are managed in association with each other for a fixed period. Therefore, even if the software is stable and is never updated, its intermediate files are also stored.

[0006]

In the conventional program configuration management, as described above, even the intermediate files that are not updated or reused are saved as a part of the program assets.

The first problem is that unnecessary information is continuously managed as it is. The reason is that the compile unit is just an intermediate file, and if the source unit and the load module are saved after the program development is completed, even if the compile unit is not managed, there is a problem from the viewpoint of program maintenance. Because there is no.

The second problem is that unnecessary resources remain in the library of the external storage device and are not deleted. The reason is as mentioned in the first problem and the reason,
The reason is that there is no means to judge and delete the condition for deleting a compilation unit from the library after the program development stage is finished and the update no longer occurs.

An object of the present invention is to eliminate the compile unit of an intermediate file for which there is no opportunity to update or reuse it in program management, and effectively utilize resources.

[0010]

Therefore, according to the present invention,
A source unit, which is the processing unit of the source program,
A compilation unit that translates the source unit,
In a system in which a load module in which the compilation units are combined and each of which are stored in a library for program management, a program configuration management database that manages the load modules is searched, and a compilation unit that satisfies a predetermined deletion condition is searched from the compilation unit library. It is characterized by deleting.

Further, the deletion condition is that the use result of the load module has been normally terminated, and that a predetermined period has passed without being updated since the compile units constituting the load module have been combined. Characterize.

Further, the program configuration management database has program configuration management information for each load module for each program to be managed, and the program configuration management information includes the load module identification name and the year / month of the combining process. Date, the used linker information, a usage result indicating whether the load module has completed normally or abnormally when executed, and a combined unit configuration of compile units configuring the load module,
And the combined unit configuration includes a combined compilation unit identifier and a final compilation date of the compilation unit.

Further, the program configuration management system creates and manages a library for accumulating program resources and a source unit of the program resources by performing a process of translating and combining to create a compile unit and a load module. In addition, the present invention is characterized by including a processing unit that obtains a usage result of the load module and a program configuration management database that holds program configuration management information that manages a configuration and a usage result of the load module.

Further, the library includes a source unit library for storing a source program in a translation processing unit, a compile unit library for storing a translated source unit, and a load module library for storing a load module in which the compile units are combined. And are included.

Further, the processing unit executes translation processing means for translating a source unit of the source library to obtain a compilation unit, combination processing means for coupling the compilation unit to obtain a load module, and the load module. Load module execution processing means,
Translation information of the source unit from the translation processing means, and binding information of the compilation unit from the binding processing means,
Usage result information of the load module execution processing means,
Related resource information acquisition means for obtaining related information including, related resource information registration means for storing the related information in a program configuration management database, and the deletion condition of the compile unit based on the related information in the program configuration management database. Compile unit deletion judging means for judging, and the compiling unit is deleted from the compiling unit library based on the judgment result, and a deletion identification is added to the compiling unit from the program structure management information of the program structure management database. And a compiling unit deleting means.

[0016]

BEST MODE FOR CARRYING OUT THE INVENTION Embodiments of the present invention will be described with reference to the drawings. Referring to FIG. 1, a program configuration management system 1 includes a library 10 that stores program resources existing on an external storage device (not shown), and a processing unit 20 that translates, combines, and executes programs.
And a program configuration management database 3 for registering related resource information for program configuration management.

The program library 10 includes a source unit library 11, a compile unit library 12, and a load module unit library 13.
And, are included. Source unit library 11
Stores a source unit which is a processing unit at the time of translating a source program. The compile unit library 12 stores a compile unit obtained by translating a source unit. The load module library 13 stores a load module of an execution program formed by combining compile units.

The processing unit 20 includes a translation processing unit 21, a combination processing unit 22, and a load module execution processing unit 23.
A compile unit deletion determination means 24, a compile unit deletion means 25, and a related resource information acquisition means 26.
And related resource information registration means 27.

The translation processing means 21 takes out a source program described in a predetermined programming language from the source unit library 11, translates it, and outputs it to the compile unit library 12 as a compile unit.

The combining processing means 22 acquires the compile units from the compile unit library 12, combines them, and stores them in the load module library 13 as a load module of the executable file.

The load module execution processing means 23 takes out a load module which is an executable file from the load module library 13 and causes the processing section 20 to execute the load module to execute a predetermined process.

The load module execution processing means 23 reads a predetermined load module from the load module library 13 and executes it. The execution result of the load module is passed to the related resource information acquisition means 26 as the resource related information.

The compile unit deletion judging means 24 is
The program configuration management information registered in the program configuration management database 30 is automatically searched, and the compile unit of the program is not used for translation or combination processing for a predetermined period, and the load module that combines the compile units. When it is determined that the execution result of (1) has ended normally, the information is passed to the compiling unit deleting means 25.

The compile unit deleting means 25 deletes the corresponding compile unit in the compile unit library 12 and the program for the compile unit judged to be erasable based on the information passed from the compile unit deleting judging means 24. The deletion is assigned to the program configuration management information of the corresponding compilation unit registered in the configuration management database 30.

The related resource information acquisition means 26 constantly monitors the operation in the processing section 20, and when the translation processing means 21, the combination processing means 22 and the load module execution processing means 23 operate, the related load module identifier Then, the processing date and time and the information on the use result (normal end or abnormal end) are acquired, and the information is passed to the related resource information registration means 27.

The related resource information registration means 27 appropriately registers the information passed from the related resource information acquisition means 26 in the related program configuration management information 31 of the program configuration management database 30. Since the load module is composed of a plurality of compile units, and the compile unit may be combined with one or more load modules and used, the related resource information registration means 27 makes the program configuration management of the program configuration management database 30. Search all the information 31 and find the relevant load module.

Referring to FIG. 2, the program configuration management information 31 includes the identifier 3111 of the load module 311.
And the date and time when the load module 311 was combined and the linker information 3112 that was used, and the usage result 3113 that indicates whether the load module 311 was abnormally ended or normally ended as a result of execution. 311 and a combined unit configuration 3114 of the compile units that constitute 311. The combined unit configuration 3114 includes the compiled unit identifier and the last compilation date 31114 to 3114n.
And, including.

The compile unit deletion judging means 24
All the program configuration management information 31 is searched, the usage result 3113 of the load module 311 is normally terminated, and the compilation unit identifier for which the last compilation date of the compiling unit to be configured has passed a predetermined period is deleted and the deletion condition is determined. The compile unit deleting means 25 is notified of the compile units that satisfy the condition.

Next, the operation of this embodiment will be described with reference to the drawings. With reference to FIG. 1 and the flowcharts of FIGS. 3 and 4, the overall operation of this embodiment will be described.

Referring to FIG. 3, the translation processing means 21
When the compile unit 120 is generated from the source unit 110 in the source unit library 11 and stored in the compile unit library 12, the related resource information acquisition unit 26 manages including the processing date and time regarding the source unit 110 and the compile unit 120. The information is acquired, and the related resource information registration means 27 registers the management information in the program configuration management information 31 of the program configuration management database 30. When the binding processing unit 22 generates the load module 130 from the compile unit 120 in the compile unit library 12 and stores it in the load module library 13, the related resource information acquisition unit 26 processes the compile unit 120 and the load module 130. The management information including the date and time is acquired, and the related resource information registration means 27 registers the management information in the program configuration management information 31 of the program configuration management database 30. When the load module execution processing unit 23 executes the load module 130 in the load module library 13, the related resource information acquisition unit 26 manages the processing date and time and the end state (whether the end is normal or abnormal). Then, the related resource information registration means 27 registers the management information in the program configuration management information 31 of the program configuration management database 30.

Referring to FIG. 4, the compile unit deletion judging means 24 is automatically started and the program configuration management database 30 stores the program configuration management information 31.
Is obtained (step 41 in FIG. 4). It is checked whether the program configuration management information 31 includes the compile unit information. If the compile unit information is included (Y in step 42), first, the load module use result 3113 is checked (step 43). Next, the final compilation dates 31141 to 3114n for the compilation units of the combined configuration 3114 are examined (step 44). Here, when the normal termination of the load module can be confirmed (Y of step 43), and when it can be determined that the compilation unit has passed from the last compilation date for a certain period or more (Y of step 44), the corresponding compilation is performed. Information about the unit is passed to the compile unit deleting means 25 (step 45). For a compile unit that does not satisfy either condition of normal termination of the load module or unused of the compile unit for a certain period, the corresponding compile unit is not targeted for deletion. The above processing is performed for all the program configuration information 31 registered in the program configuration management database 3.
(N in step 46). After that, if there is a compiling unit that can be deleted by the compiling unit deleting means 25 (Y in step 47), the corresponding compiling unit in the compiling unit library 12 is deleted (step 48), and the program structure management information in the program structure management database 30 is deleted. The deletion identification is added to the corresponding compilation units 31141 to 3114n of the 31 combined unit configuration 3114 (step 49).

Next, the operation of this embodiment will be described with reference to the schedule of program creation work. As shown in FIG.
On July 10, 001, the source unit 110 was translated to obtain the compile unit 120, and this information was registered in the program configuration management database 3. Next, on July 20, 2001, the compile unit 120 was combined to obtain the load module 130, and this information was registered in the program configuration management database 3. Next, on July 25, 2001, the load module 130 was executed and terminated normally, and this information was registered in the program configuration management database 3.
In this way, the program configuration management information 131 including the source unit 110, the compilation unit 120, and the load module 130 is registered in the program configuration management database 30.

Here, if the period which is the criterion for the compile unit deletion determination is set to half a year, and it is assumed that the translation / combining process regarding the compile unit 120 has not been performed for half a year since July 20, 2001, 2002
When the compile unit deletion determination means 24 operates after the 20th of a month, the compile unit information is registered (step 42 in FIG. 4), and the information that the load module is normally completed is registered (step 43). Y), the information that the compile unit has been used in the last half year is not registered (Y in step 44), it is determined that the compile unit can be deleted through the above steps, and the compile unit from the compal unit library 12 is determined. Deletion of 120 and deletion identification are added to the compilation unit 120 from the program configuration management database 30 (steps 48, 49).

Next, this embodiment will be described with reference to another concrete example. Referring to FIG. 6, FIG. 6 is an example in which a plurality of load modules 131 and 132 have a common compile unit 122. Source units 111 to 113, compilation units 121 to 123, load module 1
31 and the load module 132 have a relationship as shown in the figure. That is, the translation processing means 21 causes the source unit 111 to compile unit 121 and the source unit 112 to compile unit 122.
A compile unit 123 is generated from each source unit 113. Further, by the combining processing 22 means, the load module 131 from the compile unit 121 and the compile unit 122 and the compile unit 1
A load module 132 is generated from each of 22 and the compilation unit 123.

The combined unit configuration 3114 of the program configuration management information load module 131 comprises a compile unit 121 and a compile unit 122, and the other load module 132 comprises a compile unit 122 and a compile unit 123. ing. Therefore, the source unit 112 and the compile unit 122 are included in both the load module 131 and the load module 132.

At this time, the compiling unit deletion judging means 24 judges the deletion of the compiling unit 123 by the load module 131 and the load module 13.
It can be deleted only when the execution information of both No. 2 and No. 2 is checked and it can be confirmed that both have been completed normally, and it is further determined that the compile unit 122 has not been used for a certain period of time or more. Then, the compile unit deleting means 25 deletes the compile unit 122 of the compile unit library 12, and the compile unit 1 registered in the program configuration management database 30.
A deletion identification is added to 22. Also, load module 1
When the usage result in which 31 is normally terminated and the load module 132 is abnormally terminated is registered, the compile unit 122 and the compile unit 123 cannot be deleted.

[0037]

The first effect of the present invention is that the source unit and load module necessary for maintenance of the currently used program can be efficiently managed by the program management information. The reason is that a compile unit that can be determined to be unnecessary is detected and deleted from the compile unit library and the program configuration management database.

The second effect is that the external storage device for storing the program library can be effectively utilized. The reason is to detect a compilation unit that can be determined to be unnecessary and delete it from the library.

[Brief description of drawings]

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

FIG. 2 is a diagram showing an item configuration of program configuration management information stored in a program configuration management database shown in FIG.

FIG. 3 is a diagram showing a processing procedure of translation and combination of source units.

FIG. 4 is a diagram showing a procedure for deleting a compilation unit.

FIG. 5 is an illustration of program configuration management in this embodiment.

FIG. 6 is an illustration of a compile unit deletion process in this embodiment.

[Explanation of symbols]

1 Program configuration management system 10 program library 11 Source Unit Library 12 Compile unit library 13 Load module library 20 Processing Department 21 Translation processing means 22 Join processing means 23 Load module execution processing means 24 Compile unit deletion determination means 25 Compile Unit Deletion Means 26 Related resource information acquisition means 27 Related resource information registration means 30 Program configuration management database

Claims (6)

[Claims] 1. A system in which a source unit, which is a processing unit of a source program, a compile unit that translates the source unit, and a load module that combines the compile units are respectively stored in a library to manage a program, A program configuration management system characterized by searching a program configuration management database that manages load modules and deleting a compilation unit that satisfies a predetermined deletion condition from a compilation unit library. 2. The deletion condition is that the usage result of the load module has ended normally, and that a predetermined period has passed without being updated since the compile units constituting the load module have been combined. The program configuration management system according to claim 1, which is characterized in that. 3. The program configuration management database has program configuration management information for each load module for each program to be managed, and the program configuration management information includes an identification name of the load module and a year / month of a combining process. Including the date, the linker information used, the use result indicating whether the load module executed normally or abnormally when executed, and the combined unit configuration of the compile units configuring the load module, 2. The program configuration management system according to claim 1, wherein the combined unit configuration includes a combined compilation unit identifier and a final compilation date of the compilation unit. 4. The program configuration management system comprises: a library for accumulating program resources; a source unit of the program resources;
A processing unit that performs a combining process to create and manage a compile unit and a load module, and obtains a usage result of the load module, and program configuration management information that manages the configuration and usage result of the load module The program configuration management system according to claim 1, further comprising: 5. The library includes a source unit library that stores a source program in a translation processing unit, a compile unit library that stores a translated source unit, and a load module library that stores a load module in which the compile units are combined. The program configuration management system according to claim 1, further comprising: 6. The processing unit executes translation processing means for translating a source unit of the source library to obtain a compile unit, combining processing means for combining the compile units to obtain a load module, and executing the load module. Load module execution processing means, translation information of the source unit from the translation processing means, binding information of the compilation unit from the binding processing means,
Usage result information of the load module execution processing means,
Related resource information acquisition means for obtaining related information including, related resource information registration means for storing the related information in a program configuration management database, and the deletion condition of the compile unit based on the related information in the program configuration management database. Compile unit deletion determining means for making a decision, and deleting the corresponding compile unit from the compile unit library based on the result of the decision, and adding a deletion identification to the relevant compile unit from the program configuration management information in the program configuration management database. The program configuration management system according to claim 1, further comprising: a compile unit deleting unit.