1.6.3 Managing task progress
You can check the progress of tasks according to user need by using any of the following methods:
- Checking the status of tasks executed by a logged-in user
-
You can check the status of tasks executed by a logged-in user for each of the statuses in the task summary area.
You can also display a list of tasks that have the applicable status in the task summary area in order to check details or take action.
- Checking the statuses of all tasks
-
You can check in a list the statuses of all tasks that can be viewed by users.
By checking the task statuses such as In Progress or Completed in the task list, you can get a good understanding of how tasks are being processed automatically.
The list also shows when tasks start and finish processing, who submitted tasks, and other information.
- Checking the progress of a task
-
You can check the progress of a task being processed by JP1/AO.
You can also find out how far the processing of a task has progressed, which plug-in the task is currently processing, and other information.
- Organization of this subsection
(1) Overall progress of a task
In the detailed task information, the progress of the highest level of the task flow is displayed as follows:
(number-of-steps-that-have-finished-processing + number-of-steps-that-do-not-require-processing)/number-of-all-steps-contained-in-the-flow
The following figure shows an example of a task flow.
|
|
![[Figure]](GRAPHICS/UG020031.GIF)
JP1/AO calculates the progress of the processing flow as follows:
Progress = (3+1)/6
= 4/6
(2) Progress of individual task components
As detailed task information, JP1/AO displays the status, return value, start time, end time, and comment for each step name. The status in the detailed task information indicates the step status, or the status in the task processing engine.
You can change information displayed in the status by using the property file (config_user.properties). By default, the status of the step is displayed.
The following table describes information that is displayed as step statuses.
|
No. |
Step status |
Processing status category |
|---|---|---|
|
1 |
Waiting |
Steps that have not finished processing |
|
2 |
Interrupted |
|
|
3 |
Interrupted (After Execution) |
|
|
4 |
In Progress |
|
|
5 |
Waiting for Response |
|
|
6 |
Abnormal Detection |
|
|
7 |
Not Executed |
|
|
8 |
Failed |
|
|
9 |
Bypassed |
Steps that do not require processing |
|
10 |
Completed |
Steps that have finished processing |
|
11 |
Ended with a Warning |
|
|
12 |
Waiting to Repeat |
Out of scope# |
- #
-
Indicates the status before steps under the Repeated Execution Plug-in or repeated execution flows enter the repeated execution status. Therefore, the status is not displayed for the top flow.
The following table describes information that is displayed as statuses in the task processing engine.
|
No. |
Task processing engine status |
Processing status category |
|---|---|---|
|
1 |
Not sched. to exe. |
Steps that have not finished processing |
|
2 |
Wait for start time |
|
|
3 |
Waiting for prev. to end |
|
|
4 |
Waiting to execute |
|
|
5 |
Now queuing |
|
|
6 |
Shutdown |
|
|
7 |
Now running |
|
|
8 |
Failed to start |
|
|
9 |
Failed to start - WR |
|
|
10 |
Killed |
|
|
11 |
Killed - WR |
|
|
12 |
Not executed + Ended |
|
|
13 |
Not executed + Ended - W |
|
|
14 |
Running + Abend |
|
|
15 |
Running + Warning |
|
|
16 |
Ended abnormally |
|
|
17 |
Ended abnormally - WR |
|
|
18 |
Unknown end status |
|
|
19 |
Unknown end status - WR |
|
|
20 |
Invalid exe. seq. |
|
|
21 |
Interrupted |
|
|
22 |
Bypassed |
Steps that do not require processing |
|
23 |
Ended normally |
Steps that have finished processing |
|
24 |
Normal end + False |
|
|
25 |
Ended with warning |
Related topics
-
Property file (config_user.properties) in the Job Management Partner 1/Automatic Operation Configuration Guide