JPS63217440A - Table managing system - Google Patents

Abstract

PURPOSE:To simplify the logic of a process where a table access subject gives an access to a table by storing the control information on the table loaded in a memory separate from the table main body by a request given from a table separating/merging means. CONSTITUTION:A file table control means 32 stores the file table managing information, i.e., the information on a table set on a table storing file 2 which is needed for the processing of a table separating/merging means 31. While a memory table managing means 33 stores the memory table control information, i.e., the information on the table set on a memory which is needed for processing of the means 31. Then a table control information storing means 34 stores the table control information on the table loaded into a memory separated from a table main body 1 by the means 31 by a request of the means 31. Thus the table main body 1 and the table control information are stored in the memory separately from each other and then stored connected to each other in the file 2 of a secondary memory respectively.

Description

[Detailed Description of the Invention] [Field of Industrial Application] The present invention relates to a table management method, and particularly to a data processing system in which a table is stored and updated both in memory and in a table storage file of a secondary storage medium. between table management methods.

[Conventional technology]

Conventionally, this type of table management method adds table control information necessary for storing the table on a secondary storage medium and table control information necessary for managing the table in a data processing system to the table body. However, tables were managed in a form in which the table body and table control information were linked both in memory and on secondary storage media. If the block length of a table storage file on a storage medium is determined based on the table length of a table with a large table length, a large invalid area will be created in the block that stores the table with a small table length.
A table with a large table length was divided into multiple blocks and stored in a table storage file.

[Problem that the invention seeks to solve]

In the conventional table management method described above, tables loaded into memory are also managed in a concatenated form with the table body and table control information, so table accesses in memory that originally only require the table body are managed. The drawback is that the subject must be aware of the existence of table control information when accessing the table.

In particular, when the difference in table length between multiple tables to be managed is large and a table with a large table length is to be divided into multiple blocks and accommodated, this is necessary to store the table on the secondary storage medium. Table control information is required for each block on the table storage file of the secondary storage medium, so the table control information for each block is distributed and exists in one table, so the table access entity must access the table. This has the disadvantage that the processing logic becomes complex.

In view of the above-mentioned points, an object of the present invention is to make it possible to store a table main body and table control information in a separate form in a memory, but in a connected form in a table storage file of a secondary storage medium. To provide a table management method that eliminates the need for a table access subject to be aware of table control information when accessing a table.

[Means for solving problems]

The table management method of the present invention is such that the table body and table control information are stored in a separate form in the memory and in a connected form in the table storage file of a secondary storage medium, so that the table is manually transferred from the table storage file to the memory. A table separation and merging means that separates the table body and table control information when outputting the table from memory to a table storage file, and merges the table body and table control information when outputting the table from memory to a table storage file, and a table separation and merging means that is necessary for the processing of this table separation and merging means. File table management means for storing file table management information, which is information about tables on the table storage file, and memory table management information, which is information about tables loaded on memory, which is necessary in the processing of the table separation and merging means. and table control information storage means for storing table control information of a table loaded onto a memory separated from the table body by the table separation and merging means at the request of the table separation and merging means. has.

[Effect]

In the table management method of the present invention, the table separation/merging means stores the table main body and table control information in a separate form in the memory and in a connected form in the table storage file of the secondary storage medium. When inputting a table to the memory, the table body and table control information are separated, and when outputting the table from the memory to the table storage file, the table body and table control information are merged, and the file table management means separates and merges the table. The memory table management means stores file table management information, which is information about tables on the table storage file that is necessary in the processing of A certain memory table management information is stored, and the table control information storage means stores the table control information of the table loaded on the memory separated from the table body by the table separation and merging means at the request of the table separation and merging means.

〔Example〕

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

FIG. 1 is a block diagram showing the configuration of an embodiment of the table management method of the present invention.9 The table management method of this embodiment includes a table storage file 2, table separation/merging means 31, and file table management means. 32, a memory table management means 33, and a memory (not shown) that stores table control information 4 in block units and table control information 5 in table units regarding table body 6 accessed by table access subject 35. A table control information storage means 34, a table access entity 35 in memory that accesses the table body 6 and uses the table body 6, a file input/output means 36, a table body 6, table control information 4 in blocks, and It is composed of a memory buffer 37 that separates and merges table control information 5 for each table.

The file table management means 32 stores the type of table stored in the table storage file 2, the storage position on the table storage file 2, the length of the table body 6, the number of table control information, and the table format i.
A file table management file f1139 containing the addition position of the n+ information, the length of the table control information, etc. is stored in preparation for processing by the table separation/merging means 31.

The memory table management means 33 determines the type of table loaded on the memory, the storage position of the table control information 4 for each block and the table control information 5 for each table on the table control information storage means 34, etc. The memory table management information 38 is stored in preparation for processing by the table separation/merging means 31.

The processes in the table management method of this embodiment include a table load request 10, a table read request 11, a file input/output 12, and a file input/output processing completion notification 1.
3, a memory table management information save request 14, a table control information save request 15, a table separation/merging means processing completion notification 16, a table write request 17,
Transfer of table control information 18, Reference of memory table management information 19, Reference of file table management information 2
0, a table write request 21, and a table separation and merging 22.

FIG. 2 is a diagram showing a method of configuring a table, which is a processing target of the table management method of this embodiment, on the table storage file 2.

The table in the table storage file 2 is stored in a secondary storage medium (
(not shown) is added with block-based table control information 4 necessary for storing tables and table-based table control information 5 necessary for managing tables in the data processing system. has been done. Note that if the logical table 1 is too large to be accommodated in one block 3 on the table storage file 2, it is divided into a plurality of blocks 3 to form the table.

Next, the operation of the table management system of this embodiment configured as described above will be explained.

First, the process of reading a table from the table storage file 2 to the memory will be described.

The table access subject 35 on the memory makes a table load request 10 regarding the table to be accessed to the table separation/merging means 31.

Upon receiving the table load request 10, the table separation/merging means 31 performs a reference 20 for file table management information to the file table management means 32, and stores the table storage file of the table to be read in the referenced file table management information 39. A read request 11 for a table including storage locations etc. on the file input/output means 36 is made to the file input/output means 36.

The file input/output means 36 is the table separation/merging means 31
Based on the table continuation request 11 received, the table body 6 forming the contents of the logical table l and the table control information 4 in blocks are stored in the table storage file 2.
A file input/output 12 is performed to read the table control information 5 for each table into the memory buffer 37, and a file input/output processing completion notification 13 is sent to the table separation/merging means 31.

Upon receiving the file input/output processing completion notification 13, the table separation/merging means 31 makes a reference 20 to the file table management information to the file table management means 32, and the table body 6 in the referenced file table management information 39 is
The table is stored in the memory buffer 37 based on the length of the table, the number of table control information, the addition position of the table control information, the length of the table control information, etc. Separation and merging 22 of the table to be separated into information 5 is performed.

Next, the table separation/merging means 31 stores the table control information storage B15 regarding the block-based table control information 4 and the table-based table control information 5 separated from the table body 6 into the table control information storage means 34.
, requests the memory table management means 33 to save the memory table management information 14, and stores the table control information 4 in blocks on the table control information storage means 34.
After storing memory table management information 38 indicating the storage location of table control information 5 for each table, etc., only the table body 6 is delivered to the table access entity 35 along with a processing completion notification 16 of the table separation/merging means.

Next, the process of writing a table from the memory to the table storage file 2 will be explained.

The table access entity 35 in the memory updates the table by a table write request 17 to the table separation/merging means 31 in order to reflect the update contents made to the table body 6 in the logical table 1 in the table storage file 2. The main body 6 is delivered to the memory table separation/merging means 31.

Upon receiving the table write request 17, the table separation/merging means 31 makes a reference 19 to the memory table management information regarding the table to be written to the memory table management means 33, and based on the referenced memory table management information 38, table control information is generated. The table control information 18 for the table control information 4 for each block and the table control information 5 for each table of the table to be written is received from the storage means 34 .

Next, the table separation/merging means 31 performs a reference 20 to the file table management information regarding the table to be written to the file table management means 32, and in the referenced file table management information 39, the length of the table body 6, the table Number of control information.

Table main body 6, table control information 4 for each block, and table control information 5 for each table based on the addition position of the table control information, the length of the table control information, etc.
Separation and merging 22 of the tables is performed on the memory buffer 37.

Further, the table separation/merging means 31 performs a reference 20 for file table management information to the file table management means 32, and the referenced file table management information 39
A table write request 21 is made to the file input/output means 36, including the storage position of the table to be written in the table storage file 2, etc.

The file input/output means 36 is the table separation/merging means 31
The receiver performs a file input/output 12 to write the merged table to the table storage file 2 based on the received table write request 21, and sends a file input/output processing completion notification 13 to the table separation/merging means 31.

Upon receiving the file input/output processing completion notification 13, the table separation and merging means 31 sends a processing completion notification 16 of the table separation and merging means to the table access subject 35.

Note that in this embodiment, the table access entity 3 on the memory
5 describes the case where the table body 6 receives direct light from the table separation and merging means 31, but the table body 6 is stored in another area on the memory by the table separation and merging means 31, and the address of that area is used as the table accessing subject. 3
5, and the table body 6 is accessed by the table access subject 35 based on the address. In this case, the address on the memory where the table body 6 is stored is stored in the memory table management information @38 in the memory table management means 33.

〔Effect of the invention〕

As explained above, the present invention makes it possible to store the table main body and table control information in a separate form in memory, but in a connected form in a table storage file of a secondary storage medium. This has the effect that the table access subject does not need to be aware of table control information when accessing a table.

In particular, when a table with a large table length is divided into multiple blocks and stored in a secondary storage medium because the difference in table length between multiple tables to be managed is large, each block is distributed into one table. The above-mentioned effect is significant because there is no need to be aware of the table control information that exists and forces complicated access processing.

[Brief explanation of the drawing]

FIG. 1 is a block diagram showing the configuration of an embodiment of the present invention, and FIG. 2 is a diagram showing a method of configuring tables on the table storage file in FIG. 1. In the figure, l...Logical table, 2...Table storage file, 3...Block, 4...Table control information in block units 1.5... Table control information in table units, 6 ...Table body, 10...Table load request, 11...Table read request, 12...File input/output, 13...File input/output processing completion notification, 14...
Request to save memory table management information, 15... Request to save table control information, 16... Notification of completion of processing of table separation/merging means, 17... Request to write table, 18... Delivery of table control information , 19... Reference to memory table management information, 20... Reference to file table management information, 21... Table write request, 22... Separation and merging of tables, 31... Table separation and merging means, 32...File table management means, 33---Memory table management means, 34...Table control information storage means, 35...Table access subject, 36...File input/output means, 37...Memory buffer; 38... memory table management information; 39... file table management information.

Claims (1)

[Claims] When inputting a table from the table storage file to the memory in order to store the table body and table control information in separate form in the memory and in a connected form in the table storage file of the secondary storage medium, table separation/merging means for separating the table body and table control information and merging the table body and table control information when outputting the table from the memory to the table storage file;
A file table management means for storing file table management information, which is information regarding tables on a table storage file, which is necessary in the processing of the table separation and merging means; memory table management means for storing memory table management information, which is information about tables that are stored in the table; A table management method comprising: table control information storage means for storing table control information at the request of the user;