confirm
You can use the confirm command to validate the status of a job after completion.
Overview
The command is used to change the status of a job after it completes the run. When a job is finished with the status ABEND, you can use the confirm command to change the status to SUCC, so that any other depended jobs can start the run. It is also possible for a job to remain incomplete, either successfully or unsuccessfully. These jobs are finished as DONE and not SUCC or ABEND. The confirm command can be used to change the status of these jobs to either SUCC or ABEND, so that the workflow is not interrupted. The command option can also be used when there is a delay for the job to finish.
When you use the command option while the job is running, tthe confirmation overrides the evaluation status when the job is finished. Based on the (SUCC or ABEND) status that you provide with the command, the jobs finish with either SUCC or ABEND.
Syntax and command line options
ocli plan confirm | conf = <jobselect><succ | abend><IF 'output_condition_name[, output_condition_name]
[, ...]']><noask>
The details that are required with each parameters are described below.
Arguments
jobselectSpecify the job to update, by means of attributes and qualifiers.
For example,
WA_AGT_0#JOB_STREAM.JOB
.
SUCC
To confirm that the job ended successfully.
ABEND
To confirm that the job ended unsuccessfully.
output_condition_nameTo 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.
noaskWhen you add the option as an argument the agent will not ask for confirmation before taking action on each qualifying job.
Change in status after confirm command
Initial job status | Status after confirm ;succ
|
Status after confirm ;abend |
---|---|---|
READY | No effect, with or without output conditions | No effect, with or without output conditions. |
HOLD | No effect, with or without output conditions | No effect, with or without output conditions. |
EXEC |
|
|
ABENP | SUCCP, with or without output conditions |
|
SUCCP | No effect, with or without output conditions | No effect, with or without output conditions. |
PEND |
|
|
DONE | SUCC, with or without output conditions. | ABEND, with or without output conditions. |
SUCC |
|
|
ABEND | SUCC, with or without output conditions. |
|
SUPPR |
|
The operation is not supported, with or without output conditions. |
FAIL | The operation is not supported, with or without output conditions. | The operation is not supported, with or without output conditions. |
SCHED | No effect, with or without output conditions | No effect, with or without output conditions |
ERROR (for shadow jobs only) | SUCC, with or without output conditions | ABEND, with or without output conditions |
any job in the EXTERNAL job
stream |
SUCC, with or without output conditions | ABEND, with or without output conditions |
Examples
- To issue a succ confirmation for job
job3
in job streammisdly(1200 02/17/06)
, run the following command:ocli plan confirm misdly(1200 02/17/06).job3;succ
- To issue an abend confirmation for job number
234, run the following
command:
ocli plan confirm 234;abend
- To issue a succ confirmation for job
job4
and setMYOUTPUTCOND
to true in thedaily(1130 02/17/2016) job stream
, run the following command:ocli plan confirm daily(1130 02/17/2016).job4;succ if MYOUTPUTCOND