JP2012173985A - Error message output method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To output an error message even when the number of items output as contents of the error message exceeds an upper limit value when the error occurs during operation.SOLUTION: An error message registration processing section 40 registers error information in an error information holding table 10 when an error occurs. An error message target acquisition processing section 70 acquires corresponding error message output target information from an error information generation parameter table 30. An error message generation processing section 80 generates an error message and stores it in a temporary storage area (memory). An error message upper limit determination processing section 110 determines whether or not the number of error messages to be output matches the upper limit number of error messages, and outputs the error message which is stored in the temporary storage area when they match. The procedure is repeated until the corresponding error message output target information is not acquired by the error message target acquisition processing section 70.

Description

  The present invention relates to a technique for outputting an error message that is output when an error occurs when a program is operated on an information processing apparatus.

  When an error occurs during operation in a software processing system created in advance by the information processing device, an error message is output to the external display device. Patent document 1 is mentioned as a technique relevant to this. Patent Document 1 discloses a method of outputting an error message in accordance with a rule extracted from an error information generation parameter table by providing an error information generation parameter table and defining user-specific customization in advance. . The error information generation parameter table defines user-specific customization for determining whether to notify the user of an error state detected by the software and for the format of the error message body when notifying the error state. This facilitates user-specific customization processing that outputs an appropriate error message according to the level of the software user.

Japanese Patent Laid-Open No. 5-100911

  In Patent Document 1, no consideration is given to the upper limit of the number of error messages that can be output at one time. For this reason, it is not possible to handle an error information table in which the number of output error messages exceeds the upper limit.

  Here, the number of output error messages refers to the number of items output as the contents of error messages.

  In addition, since the file layout used in the error source process and the file layout for error messages are managed separately, both maintenances are required during maintenance.

  In the present invention, the error message output upper limit number is defined in the error message upper limit table, and if an error occurs, if this upper limit value is exceeded, error message output is performed for the upper limit number, and then the remaining error messages Control to implement output.

  Also, output means for each user and for each error message is defined in the output means identification table.

  In addition, the table contents and the reference method for unifying file layout management are defined.

  The present invention makes it possible to output an error message even when the number of error messages exceeds the upper limit.

The hardware block diagram in one Embodiment of this invention. The flowchart in one Embodiment of this invention. The data block diagram of the error information holding table used by one Embodiment of this invention. The data block diagram of the error message upper limit table used by one Embodiment of this invention. The data block diagram of the error message production | generation parameter table used by one Embodiment of this invention. FIG. 3 is a data configuration diagram of an error information output destination printer definition table used in an embodiment of the present invention. . Error message example (1) Error message example (part 2). The data block diagram of an error message generation parameter table. The data block diagram of an error message upper limit table. Error message example (part 3). Error message example (part 4).

Hereinafter, embodiments of the present invention will be described with reference to the drawings.
When an error occurs during operation in a software processing system created in advance by the information processing device, an error message is output to the external display device. Even when the number of output error messages exceeds the upper limit, an embodiment is shown in which the number of output error messages is controlled only by the definition of the error information table.

  Here, the number of output error messages refers to the number of items output as error messages.

FIG. 1 shows a hardware configuration diagram constituting this embodiment.
FIG. 1 includes a terminal 1-1, a web web application server 1-2, a DB server 1-3, a batch server 1-4, and printers 1-5 and 1-6.

  In the present embodiment, the operator operates the terminal 1-1, and performs input for the definition of the error information generation parameter table shown in FIG. 9 and the definition of the error message upper limit table shown in FIG. All the terminals operated by the operator are connected to the web application server 1-2, and the information input by the terminal 1-1 is registered in each table of the DB server 1-3 via the web application server 1-2. The Here, the DB server includes an error information holding table 10 that stores error messages, an error message upper limit table 20 that holds upper limit values of error messages, and an error message generation parameter table 30 that stores information used to create error messages. And an output printer definition table 40 that holds output destination printer information for each error content.

  The information registered in each table of the DB server 1-3 is referred to by the batch server 1-4. The batch server 1-4 generates an error message based on the information registered in the DB server 1-3, and the printer The error message generated by 1-5 (or 1-6) is output.

Next, an error message output method will be specifically described with reference to FIGS. The flow of processing is shown in the flowchart shown in FIG. First, the error message registration processing unit 40 creates information (input information) created as intermediate information of the software processing system that the program causing the abnormality in the batch server 1-4 takes in as input information. Is registered in the error information holding table 10 together with the program ID and error code (S100).

Next, the error message upper limit number acquisition processing unit 60 acquires the upper limit number of error messages that can be output at one time from the error message upper limit table 20 using the system code as a key (S110). Here, the system code refers to a common code in the system.
In addition, the error message target acquisition processing unit 70 uses the error ID generation parameter table 30 as a key for the program ID and error code in which the error occurred, and the corresponding error message output target information (item name, copy phrase, layout pattern). Is acquired (S120). At this time, when there are a plurality of pieces of relevant error message output target information, they are acquired in ascending order of sequence numbers. Note that this order may be reversed. Furthermore, it does not prevent the order according to other rules.

  The error message acquisition determination processing unit 100 determines whether or not the error message output target information has been acquired (S130). If the error message acquisition target processing unit 100 can acquire the error message, the error message target copy phrase acquisition processing unit (S200) generates an error message. Necessary item information is acquired from various copy phrase files 150, and the error message generation processing unit 80 generates an error message based on the error message output target information acquired in the error message target acquisition process (S120). (S140). The generated error message is stored in a temporary storage area (memory).

  If there are a plurality of error messages to be output, the process from the error message target acquisition (S120) to the output (S160) is repeated.

In the middle of the repetition, the error message upper limit determination processing unit 110 determines whether or not the number of output error messages matches the error message upper limit number acquired in the error message upper limit number acquisition process (S110) (S150). If this determination matches, an error message stored in the temporary storage area is output (S160).
Thereafter, the process is repeated until the corresponding error message output target information is not acquired in the error message target acquisition process (S120).

  If the corresponding error message output target information is not acquired in the error message target acquisition (S120), the presence / absence of the output target is checked (S170), and if there is an output target, the error message file is output.

After file output for the error message to be output is completed, the output destination printer information acquisition processing unit 120 outputs the corresponding error message from the output destination printer definition table 40 using the program ID and error code in which the error occurred as a key. Get destination information (output destination printer address) (S180)
When the output destination printer determination processing unit 130 determines whether or not the output destination printer information has been acquired (S190), if the output destination printer information is acquired, based on the error message output destination information acquired in the output destination printer information acquisition processing (S180) Then, output to the corresponding printer is performed, and the process is terminated. At this time, the output error message is as shown in FIG.

  Next, an embodiment in which error message output is controlled by different output means for each user and for each error message will be described. For example, the information to be read from the error message differs depending on the position such as the person in charge of operation and the person in charge of maintenance. Therefore, the output means is controlled by the output destination code and the error code.

  First, the hardware used in this embodiment is the apparatus shown in FIG.

  The error message output method will be specifically described with reference to FIGS. It is assumed that the error information holding table uses the table of FIG.

  First, the error message registration processing unit 40 stores the information created as intermediate information of the software processing system, which is taken as the input information by the program in which the error occurred in the batch server 1-4, and holds the error information together with the program ID and error code. Register in the table 10 (S200).

  Next, from the error information generation parameter table 30, the error message target acquisition processing unit 60 determines the corresponding error message output target information (item name, start position, byte length, output destination) from the program ID and error code that generated the error. Code). At this time, if there are a plurality of pieces of relevant error message output target information, they are acquired in ascending order of output destination code and in ascending order of sequence number. Next, it is determined whether or not the output destination code matches the previous record (S230). If it is the first record, the answer is always Yes. Further, the error message upper limit number acquisition processing unit 50 acquires the upper limit number of error messages that can be output at one time from the error message upper limit table 20 based on the output destination code acquired in the error message target acquisition (S210) ( S260). Here, the reason why the error message upper limit table is acquired based on the output destination code is to deal with a case where the upper limit number of error messages differs for each output destination.

  The error message generation processing unit 70 generates an error message based on the input information that caused the error registered in the error message registration (S200) and the error message output target information acquired in the error message target acquisition (S210). Perform (S270). The generated error message is stored in a temporary storage area.

  When there are a plurality of error messages to be output, the process is repeated from the acquisition of the error message target (S210) to the output process (S290). During the repetition, in the error message target acquisition (S210), it is determined whether or not the acquired output destination code matches the output destination code acquired last time (S230). If they match as a result of the determination, the output target determination process (S240) and the output process (S250) are not performed. In the middle of repetition, the error message upper limit determination processing unit determines whether the number of output error messages matches the error message upper limit number acquired in the error message upper limit number acquisition (S260) (S280). If they match as a result of the determination, an error message stored in the temporary storage area is output (S290). The output processing unit 80 controls the output subprogram to be called based on the output destination code. The output destination printer is controlled by the called output subprogram. For example, when the output subprogram 1 is called, it is output to the printer 1-5, and when the output subprogram 2 is called, it is output to the printer 1-6.

  Next, until the output destination code acquired in the error message target acquisition (S210) does not match the output destination code acquired previously, the error message target acquisition (S210), the error message upper limit number acquisition (S260), and the error message are repeated. Repeat generation (S270).

  When the output destination code acquired in the error message target acquisition (S210) does not match the previously acquired output destination code (S230), output processing is performed (S250). At this time, the output error message is as shown in FIG. Among these, the operation report is as shown in FIGS.

  Thereafter, until the corresponding error message output target information is not acquired in the error message target acquisition (S210), the error message target acquisition (S210), the error message upper limit number acquisition (S260), and the error message information generation (S270) )repeat.

  The error message acquisition determination processing unit determines whether or not the error message output target information has been acquired (S220). If the error message acquisition target information cannot be acquired, the presence / absence of an output target is confirmed (S300), and then an error message is output (S310). At this time, the output error message is as shown in FIG.

1-1: Terminal
1-2: Web application server
1-3: DB server
1-4: Batch server
1-5: Printer
1-6: Printer
10: Error information holding table
20: Error message upper limit table
30: Error message generation parameter table
40: Error message output destination parameter table
50: Error message registration processor
60: Error message upper limit acquisition processing block
70: Error message target acquisition processing part
80: Error message generation processor
90: Output processing section
100: Error message acquisition judgment processing part
110: Error message upper limit judgment processing part
120: Output destination printer information acquisition processing section
130: Output printer determination processing unit
140: Error message target copy phrase acquisition processing part
150: Various copy phrase files

Claims (4)

In an error message output control method for controlling an error message related to an error generated by an information processing device,
In advance, an error message upper limit table that defines an upper limit value of the number of output error messages is stored,
Detecting the occurrence of an error in the information processing device;
Identify the number of error messages that should be output based on the detected error,
Determine whether the identified error message exceeds the upper limit,
As a result of the determination, if the upper limit value is exceeded,
(1) Output an error message for the upper limit,
(2) An error message output control method that outputs an error message other than the upper limit value after the output of the error message of (1). The error message output control method according to claim 1,
Store in advance an error message output destination table that defines the output destination for each error message type,
Identify the type of error message to be output based on the detected error,
The output of (1) and (2) is output to an output destination specified by the type of the specified error message and the error message output destination table. The error message output control method according to claim 2,
The error message output destination table is:
An error message output control method, wherein an error code is recorded as an error type and an output destination code is recorded as an output destination of the error message. In the error message output control method according to claim 2 or 3,
The error message output destination table records an output destination for each error message type for each program ID for identifying a program that generates the error,
The detection of the occurrence of the error is, from the program ID of the program in which the error has occurred, obtaining the upper limit value of the message corresponding to the program ID from the error message upper limit table,
Identify the error message generation parameter corresponding to the program from the program ID,
An error message output control method, comprising: generating an error message corresponding to a program in which the error has occurred from the specified error message generation parameter.

Images