JPH1185597A - Lock control method for plural hierarchized objects - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a method for lock control for locking only all objects in the parantal relation with a certain object when there is a lock request to that object in the lock control of plural hierarchized objects. SOLUTION: When lock is requested from a client 1 to one object A-1 in an information processing system environment with which plural hierarchized objects A, B and C can be controlled and that object A-1 is not under lock, a lock file A is generated while including the name of that object A-1, its hierarchical position in hierarchical structure and the name of object A-2 on the high-order hierarchy in the parental relation with that object A-1. With this lock file A, that object A-1, all the objects A-2 on the high-order hierarchy in the parent relation with that object A-1 and all objects A-a and A-b on a low-order hierarchy in the parental relation with that object A-1 are locked.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

[0001] 1. Field of the Invention [0002] The present invention relates to a lock (exclusive access) control method for a plurality of hierarchical objects in an information processing system environment.

[0002]

2. Description of the Related Art A conventional lock control method for a plurality of hierarchical objects in an information processing system environment includes:
During processing by a first access exclusion request (a lock request: hereinafter referred to as a first lock request) including a change in the content of one object, a second access including a change in the content of the object Exclusion request (hereinafter, the second
When there is a lock request (described as a lock request), a lock (exclusive) control in which the second lock request is rejected during the processing by the first lock request is known.

[0003] The contents of the lock include a lock control for locking the entire plurality of hierarchical objects by a first lock request and exclusion of lock requests after the second lock request, or an access control. There is known a control in which only one object for which an exclusion request has been made is locked by a first lock request, and exclusion control of lock requests after the second lock request is performed.

[0004] In the former case of the exclusive control for locking the whole of a plurality of hierarchized objects, until the processing of one object by the first lock request is completed, the object is not in a parent-child relationship after the second lock request. Since the object cannot be processed, the user has to wait until the processing of the first lock request ends.

On the other hand, in the latter case of exclusive control for locking only an object for which a lock request has been made, even if the object is not being processed by the first lock request, objects other than the object being processed are processed after the second lock request. Was possible, but during the processing of one object by the first lock request, the first
If another object having a parent-child relationship with the object being processed is processed by the lock request, inconsistencies may occur in the parent-child contents of the objects.

Note that the parent-child relationship in the specification of the present invention means that the object has a relationship of a parent, grandparent, great-grandparent, child, grandchild, great-grandchild, and the like. For example, in the case of a parent object, the parent, grandparent,
This means all objects belonging to a hierarchy higher than the hierarchy to which the object belongs, such as a great-grandparent.

In the case of a child object, the child, grandchild,
This means all objects belonging to a hierarchy lower than the hierarchy to which the object belongs, such as a great-grandchild. Therefore, in the specification of the present invention, the expressions of parent-child relationship, parent object, child object, etc. all indicate the above-described parent-child relationship, parent object, child object in a broad sense.

[0008]

Conventionally, for a certain object among a plurality of hierarchical objects,
Since there is no way to indicate the hierarchical position of the object in the hierarchy or any other object that is in a parent-child relationship with the object, during the change of the object, the object in the parent-child relationship with the object is determined. Even if an attempt is made to lock only the object and the object having a parent-child relationship with the object, there has been no method for determining the object having the parent-child relationship with the object.

[0009] Therefore, since an effective and simple control technique for locking an object including a lock request object and an object having a parent-child relationship with the object has not been established, an arbitrary one of a plurality of hierarchically arranged objects has not been established. If there is a lock request for an object, lock the entire hierarchical object at the expense of object data use efficiency, or take the risk that the parent-child relationship between objects may be lost. There was no alternative but to lock only the object that requested the lock.

[0010] In a client / server environment, an effective and simple control technique for locking only an object for which a lock request is made and an object having a parent-child relationship with the object has not been established.

However, in an information processing system environment in which a plurality of hierarchical objects are managed, in order to effectively use stored object data and increase the use efficiency, the first lock request described above is required. It has been desired to realize lock control in which only an object and an object having a parent-child relationship with the object can be exclusively used (accessible) only to the process that has issued the first lock request.

[0012] The present invention provides an information processing system environment in which a plurality of hierarchical objects can be controlled, when a first lock request for one object is issued,
An object of the present invention is to realize lock control for performing exclusive access control on only the object and all objects having a parent-child relationship with the object.

[0013]

According to the present invention, a lock request is issued to one object in an information processing system environment capable of storing and controlling a plurality of layered objects and processing using the objects. When the lock request has been made, the object that has made the lock request, all child objects of the object in all layers lower than the layer to which the object belongs, and the objects in all layers higher than the layer to which the object belongs Is locked only for all parent objects.

The control of the lock is realized by, for example, a method described below. First, when a lock request is made for one object that has not been locked (hereinafter referred to as a first object), the hierarchical position to which the first object belongs in the entire hierarchical structure, A lock file having a name including the first object and names of all parent objects of the first object is generated.

Then, when a lock request is issued to one of the child objects of the first object, the parent objects of the child object are sequentially traced back from the lower hierarchy to obtain the lock file. Since a parent object having a name that matches the name of the first object in the name is found, it is determined that the child object is locked.

When a lock request is issued to the first object itself, the first object is locked because the name of the first object exists in the name of the lock file. It is determined that there is.

Further, when there is a lock request for one of the parent objects of the first object, the name of the parent object is included in the name of the lock file. Is determined to be locked.

Further, in a client / server environment, a plurality of hierarchically managed objects are collectively managed by a server, and in response to a lock request from the client to the plurality of objects, a lock file corresponding to the lock request is created. Lock control and lock determination by generation are also performed collectively by the server.

In a client / server environment, when a certain client issues a lock request for a plurality of objects or a lock information acquisition request for a plurality of objects, the request from the client to the server is collectively transmitted by a packet or the like. It is done.

[0020]

DESCRIPTION OF THE PREFERRED EMBODIMENTS Embodiments of the present invention will be described below in detail with reference to the drawings. FIG. 1 is a diagram illustrating a lock control method for a plurality of hierarchical objects in a client / server environment which is one form of an information processing system environment.

In a hierarchical object, if the parent object is different, a plurality of object names having the same name may exist in one hierarchy. Therefore, an object of a certain hierarchy has, as information, the name of the parent-child relationship of the object up to the first (top) parent object in which no object of the same name exists. For example, the parent object name of the highest hierarchy is “ABC”, the child object name of “ABC” of the second hierarchy is “PQR”, and the “PQR” of the third hierarchy is “PQR”.
Assuming that the child object name of “QR” is “XYZ”, the object “XYZ” includes “ABC / PQR / XYZ”
Object name information indicating a parent-child relationship.

In the information processing system, before the lock request for an object and the exclusive processing of the access are completed, the next lock request for the object or an object having a parent-child relationship with the object may occur in various ways. However, for convenience of explanation, a plurality of clients 1-4 as shown in FIG. 1 locks to an arbitrary object in a plurality of layered objects A, B, and C in the server 5. Consider the case where there is a request.

The network 6 includes clients 1-4
And the server 5 are connected to form a local area network (LAN). Each of the clients 1 to 4 and the like includes at least an input device such as a keyboard (not shown) and an output device such as a display and a printer, and can transmit the contents requested by the user from the input device to the server 5 via the network 6. ing.

The server 5 can store a plurality of hierarchical objects (hierarchical multiple objects) A, B, C, and the like, and a lock request due to an access including a change to any one of the hierarchical multiple objects is issued. If the object is not locked, a lock file indicating that the object and an object having a parent-child relationship with the object are locked can be generated and stored.

Consider a case where there is a lock request 7-1 due to an access including a content change to the object A- (1) at the position (1) in the hierarchical multiple objects A.
The objects to be excluded by the lock request 7-1 include the child objects (a) and (b) of the object A- (1) included in the lower layer of the object A- (1) including the object A- (1) itself. ,
And parent object A- of the upper layer of object A- (1)
(2).
It is necessary to exclude a lock request by an access including a change from 4 or the like.

In order to realize the exclusion of the lock request by such access, generation of a lock file having the following name and lock determination are used. Hereinafter, the object having the name D is referred to as “object D”.

Now, assuming that a lock request for the object A- (1) is generated and a lock request is generated for the parent object or the child object of the object A- (1) as described above, the following lock file name (A Generate the lock file indicated by).

However, here, unlike FIG. 1, the depth of the hierarchical structure of the hierarchical structure of the hierarchical multiple objects A including the object A- (1) is "m", and the object A- (1 ) Is the relative depth of the hierarchy from the parent object of the highest hierarchy to the object A- (1).

(A) = “P (n) .P (m−1)... .P (2) .P (1) .A- (1)... Lock file name to be locked A- (1): Name of object for which lock request is made P (i): Includes object A- (1) as a child object and is higher than object A- (1) by i layers Name of the parent object of the hierarchy In the lock file name (A) generated above, the number of periods “.” Included in the file name is “m”, the same number as the depth of the hierarchy of the hierarchy, and the name A- The number of periods “.” After (1) is calculated from the total number of layers “m” in the hierarchical structure to the number of layers relative to the top level object P (n) of the object A- (1). “mn” minus “mn”.

The determination as to whether or not the object A- (1) is locked is made by the following names (A)-(1) to (A)-(n
If the lock file of +1) exists, it is determined that the lock is locked, and if not, it is determined that the lock is not locked.

(A)-(1): "P (n) ..... P (2) .P (1) .A- (1). *. * ..... *." (A)-(2 ): "P (n) ..... P (2) .P (1) ............" (A)-(3): "P (n) ..... P (2) ... ..… .. ”:: (A)-(n + 1):“ P (n) .......… .. ”where“ * ”in (A)-(1) is This is an expression that means an arbitrary character string including an empty character. Therefore, (A)-(1) means that all child objects of object A- (1) have names "*".
The object A- (1) and the object A- (1)
Indicates that all child objects are locked.

The lock file names (A)-(2) to (A)-(n + 1) are the names of the lock files of the respective parent objects of the object A- (1). In the lock file names (A)-(1) to (A)-(n + 1), the number of periods “.” Included in the file name is all “m”. (A)-(1) is the name of the lock file of the object A- (1) or all its child objects, and (A)-(2) to (A)-(n + 1) are the objects A- ( This is the name of the lock file of each parent object in 1).

The name (A) of the lock file may be recorded as a record of the lock file of the object A- (1). In this case, the name of the lock file may be determined by a predetermined method.

In FIG. 1, when a lock request 7-1 is made to the object A- (1) in the server 5 from the client 1 via the network 6, and the object A- (1) is not locked, Is the object A- (1), its child objects A- (a) and A- (b), and the object A- (b).
In order to lock the parent object A- (2) of (1), a lock file having the lock file name (A) is generated and stored. (In this case, a lock file named “A- (2), A- (1)...) Is generated.” Here, during the processing of the lock request 7-1, that is, the lock file name (A) Object 2 in the server 5 from the client 2 while being locked by the lock file of
(C) has a lock request 7-2, the object A-
It is determined whether or not the lock is being performed based on whether or not a lock file including the name of (c) or the name of the parent object of the object A- (c) exists (if it exists,
It is determined that it is locked).

In a situation where the objects A- (2), A- (a), and A- (b) are locked by the lock file having the lock file name (A), the client 2
When lock request 7-2 comes to A- (c), the lock file name
If only the lock file of (A) exists, it is determined that the object A- (c) is not locked. And
A lock file named "A- (2), A- (1), A- (c)" is generated.

Next, the object B-
When the lock request 7-3 is issued to (1), if the object B- (1) is not locked, the object B-
(1), parent objects B- (3) and B- of object B- (1)
"B- (3) .B- (2) .B-" indicates that (2) is locked.
(1). Is generated and stored. Here, during the change access processing by the lock request 7-3, that is, while being locked by the lock file with the lock file name (B), the change from another client to any one of the hierarchical multiple objects B is performed. Is determined, it is determined whether or not the lock is being performed based on the existence of the lock file having the lock file name (B).

When the client 3 issues a lock request 7-4 to the object C- (1), if the object C- (1) is not locked, the lock file name "C- (1) ..." The lock file of (C) is generated and stored.

During the change access processing by the lock request 7-4, that is, while being locked by the lock file having the lock file name (C), any one of the objects in the hierarchical plurality of objects C is received from another client. Lock file name if the file was accessed with changes
Whether or not the lock file is locked is determined based on the existence of the lock file of (C).

The hierarchical plural objects A in FIG.
FIG. 2 is a diagram showing each object in B and C and its lock file name in more detail. In FIG. 2, the parent object names of the highest hierarchy of each of the hierarchized plural objects A, B, and C are EDBID1, EDBI, respectively.
D2 and EDBID3 (EDBID: Engineering Data-BaseID) are indicated by the names, and the names of the objects in the lower layers are indicated by the names of the documents 1 and 2, respectively. The names of the objects in the lowest layer are the sheets 1 and 2. , Sheet 3.

The depth “m” of the hierarchical structure is “3”.
Therefore, simply setting the names of the lock files such as sheet 1 and sheet 2 or document 1 and document 2 makes it possible to include a plurality of object sheets 1 and 2 in one layered multiple object. Since the object documents 1 and 2 exist in the generalized plural objects A, B, and C, respectively, it is not possible to specify which object is to be pointed. Therefore, the name of the lock file is the name of the parent object of the highest hierarchy. The name that goes back to is described.

Note that, in the following description, for example, a child object A-
When expressing (1), "A- (2) / A-
(1) ”. Clients 1-4
Sends a lock request or a lock information acquisition request to the server 5 by using the notation method.

First, in the case of the hierarchized plural objects A, the object document 2 of the second layer is the lock request 7-
Since it is the object of 1, a lock request is generated for the object of “EDBID1 / document 2”.

As a result, whether or not the object of “EDBID1 / document 2” is locked is checked by a check method described later. if,
If the search result is not locked, a lock file with the lock file name “EDBID1. Document 2 ..” is generated by the above-described method, and “EDBID1”, “EDBID1 / Document2”, “EDBID1 / Document2 /” The objects of “sheet 1” and “EDBID1 / document 2 / sheet 2” are locked.

By creating the lock file “EDBID1.document2 ..”, four objects (“EDBID1”, “EDBID1 / document2”, “EDBID1 / document2 / sheet”) surrounded by the dotted line a "1" and "EDBID1 / document2 / sheet2") are locked, and it becomes possible to determine that these objects are locked in a lock state determination method described later.

Next, in the case of the hierarchized plural objects B, the lowermost object sheet 2 is the lock request 7-3.
Therefore, a lock request is generated for the object of “EDBID2 / document 1 / sheet 2”.

As a result, whether or not the object of “EDBID2 / document 1 / sheet 2” is locked is checked by a check method described later. If the search result is not locked, lock file name "EDBID2. Document 1.
Create a lock file named "Sheet 2." and click "EDBI
D2 "," EDBID2 / document 1 "and" EDBID2 / document 1 / sheet "
2) Lock the object.

By creating a lock file in this manner, three objects surrounded by a dotted line b
("EDBID2", "EDBID2 / Document 1" and "EDBID2 / Document 1"
/ Sheet 2 ") is locked, and it becomes possible to determine that these objects are locked in a lock state determination method described later.

Further, in the case of the hierarchical multiple objects C, the object EDBID3 of the highest hierarchy is
Since it is the target of 7-4, a lock request is generated for the object of "EDBID3".

As a result, whether or not the object of “EDBID3” is locked is checked by a checking method described later. If the investigation result is not locked, a lock file with the lock file name "EDBID3 ..." is generated by the above-described method, and "EDBID3", "EDBID3 / document 1", "EDBID3 / document 2" The objects “EDBID3 / document 1 / sheet 1”, “EDBID3 / document 1 / sheet 2”, and “EDBID3 / document 2 / sheet 1” are locked.

By creating a lock file in this manner, six objects (“EDBID3”, “EDBID3 / document 1”, “EDBID3 / document 1”), which are all objects of the hierarchical multiple objects C surrounded by the dotted line c, “Document 2”, “EDBID3 / Document 1 / Sheet 1”, “EDBID3 / Document 1 / Sheet 2” and “EDBID3 / Document 2 / Sheet 1”) are locked. It can be determined that the object is locked.

Next, a method of checking whether an object is locked or not will be described. In the case of the hierarchical multi-object A, the object surrounded by the dotted line a is the client 1
Is locked by lock request 7-1.
Here, from another client 2 or the like, the object of “EDBID1 /
It is assumed that there is a lock request or a request for investigating whether or not a lock has been made (a lock information acquisition request).

First, it is checked whether or not a lock file of “EDBID1 / document 2” itself or a child object having the name “EDBID1.document 2. *.” Exists. Next, it is checked whether or not there is a lock file of the parent object of “EDBID1 / document 2” with the name of “EDBID1 ...”.

In the above investigation, if no lock file exists, it is determined that the lock is not being performed. In addition, if even one lock file exists in the above investigation, it is determined that the lock is being performed.

In the case of the hierarchical multi-object B, a dotted line
In the case where the object enclosed by b is locked by the lock request 7-3 from the client 2, the “EDBID1 /
Whether there is a lock request for "Document 2 / Sheet 2"
It is assumed that there is a lock information acquisition request.

In this case, a lock determination is made for "EDBID1 / document2 / sheet2". First, "EDBID1. Document 2. Sheet 2."
It is checked whether a lock file of “BID2 / document 1 / sheet 2” itself exists.

Next, “EDBID2. Document 1 ..” or “EDBID2.
It is checked whether a lock file of the parent object of “EDBID2 / document 1 / sheet 2” with the name “BID2 ...” exists. In the above investigation, if no lock file exists, it is determined that the file is not locked. Also,
If there is at least one lock file in the investigation, it is determined that the file is locked.

In the case of the hierarchical multiple object C, a dotted line
In the case where the object enclosed by c is locked by the lock request 7-4 from the client 3, "EDBID3" of the hierarchical multiple objects C from other clients 1 and 2 etc.
It is assumed that there is a lock request or a lock information acquisition request indicating whether a lock request has been issued.

In this case, lock determination is performed for "EDBID3". Check whether a lock file named "EDBID3. *. *." Exists. If no lock file exists in the above investigation, it is determined that the file is not locked. If there is even one lock file in the above investigation, it is determined that the file is locked.

However, in the above, "*" represents an arbitrary character string including a null character. FIG. 3 is a flowchart of the lock control operation in the server 5. Step S1
Then, the server 5 accepts the name of an object (hereinafter, referred to as a target object) for which a lock request has been made from one of the clients via the network 6.

In step S2, it is checked whether or not the received target object exists in the server 5.
In step S3, it is determined whether or not the target object exists in the server 5 based on the result of the investigation in step S2.
If the target object does not exist, the process proceeds to step S7.

In step S4, a lock determination is made based on the name of the received target object and the names of all lock files that are presently present by the method for determining whether or not the lock file exists as described with reference to FIG. Do
Investigate whether the target object is locked. As a result of the investigation, if locked, the process proceeds to step S7, and if not locked, the process proceeds to step S5.

In step S5, the result of the examination in step S4 reveals that there is no object already locked among the objects to be subjected to the lock control processing by the current lock request. Generates a lock file for performing lock control.

In step S6, the target object lock control process described with reference to FIG. 2 is performed in response to the current lock request. In step S7, the client that has requested this lock request is notified via the network 6 whether or not the lock on the target object has succeeded.

FIG. 4 shows that the lock request received in step S1 of FIG. 3 includes a plurality of objects, and the third layer has a first layer and a second layer having the same parent object name among the three layers. It is a flowchart at the time of seeing from the client side the lock control of the server 5 when making a batch lock request for a plurality of eyes.

When a lock request for a plurality of objects is issued at once, in order to guarantee that all objects are locked, if one object cannot be locked, all locks are canceled.
Mode and lock only lockable objects po
Prepare ssible mode.

In step S11, four objects (“EDBID5 / document 1 / sheet 1”, “EDBID5 / document 1 / sheet 2”),
A batch lock request is issued for "EDBID5 / Document1 / Sheet3" and "EDBID5 / Document1 / Sheet5" and the server 5
Now, in response to the batch lock request, steps S1 to S1 in FIG.
Step S5 is performed.

Step S12 is the same as steps S1 to S
Since all the target objects are not locked in the process of No. 5, lock files are generated for all the target objects, and all the target objects are successfully locked.

Step S14 indicates that the processing for the collective lock request has been completed in response to the result of successful locking of all target objects in step S12. In step S13, the locked object ("EDBID5 / document 1"
/ Sheet 3 "), there is no lock file for that object, and the lock fails for that object alone. In this case, the lock mode set by the user to select whether to cancel the change processing of the object without locking all the objects or to lock only the lockable object and change the object only. Perform according to. In the case of step S13, the process proceeds to step S15 or S16 according to the lock mode instruction issued together with the batch lock request from the client.

Step S15 is a process in the case where the user selects the possible mode. The objects locked this time (“EDBID5 / document 1 / sheet 3”) except for the object (“EDBID5 / document 1 / sheet 3”) for which the lock failed. Sheet 1 ”,“ EDBID5 / Document 1 / Sheet 2 ”, and“ EDBID5 / Document 1 / Sheet 5 ”) have been locked.

Step S16 is processing when the user selects the all mode, and the target objects ("EDBID5 / document1 / sheet1", "EDBID5
/ Document 1 / Sheet 2 "," EDBID5 / Document 1 / Sheet 5
)), That is, the lock file of the target object once created is deleted, and the current batch lock process is canceled.

As described above, from FIG. 4, in order to guarantee that all target objects are locked, if at least one target object cannot be locked, all target objects are not locked. Mode and poss to lock only lockable target objects
By providing ible mode for clients,
It is also possible to cope with a case where a batch lock request for a plurality of objects occurs.

FIG. 5 is a configuration diagram of a system in which one central server 5 centrally controls lock management (generation / deletion of the lock file, acquisition of lock information) in a client / server environment. A lock information acquisition request 10 from the client 1 and a lock request 11 from the client 3 are sent to the central server 5, and these requests 1
0 and 11 are collectively processed by the central server 5 by the lock control method of the present embodiment, and a lock file is generated on the central server 5 (in the case of the lock request 11). Therefore, lock management of a plurality of hierarchical objects can be centrally performed in a client / server environment without causing inconsistency in the relationship between the objects in a parent-child relationship.

For example, assume that the client 1 wants to update the object A with an editor or the like. In that case, first, a lock information acquisition request 10 is sent to the central server 5 so as to acquire lock information on the object.

Upon receiving this lock information acquisition request 10, the central server 5 determines whether or not the object A is locked. As a determination method, the existence of the lock file of the object A and the object having the parent-child relationship is checked. Then, the determination result is returned to the client 1.

In the client 1, if the returned judgment result indicates that the object A is locked, it means that the object A can be accessed only in the reading mode. Conversely, if the determination result indicates that the object A is not locked, it means that the object A can be accessed not only in the read mode but also in the update mode.

When accessing the object A from the client 1 in the update mode, in order to prevent the object A from being updated by another access during the update,
Object A needs to be locked. To do so, it is necessary to send a lock request to the central server 5.

In the central server 5, upon receiving the lock request,
A lock file for object A is generated on the master server 5. After the lock file of object A is created, client 1 can freely update object A.

After the update processing of the object A by the client 1 is completed, when it is no longer necessary to continue the lock, the client 1 transmits a lock release request for the object A to the central server 5. Upon receiving the lock release request, the central server 5 deletes the lock file of the object A.

In the procedure described above, first, the client 1 sends a lock information acquisition request 10 of the object A to the general server 5, and the client 1 receives the judgment result of the general server 5, and If the lock request has not been sent, the lock request is sent. However, the step of sending the first lock information acquisition request 10 and receiving the determination result is omitted, and the lock request 11 from the client 3 in FIG. , It is also possible to send the lock request 11 first.

The reason why the lock request can be transmitted first is that, upon receiving the lock request 11, the central server 5 determines whether or not the object requested to be locked is locked each time. This is because, based on the result of the determination, it is determined whether or not to lock an object for which a lock request has been made, and information on the success or failure of the lock on the object is returned to the client side.

FIG. 6 shows a case where a batch lock request for a plurality of objects is issued on the side of the clients 1 to 4 etc. to reduce the traffic load on the network. The case of sending with information 9 is shown.

In the case of FIG. 6, one packet information 9 includes a lock request command 9-0 indicating that the packet information is information of a lock request to the server 5.
And lock mode information 9- in which the lock mode selected by the user in the possible mode or the all mode is set.
1 and delimiters 9-2, 9-4, 9-6, 9-8, 9-
9 and object name information 9-3, 9-5, and 9-7 for each layer between the sections delimited by these delimiters.

A plurality of target objects (“ED
BID / Document ID / Sheet 1 "," EDBID / Document ID / Sheet 2 "
,..., “EDBID / document ID / sheet n”), the first layer and the second layer in the packet information 9 are shared and “lock mode: $ n: EDBID: $ n: document ID : ￥ n: sheet 1, sheet 2,..., Sheet n: ￥ n: ￥ n: ”.

For example, if only one first object “EDBID5 / document 1 / sheet 1” (hierarchical structure has three layers and the object of the third layer) in the batch lock request in FIG. Mode: ￥ n: EDBID5: ￥ n
: Document 1: $ n: Sheet 1 ". Also, for the sheets 2, 3, and 5 of the other objects, packets must be created individually and the packets must be sequentially transmitted to the central server 5. When the four objects for which the batch lock request has been made in step S11 of FIG. 4 are sent collectively, since "EDBID5 / document 1" is common, "lock mode: $ n: EDBID5: $" n: document 1: {n: sheet 1, sheet 2, sheet 3, sheet 5 ", and only one packet needs to be transmitted to the central server 5, so that the traffic load on the network 6 can be reduced.

The sent packet information 9 is transmitted to the
"EDBID / Document ID / Sheet 1", "EDBID / Document ID / Sheet 2" ... "EDBID / Document ID /
When a lock file is generated by performing a lock control process on each object after converting the data into a sheet n, the format indicating the object is further converted into a format indicating the name of the lock file of the object, and the name is changed. Will generate a lock file.

As described above, each client sends the information of a plurality of objects for which a lock request has been made to the server 5 in a lump using the packet information 9, thereby reducing the traffic load on the network 6. Becomes

FIG. 7 shows an information processing system environment.
FIG. 1 is a configuration diagram of an embodiment in which a program for implementing a method of controlling lock of a plurality of hierarchical objects according to the present embodiment is stored in a storage medium.

The information processing device 21 corresponds to the server 5 in FIGS. 1 and 5, and is a device capable of performing information processing such as a mainframe, a workstation, or a personal computer, and executes the lock control processing of the present embodiment. Storage device 24 capable of storing a program (data) 26 that can be stored therein, and a display 2 as an output device capable of outputting storage contents, processing results, and the like.
3. Medium drive device 2 for driving general storage medium 31
5. An input device, a processing device, and the like (not shown) are provided.

The program (data) provider 41 is connected to the information processing apparatus 21 via a line 51, and transfers a program (data) 42 stored in the program (data) provider 41 via the line 51. Information processing device 21
Program (data) 26
Can be stored as

The portable storage medium 31 is, for example, a CD-ROM 32 storing a program (data) 34 or a floppy disk 3 storing a program (data) 35.
As shown in FIG. 3, a program and data to be processed by the information processing device 21 are stored therein. The programs and data are inserted into the medium driving device 25 of the information processing device 21 and the programs (data) 34 and 35 are read by the medium driving device 25. As a result, the program (data) is stored in the storage device 24 in the information processing device 21.
26 can be stored.

Therefore, even if the program (data) 42 is initially transmitted from the program (data) provider 41, the program (data) 34 of the CD-ROM 32 or the program (data) of the floppy disk 33 is stored in the general storage medium 31. Even if the program (data) is stored as the program (data) 35, the program (data) 26 is ultimately implemented as the program (data) 26 stored in the storage device 24 of the information processing apparatus 21. The same handling is possible without being limited by the above.

[0092]

According to the present invention, in a plurality of hierarchical objects, only an object for which a lock request is made and an object having a parent-child relationship with the object are locked. , An access request to an object that is not in a parent-child relationship with the object can be made, so that exclusive control of effective access (lock management) without lowering the access efficiency to the object becomes possible.

Further, since only the necessary parent objects and child objects are locked, when a new lock request is issued to an object having a parent-child relationship with the object being processed by the lock request, the relationship between the two objects is generated. , It is possible to perform rational and simple lock control (exclusive control) without causing contradiction.

Also, when there is an object for which either the parent or child object has already been locked among the objects for which the collective lock request has been issued, the lock of all the objects for which the lock request has been issued is obtained. Can be canceled or only an object that has not yet been locked can be selected, so that flexible lock control can be performed.

Further, in the client / server environment, the server integrally controls the lock of a plurality of hierarchical objects, thereby simplifying the lock control in the client / server environment, and the The inconsistency due to the change of the data is eliminated, and furthermore, the transmission load on the network can be reduced by collectively receiving the lock requests of the plurality of objects from the client as a packet.

[Brief description of the drawings]

FIG. 1 is a diagram illustrating an overall configuration of a client / server system according to an embodiment of the present invention.

FIG. 2 is a diagram illustrating a lock control method for a plurality of hierarchical objects according to the embodiment.

FIG. 3 is a flowchart illustrating lock control processing of a server.

FIG. 4 is a flowchart illustrating lock processing in all mode and possible mode when a batch lock request for a plurality of objects is made.

FIG. 5 is a diagram showing a method for centrally managing lock information by a server in a client / server system.

FIG. 6 is a diagram showing an example of a format of packet information for requesting a server to perform a collective lock.

FIG. 7 is a diagram illustrating a configuration when a program according to an embodiment of the present invention stored in a storage medium is executed.

[Explanation of symbols]

 1-4 Client 5 Server 6 Network 7-1 to 7-4 Lock request 9 Packet information 10 Lock information acquisition request 11 Lock request A, B, C Hierarchical multiple objects (A), (B), (C) Lock file Name

Claims (13)

[Claims] In an information processing system environment capable of storing and controlling a plurality of hierarchical objects and processing using those objects, when a lock request is issued to one object, the lock request is issued. The object, all child objects of the object in all layers below the layer to which the object belongs, and all parent objects of the object in all layers above the layer to which the object belongs. A lock control method for a plurality of hierarchical objects. 2. The object for which the lock request has been issued, first information indicating at least a hierarchical position in the hierarchical structure of the plurality of hierarchized objects, and a name of the object. And a second for the names of all parent objects of the object
By creating and deleting a lock file with the information of
The method according to claim 1, wherein the lock control is performed. 3. The hierarchical file system according to claim 2, wherein the lock file further includes third information indicating the number of layers in the hierarchical structure of the hierarchical objects. Object lock control method. 4. The lock control according to claim 3, wherein the first, second and third information are set in a name or a record of the lock file. Method. 5. The name or record of the lock file is such that the name of the object for which the lock is requested and the names of all parent objects of the object are specified by a specific symbol from the object of the highest hierarchy to the top of the hierarchy. Behind the specific symbol following the name of the lock-requested object, the number of all the hierarchies in which the specific symbol is lower than the hierarchy to which the lock-requested object belongs is arranged. Wherein the first information is indicated by the order of appearance of the specific symbol in the character string following the name of the object for which the lock request has been made, and the second information Is indicated by each object name in the character string, and the last object name arranged in the character string is the lock It represents the name of there was the object,
The other object names in the character string represent the names of all the parent objects, and the third information is indicated by the total number of the specific symbols in the character string. A lock control method for a plurality of hierarchically described objects. 6. When a new lock request is issued, a search is made as to whether or not the lock file indicating that the object is locked exists based on the name of the object for which the lock request has been issued. 6. The lock control method for a plurality of hierarchical objects according to claim 2, wherein it is determined whether or not the object for which the new lock request has been made is already locked. . 7. In an information processing system environment capable of storing and controlling a plurality of hierarchical objects and processing using those objects, when a collective lock request is issued for a plurality of objects, said lock request is For each individual object, all child objects of the object at all levels below the level to which the object belongs,
Attempts to lock only all the parent objects of each object in all the hierarchies higher than the hierarchy to which each of the objects belongs. A lock control method for a plurality of hierarchical objects, wherein the lock is not performed. 8. In an information processing system environment capable of storing and controlling a plurality of hierarchical objects and processing using those objects, when a collective lock request is issued for a plurality of objects, the lock request is issued. For each individual object, all child objects of the object at all levels below the level to which the object belongs,
Attempts to lock only all parent objects of each object in all layers higher than the layer to which each object belongs, excludes already locked objects, and locks only lockable objects. A lock control method for a plurality of layered objects. 9. When a lock request is made for a plurality of objects in a lump, one of the lock control method according to claim 7 and the lock control method according to claim 8 is designated at the time of the lock request. A lock control method for a plurality of hierarchical objects. 10. The server according to claim 1, wherein the lock control of the plurality of hierarchized objects in response to the lock request is integrally performed by a server in a client / server environment. A lock control method for a plurality of layered objects described in one. 11. When a request for locking a plurality of objects or a request for determining whether or not a plurality of objects can be locked is issued on the client side,
11. The lock control method for a plurality of hierarchical objects according to claim 10, wherein the requests are collectively requested to the server. 12. When a lock request is issued to one object in an information processing system environment capable of storing and controlling a plurality of hierarchical objects and processing using those objects, the object is locked. A first information indicating at which hierarchical position in the hierarchical structure of the plurality of hierarchical objects the object belongs; and a name of the object and a name of the object. Second for all parent object names
By creating and deleting a lock file with the information of
A lock file generation / deletion unit for performing control for applying the lock; and when a new lock request is generated, the lock file generation / deletion unit indicates that the object is locked based on the name of the object that has issued the lock request. Determining means for determining whether or not the object for which the new lock request has been made is already locked by searching for whether or not a lock file exists; A plurality of hierarchical objects, comprising: a lock file generating / deleting means for generating a lock file corresponding to the requested object when the requested object can be locked; Lock control device. 13. When a lock request is issued for one object in an information processing system environment capable of storing and controlling a plurality of hierarchical objects and processing using the objects, at least the object First information indicating which hierarchical position in the hierarchical structure of the plurality of hierarchized objects belongs, and second information relating to the names of the objects and the names of all parent objects of the objects.
A computer-readable recording medium that records a program for causing a computer to execute a procedure for generating a lock file having the information of: and a procedure for performing an exclusive process of another lock request using the lock file.