JPH06301567A - Non stop type information processor - Google Patents

Abstract

PURPOSE:To constitute the processor so that the operation can be continued without a discrepancy on a receiving side of an asynchronous even if a fault is generated in a data transfer means position in the middle, and the processing can be executed at a high speed. CONSTITUTION:A data processing processor 2 imparts a count value corresponding to a lock instruction in an ID count table 2b to an asynchronous report for showing a fact that a lock instruction from a data processing processor 1 can be registered in a lock control table 2a and issues it. When its asynchronous report is received, the data processing processor 1 compares a count value corresponding to its lock instruction ID with a count value at every lock instruction ID in an ID count receiving table 1b. When those count values coincide with each other, the data processing processor 1 disregards the asynchronous report, and receives only a first asynchronous report.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a non-stop type information processing apparatus, and more particularly to speeding up asynchronous reporting for a specific instruction.

[0002]

2. Description of the Related Art Conventionally, in a non-stop type information processing apparatus, a retry is performed by an alternative path in preparation for a failure that occurs during asynchronous reporting. At this time, the sender's response to the asynchronous report is expected so that no contradiction occurs on the receiver of the asynchronous report.

For example, in the case where the non-stop type information processing apparatus has a configuration as shown in FIG. 28, data as shown in FIG. 29 is exchanged between the data processors 12 and 7. Figure 2
9 (a) shows a lock instruction 17 output from the data processor 12, and the lock instruction 17 includes a lock instruction code 17a and its lock instruction ID (identification information) 17
b and are included.

FIG. 29 (b) shows an asynchronous report 18 output from the data processor 7. The asynchronous report 18 includes an asynchronous report 18a and a lock instruction ID 18b of a lock instruction corresponding to the asynchronous report 18a. FIG. 29C shows the normal end report 1 output from the data processor 7.
29, and FIG. 29D shows the abnormal end report 20 output from the data processor 7.

30 to 32 are flowcharts showing the processing operation of the data processor 12 of FIG. 28, and FIGS. 33 and 34 are flowcharts showing the processing operation of the data processor 7 of FIG. The processing operation of the conventional non-stop information processing apparatus will be described with reference to FIGS. 28 to 34.

The data processor 12 uses the lock instruction 1
7 is issued, the lock instruction I of the lock instruction 17 is issued.
D17b is registered in the lock command ID table 12a (lock ID registration processing) (step 181 in FIG. 30).

Thereafter, the data processor 12 issues the lock instruction 17 to one of the data transfer control processors 3 and 4 (lock instruction issue processing) (step 182 in FIG. 30). When the data transfer control processors 3 and 4 receive the lock instruction 17 from the data processor 12, the lock instruction 17 is transferred to the data processor 7.

When the data processor 7 receives the lock command 17 via the data transfer control processors 3 and 4,
It is determined whether the lock command 17 can be registered in the lock control table 7a (lock control table registration determination process).
(FIG. 33, step 211).

The data processor 7 uses the lock instruction 1
When it is determined that 7 can be registered in the lock control table 7a, the lock command 17 is registered in the lock control table 7a (lock control table registration process) (step 212 in FIG. 33). After that, the data processor 7 issues the normal termination report 19 to one of the data transfer control processors 3 and 4 (normal termination report issuance processing) (step 213 in FIG. 33). When the data transfer control processors 3 and 4 receive the normal termination report 19 from the data processor 7,
The normal end report 19 is transferred to the data processor 12.

When the data processor 12 receives the end report via the data transfer control processing devices 3 and 4, it judges whether the end report is the normal end report 19 (normal end report judgment processing) (step in FIG. 31). 191).

When the data processor 12 determines that the end report is the normal end report 19, the normal end report 1
The lock command ID 17b of the lock command 17 corresponding to 9 is deleted from the lock command ID table 12a (lock ID
(Table deletion process) (step 192 in FIG. 31), the lock instruction ID is released.

On the other hand, when the data processor 7 determines that the lock instruction 17 cannot be registered in the lock control table 7a, the lock instruction ID 17 of the lock instruction 17 is determined.
b is registered in a hold table (not shown) (asynchronous report lock ID registration processing) (step 214 in FIG. 33).

After that, the data processor 7 issues the abnormal termination report 20 to one of the data transfer control processors 3 and 4 (abnormal termination report issuance processing) (step 215 in FIG. 33). When the data transfer control processors 3 and 4 receive the abnormal end report 20 from the data processor 7,
The abnormal end report 20 is transferred to the data processor 12.

When the data processor 12 receives the end report via the data transfer control processors 3 and 4, the data processor 12 determines whether or not the end report is the normal end report 19 (normal end report judgment processing) (step in FIG. 31). 191). When the data processor 12 determines that the end report is the abnormal end report 20, the data processor 12 enters a state of waiting for an asynchronous report.

After that, when the data processing processor 7 can register the lock instruction 17 in the lock control table 7a, the data processing processor 7 registers the lock instruction 17 in the lock control table 7a (lock control table registration processing). (FIG. 34, step 221). Subsequently, the data processor 7 issues an asynchronous report 18 to the data transfer control processing devices 3 and 4 (asynchronous report issuing process) (FIG. 3).
4 step 222).

At this time, the data processor 7 judges whether or not there is an abnormality in the data transfer control processors 3 and 4 (transmission abnormality judgment processing) (step 223 in FIG. 34). The lock command ID 17b of the corresponding lock command 17 is deleted from the pending table (asynchronous report lock ID deletion processing) (step 22 in FIG. 34).
4). This completes the process of issuing the asynchronous report 18 in the data processor 7.

Upon receiving the asynchronous report 18 from the data processor 7, the data transfer control processors 3 and 4 transfer the asynchronous report 18 to the data processor 12.
When the data processor 12 receives the asynchronous report 18 via the data transfer control processors 3 and 4, it reads the contents of the lock control table 7a of the data processor 7 (lock control table read process) (step 201 in FIG. 32). ).

The data processor 12 uses the lock instruction 1
7 is a lock control table 7a of the data processor 7.
The lock command ID 17b of the lock command 17 is deleted from the lock command ID table 12a (lock ID table deletion process) (step 202 in FIG. 32), and the lock command ID 17b is released.

When a failure occurs in the data transfer control processor 3 while the asynchronous report 18 is being transferred by the data transfer control processor 3, the data processor 7 sets a path in the data transfer control processor 4. (Asynchronous report alternative path setting process) (step 225 in FIG. 34), the asynchronous report 18 is transferred via the data transfer control processing device 4.

The data transfer control processor 4 transfers the asynchronous report 18 to the data processor 12. Even if the asynchronous reports 18 are overlapped and reported by this retry, the data processor 12 does not lock the lock control table 7
Since the contents of a are confirmed, no contradiction occurs in the data processor 12.

The flow charts shown in FIGS. 30 to 34 are subroutines that operate when the data processor 12 or 7 issues a lock command, or when a lock command, an end report, or an asynchronous report is received and an interrupt occurs. And the return in each process indicates the return to the process that was operating when the interrupt occurred.

[0022]

In the above-mentioned conventional non-stop type information processing apparatus, it is necessary to wait for a response from the transmitting side to the asynchronous report in order to prevent a contradiction on the receiving side of the asynchronous report. There is a problem that you can not do.

Therefore, the object of the present invention is to solve the above-mentioned problems, and even if a failure occurs in the intermediate data transfer means, the asynchronous report receiving side can continue the operation without contradiction, and high-speed processing is performed. An object of the present invention is to provide a non-stop type information processing device that can perform such operations.

[0024]

A first non-stop information processing apparatus according to the present invention is a first non-stop information processing apparatus, wherein a first data processing processor and a first data processing processor are connected to each other. And a second data transfer control processing device, the lock command is output when a lock command is issued from the first data processing processor to the second data processing processor to instruct access inhibition to the target device. When an asynchronous report indicating that it has been registered in the lock control table is output from the second data processor to the first data processor, the first and second
A non-stop information processing device that continues data transfer between the first and second data processing processors by using the other one of the data transfer control processing devices even if a failure occurs, It is provided with a determining means for determining whether or not the two are for the same lock command.

A second non-stop information processing apparatus according to the present invention comprises first and second data processing processors and the first data processor.
And a first and second data transfer control processing device for connecting between the second data processing processor, and instructing from the first data processing processor to the second data processing processor to inhibit access to the target device. If the asynchronous report indicating that the lock instruction is registered in the lock control table is output from the second data processor to the first data processor when the lock instruction to And a non-stop information processing device for continuing data transfer between the first and second data processing processors by using the other one of the second data transfer control processing device even if a failure occurs, A determination means for determining whether or not the lock command for which the asynchronous report is currently held is held pending during the previous investigation; Means and a means for performing reception processing of asynchronous reporting, the contents of the lock control table reads for lock instruction it is determined that the asynchronous reporting has been a pending during the previous survey.

A third non-stop type information processing apparatus according to the present invention includes first and second data processing processors and the first data processing processor.
And a first and second data transfer control processing device for connecting between the second data processing processor, and instructing from the first data processing processor to the second data processing processor to inhibit access to the target device. If the asynchronous report indicating that the lock instruction is registered in the lock control table is output from the second data processor to the first data processor when the lock instruction to And a non-stop information processing device for continuing data transfer between the first and second data processing processors by using the other one of the second data transfer control processing device even if a failure occurs, The lock command is sent to the first data processor in response to an abnormal termination report from the second data processor in response to the lock instruction. Monitoring means for monitoring the reception of the asynchronous report for a predetermined time, and when the monitoring means detects the non-reception of the asynchronous report at the predetermined time, the contents of the lock control table are read to determine that the asynchronous report has not been received. And means for receiving the asynchronous report for the lock instruction.

A fourth non-stop type information processing apparatus according to the present invention includes first and second data processing processors, and the first
And a first and second data transfer control processing device for connecting between the second data processing processor, and instructing from the first data processing processor to the second data processing processor to inhibit access to the target device. If the asynchronous report indicating that the lock instruction is registered in the lock control table is output from the second data processor to the first data processor when the lock instruction to And a non-stop information processing device for continuing data transfer between the first and second data processing processors by using the other one of the second data transfer control processing device even if a failure occurs, A determination means for determining whether the current number of times the lock command is issued is the same as the number of times of the previous investigation, and the determination means is the same as the number of times of the previous investigation. And a reception processing of asynchronous reporting, and means for executing the content of the lock control table reads for lock instruction was.

A fifth non-stop type information processing apparatus according to the present invention comprises first and second data processing processors and the first data processing processor.
And a first and second data transfer control processing device for connecting between the second data processing processor, and instructing from the first data processing processor to the second data processing processor to inhibit access to the target device. If the asynchronous report indicating that the lock instruction is registered in the lock control table is output from the second data processor to the first data processor when the lock instruction to And a non-stop information processing device for continuing data transfer between the first and second data processing processors by using the other one of the second data transfer control processing device even if a failure occurs, A judgment means for judging whether or not the current number of receptions of the lock command is the same as the number of receptions at the previous investigation, and the judgment means is the same as the number of receptions at the previous investigation. Means for adding request information for requesting confirmation of the contents of the lock control table to an asynchronous report to the lock command, and outputting the contents of the lock control table when the asynchronous report with the request information is received. And means for receiving and receiving an asynchronous report for the lock command corresponding to the request information.

A sixth non-stop information processing apparatus according to the present invention comprises first and second data processing processors, and the first data processing processor.
And a first and second data transfer control processing device for connecting between the second data processing processor, and instructing from the first data processing processor to the second data processing processor to inhibit access to the target device. If the asynchronous report indicating that the lock instruction is registered in the lock control table is output from the second data processor to the first data processor when the lock instruction to And a non-stop information processing device for continuing data transfer between the first and second data processing processors by using the other one of the second data transfer control processing device even if a failure occurs, Monitoring means for monitoring the time since the asynchronous report was sent to the second data processor; and the monitoring means sends the asynchronous report. And a means for adding request information for requesting confirmation of the contents of the lock control table to the asynchronous report when detecting that a predetermined time has elapsed from then, and outputting the asynchronous report to the first data processor. The data processor of the above comprises means for reading the contents of the lock control table when an asynchronous report to which the request information is added is received, and performing a process of receiving an asynchronous report for a lock command corresponding to the request information. There is.

[0030]

DESCRIPTION OF THE PREFERRED EMBODIMENTS Next, the present invention will be described with reference to the drawings.

FIG. 1 is a block diagram showing the configuration of the first embodiment of the present invention. In the figure, the data processors 1 and 2 are connected to each other via data transfer control processors 3 and 4. Note that FIG. 1 shows a case where the data processing processor 2 issues a termination report or an asynchronous report in response to a lock instruction from the data processing processor 1.

The data processor 1 registers the lock instruction ID of the lock instruction with the lock instruction ID table 1a.
And an ID count reception table 1b for storing the count value of the lock command ID corresponding to the asynchronous report given to the asynchronous report of the data processor 2.

The data processor 2 has a lock control table 2a for registering a lock command from the data processor 1 and an ID counting table 2b for counting and storing the number of lock commands for each lock command ID. There is.

FIG. 2 is a diagram showing an asynchronous report output from the data processor 2 of FIG. In the figure, an asynchronous report 5 is an asynchronous report 5a and a lock instruction ID 5b.
And an ID counter 5c.

FIG. 3 is a flowchart showing the processing operation of the data processor 2 of FIG. 1, and FIG. 4 is a flowchart showing the processing operation of the data processor 1 of FIG. The operation of the first embodiment of the present invention will be described with reference to FIGS.

The lock command issuing process and the end report receiving process by the data processor 1 are shown in FIGS. 30 and 31.
34. The lock registration & asynchronous report issuing process by the data processor 2 is the same as the process of the conventional example shown in FIG.

When issuing a lock instruction, the data processor 1 registers the lock instruction ID of the lock instruction in the lock instruction ID table 1a and issues the lock instruction to one of the data transfer control processors 3 and 4. To do. The data transfer control processors 3 and 4 are data processors 1.
When the lock command is received from, the lock command is transferred to the data processor 2.

When the data processor 2 receives the lock command via the data transfer control processors 3 and 4, the number of lock commands is counted for each lock command ID and the ID counting table 2b is updated (ID counting process). (Figure 3 Step 2
1). After that, the data processor 2 judges whether or not the lock command can be registered in the lock control table 2a (lock control table registration judgment processing) (step 22 in FIG. 3).

When the data processor 2 determines that the lock command can be registered in the lock control table 2a, it registers the lock command in the lock control table 2a (lock control table registration process) (step 2 in FIG. 3).
3).

Subsequently, the data processor 2 transfers the normal end report to one of the data transfer control processors 3 and 4 (normal end report issuing process) (step 2 in FIG. 3).
4). When the data transfer control processors 3 and 4 receive the normal end report from the data processor 2, the data transfer control processors 3 and 4 transfer the normal end report to the data processor 1.

When the data processor 1 receives the end report via the data transfer control processors 3 and 4, it determines whether the end report is a normal end report. When the data processor 1 determines that the end report is a normal end report, the lock instruction I of the lock instruction corresponding to the normal end report is received.
D is deleted from the lock command ID table 1a, and the lock command ID is released.

On the other hand, when the data processor 2 determines that the lock instruction cannot be registered in the lock control table 2a, the lock instruction ID of the lock instruction is registered in the hold table (asynchronous report lock ID registration processing) ( Figure 3
Step 25).

The data processor 2 issues an abnormal end report to one of the data transfer control processors 3 and 4 (abnormal end report issuing process) (step 26 in FIG. 3). Upon receiving the abnormal end report from the data processing processor 2, the data transfer control processing devices 3 and 4 transfer the abnormal end report to the data processing processor 1.

When the data processor 1 receives the end report via the data transfer control processors 3 and 4, it determines whether the end report is a normal end report. When the data processor 1 determines that the end report is an abnormal end report, the data processor 1 enters a state of waiting for an asynchronous report.

After this, when the data processing processor 2 can register the lock instruction in the lock control table 2a, the data processing processor 2 registers the lock instruction in the lock control table 2a. Then, the data processor 2 gives the asynchronous report 5 a count value corresponding to the lock instruction in the ID count table 2b, and issues the asynchronous report 5 to the data transfer control processors 3 and 4.

At this time, the data processor 2 judges whether or not there is an abnormality in the data transfer control processors 3 and 4, and if there is no abnormality, the lock instruction ID of the lock instruction corresponding to this asynchronous report 5 is stored in the pending table. Remove from. By this, the asynchronous report 5 in the data processor 2
Issuance processing is completed.

Upon receiving the asynchronous report 5 from the data processor 2, the data transfer control processors 3 and 4 transfer the asynchronous report 5 to the data processor 1. When the data processor 1 receives the asynchronous report 5 via the data transfer control processors 3 and 4, the count value corresponding to the lock command ID and the total count existing in the ID count reception table 1b for each lock command ID. The numerical value is compared (asynchronous report selection process) (step 31 in FIG. 4).

If the count values match, the data processor 1 ignores the asynchronous report 5. Further, if the count values do not match, the data processor 1 determines that a new asynchronous report 5 has been made, and determines the count value of the lock command ID corresponding to the asynchronous report 5 in the ID count reception table 1b. It is updated with the count value of the asynchronous report 5 (ID count storing process) (step 32 in FIG. 4). Thereafter, the data processor 1 deletes the lock command ID corresponding to the asynchronous report 5 from the lock command ID table 1a and releases the lock command ID (lock ID table deletion process) (step 33 in FIG. 4).

If a failure occurs in the data transfer control processor 3 while the asynchronous report 5 is being transferred by the data transfer control processor 3, the data processor 2 sets a path in the data transfer control processor 4. Then, the asynchronous report 5 is transferred via the data transfer control processing device 4. Upon receiving the asynchronous report 5, the data transfer control processing device 4 transfers the asynchronous report 5 to the data processor 1.

At this time, the asynchronous report 5 transferred to the data processor 1 via the data transfer control processing device 3 and the asynchronous report 5 transferred via the data transfer control processing device 4 overlap and report. However, the data processor 1 will only accept the first asynchronous report 5.

Therefore, since the asynchronous report 5 having the same count value of the same lock instruction ID is reported only once to the data processor 1, the data processor 1 corresponds to the lock instruction ID without contradiction. Asynchronous report 5 can be received.

FIG. 5 is a block diagram showing the configuration of the second embodiment of the present invention. In the figure, the data processors 6 and 7 are connected to each other via data transfer control processors 3 and 4. Note that FIG. 5 shows a case where the data processing processor 7 issues an end report or an asynchronous report in response to a lock instruction from the data processing processor 6.

The data processor 6 registers the lock instruction ID of the lock instruction with the lock instruction ID table 6a.
And a pre-lock command ID table 6b that stores the contents of the lock command ID table 6a at the time of the previous investigation. The data processor 7 also has a lock control table 7a for registering a lock command from the data processor 6.

FIG. 6 is a flowchart showing the processing operation of the data processor 7 of FIG. 5, and FIG. 7 is a flowchart showing the processing operation of the data processor 6 of FIG. The operation of the second embodiment of the present invention will be described with reference to FIGS.

The lock command issuing process and the end report receiving process by the data processor 6 are shown in FIGS. 30 and 31.
33. The lock command receiving process by the data processor 7 is the same as the process of the conventional example shown in FIG.

When issuing a lock instruction, the data processor 6 registers the lock instruction ID of the lock instruction in the lock instruction ID table 6a and issues the lock instruction to one of the data transfer control processors 3 and 4. To do. The data transfer control processors 3 and 4 are data processors 6
When the lock command is received from, the lock command is transferred to the data processor 7.

When the data processor 7 receives the lock command via the data transfer control processors 3 and 4, it determines whether the lock command can be registered in the lock control table 7a.

When the data processor 7 determines that the lock instruction can be registered in the lock control table 7a, it registers the lock instruction in the lock control table 7a. When the data processor 7 registers the lock command in the lock control table 7a, it issues a normal termination report to one of the data transfer control processors 3 and 4. Upon receiving the normal end report from the data processing processor 7, the data transfer control processing devices 3 and 4 transfer the normal end report to the data processing processor 6.

When the data processor 6 receives the end report via the data transfer control processors 3 and 4, it determines whether the end report is a normal end report. When the data processor 6 determines that the end report is the normal end report, the lock instruction I of the lock instruction corresponding to the normal end report is received.
D is deleted from the lock command ID table 6a, and the lock command ID is released.

On the other hand, when the data processor 7 determines that the lock instruction cannot be registered in the lock control table 7a, it registers the lock instruction ID of the lock instruction in the hold table (not shown).

The data processor 7 uses the lock instruction ID
Is registered in the hold table, an abnormal end report is issued to one of the data transfer control processing devices 3 and 4. Upon receiving the abnormal end report from the data processing processor 7, the data transfer control processing devices 3 and 4 transfer the abnormal end report to the data processing processor 6.

When the data processor 6 receives the end report via the data transfer control processors 3 and 4, it determines whether the end report is a normal end report. When the data processor 6 determines that the end report is an abnormal end report, the data processor 6 waits for an asynchronous report.

After that, when the data processing processor 7 can register the lock instruction in the lock control table 7a, the data processing processor 7 registers the lock instruction in the lock control table 7a (lock control table registration processing) (FIG. 6 step 41). Subsequently, the data processor 7 issues an asynchronous report to the data transfer control processors 3 and 4 (asynchronous report issuing process) (step 4 in FIG. 6).
2).

When the data processor 7 issues the asynchronous report, it deletes the lock instruction ID of the lock instruction corresponding to this asynchronous report from the pending table (asynchronous report lock ID deletion processing) (step 43 in FIG. 6). This completes the asynchronous report issuing process in the data processor 7.

Upon receipt of the asynchronous report from the data processor 7, the data transfer control processors 3 and 4 transfer the asynchronous report to the data processor 6. When the data processor 6 receives the asynchronous report via the data transfer control processors 3 and 4, the lock command ID corresponding to the asynchronous report is deleted from the lock command ID table 6a (lock ID table deletion process) (FIG. 7). Step 5
3) Release the lock command ID.

In the data processor 6, the timer process is activated at regular intervals to save the asynchronous report lost at the time of the failure of the data transfer control processors 3 and 4, and the lock instruction I
Contents of D table 6a and pre-lock command ID table 6b
Is compared (lock command ID table hold check process) (step 51 in FIG. 7).

Since the previous lock command ID table 6b stores the contents of the lock command ID table 6a at the time of the previous investigation, a lock command for which an asynchronous report has not been returned by comparison with the contents of the lock command ID table 6a. The ID can be detected.

When a match is detected in the comparison, the data processor 6 reads the contents of the lock control table 7a from the data processor 7 (lock control table read process) (step 52 in FIG. 7). The data processor 6 deletes the lock command ID registered in the lock control table 7a from the lock command ID table 6a (lock ID table deletion process) (step 53 in FIG. 7) and releases the lock command ID.

In the second embodiment of the present invention, if a failure occurs during the transfer of asynchronous reports by the data transfer control processors 3 and 4, the asynchronous reports will be lost, but the data will be lost at regular intervals. The lock instruction ID for which the asynchronous report is lost can be detected by the timer processing performed by the processor 6.

Therefore, when the data processor 6 detects the lock instruction ID for which the asynchronous report is lost, by confirming the registration of the lock instruction ID in the lock control table 7a, the lock instruction for which the asynchronous report is lost is confirmed. Processing can continue as if an asynchronous report had been received.

FIG. 8 is a block diagram showing the configuration of the third embodiment of the present invention. In the figure, the data processors 8 and 7 are connected to each other via data transfer control processors 3 and 4. Note that FIG. 8 shows a case where the data processing processor 7 issues an end report or an asynchronous report in response to a lock instruction from the data processing processor 8.

The data processor 8 registers the lock instruction ID of the lock instruction with the lock instruction ID table 8a.
And a pre-lock command ID table 8b and an ID suspension count table 8c. Further, the data processor 7 has a lock control table 7a for registering a lock command from the data processor 8.

Pre-lock instruction I of data processor 8
The D table 8b stores the contents of the lock command ID table 8a at the time of the previous investigation. Further, the number of times the contents of the lock command ID table 8a and the contents of the previous lock command ID table 8b match is stored in the ID suspension count table 8c by counting for each lock command ID.

FIG. 9 is a flow chart showing the processing operation of the data processor 8 of FIG. The operation of the third embodiment of the present invention will be described with reference to FIGS. 8 and 9. The lock command issuing process and the end report receiving process by the data processor 8 are the same as those of the conventional example shown in FIGS. 30 and 31.

The lock command receiving process by the data processor 7 is the same as the conventional process shown in FIG. 33, and the lock registration & asynchronous report issuing process by the data processor 7 is the second process of the present invention shown in FIG. The processing is the same as that of the embodiment described above.

When issuing a lock instruction, the data processor 8 registers the lock instruction ID of the lock instruction in the lock instruction ID table 8a, and issues the lock instruction to one of the data transfer control processors 3 and 4. To do. The data transfer control processors 3 and 4 are data processors 8
When the lock command is received from, the lock command is transferred to the data processor 7.

When the data processor 7 receives the lock command via the data transfer control processors 3 and 4, it determines whether the lock command can be registered in the lock control table 7a.

When the data processor 7 determines that the lock command can be registered in the lock control table 7a, it registers the lock command in the lock control table 7a. When the data processor 7 registers the lock command in the lock control table 7a, it issues a normal termination report to one of the data transfer control processors 3 and 4. Upon receiving the normal end report from the data processing processor 7, the data transfer control processing devices 3 and 4 transfer the normal end report to the data processing processor 8.

When the data processor 8 receives the end report via the data transfer control processors 3 and 4, it determines whether the end report is a normal end report. When the data processor 8 determines that the end report is the normal end report, the lock instruction I of the lock instruction corresponding to the normal end report is received.
D is deleted from the lock command ID table 8a, and the lock command ID is released.

On the other hand, when the data processor 7 determines that the lock instruction cannot be registered in the lock control table 7a, it registers the lock instruction ID of the lock instruction in the hold table (not shown).

The data processor 7 uses the lock instruction ID
Is registered in the hold table, an abnormal end report is issued to one of the data transfer control processing devices 3 and 4. Upon receiving the abnormal end report from the data processing processor 7, the data transfer control processing devices 3 and 4 transfer the abnormal end report to the data processing processor 8.

When the data processor 8 receives the end report via the data transfer control processors 3 and 4, the data processor 8 determines whether or not the end report is a normal end report. When the data processor 8 determines that the end report is an abnormal end report, the data processor 8 waits for an asynchronous report.

After that, when the data processing processor 7 can register the lock instruction in the lock control table 7a, the data processing processor 7 registers the lock instruction in the lock control table 7a. Then, the data processor 7 issues an asynchronous report to the data transfer control processors 3 and 4, and deletes the lock instruction ID of the lock instruction corresponding to this asynchronous report from the pending table. by this,
The process of issuing an asynchronous report in the data processor 7 is completed.

Upon receiving the asynchronous report from the data processor 7, the data transfer control processors 3 and 4 transfer the asynchronous report to the data processor 8. When the data processor 8 receives the asynchronous report via the data transfer control processors 3 and 4, the lock command ID corresponding to the asynchronous report is deleted from the lock command ID table 8a (lock ID table deletion process) (FIG. 9). Step 6
4) Release the lock command ID.

In the data processor 8, a timer process is activated at regular intervals to save the asynchronous report lost when the data transfer control processors 3 and 4 fail, and the lock instruction I
Contents of D table 8a and pre-lock command ID table 8b
Content is compared.

The data processor 8 updates the count value of the ID suspension count table 8c for each lock command ID for which a match is detected by the comparison, and the count value of the ID suspension count table 8c for each lock command ID for which no match is detected. Reset the count value (ID hold count & reset process)
(FIG. 9, step 61).

The data processor 8 determines whether or not the count value of the ID suspension count table 8c is equal to or greater than the preset value (ID suspension count check processing) (FIG. 9).
Step 62).

The data processor 8 ends the timer processing if the count value of the ID suspension count table 8c is within the set value. When the count value of the ID suspension count table 8c becomes equal to or larger than the set value, the data processor 8
The contents of the lock control table 7a are read from the data processor 7 (lock control table reading process) (FIG. 9).
Step 63).

The data processor 8 deletes the lock command ID registered in the lock control table 7a from the lock command ID table 8a (lock ID table deletion process) (step 64 in FIG. 9) and releases the lock command ID. .

In the third embodiment of the present invention, if a failure occurs while transferring the asynchronous report in the data transfer control processing devices 3 and 4, the asynchronous report will be lost, but after a certain period of time. The lock instruction ID for which the asynchronous report is lost can be detected by the timer processing of the data processor 8.

That is, the timer processing of the data processor 8 is activated, and the lock instruction ID for which the asynchronous report is currently suspended and the lock instruction ID for which the asynchronous report was previously suspended.
When the number of times of matching with the number exceeds the set value, the data processor 8 causes the lock control table 7a of the lock instruction ID
Since it confirms the registration with, it is possible to continue the processing of the lock instruction for which the asynchronous report is lost as if the asynchronous report was received.

FIG. 10 is a block diagram showing the configuration of the fourth embodiment of the present invention. In the figure, the data processors 9 and 7 are connected to each other via data transfer control processors 3 and 4. Note that FIG. 10 shows a case where the data processing processor 7 issues an end report or an asynchronous report in response to a lock instruction from the data processing processor 9.

The data processor 9 registers the lock instruction ID of the lock instruction with the lock instruction ID table 9a.
And an ID timer table 9b for counting the time after the abnormal end report is sent from the data processor 7. Further, the data processor 7 has a lock control table 7a for registering a lock command from the data processor 9.

11 and 12 are flowcharts showing the processing operation of the data processor 9 of FIG. The operation of the fourth embodiment of the present invention will be described with reference to FIGS.

The lock command issuing process by the data processor 9 is the same as the process of the conventional example shown in FIG. 30, and the lock command receiving process by the data processor 7 is the same as the process of the conventional example shown in FIG. The lock registration & asynchronous report issuing process by the data processor 7 is the same as the process of the second embodiment of the present invention shown in FIG.

When issuing a lock instruction, the data processor 9 registers the lock instruction ID of the lock instruction in the lock instruction ID table 9a, and issues the lock instruction to one of the data transfer control processors 3 and 4. To do. The data transfer control processors 3 and 4 are data processors 9
When the lock command is received from, the lock command is transferred to the data processor 7.

When the data processor 7 receives the lock command via the data transfer control processors 3 and 4, it determines whether the lock command can be registered in the lock control table 7a.

When the data processor 7 determines that the lock command can be registered in the lock control table 7a, it registers the lock command in the lock control table 7a. When the data processor 7 registers the lock command in the lock control table 7a, it issues a normal termination report to one of the data transfer control processors 3 and 4. Upon receiving the normal end report from the data processor 7, the data transfer control processing devices 3 and 4 transfer the normal end report to the data processor 9.

When the data processor 9 receives the end report via the data transfer control processing devices 3 and 4, it judges whether the end report is a normal end report (normal end report judging process) (step 81 in FIG. 12). ). When the data processor 9 determines that the end report is a normal end report,
The lock command ID of the lock command corresponding to the normal termination report is deleted from the lock command ID table 9a (lock ID table deletion process) (step 82 in FIG. 12), and the lock command ID is released.

On the other hand, when the data processor 7 determines that the lock instruction cannot be registered in the lock control table 7a, it registers the lock instruction ID of the lock instruction in the hold table (not shown).

The data processor 7 uses the lock instruction ID
Is registered in the hold table, an abnormal end report is issued to one of the data transfer control processing devices 3 and 4. Upon receiving the abnormal end report from the data processor 7, the data transfer control processing devices 3 and 4 transfer the abnormal end report to the data processor 9.

When the data processor 9 receives the end report via the data transfer control processing devices 3 and 4, it judges whether the end report is a normal end report (normal end report judging process) (step 81 in FIG. 12). ). When the data processor 9 determines that the end report is an abnormal end report,
A timer is registered in the ID timer table 9b for each lock command ID and started (ID timer start processing) (step 83 in FIG. 12), and the asynchronous report waiting state is entered.

After that, when the data processing processor 7 can register the lock instruction in the lock control table 7a, the data processing processor 7 registers the lock instruction in the lock control table 7a. Then, the data processor 7 issues an asynchronous report to the data transfer control processors 3 and 4, and deletes the lock instruction ID of the lock instruction corresponding to this asynchronous report from the pending table. by this,
The process of issuing an asynchronous report in the data processor 7 is completed.

When the data transfer control processors 3 and 4 receive the asynchronous report from the data processor 7, they transfer the asynchronous report to the data processor 9. When the data processor 9 receives the asynchronous report via the data transfer control processors 3 and 4, it resets the timer of the ID timer table 9b of the lock instruction ID corresponding to the asynchronous report (ID reset processing) (step in FIG. 11). 76),
The lock command ID is deleted from the lock command ID table 9a (lock ID table deletion process) (step 77 in FIG. 11), and the lock command ID is released.

In the data processor 9, a timer process is started at regular time intervals in order to save an asynchronous report lost at the time of a failure of the data transfer control processors 3 and 4, and an ID timer table 9b is registered for each registered lock command ID. The timer subtraction process is performed (ID timer process) (step 71 in FIG. 11).

At this time, the data processor 9 determines whether or not a time-out has occurred by the timer subtraction processing (ID timer check processing) (step 7 in FIG. 11).
2). When it is determined that a time-out has occurred, the data processor 9 reads the contents of the lock control table 7a from the data processor 7 (lock control table read processing) (step 73 in FIG. 11).

The data processor 9 determines whether or not the lock command ID is registered in the lock control table 7a (lock control table check process) (FIG. 1).
1 step 74).

If the lock command ID is registered in the lock control table 7a, the data processor 9 resets the timer of the ID timer table 9b for the lock command ID (ID reset process) (step 7 in FIG. 11).
6), the lock instruction ID is assigned to the lock instruction ID table 9
Deleted from a (lock ID table deletion processing) (FIG. 11)
In step 77), the lock command ID is released.

On the other hand, if the lock instruction ID is not registered in the lock control table 7a, the data processor 9 sets the timer of the lock instruction ID in the ID timer table 9b and restarts (ID timer restart processing). ) (FIG. 11, step 75).

In the fourth embodiment of the present invention, if a failure occurs while transferring the asynchronous report in the data transfer control processing devices 3 and 4, the asynchronous report will be lost, but after a certain period of time. Since the timeout of the lock instruction ID is detected by the timer processing performed in the data processor 9, the lock instruction ID for which the asynchronous report is lost is detected.
Can be detected.

Accordingly, the timer processing of the data processor 9 is started, and the lock instruction ID for which the asynchronous report is lost
When the lock is detected, the data processor 9 confirms the registration of the lock instruction ID in the lock control table 7a to continue the processing of the lock instruction for which the asynchronous report is lost, as if the asynchronous report was received. be able to.

FIG. 13 is a block diagram showing the configuration of the fifth embodiment of the present invention. In the figure, the data processors 10 and 7 are connected to each other via data transfer control processors 3 and 4. Note that FIG. 13 shows a case where the data processing processor 7 issues an end report or an asynchronous report in response to a lock instruction from the data processing processor 10.

The data processor 10 registers the lock instruction ID of the lock instruction in the lock instruction ID table 10
a, a lock command ID counting table 10b, and a previous lock command ID counting table 10c. Further, the data processor 7 has a lock control table 7a for registering a lock command from the data processor 10.

Lock instruction I of the data processor 10
The D count table 10b stores the number of lock commands counted for each lock command ID when the lock command is issued. Further, the previous lock command ID counting table 10c stores the count value of the lock command ID counting table 10b at the time of the previous investigation.

14 and 15 are flowcharts showing the processing operation of the data processor 10 of FIG.
The operation of the fifth embodiment of the present invention will be described with reference to FIGS.

The end report receiving process by the data processor 10 is similar to the conventional process shown in FIG. 31, and the lock command receiving process by the data processor 7 is similar to the conventional process shown in FIG. The lock registration & asynchronous report issuing process by the data processor 7 is the same as the process of the second embodiment of the present invention shown in FIG.

When issuing a lock command, the data processor 10 registers the lock command ID of the lock command in the lock command ID table 10a (lock ID registration process) (step 91 in FIG. 14). When the data processor 10 registers the lock command ID of the lock command, the data processor 10 counts the number of lock commands corresponding to the lock command ID of the lock command and stores the count in the lock command ID counting table 10b (lock command ID counting process) ( 14 step 92).

After that, the data processor 10 issues the lock instruction to one of the data transfer control processors 3 and 4 (lock instruction issue processing) (step 93 in FIG. 14). Upon receiving the lock command from the data processor 10, the data transfer control processing devices 3 and 4 transfer the lock command to the data processor 7.

When the data processor 7 receives the lock command via the data transfer control processors 3 and 4, it judges whether the lock command can be registered in the lock control table 7a.

When the data processor 7 determines that the lock instruction can be registered in the lock control table 7a, it registers the lock instruction in the lock control table 7a. When the data processor 7 registers the lock command in the lock control table 7a, it issues a normal termination report to one of the data transfer control processors 3 and 4. Upon receiving the normal end report from the data processor 7, the data transfer control processing devices 3 and 4 transfer the normal end report to the data processor 10.

When the data processor 10 receives the end report via the data transfer control processors 3 and 4, it determines whether the end report is a normal end report. When the data processor 10 determines that the end report is a normal end report, it deletes the lock command ID of the lock command corresponding to the normal end report from the lock command ID table 10a and releases the lock command ID.

On the other hand, when the data processor 7 determines that the lock instruction cannot be registered in the lock control table 7a, it registers the lock instruction ID of the lock instruction in the hold table (not shown).

The data processor 7 uses the lock instruction ID
Is registered in the hold table, an abnormal end report is issued to one of the data transfer control processing devices 3 and 4. Upon receiving the abnormal end report from the data processing processor 7, the data transfer control processing devices 3 and 4 transfer the abnormal end report to the data processing processor 10.

When the data processor 10 receives the end report via the data transfer control processors 3 and 4, it determines whether the end report is a normal end report. When the data processor 10 determines that the end report is an abnormal end report, the data processor 10 waits for an asynchronous report.

After that, when the data processing processor 7 can register the lock instruction in the lock control table 7a, the data processing processor 7 registers the lock instruction in the lock control table 7a. Then, the data processor 7 issues an asynchronous report to the data transfer control processors 3 and 4, and deletes the lock instruction ID of the lock instruction corresponding to this asynchronous report from the pending table. by this,
The process of issuing an asynchronous report in the data processor 7 is completed.

Upon receiving the asynchronous report from the data processor 7, the data transfer control processors 3 and 4 transfer the asynchronous report to the data processor 10. When the data processor 10 receives the asynchronous report via the data transfer control processors 3 and 4, the lock command ID corresponding to the asynchronous report is deleted from the lock command ID table 10a (lock ID table deletion process) (FIG. 15). In step 103), the lock command ID is released.

In the data processor 10, a timer process is started at regular time intervals in order to save the asynchronous report lost when the data transfer control processors 3 and 4 have failed, and the contents of the lock command ID counting table 10b and the previous lock command ID are stored. The contents of the counting table 10c are compared (lock command ID
Counting table check process) (Step 10 in FIG. 15)
1).

If no match is detected in the comparison, the data processor 10 ends the timer processing. Also,
If a match is detected in the comparison, the data processor 10 reads the contents of the lock control table 7a from the data processor 7 for each lock instruction ID for which a match is detected (lock control table read process) (step in FIG. 15). 102).

The data processor 10 deletes the lock command ID registered in the lock control table 7a from the lock command ID table 10a (lock ID table deleting process) (step 103 in FIG. 15) and releases the lock command ID. .

In the fifth embodiment of the present invention, if a failure occurs while transferring the asynchronous report in the data transfer control processing devices 3 and 4, the asynchronous report will be lost, but after a certain period of time. The lock instruction ID for which the asynchronous report is lost can be detected by the timer processing of the data processor 10.

That is, when the timer processing of the data processor 10 is started and the count value of the lock instruction ID for which the asynchronous report is currently suspended and the count value of the lock instruction ID for which the previous suspension has been performed match, the data is The processor 10 uses the lock control table 7a of the lock instruction ID.
Since it confirms the registration with, it is possible to continue the processing of the lock instruction for which the asynchronous report is lost as if the asynchronous report was received.

FIG. 16 is a block diagram showing the configuration of the sixth embodiment of the present invention. In the figure, the data processors 11 and 7 are connected to each other via data transfer control processors 3 and 4. Note that FIG. 16 shows a case where the data processing processor 7 issues an end report or an asynchronous report in response to a lock instruction from the data processing processor 11.

The data processor 11 registers the lock instruction ID of the lock instruction in the lock instruction ID table 11
a, a lock command ID counting table 11b, a previous lock command ID counting table 11c, and an ID matching count table 11d. The data processor 7 also has a lock control table 7a for registering a lock command from the data processor 11.

Lock instruction I of the data processor 11
The D count table 11b stores the number of lock commands counted for each lock command ID when the lock command is issued. The previous lock command ID counting table 11c stores the count value of the lock command ID counting table 11b at the time of the previous investigation.

Further, the ID match count table 11d.
The number of times that the content of the lock command ID counting table 11b and the content of the previous lock command ID counting table 11c match is counted and stored for each lock command ID.

FIG. 17 shows the data processor 1 of FIG.
3 is a flowchart showing the processing operation of No. 1. These Figure 1
The operation of the sixth embodiment of the present invention will be described with reference to FIGS.

The end report receiving process by the data processor 11 is similar to the process of the conventional example shown in FIG. 31, and the lock command issuing process by the data processor 11 is the fifth embodiment of the present invention shown in FIG. The process is the same as that of.

Further, the lock command receiving process by the data processor 7 is similar to the process of the conventional example shown in FIG. 33, and the lock registration & asynchronous report issuing process by the data processor 7 is the second process of the present invention shown in FIG. The processing is the same as that of the embodiment described above.

When issuing a lock instruction, the data processor 11 registers the lock instruction ID of the lock instruction in the lock instruction ID table 11a. When the data processor 11 registers the lock instruction ID of the lock instruction, the data processor 11 counts the number of lock instructions corresponding to the lock instruction ID of the lock instruction, and the lock instruction ID counting table 11b.
To store.

After that, the data processor 11 issues the lock instruction to one of the data transfer control processors 3 and 4. Upon receiving the lock command from the data processor 11, the data transfer control processing devices 3 and 4 transfer the lock command to the data processor 7.

When the data processor 7 receives the lock command via the data transfer control processors 3 and 4, it determines whether or not the lock command can be registered in the lock control table 7a.

When the data processor 7 determines that the lock instruction can be registered in the lock control table 7a, it registers the lock instruction in the lock control table 7a. When the data processor 7 registers the lock command in the lock control table 7a, it issues a normal termination report to one of the data transfer control processors 3 and 4. Upon receiving the normal end report from the data processor 7, the data transfer control processing devices 3 and 4 transfer the normal end report to the data processor 11.

When the data processing processor 11 receives the end report via the data transfer control processing devices 3 and 4, it determines whether or not the end report is a normal end report. When the data processor 11 determines that the end report is a normal end report, it deletes the lock command ID of the lock command corresponding to the normal end report from the lock command ID table 11a and releases the lock command ID.

On the other hand, when the data processor 7 determines that the lock instruction cannot be registered in the lock control table 7a, it registers the lock instruction ID of the lock instruction in the hold table (not shown).

The data processor 7 uses the lock instruction ID
Is registered in the hold table, an abnormal end report is issued to one of the data transfer control processing devices 3 and 4. Upon receiving the abnormal end report from the data processing processor 7, the data transfer control processing devices 3 and 4 transfer the abnormal end report to the data processing processor 11.

When the data processor 11 receives the end report via the data transfer control processors 3 and 4, it determines whether the end report is a normal end report. When the data processor 11 determines that the end report is an abnormal end report, the data processor 11 waits for an asynchronous report.

After that, when the data processing processor 7 can register the lock instruction in the lock control table 7a, the data processing processor 7 registers the lock instruction in the lock control table 7a. Then, the data processor 7 issues an asynchronous report to the data transfer control processors 3 and 4, and deletes the lock instruction ID of the lock instruction corresponding to this asynchronous report from the pending table. by this,
The process of issuing an asynchronous report in the data processor 7 is completed.

Upon receiving the asynchronous report from the data processor 7, the data transfer control processors 3 and 4 transfer the asynchronous report to the data processor 11. When the data processor 11 receives the asynchronous report via the data transfer control processors 3 and 4, the lock command ID corresponding to the asynchronous report is deleted from the lock command ID table 11a (lock ID table deletion process) (FIG. 17). In step 114), the lock command ID is released.

In the data processor 11, a timer process is activated at regular intervals to save the asynchronous report lost at the time of the failure of the data transfer control processors 3 and 4, and the contents of the lock command ID counting table 11b and the previous lock command ID are stored. The contents of the counting table 11c are compared.

The data processor 11 updates the count value of the ID match count table 11d for each lock command ID for which a match is detected by the comparison, and the ID match count table 11d for each lock command ID for which no match is detected.
The count value of is reset (ID matching count process) (step 111 in FIG. 17).

The data processor 11 determines whether or not the count value of the ID match count table 11d is equal to or larger than the preset value (ID match count check process).
(FIG. 17, step 112).

If the count value of the ID match count table 11d is within the set value, the data processor 11 ends the timer process. Further, the data processor 11 is
When the count value of the D match count table 11d becomes equal to or larger than the set value, the contents of the lock control table 7a are read from the data processor 7 (lock control table read process) (step 113 in FIG. 17).

The data processor 11 deletes the lock command ID registered in the lock control table 7a from the lock command ID table 11a (lock ID table deleting process) (step 114 in FIG. 17) and releases the lock command ID. .

In the sixth embodiment of the present invention, if a failure occurs during the transfer of asynchronous reports by the data transfer control processors 3 and 4, the asynchronous reports will be lost, but after a certain period of time. The lock instruction ID for which the asynchronous report is lost can be detected by the timer processing of the data processor 11.

That is, the timer processing of the data processor 11 is activated, and the number of times that the count value of the lock instruction ID for which the asynchronous report is currently suspended and the count value of the lock instruction ID for which the previous suspension has been held match each other is determined. When the value exceeds the set value, the data processor 11 confirms the registration of the lock instruction ID in the lock control table 7a. Therefore, the asynchronous instruction is lost and the processing of the lock instruction can be continued as if the asynchronous report was received. it can.

FIG. 18 is a block diagram showing the configuration of the seventh embodiment of the present invention. In the figure, the data processors 12 and 13 are connected to each other via data transfer control processors 3 and 4. Note that FIG. 18 shows a case where the data processing processor 13 issues an end report or an asynchronous report in response to a lock instruction from the data processing processor 12.

The data processor 12 registers the lock instruction ID of the lock instruction in the lock instruction ID table 12
a. Further, the data processor 13 has a lock control table 13a for registering a lock command from the data processor 12, and an ID counting table 13b.
And the previous ID counting table 13c.

The ID count table 13b of the data processor 13 stores the number of lock commands counted for each lock command ID when the lock command is received. The previous ID count table 13c stores the count value of the ID count table 13b at the time of the previous survey.

FIG. 19 shows the data processor 1 of FIG.
3 is a diagram showing an asynchronous report C output from FIG. In the figure, the asynchronous report C14 is composed of an asynchronous report C14a and a lock command ID 14b.

FIG. 20 shows the data processor 1 of FIG.
21 is a flowchart showing the processing operation of No. 3, and FIG. 21 is a flowchart showing the processing operation of the data processor 12 of FIG. The operation of the seventh embodiment of the present invention will be described with reference to FIGS.

The lock command issuing process and the end report receiving process by the data processor 12 are shown in FIGS.
This is the same as the processing of the conventional example shown in FIG. Further, the lock command receiving process by the data processor 13 is the same as the process of the first embodiment of the present invention shown in FIG. 3, and the lock registration & asynchronous report issuing process by the data processor 13 is the present invention shown in FIG. The process is the same as that of the second embodiment.

When issuing a lock instruction, the data processor 12 registers the lock instruction ID of the lock instruction in the lock instruction ID table 12a and issues the lock instruction to one of the data transfer control processors 3 and 4. To do.
Upon receiving the lock command from the data processor 12, the data transfer control processing devices 3 and 4 transfer the lock command to the data processor 13.

When the data processor 13 receives the lock command via the data transfer control processors 3 and 4, it counts the number of lock commands for each lock command ID and updates the ID counting table 13b. After that, the data processor 13 determines whether or not the lock instruction can be registered in the lock control table 13a.

When the data processor 13 determines that the lock instruction can be registered in the lock control table 13a, it registers the lock instruction in the lock control table 13a. When the data processor 13 registers the lock command in the lock control table 13a, it issues a normal termination report to one of the data transfer control processors 3 and 4. The data transfer control processors 3 and 4 are data processors 1.
When the normal end report is received from 3, the normal end report is transferred to the data processor 12.

When the data processor 12 receives the end report via the data transfer control processors 3 and 4, it determines whether the end report is a normal end report. When the data processor 12 determines that the end report is a normal end report, it deletes the lock command ID of the lock command corresponding to the normal end report from the lock command ID table 12a, and releases the lock command ID.

On the other hand, when the data processor 13 determines that the lock command cannot be registered in the lock control table 13a, the data processor 13 registers the lock command ID of the lock command in the hold table (not shown).

The data processor 13 uses the lock instruction I
When D is registered in the hold table, an abnormal end report is issued to one of the data transfer control processing devices 3 and 4. The data transfer control processing devices 3 and 4 are data processing processors 13
When the abnormal end report is received from the data processing processor 12, the abnormal end report is transferred to the data processor 12.

When the data processor 12 receives the end report via the data transfer control processors 3 and 4, it determines whether the end report is a normal end report. When the data processor 12 determines that the end report is an abnormal end report, the data processor 12 enters a state of waiting for an asynchronous report.

After that, when the data processing processor 13 can register the lock instruction in the lock control table 13a, the data processing processor 13 registers the lock instruction in the lock control table 13a. Then, the data processor 13 issues an asynchronous report to the data transfer control processors 3 and 4, and deletes the lock instruction ID of the lock instruction corresponding to this asynchronous report from the pending table. This completes the asynchronous report issuing process in the data processor 13.

Upon receiving the asynchronous report from the data processor 13, the data transfer control processors 3 and 4 transfer the asynchronous report to the data processor 12. When the data processor 12 receives the asynchronous report via the data transfer control processors 3 and 4, the data processor 12 determines whether the asynchronous report is an asynchronous report C requesting confirmation of the contents of the lock control table 13a (asynchronous report C determination). Processing) (FIG. 21)
Step 131).

When the data processor 12 determines that the asynchronous report is not the asynchronous report C, it deletes the lock command ID corresponding to the asynchronous report from the lock command ID table 12a (lock ID table deletion process) (step 21 in FIG. 21). 132), the lock instruction ID is released.

In the data processor 13, a timer process is activated at regular intervals in order to save the asynchronous report lost at the time of the failure of the data transfer control processors 3 and 4, and the contents of the ID counting table 13b and the previous ID counting table 13c are saved. The contents are compared (ID counting table check processing) (step 121 in FIG. 20).

If no coincidence is detected in the comparison, the data processor 13 ends the timer processing. Also,
If a match is detected in the comparison, the data processor 13 sends an asynchronous report C requesting confirmation of the contents of the lock control table 13a corresponding to the lock instruction ID to the data transfer control processors 3 and 4 (asynchronous report). Issuing process) (step 122 in FIG. 20).

Upon receiving the asynchronous report C from the data processor 13, the data transfer control processors 3 and 4 transfer the asynchronous report C to the data processor 12. The data processor 12 is a data transfer control processor 3,
When the asynchronous report C is received via 4, it is determined whether the asynchronous report C is an asynchronous report C requesting confirmation of the contents of the lock control table 13a (asynchronous report C determination processing).
(FIG. 21, step 131).

When the data processor 12 determines that the asynchronous report is the asynchronous report C, it reads the contents of the lock control table 13a from the data processor 13 (lock control table read process) (step 13 in FIG. 21).
3).

The data processor 12 deletes the lock command ID registered in the lock control table 13a from the lock command ID table 13a (lock command ID table correction process) (step 134 in FIG. 21) and releases the lock command ID. To do.

In the seventh embodiment of the present invention, if a failure occurs while transferring the asynchronous report in the data transfer control processors 3 and 4, the asynchronous report will be lost, but after a certain period of time. The lock instruction ID for which the asynchronous report is lost can be detected by the timer processing of the data processor 13.

That is, when the timer process of the data processor 13 is activated and the lock command ID whose number of receptions matches the count value at the time of the previous investigation is detected, the lock control table 13a corresponding to the lock command ID is detected. An asynchronous report C is issued requesting confirmation of the contents.

Since the data processor 12 confirms the registration of the lock instruction ID in the lock control table 13a in response to the asynchronous report C, the asynchronous report is received for the processing of the lock instruction for which the asynchronous report is lost. Can continue as.

FIG. 22 is a block diagram showing the structure of the eighth embodiment of the present invention. In the figure, the data processors 12 and 15 are connected to each other via data transfer control processors 3 and 4. Note that FIG. 22 shows a case where the data processing processor 15 issues an end report or an asynchronous report in response to a lock instruction from the data processing processor 12.

The data processor 12 registers the lock instruction ID of the lock instruction in the lock instruction ID table 12
a. Further, the data processor 15 has a lock control table 15a for registering a lock command from the data processor 12, and an ID counting table 15b.
And a previous ID counting table 15c and an ID matching counting table 15d.

The ID count table 15b of the data processor 15 stores the number of lock commands counted for each lock command ID when the lock command is received. The previous ID counting table 15c stores the count value of the ID counting table 15b at the time of the previous survey.

Further, the ID match count table 15d.
The number of times that the content of the lock command ID counting table 15b and the content of the previous lock command ID counting table 15c match is counted and stored for each lock command ID.

FIG. 23 shows the data processor 1 of FIG.
6 is a flowchart showing a processing operation of No. 5. These Figure 2
The operation of the eighth embodiment of the present invention will be described with reference to FIGS.

The lock command issuing process and the end report receiving process by the data processor 12 are shown in FIG. 30 and FIG.
The processing is the same as the processing of the conventional example shown in FIG. 1, and the asynchronous report receiving processing by the data processor 12 is the same as the processing of the seventh embodiment of the present invention shown in FIG.

Further, the lock command receiving process by the data processor 15 is similar to the process of the first embodiment of the present invention shown in FIG. 3, and the lock registration & asynchronous report issuing process by the data processor 15 is shown in FIG. This is similar to the processing of the second embodiment of the present invention shown.

When issuing a lock instruction, the data processor 12 registers the lock instruction ID of the lock instruction in the lock instruction ID table 12a, and issues the lock instruction to one of the data transfer control processors 3 and 4. To do. Upon receiving the lock command from the data processor 12, the data transfer control processing devices 3 and 4 transfer the lock command to the data processor 15.

When the data processor 15 receives the lock command via the data transfer control processors 3 and 4, it counts the number of lock commands for each lock command ID and updates the ID counting table 15b. Thereafter, the data processor 15 determines whether the lock command can be registered in the lock control table 15a.

When the data processor 15 determines that the lock instruction can be registered in the lock control table 15a, it registers the lock instruction in the lock control table 15a. When the data processor 15 registers the lock command in the lock control table 15a, it issues a normal termination report to one of the data transfer control processors 3 and 4. The data transfer control processors 3 and 4 are data processors 1.
When the normal end report is received from 5, the normal end report is transferred to the data processor 12.

When the data processor 12 receives the end report via the data transfer control processors 3 and 4, the data processor 12 determines whether or not the end report is a normal end report. When the data processor 12 determines that the end report is a normal end report, it deletes the lock command ID of the lock command corresponding to the normal end report from the lock command ID table 12a, and releases the lock command ID.

On the other hand, when the data processor 15 determines that the lock instruction cannot be registered in the lock control table 15a, it registers the lock instruction ID of the lock instruction in the hold table (not shown).

The data processor 15 uses the lock instruction I
When D is registered in the hold table, an abnormal end report is issued to one of the data transfer control processing devices 3 and 4. The data transfer control processors 3 and 4 are data processors 15
When the abnormal end report is received from the data processing processor 12, the abnormal end report is transferred to the data processor 12.

When the data processor 12 receives the end report via the data transfer control processors 3 and 4, the data processor 12 determines whether or not the end report is a normal end report. When the data processor 12 determines that the end report is an abnormal end report, the data processor 12 enters a state of waiting for an asynchronous report.

After that, when the data processing processor 15 can register the lock instruction in the lock control table 15a, the data processing processor 15 registers the lock instruction in the lock control table 15a. Then, the data processor 15 issues an asynchronous report to the data transfer control processors 3 and 4, and deletes the lock instruction ID of the lock instruction corresponding to this asynchronous report from the pending table. This completes the asynchronous report issuing process in the data processor 15.

Upon receiving the asynchronous report from the data processor 15, the data transfer control processors 3 and 4 transfer the asynchronous report to the data processor 12. When the data processor 12 receives the asynchronous report via the data transfer control processors 3 and 4, the data processor 12 determines whether or not the asynchronous report is an asynchronous report C requesting confirmation of the contents of the lock control table 15a.

When the data processor 12 determines that the asynchronous report is not the asynchronous report C, it deletes the lock instruction ID corresponding to the asynchronous report from the lock instruction ID table 12a and releases the lock instruction ID.

In the data processor 15, a timer process is activated at regular intervals to save the asynchronous report lost at the time of the failure of the data transfer control processors 3 and 4, and the contents of the ID counting table 15b and the previous ID counting table 15c are stored. The content is compared.

The data processor 15 updates the count value of the ID match count table 15d for each lock command ID for which a match is detected by the comparison, and the ID match count table 15d for each lock command ID for which no match is detected.
The count value of is reset (ID matching count process) (step 141 in FIG. 23).

The data processor 15 determines whether or not the count value of the ID match count table 15d is equal to or larger than the preset value (ID match count check process).
(FIG. 23, step 142).

The data processor 15 terminates the timer processing if the count value of the ID match count table 15d is within the set value. In addition, the data processor 15
When the count value of the D match count table 15d becomes equal to or larger than the set value, an asynchronous report C requesting confirmation of the contents of the lock control table 15a corresponding to the lock instruction ID is transmitted to the data transfer control processing devices 3 and 4 (asynchronous report). Issue process) (step 143 in FIG. 23).

Upon receiving the asynchronous report C from the data processor 15, the data transfer control processors 3 and 4 transfer the asynchronous report C to the data processor 12. The data processor 12 is a data transfer control processor 3,
When the asynchronous report C is received via 4, it is determined whether the asynchronous report C is an asynchronous report C requesting confirmation of the contents of the lock control table 15a.

When the data processor 12 determines that the asynchronous report is the asynchronous report C, the data processor 12 reads the contents of the lock control table 15a from the data processor 15. After that, the data processor 12 deletes the lock command ID registered in the lock control table 15a from the lock command ID table 15a, and releases the lock command ID.

In the eighth embodiment of the present invention, if a failure occurs while the asynchronous transfer is being transferred by the data transfer control processors 3 and 4, the asynchronous report will be lost, but after a certain period of time. The lock instruction ID for which the asynchronous report is lost can be detected by the timer processing of the data processor 15.

That is, when the timer processing of the data processor 15 is activated and the number of times the number of receptions of the lock command ID that matches the count value at the time of the previous investigation exceeds the set value, the lock corresponding to the lock command ID is locked. An asynchronous report C requesting confirmation of the contents of the control table 15a is issued.

In response to the asynchronous report C, the data processor 12 confirms the registration of the lock instruction ID in the lock control table 15a. Therefore, the processing of the lock instruction for which the asynchronous report is lost receives the asynchronous report. Can continue as.

FIG. 24 is a block diagram showing the configuration of the ninth embodiment of the present invention. In the figure, the data processors 12 and 16 are connected to each other via data transfer control processors 3 and 4. Note that FIG. 24 shows a case where the data processing processor 16 issues an end report or an asynchronous report in response to a lock instruction from the data processing processor 12.

The data processor 12 has a lock command ID table 12a for registering the lock command ID of the lock command to be issued. Further, the data processing processor 16 has a lock control table 16a for registering a lock command from the data processing processor 12 and an attention lock timer table 16b for counting the time after sending an asynchronous report to the data processing processor 12. There is.

25 to 27 are flowcharts showing the processing operation of the data processor 16 of FIG. The operation of the ninth embodiment of the present invention will be described with reference to FIGS.

The lock command issuing process and the end report receiving process by the data processor 12 are shown in FIGS.
The processing is the same as the processing of the conventional example shown in FIG. 1, and the asynchronous report receiving processing by the data processor 12 is the same as the processing of the seventh embodiment of the present invention shown in FIG.

When issuing a lock instruction, the data processor 12 registers the lock instruction ID of the lock instruction in the lock instruction ID table 12a and issues the lock instruction to one of the data transfer control processors 3 and 4. To do. Upon receiving the lock command from the data processor 12, the data transfer control processing devices 3 and 4 transfer the lock command to the data processor 16.

When the data processor 16 receives the lock command via the data transfer control processors 3 and 4, the attention lock timer table 1 for each lock command ID is received.
The timer 6b is reset (attention lock timer reset processing) (step 151 in FIG. 25).

After that, the data processor 16 judges whether or not the lock command can be registered in the lock control table 16a (lock control table registration judgment processing) (step 152 in FIG. 25).

When the data processor 16 determines that the lock command can be registered in the lock control table 16a, it registers the lock command in the lock control table 16a (lock control table registration process) (step 153 in FIG. 25).

When the data processor 16 registers the lock command in the lock control table 16a, it issues a normal termination report to one of the data transfer control processors 3 and 4 (normal termination report issuing process) (step 15 in FIG. 25).
4). When the data transfer control processors 3 and 4 receive the normal end report from the data processor 16, the data transfer control processors 3 and 4 transfer the normal end report to the data processor 12.

When the data processor 12 receives the end report via the data transfer control processors 3 and 4, it determines whether the end report is a normal end report. When the data processor 12 determines that the end report is a normal end report, it deletes the lock command ID of the lock command corresponding to the normal end report from the lock command ID table 12a, and releases the lock command ID.

On the other hand, when the data processor 16 determines that the lock instruction cannot be registered in the lock control table 16a, it registers the lock instruction ID of the lock instruction in a pending table (not shown) (asynchronous report lock ID registration). Processing) (step 155 in FIG. 25).

The data processor 16 uses the lock instruction I
When D is registered in the hold table, an abnormal end report is issued to one of the data transfer control processing devices 3 and 4 (abnormal end report issuing process) (step 156 in FIG. 25). Upon receiving the abnormal end report from the data processing processor 16, the data transfer control processing devices 3 and 4 transfer the abnormal end report to the data processing processor 12.

When the data processor 12 receives the end report via the data transfer control processors 3 and 4, it determines whether the end report is a normal end report. When the data processor 12 determines that the end report is an abnormal end report, the data processor 12 enters a state of waiting for an asynchronous report.

After that, when the data processing processor 16 can register the lock instruction in the lock control table 16a, the data processing processor 16 registers the lock instruction in the lock control table 16a (lock control table registration processing) (FIG. 26 step 161). Subsequently, the data processor 16 issues an asynchronous report to the data transfer control processing devices 3 and 4 (asynchronous report issuing process) (FIG. 26).
Step 162).

When the data processor 16 issues an asynchronous report, it deletes the lock command ID of the lock command corresponding to this asynchronous report from the pending table (asynchronous report lock ID deletion process) (step 163 in FIG. 26).

At this time, the data processor 16 sets the attention lock timer table 1 for each lock instruction ID.
A timer is registered in 6b and started (attention lock timer processing) (step 164 in FIG. 26). This completes the asynchronous report issuing process in the data processor 16.

Upon receiving the asynchronous report from the data processor 16, the data transfer control processors 3 and 4 transfer the asynchronous report to the data processor 12. When the data processor 12 receives the asynchronous report via the data transfer control processors 3 and 4, the data processor 12 determines whether or not the asynchronous report is an asynchronous report C requesting confirmation of the contents of the lock control table 16a.

When the data processor 12 determines that the asynchronous report is not the asynchronous report C, it deletes the lock instruction ID corresponding to the asynchronous report from the lock instruction ID table 12a and releases the lock instruction ID.

In the data processor 16, a timer process is activated at regular intervals in order to save an asynchronous report lost at the time of a failure of the data transfer control processors 3 and 4, and an attention lock timer table is registered for each registered lock command ID. The contents of 16b are updated.

At this time, the data processor 16 determines whether or not a timeout has occurred due to the update processing (attention lock timer check processing) (step 171 in FIG. 27).

When it is determined that a time-out has occurred, the data processor 16 sends an asynchronous report C requesting confirmation of the contents of the lock control table 16a corresponding to the lock instruction ID to the data transfer control processors 3 and 4 (asynchronous). Report issuance process) (step 172 in FIG. 27). Subsequently, the data processor 16 resets and starts the timer in the attention lock timer table 16b (attention lock timer restart processing) (step 173 in FIG. 27).

Upon receiving the asynchronous report C from the data processor 16, the data transfer control processors 3 and 4 transfer the asynchronous report C to the data processor 12. The data processor 12 is a data transfer control processor 3,
When the asynchronous report C is received via 4, it is determined whether the asynchronous report C is the asynchronous report C requesting confirmation of the contents of the lock control table 13a.

When the data processor 12 determines that the asynchronous report is the asynchronous report C, the data processor 12 reads the contents of the lock control table 16a from the data processor 16. After that, the data processor 12 deletes the lock command ID registered in the lock control table 16a from the lock command ID table 12a, and releases the lock command ID.

In the ninth embodiment of the present invention, if a failure occurs while the asynchronous transfer is being transferred by the data transfer control processors 3 and 4, the asynchronous report will be lost, but after a certain period of time. The lock instruction ID for which the asynchronous report is lost can be detected by the timer processing of the data processor 16.

That is, when the data processing processor 16 starts the timer processing and the timeout of the attention lock timer table 16b is detected, an asynchronous report requesting confirmation of the contents of the lock control table 16a corresponding to the lock instruction ID. C is issued.

Since the data processor 12 confirms the registration of the lock instruction ID in the lock control table 16a in response to the asynchronous report C, the asynchronous report is received for the processing of the lock instruction for which the asynchronous report is lost. Can continue as.

The above-mentioned respective processes are executed from the data processor 1, 6, 8 to 12 to the data processor 2, 7 ,.
The processing is for issuing a lock command to 13.15 and 16. However, the processing can be applied to the opposite case. Further, the flowchart showing each process shows a subroutine of each data processor 1, 2, 6 to 13, 15, 16 and the return shows a return to the original process.

As described above, every time the data processor 1 receives an asynchronous report from the data processor 2, the count value of the ID counting table 2b assigned to the asynchronous report from the data processor 2 and the data processor A data transfer control processing device positioned in the middle by comparing the count value held in the ID count reception table 1b of 1 and ignoring the asynchronous report in which the coincidence is detected and accepting only the first asynchronous report. Even if a failure occurs in 3 or 4, the receiving side of the asynchronous report can continue the operation without contradiction, and high-speed processing can be performed.

Further, the timer processing is started by the data processors 6 and 8 at regular intervals, and the lock command IDs currently registered in the lock command ID tables 6a and 8a and the previous lock command ID tables 6b and 8b at the time of the previous investigation. The lock instruction table 7 is compared with the lock command ID registered in the lock control table 7 when the two match, or when the number of times they match is equal to or greater than a set value.
The content of a is read, and the lock command ID registered in the lock control table 7a is set to the lock command ID table 6a,
By deleting from 8a, the processing of the lock instruction for which the asynchronous report is lost can be continued as if the asynchronous report was received.

Therefore, even if a failure occurs in the data transfer control processing devices 3 and 4 located in the middle, the receiving side of the asynchronous report can continue the operation without contradiction, and the high speed processing can be performed.

Further, when the abnormal end report is received from the data processing processor 7, the timer is registered in the ID timer table 9b of the data processing processor 9 for each lock instruction ID and is started.
If the ID timer table 9b times out without receiving the asynchronous report from the device within a predetermined time, the data processor 9 reads the contents of the lock control table 7a from the data processor 7, and the contents are registered in the lock control table 7a. Lock command ID to lock command ID
By deleting from the table 9a, the processing of the lock instruction for which the asynchronous report is lost can be continued as if the asynchronous report was received.

Therefore, even if a failure occurs in the data transfer control processing devices 3 and 4 located in the middle, the receiving side of the asynchronous report can continue the operation without contradiction, and the high speed processing can be performed.

Furthermore, the timer processing is started in the data processors 10 and 11 at regular intervals, and the count value of the lock instruction ID currently registered in the lock instruction ID counting tables 10b and 11b and the previous lock instruction at the time of the previous investigation. ID
Lock command ID registered in the counting tables 10c and 11c
Of the lock control table 7a is read from the data processor 7 and registered in the lock control table 7a when they match or when the number of times they match exceeds a set value. The lock command IDs that are present are locked command ID tables 10a and 11a.
The lock instruction whose asynchronous report has been lost can continue to be processed as if the asynchronous report was received.

Therefore, even if a failure occurs in the data transfer control processing devices 3 and 4 located in the middle, the receiving side of the asynchronous report can continue the operation without contradiction, and the high speed processing can be performed.

Also, the timer processing is started in the data processing processors 13 and 15 at regular intervals, and the count value of the lock command ID received from the data processing processor 12 currently registered in the ID counting tables 13b and 15b and the previous investigation. At times, the count values of the lock command IDs registered in the previous ID counting tables 13c and 15c are compared with each other, and when they match or when the number of times they match exceeds a set value, the lock control tables 13a and 15a By issuing an asynchronous report C requesting confirmation of the contents to the data processor 12 and deleting the lock command IDs registered in the lock control tables 13a and 15a from the lock command ID table 12a, the lock in which the asynchronous report is lost Processing of the instruction may continue as if an asynchronous report had been received.

Therefore, even if a failure occurs in the data transfer control processing devices 3 and 4 located in the middle, the receiving side of the asynchronous report can continue the operation without contradiction, and the high speed processing can be performed.

Further, when the data processing processor 16 issues an asynchronous report, a timer is registered in the attention lock timer table 16b for each lock instruction ID and started, and the timer processing of the data processing processor 16 is started at fixed time intervals. When a time-out occurs due to the update of the contents of the attention lock timer table 16b in the above, an asynchronous report C requesting confirmation of the contents of the lock control table 16a corresponding to the lock instruction ID is issued to the data processor 12,
By deleting the lock command ID registered in the lock command ID table 12a from the lock command ID table 12a, the process of the lock command for which the asynchronous report is lost can be continued as if the asynchronous report was received.

Therefore, even if a failure occurs in the intermediate data transfer control processing devices 3 and 4, the receiving side of the asynchronous report can continue the operation without contradiction, and the high speed processing can be performed.

[0244]

As described above, according to the first non-stop information processing apparatus of the present invention, the lock instruction for instructing the second data processing processor to inhibit access to the target apparatus from the first data processing processor. Is output from the second data processor, an asynchronous report indicating that the lock instruction is registered in the lock control table is output.
When it is output to the data processor of the above, by determining whether or not the asynchronous report is for the same lock instruction, even if a failure occurs in the intermediate data transfer means, there is no contradiction on the receiving side of the asynchronous report. There is an effect that the operation can be continued and high-speed processing can be performed.

According to the second non-stop information processing apparatus of the present invention, when the first data processing processor outputs a lock command for instructing access inhibition to the target apparatus to the second data processing processor, The second is an asynchronous report indicating that the lock instruction is registered in the lock control table.
When the data processing processor of the above outputs to the first data processing processor, the lock instruction for which the asynchronous report is currently held is judged to have been held in the previous investigation. By reading the contents of the lock control table and executing the processing, even if a failure occurs in the data transfer means located in the middle, the operation can be continued on the receiving side of the asynchronous report without any contradiction, and high-speed processing can be performed. There is an effect that can be.

According to the third non-stop information processing apparatus of the present invention, when a lock instruction for instructing access inhibition to the target device is output from the first data processor to the second data processor, The second is an asynchronous report indicating that the lock instruction is registered in the lock control table.
To the first data processor of the non-stop information processing device that is output from the second data processor to the first data processor in response to the abnormal termination report from the second data processor in response to the lock instruction. Monitoring means for monitoring the reception of the asynchronous report for the lock command for a predetermined time, and when the monitoring means detects the non-reception of the asynchronous report at the predetermined time, the contents of the lock control table are read out and the lock command for which the asynchronous report is not received is received. By including means for performing asynchronous report reception processing, even if a failure occurs in the intermediate data transfer means, the asynchronous report reception side can continue operation consistently and high-speed processing can be performed. There is an effect.

According to the fourth non-stop information processing apparatus of the present invention, when the lock instruction for instructing the access inhibition to the target apparatus is output from the first data processor to the second data processor, The second is an asynchronous report indicating that the lock instruction is registered in the lock control table.
In the case where the data processing processor of 1 is output to the first data processing processor, the asynchronous report receiving process for the lock command for which it is determined that the current number of times of issuing the lock command is the same as the number of times of issuing the previous investigation is stored in the lock control table. By reading out and executing the content, even if a failure occurs in the data transfer means located in the middle, the receiving side of the asynchronous report can continue the operation without contradiction, and the high speed processing can be performed.

According to the fifth non-stop information processing apparatus of the present invention, when a lock instruction for instructing access inhibition to the target device is output from the first data processor to the second data processor, The second is an asynchronous report indicating that the lock instruction is registered in the lock control table.
When output from the first data processor to the first data processor, the request for confirmation of the contents of the lock control table is sent to the asynchronous report for the lock instruction which is determined that the current number of receptions of the lock instruction is the same as the number of receptions at the previous investigation. Request information to be output to the first data processor, and when the asynchronous report to which the request information is added is received, the contents of the lock control table are read and asynchronous to the lock command corresponding to the request information. By performing the report receiving process, even if a failure occurs in the intermediate data transfer means, the receiving side of the asynchronous report can continue the operation without contradiction, and high speed processing can be performed.

According to the sixth non-stop information processing apparatus of the present invention, when a lock instruction for instructing access inhibition to the target apparatus is output from the first data processor to the second data processor, The second is an asynchronous report indicating that the lock instruction is registered in the lock control table.
Monitoring means for monitoring the time after the asynchronous report is transmitted to the second data processor of the non-stop type information processing apparatus that is output from the first data processor to the first data processor, and the monitoring means. And a means for adding request information for requesting confirmation of the contents of the lock control table to the asynchronous report when detecting that a predetermined time has elapsed since the means transmitted the asynchronous report, and outputting the asynchronous report to the first data processor. The first data processor,
Data located in the middle by providing a means for reading the contents of the lock control table and receiving the asynchronous report for the lock command corresponding to the request information when the asynchronous report with the request information is received. Even if a failure occurs in the transfer means, there is an effect that the receiving side of the asynchronous report can continue the operation without contradiction and high-speed processing can be performed.

[Brief description of drawings]

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

2 is a diagram showing an asynchronous report output from the data processor of FIG. 1. FIG.

FIG. 3 is a flowchart showing a processing operation of the data processor of FIG.

FIG. 4 is a flowchart showing a processing operation of the data processor of FIG.

FIG. 5 is a block diagram showing a configuration of a second exemplary embodiment of the present invention.

6 is a flowchart showing a processing operation of the data processor of FIG.

FIG. 7 is a flowchart showing a processing operation of the data processor of FIG.

FIG. 8 is a block diagram showing a configuration of a third exemplary embodiment of the present invention.

9 is a flowchart showing a processing operation of the data processor of FIG. 8. FIG.

FIG. 10 is a block diagram showing a configuration of a fourth exemplary embodiment of the present invention.

11 is a flowchart showing a processing operation of the data processor of FIG.

12 is a flowchart showing a processing operation of the data processor of FIG.

FIG. 13 is a block diagram showing a configuration of a fifth exemplary embodiment of the present invention.

FIG. 14 is a flowchart showing a processing operation of the data processor of FIG.

15 is a flowchart showing the processing operation of the data processor of FIG.

FIG. 16 is a block diagram showing a configuration of a sixth exemplary embodiment of the present invention.

17 is a flowchart showing the processing operation of the data processor of FIG.

FIG. 18 is a block diagram showing a configuration of a seventh exemplary embodiment of the present invention.

19 is a diagram showing an asynchronous report output from the data processor of FIG. 18. FIG.

20 is a flowchart showing a processing operation of the data processor of FIG. 18. FIG.

21 is a flowchart showing the processing operation of the data processor of FIG. 18. FIG.

FIG. 22 is a block diagram showing a configuration of an eighth exemplary embodiment of the present invention.

23 is a flowchart showing a processing operation of the data processor of FIG. 22. FIG.

FIG. 24 is a block diagram showing a configuration of a ninth exemplary embodiment of the present invention.

FIG. 25 is a flowchart showing a processing operation of the data processor of FIG. 24.

FIG. 26 is a flowchart showing a processing operation of the data processor of FIG. 24.

FIG. 27 is a flowchart showing a processing operation of the data processor of FIG. 24.

FIG. 28 is a block diagram showing a configuration of a conventional example.

29A is a diagram showing a lock instruction output from the data processor of FIG. 28, and FIG. 29B is a diagram showing an asynchronous report output from the data processor of FIG.
FIG. 29C is a diagram showing a normal termination report output from the data processing processor of FIG. 28, and FIG. 29D is a diagram showing an abnormal termination report output from the data processing processor of FIG. 28.

30 is a flowchart showing the processing operation of the data processor of FIG. 28. FIG.

31 is a flowchart showing the processing operation of the data processor of FIG. 28. FIG.

32 is a flowchart showing the processing operation of the data processor of FIG. 28. FIG.

33 is a flowchart showing the processing operation of the data processor of FIG. 28. FIG.

34 is a flowchart showing the processing operation of the data processor of FIG. 28. FIG.

[Explanation of symbols]

1, 2, 6 to 13, 15, 16 Data processor 1b ID counting reception table 2a, 7a, 13a, 15a, 16a Lock control table 2b, 13b, 15b ID counting table 5b, 14b Lock instruction ID 5c ID counting 6b, 8b Pre-lock command ID table 8c ID hold count table 9b ID timer table 10b, 11b Lock command ID counting table 10c, 11c Pre-lock command ID counting table 11d, 15d ID matching count table 13c, 15c Pre-ID counting table 16b Attention lock timer table

Claims (13)

[Claims] 1. A first and a second data processor, and a first and a second data transfer control processor for connecting the first and second data processors,
An asynchronous report indicating that the lock instruction is registered in the lock control table is output when the lock instruction for instructing access inhibition to the target device is output from the first data processor to the second data processor. When output from the second data processor to the first data processor, even if a failure occurs in one of the first and second data transfer control processing devices, the other is used to output the first and second data transfer control processing devices. A non-stop type information processing device for continuing data transfer between second data processors, characterized in that the non-stop type information processing device includes a judging means for judging whether or not the asynchronous report is for the same lock instruction. Type information processing device. 2. The determination means is provided in the second data processor, and counts the number of times a lock command is issued corresponding to each piece of identification information for identifying each lock command, and the second means. Means for providing the asynchronous report with the identification information corresponding to the asynchronous report and the count value of the counting means corresponding to the identification information, which is provided in the data processing processor when the asynchronous report is transmitted; A storage unit provided in the data processing processor for storing the identification information and the count value assigned to the asynchronous report in association with each other, and a storage unit provided in the first data processing processor and assigned to the asynchronous report. Comparing means for comparing the count value with the content of the storing means corresponding to the identification information of the count value, and the comparing means provided in the first data processor. 2. The non-stop information processing apparatus according to claim 1, further comprising: a unit that performs a process of receiving the asynchronous report when a mismatch is detected in 1. 3. A first and a second data processing processor, and a first and a second data transfer control processing device connecting the first and second data processing processors,
An asynchronous report indicating that the lock instruction is registered in the lock control table is output when the lock instruction for instructing access inhibition to the target device is output from the first data processor to the second data processor. When output from the second data processor to the first data processor, even if a failure occurs in one of the first and second data transfer control processing devices, the other is used to output the first and second data transfer control processing devices. A non-stop information processing device for continuing data transfer between second data processors, wherein whether or not the lock instruction for which the asynchronous report is currently suspended was suspended during the previous investigation And a non-synchronous report for the lock command for which the above-mentioned non-synchronous report was judged to be pending at the time of the previous investigation. The reception processing, fault tolerant data processing apparatus characterized by comprising means for executing the content of the lock control table reads. 4. The holding means, which is provided in the first data processor, holds holding information for identifying a lock instruction for which the asynchronous report was suspended at the time of the previous investigation, and the first data. Provided in the processor
Comparing means for comparing the content of the holding means with the identification information of the lock instruction for which the asynchronous report is currently suspended;
Means provided in the first data processor for determining that the lock instruction for which the asynchronous report is currently held when the match is detected by the comparison means is that the asynchronous report was held for the previous investigation. The non-stop information processing apparatus according to claim 3, wherein the non-stop information processing apparatus comprises: 5. The holding means, which is provided in the first data processor, holds the identification information of a lock instruction for which the asynchronous report was suspended at the time of the previous investigation, and the first data. Provided in the processor
Comparing means for comparing the content of the holding means with the identification information of the lock instruction for which the asynchronous report is currently suspended;
Counting means provided in the first data processor for counting the number of times a match is detected by the comparing means, and the asynchronous report when the count value of the counting means reaches a preset predetermined value. 4. The non-stop information processing apparatus according to claim 3, further comprising means for determining that the currently held lock command is that the asynchronous report was held at the time of the previous investigation. 6. A first and a second data processing processor, and a first and a second data transfer control processing device connecting the first and second data processing processors,
An asynchronous report indicating that the lock instruction is registered in the lock control table is output when the lock instruction for instructing access inhibition to the target device is output from the first data processor to the second data processor. When output from the second data processor to the first data processor, even if a failure occurs in one of the first and second data transfer control processing devices, the other is used to output the first and second data transfer control processing devices. A non-stop information processing device for continuing data transfer between second data processors, wherein the first data processor is responsive to an abnormal termination report from the second data processor in response to the lock instruction. And a monitoring means for monitoring the reception of the asynchronous report for the lock command for a predetermined time, and the monitoring means at the predetermined time. A non-stop type, characterized in that when the non-reception of the asynchronous report is detected, the content of the lock control table is read to perform the reception processing of the asynchronous report for the lock command for which the asynchronous report is not received Information processing equipment. 7. A first and a second data processor, and a first and a second data transfer control processor for connecting the first and second data processors,
An asynchronous report indicating that the lock instruction is registered in the lock control table is output when the lock instruction for instructing access inhibition to the target device is output from the first data processor to the second data processor. When output from the second data processor to the first data processor, even if a failure occurs in one of the first and second data transfer control processing devices, the other is used to output the first and second data transfer control processing devices. A non-stop information processing device for continuing data transfer between second data processors, wherein the determination means determines whether or not the current number of times a lock command is issued is the same as the number of times the lock command was issued at the previous investigation. The process of receiving the asynchronous report for the lock command, which the judgment means judges to be the same as the number of issuances at the time of the previous investigation, is executed by reading the contents of the lock control table. Fault tolerant data processing apparatus characterized by comprising: means for. 8. The determining means is provided in the first data processing processor, and is provided in the first data processing processor and counting means for counting the number of times the lock instruction is issued, and the determining means is provided in the first data processing processor. Holding means for holding the number of times the lock command is issued, comparison means provided in the first data processor for comparing the count value of the counting means with the contents of the holding means, and the first data processor. 8. The stop type information processing apparatus according to claim 7, further comprising means for determining that the number of issuances is the same as the number of issuances at the time of the previous investigation, when the coincidence is detected by the comparing means. 9. The determination means is provided in the first data processing processor, is provided in the first data processing processor for counting the number of times the lock instruction is issued, and is provided in the first data processing processor, and the previous survey is performed. Holding means for holding the number of times the lock command is issued, and comparison means provided in the first data processor for comparing the count value of the first counting means with the contents of the holding means. Second counting means provided in the first data processing processor for counting the number of times the comparison means detects a match, and a count value of the second counting means provided in the first data processing processor. 8. The non-stop type information processing apparatus according to claim 7, further comprising means for determining that the same as the number of times of issuance at the time of the previous survey when is a predetermined value. 10. A first and a second data processor, and a first and a second data transfer control processor for connecting the first and second data processors,
An asynchronous report indicating that the lock instruction is registered in the lock control table is output when the lock instruction for instructing access inhibition to the target device is output from the first data processor to the second data processor. When output from the second data processor to the first data processor, even if a failure occurs in one of the first and second data transfer control processing devices, the other is used to output the first and second data transfer control processing devices. A non-stop information processing device for continuing data transfer between second data processors, comprising: a judging means for judging whether or not the current number of receptions of the lock command is the same as the number of receptions at the time of the previous investigation; Request information for requesting confirmation of the contents of the lock control table is sent to the asynchronous report for the lock command that the judging means judges to be the same as the number of receptions at the time of the previous investigation. A means for giving and outputting the request, and a means for receiving the asynchronous report to which the request information is added, reading the contents of the lock control table, and performing an asynchronous report receiving process for the lock command corresponding to the request information. A non-stop information processing device comprising: 11. The determination means is provided in the second data processing processor, and is provided in the second data processing processor, and counting means for counting the number of times the lock command is received, and the determination means at the time of the previous investigation. Holding means for holding the number of times the lock command is received, comparison means provided in the second data processor for comparing the count value of the counting means with the contents of the holding means, and the second data processor. 11. The non-stop type information processing apparatus according to claim 10, further comprising means for determining that the number of receptions is the same as the number of receptions at the time of the previous investigation when the comparison means detects a match. 12. The determination means is provided in the second data processing processor, and is provided in the second counting processor and the first counting means for counting the number of times the lock command is received. Holding means for holding the number of times the lock command is received, and comparison means provided in the second data processor for comparing the count value of the first counting means with the content of the holding means. Second counting means provided in a second data processing processor, for counting the number of times a match is detected by the comparing means;
11. The non-stop information processing according to claim 10, further comprising means for determining that the count value of the counting means is equal to the number of receptions at the previous survey when the count value reaches a preset predetermined value. apparatus. 13. A first and a second data processor, and a first and a second data transfer control processor for connecting the first and second data processors,
An asynchronous report indicating that the lock instruction is registered in the lock control table is output when the lock instruction for instructing access inhibition to the target device is output from the first data processor to the second data processor. When output from the second data processor to the first data processor, even if a failure occurs in one of the first and second data transfer control processing devices, the other is used to output the first and second data transfer control processing devices. A non-stop information processing device for continuing data transfer between second data processing processors, comprising: a monitoring means for monitoring a time period after transmitting the asynchronous report to the second data processing processor; The content of the lock control table in the asynchronous report when the monitoring means detects that a predetermined time has elapsed since the asynchronous report was transmitted. Means for adding request information for requesting confirmation and outputting to the first data processing processor, wherein the first data processing processor receives the asynchronous report with the request information. A non-stop type information processing apparatus comprising means for reading the contents of a lock control table and performing an asynchronous report reception process for a lock command corresponding to the request information.