JPH04358238A - Generation managing method for source program - Google Patents

Abstract

PURPOSE:To prevent the generation management of a user from being failed by easily updating a generation or turning back to a required generation only according to a logical member name and a generation number designated by the user. CONSTITUTION:While defining plural files as one set body, a distributed and sequentially programmed file manages the respective files as members in the set body. A real image 2 has the file of real member names which are conscious of on a system side. A logical image 3 has the file of logical member names. A management part 4 manages real member names, pointers to real members, generation member names and generation numbers so that they can be correspondent one and another. A generation managing function 5 manages one generation of a source program file corresponding to two members.

Description

[Detailed description of the invention]

0001

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a generation management method for source programs used in information processing systems.

0002

2. Description of the Related Art In a conventional source program generation management method for an information processing system, it is necessary to prepare media for each generation and for the administrator to be explicitly aware of the information on those media.

0003

[Problem to be Solved by the Invention] In the conventional source program generation management method, media for the number of generations are prepared and managed individually, so in order to avoid the complexity of media management, it is necessary to This method has the disadvantage that the number cannot be increased and that errors are likely to occur because the person in charge must be aware of the media's information regarding the generation.

0004

[Means for Solving the Problems] The source program generation management method of the present invention is a divided sequential file system in which a plurality of files are made into one aggregate, and each file is managed as a member in the aggregate. In addition, the management section has an additional information area that manages logical member names and generation numbers in addition to the actual member names that are recognized on the system side.
It is configured by having a generation management function that manages one generation of a source program file by associating it with one member.

[0005]

Embodiments Next, embodiments of the present invention will be described with reference to the drawings.

FIG. 1 is a functional block diagram showing an embodiment of the source program generation management method of the present invention. As shown in FIG. 1, a user program 1 is a source program that a user attempts to create or update. Further, the real image 2 is an image in which an actual file is stored. 2A0 is the 0th generation physical image of logical member name A, 2A1 is the 1st generation physical image,
2An is the nth generation physical image.

On the other hand, the logical image 3 is a logical image of the source program file for the user. 3A0 is the 0th generation of logical member name A, and 3A1 is the 1st generation.
Generations, . . . 3An are respective logical images of the n-th generation. Note that 2B0 is the 0th generation logical image of logical member name B, and 3B0 is the 0th generation logical image of logical member name B.

[0008]Furthermore, the division type sequential file management unit 4
is set with information for managing source program files as members.

FIG. 2 is an information configuration diagram showing an example of information in the distributed sequential file management section 4 of FIG. 1. As shown in FIG. As shown in FIG. 2, this management unit 4 stores real member names 41 and pointers 42 to the members, which are file management level information.
and a field in which a logical member name 43 and a generation number 44 of the member as additional information are set.

Note that the actual member name 41 is given based on predetermined additional criteria and is not known to the user. The user then selects the logical member name 43 and its generation number 44.
The source program file can be accessed using only this information.

Therefore, the generation management function 5 manages the source programs of each generation by associating them with the members of the divided sequential file.
The logical member name 43 and generation number 44 are used.

In actual processing, the logical member name 43 and generation number 44 specified by the user are received, a member that matches them is specified, and the real member name 41 of the management unit 4 corresponding to the member is specified. The file is accessed based on the information of the member pointer 42 and the member pointer 42.

The operation of this embodiment will be explained below with reference to each figure.

When the user program 1 accesses the 0th generation whose member name is A, the generation management function 5 performs the following steps.
Read the management section 4 of the divided sequential file, search for a member whose logical member name 43 is A and whose generation number 44 is 0,
Obtain the 0th generation source program of logical member A. Similarly, for the nth generation, the logical member name 43 is A,
The member 2An whose generation number 44 is n is searched to obtain the nth generation source program. Note that source programs of other generations can also be accessed in the same way. In this way, the generation is recognized using the generation number 44.

At this time, the following two methods can be considered as examples of member management methods. One way is to
The other method is when all generations retain the complete source program content, and only the first generation retains the complete content as a mask, and the second and subsequent generations retain only the changed content. It is.

In the former case, the member searched by the above-mentioned method directly indicates the specified generation, but in the latter case, the subsequent parts are updated up to the specified generation based on the oldest master. obtained by

For example, when obtaining the latest nth generation whose member name is A, the former corresponds to the logical member 3An as it is to the real member 2An, while the latter corresponds to the master real member 2A0. A logical member 3An is obtained by updating up to 2A1, 2A2, . . . 2An.

Therefore, in the former case, there is an advantage that the speed is fast when accessing any generation, but a disadvantage is that the amount of files used increases when updates are frequently performed. There is.

[0019] In the latter case, although the file size may be small, in order to access members of a certain generation, it is necessary to sequentially change changes from the master member. The disadvantage is that it takes time to obtain the

[0020] Therefore, as a file management method, these methods can be used depending on the purpose, taking the above points into consideration.

[0021]

[Effects of the Invention] As explained above, the source program generation management method of the present invention allows generation to be easily updated and required generations to be updated simply by using the logical member name and generation number specified by the user. This has the effect of preventing errors in generation management by the user. Furthermore, since each generation of source programs is managed as a member of one file, it is possible to expect a reduction in the number of media.

[Brief explanation of the drawing]

FIG. 1 is a functional block diagram showing an embodiment of a source program generation management method according to the present invention.

FIG. 2 is an information configuration diagram showing an example of information in the management unit 4 of the divided sequential file in FIG. 1;

[Explanation of symbols]

1 User program 2 Real image 2A0, ~ 2An, 2B0 Physical image 3
Logical image 3A0, ~3An, 3B0 Logical image 4
Management section 41 Real member name 42 Pointer 43 Logical member name 44 Generation number 5 Generation management function

Claims (1)

[Claims] [Claim 1] A plurality of files are set as one collection,
For split-type sequential files that manage each file as a member within the collection, an addition is added to the management section that manages logical member names and generation numbers in addition to the actual member names that are recognized on the system side. A source program generation management method characterized by having an information area and a generation management function for managing one generation of a source program file by associating it with one member.