JPH03255548A - Storage managing system for object - Google Patents

Abstract

PURPOSE:To eliminate the need for changing a concept object managing part and its object group even if the specifications of a file organization are changed by placing information related to a file in the management of the object managing part and sharing it. CONSTITUTION:This system is provided with an object storage part 107, a file object storage part 115, a file object managing part 108, and a concept object managing part 100, and in accordance with procedure information 100, 109, read-out and write of an object which is subjected to input designation are executed. That is, the object managing part is divided into two layers of the concept object managing part 100 and the file object managing part 108, and the procedures of a file reference and a data conversion are described in the file object managing part 108. In such a manner, the reference of the object having the same file organizing method is shared, and even if the specifications of the file organizing method are changed, no influence is exerted on the object group belonging to the concept object managing part 100, and the data conversion and the file reference/write are facilitated.

Description

[Detailed Description of the Invention] [Industrial Application Field] The present invention relates to an object storage management method, and in particular, to changing a file organization method on a secondary storage device without changing the object structure on the main storage device. This article relates to a storage management method for objects that can be used.

[Conventional technology]

312I on conventional object storage management methods
Explain using. Conventionally, objects are stored in the main memory 30.
0 to a file in the secondary storage device 310, or from a file in the secondary storage device 310 to the main storage device 300. Here, data and its procedures are treated as objects. The object management unit 301 exists in an area on the main memory at 300, and stores data structures and operation procedures for the data.
03 exists for each type of data structure. When a user issues an object creation request to a certain object management unit 301, a storage area for the object 308 is secured on the main storage device 300 based on data structure information held in the object management unit 301. Furthermore, an object number, which is a logical number, is assigned. This object 30
The correspondence between addresses on the main storage device No. 8 and object numbers is registered in the object-address management section 312. Further, the object number 306 is the object set table 3 in the area of the object management section 301.
05 and is associated with it. Objects registered in this object set table 305 will exist on the main storage device j 300. The object also holds an address 307 to the object management unit 301 to which it belongs. The object 308 on the main storage device 300 is stored in the file 311 of the secondary storage device 310 at the time of creation. A collection of objects 308 belonging to one object management section is stored,
The file name is area 3 in the object management section 301.
It is held at 04.

A procedure for writing the object 308 from the secondary storage device 310 to the main storage device 300 in such an environment will be described. It is assumed that the user requests the object management unit 301 for an object number to be written. The object management unit 301 checks whether the requested object number exists in the object set table 305. If it does not exist, a file reference procedure 30B in the object management unit 301 is activated. This file reference procedure 303 reads the object from the corresponding file 311 in the secondary storage device 310 based on the file name 304 and object number and writes it onto the main storage device 300 via the data bus 309. When the format of the object in the file is different from the format of the object in the main memory, the format is converted during the writing process, that is, during the file reference procedure. Next, the object number of the written object is registered in the object set table 305, and the number and main storage
The above address is registered in the object address management section 312.

The procedure for writing an object from the main storage device 300 to the secondary storage device 310 is as follows.

The object number of the object 308 to be stored in the file 311 is given to the object management unit 301. The object management unit 301 checks whether the object number exists in the object set table 305, and if it exists, starts the file writing procedure 303 of the object management unit 301. The file write procedure 303 converts the object number to a main memory address via the object address management unit 312, and data the object at that address to the file 311 on the secondary storage device 310 pointing to the file name 304. Write via. At this time, if necessary, the object format conversion procedure 303 is used to convert the object into the format of the secondary storage device 310 and store it.

As mentioned above, procedures can be roughly divided into procedures that refer to (or write) a file, and procedures that convert objects in a file to a data format on the main memory (or convert objects on the main memory into a secondary There are procedures for converting data into a data format on a storage device, and calculation procedures for manipulating data held by an object.When referring to an object and manipulating it, use the above procedure to 1) Convert the object format in the file to the data format on the main storage device; 2) Calculate by referring to the data in the object.

[Problem to be solved by the invention]

Conventional object storage management methods have the following problems because data conversion and file reference/write procedures are defined in the object management section.

■There are multiple files with the same file organization method in the secondary storage device. At this time, it is necessary to write exactly the same data conversion and file reference/write procedures for each of the plurality of object management units. A redundant main storage area is required for this purpose.

■If the file management method is changed, all related object management procedures must be changed.

An object of the present invention is to divide the conventional object management section into two layers, a conceptual object management section and a file/object management section, and replace the file reference and data conversion procedures defined in the conventional object management section with the file object management section. By proposing an object management method described in the conceptual object management section, objects with the same file organization method can share references, and even if the specifications of the file organization method change, the object group belonging to the conceptual object management section will not be affected. The object of the present invention is to provide a storage management method for objects.

[Means to solve the problem]

The object storage management method of the present invention includes an object storage section that stores objects, and file name 1 procedure information and file/object management section specification information that are arranged in correspondence with files on a secondary storage device and attached to the files. a plurality of file object storage sections storing file objects consisting of a plurality of file object storage sections; and a plurality of file object storage sections for storing file objects consisting of a plurality of file object storage sections; a file/object management unit that stores operational procedures and data structures for processing read/write and format conversion of objects between the storage unit and files on the secondary storage device;
A file object that exists for each data structure and is specified by the stored object of the same data structure, holds the number of the object it manages, data structure information 1 procedure information, and specifies the stored file object. The present invention is characterized in that it has a plurality of conceptual object management units that hold management unit pointers, and reads and writes input-specified objects according to the file object and procedure information held by the file object management units.

〔Example〕

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

FIG. 1 is a block diagram showing one embodiment of the present invention. The object management section includes a conceptual object management section 100 and a file object management section 108. Each object management section is composed of arbitrary objects that have data and procedures with a structure defined therein.

FIG. 2 is a flowchart showing the data reference operation when a user program operates an object.

In the following, explanation will be given using FIG. 1 according to the flowchart shown in FIG. 2. As in the conventional method, the user specifies the object 107 that he or she wishes to operate using the object number, and executes the procedure 101 defined in the conceptual object management section 100 that exists for each type of data FI4 structure.
By calling , the object 107 having the data structure 104 of the conceptual object management unit 100 can be operated.

The conceptual object management unit 100 manages whether a necessary object is in the main memory bag W114 or in the secondary storage device 118 using an object set table 1.2.
If the necessary object lO7 does not exist in the main storage device 114 (step 200) - the file object pointed to by the file object management section pointer 10'' of the conceptual object management section 100] - Stella 7201 for 15), A request is issued to write the corresponding object from file 1-)7 in the secondary storage device 118 to the main storage device l14.
File name 1 of the corresponding file is placed corresponding to
16), and further stores the file/object management unit 10 to which it belongs in its own area.
8 address] 13 is held. Also, file
The object management unit 108 holds a data structure 111 of a file object and its operation procedure 109, and is shared by file objects having the same data usage and operation procedure. The procedures include a file reference procedure that writes objects in a file onto the main memory according to the data structure 111, an object format conversion procedure that mutually converts the file format and the format on the main memory, and a main memory It has procedures for reading and writing objects on the device 114 to files on the secondary storage bag ff111.8. When the file object 115 receives a request to write an object in the file onto the main memory 114, it
File/object management unit 108 specified by 13
is requested to start the file reference procedure in the operation procedure 109. This file reference procedure writes the object of the file specified by the file name 116 into the object area on the main storage device 114 via the data hash 119 (step 203). If necessary, the object format conversion procedure in the operation procedure 109 converts the object format in the file to the object format on the main storage device.
204〉. Next, the object number of the written object is registered in the object set table 102, and the number and address on the main storage device 114 are registered in the object address management section 120. Procedure 10 for conceptual object]-07 is executed for object 107 written on main storage 114 (step 205).

On the other hand, reading the object 107, the secondary storage device 1
18 is written to the conceptual object management unit (the secondary storage device 11 for the file object 115 pointed to by the file object management unit pointer 103 of 00).
Issue the object number of the object to be written to 18 and a write request. The file object 115 that has received this request learns the file object management section 108 to which it belongs from the address 113, and issues a request to start the write procedure in the operation procedure 109 to that management section. The write procedure converts the object number into a main memory address via the object address management unit 120, and writes the object at that address to the file 117 on the secondary storage device 118 pointed to by the file name 16 via the data bus 119. and write. At this time, if necessary, procedure 1 for converting the object format.
09 to convert it into the format of the second secondary storage device 118 and store it.

When changing the file organization method here, the file reference procedure held in the procedure group 109 of the corresponding file/object management unit is rewritten. Also, if the format of objects 1~ in the file is changed,
Alternatively, when the format of an object on the main storage device is changed, the object format conversion procedure held in the procedure group 109 is rewritten. At this time, the conceptual object management section and the objects belonging to it do not require any changes. This kind of flexibility is achieved by performing operations based on logical object numbers in the procedures of the conceptual object management section, and when a file reference is required, the file object held by the file object pointed to by the file object management section pointer 103 is This is achieved because a request is issued to read and write an object corresponding to an object number from a name, and because a group of file-related procedures held in the file object management section can be shared by a plurality of conceptual object management sections.

E. Effects of the Invention] According to the present invention, by sharing file-related information under the control of the file/object management section, even if there is a change in file organization specifications, the conceptual object management section and its object group can be maintained. No changes are required and the size of the application program is reduced.
This has the great effect of improving program development productivity and system throughput.

[Brief Description of the Drawings] Fig. 2 is a block diagram showing an embodiment of the present invention, Fig. 2 is a flowchart explaining the invention in detail, and Fig. 3 is a diagram explaining a conventional object management method. be. 100 -- Conceptual object management section, 101 -- Procedure group, 102 -- Object set table, 10
3...File/object management section pointer, 10
4...Data structure, 105...Object number,
106--address, 1.07 object, 10.
8--File/object management section, 109--Procedure group, 111--Data structure, 113-Address, 1
14... Main storage device, 115... File object, 116...-File name, 117... File,
118...Secondary storage device, 119-data bus, 1
20.-Object address management section, 300...
Main storage device, 301... Object management section, 302...
...Data structure, 303...Procedure group, 304...
File name, 305...Object set table, 3
06...Object number, 307,...Address,
308...-object, 309 data bus 53
10...Secondary storage device, 31 To file, 312 Object address management section.

Claims (1)

[Claims] In an object storage management system, an object storage unit that stores objects, and a file name, procedure information, and file/object management unit specification information arranged in correspondence with a file on a secondary storage device and attached to the file. A plurality of file object storage units that store file objects; and a file object storage unit that is specified by file object management unit specification information that is provided for each data structure and is specified by the stored file objects of the same data structure; a file/object management unit that stores operational procedures and data structures for reading, writing, and format conversion of objects between and files on the secondary storage device;
A file object that exists for each data structure and is specified by the stored object of the same data structure, holds the number of the object it manages, data structure information, and procedure information, and also specifies the stored file object. An object characterized in that it has a plurality of conceptual object management units that hold management unit pointers, and reads and writes input specified objects according to the file object and procedure information held by the file object management units. storage management method.