JPH04295928A - Program startup method - Google Patents

Abstract

(57) [Summary] This bulletin contains application data before electronic filing, so abstract data is not recorded.

Description

[Detailed description of the invention]

0001

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a method for starting a program.

0002

[Prior Art] Conventionally, load modules are registered on an auxiliary storage device, and each time a startup request is made, a load module is input from the auxiliary storage device to start a program.
It was expanded to the main memory and the program was started.

In the conventional method described above, even in the case of a frequently used load module, each time a program startup request is made, the load module is input from the auxiliary storage device in which the load module is registered, and the load module is transferred to the main storage device. Since the program is expanded and the program is started, there is a drawback that the program startup efficiency is poor.

0004

SUMMARY OF THE INVENTION An object of the present invention is to improve the startup efficiency of a program by starting the program by inputting it from an auxiliary storage device even if the load module is frequently used at startup.

[0005]

[Means for Solving the Problems] The program starting method of the present invention expands the load module on the auxiliary storage device onto the main storage device when starting the program, and stores the load module on the auxiliary storage device in a computer system that executes the program. A load module main memory storage means for storing load modules registered in the main memory on the main memory, load modules that have already been executed, and the load modules stored on the main memory by the load module main memory storage means. stores/manages the load module name of the loaded load module, whether or not it is stored on the main storage device, the original auxiliary storage device name, etc., and determines the load module to be stored in the main storage device based on the frequency of use; a load module management means that issues a storage request to the load module main storage storage means; a load module registered on the auxiliary storage;
Alternatively, the present invention is characterized by comprising a program execution means for expanding the load module stored in the load module main storage storage means into an executable format and executing it.

[0006]

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

FIG. 1 is a block diagram showing an embodiment of a computer system to which the program starting method of the present invention is applied. In FIG. 1, the present embodiment is composed of a terminal 1 and a host computer 2. In the host computer 2, in addition to an auxiliary storage device 6 and a main storage device 7, a load module main storage device is stored as a functional unit. Means 3, load module management means 4, and program execution means 5 are provided. Further, the auxiliary storage device 6 stores files including a plurality of load modules A, B, etc., and the main storage device 7 stores a load module management area 8, a load module storage area 9, and a load module expansion area 10.
is provided. The functions of the main parts are as follows. Terminal 1: Operated by an operator to request startup of a program. Load module main storage storage means 3; load module management means 4 to main storage 7
It has a function of storing the load module in the specified file on the auxiliary storage device 6 in the load module storage area 9 on the main storage device 7 when there is a request to store the load module. Also, load module management means 4
When there is a request to delete a load module on the main storage device 7 from
Delete from above. Load module management means 4; manages information for automatically storing load modules executed on the system on the main storage device 7, and determines which load modules to store on the main storage device 7; A storage request is made to the load module main storage storage means 3. More specifically, as shown in FIG. 2, the overall size of the load module storage area 9, the size of the free area, the number of expansion modules, the module name of the load module, the auxiliary storage device name, the file name, the load module storage area Management information such as the above address, size, number of executions, etc. is stored and managed in the load module management area 8, and when the load module main storage storage means 3 stores the load module and executes the program. It provides necessary information when the means 5 operates. Program execution means 5: When a request to start a program of a specific load module is made from the terminal 1, if the load module is already stored in the load module storage area 9, the load module is transferred from the load module storage area 9 to the load module deployment area. If it is a load module that is not stored in the load module storage area 9, it is read from the auxiliary storage device 6, expanded in the load module expansion area 10, and activated.

[0008] The operation of the above embodiment will now be explained in different cases. (1) Execution of a load module (in the case of a load module already stored in the main memory) A program startup request for a load module stored in the auxiliary storage device 6, for example load module A, is sent from the terminal 1 to the host computer 2. Once issued, this program activation request is accepted by the program execution means 5. Upon receiving the activation request, the program execution means 5 inquires of the load module management means 4 whether the designated load module A is stored on the main storage device 7 or not. Upon receiving the inquiry, the load module management means 4 searches the load module management area 8. When the load module A is stored in the load module storage area 9, the program execution means 5 is notified of this fact and the position (address) of the load module A on the load module storage area 9. Upon receiving the notification, the program execution means 5 transfers the data of the load module A from the load module storage area 9 to the load module expansion area 10, expands it, and then starts it.

(2) Starting a program (in the case of a load module that is not stored on the main storage device) A program starting request for a load module stored in the auxiliary storage device 6, for example, load module B, is sent from the terminal 1 to the host computer 2. When issued to the program execution means 5, this program start request is accepted by the program execution means 5. Upon receiving the activation request, the program execution means 5 inquires of the load module management means 4 whether the specified load module B is stored on the main storage device 7 or not. Upon receiving the inquiry, the load module management means 4 searches the load module management area 8. If the load module B is not stored in the load module storage area 9, the program execution means 5 is notified that the load module B is not stored. The program execution means 5 that has received the notification reads the load module B from the auxiliary storage device 6, expands it in the load module expansion area 10, and starts it.

(3) When the load module registration program is started, the load module management means 4 receives an inquiry as to whether or not a specified load module, for example, load module C, is stored on the main storage device. The load module management area 8 is searched to determine whether module C is stored in the load module storage area 9 based on the load module name, registered auxiliary storage device name, and file name. At this time, if load module C is not registered in the load module management area 8, the load module information, that is, the load module name, registered auxiliary storage device name, file name, and load module size, are registered and stored. Set the completed flag to not yet stored, and set the execution count to 1.

(4) Load module storage (if there is free space) When a program is started, a load module receives an inquiry as to whether a specified load module, for example, load module B, is stored on the main storage device. The module management means 4 searches the load module management area 8 to determine whether a load module is stored in the load module storage area 9 based on the load module name, registered auxiliary storage device name, and file name. At this time, if load module B is registered in the load module management area 8, the number of executions in the registered information is increased by 1. If load module B is not stored on the main storage device 7, the execution frequency of load module B is determined based on the updated number of executions. If it is determined that the load module B is high, the load module management area 8 checks whether there is enough free space in the load module storage area 9 to store the load module B.
The size of the free area of the load module B is compared with the size of the load module B, and if there is sufficient free space, a storage request for the load module B is notified to the load module main storage device storage means 3. Upon receiving the storage request, the load module main storage device storage means 3 reads the load module B from the file in the auxiliary storage device 6, stores it in the load module storage area 9, and notifies the load module management means 4 of the stored address. . Upon receiving the notification, the load module management means 4 sets the stored flag to the stored state and registers the address of the received load module B on the load module storage area 9.

(5) Load module storage (when there is no free space) When the program is started, a load module receives an inquiry as to whether a specified load module, for example load module E, is stored on the main storage device. The module management means 4 searches the load module management area 8 to determine whether a load module is stored in the load module storage area 9 based on the load module name, registered auxiliary storage device name, and file name. At this time, if the load module E is registered in the load module management area 8, the number of executions in the registered information is increased by 1. If the load module E is not stored on the main memory, the frequency with which the load module E is executed is determined based on the updated number of executions. If it is determined that the load module E is high, check whether there is enough free space in the load module E storage area 9 to store the load module E, and check the size of the free space in the load module management area 8 and the size of the load module E to be stored. Compare and find out. If there is not enough free space, the number of executions of load module E is compared with the number of executions of other stored load modules, and a stored load module whose number of executions is less than the number of executions of load module E is searched for. If there is no stored load module that has been executed less often than load module E,
Processing ends. If the stored load module A has been executed fewer times than the load module E, the size of the load module B is compared with the size of the free area plus the size of the load module A. If load module E is larger, a stored load module with a smaller number of executions than load module E is searched. If a stored load module D is found that has been executed less than load module E, and the total size of free space and load module A and load module D is greater than or equal to load module E, then load module A A request to delete the load module D from the load module storage area 9 is made to the load module main storage storage means 3.

Upon receiving the deletion request, the load module main memory storage means 3 deletes the load modules B and C from the load module storage area 9, and notifies the load module management means 4 that the deletion has been completed. Upon receiving the notification, the load module management means 4 sets the stored flags of the load modules A and D on the load module management area 8 to unstored flags. Then, the load module main storage storage means 3 is notified of a request to store the load module E in the load module storage area 9, and the load module main storage storage means 3 that has received the notification stores the load module E from the auxiliary storage 6. is read and stored in the load module storage area 9, and the address on the load module storage area 9 of the stored load module E is sent to the load module management means 4.
Notify. Load module management means 4 that received the notification
registers in the load module management area 8 the address of the stored load module E in the load module storage area 9 and a flag indicating that it has been stored.

[0014]

[Effects of the Invention] As explained above, the present invention allows the system to load the load module that is determined to be used frequently on the main storage device in advance, thereby assisting the load module each time the program is started. There is no need to input data from the storage device, and input can be performed simply by transferring data on the main storage device, which has the effect of increasing program startup efficiency.

[Brief explanation of drawings]

FIG. 1 is an overall configuration diagram showing an embodiment of the present invention.

FIG. 2 is a detailed explanatory diagram of the main storage device in FIG. 1;

[Explanation of symbols]

1 Terminal 2 Host computer 3 Load module main storage storage means 4
Load module management means 5 Program execution means 6 Auxiliary storage devices A, B, C, D, E... all load modules 7
Main storage device 8 Load module management area 9 Load module storage area 10 Load module deployment area

Claims (1)

[Claims] Claim 1: When a program is started, a load module on an auxiliary storage device is loaded onto the main storage device, and in a computer system that executes the program, the load module registered on the auxiliary storage device is loaded onto the main storage device. The load module main memory storage means to be stored on the main memory, the load module that has already been executed, the load module name of the load module stored on the main memory by the load module main memory storage means, and the load module name on the main memory. stores/manages the name of the original auxiliary storage device, determines the load module to be stored in the main storage device based on the frequency of use, and issues a storage request to the load module main storage device storage means. A load module management means, and a program execution means for developing a load module registered on an auxiliary storage device or a load module stored in a load module main storage storage means into an executable format and executing the load module. A program startup method characterized by: