JPH04330548A - Information processing system - Google Patents

Abstract

PURPOSE:To detect the connection error before operation by receiving a device name set command and normally terminating the device name set command in the case of indication of setting of the same device name whether it is not set yet or is already set but abnormally terminating it in the case of indication of a different device name. CONSTITUTION:A central processing unit 1 provided with a program 4 and input/output ports 11 to 14, peripheral controllers 31 and 32 of the same type, and input/output interface busses 21 to 24 which connect peripheral controllers 31 and 32 to the central processing unit 1 are provided. In this case, the device name set command is used by the program 4 to indicate setting of the device name to peripheral controllers 31 and 32 from all input/output interface busses 21 to 24. When peripheral controllers 31 and 32 receive the device name set command, they normally terminate it in the case of indication of setting of the same device name whether it is not set yet or is already set, but they abnormally terminate it in the case of indication of setting of a different device name. After normal termination of the first command, the program 4 issues the device name set command to a next input/output port 12.

Description

[Detailed description of the invention]

0001

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to an information processing system, and in particular to a plurality of peripheral control devices and a plurality of input/output interfaces connecting each of the peripheral control devices to a central processing unit.
The present invention relates to an information processing system that has a plurality of input/output interface buses and is configured to check whether peripheral control devices are correctly connected to the plurality of input/output interface buses.

0002

[Background Art] For the purpose of load distribution and reliability improvement,
A so-called cross-call connection, in which multiple input/output interface buses are provided between a central processing unit and a peripheral control unit, has traditionally been used, but the cables that constitute the input/output interface buses have to be connected manually. Whether or not the cable is correctly connected from the intended port on the central processing unit side to the intended peripheral control device is determined by a test in which input/output commands are issued to the peripheral control device.

0003

[Problem to be Solved by the Invention] However, although this method can test whether the cable is physically correctly connected to the peripheral control device, it cannot be confirmed whether the cable is connected to the intended peripheral control device. In an information processing system where multiple peripheral control devices of the same type are connected, even if you connect them as shown in Figure 1 with the intention of connecting them as shown in Figure 2, you will not realize the mistake until you actually start using the system. There were times when it happened.

0004

Means for Solving the Problems The present invention provides a central processing unit, a plurality of peripheral control devices, and a plurality of input/output interfaces that connect each of the peripheral control devices to the central processing unit.
In the information processing system, the central processing unit sequentially uses each of the plurality of input/output interface buses for each of the peripheral control devices to identify peripheral control devices uniquely named in the system. means for outputting a device name setting command for instructing the peripheral control device to set a logical name for the peripheral control device, and, if a device name mismatch is reported from the peripheral control device as a result, displaying the fact. , when the device name setting command is input, the peripheral control device stores the device name attached to the command if the device name has not been set, and the central processing unit determines that the command has been successfully completed. If it has already been set, compare the stored device name with the device name sent by the command, and if they match, report normal completion, and if they do not match, "device name mismatch". It is characterized by having a means for reporting abnormal termination.

[0005]

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

FIG. 1 is a block diagram of one embodiment of the present invention. This information processing system includes a central processing unit 1 having a program 4 and input/output ports 11 to 14, peripheral control devices 31 and 32 of exactly the same type, and a peripheral control device 3.
1 and 32 to the central processing unit 1.

In the system of this embodiment, it is assumed that the peripheral control devices are individually identified by giving logical names, and here, the peripheral control device 31 is named MS01, and the peripheral control device 32 is named MS02. .

Now, in this example, it is assumed that the configuration as shown in FIG. 2 was originally intended. That is, the input/output ports 11 and 12 on the central processing unit side are connected to the peripheral control device 31, and the input/output ports 13 and 14 are connected to the peripheral control device 31.
The intention was to connect it to the peripheral control device 32. The components previously provided in the system are therefore those of FIG.

Suppose that a connection error is made as shown in FIG. Since the physical connection is correct and both peripheral control devices 31 and 32 are of the same type, the conventional method of simply checking the physical connection is to check the input/output specific to the peripheral control device. Even if you use a command, incorrect connection of the input/output interface bus cannot be detected.

Therefore, in this embodiment, a program 4 for detecting such mistakes is prepared. FIG. 4 shows the processing flow of program 4. The program 4 sequentially issues device name setting commands to all input/output interface buses based on previously existing system configuration information (FIG. 3). First, input/output port 11
A device name setting command that specifies "MS01" is issued using . This is received by the peripheral control device 31. Since the peripheral control device 31 has no device name set at that point, it accepts this command, sets the device name "MS01" in its own appropriate storage area, and normally terminates the command.

When the first command ends normally, the program 4 issues a device name setting command to the next input/output port 12. At this time as well, according to the configuration information in FIG. 3, the device name to be set is "MS01". However, the input/output port 12 is connected to the peripheral control device 32. Since the peripheral control device 32 has no device name set at this point, it accepts this command, sets the device name "MS01" in its own appropriate area, and normally terminates the command.

When the second command is successfully completed, the program 4 issues a device name setting command to the next input/output port 13. At this time, according to the configuration information shown in FIG. 3, the device name to be set is "MS02". However, the input/output port 13 is connected to the peripheral control device 31. The device name "MS01" has already been set in the peripheral control device 31. Therefore, the peripheral control device 31 compares the already set "MS01" with "MS02" that has just been received in the device name setting command, and since they are not the same, it abnormally terminates this command. At this time, it is also reported to the program 4 that the already set device name is "MS01".

[0013] When the third device name setting command terminates abnormally, program 4 stores the port number when the command was issued, the device name that was attempted to be set, and the already set device reported by the peripheral control device. Display an error message containing the name.

Next, the program 4 issues a device name setting command to the next input/output port 14. At this time, according to the configuration information in Figure 3, the device name to be set is “MS02
". The input/output port 14 is connected correctly, but the device name "MS01" is already set in the peripheral control device 32. Therefore, the peripheral control device 32 uses the already set "MS01" and the device name "MS01". It compares it with "MS02" that was just received with the device name setting command, and since they are not the same, the command is abnormally terminated.At this time, it is also reported to the program 4 that the already set device name is "MS01."

When the fourth device name setting command terminates abnormally, program 4 stores the port number when the command was issued, the device name that was attempted to be set, and the already set device reported by the peripheral control device. Display an error message containing the name.

In this embodiment, the configuration of the peripheral control device is as described above, so the program ends here.

As a result of program execution, the following error message is displayed, for example.

ILLIGAL PATH CONNECTION
PORT#3 REQ=MSO2 RES=
MSO1 ILLIGAL PATH CONNEC
TION PORT#3 REQ=MSO2
RES=MSO1 ILLIGAL PATH CO
NNECTION PORT#4 REQ=MS
O2 RES=MSO1 Here, REQ= indicates the device name to be set using the device name setting command, and RES= indicates the actually set device name. This message indicates that there is a connection error in the input/output interface bus between MS01 and MS02.

[0019]

[Effects of the Invention] As explained above, the present invention provides a program that instructs a peripheral control device to set a device name from all input/output interface buses using a device name setting command, and a program that uses a device name setting command to set a device name. By configuring the peripheral control device with a peripheral control device that terminates normally if the same device name is specified and terminates abnormally if the device name is different, each peripheral control device can have multiple inputs. When connecting an output interface bus, it is possible to quickly detect a connection error before the system starts operating.

[Brief explanation of the drawing]

FIG. 1 is a configuration diagram of an embodiment of the present invention.

FIG. 2 is a configuration diagram of an embodiment of the present invention.

FIG. 3 is a diagram showing configuration information in the same embodiment.

FIG. 4 is a flow diagram showing the processing of the program in FIG. 1;

[Explanation of symbols]

1 Central processing unit 4 Program 11 Input/output port 12 Input/output port 13 Input/output port 14 Input/output port 21 Input/output interface bus 22 Input/output interface bus 23 Input/output interface bus 24 Input/output interface bus 31
Peripheral control device 32 Peripheral control device

Claims (1)

[Claims] 1. An information processing system comprising a central processing unit, a plurality of peripheral control devices, and a plurality of input/output interface buses connecting each of the peripheral control devices to the central processing unit, wherein the central processing unit The device sequentially uses each of the plurality of input/output interface buses for each peripheral control device to instruct the peripheral control device to set a logical name for the peripheral control device that is uniquely named in the system. means for outputting a device name setting command to output a device name setting command, and, if a peripheral control device reports a device name mismatch as a result, displaying a notification to that effect, the peripheral control device outputs a device name setting command to When input, if the device name has not been set, it stores the device name attached to the command and reports to the central processing unit that the command has completed normally, and if it has already been set, it remembers the device name attached to the command. The device name sent by the command is compared with the device name sent by the command, and if they match, a normal termination is reported, and if they do not match, an abnormal termination of "device name mismatch" is reported. information processing system.