JPS61122762A - Control processing system of data set area - Google Patents

Abstract

PURPOSE:To improve the maneuverability of data set allocation by previously determining a temporary data setting area to be used for the whole system, sorting the temporary data setting area in each purpose and determining the tolerance of respective areas to control them. CONSTITUTION:The information of the size of the temporary data setting area of the whole system and that of a temporary data setting area to be used in each volume are registered in a system profile storage part 1, and at the initial setting of the system, reads out by a system profile extracting part 6 and set up in a work volume control table 5. The information of minimum guaranteed variable and the maximum used variable in each user is registered in a user profile storage part 2 by a user property definition command.

Description

[Detailed Description of the Invention] [Industrial Application Field] The present invention relates to a data set area management processing method, particularly for example, T
S S (Time Sharing System
) In a data processing system that performs control, etc., by defining a temporary data set area to be used by the entire system, further classifying the temporary data set area by use, and determining and managing the allowable amount of the temporary data set area.

The present invention relates to a data set area management processing method that can guarantee area acquisition for the system or each user.

[Conventional technology and problems]

For example, in a data processing system that performs TSS control, a DAS such as a magnetic disk device used by a terminal user is
The data set area H area on D is allocated in the order in which acquisition requests are made, as long as there is space in the area. Therefore, when a terminal user wants to reserve an area on the DASD, if another user is using too much space, the area may become insufficient and the necessary area may not be available.

Originally, it is a problem that terminal users are unable to acquire the necessary space due to excessive use of space by other users who are unrelated to them and do not need to be aware of, and are therefore unable to carry out their work.This problem can be solved. It is desirable to do so.

In particular, for temporary datasets that are work datasets that store intermediate processing data and are automatically deleted when a job or session ends, the terminal user himself/herself does not need to be aware of the use of the temporary data set. Because there are some things that are not available and the temporary data set cannot be obtained internally.

When it comes to not being able to carry out work, there is a problem of extremely poor service quality.

[Means for solving problems]

The present invention aims to solve the above-mentioned problems, and divides the DASD data set area of the entire system into a storage data set area and a temporary data set area, and further divides the temporary data set area into a temporary data set area for each volume and a temporary data set area for each user. It is divided into a temporary data set area and a common temporary data set area, and the maximum usage capacity is determined and managed for each area. and,
During system operation, a means is provided to allocate areas by cutting out areas within the maximum allowable capacity for each area. In other words, the data set area management processing method of the present invention is as follows:
Information that determines the size of the temporary dataset area for the entire system and temporary data that can be used for each volume in a dataset area management processing method that manages the dataset area secured on the direct access volume in a data processing system. The system profile storage unit stores information that determines the size of the set iI area, and the minimum guaranteed amount that can be used as a temporary data set and the maximum amount that can be used as a temporary data set are registered for each user. a user profile storage unit;
The usage amount of the temporary data set area is calculated for each volume and each user based on the volume management information obtained from the system profile storage unit and the user profile storage unit, and based on the size of the temporary data set iJ area of the entire system. a usage amount calculation unit that calculates the amount of the common temporary data set area by subtracting the sum of each minimum guaranteed amount of all users currently being processed;

A usage amount inspection unit that checks the usage amount that can be allocated based on the above-mentioned minimum guaranteed amount and maximum usage amount of the acquisition requesting user, and a minimum guaranteed amount for the area requested for acquisition according to the inspection result by the usage amount inspection unit. The present invention is characterized by comprising an area allocating unit that allocates an area cut out from the common temporary data set area for the excess amount. Embodiments will be described below with reference to two drawings.

〔Example〕

FIG. 1 is a block diagram of the configuration of an embodiment of the present invention, FIG. 2 is a diagram for explaining the management of a temporary data set area according to the present invention, and FIG. 3 is a diagram for explaining the relationship between the number of expansions and the amount of increment. Show the diagram.

In the figure, ■ is a system profile storage section in which system constants etc. determined at the time of system integration are stored, 2 is a user profile storage section in which user information is registered for each user, and 3 is a temporary data storage.

4 is an area allocation unit that allocates a temporary data storage area; 5 is a work volume management table that stores work volume information; 6 is a system profile extraction unit , 7 is a user profile extraction unit, 8 is a user profile collection unit, 9 is a volume information update unit, 10 is a usage checking unit that checks the usage amount in response to an area acquisition request, and 11 is a calculation unit that calculates the usage amount of the area. 12 is a temporary data set; 13 is an allocation determination unit that determines whether or not to allocate in response to an SI area acquisition or expansion request; 13 is an increment amount determination unit that determines an increment amount in response to an expansion request; an allocation execution unit that allocates
Reference numeral 15 represents a usage amount addition unit that adds the allocated usage amount, and 16 represents an area release unit that releases the area in response to a release request for the temporary data set area.

In the case of the present invention, in managing the data set 8i area on the DASD, for example, as shown in FIG. 2, each volume is managed separately into a storage data storage area and a temporary data storage area. . Then, the sum total of these temporary data set areas is defined as the temporary data set Si area of the entire system. By preventing the creation of a temporary database that exceeds the size of the temporary data storage area of the entire system, the area of saved data sets that must be permanently saved is guaranteed.

In addition, the area that can be used as a temporary dataset for each volume is determined in advance, and by preventing temporary datasets from being created on the volume in excess of this size, overuse of the temporary dataset area can be avoided. Prevent encroachment on the saved data set area by The reason why the upper limit value is set for each volume is because, for example, when creating a database on a saved data set area, it may be necessary to secure an area from a specific volume in terms of access performance.

Information on the size of the temporary data set area for the entire system and the size of the temporary data set area usable for each volume is registered in the system profile storage unit 1 shown in FIG. 1, for example, at the time of system editing.
At the time of system initialization at L (Initial Program Load), the system profile extraction unit 6 reads out the profile and sets it in the work volume management table 5.

Furthermore, the size of the temporary data set area that can be used by each user is determined as the minimum guaranteed amount.

This minimum guaranteed amount of area is secured when the user requests processing from the system, that is, at the time of so-called LOGON, and if it cannot be secured at this time, LOGON is disabled. Once secured, the guaranteed minimum amount cannot be taken away from other users and can be used exclusively by the user until the user logs off. Further, the maximum amount of temporary data that each user is permitted to use is determined in advance.

The information on the minimum guaranteed amount and maximum usage amount for each user is registered in the user profile storage section 2 shown in FIG. 1 by a user attribute definition command. Note that, for example, a user identifier UID, a password, etc. are also registered in the user profile storage unit 2.

User identifier UID and temporary data set)? The information on the minimum guaranteed amount and maximum usage amount of the fI area is read by the user profile extraction unit 7 at the time of LOGON or the start of a batch job, and is set in the work volume management table 5. This setting information is collected by the user profile collection unit 8 at the time of LOGOFF or job termination.

It is deleted from the work volume management table 5.

From the temporary data set area of the entire system, LOGON
The area obtained by subtracting the sum of the minimum guaranteed amounts of the users who are currently using the database is managed as a common temporary data set area as shown in FIG. In the example shown in Figure 2, the user identifier A
, B, and C are in LOGON, and the remaining area is used as a common temporary data set area.

A user who has used up the seven feet of temporary data area for each user is permitted to cut out and use this common temporary data set area as long as it does not exceed the user's maximum usage amount.

The polyneme information update unit 9 shown in FIG. 1 is activated when a volume is mounted or dismounted,
It executes the process of updating the volume management information on the work volume management table 5. If the device is not a removable medium, the volume information update unit 9 is not necessary.

When there is a request to acquire or expand the 6N area, the allocation determination unit 12 of the area allocation unit 4 is activated. The allocation determination section 12 checks whether or not an area request can be allocated, and calls the usage amount inspection section 10 for this check. The usage inspection unit 10 is a work volume.

By referring to the management table 5, it is checked whether the requested usage amount can be secured based on the above-mentioned minimum guaranteed amount, maximum usage amount, size of the common temporary data set area, etc.

If the allocation determination unit 12 determines that 1 allocation is not possible according to the inspection result by the usage amount inspection unit 10.

Notify the requester that the area cannot be secured. If the allocation is possible, control is transferred to the 1 allocation execution unit 14. In particular, when the area request is an expansion request, the increment amount determination unit 13 is activated before control is transferred to the allocation execution unit 14.

In the case of this embodiment, the increment amount determination unit 13 has two units, for example, as shown in FIG.
Determine the incremental amount as shown in b).

Normally, the number of area expansions for one data set is:

For example, there is a limit of 16 times per volume, and this limit also applies to temporary data sets. Therefore, in order to prevent abnormal termination due to exceeding the number of extensions of the temporary data set, the user generally needs to estimate the area usage of the temporary data set and determine the initial amount and increment amount accordingly.

However, the temporary data set is originally a work file, and the user may not be aware of it, and even if the user is aware of it, it is a heavy burden. It is desired that the program be expanded so that even if the user mistakenly specifies a small increment amount, an abnormal termination will not occur.

By the way, looking at the expansion of temporary dataset statistically,
In most cases, the number of extensions exceeds the number of extensions. this is.

The conventional extension is 2, for example, as shown in Figure 3 (A).

This relates to the fact that the data is expanded uniformly by the specified increment amount, regardless of the number of expansions. Therefore, in the case of the present embodiment, for example, as shown in FIG. 3(b).

When there are nine or more expansions remaining, the area is expanded according to the initial increment amount specified by the user.

When the number of times that can be extended is 8 or less, the data is expanded by 1, for example, 40% more than the previous increment amount. By doing this, if the user's maximum usage is within the permitted range, the total amount of usage will be approximately 5.
It can be expanded to double the size. In addition, Figure 3 (
Whether or not to perform the increment shown in b) can be selected for each user, and information on whether or not this is applicable is registered in the user profile storage unit 2 shown in FIG.

The allocation execution unit 14 shown in FIG. 1 uses the amount specified by the user in the case of initial allocation, and the amount specified by the user in the case of expansion.

The increment amount determined by the increment amount determination unit 13 is secured and allocated from the unused temporary data storage area H. If the allocation is successful, the usage amount addition unit 15 is activated. Usage amount adding section 1
5 adds the newly allocated amount to the current usage amount for each user by calling the usage amount calculation unit 11 and sets it in the work volume management table 5. Further, the usage amount calculation unit 11.

Calculate the remaining amount of the temporary data set area for each volume and the size of the common temporary data set area as necessary.

When there is an area release request, the area release unit 16 is activated, and the area release unit 16 subtracts the usage amount added by the usage amount addition unit 15 by calling the usage amount addition unit 15.

Through the above processing, as long as there is space in the temporary data storage RM area for each user in response to a user's area allocation request, it is used, and at least the minimum guaranteed amount can always be used. When this minimum guaranteed amount is used up, six empty pages in the common temporary data set area can be used within a range that does not exceed the maximum usage amount. Of course, regarding switching to the common temporary data sesoto area,
There is no need for Niichiza to be aware of this. In addition, if processing exceeding the maximum usage amount is required, notify the system administrator, redefine the maximum usage amount in the user profile storage unit 2, and log on again, and the new maximum usage amount will become effective. .

The usage of all temporary data sets is tracked for each user.1 For example, temporary data sets such as system input (SYSIN)/system output (SYSOUT),
What the user acquires and the O3 subsystem erases;
Also, items acquired by subsystems and deleted by users are added to each user's usage amount. Note that temporary data sets used only by subsystems for which the request source cannot be determined are treated as temporary data sets used by the system, and are not added to the usage amount for each user.

The user who requested the area can be identified by the USER parameter at the time of LOGON in the case of a conversational processing, for example, or by the USER parameter in the job control statement in the case of a batch job.

〔Effect of the invention〕

As explained above, according to the present invention, the operability of data allocation is improved, and for each terminal user,
It becomes possible to secure a minimum guaranteed amount registered in advance for the temporary data set area, and it becomes possible to prevent harmful effects caused by other users unreasonably using too much space. The burden of estimating the amount of data set area used is reduced.

[Brief explanation of drawings]

FIG. 1 is a block diagram of the configuration of an embodiment of the present invention, FIG. 2 is a diagram for explaining the management of a temporary data set area according to the present invention, and FIG. 3 is a diagram for explaining the relationship between the number of expansions and the amount of increment. Show the diagram. In the figure, 1 is the system profile storage gL, 2 is the user profile storage unit, 3 is the work volume management unit,
4 is an area allocation section, 5 is a work volume management table, 10 is a usage amount inspection section, 11 is a usage amount calculation section, 12 is an allocation determination section, 13 is an incremental amount determination section, 14 is an allocation execution section, and 15 is a usage section. The quantity addition section 16 represents an area release section. Patent applicant Fujitsu Ltd. Representative Patent Attorney Hiroshi Mori (1 other person) Su1n

Claims (2)

[Claims] (1) In a data set area management processing method that manages the data set area secured on a direct access volume in a data processing system, information that determines the size of the temporary data set area for the entire system and information that can be used for each volume A system profile storage section that stores information that determines the size of the temporary data set area, and the minimum guaranteed amount that can be used as a temporary data set and the maximum amount that can be used as a temporary data set are registered for each user. Based on the volume management information obtained from the user profile storage unit, the system profile storage unit, and the user profile storage unit, the usage amount of the temporary data set area is calculated for each volume and each user, and the temporary dataset area for the entire system is calculated. A usage calculation unit that calculates the amount of the common temporary dataset area by subtracting the sum of each minimum guaranteed amount of all users currently being processed from the size of the dataset area, and the above minimum guaranteed amount and maximum amount of the acquisition requesting user. A usage amount inspection unit that checks the amount of usage that can be allocated based on the usage amount, and according to the inspection results by the usage amount inspection unit, the amount exceeding the minimum guaranteed amount for the area requested to be acquired is collected from the common temporary data set area. A data set area management processing method comprising: an area allocation unit that allocates a cut out area. (2) In response to a temporary data set expansion request, when the remaining number of expansions is less than a predetermined number of times, the area allocation unit allocates an area at once within a range that does not exceed the maximum usage amount of the user. The data set area management processing method according to claim 1, wherein the data set area management processing method is configured to perform allocation by sequentially increasing the amount.