JPH06110668A - Update processing system for load module library with generation - Google Patents

Abstract

PURPOSE:To improve the efficiency of program development by decreasing the work of generation erase and generation UP accompanied with the program development work concerning the update processing system for load module library with generation to manage and update the load modules of plural generations. CONSTITUTION:A generation managing table 18 of a load module library 16 with generation is provided with an area for storing setting information concerning the plural levels for one generation of the load module. An automatic generation switching mechanism 13 selects the reading request of the load module and the latest level among the generations and additionally prepares the latest level among the generations corresponding to the updating request. A use condition monitoring mechanism 14 manages the use conditions of load modules and when the plural levels exist in one generation, the information of the old level is erased on the condition that there is no user.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a generation load module library update processing system capable of increasing the efficiency of program development on a generation load module library.

In order to realize active maintenance of programs,
It is considered to be an important technology to manage generations of load modules using a load module library with generations. In the program development work using such a load module library with generations, there is a demand for technology that can simplify generation management and update the load module library in operation without being aware of generation management. There is.

[0003]

2. Description of the Related Art FIG. 9 is an explanatory diagram of a conventional technique. The root directory 90 has management information such as the upper directory 91. The root directory 90 and the upper directory 91 are files having management information for associating the file names with the positions on the volume of the files managed under it. In the example of FIG. 9, the load module library with generation 92 is managed by the upper directory 91.

Load module library with generation 92
Has management information 93 for the entire load module and management information 94m, 94n for each generation. In the overall management information 93, sharing related information of data of each generation and attribute information of each generation are stored. The management information 94m and 94n for the m-th generation and the n-th generation include information about where in the volume the blocks making up the generation are stored, and detailed information (creation date / time and update date / time) closed to the generation. Is stored.

B1 to B7 represent blocks constituting each generation. In this example, the mth generation load module is composed of blocks B1 to B4, and the nth generation load module is composed of blocks B4 to B4. It is composed of B7. The block B4 is shared by the mth generation and the nth generation.

As a reference of such a load module with generation, for example, Japanese Patent Laid-Open No. 105619/1993
Japanese Patent Laid-Open No. 4-52826. Conventionally, when the load module of the load module library with generation 92 is updated, the generation is always updated, and it is necessary to delete the unnecessary old generation.

[0007]

[Problems to be Solved by the Invention] Modules are frequently modified during program development work. Although it is possible to manage the generations for each modification, there is an upper limit to the number of generations that can be stored in one load module library with generation 92, and the user can delete the unnecessary generations while raising the generation UP. Need to do. Therefore, there is a problem that the development work may be complicated, and management of generations such as how many generations the current latest generation is is difficult.

The present invention solves the above-mentioned problems, and in response to a load module use request, control is performed so that the latest load module library is always selected. It aims to improve program development efficiency by providing a program development environment that can update the load module library.

[0009]

FIG. 1 is a diagram for explaining the principle of the present invention. In FIG. 1, 10 is a processing device including a CPU and memory, 11 is a program loading mechanism for loading a program to be executed, 12 is a generation management mechanism having a processing function for managing the generation of a load module, and 13 is designated by a user. Generation switching mechanism for selecting the latest level from among the generations on the medium, 14 is a usage status monitoring mechanism for monitoring the usage status of the load module, and 15 is a usage for storing information on the usage status of the load module. A status management table, 16 is a load module library with generations, 17 is overall management information for managing generations and management information for each generation, 18
Represents a generation management table, and 19-1 to 19-3 represent load modules of each generation.

Load module library with generation 16
Is a file that stores the configuration data of multiple generations of load modules and their management information. Generation Management Organization 12
Is a processing means of the operating system that provides a reference and update function for the load module library with generation 16. Program loading mechanism 11
Is a processing unit that requests the generation management mechanism 12 to perform processing and loads the load module of the program to be executed from the load module library with generation 16.

According to the present invention, the management information 17 of the loadable module library with generation 16 has a generation management table 18 having an area for storing setting information regarding a plurality of levels for one generation of the load module. Multiple levels can be set for each generation.

The generation management mechanism 12 selects the latest level of the designated generation for the read request of the load module for program execution by the program loading mechanism 11, and the latest level of the designated generation for the update request of the load module. It has a generation automatic switching mechanism 13 for additionally creating a level. Further, the usage status management table 15 manages the usage status of the load module, and deletes the information of the old level on condition that there is no user when there are multiple levels in one generation. have.

[0013]

According to the present invention, an automatic generation switching mechanism 13 for selecting a level within a generation and a load module usage status monitoring mechanism 14 are provided in the system, and one generation of the load module library with generation 16 is provided. Have a structure that manages multiple levels. This makes it possible to update the load module of the generation under execution, and realizes a mechanism that always uses the latest updated load module for a program execution request. By doing so, it is not necessary to delete the generations associated with the program development work, and the work amount of the generation UP is reduced, so that the program development efficiency is improved.

[0014]

[Embodiment] FIG. 2 shows a configuration example of a generation management table according to an embodiment of the present invention. The management information 17 of the load module library with generation 16 is managed by the data structure as shown in FIG. The generation management table meta 21 is pointed to from the root control table 20. The generation management table meta 21 is the minimum generation / minimum level generation management table 1
8 and pointer information to the maximum generation / maximum level generation management table 18-2. The generation management tables 18, 18-1, ... Are linked by mutual pointers.

The generation management table 18 includes fields of generation number and level number, fields related to generation attributes, pointer fields to generation management table of previous generation number / level number, and subsequent generation number / level number. Of the generation management table, a field of a pointer to the data inheritance source generation / level, a field of a pointer to the generation / level configuration data table, and the like. The pointer to the data inheritance generation and the pointer to the generation configuration data table are
This is information for managing the sharing relationship of data between generations and levels.

In this embodiment, the generation number is managed by a 4-digit number. Furthermore, a 1-digit level number is added to each generation, and 5
Manage generations and levels with digit numbers. When differentially managing the data of the load module library with generations, a 5-digit number in which a generation number and a level number are arranged is treated in the same manner as a conventional generation number. That is, conventionally, the generation management table 18 is provided for each generation, but in the present embodiment, the generation management table 18 is provided for each level of each generation and is managed in the same manner as in the past.

Next, the operation of the embodiment of the present invention will be described with reference to FIGS. In the explanation below
Corresponds to ~ shown in Figs. As shown in FIG. 3, when there is a program execution request from the user a, the program loading mechanism 11 is activated, and the program loading mechanism 11 requests the generation management mechanism 12 to read the load module.

In response to a request from the program loading mechanism 11, the generation management mechanism 12 uses the automatic generation switching mechanism 13 to select the latest level of the latest generation.
In this example, the 3rd generation 1st level is the latest level of the latest generation. If the user does not explicitly specify a generation, the latest generation is treated as the default.

Upon receiving the notification from the automatic generation switching mechanism 13, the usage monitoring mechanism 14 records in the usage management table 15 that the user a executes 3 generation 1 level. The usage status management table 15 is
It has setting fields related to usage generation and usage.

Next, as shown in FIG. 4A, it is assumed that the user b makes a program update request. The automatic generation switching mechanism 13 additionally creates and allocates the latest level of the latest generation in response to a program update request. Three generations and two levels will be automatically generated.

It is assumed that, after the third generation, second level update process is completed, as shown in FIG. 4B, the user c issues a program execution request. Since the automatic generation switching mechanism 13 selects the latest level of the latest generation, it selects the load module of the 3rd generation and the 2nd level, and executes its read processing. The usage status monitoring mechanism 14 is notified of this, and the usage status monitoring mechanism 14
The fact that the user c executes the 3rd generation 2nd level is recorded in the usage status management table 15.

As shown in FIG. 5, it is assumed that the execution of the user a is completed and there are no users of the third generation and the first level. The usage status monitoring mechanism 14 uses the usage status management table 1
When 5 is detected and it is detected that there are no users at the 3rd generation 1st level, the load module library with generation 1
Delete the 3rd generation 1st level data in 6.

As described above, when a new level is created in a generation, the usage status monitoring mechanism 14 monitors the usage status and automatically deletes the old level with no user, thereby Prevent the above data volume from unduly increasing.

By the way, in the case of executing and updating the load module, the following exclusive control is performed. (1) Exclusive acquisition processing for the file name of the load module library with generations.

(2) Exclusive acquisition processing for the generation of the load module library with generation. (3) Execution / update processing of the specified generation of the load module library with generations. (4) Exclusive release processing for the generation of the load module library with generations.

(5) Exclusive release processing for the file name of the load module library with generation. According to the present invention, in the above process (2), a generation selection process for execution or a generation selection process for update is performed. Further, in the processing of (4) above, the control table releasing process for ending the execution or the control table releasing process for ending the update is performed. The process flow will be described below.

FIG. 6A is a diagram showing a processing flow for selecting a generation for execution. 6A to 6G are processes executed by the automatic generation switching mechanism 13, and FIG. 6H is a process executed by the usage status monitoring mechanism 14.

(A) From the route control table 20 shown in FIG.
The generation management table meta 21 is taken out. (b) The pointer to the generation management table 18 of the minimum generation / minimum level is extracted from the generation management table meta 21.

(C) The following processing for the generation management table 18 is repeated in ascending order up to the maximum level of the maximum generation. (d) Check the generation number in the generation management table 18,
Determine if it is a user-specified generation. If it is not the user-specified generation, the next generation management table is searched by process (c).

(E) to (g) Within the user-specified generation, the usage of the usage status management table 15 is sequentially examined from the maximum level to the minimum level, and the latest level that is not being updated is selected. (h) “Usage generation”, “user”, and “use (execution)” are recorded in the usage status management table 15.

(I) Information on the selected generation and level is returned to the calling source, and the processing ends. FIG. 6B shows the control table release processing by the usage status monitoring mechanism 14 when the module execution is completed.

When the execution of the program is completed, the usage status monitoring mechanism 14 uses the usage status management table 15
Delete the records of "generation of use", "user", and "use (execution)".

FIG. 7A is a diagram showing a flow of generation selection processing for updating. 5A to 5E are processes executed by the automatic generation switching mechanism 13, and FIG. 5H is a process executed by the usage status monitoring mechanism 14. Also,
(f) and (g) are executed as an extension of a combined editing program (not shown) called a linker that creates a load module.

(A) From the route control table 20 shown in FIG.
The generation management table meta 21 is taken out. (b) The pointer to the generation management table 18 of the minimum generation / minimum level is extracted from the generation management table meta 21.

(C) The following processing for the generation management table 18 is repeated in ascending order up to the maximum level of the maximum generation. (d) Check the generation number in the generation management table 18,
Determine if it is a user-specified generation. If it is not the user-specified generation, the next generation management table is searched by process (c).

(E) The maximum level in the user-specified generation is extracted. (f) Raise one level and create a new level. (g) Perform link processing for the created new level.

(H) In the usage status management table 15, "use generation", "user", and "use (update)" are recorded. FIG. 7B shows the control table release processing by the usage status monitoring mechanism 14 when the module update is completed.

When the update of the program is completed, the usage status monitoring mechanism 14 determines from the usage status management table 15
Delete the records of "generation of use", "user", and "use (update)".

FIG. 8 shows an unnecessary level deletion processing flow by the usage status monitoring mechanism 14. The following processing by the usage status monitoring mechanism 14 operates as a patrol function, and is executed for a generation of a specific library, for example, when any processing request enters the generation management mechanism 12. It

(A) The following processing is performed from the (maximum level-1) level to the minimum level excluding the newest level in the designated generation. (b) Check the user field of the usage status management table 15 to see if there is a user of the corresponding usage generation (including the level number).

(C) If there is a user, skip the next process (d). (d) If there is no user, delete that level's load module for that generation.

(E) The process is repeated by returning to the process (a) until the process for the minimum level is completed. The level control within the generation as described above can be selected as a system option or an option for each load module library, and the user can arbitrarily select whether to perform the control according to the conventional technique or the control according to the present invention. It is even more useful to do so.

[0043]

As described above, according to the present invention,
Since the load module in operation can be modified without performing generation UP, it is not necessary to delete an old version or manage generations, and the efficiency of program development can be improved.

[Brief description of drawings]

FIG. 1 is a diagram illustrating the principle of the present invention.

FIG. 2 is a diagram showing a configuration example of a generation management table according to the embodiment of the present invention.

FIG. 3 is an explanatory view of an embodiment of the present invention.

FIG. 4 is an explanatory diagram of an embodiment of the present invention.

FIG. 5 is an explanatory view of an embodiment of the present invention.

FIG. 6 is a diagram showing a flow of generation selection processing for execution according to the embodiment of the present invention.

FIG. 7 is a diagram showing a flow of generation selection processing for updating according to the embodiment of the present invention.

FIG. 8 is a diagram showing an unnecessary level deletion processing flow according to the embodiment of the present invention.

FIG. 9 is an explanatory diagram of a conventional technique.

[Explanation of symbols]

 10 Processor 11 Program Loading Mechanism 12 Generation Management Mechanism 13 Generation Automatic Switching Mechanism 14 Usage Monitoring Mechanism 15 Usage Status Management Table 16 Generation Module with Load Module 17 Management Information 18 Generation Management Table 19-1 to 19-3 Load Module

Claims (1)

[Claims] 1. A generation-equipped load module library (16) storing configuration data of load modules of a plurality of generations and management information thereof, and a generation management mechanism for referring to and updating the generation-equipped load module library (16) 12)
And a program loading mechanism (11) for requesting processing to the generation management mechanism (12) and loading a program from the load module library with generation (16), the load module library with generation In the management information of (16), a generation management table (18) having an area for storing setting information about multiple levels for one generation of the load module is provided.
The generation management mechanism (12) selects the latest level of the specified generation in response to the read request of the load module by the program loading mechanism (11), and selects the latest level of the specified generation in response to the update request of the load module. Use to automatically create a new generation switching mechanism (13) and manage the usage status of load modules, and delete the previous level information if there are no users when multiple levels exist in one generation. An update processing system for a load module library with generation, which is provided with a status monitoring mechanism (14).