JP2626450B2 - Backing store usage calculator - Google Patents

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a library for loading a load module (pre-initialized load module) when a normal load module (a load module generated at the time of program linking) is developed in a virtual space before executing the program. Virtual storage system (using a virtual storage system) that is registered in the backing store for use and loads the pre-initialized load module from the backing store for library to the virtual space at execution (memory and backing store used during program execution) when loading the program Information processing system)
In particular, the present invention relates to a backing store usage calculating device that calculates a backing store usage to be requested when acquiring a backing store resource at the time of loading a program.

[0002]

2. Description of the Related Art Conventionally, the above-mentioned "calculation of backing store usage" has been performed by the following two methods.

In the first method, the size of a compile unit group generated at the time of compiling a program and the size of a normal load module generated at the time of program link are calculated, and the size of such a compile unit group and the size of a load module are calculated. In addition, a certain margin was added to calculate the necessary backing store usage.

When a normal load module is developed in a virtual space, a division loss (loss due to page garbage or the like) occurs due to division into pages and segments, and a new part for managing pages and the like is generated. Table groups also occur, which requires more backing store usage during actual program execution than the backing store usage based solely on the size of the compilation units and load modules calculated at program compilation and program linking. It is general. For this,
The above-described “addition of a certain margin” is performed.

In the second method, when a program is loaded from a library backing store of a pre-initialized load module into a runtime virtual space, the amount of backing store actually considered necessary is reduced by JCL (Jo).
b Control Language) or the like, and the backing store usage indicated by the specification is “backing store usage to be requested”
It was certified (calculated) as

[0006]

In the above-mentioned conventional technology (technology relating to calculation of backing store usage),
There were the following problems.

In the first method, it is difficult to accurately determine a “certain margin” to be added when the backing store usage is calculated. The required backing store usage is different, and the difference causes inconvenience. In other words, if a calculation that is larger than the actually required backing store usage is made, backing store resources are wasted, and if a calculation that is too small is made, a program based on the shortage of backing store resources is used. Execution interruption occurs.

In the second method, since an external specification indicating the amount of backing store used by JCL or the like is required, an extra man-hour for performing the specification is required.

SUMMARY OF THE INVENTION In view of the foregoing, it is an object of the present invention to accurately calculate a backing store usage required at the time of program execution, and to request a necessary and sufficient (optimal) backing store usage to perform backing. It is an object of the present invention to provide a backing store usage calculating device which makes it possible to acquire store resources (in this case, it is not necessary to specify the backing store usage from outside).

[0010] As an example of a conventional technique for effectively using a backing store resource in a virtual storage system,
There is a patent application relating to “JP-A-63-201721 (program link system)”. This conventional technique collects rewritable pages by sequentially arranging segments having the same attribute at the time of program linking, and creates only a file for rewritable pages on the backing store at the time of program execution. The purpose is to make effective use of backing store resources. Therefore, the point of view differs between this conventional technique and the present invention which aims at effective use of the backing store resources based on the calculation of the optimal backing store usage.

[0011]

SUMMARY OF THE INVENTION A backing store usage calculating device according to the present invention is a virtual storage system for loading a pre-initialized load module from a library backing store into a virtual space at runtime. Backing store usage calculating means for calculating the backing store usage required when executing the program of the pre-initialized load module based on the size of the pre-initialized load module developed on the virtual space by the means,
Backing store usage registering means for registering the backing store usage calculated by the backing store usage calculating means in the library backing store in association with the pre-initialized load module, and a library of the pre-initialized load module When loading a program from the backing store to the run-time virtual space (this "
(When the first program is loaded)) , the backing store usage corresponding to the pre-initialized load module and the backing store usage registered in the library backing store by the backing store usage registering means is obtained. Backing store usage requesting means for requesting the backing store usage when acquiring the backing store resource.

Further, the backing store usage calculating apparatus of the present invention is a virtual space development / backing store in a virtual storage system for dynamically loading a plurality of pre-initialized load modules from a library backing store into a virtual space at the time of execution. Calculating a backing store usage required when each of the plurality of pre-initialized load modules is executed on the basis of the size of each of the plurality of pre-initialized load modules developed on the virtual space by the registration means; Backing store usage calculating means, and a backing store registering the backing store usage calculated by the backing store usage calculating means in the library backing store in association with each of the plurality of pre-initialized load modules. Executing from the storage store usage registering means, the load module name designation input means for receiving the designation of the load module name to be calculated for the plurality of pre-initialized load modules from the outside, and the library backing store of the plurality of pre-initialized load modules When a dynamic program is loaded into the virtual space (this "program loading"
During loading of a ram) , the backing store usage corresponding to some pre-initialized load modules specified by the calculation target load module name input by the load module name specification input means at the time of loading the backing store. A backing store usage amount that obtains some backing store usage amounts registered in the library backing store by the usage amount registration unit and requests an additional amount of the backing store usage amounts when acquiring backing store resources. Request means.

[0013]

Next, the present invention will be described in detail with reference to the drawings.

FIG. 1 is a block diagram showing a configuration of a virtual storage system including a first embodiment of a backing store usage calculating device according to the present invention.

This virtual storage system is a virtual space development /
It comprises a backing store registration means 1, a load module loading means 4, a virtual space 7, a library backing store 8, and a backing store usage calculating device of this embodiment.

The virtual space 7 is constituted by a memory and a backing store (a backing store for a library is generally used as the backing store), and is an execution space which is a virtual space used when executing a program. It is similar to spatiotemporal space. That is,
A normal load module (a load module generated at the time of program linking) is expanded on a virtual space 7 simulated as a virtual space at the time of execution to generate a pre-initialized load module (a load module when expanded on the virtual space). For this purpose, a virtual space 7 is provided.

The library backing store 8 includes a load module registration area 81 in which a pre-initialized load module is registered, and a backing store usage management table 8 corresponding to the load module registration area 81.
2 (a table in which the backing store usage required by the pre-initialized load module registered in the load module registration area 81 when executing the program is registered). Although not shown, the library backing store 8 includes a load module registration area 81 and a backing store usage management table 8.
There may be a load module registration area other than 2 and a backing store usage management table.

The backing store usage calculating device of this embodiment includes a backing store usage calculating means 2, a backing store usage registering means 3, and a backing store usage requesting means 5.

Note that “◎” in FIG. 1 indicates “start” and “end” of a series of processing flows formed by the operation of each means (also in FIG. 2 described later). Similar).

Next, with reference to FIG. 1, the operation of the virtual storage system including the backing store usage calculating device of this embodiment will be described.

First, the library backing store 8
The operation at the time of registering the pre-initialized load module into the server will be described.

The virtual space development / backing store registration means 1 develops a normal load module in a load module library (not shown) in the virtual space 7.

The virtual space development / backing store registration means 1 registers a pre-initialized load module which is a load module developed on the virtual space 7 in a load module registration area 81 in the library backing store 8. .

The above processing by the virtual space development / backing store registration means 1 is the same as the processing in the prior art.

The backing store usage calculating means 2 in the backing store usage calculating device is called by the virtual space expanding / backing store registering means 1 to determine the size of the pre-initialized load module expanded in the virtual space 7. Based on this, the amount of backing store used by the pre-initialized load module required at the time of executing the program is calculated. Since this calculation is performed based on the size of the pre-initialized load module developed in the virtual space 7, generation of a page garbage and the like and generation of a new table group for managing pages and the like are also considered. It becomes something. The backing store usage calculated in this way is the amount of backing store usage required when acquiring the backing store resource for the pre-initialized load module. Calculation "is possible.

The backing store usage registering means 3 in the backing store usage calculating device stores the backing store usage calculated by the backing store usage calculating means 2 in the backing store usage management corresponding to the load module registration area 81. Register in the table 82.

Second, library backing store 8
The operation when loading the pre-initialized load module registered in the load module registration area 81 in the virtual space (not shown) at the time of execution will be described.

The load module loading means 4 calls the backing store usage requesting means 5 in the backing store usage calculating device when loading the program of the pre-initialized load module in the load module registration area 81.

The backing store usage request means 5 stores the backing store usage (in the backing store usage management table 82 corresponding to the load module registration area 81 in which the pre-initialized load module to be loaded with the program is registered). Obtain (refer to) the backing store usage amount accurately calculated as described above, and request the backing store usage amount when acquiring the backing store resource for the pre-initialized load module.

As a result, when acquiring the backing store resource for the pre-initialized load module, it is possible to request an optimum (not too large, not too small, and sufficient necessary) backing store usage. Moreover, at this time, there is no need to specify the backing store usage from outside.

The load module loading means 4
The pre-initialized load module in the load module registration area 81 is loaded into the runtime virtual space having the backing store obtained based on the above request.

FIG. 2 is a block diagram showing the configuration of a virtual storage system including a second embodiment of the backing store usage calculation device of the present invention. The components in FIG. 2 that correspond to the components in FIG. 1 are denoted by the same reference numerals as those in FIG. However, the components in FIG. 1 and the components in FIG. 2 denoted by the same reference numerals do not always perform the same processing.

This virtual storage system is a virtual space development and
It comprises a backing store registration means 1, a load module loading means 4, a virtual space 7, a library backing store 8, and a backing store usage calculating device of this embodiment.

Like the virtual storage system including the backing store usage calculating device of the first embodiment, the virtual storage system including the backing store usage calculating device of the present embodiment is simulated in the virtual space at the time of execution. In order to generate a pre-initialized load module by expanding a normal load module on the virtual space 7,
Is provided.

The library backing store 8 includes load module registration areas 81-1, 81-2,..., 81-n in which pre-initialized load modules are registered.
(N is a positive integer of 2 or more) and backing store usage management tables 82-1, 82-2,... Corresponding to the load module registration areas 81-1, 81-2,.
82-n (load module registration areas 81-1, 81-
2,..., 81-n are stored in the backing store used by the pre-initialized load module when the program is executed. Although not shown, the library backing store 8 has load module registration areas 81-1, 8
, 81-n and the backing store usage management tables 82-1, 82-2,..., 82-n, there may be load module registration areas and backing store usage management tables.

The backing store usage calculating device of this embodiment comprises a backing store usage calculating means 2, a backing store usage registering means 3, a backing store usage requesting means 5, a load module name designation input means 6, It is comprised including.

Next, with reference to FIG. 2, the operation of the virtual storage system including the backing store usage calculating device of this embodiment will be described.

In the virtual storage system including the backing store usage calculating device of the present embodiment, a plurality (n) of pre-initialized load modules are transferred from the library backing store 8 in order to realize dynamic linking and overlay. It shall be dynamically loaded into a run-time virtual space (not shown).

First, the library backing store 8
The operation at the time of registering the pre-initialized load module into the server will be described.

The operation at this time is the same as the operation in the first embodiment. However, in this embodiment, a plurality of pre-initialized load modules to be dynamically loaded based on a dynamic link or the like are stored in the load module registration area 8 in the library backing store 8.
, 81-n, and a plurality of backing store usages corresponding thereto are stored in the backing stores corresponding to the load module registration areas 81-1, 81-2,..., 81-n. Usage amount management tables 82-1, 8
2-2,..., 82-n.

Second, library backing store 8
, Load module registration areas 81-1, 81-2,
, 81-n, the operation when dynamically loading a plurality of pre-initialized load modules into the virtual space at the time of execution will be described.

The load module load means 4 calls the backing store usage request means 5 in the backing store usage calculation device when a plurality of pre-initialized load modules are dynamically loaded.

The backing store usage requesting means 5 prompts the load module name designation input means 6 to externally input a "calculation target load module name designation" described later.

The load module name designation input means 6
“Identification information (load module name) of a pre-initialized load module included in a combination that is likely to require the largest backing store usage among combinations of pre-initialized load modules that are loaded simultaneously, that is, A load module name designation indicating "the load module name of the pre-initialized load module to be calculated for the backing store usage to be requested" is externally received. Here, the input “from outside” means a direct instruction from the user, an input by the JCL, or the like.

Further, the load module name specification input means 6 passes the input calculation target load module name specification to the backing store use amount requesting means 5.

The backing store usage requesting means 5 includes several load module registration areas (load module registration areas 81-1 and 81-1) for storing some pre-initialized load modules specified by the calculation target load module name designation. ,..., 81-n) (some of the backing store usage management tables 82-1, 82-2,..., 82-n). ) Is acquired (referenced) and the amount of backing store usage is requested when acquiring backing store resources.

Thus, even when a dynamic program load of a plurality of pre-initialized load modules (a program load from the library backing store 8 to the execution-time virtual space) is performed to realize a dynamic link or the like. In obtaining the backing store resources for the plurality of pre-initialized load modules, it is possible to accurately calculate the backing store usage required when executing the program, and to request the optimum backing store usage. become.

[0048]

As described above, according to the present invention, when a pre-initialized load module is registered in a library backing store, the amount of backing store used by the pre-initialized load module is calculated, and the backing store usage is calculated. Register the amount in the library backing store corresponding to the pre-initialized load module, and acquire the backing store usage when loading the pre-initialized load module program from the library backing store to the runtime virtual space By performing (referencing), it is possible to accurately calculate the amount of backing store usage required at the time of program execution, and to obtain a necessary and sufficient (optimal) backing store usage and acquire backing store resources. so , There is an effect that it is possible to effectively utilize the backing store resources in a virtual storage system (also reduced interrupting program execution due to lack of backing store resources). In addition, this effect is
A program related to the pre-initialized load module
This is the effect obtained from the first execution of the ram.

Further, since there is no need to specify the backing store usage from the outside, there is an effect that an extra man-hour for specifying the backing store is not required.

Further, even if the designation of the load module name to be calculated is input, even if the dynamic loading of a plurality of pre-initialized load modules for realizing a dynamic link or the like is performed, the optimum backing store is obtained. There is an effect that the backing store resource can be obtained by requesting the usage amount. In this case, it is necessary to input the name of the load module to be calculated from the outside.However, compared to the man-hour to specify the amount of backing store usage of some pre-initialized load modules, In general, the number of steps required to specify the load module name to be calculated is small (for example, the number of steps to create the JCL indicating the load module name specification having the load module name is calculated by adding the backing store usage. The number of steps is usually smaller than the number of steps for creating a JCL indicating a designation having an amount), so that the above-described effect is significant.

[Brief description of the drawings]

FIG. 1 is a block diagram showing a configuration of a virtual storage system including a first embodiment of a backing store usage calculating device of the present invention.

FIG. 2 is a block diagram illustrating a configuration of a virtual storage system including a second embodiment of the backing store usage calculation device of the present invention.

[Explanation of symbols]

1 virtual space development / backing store registration means 2 backing store usage calculation means 3 backing store usage registration means 4 load module loading means 5 backing store usage request means 6 load module name designation input means 7 virtual space 8 library backing store , 81-n Load module registration area 82, 82-1, 82-2, ..., 82-n Backing store usage management table

Claims (2)

(57) [Claims] 1. A virtual storage system for loading a pre-initialized load module from a backing store for a library into a virtual space at the time of execution, wherein the pre-initialized load module expanded on the virtual space by virtual space expansion / backing store registration means. Backing store usage calculating means for calculating a backing store usage required when executing the program of the pre-initialized load module based on the size; and backing store usage calculated by the backing store usage calculating means. Backing store usage registration means for registering in the library backing store in association with the pre-initialized load module, and a library backing store for the pre-initialized load module When the program is loaded into the runtime virtual space, the backing store usage corresponding to the pre-initialized load module and the backing store usage registered in the library backing store by the backing store usage registering means are obtained. Backing store usage calculating means for requesting the backing store usage when acquiring the backing store resource. 2. A virtual storage system for dynamically loading a plurality of pre-initialized load modules from a library backing store into a virtual space at runtime at the time of execution. Backing store usage calculating means for calculating, based on the size of each of the plurality of pre-initialized load modules, a backing store usage required for executing each program of the plurality of pre-initialized load modules; Backing store usage registering means for registering each backing store usage calculated by the usage calculating means in the library backing store in association with each of the plurality of pre-initialized load modules; and A load module name specification input means for externally receiving a calculation target load module name specification for the initialized load module, and when dynamically loading a program from the backing store for libraries of the plurality of pre-initialized load modules to the execution-time virtual space. A backing store usage corresponding to some pre-initialized load modules specified by the calculation target load module name input by the load module name specification inputting means, and A backing store usage that obtains some backing store usage registered in the backing store and requests an additional amount of the backing store usage when acquiring backing store resources. A backing store usage calculating device, comprising: a volume requesting means.