confirm
You can use the confirm command to change the status of a task after it finishes.
Overview
When a task finishes with the ABEND status, you can use the confirm command to change the status to SUCC, so that the other depended tasks can start. You can use the confirm command to change the status of the tasks to either SUCC or ABEND, so that the workflow is not interrupted. The command can also be used when there is an issue delays task completion.
When you use the confirm command while the task is running, the confirmation overrides the evaluation status when the task is finished. Based on the (SUCC or ABEND) status that you provide with the command, the tasks finish with either SUCC or ABEND status.
You can also override the evaluation of the output conditions. For example, if you
set one or more output conditions to true (by using the confirm
SUCC), the specified output conditions are set to true and
any other conditions in the task are set to false. You must have
confirm access to the task.
Syntax and command line options
ocli plan confirm | conf jobselect;[succ | abend] [IF 'output_condition_name[, output_condition_name]
[, ...]'] [;noask]- jobselect
-
Specify the task to update, by using attributes and qualifiers.
For example, enter the following command
WA_AGT_0#WORKFLOW.TASK.
- SUCC
- To confirm that the task ended successfully.
- ABEND
- To confirm that the task ended unsuccessfully.
- output_condition_name
- To confirm the SUCC or ABEND status for one or more specified output conditions. The conditions which are not specified are set to false. This setting overrides any other evaluation.
- noask
-
When you add the noask option as an argument, the agent does not ask for confirmation before it acts on each qualifying item.
Change in status after confirm command
| Initial task status | Status after running the confirm
;succ command |
Status after running confirm ;abend
command |
|---|---|---|
| READY | No effect regardless of output conditions | No effect regardless of output conditions |
| HOLD | No effect regardless of output conditions | No effect regardless of output conditions |
| EXEC |
|
|
| ABENP | SUCCP regardless of output conditions | No effect regardless of output conditions |
| SUCCP | No effect regardless of output conditions | No effect regardless of output conditions |
| PEND |
|
|
| DONE | SUCC regardless of output conditions. | ABEND regardless of output conditions. |
| SUCC |
|
|
| ABEND | SUCC, regardless of output conditions. |
|
| SUPPR |
|
The operation is not supported regardless of output conditions. |
| FAIL | This operation is not supported regardless of output conditions. | This operation is not supported regardless of output conditions. |
Examples
- To issue a succ confirmation for the
task4task infronttl(1000 04/11/08)workflow, run the following command:ocli plan confirm fronttl(1000 04/11/08).task4;succ - To issue an abend confirmation for the
352 task, run the following
command:
ocli plan confirm 352;abend - To issue a succ confirmation for
task7task and set theMYOUTPUTCONDresult to true in theweekly(1230 04/11/2018) workflowworkflow, run the following command:ocli plan confirm weekly(1230 04/11/2018).task7;succ if MYOUTPUTCOND