JPH052504A - Dummy fault display system - Google Patents

Abstract

PURPOSE:To add a message indicating the existence of a fault generated by a false fault to a fault log and to make it possible to specify whether the leg due to the dummy fault is to be sampled or not. CONSTITUTION:This dummy fault display system is constituted of a fault detecting circuit 1, a dummy fault generating circuit 2, an error display flag 100, a dummy fault status flag 200, and a log suppressing flag 300, and in the case of executing a dummy fault test by a test program, a message indicating the existence of a fault generated due to a dummy fault is added to a fault information log. Whether the fault information log based due to the dummy fault is to be sampled or not can be specified.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a pseudo fault display system, and more particularly to hardware fault information.

[0002]

2. Description of the Related Art Conventionally, when a pseudo fault occurs, the cable is shredded or shorted asynchronously from the outside of the device, or a pseudo fault is generated by a dedicated pseudo fault generating circuit to check the operation of the fault processing function of the device. Was going on.

In a test program, when a pseudo fault generating circuit is used to automatically evaluate the operation of the fault processing function of the apparatus, the service processor collects all hardware fault information (HW log) each time the pseudo fault is evaluated. It was

[0004]

In this conventional pseudo fault evaluation method, every HW log is collected by the service processor every time a pseudo fault occurs, so that the HW log file in the service processor is full. However, there is a problem in that the HW log cannot distinguish the failure caused by the pseudo failure from the failure caused by the real failure.

[0005]

The pseudo fault display system of the present invention has a pseudo fault state flag indicating a pseudo fault evaluation state and a software instruction for unsetting the flag, and collects fault information of hardware. It has a log collection deterrence flag indicating whether or not and a software instruction set for setting / clearing the flag, and only when the pseudo obstacle state flag is set,
When the HW log is collected when the pseudo failure occurrence instruction is executable and the log collection suppression flag is not set, when the HW log is collected and when the pseudo failure status flag is set The time-series log and the status log have a service processor that displays a message indicating that a failure has occurred due to a pseudo failure occurrence instruction.

[0006]

The present invention will be described below with reference to the drawings.

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

The fault detection circuit 1 is a circuit for detecting a device failure, and outputs an error signal ERR via a signal line 101.

The pseudo fault generating circuit 2 is a circuit for outputting a pseudo fault trigger ET through the signal line 102 when the pseudo fault generating instruction is executed. When the false trigger ET is output, the fault detection circuit determines that the device has failed, and the error signal ER
Output R.

The error display flag 10 is a flag that is set by the error signal ERR when a failure is detected by the failure detection circuit 1, and notifies the outside that the apparatus is in failure through the signal line 100. The signal held by the error display flag 10 is an error signal EIF, which is a signal which, once set, does not disappear until the device is reset.

The pseudo obstacle state flag 20 is a flag indicating a pseudo obstacle evaluation state, which is set by a pseudo obstacle state setting instruction and reset by a pseudo obstacle releasing instruction.
The signal MNT held by the false state flag 20 is the signal line 20.
It is output via 0.

The pseudo fault occurrence instruction can be executed only when MNT = 1.

The log inhibition flag 30 is a flag indicating whether or not the service processor collects the HW log of the device when a failure occurs. L held by the log suppression flag 30
The I signal is output via the signal line 300. The log suppression flag 30 is set by the execution of the log suppression setting instruction and reset by the execution of the log suppression cancellation instruction.
When a failure occurs and the log suppression flag 30 is LI = 1, the machine check failure processing operation is performed as usual, but the service processor does not collect HW information only (time series log and status log). To SVP
(Do not register to File in (Service Processor)).

FIG. 2 is a diagram showing command word formats of a software instruction for setting / releasing the pseudo failure state flag 20 and the log inhibition flag 30 and a software instruction for generating a pseudo failure.

The operation code is bit 0 of the instruction word.
-7, which is 88 (hexadecimal) in common with all 5 instructions. The operation is determined by the auxiliary code (bits 8-15 of the instruction word). When the auxiliary code is 01 (hexadecimal), the pseudo obstacle state setting command sets the pseudo obstacle state flag 20. When the auxiliary code is 00 (hex)
The false state flag 20 is reset. Auxiliary code is 03
When (hexadecimal), the log inhibition flag 30 is set by the log inhibition setting command. When the auxiliary code is 02 (hexadecimal), the log suppression flag 30 is reset by a log suppression cancellation command. When the auxiliary code is 04 (hexadecimal), it is a pseudo failure occurrence instruction, and can be executed when the pseudo failure state flag 20 is 1.
In this instruction, bits 16-31 of the instruction word can specify a false obstacle point (a place where the false obstacle is generated). Execution of this instruction can cause a pseudo failure in the device.

FIG. 3 is a flow chart of a microprogram corresponding to an operation code (OP code) 88 instruction.

The microprogram corresponding to the OP code 88 instruction is activated. The microprogram determines the value of the auxiliary code in bits 8-15 of the instruction word.

When the auxiliary code is 00, the false obstacle state flag 2
Reset 0.

When the auxiliary code is 01, the false obstacle state flag 2
Set to 0.

When the auxiliary code is 02, the log suppression flag 3
Reset 0.

When the auxiliary code is 03, the log suppression flag 3
Set to 0.

When the auxiliary code is not 00-03, it is recognized that the auxiliary code is 09. At this time, when the false obstacle state flag 20 is 0, the operation becomes an exception. 1
When, the pseudo obstacle is generated for the designated pseudo obstacle point.

FIG. 4 shows H of the service processor (SVP).
It is a flowchart of a W log collection program. An HW failure occurs in the device and the log collection routine is activated.

The log collection routine refers to the log inhibition flag 30. If the log suppression flag 30 is 1, the operation ends without doing anything.

If the log inhibition flag 30 is 0, the HW log information is collected. Next, referring to the pseudo failure state flag 20, if it is 1, a message that is a log generated by the pseudo failure is added to the time series log and the status log. If it is 0, it is recognized as a real obstacle. Next, the time series log and the status log are registered in the log file in the fixed disk of SVP.

[0026]

As described above, according to the present invention, whether or not the failure log is a real failure is determined by the pseudo failure evaluation by performing the pseudo failure test only when the pseudo failure flag is set. The result is that maintenance personnel do not have to be confused when examining the failure log.

In addition, when performing the pseudo failure evaluation, it is possible to specify whether or not to collect the failure log when the test program is executed, so that the maintenance staff may be confused by the unnecessary log or the log Fil.
It has the result that it can be prevented from filling up e.

[Brief description of drawings]

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

[Fig. 2] Command word format of software command

FIG. 3 is a flowchart of a microprogram corresponding to software instructions.

FIG. 4 is a flowchart of a service processor log collection program.

[Explanation of symbols]

1 Fault detection circuit 2 Pseudo fault generation circuit 10 Error display flag 20 False status flag 30 log suppression flag 100-102, 200, 300 signal line

Claims (5)

[Claims] 1. A software instruction set having a pseudo obstacle state flag indicating a pseudo obstacle evaluation state in a pseudo obstacle display method for automatically evaluating a fault processing function of an apparatus by a test program, and setting and canceling the pseudo obstacle state flag. A pseudo fault display method characterized by having. 2. The pseudo failure display method according to claim 1, further comprising a log collection suppression flag indicating whether or not to collect hardware failure information when a pseudo failure occurs, and the log collection suppression is provided. A pseudo fault indication method having a software instruction set for setting and clearing a flag. 3. The pseudo fault display system according to claim 1, further comprising a pseudo fault generation instruction which can be executed only when the pseudo fault state flag is set. 4. The pseudo failure display method according to claim 1, wherein when a pseudo hardware failure occurs during execution of the pseudo failure occurrence instruction, the log collection suppression flag is not set. A pseudo fault display method in which a service processor collects hardware failure information and the service processor does not collect hardware failure information when the log collection suppression flag is set. 5. The pseudo failure display method according to claim 1, 2, 3 or 4, wherein when the service processor collects hardware failure information and the pseudo failure status flag is set, a time series log and Pseudo-fault display method, which displays a message in the status log indicating that a pseudo fault has occurred due to a pseudo-fault instruction.