JPH08110869A - File system - Google Patents

Abstract

PURPOSE: To improve the flexibility of the handling of file resources by enabling access to a virtual file resource obtained by performing a specific procedure to an existent file resource. CONSTITUTION: When a communication part 1 receives a request to read out a file name, it requests a file name management part 2 to work out the file name, and requests a virtual file name management part 3 to work out the file name if the file name is not worked out. The virtual file name management part 3 retrieves a virtual file resource management table 14 and passes the physical position and procedure name of the file to the communication part 1. The communication part 1 obtains procedure definitions together with the physical position of the file and pass them to a procedure application part 6 together with the physical position of the file. The procedure application part 6 passes the physical position of the file to a file reading/writing part 5 and applys the procedure to the read information according to the procedure definitions, thereby outputting the information through the communication part 1.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a file resource in a network information system in which resources of a plurality of computer systems for information processing are dispersedly arranged on a network and a plurality of computer systems communicate with each other to operate. The present invention relates to a file system method for managing a name and a physical location of a file resource corresponding to the name and performing name-to-location resolution.

[0002]

2. Description of the Related Art As a conventional file resource management system of this type, see, for example, Akihiro Uetani, "Local Area Network Ethernet Overview", 2nd edition, Maruzen Co., Ltd.
p. 222-229, the resource management method and file service of the clearing house service of Xerox Co. of the United States are described. In this method, the name of a resource in a distributed system is associated with an arbitrary number of attributes and managed by a distributed database, and a name-to-address conversion is provided. In the clearing house service, a file is specified by using a file ID, a directory and a local file name, and a path name, and a file service is realized.

As another file resource management method, for example, "What comes after distributed operating system UNIX", edited by Mamoru Maekawa, Mario Tokoro and Kentaro Shimizu,
Kyoritsu Publishing, p. 243-264 describe the resource management scheme of the GALAXY operating system. In this method, the logical identifier of the object and the position information of the physical substance of the object are associated with each other,
It is stored and managed in a global database. This resource management system records and manages location information for all copies of an object.

In the name service system described in Japanese Patent Laid-Open No. 63-236436, the name and network address of the information processing device, that is, the name of the information processing device which is a resource on the network and its physical name. It also includes control means for managing the network addresses at different positions in a table. A name service for searching a network address in response to a name inquiry from the information processing device is provided.

In these conventional file resource management methods, the name of the file resource and the physical position information or attribute of the file resource are associated with each other and managed by a resource management table or resource management database. The physical position information or attribute of the corresponding file resource is output from the file name. In such a commonly used file resource management system or system on the network, the position of the file resource is virtualized in the sense of hiding the physical position of the file. However, the handling of file resources must be performed by the application, and in this sense, file management that virtualizes the handling of files is not provided.

Particularly, in the conventional system, a virtual file resource (file resource 2) obtained as a result of applying data processing to a certain file resource (file resource 1).
In addition, a virtual name (name 2) different from the name (name 1) of the original file resource (file resource 1) cannot be given and handled. For example, for a virtual file resource (file resource 2) obtained as a result of applying data processing such as type conversion and access protocol conversion processing to a certain resource (resource 1), the original file resource A file resource (file resource 2) having a virtual name (name 2) that is different from (file resource 1) and is accessible by a desired type or access protocol Cannot be treated as if it exists. The conventional technology does not provide a highly flexible network information system that can be handled in this way. Furthermore, by managing multiple procedure names for handling file resources, it is possible to select one or more procedures from among multiple procedures and apply them to file resources depending on the system status and user's intention. It does not provide a highly flexible network information system.

File transfer protocol service system WUFTPD developed at the University of Washington
(For example, Shin Yoshimura, "Internet Usage and Mechanism 2 FTP and Telnet", UNIX MAGAZ
INE 1993, ASCII etc.) is a non-existent file that can be created by adding a specific suffix or prefix to an existing file name or removing a specific suffix or prefix from an existing file name when reading and transferring the file. By designating the name, the service for transferring the result of performing the procedure on the file resource is realized.

[0008] However, this system is a file transfer service system, and generally relates to file resources in each operation such as file opening, closing, generation, deletion, attribute operation, listing, writing, and replacement, which a file system has. No reference is made to the application of the procedure.

[0009]

SUMMARY OF THE INVENTION The present invention has been made in view of the above-mentioned circumstances, and an existing file is created for a virtual resource obtained as a result of performing a predetermined procedure on the existing file resource. By implementing a file resource management method that manages resource locations, procedure names, and virtual names in association with each other, it becomes possible to access virtual file resources having the characteristics desired by the user, and network information. The purpose of the present invention is to virtualize the file resources of a plurality of computer systems of the system, and to increase the flexibility of the entire network information system.

[0010]

According to a first aspect of the present invention, there is provided a file system in a network information system in which a plurality of computer systems that perform information processing are connected by a network, and the computer system actually exists. The actual file resource location information indicating the physical location of the file resource, the procedure name that is the name of one or more procedures for processing the file resource, and the virtual file name that is the name of the virtual file resource are associated with each other. A virtual file resource management table that holds and manages one or more sets of virtual file names, and the real file resource location information that is determined by the virtual file name management means by receiving the virtual file name and corresponding to the virtual file name. A virtual file name resolving means for searching the procedure name, and the virtual file name solution It is characterized in that it has a procedural application means for applying a procedure determined by the procedure name to real file resources the determined by real file resource location information corresponding to the virtual file name obtained by means.

According to a second aspect of the present invention, in a file system in a network information system in which a plurality of computer systems that perform information processing are connected by a network, a real file name that is the name of a file resource that actually exists in the computer system. And file name management means having a file resource management table that holds and manages at least one set of real file resource position information indicating the physical position of the existing file resource, and a virtual file resource name virtual A file name conversion procedure name that is a name of a file name conversion procedure that outputs a set of a procedure name and a real file name or a virtual file name for inputting a file name and processing a file resource Conversion procedure with virtual file name correspondence table that holds and manages one or more And a recursive process for a virtual file name obtained by applying a file name conversion procedure corresponding to one or more of the file name conversion procedure names of the conversion procedure management means to a given virtual file name. The procedure name obtained by applying one or more file name conversion procedures and the real file resource position information of the file name management means corresponding to the obtained real file name and the application of the file name conversion procedure And a procedure defined by the procedure name is applied to an existing file resource defined by the real file resource position information corresponding to the virtual file name obtained by the virtual file name resolution means. It is characterized by having procedure applying means.

According to a third aspect of the present invention, in the file system according to the first or second aspect, the system state acquisition means for acquiring a parameter indicating the system state, and the system state acquisition means for acquiring the parameters. Further comprising procedure selecting means for selecting one or more procedure names from the plurality of procedure names when a plurality of procedure names are obtained corresponding to a certain virtual file name based on a parameter, The virtual file name resolving means outputs the real file resource position information and the one or more procedure names selected by the procedure selecting means, and the procedure applying means is obtained by the virtual file name resolving means. For the existing file resource defined by the real file resource position information corresponding to the virtual file name, the procedure It is characterized in applying the procedure selected by the selecting means is determined by the procedure name output from the virtual file name resolution unit.

According to a fourth aspect of the present invention, in the file system according to the first or second aspect, the virtual file name resolution means receives a parameter for selecting a procedure, and a plurality of virtual file name resolution means correspond to the virtual file name. When the procedure name is obtained, the procedure further comprises procedure selecting means for selecting one or more procedure names from the plurality of procedure names based on the parameter, and the virtual file name solving means is provided with the real file resource position information. Outputting the one or more procedure names selected by the procedure selecting means,
The procedure applying means selects the virtual file name solving means selected by the procedure selecting means for an existing file resource determined by the real file resource position information corresponding to the virtual file name obtained by the virtual file name solving means. It is characterized in that a procedure determined by the procedure name output from is applied.

According to a fifth aspect of the present invention, in the file system according to the first or second aspect, a name parsing means for parsing an input name, a predetermined token, and one or more of the procedure names. And one or more of the procedure names are selected using the procedure management means based on the token appearing in the syntax tree resulting from the syntax analysis by the name analysis means. The virtual file name resolving means outputs the real file resource position information and the one or more procedure names selected by the procedure selecting means, and the procedure applying means, An actual file resource determined by the real file resource position information corresponding to the virtual file name obtained by the virtual file name solving means. Is characterized in applying the procedure determined by the procedure name output from the virtual file name resolution unit is selected by the procedure selection means to.

According to a sixth aspect of the invention, in the file system according to any one of the first to fifth aspects, a single file or a plurality of files corresponding to the virtual file name obtained by the virtual file name solving means are provided. Consists of one or more actual file resource location information and one or more procedure names required to configure a virtual file resource for the virtual file name from the real file resource location information and one or more procedure names And a procedure applying means for applying a procedure defined by the expression generated by the expression generating means.

[0016]

According to the first aspect of the present invention, the virtual file name management means includes the real file resource position information indicating the physical position of the existing file resources that are distributed and arranged on the network, and the file. A virtual file resource management table manages a procedure name, which is the name of one or more procedures for processing resources, and a virtual file name, which is the name of a virtual file resource, in association with each other. The virtual file resource is a file resource obtained by executing a predetermined procedure on a certain existing file resource. Upon receiving the virtual file name, the virtual file name solving means outputs the corresponding procedure name and real file resource position information based on the virtual file resource management table. Based on the actual file resource position information output from the virtual file name resolution means,
By executing the procedure corresponding to the procedure name with respect to the existing resource by the procedure applying means, it becomes possible to access the virtual file resource. As described above, not only the existing file resource but also the virtual file resource obtained as a result of applying the predetermined procedure to the existing file resource can be accessed. Thereby, for example, a virtual file resource having a property desired by the user can be set and the virtual file resource can be accessed by the virtual file name. With such a configuration, the handling of file resources can be virtualized, and the flexibility of the entire network information system can be increased.

According to the second aspect of the invention, the file name management means is a real file name that is the name of an existing file resource that is distributed and arranged on the network,
The file resource management table manages the actual file resource location information indicating the physical location of the existing file resource in association with each other. The conversion procedure management means receives a virtual file name, which is the name of a virtual file resource, as input, and a procedure name, which is the name of one or more procedures for processing the file resource, and a real file name or virtual file name. The file name conversion procedure name that is the name of the file name conversion procedure that outputs the set is managed in the virtual file name correspondence table.
When the virtual file name is input, the virtual file name solving means sequentially applies the file name conversion procedure held in the virtual file name correspondence table to the name. The file name conversion procedure is recursively applied to the obtained virtual file name. For the real file name, the real file resource position information corresponding to the real file name is obtained from the file resource management table. Then, the obtained real file resource position information and the procedure name performed until the real file resource position information is obtained are output. Access is performed by the procedure applying means using the procedure corresponding to the output procedure name. In this way, access to the virtual file resource corresponding to the given virtual file name can be performed to the virtual file resource that is the procedure for the file resource based on the actual file resource position information. It will be executed as an access. This makes it possible to virtualize the handling of file resources and build a highly flexible system.

According to the third aspect of the present invention, the system state obtaining means for obtaining the parameter showing the system state is provided, and the virtual file name solving means obtains a plurality of procedure names corresponding to the virtual file names. When obtained, the procedure selecting means selects one or a plurality of procedure names from the plurality of procedure names obtained based on the parameters obtained by the system state obtaining means. Virtual file name resolution means
One or more procedure names selected by the procedure selecting means are output together with the actual file resource position information. This makes it possible to access virtual file resources that match the system state. The user can access the desired virtual file resource without knowing the system status.

According to the invention described in claim 4, when a parameter for externally selecting a procedure is set and the virtual file name solving means obtains a plurality of procedure names corresponding to the virtual file name. The procedure selecting means selects one or more procedure names from the plurality of procedure names based on the set parameters. The virtual file name solving means outputs one or a plurality of procedure names selected by the procedure selecting means together with the real file resource position information. As a result, the virtual file resource to be accessed can be changed according to the designation from the user or the result of a certain process.

According to the invention of claim 5, the procedure management means has a procedure syntax management table for associating a predetermined token with one or more procedure names, and the inputted name is used for the name analysis means. The procedure selecting means selects one or more procedure names by using the procedure managing means based on the token appearing in the syntax tree as a result of the syntax analysis. The virtual file name resolution means obtains real file resource position information based on the token appearing in the syntax tree as a result of the syntax analysis by the name analysis means, and also determines one or more procedure names selected by the procedure selection means. Output with real file resource location information. By using the result of such a syntax analysis, it becomes possible to instruct, for example, a parameter, a selection procedure, and a necessary real file name when the virtual file name is input. As a result, it is possible to improve flexibility when the user accesses the virtual file resource.

According to the sixth aspect of the invention, the expression generating means generates an expression from the real file resource position information and the procedure name obtained by the virtual file name solving means. Then, the procedure applying means can access the real file resource by the virtual file name using the expression generated by the expression generating means. Therefore, regarding the contents of the processing to be performed on the real file resource necessary to access the virtual file resource,
The user does not need to know, and can automatically access the real file resource only by the virtual file name.

[0022]

1 is a block diagram showing a first embodiment of a file system according to the present invention. In the figure, 1 is a communication unit, 2 is a file name management unit, 3 is a virtual file name management unit, 4 is a procedure management unit, 5 is a file read / write unit, 6 is a procedure application unit, 11 is a file name resolution unit, and 12 is a file name resolution unit. A file resource management table, 13 is a virtual file name resolution unit, 14 is a virtual file resource management table, 15 is a procedure search unit, and 16 is a procedure management table.

The communication unit 1 receives a request for the file system, and according to the contents of the request, the file name management unit 2, the virtual file name management unit 3, the procedure management unit 4, the file read / write unit 5, and the procedure application unit 6 are requested. Make a request. The communication unit 1 corresponds to, for example, a kernel interface in the file system of the UNIX operating system, and an interface portion of a remote procedure call in the file system of the client / server method.

The file name management unit 2 comprises a file name resolution unit 11 and a file resource management table 12. The file resource management table 12 is a table including a binary group of a file name and a physical position of the file. The physical position of a file is, for example, a block number in a disk system, an inode number in a UNIX file system,
It corresponds to the host name on the network and the file name local to the host in the distributed file system. The file name resolution unit 11 checks the file resource management table 12 using the requested file name as a key, and returns the physical position of the file corresponding to the file name. The file name resolution unit 11 can also be configured to have a function of adding or deleting a binary group of a file name and a physical position of the file to the file resource management table 12. In the example shown in FIG. 1, the lines corresponding to name1, name2, ... In the file resource management table 12 are for managing existing files, and are represented by name1, name2 ,. Indicates that the physical location of the file is Loc1, Loc2, ....

The virtual file name management unit 3 comprises a virtual file name resolution unit 13 and a virtual file resource management table 14. The virtual file resource management table 14 is a table composed of a triple of a virtual file name, a physical position of an existing file, and a procedure name. The virtual file name resolution unit 13 checks the virtual file resource management table 14 using the requested virtual file name as a key, and returns the corresponding physical position and procedure name. Further, the virtual file name resolution unit 13 is configured to have a function of adding or deleting a triplet of a virtual file name, a physical position of an existing file, and a procedure name to the virtual file resource management table 14. You can also do it. In the example shown in FIG. 1, vn of the virtual file resource management table 14
The lines corresponding to ame1, vname2, ... Are for managing virtual files. For example, v
The virtual file represented by name1 has the position Lo.
Procedure proc1 for the existing file in c1
Indicates that the file is a virtual file obtained by applying. The virtual file represented by vname4 is a virtual file obtained by applying the procedures proc2 and proc3 to the existing file at the position Loc1 in the order of proc2 and proc3. The virtual file represented by vname5 is a virtual file obtained by applying any one of the procedures proc2 and proc3 to the existing file at the position Loc1. For example, one of a plurality of procedures may be selected depending on whether the request type is read or write.

The procedure management unit 4 comprises a procedure search unit 15 and a procedure management table 16. Procedure management table 1
6 is a table consisting of a procedure name and a binary set of procedure definitions. The procedure search unit 15 checks the procedure management table 15 using the requested procedure name as a key, and returns the corresponding procedure definition. The procedure retrieval unit 15 can also be configured to have a function of adding or deleting a binary set of a procedure name and a procedure definition to the procedure management table 16.

The file read / write unit 5 receives read requests and write requests from the communication unit 1 and the procedure application unit 6. In the case of a read request, the physical position of the file is given, the file stored in the specified position is read, and the read result is returned. In the case of a write request, the physical position of the file and the write contents are given, and the file is written to the specified physical position.

The procedure application section 6 receives a read request and a write request from the communication section 1. In the case of a read request, the physical position of the file and the procedure definition are given, the physical position of the file is given to the file read / write unit 5, and the read request is issued. Procedure application section 6
Performs a procedure on the read result of the file according to the given procedure definition. In case of write request,
The procedure application unit 6 determines the physical location of the file, the procedure definition,
The write content is given, and the result of applying the procedure according to the procedure definition to the given write content is used as the second write content for the file read / write unit 5, and further the physical position is given to make a write request. The procedure application unit 6 generates an expression from the procedure definition received from the communication unit 1 and the physical position of the file, and using the generated expression,
It is also possible to configure so that the information read from the file is processed, or the information to be written is processed and the write request is made so as to be written in the file.

FIG. 2 shows the first file system of the present invention.
3 is a flowchart showing an example of an operation in the embodiment of FIG. FIG. 2 shows a case where a read request is made. First, in S31, the communication unit 1 receives a file name and a read request. In S32, the communication unit 1 makes a file name resolution request to the file name management unit 2 so as to resolve the received file name. If the requested file name is registered in the file resource management table 12, the file name management unit 2 returns a binary set of the file name and its physical position, and if not registered, returns it as undefined. .

In S33, it is determined whether or not the answer from the file name management section 2 is undefined. If not, the received name is an actual file name. Communication unit 1
In step S34, the file read / write unit 5
The physical position of the file obtained from the file name management unit 2 is passed, the content is read from the physical position and returned to the request source.

In S33, if the answer from the file name management unit 2 is undefined, the communication unit 1 proceeds to S35.
At, the virtual file name management unit 3 is requested to resolve the file name. If the requested file name is registered in the virtual file resource management table 14, the virtual file name management unit 3 returns a triplet of the virtual file name, the physical position of the existing file, and the procedure name. In S36, it is determined whether the triplet set is returned from the virtual file name management unit 3 or is undefined, and if it is undefined, it is returned to the request source as a file name error.

When the triplet is obtained in S36, the communication section 1 requests the procedure management section 4 for a procedure definition corresponding to the procedure name obtained in the virtual file name management section 3 in S37. If the requested procedure name is registered in the procedure management table 16, the procedure management unit 4 returns a binary set of the procedure name and the procedure definition. In S38, it is determined whether a binary set has been obtained from the procedure management table 16 or is undefined, and if undefined, an error indicating that the procedure is undefined is returned to the request source.

When the binomial set is obtained in S38, the communication section 1 determines the physical position of the actual file obtained from the virtual file name management section 3 with respect to the procedure application section 6 in S39, A read request is issued together with the procedure definition obtained from the procedure management unit 4. The procedure application unit 6 further passes the physical position of the existing file to the file read / write unit 5 to make a read request. The information read from the file read / write unit 5 executes the procedure based on the procedure definition in the procedure application unit 6, and the read information on the executed procedure is returned from the communication unit 1 to the request source.

The processing when the requested access to the file is a write request is only the processing of S34 and S39 in the flowchart shown in FIG. That is, when the given file name is the file name corresponding to the existing file, the communication unit 1 determines the physical position of the file obtained from the file name management unit 2 and the information to be written in the file reading / writing unit. A write request is made by passing it to 5. Then, the file read / write unit 5 writes the information to be written in the physical position of the file. If the given file name is a virtual file name, the communication unit 1 passes the physical position of the file, the procedure definition and the information to be written to the procedure application unit 6. The procedure application unit 6 performs a procedure based on the procedure definition on the information to be written, and stores the information together with the physical position of the file in the file reading / writing unit 5.
Pass to. The file reading / writing unit 5 writes the written information to which the procedure is applied, in the physical position of the file passed from the procedure application unit 6.

The above operation will be described below by using a specific example. Here, the file resource management table 12, the virtual file resource management table 14, and the procedure management table 16 will be described based on a specific example assuming that the information shown in FIG. 1 is stored.

First, the communication unit 1 is given a file name nam
The operation when a read request is made by designating e1 will be described. When the communication unit 1 receives the read request for the file indicated by the file name name1, the communication unit 1 sends the file name na to the file name resolution unit 11 of the file name management unit 2.
Request to resolve the file name corresponding to me1. The file name resolution unit 11 searches the file resource management table 12 using the file name name1 as a key, and sets <nam
The binomial set of e1, Loc1> is obtained. Then, this is returned to the communication unit 1 as a result. The communication unit 1 determines that this file is an existing file because the corresponding item is stored in the file resource management table 12. Communication unit 1
Passes the physical position Loc1 of the file to the file read / write unit 5 to make a read request. The file read / write unit 5 reads the file at the position Loc1 and returns the read result to the communication unit 1. The communication unit 1 returns the read result to the read requester.

Next, the file name vna for the communication unit 1
The operation when a read request is made by designating me1 is shown. When the communication unit 1 receives the read request for the file indicated by the file name vname1, it sends the file name vn to the file name resolution unit 11 of the file name management unit 2.
Request to resolve the file name corresponding to ame1. The file name resolution unit 11 uses the file name vname1.
The file resource management table 12 is searched by using as a key, but since the corresponding item does not exist, the result is returned as undefined.

The communication unit 1, which has received the undefined result from the file name resolution unit 2, causes the virtual file name resolution unit 13 of the virtual file name management unit 3 to resolve the file name corresponding to the file name vname1. Request. The virtual file name resolution unit 13 uses the virtual file resource management table 14
To obtain a triplet of <vname1, Loc1, proc1>. The communication unit 1 uses the virtual file resource management table 1
Since the item corresponding to 4 has been stored, it is determined that this file is a virtual file. The communication unit 1, which has received the result of the above-mentioned triplet from the virtual file name management unit 3, instructs the procedure search unit 15 of the procedure management unit 4 to
Request the procedure definition corresponding to the procedure name proc1.
The procedure search unit 15 searches the procedure management table 16 using the procedure name proc1 as a key, and <proc1, def1>
Is returned as a result.

The communication unit 1 passes the physical position Loc1 and the procedure definition def1 to the procedure application unit 6. The procedure application unit 6 passes the physical position Loc1 to the file read / write unit 5 and makes a read request. File read / write unit 5
Reads from the physical position Loc1 and returns the read result to the procedure application unit 6. The procedure application unit 6 applies the procedure to the read result according to the procedure definition,
The second read result is returned to the communication unit 1. The communication unit 1 returns the second read result received from the procedure application unit to the read requester.

The operation when a write request is made to the communication unit 1 is almost the same as the above-mentioned operation. For example, when a write request is made to the communication unit 1 by designating the file name name1, the communication unit 1 obtains from the file name management unit 2 a binary combination of <name1, Loc1>, and The physical position Loc1 and write information are passed to the read / write unit 5 to the file read / write unit 5 to make a write request. The file read / write unit 5 has a physical position L.
Write information is written to oc1. When a write request is made to the communication unit 1 by designating the file name vname1, the communication unit 1 sends <vname1, Loc1, proc to the virtual file name management unit 3.
1> three-tuple, and from the procedure management unit 4 <p
roc1, def1> is obtained, and the physical position Lo is obtained.
The c1 and the procedure definition def1 are passed to the procedure application unit 6. The procedure application unit 6 performs a procedure defined by the procedure definition def1 on the write information from the requester, passes the second write information together with the physical position Loc1 to the file read / write unit 5, and issues a write request. The file read / write unit 5 sends the second write information to the physical position Loc.
Write to 1.

FIG. 3 shows the second file system of the present invention.
It is a block diagram showing an embodiment of the. The same parts as those in FIG. 1 are designated by the same reference numerals and the description thereof will be omitted. Reference numeral 17 is a virtual file name correspondence section, and 18 is a virtual file name correspondence table.
In this embodiment, the virtual file name management unit 3 also holds and manages the file resource management table 12. The virtual file name correspondence table 18 is a table including file name conversion procedures. The file name conversion procedure, which is an element of the virtual file name correspondence table 18, is a procedure in which a file name is input and a set of procedure definition and file name is output. The virtual file name correspondence unit 17 is given a file name and returns the procedure definition as a result.

FIG. 4 is a flow chart showing an example of the operation in the second embodiment of the present invention. FIG. 4 shows an example of the operation when a read process is requested. S
At 41, the communication unit 1 receives the file name and the read request. The communication unit 1 makes a file name resolution request to the virtual file name management unit 3 so as to resolve the received file name. In the virtual file name management unit 3, S
At 42, the file resource management table 12 is searched using the file name received by the virtual file name resolution unit 13 as a key. If the received file name exists in the file resource management table 12, the file name and the physical position of the file corresponding to the file name are obtained from the file resource management table 12. If it does not exist, it is undefined. In S43, it is determined whether the search result of the file resource management table 12 is undefined. If it is not undefined, the requested file name corresponds to an existing file. In S44, the communication unit 1 receives the file name and the physical position of the file from the virtual file name management unit 3 and passes the physical position of the file to the file read / write unit 5 to make a read request.
The file reading / writing unit 5 reads information from the physical position of the received file and returns it to the request source via the communication unit 1.

Also, undefined in S43, that is,
If the requested filename is a virtual filename, then
In S45, for the virtual file name corresponding unit 17,
Request resolution of virtual file names. In S46, it is determined whether or not the virtual file name corresponding unit 17 has been able to solve the problem. If the resolution is successful, the virtual file name correspondence unit 17 returns the procedure definition and the file name to the virtual file name resolution unit 13. In the virtual file name correspondence unit 17, in S47,
The corresponding physical position is obtained from the file name using the file resource management table 12, and is returned to the communication unit 1 together with the procedure definition. In S48, the communication unit 1 passes the procedure definition and the physical position of the file to the procedure application unit 6 and makes a read request. The procedure application unit 6 passes the physical position of the file to the file read / write unit 5, and makes a read request. The file read / write unit 5 reads information from the physical position of the received file and passes it to the procedure application unit 6. The procedure application unit 6 performs a procedure based on the procedure definition on the information read by the file read / write unit 5,
It is returned to the request source via the communication unit 1.

When a write request is made, only the steps S44 and S48 of the flowchart shown in FIG. 4 are different. If the file name received by the communication unit 1 corresponds to an existing file,
As a process corresponding to S44, the communication unit 1 passes write information to the file read / write unit 5 together with the physical position of the file obtained from the virtual file name management unit 3. The file read / write unit 5 writes the write information in the physical position of the received file. If the file name received by the communication unit 1 is a virtual file name, the communication unit 1 performs processing corresponding to S48 together with the procedure definition obtained from the virtual file name management unit 3 and the physical position of the file. , Write information is passed to the procedure application unit 6 to make a write request. The procedure application unit 6 performs a procedure on the write information based on the procedure definition, and, together with this information, the physical position of the file is read by the file read / write unit 5
Pass to. The file read / write unit 5 writes the write information after the procedure is applied to the physical position of the file.

FIG. 5 is a flow chart showing an example of the operation of the virtual file name correspondence unit 17 in the second embodiment of the present invention. First, in S51, the file name conversion procedure is extracted from the first entry of the virtual file name correspondence table 18. In S52, the extracted file name conversion procedure is applied to the file name. In S53, it is determined whether or not the result of applying the file name conversion procedure to the file name is undefined.
In step 4, it is determined whether or not the next file name conversion procedure exists. If the next file name conversion procedure does not exist, the procedure definition is undefined and the virtual file name corresponding part 1
The process of 7 is completed. If the next file name conversion procedure exists, the next file name conversion procedure is retrieved from the virtual file name correspondence table 18 in S55, and the process returns to S52 to perform the file name conversion procedure.

If the result is not undefined in S53, the file resource management table 12 is searched for each element of the set of file names obtained as a result of the file name conversion procedure in S56. In S57, it is determined whether or not all file names exist in the file resource management table 12. If all the file names exist in the file resource management table 12, in S58,
A new procedure definition is created by replacing the file name of the procedure definition obtained by executing the file name conversion procedure with the physical position of the existing file obtained from the file resource management table 12, and the new procedure created The definition is returned as a result and the process ends.

In S57, if there is a file name that is not described in the file resource management table 12 in the elements of the file name set, in S59, each one is recursively shown in FIG. The algorithm shown is executed, and in S60, the file name in the procedure definition is replaced with the procedure definition obtained by the recursive execution. However, if the same name needs to be converted again during the conversion of a certain name, the result is undefined.

An example of the above operation will be described based on a specific example. It is assumed that information is stored in the file resource management table 12 and the virtual file name correspondence table 18 as shown in FIG. Here, the file name conversion procedure NProc1 is
If the given file name is N. When it is Z, the character string ".Z" is removed from the end of this file name, and the file name N
It is assumed that this is a procedure that returns a set having only elements and an expression Proc1 (N). File name conversion procedure N
It is assumed that Proc2 is a procedure that returns a set of Proc2 (N ′) and a set having only a file name N ′ in which all the characters that make up a given file name N are capitalized, as an element.

Now, name1. It is assumed that the file name Z has been requested to be read.
The operation in this case will be described below. In S41, the communication unit 1 receives this request and requests the virtual file name management unit 3 to resolve the file name. Virtual file name resolution unit 1
3 is the file name given in S42
1. The file resource management table 12 is searched using Z as a key. However, since there is no corresponding item, the process proceeds from S43 to S45, and the file name name1. Request resolution of Z.

The virtual file name correspondence unit 17 executes the algorithm shown in FIG. That is, in S51, the first file name conversion procedure Nproc1 is extracted from the virtual file name correspondence table 18, and in S52,
File name name1. Applies to Z. As a result, the file name conversion procedure NProc1 has a file name set name1 and a procedure definition Proc1 (name).
1) is output. This output is not undefined, so S5
From S3 to S56, the file resource management table 12 is searched using the element name1 of the output file name set as a key. However, since there is no corresponding item, S57
From S to S59, the algorithm 1 is recursively applied to the file name name1.

In step S51, the file name conversion procedure Nproc1 is retrieved from the virtual file name correspondence table 18, and is applied to the file name name1 in step S52. Since this result is undefined and there is a next file name conversion procedure, the process proceeds from S53 to S54 and S55, and from the virtual file name correspondence table 18, the next file name conversion procedure Nproc
2 is taken out and applied to the file name name1 in S52. As a result, the file name conversion procedure NProc
2 is a set NAME1 of file names and a procedure definition Pr
oc2 (NAME1) is output. Since this result is not undefined, the process proceeds from S53 to S54, and the file resource management table 1 is created using the element NAME1 of the file name set as a key.
2 is searched, and as a result, the physical position Loc of the file is found.
Get one. As a result, the file name conversion procedure Nproc
Since all of the set of file names obtained by applying 2 exist in the file resource management table 12, S
The process proceeds from 57 to S58, and the file name NAME1 of the procedure definition Proc2 (NAME1) is set to the physical position Loc1 of the file based on the search result of the file resource management table 12.
Replaced with new procedure definition Proc2 (Loc1)
Get. As a result, the recursive processing is terminated and the original processing is returned to.

In S60, the procedure definition Pr
The procedure name Proc2 (Lo) obtained by the recursive processing of the file name name1 of oc1 (name1)
c1) and new procedure definition Proc1 (Pr
oc2 (Loc1)), and the virtual file name corresponding part 1
The process of 7 is completed.

By the processing of the virtual file name correspondence unit 17 as described above, the file names name1. Since Z has been resolved, the process proceeds from S46 to S47, and the virtual file name resolution unit 13 sends the procedure definition Pro from the virtual file name correspondence unit 17.
It receives c1 (Proc2 (Loc1)) and passes it to the procedure applying section 6 via the communication means 1. At this time, S
As shown by 47, the physical position of the file is set in the file resource management table 12 for the obtained set of file names.
It may be passed to the procedure application unit 6 together with the procedure definition.

In step S48, the procedure application unit 6 requests the file read / write unit 5 to read the file represented by the physical position Loc1 of the file.
The procedure application unit 6 receives the read result of the file from the file read / write unit 5, and performs the procedure P for the result.
Apply roc2 to get the second result. Further, the procedure Proc1 is applied to the second result to obtain the third result. The communication unit 1 receives the third result from the procedure applying unit 6 and returns this to the read requester.

FIG. 6 shows a third file system of the present invention.
It is a block diagram showing an embodiment of the. In the figure, the same parts as those in FIG. Reference numeral 19 is a system state acquisition unit, and 20 is a procedure selection unit. In this embodiment, an example in which the system status acquisition unit 19 and the procedure selection unit 20 are provided in the virtual file name management unit 3 in the above-described first embodiment is shown. Of course, it is also possible to configure based on the second embodiment described above.

The system state acquisition unit 19 returns a parameter determined by the system state in response to a request from the procedure selection unit 20. The procedure selection unit 20 passes the file name to the virtual file name resolution unit 13, selects the procedure indicated by the parameter returned by the system state acquisition unit 19 from the plurality of procedure names returned as a result, and communicates. Returns the physical location of the file and the selected procedure name in Part 1.

An example of the operation of the third embodiment of the file system of the present invention will be described. As a specific example, an operation when a read request is made by designating the file name vname5 to the communication unit 1 will be shown. The system status acquisition unit 19 returns "2" as a parameter corresponding to the current system status.

When the communication unit 1 receives the read request for the file indicated by the file name vname5, it requests the file name resolution unit 11 of the file name management unit 2 to perform the file name resolution corresponding to the file name vname5. . The file name resolution unit 11 uses the file name vnam
The file resource management table 12 is searched using e5 as a key.
However, since the corresponding item does not exist, the result is returned as undefined.

The communication unit 1, which has received the undefined result from the file name resolution unit 11, requests the procedure selection unit 20 of the virtual file name management unit 3 to resolve the file name corresponding to the file name vname5. The procedure selection unit 20 requests the virtual file name resolution unit 13 to resolve the file name corresponding to the file name vname5, and at the same time queries the system state acquisition unit 19 about the current system state.

The virtual file name resolution unit 13 uses the file name vname5 as a key to create a virtual file resource management table 14
And search for <vname5, Loc2, proc2 + p
Obtain the triplet of loc3>. On the other hand, the system status acquisition unit 19 passes the parameter “2” corresponding to the current system status to the procedure selection unit 20.

The procedure selection unit 20 uses the procedure name "proc2 +" in the triplet obtained by the virtual file name resolution unit 13.
From "proc3", the second "proc3" is selected according to the parameter "2", and <vname5,
Returns the triplet of Loc2, proc3>.

The communication unit 1 requests the procedure search unit 15 of the procedure management unit 4 for the procedure definition corresponding to the procedure name proc3. The procedure search unit 15 searches the procedure management table 16 and returns the 2-item set <proc3, def3> to the communication unit 1 as a result. The communication unit 1 stores the physical position Loc2 of the file and the procedure definition def4 in the procedure application unit 6
Pass to. The procedure application unit 6 determines the physical position L of the file.
oc2 is passed to the file read / write unit 5 to make a read request. The file read / write unit 5 reads from the physical position Loc2 of the file and returns the read result to the procedure application unit 6. The procedure applying unit 6 determines the procedure definition d.
According to ef4, the read result is processed and the second result is returned to the communication unit 1. The communication unit 1 returns the second result received from the procedure application unit 6 to the read requester.

Here, in the case of a read request,
Although the description has been given based on the specific example, the same can be applied to the case of the write request. For example, in the write request to the file name vname5, the procedure application unit 6
Performs the procedure on the information to be written according to the procedure definition def4 to obtain the second write information. Then, the file read / write unit 5 is requested to write the second write information to the physical position Loc2 of the file.

FIG. 7 shows the fourth file system of the present invention.
It is a block diagram showing an embodiment of the. In the figure, the same parts as those in FIG. Reference numeral 21 is a procedure selection unit. In this embodiment, an example in which the procedure selection unit 21 is provided in the virtual file name management unit 3 in the first embodiment described above is shown. Of course, it is also possible to configure based on the second embodiment described above.

The procedure selection unit 21 is given a file name and a parameter from the communication unit 1, passes the file name to the virtual file name resolution unit 13, and selects the procedure indicated by the parameter from the plurality of procedures returned as a result. Then, the physical location of the file and the selected procedure are returned to the communication unit 1.

The parameters used by the procedure selection unit 21 are
In addition to the configuration obtained through the communication unit 1, the user may manually configure the setting with a keyboard or the like, or may be configured to use the result of executing a certain process.

An example of operation in the fourth embodiment of the file system of the present invention will be described. As a specific example, the file name vname5 and the parameter “2” are set for the communication unit 1.
Shows the operation when a read request is made by designating.

When the communication unit 1 receives the read request for the file in which the file name vname5 and the parameter "2" are designated, the communication unit 1 separates the file name and the parameter and sends the file to the file name resolution unit 11 of the file name management unit 2. Request to resolve the file name corresponding to the name vname5. The file name resolution unit 11 uses the file name vnam
The file resource management table 12 is searched by using e5 as a key, but since the corresponding item does not exist, the result is returned as undefined.

The communication unit 1 having received the undefined result from the file name resolution unit 11 causes the procedure selection unit 21 of the virtual file name management unit 3 to resolve the file name corresponding to the file name vname5 and the parameter "2". Ask to do. The procedure selection unit 21 uses the virtual file name resolution unit 13
Is requested to perform name resolution corresponding to the file name vname5. The virtual file name resolution unit 13 searches the virtual file resource management table 14 using the file name vname5 as a key, and <vname5, Loc2, pro
The triplet of c2 + proc3> is obtained. Procedure selection unit 21 that receives the search result from the virtual file name resolution unit 13
Is the procedure name “proc2 + proc3” in the triplet
From the second "proc" according to the parameter "2"
3 ”is selected and <vname5, Loc2,
Returns the triplet of proc3>.

The communication unit 1 requests the procedure search unit 15 of the procedure management unit 4 for the procedure definition corresponding to the procedure name proc3. The procedure search unit 15 uses the procedure management table 16
And returns the binary set of <proc3, def3> to the communication unit 1 as a result. The communication unit 1 stores the physical position Loc2 of the file and the procedure definition def4 in the procedure application unit 6
Pass to. The procedure application unit 6 determines the physical position L of the file.
oc2 is passed to the file read / write unit 5 to make a read request. The file read / write unit 5 reads from the physical position Loc2 of the file and returns the read result to the procedure application unit 6. The procedure applying unit 6 determines the procedure definition d.
According to ef4, the read result is processed and the second result is returned to the communication unit 1. The communication unit 1 returns the second result received from the procedure application unit 6 to the read requester.

FIG. 8 shows the fifth file system of the present invention.
It is a block diagram showing an example of. In the figure, the same parts as those in FIG. 22 is a lexical analysis unit, 23 is a name syntax analysis unit, 24 is a procedure selection unit,
Reference numeral 25 is a procedure syntax management table, 26 is a lexical type table, and 27 is a delimiter information table. In this embodiment, the virtual file name management unit 3 includes a lexical analysis unit 22, a name syntax analysis unit 23,
A configuration having a procedure selection unit 24 is shown. The virtual file name management unit 3 also includes a file name management unit 2 having a file name resolution unit 11 and a file resource management table 12. In addition to this, the virtual file name management unit 3 holds and manages the procedure syntax management table 25, the lexical type table 26, and the delimiter information table. The virtual file name management unit 3 in this embodiment, when the name given as the input is not described in the file resource management table 12, decomposes the name into the lexical unit by the lexical analysis unit 22 and then the lexical string into the name syntax. By performing analysis by the analysis unit 23 and the procedure syntax management table 25 and passing the analysis result to the procedure selection unit 24, the procedure for the given name is obtained.

The lexical analysis unit 22 uses the procedure syntax management table 25.
Also, the delimiter information table 27 is used to cut out a token from the character string forming the given name and register it in the token type table 26.

The syntax analysis unit 23 checks the type of each of the tokens cut out by the token analysis unit 22, registers it in the token type table 26, and checks the priority of each token from the procedure syntax management table 25 to generate a syntax tree. It is passed to the procedure selection unit 24.

The procedure selecting unit 24 checks the physical position of the file from the file resource management table 12 for the lexical characters whose types are registered as names in the lexical type table 26, and from the syntax tree and the procedure syntax management table 25, the procedure. Select.

The procedure syntax management table 25 is a table used when the name syntax analysis unit 23 performs syntax analysis. FIG.
It is an explanatory view of an example of procedure syntax management table 25. The procedure syntax management table 25 includes operator names such as keywords appearing in file names, operator types, priorities, and procedure selection rules. In the figure, “scale” and “Z” represent operator names, and “x.scale.y” and
"X.Z" represents the type of operator,
“2” and “1” respectively represent the priority order, and “pnm”
scale (y, x) ”,“ compress (x) ”
Represents the procedure selection rule.

The lexical type table 26 is registered in the lexical analysis unit 22 and the name syntax analysis unit 23, and the procedure selection unit 24.
Is a table referred to in. It is an empty table when the file name is passed to the virtual file name management unit 3. FIG. 10 is an explanatory diagram of an example of the lexical type table 26. Lexical type table 2
6 stores a lexical segment extracted by the lexical analysis unit 22 and a type associated by the name syntax analysis unit 23. In FIG. 10, the lexical analysis unit 22 uses three lexical characters “image”.
“E”, “scale”, and “2” are cut out and registered in the lexical type table 26. As types corresponding to each lexical, “name”, “operator”, and “parameter” are name syntaxes. The analysis unit 23 is associated with each other.

The delimiter information table 27 holds information about delimiters inserted between each lexical segment when the lexical segmentation unit 22 cuts out the lexical segment. FIG. 11 is an explanatory diagram of an example of the delimiter information table 27. In FIG. 11, “.” Is registered as the delimiter. The lexical analysis unit 22 searches for a delimiter "." In the file name, and cuts out a lexical character before and after the delimiter.

An example of operation in the fifth embodiment of the file system of the present invention will be described. FIG. 12 is a flowchart illustrating the operation of the virtual file name management unit 3.
If the file name given as input is not described in the file resource management table 12, the virtual file name management unit 3 divides the given file name into lexical characters by the lexical analysis unit 22 and then names the lexical string. The syntax analysis unit 23 analyzes using the procedure management table 15, and passes the analysis result to the procedure selection unit 24. Then, the procedure selection unit 24 obtains the physical position and procedure of the file based on the analysis result.

First, in S71, a file name is accepted. Then, in S72, the received file name is searched from the file resource management table 12. At this time, it is determined whether or not the file name is in the file resource management table 12 in S73.
If the file name exists in the file resource management table 12, the file resource management table 12 is determined in S74.
The physical location of the file is obtained from and returned as the result of the inquiry, and the processing ends.

In S73, the file resource management table 12
If there is no file name accepted in S75, S75
In, the lexical part is cut out from the file name accepted by the lexical analysis part 22. At this time, it is determined in S76 whether or not the token can be cut out. If the token cannot be cut out, in S77, the communication unit 1 is notified that there is no corresponding file name, and the process is ended.

When the lexical analysis unit 22 can extract the lexical item in S75, the process proceeds from S76 to S78, and the name syntax analysis unit 23 creates a syntax tree. At this time, it is determined in S79 whether the syntax tree can be created. If the syntax tree cannot be created, in S80,
The communication unit 1 is informed that the file name is incorrect, and the process ends.

If the syntax tree can be created in S78, the process proceeds from S79 to S81, and the procedure selecting section 24 selects a procedure. At this time, it is determined in S82 whether or not the procedure can be selected. If the procedure cannot be selected, in S83, the communication unit 1 is notified that the procedure has failed to be selected, and the process ends.

If the procedure can be selected in S81, S
The process proceeds from S82 to S84, and the physical position of the obtained file and the selected procedure are returned to the communication unit 1 as a result of the inquiry.

The communication section 1 receives the physical position of the file returned from the virtual file name management section 3 and the selected procedure. Then, the procedure search unit 1 of the procedure management unit 4
Request a procedure definition corresponding to the procedure name from 5.
The procedure search unit 15 searches the procedure management table 16 using the procedure name as a key and returns the procedure definition. The communication unit 1 passes the physical position of the file, the procedure definition, and the type of read or write to the procedure application unit 6. In the case of writing, information to be written is also passed.

When the instruction from the requester is to read the file, the procedure application section 6 passes the physical position of the file to the file read / write section 5 to make a read request. The file read / write unit 5 reads from the physical position of the file, and the read result is read by the procedure application unit 6
Return to. The procedure application unit 6 performs a procedure on the read result according to the procedure definition and returns the second result to the communication unit 1. The communication unit 1 returns the second result received from the procedure application unit 6 to the read requester.

If the instruction from the requester is to write the file, the procedure application unit 6 applies the procedure to the information to be written according to the procedure definition, and the file read / write unit 5 along with the physical position of the file. Pass to.
The file read / write unit 5 is located at the physical position of the file.
Write the information that should be written after applying the procedure.

Next, in the flow of processing shown in FIG.
The lexical segmentation processing performed by the lexical analysis unit 22 in S75 will be described. FIG. 13 is a flowchart for explaining an example of the operation of the lexical analysis unit 22. As described above, the lexical analysis unit 22 uses the procedure syntax management table 25 and the delimiter information table 27 to cut out a lexical character from the character string forming the given file name and registers it in the lexical type table 26.

In S91, first, the delimiter information table 27
Delimiter information is obtained from and it is checked whether or not there is a delimiter in the character string that constitutes the file name. In S92, it is determined whether or not the delimiter is present. If the delimiter is not present, it is determined that the lexical segmentation has failed, and the process ends. If the delimiter exists, the character string delimited by the delimiter is cut out as a token in S93. Then, in S94, the cut-out token is registered in the token type table 26, and the processing is ended.

Next, in the flow of processing shown in FIG.
The processing of creating a syntax tree by the name syntax analysis unit 23 performed in S78 will be described. FIG. 14 is a flowchart for explaining an example of the operation of the name parsing unit 23. As described above, the name parsing unit 23 checks the type of each lexical part extracted by the lexical analyzing unit 22, registers it in the lexical type table 26, and checks the priority order of each keyword from the procedure syntax management table 25. Then, a syntax tree is created and passed to the procedure selection unit 24.

First, in S101, it is determined whether or not all the tokens have been processed. If there is an unprocessed lexical item, the unprocessed lexical item is set to the lexical type table 2 in S102.
Take one out of six. The file resource management table 12 is searched based on the extracted token, and it is determined in S103 whether the extracted token is described as an item of the file name in the file resource management table 12. If the token is described in the file resource management table 12, the type corresponding to the token is set to “name” in S104,
Register in the lexical type table 26. Then, the process returns to S101, and the process for the next token is continued.

If the token is not described in the file resource management table 12 in S103, the procedure syntax management table 25 is searched based on the token. In S105, it is determined whether or not the lexical is described in the procedural syntax management table 25, and if so, the lexical type table 26 in which the type corresponding to the lexical is set as the "operator name" in S106.
Register with. If the token is not listed in the procedural syntax management table 25, the type corresponding to the token is registered in the token type table 26 as a “parameter” in S107. In either case, the process returns to S101 to continue the process for the next token.

When the processing for all the tokens is completed in S101, the token registered as the operator name in the token type table 26 in S108 is
Check each priority from the procedure syntax management table 25,
Create a syntax tree and finish the process.

Next, in the processing flow shown in FIG.
The procedure selecting process performed by the procedure selecting unit 24 in S81 will be described. FIG. 15 is a flowchart for explaining an example of the operation of the procedure selection unit 24. As described above, the procedure selection unit 24 checks the physical position of the file from the file resource management table 12 for the lexical type registered in the lexical type table 26 as “name”, and also the name syntax analysis unit. A procedure is selected from the syntax tree created in step 23 and the procedure management table 25.

First, in S111, the lexical type table 2
The tokens whose type is registered as “name” in 6 are taken out, and the file resource management table 12 for these tokens is extracted.
To find the physical location of the corresponding file.
Subsequently, in S112, the procedure syntax management table 25 is searched based on the syntax tree created by the name syntax analysis unit 23 to obtain the procedure. The physical position of the file thus obtained and the selected procedure are returned to the communication unit 1 as a result of the file name resolution in the virtual file name management unit 3.

An example of the operation of the above fifth embodiment will be described based on a concrete example. For example, the name is transmitted to the name resolution unit 2 from a virtual resource implementation unit (not shown) or the like. Here, "image1.s", which is the name of a virtual file obtained by doubling the image file called image1.
calle. A case where a read request is made by designating the name "2" will be described. File resource management table 1
2 and the procedure management table 16 store information as shown in FIG. The procedure syntax management table 25 stores the contents shown in FIG. 9, and the delimiter information table 27 stores the contents shown in FIG. The lexical type table 26 is empty in the initial state. As a description method of the syntax tree generated by the name syntax analysis unit 23, the children c1 ,. . . , Cn are represented as (p c1 ... cn).

From the request source to the communication unit 1, "image
e1. scale. A file name "2" and a read request are transmitted. The communication unit 1 that has received the file name
Passes this name to the virtual file name management unit 3. When the virtual file name management unit 3 receives the file name “image1.scale.2” in S71 of FIG. 12,
In S72, the file name "image1.scal"
e. 2 "is checked in the file resource management table 12. The file name" image1. scale. 2 "
Is not present in the file resource management table 12, it is passed to the lexical analysis unit 22.

The lexical analysis unit 22 cuts out a lexical token from the file name in S75. First, in S91 of FIG. 13, delimiter information is obtained from the delimiter information table 27. The obtained delimiter is ".". File name "imag
e1. scale. 2 ”is the delimiter“. ”Exists, the lexical analysis unit 22 determines in S93 that the delimiter“. Based on the file name "image1. s
calle. 2 ”to the words“ image1 ”,“ scal ”
"e" and "2" are cut out, and in S94, the cut-out phrase is registered in the phrase type table 26, and
The name is passed to the name parsing unit 23. At this point, in the lexical type table 26, only the lexical column in the table shown in FIG. 10 is registered. The type field remains undefined.

The name syntax analysis unit 23 generates a syntax tree in S78 of FIG. First, S10 of FIG.
In FIG. 2, the token “image1” is the token type table 26.
Then, in S103, it is checked whether or not it is described in the file name item of the file resource management table 12. The token "image1" is the file resource management table 1
2 in S104, the token "i"
The type corresponding to “mag1” is registered in the lexical type table 26 as “name”.

Next, in S102, the token "scal
It is checked whether or not "e" is extracted from the lexical type table 26 and is described in the file name item of the file resource management table 12 in S103. The lexical "scale" is not described in the file resource management table 12. , S10
5, the token “scale” is the procedure syntax management table 2
Check whether or not it is described in 5. Lexical "scal
Since "e" is listed in the procedure syntax management table 25, S10
6, the type is registered in the lexical type table 26 as “operator name”.

Next, in S102, it is checked whether or not the token "2" is retrieved from the token type table 26, and in S103, it is described in the file name item of the file resource management table 12. Since the token "2" is not listed in the file resource management table 12, it is checked in step S105 whether the token "2" is listed in the procedure syntax management table 25. Since the token "2" is not described in the procedure syntax management table 25, the type is registered in the token type table as "parameter" in S107.

Now, the types for all the tokens registered in the token type table 26 are registered. FIG. 10 shows the lexical type table 26 completed in this way. The process proceeds from S101 to S108.

In step S108, the name syntax analysis unit 23 creates a syntax tree from the lexical type table 26 shown in FIG. 10 and the procedure syntax management table 25 shown in FIG. As a method of creating a syntax tree, for example, operator rank syntax analysis (Science Inc., AV Aho, R. Seth)
i, J. D. Ullman, Compiler I, P245)
And the like can be used. By the syntax tree analysis, a syntax tree “(scale image12)” is created and passed to the procedure selection unit 24.

The procedure selecting section 24 selects a procedure in S81 of FIG. First, in S111 of FIG. 15, for the lexical item “image1” whose type is registered as “name” in the lexical type table 26, the physical position “locatio” of the file is found from the file resource management table 12.
n1 "is obtained. Further, in S112, the syntax tree" (scale image generated by the name parsing unit 23 is generated.
The procedure “pnmscale” is referred to by referring to the procedure syntax management table 25 based on the node “scale” of “e12)”.
Get (y, x). "Image1" and "2", which are children of the parent "scale" of the syntax tree, are associated with x and y, respectively, and "image1" is assigned to the file resource management table 12.
Physical location of the file obtained from "locatio"
By substituting "n1" for the procedure "pnmsc
ale (2, location1) ”. The physical location“ location ”of the resource thus obtained
1 ”and the procedure“ pnmscale (2, locati
on1) "will be sent to the communication unit 1 in S84.

The communication unit 1 uses the file name "image1.
scale. 2 ”physical location of file“ location1 ”and selected procedure“ pnm ”
The communication unit 1 requests the procedure definition corresponding to the procedure name pnmscale from the procedure search unit 15 of the procedure management unit 4. The procedure search unit 15 uses the procedure name pnmscale as a key. Search the procedure management table 16 for <pnmsca
Returns a binary set of le, def1> as a result. The communication unit 1 passes the physical position location1 of the file and the procedure definition def1 to the procedure application unit 6. The procedure application unit 6 determines the physical position of the file
n1 is passed to the file read / write unit 5 to make a read request. The read / write unit 5 determines the physical position of the file
The data is read from the application 1 and the read result is returned to the procedure application unit 6. The procedure applying unit 6 determines the procedure definition d.
According to ef1, the read result is processed and the second result is returned to the communication unit 1. Communication section 1 is procedure application section 6
Returns the second result received from the read requester.

[0105]

As is apparent from the above description, according to the present invention, a predetermined procedure is applied to an existing file resource in a file system for handling a file resource dispersedly arranged on a network. By allowing access to the resulting virtual file resource, the flexibility of handling the file resource can be increased. At this time, it is possible to realize by managing the virtual name and the procedure in association with each other without actually generating the virtual file resource and associating it with the physical position. By using the file system of the present invention, it is possible to increase the flexibility of handling the file resources of the network information system.

[Brief description of drawings]

FIG. 1 is a block configuration diagram showing a first embodiment of a file system of the present invention.

FIG. 2 is a flowchart showing an example of operation in the first embodiment of the file system of the present invention.

FIG. 3 is a block diagram showing a second embodiment of the file system of the present invention.

FIG. 4 is a flowchart showing an example of operation in the second exemplary embodiment of the present invention.

FIG. 5 is a flowchart showing an example of an operation of a virtual file name correspondence part 17 in the second example of the present invention.

FIG. 6 is a block diagram showing a third embodiment of the file system of the present invention.

FIG. 7 is a block diagram showing a fourth embodiment of the file system of the present invention.

FIG. 8 is a block diagram showing a fifth embodiment of the file system of the present invention.

9 is an explanatory diagram of an example of a procedure syntax management table 25. FIG.

10 is an explanatory diagram of an example of the lexical type table 26. FIG.

11 is an explanatory diagram of an example of a delimiter information table 27. FIG.

FIG. 12 is a flowchart illustrating an operation of the virtual file name management unit 3.

FIG. 13 is a flowchart for explaining an example of the operation of the lexical analysis unit 22.

FIG. 14 is a flowchart for explaining an example of the operation of the name syntax analysis unit 23.

FIG. 15 is a flowchart illustrating an example of an operation of the procedure selection unit 24.

[Explanation of symbols]

DESCRIPTION OF SYMBOLS 1 ... Communication part, 2 ... File name management part, 3 ... Virtual file name management part, 4 ... Procedure management part, 5 ... File reading / writing part, 6 ... Procedure application part, 11 ... File name resolution part, 12
... File resource management table, 13 ... Virtual file name resolution unit,
14 ... Virtual file resource management table, 15 ... Procedure search unit,
16 ... Procedure management table, 17 ... Virtual file name corresponding part, 1
8 ... Virtual file name correspondence table, 19 ... System status acquisition unit, 20, 21 ... Procedure selection unit, 22 ... Lexical analysis unit, 2
3 ... Name syntax analysis part, 24 ... Procedure selection part, 25 ... Procedure syntax management table, 26 ... Lexical type table, 27 ... Delimiter information table.

 ─────────────────────────────────────────────────── ─── Continuation of the front page (72) Inventor Keihisa Kawabe 2274 Hongo, Ebina City, Kanagawa Prefecture Fuji Xerox Co., Ltd.

Claims (6)

[Claims] 1. A file system in a network information system in which a plurality of computer systems for information processing are connected by a network, and in a file system, actual file resource position information and file resources indicating physical positions of file resources actually existing in the computer system. Virtual file name management including a virtual file resource management table that holds and manages one or more sets of procedure names that are the names of one or more procedures for processing Means, virtual file name resolving means for receiving the virtual file name and retrieving the real file resource position information and the procedure name determined from the virtual file name managing means in correspondence with the virtual file name, and the virtual file name resolving means. The real file corresponding to the virtual file name obtained by the means. A file system comprising procedure applying means for applying a procedure defined by the procedure name to an existing file resource defined by file resource location information. 2. In a file system in a network information system in which a plurality of computer systems that perform information processing are connected by a network, a real file name that is the name of a file resource that actually exists in the computer system and a physical file resource that exists. File resource management table having a file resource management table that holds and manages one or more sets of real file resource position information indicating the physical position, and a virtual file name that is the name of a virtual file resource as input A virtual file that holds and manages at least one file name conversion procedure name that is a name of a file name conversion procedure that outputs a set of a procedure name that is the name of one or more procedures for processing and a real file name or a virtual file name A conversion procedure management means having a name correspondence table and a given virtual file File name conversion procedure corresponding to one or more file name conversion procedure names of the conversion procedure management means for a virtual name, and recursively one or more file name conversions for a virtual file name obtained. Virtual file name resolving means for applying the procedure and outputting the real file resource position information of the file name management means and the procedure name obtained by applying the file name conversion procedure corresponding to the obtained real file name. And procedure applying means for applying a procedure defined by the procedure name to an existing file resource defined by the real file resource location information corresponding to the virtual file name obtained by the virtual file name resolution means. The file system to be. 3. A system status acquisition unit that acquires a parameter representing a system status, and a plurality of virtual file name resolution units corresponding to a virtual file name based on the parameters acquired by the system status acquisition unit. When a procedure name is obtained, the method further comprises procedure selecting means for selecting one or more procedure names from the plurality of procedure names.
The virtual file name resolving means outputs the real file resource position information and the one or more procedure names selected by the procedure selecting means, and the procedure applying means is obtained by the virtual file name resolving means. The procedure defined by the procedure name selected by the procedure selection unit and output from the virtual file name resolution unit is applied to the existing file resource defined by the real file resource location information corresponding to the virtual file name. The file system according to claim 1 or 2. 4. When a parameter for selecting a procedure is received and the virtual file name solving means obtains a plurality of procedure names corresponding to the virtual file name, one or a plurality of the procedure names is obtained based on the parameter. The virtual file name resolving means outputs the real file resource location information and the one or more procedure names selected by the procedure selecting means, The procedure applying means selects the virtual file name solving means selected by the procedure selecting means for an existing file resource determined by the real file resource position information corresponding to the virtual file name obtained by the virtual file name solving means. The file according to claim 1 or 2, wherein a procedure defined by a procedure name output from the file is applied. system. 5. A name parsing means for parsing an input name, a procedure management means having a procedure syntax management table for associating a predetermined token with one or more of the procedure names, and a syntax by the name parsing means. The virtual file name resolving means further comprises procedure selecting means for selecting one or more of the procedure names using the procedure managing means based on the token appearing in the syntax tree as a result of the analysis. The resource location information and the one or more procedure names selected by the procedure selecting means are output, and the procedure applying means is the real file corresponding to the virtual file name obtained by the virtual file name solving means. A procedure selected by the procedure selection means for an existing file resource determined by resource location information and output from the virtual file name resolution means The file system according to claim 1 or 2, wherein a procedure defined by a name is applied. 6. A virtual file resource for the virtual file name is constructed from one or more real file resource position information corresponding to the virtual file name obtained by the virtual file name solving means and one or more procedure names. To generate an expression composed of one or more of the actual file resource position information necessary to do so and one or more of the procedure names, and a procedure defined by the expression generated by the expression generating means. The file system according to any one of claims 1 to 5, further comprising procedure applying means for applying.