JPH1115682A - Multi-operating system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a multi-operating system which prevents the non-matching and the contradiction of data and improves operability. SOLUTION: In a multi-operating system in a client server system where a server computer 1 and a client computer 2 are connected by a network 3, the server computer 1 locks all the other objects on the locked object of the server computer 1 when the client computer 2 locks the object on the server computer 1.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

[0001] The present invention relates to a multi-operating system, and more particularly to a multi-operating system in a client-server system.

[0002]

2. Description of the Related Art As a data processing method in a conventional multi-operating system, transaction processing is used to speed up and simplify the data processing.

In transaction processing in a multi-operating system, when an object is to be manipulated, the operation is performed so that data rewriting or the like by another operator may occur during the operation and data inconsistency or inconsistency may not occur. Manipulating an object after locking it.

Therefore, in the conventional multi-operating system, while an operator is operating an object, the object is locked, and other operators cannot perform processing on the object. Such inconsistencies and inconsistencies can be prevented.

[0005]

However, in the conventional multi-operating system, an object directly operated by the operator can be locked. However, when the data of the object is related to the object and the data of the object is changed, the influence is changed. Since other objects cannot be locked, there is a problem that inconsistency or inconsistency occurs in data or the like.

For example, an object a where an operator A is located
When the object a is locked to operate and the content of the object a is changed, another object b related to the changed object a may be affected. At this time, since the object b is not locked, if the operator B operates the object b, inconsistency or inconsistency occurs in data or the like.

In the case of transaction processing in a conventional multi-operating system,
Only when you try to lock an object can you tell if it can be locked, so you cannot tell if an object is locked until you lock it. In other words, it is difficult to select an unlocked object efficiently because it is only when the user tries to lock the object to determine whether the object is already locked or unlocked. I have.

The present invention has been made in view of the above circumstances, and has as its object to provide a multi-operating system capable of preventing data inconsistency and inconsistency and improving operability thereof.

[0009]

According to the first aspect of the present invention,
In a multi-operating system in a client-server system in which a server computer and at least one client computer are connected, one of the one or more client computers locks an object on the server computer. Is performed, the server computer locks all other objects related to the object on the locked server computer.

More specifically, referring to the drawings,
The present invention relates to a related object search means (S18 in FIG. 2).
And a lock ending means (S12 in FIG. 2) for continuously locking the objects searched by the above (S11 in FIG. 2).

Therefore, according to the present invention, when the client computer operates on the object,
When the data of the object performing the operation is changed, in addition to the object performing the operation, all other objects affected by the change are regarded as objects related to the object performing the operation and locked. Therefore, during operation by the operator, data of another object is rewritten by another operator,
Data inconsistency and inconsistency can be prevented from occurring.

That is, when an object is locked, another object related to itself is locked. Therefore, even if it is an object other than the object to be operated directly, only the necessary object can be locked, so that even if a plurality of operators operate the object from different client computers, data inconsistency or data inconsistency may occur. It is possible to prevent inconsistency from occurring.

According to a second aspect of the present invention, in the first aspect of the present invention, the object on the server computer has a lock ID storage unit for storing a lock ID. Of 1
The lock ID stored in the lock ID storage means is transmitted to the client computer.

Therefore, according to the present invention, the function of the invention described in claim 1 can be obtained, and the lock ID stored in the lock ID storage means can serve as a key when locking or unlocking an object. Therefore, data can be prevented from being rewritten by another client computer, and furthermore, data inconsistency or inconsistency due to data rewriting of the object can be prevented.

According to a third aspect of the present invention, in the second aspect of the present invention, the object on the server computer has management data storage means for storing data of the object, and the object is stored in the one or more client computers. When the lock ID of the client computer and the lock ID stored in the lock ID storage unit match, the management data stored in the management data storage unit is rewritten.

Therefore, according to the present invention, the operation of the invention described in claim 2 is obtained, and when rewriting the data of the object, the lock ID of the client computer for rewriting the data and the lock ID stored in the lock ID storage means are stored. Since the data is rewritten only when the IDs are compared with each other and the comparison is identical, it is possible to avoid a situation where another client computer rewrites the data of the locked object.

According to a fourth aspect of the present invention, in the first aspect of the present invention, at least one or more client computers connected to the client-server system include all of the locked computers. It is characterized by displaying that the object is in a locked state.

More specifically, referring to the drawings,
The present invention provides a management data reading means (S15 in FIG. 2) for transmitting management data to a client computer;
It has management data acquisition means (S25 in FIG. 3) for constantly grasping the object data and the lock state.

Therefore, according to the present invention, the effect of the invention described in any one of the first to third aspects can be obtained, and it can be recognized that all the objects in the locked state are in the locked state. ,
Efficiency in selecting an object can be improved.

That is, the locked state of the object is reflected on the screens of all the client computers. Thereby, the operator can always grasp the locked state of the object.

According to a fifth aspect of the present invention, in the first aspect of the present invention, the client computer has input control means for controlling an input based on a locked state of the object. Features.

More specifically, with reference to the drawings,
The present invention has an input unit (S22 in FIG. 3) for restricting the input by the operator based on the management data.

Therefore, according to the present invention, the operation of the invention described in any one of claims 1 to 4 can be obtained, and the locked object is controlled by the client computer for data input and the like to the object. Therefore, occurrence of data inconsistency or inconsistency can be prevented, and the multi-operating system can be used more efficiently.

That is, the input to the client computer is restricted depending on the locked state of the object.
This reduces the need for the operator to perform useless operations such as inputting data to locked objects, and also reduces the amount of useless communication between the client and the server.

According to a sixth aspect of the present invention, in the invention of any one of the first to fifth aspects, the server computer is configured to release the lock for releasing the lock of the object that has been locked for a predetermined time. It is characterized by having means.

More specifically, referring to the drawings,
The present invention has a lock ending unit (S12 in FIG. 2) for ending the locked state.

Therefore, according to the present invention, the operation of the invention described in any one of the first to fifth aspects can be obtained, and after a predetermined time has elapsed, the locked object is unlocked. Therefore, the use efficiency of the multi-operating system can be further improved.

That is, in the server-side object, the lock is released after a predetermined time has elapsed. As a result, the client-side object does not release the server-side object while keeping it locked, and the server-side object releases the lock after a predetermined time elapses even if the server-side object stops or communication becomes impossible, so the locked server-side object is locked forever. A so-called deadlock that continues can be prevented.

According to a seventh aspect of the present invention, in the sixth aspect of the present invention, the lock release means has a timer for counting a predetermined time.

Therefore, according to the present invention, the effect of the invention described in claim 6 can be obtained, and a predetermined time is counted by the timer, and the object is unlocked based on the count result. Can effectively avoid deadlock.

[0031]

Next, an embodiment of a multi-operating system according to the present invention will be described with reference to the drawings.

FIG. 1 shows a configuration diagram of a first embodiment of a multi-operating system according to the present invention.

FIG. 1A is a configuration diagram showing a hardware environment. It includes a server computer 1, a client computer 2, and a network 3. There are a plurality of client computers 2 (three in this embodiment). The server computer 1, the client computer 2, and the network 3 constitute a client-server system, and each client computer 2
Can operate the server computer 1 from different operators, and thus a multi-operating system is configured. Of course, in the present invention, the number of server computers 1 and client computers 2 is
It is not limited to the above values.

As shown in FIG. 1A, in this client-server system, three client computers 2 are connected to a server computer 1 via a network 3, and each client computer 2 has a display or the like. Display device 21 composed of
And an input device 22 including a keyboard, a mouse, a pointing device, and the like.

FIG. 1B is a configuration diagram showing the configuration of an object. On the server computer 1, there are a plurality of objects to be managed (hereinafter, referred to as managed objects) S1. Further, on each client computer 2, there are a plurality of objects (hereinafter, referred to as display objects) S2 for displaying the state of the management object S1 and monitoring the input of the operator.

There are a plurality of management objects S1, each of which manages some data. The management object S1 is an object of C ++ language or the like.

There are a plurality of display objects S2, each of which serves as a user interface for a predetermined specific management object S1. The display object S2 and the management object S1 have a many-to-one correspondence.
The relationship is The display object S2 is an object in the C ++ language or the like.

Next, FIG. 2 shows a block diagram of the structure of the management object S1 shown in FIG.
1 shows a block diagram of the structure of the display object S2 shown in FIG.

First, the management object S shown in FIG.
A block diagram of the structure 1 will be described. As shown in FIG. 2, the management object S1 provided in the server computer 1 includes a lock start unit S11 for starting an object lock, a lock end unit S12 for ending the object lock, and a lock time update unit S13.
A management data changing unit S14, a management data reading unit S15, and a first lock I for storing a lock ID.
D storage unit S16, first timer S17, related object search means S18, and management data storage unit S19.

The lock start means S11 is provided with the first lock I
Data is exchanged with the D storage unit S16, data is given from the related object search means S18, and data is given to the first timer S17.

The lock ending means S12 includes a first lock I
Data is exchanged with the D storage unit S16, and data is given from the first timer S17 and the related object search unit S18.

The lock time update means S13 includes a first lock ID storage section S16 and a related object search means S1.
The data is supplied from 8 and the data is supplied to the first timer S17.

The management data changing means S14 receives data from the first lock ID storage unit S16 and supplies data to the management data storage unit S19.

The management data reading means S15 receives data from the management data storage unit S19.

The management data storage unit S19 gives data to the related object search means S18.

Next, the display object S shown in FIG.
The block diagram of the second configuration will be described below. As shown in FIG. 3, the display object S2 is a management data acquisition unit S25 to which data to be rewritten is input.
A lock start request unit S26, a lock end request unit S27, a lock time update request unit S28, a management data change request unit S29, a display unit S21, an input unit S22, a second timer S23, Lock ID of 2
And a storage unit S24.

As shown in FIG. 3, the management data acquisition means S25 gives data to the display means S21 and the input means S22.

The lock start requesting means S26 is
21, data is provided to the second timer S23 and the second lock ID storage unit S24, and data is received from the input means S22.

The lock end requesting means S27 includes a display means S
Data is supplied to the input unit 21 and data is received from the input unit S22, the second timer S23, and the second lock ID storage unit S24.

The lock time update requesting means S28 exchanges data with the second timer S23 and gives the data to the display means S21.

The management data change request unit S29 gives data to the display unit S21, and receives data from the input unit S22 and the second lock ID storage unit S24.

Here, each member provided in the management object S1 shown in FIG. 2 and each member provided in the display object S2 shown in FIG. 3 are connected by the network shown in FIG. Therefore, data can be exchanged between them.

Next, the operation of each member shown in FIGS. 2 and 3 will be described in detail below. First, the operation of the components of the management object S1 shown in FIG. 2 will be described.

The lock start means S11 locks the management object S1 in response to a request from the display object S2 provided in the client computer 2. This lock is performed by first receiving a lock start request notification or a lock start request notification and a lock ID from the lock start request unit S26 of the display object S2 or the lock start unit S11 of another management object S1.

At this time, if the lock ID has already been stored in the first lock ID storage unit S16, a request rejection is returned to the request transmitting side, and the operation ends. No lock ID is stored in the first lock ID storage unit S16, and the lock ID
If a lock ID has not been received, a new lock ID is generated. Thereafter, when the data of the target managed object S1 is changed by the related object search means S18, a list of the managed objects S1 (hereinafter, referred to as related objects) to be locked which are affected by the change. And sends a lock start request notification and a lock ID to the management object S1 that has become the related object, and waits for the result to be transmitted.

If the received result is a request rejection, the display object S2 is notified of the request rejection, and the operation ends.
If the received result is normal, the lock ID is stored in the first lock ID storage unit S16, the first timer S17 is started, the lock ID and the notification of normal end are transmitted to the display object S2, and the operation is ended. I do.

The lock ending means S12 unlocks the management object S1 in response to a request from the display object S2. This lock is released by first receiving a lock end request notification and a lock ID from the lock end request unit S27 of the display object S2 or the lock end unit S12 of another management object S1.

At this time, if the lock ID is not stored in the first lock ID storage section S16, an error is transmitted to the display object S2, and the process ends. If the lock ID is stored, the lock ID is compared with the received lock ID, and if the value is different, a request rejection notification is transmitted to the display object S2, and the processing ends. If the lock IDs match, a list of related objects is obtained from the related object search means S18, a lock end request notification and a lock ID are transmitted to those managed objects S1, and the result is awaited. If the received result is a request rejection or an error, an error is transmitted to the display object S2 and the process ends. If the received result is normal, the first timer S17 is stopped, the lock ID stored in the first lock ID storage unit S16 is deleted, a notification of normal end is transmitted to the display object S2, and the operation is performed. finish.

The lock time updating means S13 performs a process of continuing to lock the management object S1 in response to a request from the display object S2. Therefore, first, a lock time update request notification and a lock ID are received from the lock time update request means S28 of the display object S2 or the lock time update means S13 of another management object S1.

At this time, if the lock ID is not stored in the first lock ID storage unit S16, an error is transmitted to the display object S2, and the operation ends. If the lock ID is stored, the stored lock ID and
The received lock ID is compared with the received lock ID, and if the values are different, a request rejection notification is transmitted to the display object S2, and the operation ends. If the lock IDs match, a list of related objects is obtained from the related object search means S18, a lock time update notification and a lock ID are transmitted to those managed objects S1, and the system waits for a result to be transmitted. . If the result received is a request rejection or error,
An error is transmitted to the display object S2, and the process ends. If the received result is normal, the first timer S17 is restarted, a normal end notification is transmitted to the display object S2, and the operation ends.

The management data changing means S14 changes the management data stored in the management data storage unit S19 of the management object S1 in response to a request from the display object S2.

First, a management data change request, data to be changed, management data, and a lock ID are received from the management data change request means S29 provided in the display object S2. At this time, if the lock ID is not stored in the first lock ID storage unit S16, an error is transmitted to the display object S2, and the process ends. If the lock ID is stored, the stored lock ID is compared with the received lock ID, and if the values are different, a request rejection notification is transmitted to the display object S2, and the process ends. If the lock IDs match, the received data is stored in the management data storage unit S19.
And sends a notice of normal termination to the display object S2, and terminates the operation.

The management data reading means S15 reads the management data stored in the management data storage section S19 of the management object S1 in response to a request from the display object S2, and transmits the management data to the display object S2. First, a management data read request and a lock ID are received from the management data acquisition unit S25 of the display object S2. At this time, if the lock ID is not stored in the first lock ID storage unit S16, or if the received lock ID is different from the received lock ID even if the lock ID is stored, a request rejection notification is transmitted to the display object S2 and the processing ends. I do. If the lock IDs match, the management data stored in the management data storage unit S19 is transmitted to the display object S2 together with a normal end notification.

The first lock ID storage section S16 stores a lock ID. If the lock ID is stored,
The management object S1 is locked.

The first timer S17 counts a predetermined time, and when this predetermined time has elapsed, outputs a signal to that effect to the lock ending means S12 to cause the lock ending means S12 to perform the lock ending operation. .

The related object retrieving means S18 detects another management object S1 which has an effect when the management object S1 is changed from the management data storage unit S19 according to a predetermined rule.

The management data storage unit S19 stores data managed by the management object S1.

Next, the display object S shown in FIG.
2 will be described in detail below with reference to FIGS. 2 and 3.

The display means S21 displays the management data of the management object S1 obtained by the management data acquisition means S25 on the display device 21 of the client computer 2,
Displays lock status, errors, etc.

The input means S22 sends the data input from the input device 22 of the client computer 2 to the lock start request means S26, lock end request means S27 and management data change request means S29. Further, the lock state of the management object S1 is acquired from the management data acquisition means S25, and the input from the input device 22 is restricted. More specifically, when the management object S1 is locked to another display object S2, all inputs are ignored.

The operation of the second timer S23 is started by the lock start requesting means S26, and after a predetermined time has elapsed, a signal is output to the lock time updating requesting means S28, and the second timer S23 outputs the signal to the lock time updating requesting means S28. Start the time update operation.

The second lock ID storage section S24 stores the lock ID given by the lock start requesting means S26.

The management data acquisition means S25 repeatedly acquires the management data and the lock state of the management object S1, and outputs them to the display means S21. In this state, first, the lock ID is acquired from the second lock ID storage unit S24, and the acquired lock ID is transmitted to the management object S1 together with the management data read notification, and the process waits until the result is received. If the result is normal, the received management data and the lock state are sent to the display means S21 and the input means S22, and the operation ends.

The lock start requesting means S26 is
22 and outputs a lock start request notification to the management object S1 and waits for the result. If the result is normal, since the lock ID has been received, the lock ID is stored in the second lock ID storage unit S24, and the second timer S
After starting 23, the operation is terminated. If the result is not normal, a signal indicating an error is sent to the display means S21.

The lock end requesting means S27 is
22 and sent to the management object S1 the lock ID and the lock end request notification acquired from the second lock ID storage unit S24, and waits until the result is received. If the received result is normal, the lock ID stored in the second lock ID storage unit S24 is deleted, and the second timer S23
Stop the counting operation. If the result is not normal,
A signal indicating an error is sent to the display means S21.

The lock time update requesting means S28 is started by the second timer S23, and is operated by the management object S1.
To the lock I acquired from the second lock ID storage unit S24.
A lock update request notification is sent together with D, and the result is awaited. If the result is normal, the second timer S23 is restarted. If it is not normal, a signal indicating an error is sent to the display means S21.

The management data change request unit S29 transmits the data obtained from the input unit S22 and the lock ID obtained from the second lock ID storage unit S24 to the management object S1, and waits for the result. If the result is normal, the process ends. If the result is not normal, a signal indicating an error is sent to the display means S21.

Next, the operation of the present embodiment will be described with reference to FIGS.

First, an outline of the operation will be described, and then details will be described. An outline of the operation will be described with reference to FIGS. FIG. 4 is a flowchart showing an outline of the operation of the multi-operating system according to the present embodiment. There are basically three operations in the multi-operating system according to the present invention. The first is the operation of hierarchically locking the managed object, the second is the operation of always displaying the lock status on the screen, and the operation of restricting the input according to the lock status, and the third is the release of the lock when the managed object times out. Operation.

The display object S2 shown in FIG.
Before changing the management data of the corresponding management object S1, the management object S1 is locked. While locked, the management data of the management object S1 cannot be changed via another display object S2. The display object S2 releases the lock after changing the management data of the management object S1.

Further, the lock of the management object S1 has a hierarchical structure. The lock of the management object S1 having the hierarchical structure will be described with reference to FIG.

FIG. 4A is a flowchart showing an operation when locking an object having a hierarchical structure. According to this flowchart, first, step A
At 11, it is confirmed whether or not the management data is locked. If it is not locked (No), the operation ends.

If it is locked (Yes), the management data is locked in step A12, other related management data is locked (step A13), and the input data is set as the management data (step A14). The management data is unlocked (step A15), and the operation ends.

That is, for example, a certain display object S
It is assumed that the management object S1-A has been locked via the server 2. At this time, by changing the data of the management object S1-A by means defined in advance in the management object S1-A, other management objects S that are affected
1-B, and the management object S1-A locks it (steps A11, A12, A13, A
14, A15).

Display 2 of Client Computer 2
1 is a management data acquisition unit S2 for the display object S2.
The management data and the lock status of the management object S1 obtained by step 5 are displayed by the display means S21.

Next, the input control operation of the locked management object S1 will be described with reference to the flowchart shown in FIG.

According to the flowchart shown in FIG. 4B, in step A20, management data and locked data are acquired. Then, data is output (step A21), and it is confirmed whether or not the lock is being performed (step A22).
20 and if locked (Yes), the process proceeds to step A23 to limit the input (step A2).
3).

That is, the management data obtaining means S25 repeatedly requests the management data reading means S15 for the management data and the lock state. The management data reading means S15 acquires the management data from the management data storage unit S19, and
It is checked whether the lock ID is stored in the storage unit S16, and the management data and the lock state are stored in the management data acquisition unit S.
25. The management data acquisition unit S25 sends the management data and the lock state of the management object S1 to the display unit S21 and the input unit S22. In the display means S21,
The management data is displayed, and if the management object S1 having the management data is locked, the fact that the management object S1 is locked is displayed. The input means S22 ignores any input from the input device 22 in the locked state (when the other display object S2 locks the management object S1) (steps A20, A21, A22,
A23).

Next, the locked management object S1
However, the operation of releasing the lock after a predetermined time set by the timer will be described with reference to the flowchart shown in FIG.

According to FIG. 4C, in step A31, the timer of the first timer S17 is started. In step A32, it is confirmed whether or not a predetermined time has elapsed. (No), the apparatus enters the standby state, and when a predetermined time has elapsed (Ye
s), and unlock the management data (step A3)
3) Then, the operation ends.

That is, the first timer S17 of the management object S1 unlocks the lock by requesting the lock end requesting means S12 to end when a predetermined time has elapsed after the start (step A3).
1, A32, A33).

Next, the locking operation of the object will be described in detail. First, start of lock, then release of lock, and finally, release of lock by timer will be described.

The lock start operation will be described with reference to FIGS. 2, 3 and 5. FIG. 5 shows a flowchart of an operation when starting the locking of the management object S1.

According to the flowchart shown in FIG. 5A, a lock start input is accepted in step A201, a lock start request is transmitted in step A202, and a subroutine (FIG. 5) in step A203 is executed. The operation of the flowchart shown in b) is performed, and thereafter, in step A204, it is confirmed whether or not the processing has been completed normally.

If it is determined in step A204 that the operation is not normally completed (No), the operation is terminated. If the operation ends normally (Yes), in step A205, the second lock ID storage unit S24 stores the lock ID, starts the second timer S23, and ends the operation.

Here, the operation of the flowchart which is the subroutine shown in FIG. 5B in step A203 will be described.

Referring to FIG. 5B, first, in step A101, the lock start means S11 receives a request for lock start, and in step A102, it is determined whether or not this management object S1 is already in a locked state. Confirm, if already locked (Yes), step A
The process proceeds to step A104, and if not locked (No), the process proceeds to step A104.

In step A104, it is confirmed whether or not the lock ID is stored in the first lock ID storage unit S16, that is, whether or not the lock ID is received. If the lock ID is received (Yes) , Step A10
6 and if the lock ID has not been received (N
o) In step A105, a lock ID is generated, and the process proceeds to step A106.

In step A106, the related object search means S18 searches for the related object, and transmits a "lock request" and a lock ID to the searched related object (step A107).

Next, in step A108, the operation from step A101 to step A107 (operation X1) is executed for all the related objects, and then the process proceeds to step A109.

In step A109, it is confirmed whether or not the processing has been completed normally. If the processing has not been completed normally (No), the processing proceeds to step A103. If the processing has been completed normally (Yes), the processing proceeds to step A110. In step A103, a request rejection is transmitted to the display object S2, and the operation is thereafter terminated.

At step A110, the lock ID is set to the first
In the lock ID storage unit S16. afterwards,
The timer of the first timer S17 is started (step A111), a normal end signal and a lock ID are transmitted (step A112), and the operation ends.

The operations of the flowcharts shown in FIGS. 5A and 5B are further summarized below. When the lock start is input by the input means S22 of the display object S2, the lock start request means S26 transmits a lock start request to the lock start means S11 of the management object S1 (steps A201, A202, A).
203).

In the lock start means S11, the first lock I
If the lock ID is stored in the D storage unit S16, a request rejection is transmitted to the lock start request unit S26 (steps A101, A102, A103).

The lock I is stored in the first lock ID storage unit S16.
If D is not stored and the lock request includes the lock ID, the lock ID is used. If the lock request does not include the lock ID, a new lock ID is generated (steps A104 and A105).

Next, the related object search means S18 provided in the management object S1 stores the management data in the management data storage unit S1.
The data of the management object S1 (related object) to be locked, which is obtained from the management data of No. 9 is obtained. The lock start request and the lock ID are transmitted to the lock start means S11 of these management objects S1 (step A).
106, A107, A108).

When the related object is successfully locked (the lock ID is transmitted), the lock ID is stored in the first lock ID storage unit S16, a timer is started, and the lock ID is transmitted to the lock start requesting unit S26. (Steps A109, A110, A111, A11
2).

Step A108 is a lock start operation of another management object, and the same procedure as described above is performed.

Lastly, the lock start requesting means S26 provided in the display object S2 sets the lock ID to the second lock I
The data is stored in the D storage unit S24 and the second timer S23 is started (steps A205 and A206).

At this time, the other display objects S2 displaying the same management object S1 indicate that the management object S1 has been locked. For example, when the display object S2-a locks the management object S1-A in FIG. 1B, the other display objects display that the management object S1-A is locked by the display unit S21. This has been described in the display operation described above.

By the above operation, the object is locked.

Next, the unlocking operation will be described with reference to FIG. 2, FIG. 3, and FIG. FIG. 6 shows a flowchart of the operation when the object is unlocked.

According to FIG. 6A, first, step A
At 220, the lock end requesting unit S27 receives an input of lock end, and thereafter transmits a lock end request and a lock ID (step A221).

Next, in step A222, the operation (X2) shown in FIG. 6B, which is a subroutine, is performed, and thereafter, the flow shifts to step A223.

In step A223, it is confirmed whether or not the processing has been completed normally.
s) The process moves to step A225, and if not normally terminated (No), the process moves to step A224. In step A224, an error is displayed on the display means S21,
Then, the operation ends.

In step A225, the lock ID stored in the second lock ID storage unit S24 is deleted, the timer of the second timer S23 is stopped (step A226), and the operation is thereafter terminated.

Next, the operation of the subroutine shown in FIG. 6B will be described. First, in step A121, the management object S2 sets the lock end means S1
2 receives the lock end request and the lock ID.

Thereafter, in step A122, it is confirmed whether or not the lock state is established. If the lock state is not established (No), the process proceeds to step A128. If the locked state is established (Yes), the process proceeds to step A123. In step A123, it is confirmed whether or not the lock ID matches the lock ID stored in the first lock ID storage unit S16. If they match (Yes), the process proceeds to step A124, and If not (No), the process proceeds to step A129.

In step A124, a lock end request signal and a lock ID are transmitted to the related object.

Then, in step A125, the operation from step A121 to step A124 (X
2) is executed for all the managed objects, and the process proceeds to step A126.

In step A126, it is confirmed whether or not the processing has been completed normally. If the processing has been completed normally (Yes), the process proceeds to step A127.
o), proceed to step A128.

In step A127, a signal indicating normal termination is transmitted, and the operation is thereafter terminated. In step A128, an error signal is transmitted, and the operation is thereafter terminated. In step A129, a signal indicating request rejection is transmitted, and the operation is thereafter terminated.

The outline of the unlocking operation of the objects shown in FIGS. 6A and 6B will be further described below.

The lock end requesting means S is input from the input means S22.
When the input of the lock end is transmitted to the lock end unit 27, the lock end request unit S27 acquires the lock ID from the second lock ID storage unit S24 and transmits it to the lock end unit S12 (steps A220 and A221).

If the lock ID is not stored in the first lock ID storage section S16, the lock ending means S12 provided in the management object S1 returns an error because the locked state is not established (steps A122 and A12).
8).

Conversely, if the lock ID is stored in the first lock ID storage unit S16, the lock ID is compared with the received lock ID. If the lock ID is different, a request rejection message is displayed on the display object S2. (Steps A123 and A129).

If the lock IDs match, the lock end and the lock ID are transmitted to the management object S1 searched by the related object search means S18, and the result is waited for (steps A124 and A12).
5).

If the processing has been completed normally, a message indicating that the processing has been completed is returned to the display object. If the processing has not been completed normally, an error is returned (steps A126, A127, A1)
28).

When the response from the management object S1 is a normal end, the lock end requesting means S27 provided in the display object S2 deletes the lock ID stored in the second lock ID storage unit S24, and the second timer S23
To stop. If it is an error, the error is displayed on the screen from the display means S21 (steps A223 and A22).
4, A225, A226).

With the above operations, the object is unlocked.

Next, the operation of continuing the lock will be described with reference to FIG. 2, FIG. 3, and FIG. FIG. 7 shows a flowchart of the operation when the locked state of the object is continued.

Referring to FIG. 7A, first, in step A251, the timer of the second timer S23 is started. Then, in step A252, it waits for a predetermined time to elapse. After the predetermined time has elapsed, in step A253, the lock time update request unit S28 receives the lock time update request.

Then, in step A254, the operation (X3) of the flowchart shown in FIG. 7B, which is a subroutine, is performed, and thereafter, the flow shifts to step A255.

In step A255, it is confirmed whether or not the processing has been normally completed. If the processing has been normally completed (Yes),
The flow shifts to step A251, and if not ended normally (No), the flow shifts to step A256. Step A2
At 56, an error is displayed on the display means S21, the timer of the second timer S23 is stopped at step A257, and the operation is thereafter terminated.

Next, the operation (X3) shown in FIG. 7B as a subroutine in the operation of step A254 will be described.

First, in step A151, the lock time updating means S1 provided in the management object S1
3 receives the lock time update request. Then, in step A152, it is confirmed whether or not the lock state is established. If the lock state is not established (No), step A160
And if it is locked (Yes), step A
Move to 153.

At Step A153, the first lock ID
It is checked whether or not the lock ID matches the lock ID stored in the storage unit S16. If the lock ID matches (Yes), the process proceeds to step A154, and if not (No), the process proceeds to step A159. .

At Step A154, the first timer S
17 is restarted, and then, in step A155, a lock time update request and a lock ID are transmitted to the related object, and the process proceeds to step A156.

In step A156, the above-described step A
The operations from 151 to step A155 are executed for all the managed objects, and thereafter, step A157
Move to

In step A157, it is confirmed whether or not the processing has been completed normally. If the processing has been normally completed (Yes), the process proceeds to step A158, and if not normally completed (No).
The process moves to step A160.

At step A158, a normal end is transmitted, and the operation is thereafter terminated. In step A159, request rejection is transmitted, and the operation is thereafter terminated. Step A160
Then, an error is transmitted, and then the operation ends.

Next, with reference to a flowchart shown in FIG. 7C, the automatic unlocking operation after a predetermined time has elapsed will be described.

First, in step A161, it is confirmed that a predetermined time has elapsed (timeout).

Then, in step A162, a lock release request and a lock ID are transmitted to the related object.

Then, in step A163, FIG.
The operation X2 shown in (b) is executed for all the managed objects, and then the operation ends.

Next, FIG. 7A and FIG. 7B
The operation shown in FIG. 7C will be described in more detail below.

The second timer S23 started by the lock start requesting means S26 starts the lock time update requesting means S28 every time a predetermined time elapses. The lock time update requesting unit S28 acquires the lock ID from the second lock ID storage unit S24 and transmits the lock ID to the lock time update unit S13 (steps A251, A252, A2).
53).

On the management object S1 side, if the lock ID is not stored in the first lock ID storage unit S16, the lock time updating means S13 returns an error to the display object (steps A151, A152, A16).
0).

Next, if the received lock ID is not the same as the lock ID stored in the first lock ID storage unit S16 of the management object, a request rejection notification is returned to the display object (steps A153 and A159).

Next, the second timer S17 is restarted (step A154).

Next, a lock time update request notification and a lock ID are transmitted to the management object S1 searched by the related object search means S18, and the result is awaited. In step A156, similar processing is executed in another management object (step A155, A
156).

If the reply is normal, a message to the effect that the processing has been normally completed is transmitted to the display object S2. If there is an error, the error is transmitted to the display object S2 (steps A158 and A160).

At this point, the process returns to the display object S2. If the received result is normal, the timer is started again and the elapse of time is waited. When the error is received, the error is displayed on the screen by the display means S21 (steps A255, A256, A257).

The automatic unlocking operation will be described in more detail with reference to FIGS. 2 and 7C. If communication becomes impossible due to a failure of the client computer 2 or the network 3 while a certain display object S2 locks the management object S1, the management object S1 automatically locks after a predetermined time has elapsed. Perform the operation.

In this automatic lock release operation, the lock ending means S12 is started when the first timer S17 has elapsed for a predetermined time (steps A161, A162, and A162).
A163). Therefore, according to this operation, the lock of the object for which the predetermined time has elapsed is automatically released.

Next, with reference to FIG. 3 and FIG. 8, an operation of restricting an input to a locked object will be described. FIG. 8 is a flowchart showing an operation of restricting an input to a locked object.

Referring to FIG. 8, first, at step A26
At 1, it is checked whether the object is locked. If it is locked (Yes), the process proceeds to step A262, and if it is not locked (N
o), and proceed to step A263.

In step A262, it is checked whether or not the object is locked by itself. If the object is locked by itself (Yes), the process proceeds to step A263. If the object is not locked by itself (No), the operation is started. Finish.

In step A263, the input data is transmitted to another member, and the operation is terminated.

The operation of the flowchart shown in FIG.
This will be described in more detail below. When there is an input to the input means S22, data indicating whether or not the management object S1 is locked is received from the management data acquisition means S25. S26, the lock end request means S27 and the management data change request means S29 are sent.

If locked, the second lock ID
If the lock ID is stored in the storage unit S24, it means that it is locked by itself, so the input is accepted and sent to the lock start request unit S26, the lock end request unit S27, and the management data change request unit S29. The lock ID is locked and stored in the second lock ID storage unit S24.
Is not stored, it means that the other display object S2 has locked the management object S1, and the input is ignored.

Next, the operation of changing the management data will be described with reference to FIGS. 2, 3 and 9. FIG. 9 is a flowchart showing the operation when the management data is changed.

First, as shown in FIG. 9A, in step A271, management data is input, and a data change request notification is sent to the management data change request means S2.
9, the second lock ID storage unit S24 receives the lock ID
Is received, and the management data acquisition unit S25 receives the data (step A272).

In step A274, the operation (X) of the flowchart as a subroutine shown in FIG.
4) is performed, and then the flow shifts to step A274.

At step A274, it is confirmed whether or not the operation is completed normally. If the operation is completed normally (Yes), the operation is terminated. If the operation is not completed normally (No), the process proceeds to step A275. Display,
Finish the operation.

Next, the operation (X4) of the flowchart shown in FIG. 9B will be described. First, in step A171, a data change request notification and a lock ID
And data.

Then, in step A172, it is confirmed whether or not the lock IDs match. Lock ID
If they match (Yes), the process moves to step A173, and if they do not match (No), the process moves to step A175.

At step A173, the data is updated. Then, after updating the data, in step A174, a normal end is notified, and the operation ends. In step A175, the request is rejected, and the operation ends.

Next, FIG. 9A and FIG. 9B
Will be described in more detail below. First, from the input means S22 to the management data change request means S
29 is transmitted. Management data change request means S
In 29, the lock ID is stored in the second lock ID storage unit S24.
Is acquired and transmitted to the display object S2 together with the management data change request notification (steps A271, A272, A
273).

In the management object S1, the management data changing means S14 compares the value of the lock ID obtained from the first lock ID storage unit S16 with the received lock ID,
If the lock ID values are the same, the received data is stored in the management data storage unit S19, and a normal end is returned to the display object S2. If the lock ID values are not the same, a request rejection is returned to the display object S2 (steps A171, A172, A173, A174, A17).
5).

Thereafter, the flow shifts to step A274 to confirm whether or not the processing is normally completed. If the processing is normal, nothing is performed, and if not, the fact is displayed (steps A274 and A2).
75).

Next, a first embodiment of the multi-operating system according to the present invention will be described in detail with reference to FIGS. 2, 3 and 10. FIG. 10 shows a configuration diagram of an embodiment of the multi-operating system according to the present invention.

As shown in FIG. 10, this embodiment of the multi-operating system includes one server computer 1, a client computer 2-1 and a client computer 2-2.

The server computer 1 has two management objects S1-1 and S1-2, and the client computer 2-1 has one display object S2-1. The client computer 2-2 has a display object S2-
1 ′ and a display object S2-2.

Now, consider a case where an operator changes the management data of the management object S1-1 from the client computer 2-1. First, the display object S2-1 locks the management object S1-1.
Since the management object S1-1 has not been locked yet, it generates a lock ID. If the value of the lock ID is
As shown in FIG. 10, it is assumed that the number is 0123567.

Further, the related object search means S11 searches the managed object S1-1 for another managed object. If the management object S1-2 is detected as a related management object, the management object S1-1 replaces the management object S1-2 with the management object S1-2.
Lock is performed using a lock ID whose value is 0123567. Similarly, the management object S1-2 may lock another management object. Finally, the management object S1-1 transmits the lock ID to the display object S2-1.

The display objects S2-1 and S2-1 'displaying the management object S1-1 are informed that the management object S1-1 has been locked by the management data acquisition means S25, and are displayed on the screen by the display means S21. Show that you are locked.

Next, when the operator inputs data, the display object S2-1 has the lock ID 0123456.
7 and the input data are transmitted to the management object S1-1. Since the lock IDs of the management objects S1-1 are equal, the management data is changed.

When the input by the operator is completed, the lock is released.
0123567 and the lock end request are transmitted to the management object S1-1. The management object S1-1 is
The lock end means S12 deletes the lock ID stored in the first lock ID storage unit S16, stops the first timer S17, and transmits a lock end request to the management object S1-2.

The display objects S2-1 and S2-1 'displaying the management object S1-1 are displayed on the screen by the management data acquisition means S25 by the display means S21 indicating that the lock of the management object S1-1 has been completed. I do.

As described above, according to this embodiment, when the management object S1 on the server computer 1 is locked from a plurality of client computers 2, the management object S1 is related to the locked management object S1. All managed objects that are affected by the rewriting of related data are set as related objects, and by locking this related object, data inconsistency or inconsistency occurs when another operator operates the related object. Can be prevented.

In the management object S1 on the server computer 1, the first lock ID storage unit S16
Stores the lock ID, and stores the lock ID in the client computer 2.
However, since the lock ID stored in the first lock ID storage unit S16 is transmitted to the client computer 2, the management of the lock ID can be completely performed. It is possible to prevent the data of the object S1 from being rewritten.

The management object S1 on the server computer 1 has a management data storage unit S19 for storing data of the management object S1, and stores the lock ID of the client computer 2 and the first lock ID storage unit S16. Only when the stored lock ID matches, the management data stored in the management data storage unit S19 is rewritten. Therefore, the locked object is rewritten by another client computer, and the data is rewritten. The occurrence of inconsistency or inconsistency can be reliably prevented.

Further, all the locked management objects S1 are displayed on the screen of the client computer 2 so that the locked object can be recognized. Therefore, the operator can determine which object is locked. Can be easily grasped.

In addition, since the data input to the locked object is restricted, the occurrence of inconsistency or inconsistency in the data on the management object can be further prevented.

Further, when a certain time has elapsed since the object was locked, the lock is automatically released, so that deadlock of the object can be reliably prevented.

Further, in order to confirm whether or not a fixed time has elapsed since the management object S1 was locked,
Since the first timer S17 is used, it is possible to effectively avoid a so-called deadlock in which the object remains locked.

[0188]

As is clear from the above description, according to the present invention, each managed object has data of another managed object related to itself, and the managed object locks the other managed object. When a certain managed object is locked, all the other affected managed objects are locked, so that a plurality of operators can operate the managed objects having different but influential relations to inconsistent data. A multi-operating system capable of preventing inconsistency can be provided.

The object on the server computer has lock ID storage means for storing the lock ID, and is stored in the lock ID storage means in one of the one or more client computers. Since the lock ID is transmitted, the lock ID can be completely confirmed. With this lock ID,
A multi-operating system capable of completely identifying a client computer can be provided.

The object on the server computer has management data storage means for storing data of the object, and stores the lock ID of one of the one or more client computers in the lock ID storage means. When the locked ID matches, the management data stored in the management data storage means is rewritten. Therefore, when the object is locked, the data of the object is rewritten by another client computer when the object is locked. A multi-operating system capable of more completely preventing inconsistency and inconsistency can be provided.

Further, since the lock state of the management object is displayed on all client computers, it is possible to determine whether or not the operator can operate the management object before operating the management object. Can be provided.

Further, since input is not accepted depending on the lock state of the management object, it is possible to prevent the operator from operating the management object already locked by another operator, to prevent erroneous operation, and to improve operability. A multi-operating system that can be further improved can be provided.

Further, when a predetermined time has elapsed while the management object is locked, the lock is automatically released, so that a failure occurs in a client computer, a network, or the like with the management object locked. Also, it is possible to provide a multi-operating system capable of preventing a deadlock state from occurring.

Further, a multi-operating system is provided in which a timer is provided for counting a certain time when an object is automatically unlocked, so that the object can be unlocked more efficiently. can do.

[Brief description of the drawings]

FIG. 1 is a configuration diagram of an embodiment of a client-server system to which a multi-operating system according to the present invention is applied.

FIG. 2 is a block diagram showing one embodiment of a structure of a management object according to the present invention.

FIG. 3 is a block diagram illustrating an embodiment of a structure of a display object according to the present invention.

FIG. 4 is a flowchart showing an outline of the operation of the multi-operating system according to the present invention.

FIG. 5 is a flowchart illustrating an object lock start operation of the multi-operating system according to the present invention.

FIG. 6 is a flowchart illustrating an object unlock operation of the multi-operating system according to the present invention.

FIG. 7 is a flowchart showing a lock continuation operation of an object of the multi-operating system according to the present invention.

FIG. 8 is a flowchart showing an input control operation of the multi-operating system according to the present invention.

FIG. 9 is a flowchart showing a management data changing operation of the multi-operating system according to the present invention.

FIG. 10 is a block diagram showing a configuration of a first embodiment of a multi-operating system according to the present invention.

[Explanation of symbols]

 1 server computer 2 client computer 3 network 21 display device 22 input device S1 management object S2 display object S11 lock start means S12 lock end means S13 lock time updating means S14 management data changing means S15 management data reading means S16 first lock ID storage Unit S17 First timer S18 Related object search unit S19 Management data storage unit S21 Display unit S22 Input unit S23 Second timer S24 Second lock ID storage unit S25 Management data acquisition unit S26 Lock start request unit S27 Lock end request unit S28 Lock time update request means S29 Management data change request means

Claims (7)

[Claims] 1. A multi-operating system in a client-server system in which a server computer and at least one or more client computers are connected, wherein one of the one or more client computers is located on the server computer. A multi-operating system, wherein when a lock is applied to an object, the server computer locks all other objects related to the object on the locked server computer. 2. An object on the server computer has a lock ID storage unit for storing a lock ID, and is stored in one of the one or more client computers in the lock ID storage unit. The transmitted lock ID is transmitted.
Multi-operating system as described. 3. An object on the server computer has management data storage means for storing data of the object, wherein a lock ID of one of the one or more client computers and the lock ID are provided.
When the lock ID stored in the storage means matches,
3. The multi-operating system according to claim 2, wherein the management data stored in said management data storage means is rewritten. 4. The apparatus according to claim 1, wherein at least one or more client computers connected to the client-server system display that all the locked objects are in a locked state. 3. The multi-operating system according to any one of 3. 5. The multi-operating system according to claim 1, wherein said client computer has input control means for controlling an input based on a locked state of said object. 6. The multi-function device according to claim 1, wherein said server computer has an unlocking means for unlocking an object which has been locked for a predetermined period of time. operating system. 7. The multi-operating system according to claim 6, wherein said unlocking means has a timer for counting a predetermined time.