JP2994258B2 - Message error check device - Google Patents

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a message error checking device, and more particularly to a message error checking device for checking the validity of a system message of an arbitrary computer system in a network having a plurality of computer systems.

[0002]

2. Description of the Related Art Heretofore, this type of system message error check is performed by a system administrator of an error check target computer based on experience and knowledge or a technical manual such as a manual. Operation was specified. In order to obtain a system message, a remote connection to an error check target computer and a complicated system message acquisition command are required.

In addition, a normal message and an abnormal message are mixedly output as system messages, and different system messages are output due to differences in the configuration of the computer. The operation and maintenance personnel output this system message to the printer, and refer to the experience and knowledge of the operation and maintenance personnel or a technical book such as a manual to determine whether the operation is normal or abnormal.

[0004]

In this conventional system message error check, remote connection to a computer device, input of a specific command, and knowledge of a message different for each computer depend on the skill of an operation and maintenance person. The time required for judgment often increases.
In addition, it is not rare that an abnormality is overlooked or the result of the determination is incorrect.

An object of the present invention is to provide a message error check device which realizes a highly reliable system operation by distinguishing each computer system and checking the validity of a system message in order to solve the above problems. To provide.

[0006]

A message error checking device according to the present invention is connected to a network to which a plurality of computer systems are connected, and includes a common message database storing system messages common to the plurality of computer systems. A unique message database storing a system message unique to the computer system, acquiring a system message of any computer system among the plurality of computer systems, and acquiring a system message of the common message database. Among them, an error message that does not match the system message of the arbitrary computer system is regarded as an error message. Configured so as to illegal messages which do not match the serial unique message database system messages.

Further, a message error checking device of the present invention is a message error checking device connected to a network including a plurality of computer systems, wherein the message acquiring device captures a system message of any one of the plurality of computer systems. A common message checking unit that sets an error message that does not match the system message of the arbitrary computer system among the system messages common to the plurality of computer systems; unique message to those do not match the unique <br/> system messages to each of the plurality of computer systems and those that do not match with the common system messages and bad message And over di checking unit is configured by an output unit that creates a list of the error messages and the illegal message.

Further, in the message error checking device according to the present invention, the message acquisition unit creates a system message file storing a system message of an arbitrary computer system, and the common message check unit reads the system message file and reads the system message file. An error message file is created by storing the extracted error message with reference to the system message, and the unique message check unit reads the system message file and extracts by referring to the common system message and the unique system message. The output unit reads the error message file and the invalid message file and creates the list.

Further, in the message error checking device according to the present invention, the common system message forms a common message database, and the unique system message forms a unique message database.

That is, the message error checking device of the present invention includes a means for remotely connecting to an error check target computer to obtain a system message, a database checking means for automatically checking whether the system message is a normal message or an invalid message, And a result printing means for printing the result of the check.

[0011]

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

FIG. 1 is a block diagram showing an embodiment of the present invention. Referring to FIG. 1, a message error checking device 1 of the present invention includes a message acquisition unit 11 that captures a system message of an arbitrary computer system among a plurality of computer systems 3, and a message acquisition unit 11 among the system messages common to the plurality of computer systems. A common message checker 12 that sets an error message that does not match a system message of an arbitrary computer system; and a system message of the arbitrary computer system that does not match a system message unique to each of the plurality of computer systems. and a unique message checking unit 13, unauthorized message that does not match with the common system messages, an output unit 14 for creating a list of the error messages and the bad message Having.

Here, the message error check device 1 is connected to each of the computer systems 3a,
3b,...

The above-mentioned common system messages are stored in the common message database 21, and the unique system messages are stored in the unique message database 22.
Is stored in

Further, the message acquiring unit 11 creates a system message file 31 storing a system message of an arbitrary computer system, and the common message checking unit 12 reads the system message file 31 and refers to the common system message. An error message file 32 is created by storing the extracted error message, and the unique message check unit 13 reads the system message file 31 and refers to the common system message and the unique system message to extract the illegal message. The output unit 14 reads the error message file 32 and the invalid message file 33 and creates a list of the error message file 32 and the invalid message file 33. Print.

FIG. 2 is an explanatory diagram showing message divisions. In the figure, a system message taken into the system message file 31 is a normal system message if it is the same as that stored in the common message database 21 or the unique message database 22, respectively. Therefore, a message that does not exist in any database is regarded as an invalid message.

An error message that does not exist in the system message file 31 in the common message database 21 is defined as an error message. In addition, a unique message
Those that do not exist in the system message file 31 in the database 22 are unique system messages of other computer systems, and are therefore treated as normal messages. That is, not all system messages existing in the unique message database 22 are included in the system message file 31.

The contents of the common message database 21 are normal message data that must be output in a system message in common to each computer. If this message has not been output, it is a message for determining that an abnormal operation is being performed.

FIG. 3 is an explanatory diagram exemplifying the correspondence of the above various messages. In the figure, the system message 31a of the computer 3a is stored in the common message database 21 with the message "Uuuu".
(An error that does not exist as a message
Error message) does not exist in the system message 31a, writes the error message file 32 as an error message.

In addition, "a" in the system message 31a
"aa" and "bbbbbb" (both computer systems
Since an invalid message that does not exist in the system 3 does not exist in the common message database 21 or the unique message database 22, it is written in the invalid message file 33 as an invalid message.

Note that "Kukukukuku" and "Kekekekekeke" (both in the
Although the normal system message of the computer 3b does not exist in the system message 31a, it is a message of another computer system, and thus does not correspond to an error message or an invalid message. Also message
"Oh oh oh" and "Okay" are both normal
Is a common system message,
And “Kikiki Kiki” are both normal computers 3
a is a system message.

FIG. 4 is a flowchart showing the operation of the message acquisition unit 11. In the figure, in the selection of an error check target computer device (41), a list of error check target computers is displayed, the operator selects and recognizes the selected target computer.

In the connection (42) to the computer to be subjected to the error check, a predefined connection command is automatically issued to the selected computer.

System message download (43)
Then, a command predefined in order to download a system message is automatically issued. Then, the download is executed and the system message file 31
Create

At the end of download (44), it is automatically determined whether the download has been completed. If the download has been completed, the process proceeds to the next process. If not, continue the download.

In disconnecting the computer device subject to the error check (45), a command predefined in advance for disconnecting from the computer is automatically issued.

FIG. 5 is a flowchart showing the operation of the common message check unit 12. In the figure, first, it is checked whether or not unread data exists in the common message database 21 (51).

If it is not read, one line is read from the database 21 (52), and it is searched whether it exists in the system message file 31 (53, 54). If so, the computer determines that a normal system message to be output has been output. If not, it is determined that a normal system message to be output has not been output, and an error message file 32 is generated (55). This process is executed for all rows of the common message database 21.

FIG. 6 is a flowchart showing the operation of the unique message check unit 13. In the figure, first, it is checked whether there is any unprocessed system message in the system message file 31 (61).

When there is, the system message is set to 1
The line is read (62), and it is searched whether it exists in the common message database 21 or the unique message database 22 (63, 64). If it exists, it is determined that a normal system message has been output. If it does not exist, it is written as an invalid message in the invalid message file 33 (65). This process is executed for all system messages in the system message file 31.

FIG. 7 is a flowchart showing the operation of the output unit 14. In the figure, heading printing (71) prints the name of the target computer device that has been subjected to the error check.

If there is an error file (72), it is checked whether or not there is an error message in the error message file 32. If there is a message, the error message file 32 is printed as a normal message that has not been output (74). If there is no message, it can be determined that all the messages to be output exist, so that "all the messages to be output existed" is printed (73).

Further, in the presence or absence of an invalid message file (75), it is checked whether or not there is an invalid message in the invalid message file 33. If there is a message, the unauthorized message file 33 is printed as an unauthorized message (77). If there is no message,
Since it can be determined that there is no illegal message, "illegal message does not exist" is printed (76).

[0034]

As described in detail above, the message error check device of the present invention can verify a system message output from a specific computer system by referring to a system message database. There is no need to rely on the experience and abilities of the personnel in charge as in. Therefore, the normality of the system message can be determined in a short time, and the reliability of the system operation can be improved.

[Brief description of the drawings]

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

FIG. 2 is an explanatory diagram showing message divisions.

FIG. 3 is an explanatory diagram exemplifying correspondence of various messages;

FIG. 4 is a flowchart showing processing of a message acquisition unit.

FIG. 5 is a flowchart showing processing of a common message check unit.

FIG. 6 is a flowchart showing processing of a unique message check unit.

FIG. 7 is a flowchart showing processing of an output unit.

[Explanation of symbols]

DESCRIPTION OF SYMBOLS 1 Message error check device 2 Printer 3 Computer system 4 Network 11 Message acquisition unit 12 Common message check unit 13 Unique message check unit 14 Output unit 21 Common message database 22 Unique message database 31 System message file 32 Error message file 33 Invalid message file

Claims (4)

(57) [Claims] 1. A common message database which is connected to a network to which a plurality of computer systems are connected and stores a system message common to the plurality of computer systems, and a unique message which stores a system message unique to each computer system. a system database for acquiring a system message of any computer system of the plurality of computer systems, and a system message of the common message database that does not match a system message of the arbitrary computer system. It was an error message, among the system message of the arbitrary computer system, consistent with the common message database and system messages of the specific message database Message error check device, characterized in that a bad message having no. 2. A message error check device connected to a network including a plurality of computer systems, wherein a message acquisition unit that captures a system message of an arbitrary computer system among the plurality of computer systems; A common message check unit that sets an error message that does not match the system message of the arbitrary computer system among the common system messages; and a system message unique to each of the plurality of computer systems among the system messages of the arbitrary computer system. A unique message check unit that sets a message that does not match the system message and a message that does not match the common system message as an invalid message; A message error check device, comprising: an output unit that creates a list of unauthorized messages. 3. The message error checking device according to claim 2, wherein the message acquiring unit creates a system message file storing a system message of an arbitrary computer system, and the common message checking unit reads the system message file. An error message file is created by storing the extracted error message with reference to the common system message, and the unique message check unit reads the system message file and refers to the common system message and the unique system message. And storing the extracted invalid message to create an invalid message file, and the output unit reads the error message file and the invalid message file to create the list. Error checking device. 4. The message error checking device according to claim 2, wherein the common system message forms a common message database, and the unique system message forms a unique message database. Message error check device.