JPS59177664A - Compression processing system of shared library file - Google Patents

Abstract

PURPOSE:To minimize the number of broken members for abnormality by declaring exclusively the compression of idle areas of a shared library file, which plural users use, in every processing unit in accordance with acceptance of a resource managing means to execute the compression at any time. CONSTITUTION:A read processing part 2 issues a request to a resource managing part 1; and if it is permitted, the part 2 reads data from a shared file 5. When update of the file is requested from an update processing part 4, this request is permitted if the read processing is not performed, and the update is executed; but if the read processing is performed, the update is held until the read processing is terminated. When a compression processing part 6 requests the compression processing to the resource managing part 1, exclusive use is declared in every processing unit of compression to compress idle areas on condition that this request is accepted, and thereafter, input/output requests are accepted. The compression processing is performed similarly for all processing units. Thus, the library file which is updated frequently and is shared is compressed at any time, and the number of members broken at an abnormal ternination time is reduced to a maximum of one member.

Description

DETAILED DESCRIPTION OF THE INVENTION [Technical Field of the Invention] The present invention relates to a compression processing method for shared library files that are shared by multiple users. Compression processing is performed by making input/output requests wait only for members to be moved, and even during compression processing, parallel processing is possible for read-only processing for members other than the members to be moved in the processing unit. This relates to compression processing methods.

[Conventional technology and problems]

FIG. 1 is a diagram explaining an example of file member update processing,
FIG. 2 is a diagram illustrating a conventional shared file management system. In FIG. 2, 1 is a resource management unit, 2 and 3 are read processing, 4 is an update process, and 5 is a file.

Generally, files that can be directly read/written by O8 (operating system).

There are sequential files and partitioned files. Among them, the partitioned file is composed of a part called a member, which stores several mutually independent data groups, and a part called a directory, which has information about the valley members.

In such a partitioned file, when adding a new member or updating an existing member, the new member or updated member is stored in the free space following the last member. Take it away. For example, Figure 1 (4
), when updating member A in a file containing members A, , B, and C, update the member A as shown in Figure 1 (
As shown in B), updated member A is added after member B. Areas of members before update that are no longer needed as a result of updating in this way, or areas of members that have been deleted, remain as free areas. When a file becomes punctured due to the addition of members, compression processing is performed to fill up the free space. When the compression process is performed, all empty @ areas are grouped together later, so the bank state of the file is released.

Incidentally, due to their nature, the load module library, professional 7jar library, CLi5t (command list), etc. are often shared and used by multiple users. In the past, compression processing could not be performed on a shared library file in which such libraries and the like were stored in the partitioned 7-isle unless the file was acquired exclusively. Therefore, we had to stop other jobs that used the library for read processing. For example, in FIG. 2, read processing 2 is executed by the resource management unit l.
If a new request is issued from the read processing 3 while the read processing from the file 5 is being executed after obtaining permission, the resource management unit 1 grants permission. In other words, even if readout process 3 is allowed, problems are unlikely to occur in the results of readout process 2. However, if the request from the update process 4 is rejected, if this is allowed and the update process for the file 5 is executed, the result of the read process 2 is no longer guaranteed, so the resource management unit 1 terminates the read process 2. Why don't you make me wait until I do? I refuse. Similarly, while the compression process is being executed, the processing order (
Even though there is a difference between directories and members, the location of the member pointed to by the directory may be different from the actual location of the member. In this way, when the correspondence between directories and members is inconsistent, the results of other processing requests (reading and writing) cannot be guaranteed. Furthermore, when writing, n may destroy the same number of another member.

As described above, in the past, the compression process required for replacing or updating modules could not be performed unless other jobs that only used the library for reading were also stopped. In particular, even though library files such as those mentioned above are mostly used only for reading, the cost of stopping jobs is high. Such a stop time may be several minutes or even several tens of minutes depending on the case. [Object of the Invention] The present invention is based on the above consideration, and even during the compression process, The purpose of this invention is to provide a compression processing method for shared library files that allows the use of read-only libraries.

[Structure of the invention]

To this end, the shared library file compression processing method of the present invention is provided with a compression processing means and a resource management means, and is composed of a plurality of members consisting of data groups and a directory containing information on the members. A compression processing method for a shared library file that performs a process of compressing the free space of a shared library file that is used in common, wherein the compression processing means, when performing the compression processing,
A request is issued to the resource management means, and on the condition that the request is accepted, for each processing unit that performs compression, the corresponding member is searched for, and exclusive use is declared to the resource management means for the relevant member to free up space. The resource management means is configured to compress the area, and then perform processing to declare that input/output requests will be accepted by the resource management means for the corresponding member, and perform compression processing for all members, and the resource management means: By issuing the above request, it is checked whether the shared library file is being used exclusively, and on the condition that it is not being used exclusively, the above request 7 is accepted and the above request is made to wait for process 7 that involves updating the directory. The exclusive use declaration makes the input/output request for the corresponding member wait, and the declaration that the input/output request will be accepted makes it possible to accept and accept the reference request 7 for the corresponding member, and the compression processing by the compression processing means ends. The present invention is characterized in that it is configured to perform a process that enables processing that involves an IJO update (see above).

[Embodiments of the invention]

Embodiments of the present invention will be described below with reference to the drawings.

FIG. 3 is a diagram showing the configuration of one embodiment of the present invention, FIG. 4 is a diagram illustrating the movement of members during compression processing to which the present invention is applied, and FIG. 5 is a diagram showing the compression processing unit and resources of the present invention. This is a diagram explaining processing by the management unit. In FIG. 3, 1 to 5 indicate those corresponding to FIG. 2, and 6 indicates compression processing.

In FIG. 3, when the resource management unit], i'i:, permits the request for compression processing 6 and starts compression processing, for example, A
DD, DEiTE, RENAME, C0PY,...
. . . UPDATE, etc. are prohibited, processing that involves updating the directory of file 5 is made to wait, and input/output requests from members across compression processing units are rejected or instructed to wait. This is an example in which the request for read processing 3 is an input/output request from a member that spans compression processing units K, and the request for read processing 2 is an input/output request for a member that does not span compression processing units. For example, if file 5 is in the state shown in Figure 4 (5) and compression processing is performed, if the processing unit is trunk unit, trunk 1 is initially the processing unit, and the members that span this are A and A. and C, the resource management unit 1 instructs members A and C to reject or wait for their input/output requests. When compression processing is performed on trunk 1, the state shown in FIG. 4(B) is reached. Therefore, let's look at track 2 next.

Since member B falls under the category spanning processing unit K, the resource management unit 1 instructs member B to reject or wait for the input/output request.

Processing by the compression processing unit (compression processing 6) and resource management unit 1 of the present invention will be explained with reference to FIG. 5. O■ The compression processing unit issues a read request to the resource management unit. Next, process 7 of ■
Line 9゜■' The resource management unit checks whether exclusive use is being used, and if exclusive use is found, it is rejected, and if not, it is accepted. If the receiver is attached, it is Buileff) IJ
〇■ The compression processing unit checks whether the request in ■ has been rejected (exclusive use, that is, writing is in progress).

If Yes, the process is terminated, and if No (D), process 2 is performed.

■ The compression processing unit searches for members that span a processing unit (for example, a tiger). Next, perform the process (■).

■ The compression processing unit declares to the resource management unit the exclusive use of the corresponding member obtained through the process of (■). Next, the process (2) is performed.0 (2)' The resource management unit instructs to reject or wait for the input/output request of the member whose exclusive use has been declared by the compression processing unit.

■ The compression processing unit performs the processing of ■ on the 0th order to compress the free area at line 90 ■ The compression processing unit declares to the resource management unit that it will accept requests from the corresponding men who have declared exclusive use in the processing of ■. do.

Next, perform the process (■).

Make it.

■ Check whether compression processing has been performed on all members.

In the case of Yes, the process ``■'' is performed, and in the case of No, the process returns to the process ``■''.

■ Renewal of Buileff in the Resource Management Department ``Carry out termination processing such as asking for forgiveness.

In the processing described above, for example, the processing unit of the processing ① may be a record. In addition, in the process from ■ to ■, the member with the smallest starting TTR (1-) is given exclusive use and the free space is compressed, and the member with the largest starting TTR is moved. When the process is finished, the process of ``2'' is performed and then the termination process is performed. However, the processing does not necessarily have to be carried out in this order, as long as it is possible to compress all members by carrying out the processing of (1) to (3) for each processing unit.

〔Effect of the invention〕

As is clear from the above description, according to the present invention, library files that are frequently updated and are used for shared use can be compressed at any time, and the compression process is performed sequentially for each processing unit. At most, only one track and one member are destroyed in the event of abnormal termination, the capacity of the backup file can be small, and recovery can be performed quickly.

[Brief explanation of drawings]

FIG. 1 is a diagram explaining an example of file member update processing,
Figure 2 is a diagram explaining the conventional shared file management method.
3 is a diagram showing the configuration of one embodiment of the present invention, FIG. 4 is a diagram illustrating the movement of members during compression processing to which the present invention is applied, and FIG. 5 is a diagram showing the compression processing section and It is a figure explaining the processing by a resource management part. 1... Resource management section, 2 and 3... Read processing, 4.
...Update processing, 5.File, 6.Initial loading processing, 7.Compression processing.

Claims (1)

[Claims] A process for compressing the free space of a shared library file that is provided with a compression processing means and a resource management means, and is composed of a plurality of members consisting of data groups and a directory containing information on the members. In this shared library file compression processing method, the compression processing means issues a request to the resource management means when performing the compression processing, and the request is not accepted. For each processing unit that performs compression, search for the corresponding member, declare exclusive use to the resource management means for the corresponding member, compress the free space, and then issue an input/output request to the resource management means for the corresponding member. The resource management means is configured to perform processing to declare that the shared library file will be accepted, and perform compression processing for all members, and the resource management means determines whether or not the shared library file is being used exclusively by issuing the request. The above request is accepted on the condition that it is not being used exclusively, and the process that involves updating the directory is made to wait.The above exclusive use declaration makes the input/output request of the corresponding member wait, and the above input/output request is made to wait. By declaring that the reception will be accepted, the reception will be able to make reference requests for the above-mentioned member, and
Compression of a shared library file characterized in that when the compression processing by the compression processing means is completed, the processing that involves the updating of the directories is performed. Processing method.