JP2008262589A - Fixed operation automatic processing program, fixed operation automatic processing method, and fixed operation automatic processing device - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To flexibly and easily handle an unexpected event occurring in the execution of routine operation carried out by a computer, and to accurately reflect its handling content to the routine operation. <P>SOLUTION: When a start confirmation check requesting intervention operation of an operator is set before the execution of a task during the execution of the routine operation, the execution of the routine operation is stopped temporarily (S3), and it is determined whether an undefined task should be carried out according to an instruction from the operator (S4). For executing the undefined task, the undefined task is defined (S5) to be executed (S6), and execution information including the execution result is stored in a database (S7). If an end confirmation check requesting intervention operation of the operator is set after the execution of the task during the execution of the routine operation, the execution of the routine operation is stopped temporarily, and in a similar manner, the undefined task is executed, and its execution information is stored in the database. <P>COPYRIGHT: (C)2009,JPO&INPIT

Description

  The present invention relates to a technique for handling an unexpected situation in a technique for automatically processing routine operations by a computer.

  A routine operation in a computer, for example, a routine operation related to failure recovery, includes not only an operation that ends with one task but also a plurality of tasks that must be sequentially executed in a predetermined order. In the case of executing a plurality of tasks sequentially, it is necessary to constantly monitor the execution status of the task and selectively execute the subsequent task according to the execution result of the preceding task.

For this reason, as described in Patent Document 1, as a technique for automating routine operations that sequentially execute a plurality of tasks, a predetermined execution condition is set based on a procedure that defines routine operations by combining various tasks. Techniques have been proposed for sequentially executing suitable tasks. In addition, in the technology disclosed in Patent Document 1, whether a routine operation is temporarily stopped at the start or end of task execution and forcedly terminated by a computer operator so that a serious failure can be preferentially recovered. The structure which can designate whether or not is adopted.
JP 2003-140918 A

  In routine operations related to failure recovery, various failures must be assumed and tasks to recover from the failures must be defined, but it is practically impossible to anticipate all failures in advance, and routine operations are not possible. There is no denying the possibility of unexpected failures during execution. When an unexpected failure occurs, it is necessary to execute an unregistered task through an intervention operation by a computer operator using a function such as a command line.

  However, when an unregistered task is executed by such a method, the execution record does not remain, and it depends on the memory of the computer operator, so that it is difficult to accurately reflect the task in the routine operation. In addition, since the task execution result does not remain, it is impossible to determine whether or not the task is appropriate, and it is difficult to determine whether or not the task should be reflected in the routine operation.

  Therefore, in view of the conventional problems as described above, the present invention makes it possible to arbitrarily execute an unregistered task during execution of a routine operation and record the execution information of the task, thereby causing an unexpected situation. It is an object of the present invention to provide a routine operation automatic processing technique that can flexibly and easily cope with the routine and accurately reflect the countermeasure content on the routine operation.

  For this reason, in the routine operation automatic processing technique according to the present invention, a plurality of types of tasks are defined in combination, and execution of the routine operations is suspended during execution of routine operations by a computer that sequentially executes the plurality of defined tasks. When execution of a routine operation is suspended, an unregistered task that is not registered in the routine operation is executed, and execution information including an execution result of the executed unregistered task is recorded in a storage medium. And Here, it is desirable to pause the execution of the routine operation before or after executing the unregistered task. Moreover, it is desirable that the execution information recorded in the storage medium can be automatically reflected in the routine operation.

  According to such a configuration, it is possible to pause execution of a routine operation and arbitrarily execute an unregistered task that is not registered in the routine operation. For this reason, even if an unexpected situation occurs during execution of a routine operation, the situation can be dealt with flexibly and easily. In addition, when an unregistered task is executed, execution information including the execution result is recorded in the storage medium, so it is possible to examine whether the coping method is appropriate at a later date. Regular operations are better.

  And, if the configuration is such that the routine operation is suspended before or after the execution of the unregistered task, it is possible to prevent the unregistered task from being performed incompletely and improve the reliability of the routine operation. it can. On the other hand, if the execution information recorded in the storage medium can be automatically reflected in the routine operation, there is no room for human error by the computer operator, and it is possible to suppress a decrease in reliability related to the modification of the routine operation. it can.

  Further, it is desirable that the routine operation can be forcibly terminated in response to an explicit instruction from the computer operator when the execution of the routine operation is suspended. In this way, the fixed operation can be forcibly terminated at any time when the execution of the fixed operation is temporarily stopped. For this reason, when a minor failure and a serious failure occur simultaneously in a routine operation related to failure recovery, the computer is completely prevented from being brought down by giving priority to recovery from the serious failure. be able to.

  Furthermore, it is desirable to visually display the execution progress of routine operations. In this way, the computer operator can visually monitor the progress of execution of routine operations.

  According to the routine operation automatic processing technology according to the present invention, even if an unexpected situation occurs during execution of the routine operation, the situation can be dealt with flexibly and easily. In addition, when an unregistered task is executed, execution information including the execution result is recorded in the storage medium, so it is possible to examine whether the coping method is appropriate at a later date. The routine operation can be made better.

Hereinafter, the present invention will be described in detail with reference to the accompanying drawings.
FIG. 1 shows an overall configuration in which a routine operation automatic processing apparatus according to the present invention is constructed using a client / server system. The client and server are composed of a computer having at least a central processing unit (CPU) and a memory, and various functions related to routine operation automatic processing are realized by a program loaded in the memory.

  In client 1, in order to define routine operations, task registration for defining procedures composed of various tasks in cooperation with input devices such as keyboard and mouse and display devices such as CRT (Cathode Ray Tube) A screen 10 is displayed. In addition, a monitoring screen 20 having a user interface such as a GUI (Graphical User Interface) is displayed on the client 2 so that the progress of execution of the routine operation can be confirmed. The task registration screen 10 and the monitoring screen 20 may be displayed on the same client.

  On the other hand, the server 30 includes a setting processing unit 32, an execution control unit 34, and a database 36 (storage medium). The setting processing unit 32 provides a function of registering the procedure 36 </ b> A set via the task registration screen 10 of the client 1 in the database 36. The execution control unit 34 generates the monitoring data 36B from the procedure 36A registered in the database 36, and displays the progress of execution of the routine operation in the execution host 40 on the monitoring screen 20 of the client 2, and the task as a constituent unit thereof. Are automatically and sequentially executed.

  Note that the functions provided by the execution control unit 34 include a pause function, an unregistered task execution function, an execution information recording function, a reflection function, a forced termination function, a progress display function, a pause means, an unregistered task execution means, and an execution. Each information recording means is realized.

As shown in FIG. 2, the procedure 36A includes (A) basic information, (B) order information, and (C) state information.
The basic information shown in FIG. 2A defines basic attributes of a task as a constituent unit of the procedure 36A, and includes at least a task identification name, an execution host name, a command name, a start confirmation check, and an end confirmation check. Composed. In the task identification name, a task name for uniquely identifying the task is set. In the execution host name, a host name for uniquely identifying the execution host 40 that executes the task is set. As the command name, a command name for uniquely specifying a command activated by a task in the execution host 40 specified by the execution host name is set. In the start confirmation check and the end confirmation check, whether to perform an intervention operation by the computer operator by temporarily stopping the execution of the routine operation at the start and end of task execution is set.

  The order information shown in FIG. 2B defines the execution order and execution conditions of each task, and includes at least a task identification name, a preceding task identification name, a start condition, and an end code. In the task identification name, a task name for uniquely identifying the task is set. In the preceding task identification name, a preceding task name for uniquely identifying a task to be executed in advance is set so as to define the task execution order. The start condition is = ,! Arithmetic conditions or logical conditions such as =, <,>, ≦, ≧, or, between, and non are set. As the end code, a code such as a numerical value indicating the execution result of the preceding task is set. Then, in order to selectively execute the task according to the execution result of the preceding task, an execution condition, for example, an end code of the preceding task = 0 is defined by the start condition and the end code.

  The status information shown in FIG. 2C displays, for example, the normal end and abnormal end of a task in different colors on the monitoring screen 20 of the client 2 so that the execution progress of the routine operation can be grasped at a glance. And includes at least a task identification name, a state name, a state color, a state condition, and an end code. In the task identification name, a task name for uniquely identifying the task is set. The state name is set with the task execution state, for example, normal end, warning, abnormal end, and waiting for execution. In the status color, color information for displaying the task execution status by color is set. The state condition is = ,! Arithmetic conditions and logical conditions such as =, <,>, ≦, ≧, or, between, and non are set. As the end code, a code such as a numerical value indicating the task execution result is set. Then, in order to uniquely specify the execution state according to the task execution result, a specific condition, for example, a task end code = 0, is defined by the state condition and the end code.

On the other hand, as shown in FIG. 3, the monitoring data 36B includes (A) basic information and (B) order information.
The basic information shown in FIG. 3A includes an end code, a history number, and an additional flag in addition to each item of the basic information of the procedure 36A. In the end code, the execution result of the task specified by the task identification name, that is, the end code of the task is automatically set. In the history number, the number of executions of each task performed during execution of the routine operation is automatically set. Therefore, the task group having the same history number is a routine operation executed at that time. In the addition flag, a flag indicating whether or not the task specified by the task identification name is undefined, that is, whether or not the task is added during execution of the routine operation is automatically set. The order information shown in FIG. 3 (B) includes a history number similar to the basic information described above in addition to each item of the order information of the procedure 36A.

Next, the operation of the routine operation automatic processing device will be described.
Prior to executing the routine operation, first, a procedure 36A that defines the routine operation is defined. That is, on the task registration screen 10 of the client 1, basic information, order information, and status information of a task as a constituent unit of the procedure 36A are input. Then, the function provided by the setting processing unit 32 of the server 30 generates a procedure 36 </ b> A from the basic information of the input task and the like, and this is registered in the database 36. In the routine operation as shown in FIG. 4A, basic information, order information and status information as shown in FIGS. 4B to 4D are set in the procedure 36A of the database 36, respectively. The

  When executing a routine operation, for example, if a procedure that defines a desired routine operation is designated from among a plurality of procedures 36A registered in the database 36 via a procedure designation screen (not shown), the server 30 executes In the control unit 34, a routine operation automatic process shown in FIGS. 5 and 6 is started.

  In step 1 (abbreviated as “S1” in the figure, the same applies hereinafter), monitoring data in which an end code, a history number, an additional flag, and a history number are added to the basic information and order information of the specified procedure, respectively. 36B is generated and registered in the database 36. When the procedure 36A shown in FIG. 4 is designated, the monitoring data 36B shown in FIG. 7 is generated and registered.

  In step 2, the basic information of the task to be executed is sequentially read based on the setting contents of the monitoring data 36B. That is, in the first process, a task for which the preceding task identification name in the order information is not set is specified as the first task to be executed, and the basic information in which the task identification name is set is read. On the other hand, in the processing after the next time, a task that matches the execution condition specified by the start condition and the end code is identified from those in which the executed task is set in the preceding task identification name of the order information. The basic information in which the identification name is set is read.

  In step 3, it is determined whether or not the basic information start confirmation check is set to “present” in order to determine whether or not an intervention operation by the computer operator is requested before the task execution. If the start confirmation check is set to “Yes”, the process proceeds to Step 4 (Yes), and if the start confirmation check is not set to “None”, the process proceeds to Step 9 (No). Note that the processing in step 3 corresponds to a pause function and a pause means, respectively.

  In step 4, it is determined whether or not an instruction to execute an unregistered task has been issued by the computer operator. Here, whether or not an instruction to execute an unregistered task has been made can be determined, for example, based on whether or not “execute unregistered task” is selected from the menu of the monitoring screen 20. If an instruction to execute an unregistered task is issued, the process proceeds to step 5 (Yes), and if an instruction to execute an unregistered task is not issued, the process proceeds to step 8 (No).

  In step 5, a task to be executed prior to the task specified in step 2 is designated. That is, when an execution instruction for an unregistered task is given, a command execution screen as shown in FIG. 8 is displayed on the monitoring screen 20 of the client 2. The command execution screen includes a drop-down list that specifies a task name that uniquely identifies an unregistered task, a command execution host, an execution command, an execution parameter, and a parameter file. Then, on the command execution screen, specify the task name, command execution host and execution command, and if necessary, specify the execution parameters and parameter file and press the “Execute” button. Information and order information are generated and additionally registered in the monitoring data 36B of the database 36. At this time, 1 (added) is set to the added flag of the generated basic information.

In step 6, the task added in step 5 is executed.
Note that the series of processing from step 4 to step 6 corresponds to the unregistered task execution function and the unregistered task execution means, respectively.

  In step 7, the end code indicating the task execution result is recorded in the end code of the basic information of the monitoring data 36B. Thereafter, the process returns to step 4 to determine whether or not another unregistered task should be further executed. Note that the processing of step 7 corresponds to the execution information recording function and the execution information recording means, respectively.

  In step 8, it is determined whether or not the routine operation is continued, in other words, whether or not the routine operation is forcibly terminated. Whether or not to continue the routine operation can be determined from an operation performed by the computer operator during the suspension of the routine operation, for example. If the routine operation is continued, the process proceeds to Step 9 (Yes), and if the routine operation is not continued, that is, if the routine operation is forcibly terminated, this process is terminated (No). Note that the processing in step 8 corresponds to the forced termination function.

In step 9, the task specified in step 2 is executed.
In step 10, the end code indicating the task execution result is recorded in the end code of the basic information of the monitoring data 36B.

  In step 11, it is determined whether or not the end confirmation check of the basic information is set to “present” in order to determine whether or not an intervention operation by the computer operator is requested after the task execution. If the end confirmation check is set to “Yes”, the process proceeds to Step 12 (Yes), and if the end confirmation check is not set to “None”, the process proceeds to Step 17 (No). Note that the processing in step 11 corresponds to a pause function and a pause means, respectively.

  In step 12, it is determined whether or not an instruction to execute an unregistered task has been issued by the computer operator. If an execution instruction for an unregistered task is issued, the process proceeds to step 13 (Yes), and if an execution instruction for an unregistered task is not issued, the process proceeds to step 16 (No).

In step 13, a task to be executed subsequent to the task specified in step 2 is designated.
In step 14, the task added in step 13 is executed.

Note that a series of processing from step 12 to step 14 corresponds to an unregistered task execution function and an unregistered task execution means, respectively.
In step 15, an end code indicating the task execution result is recorded in the end code of the basic information of the monitoring data 36B. Thereafter, the process returns to step 12 to determine whether or not another unregistered task should be further executed. Note that the processing of step 15 corresponds to the execution information recording function and the execution information recording means, respectively.

  In step 16, it is determined whether or not to continue the routine operation. If the routine operation is continued, the process proceeds to Step 17 (Yes), and if the routine operation is not continued, that is, if the routine operation is forcibly terminated, the present process is terminated (No). Note that the processing in step 16 corresponds to the forced termination function.

  In step 17, it is determined whether or not the routine operation has ended, that is, whether or not the processing of all tasks of the procedure 36A that defines the routine operation has ended. Then, if the standard operation is finished, this process is finished (Yes), and if the standard operation is not finished, the process returns to Step 2 (No).

  According to the routine operation automatic processing described above, when the routine operation is paused before the task execution or after the task execution and an intervention operation by the computer operator is requested, FIG. 9 (before execution of the process 2) and FIG. As shown in (after execution of process 1), an unregistered task (process 3) can be arbitrarily added and executed. At this time, when the routine operation shown in FIG. 9 is executed, the basic information and the order information of the monitoring data 36B are as shown in (A) and (B) of FIG. 11, respectively. Note that the monitoring data 36B shows an example in which the routine operation has ended normally as a result of additionally executing the process 3 before executing the process 2 because the end code of the process 1 ended at the warning level 2. In the basic information shown in FIG. 5A, the history number is set to 1 as the execution history of all tasks, and the additional flag of processing 3 is set to 1 so that the additionally executed task can be identified. In addition, the additional flag of other processing is set to 0.

  For this reason, even when an unexpected failure occurs in a routine operation related to failure recovery, the failure can be flexibly and easily dealt with. Further, since the added task and the execution result remain in the monitoring data 36B, it is possible to examine later whether or not the coping method is appropriate, and the routine operation can be improved.

  Furthermore, when the routine operation is paused, it is possible to forcibly end the routine operation in addition to arbitrary execution of the unregistered task. For this reason, in routine operations related to failure recovery, for example, when a minor failure and a major failure occur at the same time, it is possible to prevent the system from going down completely by giving priority to recovery from a major failure. Can be prevented.

  When reflecting an unregistered task executed during execution of a routine operation to the procedure 36A, for example, if "reflection to routine operation" is specified from the menu on the monitoring screen 20 of the client 2, the reflection process (reflection) shown in FIG. Function) is activated. When performing the reflection process, it is necessary to specify the procedure 36A and the monitoring data 36B as the reflection destination and the reflection source on the reflection condition designation screen (not shown).

In step 21, the monitoring data 36B is read from the database 36.
In step 22, the basic information of the task is sequentially read in the order of execution based on the setting contents of the monitoring data 36B by the same processing as in step 2.

  In step 23, it is determined whether or not the task is an unregistered task with reference to the basic information addition flag. If it is an unregistered task, the process proceeds to step 24 (Yes), and if it is not an unregistered task, the process proceeds to step 25 (No).

In step 24, the unregistered task executed during execution of the routine operation is reflected in the procedure 36A by additionally registering the unregistered task in the procedure 36A.
In step 25, it is determined whether or not the routine operation has been completed, that is, whether or not the processing of all executed tasks has been completed. If processing for all tasks is completed, the present processing is terminated (Yes), and if processing for all tasks is not completed, the processing returns to Step 22 (No).

  According to the reflection process described above, an unregistered task arbitrarily executed during execution of a routine operation is automatically reflected in the procedure 36A. For this reason, when reflecting an unregistered task in a routine operation, there is no room for human error by a computer operator, and a decrease in reliability associated with a change in the routine operation can be suppressed.

  (Appendix 1) When a routine operation by a computer defined by combining various tasks is being executed, a pause function for temporarily stopping execution of the routine operation, and execution of the routine operation being paused by the pause function In addition, in response to an explicit instruction from the computer operator, an unregistered task execution function for executing an unregistered task for the routine operation, and execution of the task when the task is executed by the unregistered task execution function A routine operation automatic processing program for causing a computer to execute an execution information recording function for recording execution information including a result in a storage medium.

  (Supplementary note 2) The routine operation automatic processing program according to supplementary note 1, wherein the temporary stop function pauses execution of the routine operation before or after execution of the task.

  (Supplementary note 3) The supplementary feature 1 or 2 includes a reflection function that automatically reflects the execution information recorded by the execution information recording function in the routine operation according to an explicit instruction from a computer operator. The routine operation automatic processing program according to attachment 2.

  (Additional remark 4) When execution of routine operation is suspended by the said suspension function, the forced termination function which forcibly terminates the routine operation according to an explicit instruction from the computer operator is included. The routine operation automatic processing program according to any one of supplementary notes 1 to 3, which is a feature.

  (Supplementary note 5) The routine operation automatic processing program according to any one of supplementary notes 1 to 4, further comprising a progress display function for visually displaying the execution progress of the routine operation.

  (Appendix 6) During execution of a routine operation by a computer defined by combining various tasks, the execution of the routine operation is temporarily stopped, and a task unregistered in the routine operation according to an explicit instruction from the computer operator A routine operation automatic processing method characterized by recording execution information including an execution result of an executed unregistered task on a recording medium.

  (Supplementary note 7) During execution of a routine operation by a computer defined by combining various tasks, pause means for temporarily stopping the execution of the routine operation, and execution of the routine operation being paused by the suspension means In addition, in response to an explicit instruction from the computer operator, an unregistered task execution means for executing an unregistered task for the routine operation, and execution of the task when the task is executed by the unregistered task execution means A routine operation automatic processing device comprising: execution information recording means for recording execution information including a result on a storage medium.

Overall configuration diagram of a routine operation automatic processing apparatus according to the present invention The structure of a procedure is shown, (A)-(C) are explanatory drawings of basic information, order information, and status information, respectively. The structure of monitoring data is shown, (A) and (B) are explanatory diagrams of basic information and order information, respectively. An example of a routine operation is shown, and (A) to (D) are respectively a block diagram of the procedure and an explanatory diagram of basic information, order information, and status information of tasks. Flow chart showing routine operation automatic processing Flow chart showing routine operation automatic processing An example of monitoring data is shown, (A) and (B) are explanatory diagrams of basic information and order information, respectively. Illustration of command execution screen The state where the unregistered task was executed before the task execution is shown. (A) and (B) are explanatory diagrams of the monitoring screen before and after the unregistered task execution, respectively. The state where the unregistered task is executed after the task execution is shown, and (A) and (B) are explanatory diagrams of the monitoring screen before and after executing the unregistered task, respectively. FIG. 9 shows an example of monitoring data after execution of routine operations shown in FIG. 9, and (A) and (B) are explanatory diagrams of basic information and order information, respectively. Flow chart showing the reflection process

Explanation of symbols

30 Server 34 Execution Control Unit 36 Database 36A Procedure 36B Monitoring Data

Claims (5)

A pause function that prescribes a combination of multiple types of tasks and pauses the execution of the routine operations during execution of the routine operations by a computer that sequentially executes the prescribed tasks,
An unregistered task execution function for executing an unregistered task that is not registered as part of the routine operation when execution of the routine operation is suspended;
After executing the unregistered task, it is determined whether to continue to execute the routine operation that has been paused, and based on the result, the function to continue to execute the routine operation;
An execution information recording function for recording execution information of the routine operation including an execution result of the executed unregistered task on a storage medium when the unregistered task is executed;
Routine operation automatic processing program to make computer realize.   The routine operation automatic processing program according to claim 1, wherein the pause function pauses execution of the routine operation before or after execution of the unregistered task.   2. The reflection function for automatically reflecting the execution information of the unregistered task recorded by the execution information recording function in the routine operation when an instruction is given from the outside. The routine operation automatic processing program according to 2.   When execution of a routine operation is paused during execution of a routine operation by a computer that prescribes a combination of multiple types of tasks and sequentially executes the plurality of prescribed tasks, and the execution of the routine operation is suspended In addition, an unregistered task that is not registered in the routine operation is executed, and execution information including an execution result of the executed unregistered task is recorded in a storage medium. A pause unit that prescribes a combination of a plurality of tasks and pauses execution of the routine operation during execution of the routine operation by a computer that sequentially executes the plurality of tasks defined;
Unregistered task execution means for executing an unregistered task that is not registered in the routine operation when execution of the routine operation is suspended by the suspension means;
Execution information recording means for recording execution information including an execution result of the unregistered task in a storage medium when the unregistered task is executed by the unregistered task execution means;
A routine operation automatic processing device characterized by comprising the above.

Images