JPS6042494B2 - Program module management method - Google Patents

Description

[Detailed Description of the Invention] The present invention provides a program/module management method, particularly for program modules whose levels have been updated in chronological order, for example, due to addition of functions or specification changes. The modified contents are saved in chronological order and a version level is assigned, and the level update result corresponding to the given version level can be downloaded from the program.
This relates to a program/module management method that makes modules reproducible.

In program development and maintenance work, it is necessary to update the level of the program or module by adding functions or changing specifications.

In such cases, the administrator of the library that stores the various program modules would conventionally transfer the level update results back to the original library if there is free space in the large memory where the program modules are stored. If there is no free space, the original library is backed up, for example, on a magnetic tape, and the level update results are stored as the next library in a large capacity memory. For this reason, as shown in FIG. 1, as the content of the original program module 1-1 is updated, typically the content of the program module on the large capacity memory is updated to the second level. level 1
-2 content, 3rd level 1-3 content, 4th level 1-
4, the contents of the programs and modules corresponding to each level must be saved, so magnetic tape is used as a backup.
It was necessary to preserve them like 2-1, 2-2, 2-3, 2-4... In other words, even if the program or module provided to User A at a certain point had content at the second level, even if the level of the program or module has been updated to the third or fourth level since then, For user A to detect obstacles, etc., it is necessary to reproduce the contents of the second level.

For this purpose, based on the version level given corresponding to the second level program module provided to User A, the magnetic tapes 2-1 and 2 are used to reproduce the contents of the second level. -2, 2-3, etc. For this reason, it is generally essential to have multiple libraries for a single program module. The purpose of the present invention is to reduce the number of libraries by solving the above problems, and the program module management method of the present invention is a program module management method that manages each updated level of a single program module in a library , the content of the original program ●module, the content of the second level corresponding to the content of the modification that updated the content of the content of the original program●module, and the content of the modification that updated the content of the second level are stored on the large capacity memory. It is configured to sequentially store the contents of the third level and..., and to store the symbol corresponding to the version level p set at any predetermined time in association with the contents of the first label, and for each ranking. The version level q of a given rank is configured to remember the version level of
Determine the contents of the j-th level that is associated with the above version
The program module is characterized in that a program module corresponding to the j-th level is reproduced by the contents of the module, the modified contents of the first level, the modified contents of the second level, and the modified contents of the j-th level. There is.

This will be explained below with reference to the drawings. Fig. 2 shows a schematic configuration of an embodiment of the present invention, Fig. 3 shows a mode of setting a version level in the present invention, and Fig. 4 shows a mode of setting a version level in the present invention. An example embodiment for reproducing a corresponding one level program module is shown.

In FIG. 2, 3 is a version level storage unit, 4-
N and 4-m are large-capacity memories, and although they are shown as two large-capacity memories in the illustration, they may be a single large-capacity memory if necessary, and 5-N and 5-m are large-capacity memories, respectively. In the backup magnetic tape, 6-N and 6-m each represent a directory portion on the large-capacity memory, and 7-N and 7-m each represent a data portion on the large-capacity memory.

In the illustration, (4) #n program module and #m program module.
The modules are each provided to user A at the first level, that is, the original program ● module with a version ● level RlJ set, and (B) #n program ● module is updated at the second level N2 and updated at the third level N3. At the stage when the update has been performed and when the second level M2 update has been performed for the #m program module, the version level R2J is set and user B is provided, and (C) the #n program・As for the module, when the fourth level N4 update has been performed and #m
For the program module, when the third level M3 has been updated, the version level R3J is set and provided to user C, and (2) for the #n program module, the fifth level N5 is further updated. At the stage when program module #m has been updated to the fourth level M4 and the fifth level M5, the version level R4J is set and provided to user D. It represents the state in which

In this case, for example, the version provided to user C above.
Corresponding to the program of level R3J, for the #n program module, a symbol version level R3 is given to the directory section corresponding to the fourth level N4, and for the #m program● module, the symbol of version level R3 is given to the directory section corresponding to the fourth level N4. A symbol of version level R3 is given to the directory section corresponding to .

In the illustrated case, the directory section 6-n(7)n1
The original program ● module of the #n program module is stored in the data section pointed to by , and the first
Contents of corrections made by level updates are stored, and...
ing. In addition, the original program ● module of the #m program ● module is stored in the data section pointed to by m1 of the directory section 6-m, and the directory section 6-m (
7) The data section pointed to by M2 stores the content of corrections due to the level update of the first level, and so on. Further, the contents of the large-capacity memories 4-n and 4-m are backed up to magnetic tapes 5-n and 5-m as necessary.
FIG. 3 shows a mode of setting the version level in the present invention, and will be described below by taking as an example a case where the version level R4 shown in FIG. 3 is set.

(1) First, for example, a program to be provided to user D.
Check if the module exists in the library,
If the desired #n program ● module exists, extract it.

(2) Regarding the #n program module, the version number is stored in N5 in the directory section 6-n corresponding to the latest level in the #n program module, that is, the fifth level in the case shown in FIG. -Set the symbol R4J corresponding to the level.

(3) Next, if #m program module exists in the library, extract it.

(4) For the #m program ● module, set the symbol R4J corresponding to the version ● level in M5 in the directory section 6-m, corresponding to the latest level in the #m program module, that is, the fifth level. do.

(5) When the process of setting the version level symbol R4J corresponding to all the desired program modules in the library is completed, the version files existing in the library are
A version level and a symbol corresponding to the version level are set in the level storage unit 3.

For example, ■02L04 and R4J are set. (6) In this state, the desired program module is provided to user D, and it is recorded that the program module provided to user D is at the version level "VO2LO4, r4J".

After that, if necessary, use the #n program module or #
It goes without saying that the level of the m program module is updated. FIG. 4 shows an embodiment of the present invention for reproducing a program module of a corresponding level based on a certain version level. The following problem occurred in user C, and the program provided to user C ◆Module version●Level゜6■02L0
An example of reproducing a corresponding program module based on 3.r3J' will be explained. (7) First, check that the symbol corresponding to the version level is R3J.

(8) The program module to be output to reproduce is #
n program module is found in the library.

(9) Then, the directory section 6-n is searched and the pointer N4 having the symbol R3 is extracted.

00 Then, based on pointer N4, pointer Nl,
Data section 7- pointed to by n2, n3, n4
Output the contents of n.

(11) Again, by processing similar to the above processing (7), (8), (9), and Ql, for the #m program Output the contents of m.

As explained above, according to the present invention, as shown in FIG. 3, it is sufficient to have a single library for a single program module, and the library manager can provide the program module to the user. Version
It is enough to set the level.

[Brief explanation of the drawing]

FIG. 1 is an explanatory diagram illustrating a conventional program/module management system, and FIG. 2 shows a schematic configuration of an embodiment of the present invention. FIG. 3 shows an embodiment in which a version level is set in the present invention, and FIG. 4 shows an embodiment in which a program module at a corresponding level is reproduced based on a certain version level in the present invention. In the figure, 3 represents a version level storage section, 4 a large capacity memory, 5 a backup magnetic tape, 6 a directory section on the large capacity memory, and 7 a data section on the large capacity memory.

Claims (1)

[Claims] 1 In a program module management method that manages each updated level of a single program module in a library, the content of the original program module and the modified content that updated the content of the original program module are stored in large-capacity memory. The contents of the second level corresponding to the contents of the second level corresponding to the contents of the third level corresponding to the revised contents updated to the contents of the second level, etc. are sequentially stored, and the version/level p set at any predetermined time is stored. It is configured to store the corresponding symbol in association with the content of the i-th level, and is configured to store the version level of each rank, and the above-mentioned code is stored in correspondence with the version level q of a given rank. The content of the j-th level associated with version level q is determined, and the content of the original program module, the modified content of the first level, the modified content of the second level, and the modified content of the j-th level are determined. A program module management method characterized in that a program module corresponding to a j-th level is reproduced depending on the program module.