2.4.1 Checking action status
To see the execution results of actions, open the Checking the status dialog box from the Job Design View.
A status is assigned to each of the action flow (Hello Check) contained in the job and the actions (make file, check file, and complete) defined in the action flow.
|
- Organization of this subsection
(1) Checking actions
In this example, the action make file created the c:\temp\hello.txt file and thus the action check file ended normally. The normal end caused the third action to display a message dialog box containing the message Success!.
Procedure
-
In the Job Design View, click the Exec. on time tab.
When you select a job, the
(Checking the status) button appears.
-
Click the
(Checking the status) button.
The Checking the status dialog box appears.
-
Check the status of the job.
The upper area of the Checking the status dialog box displays a job list, including the job's start time, end time, and status.
-
In the job list, select a job.
A unit list appears in the lower left area of the dialog box.
- Note
-
In the job list and unit list shown in steps 3 and 4, a job or unit is displayed in red font if the job or unit ended abnormally. For details on how abnormally-ended jobs and units are displayed, see 2.4.1(3) Checking for abnormal end.
-
In the unit list, select a unit.
-
The lower right area of the dialog box displays the information of the unit, including the unit's status, the start time, and the end time.
-
In the unit list, click the triangle mark to the left of the unit name.
Units in the action flow appear in a tree view.
-
Select the check file unit.
-
Click the Execution result button in the lower right of the dialog box.
The Execution result dialog box appears.
-
Check the execution command, standard output, and standard error output.
You find that the check file action ended normally.
(2) Testing the recovery execution command
Let's test the recovery execution command in the check file action.
Firstly, delete the hello.txt file that you initially created.
Procedure
-
In the Job Design View, click the Action flow tab.
-
Select the action flow Hello Check, and then click the
(Edit) button.
A dialog box appears for the action flow Hello Check.
-
Right-click the icon of the unit make file and select Edit from the menu. Alternatively, double-click the icon of the unit make file.
A dialog box appears for the unit make file.
-
Change the parameter from /c echo hello!! >c:\temp\hello.txt to /c del c:\temp\hello.txt, and then click the OK button.
-
Click the Register button to register the action flow Hello Check.
A message appears, asking whether you really want to overwrite the action flow.
-
Click the OK button.
The Job Design View appears again. In the Exec. on time tab, select the job TEST02.
-
Click the
(Edit) button.
A dialog box appears for the job TEST02.
-
Click the Register button to register the job.
A message appears, asking whether you really want to overwrite the job.
-
Click the OK button.
(3) Checking for abnormal end
The following figure shows the status transition of the action flow (Hello Check) contained in the job and the actions (make file, check file, and complete) contained in the action flow. The second action (check file) ended abnormally (ENDE). This caused the subsequent action (complete) not to run and the status of both the action flow and the job, which are containers of the second action, to be set to Ended abnormally (ENDE).
|
In this example, the action make file deleted the c:\temp\hello.txt file and thus the if statement in the action check file returned true. This caused the execution command (cmd.exe) ended abnormally. The abnormal end, in turn, caused the recovery execution command to run to display a dialog box containing the message Failure!.
Procedure
-
Open the Checking the status dialog box. From the job list, select an abnormally-ended job, which is displayed in red font.
-
Select the unit check file, which is displayed in red font.
-
Click the Execution result button.
The Execution result dialog box appears.
-
Check the execution command, standard output, and standard error output.
You find that the execution command in check file ended abnormally.
-
Additionally, confirm that the recovery execution command run has ended.