confirm
Confirms the completion of a job that was scheduled with the confirmed keyword. By default, evaluation on the job is performed when the job completes. However, if you confirm the job while it is running, the confirmation overrides the evaluation performed at job completion time. You can also override the evaluation of the output conditions: for example, if you set one or more output conditions to true (using confirm SUCC), the specified output conditions are set to true and any other conditions in the job are set to false.
You must have confirm access to the job.
Syntax
{confirm | conf} jobselect
;{succ | abend}
[;IF 'output_condition_name[, output_condition_name]
[, ...]'] [;noask]
Arguments
- jobselect
- See Selecting jobs in commands.
- succ
- Confirms that the job ended successfully.
- abend
- Confirms that the job ended unsuccessfully.
- output_condition_name
- Confirms the SUCC or ABEND status for one or more specified output conditions. Any conditions not specified are set to not satisfied. This setting overrides any other evaluation.
- noask
- Specifies not to prompt for confirmation before taking action on each qualifying job.
Comments
Changing the state of a job from
ABEND to SUCC does not require that the confirmed keyword be
used to schedule the job. For more information about job confirmation,
see confirmed.
For more information about EXTERNAL
jobs, see Managing internetwork dependencies in the plan.
State change after confirm command shows the effect of the confirm command on the various states of jobs, with or without output conditions:
Initial Job State | State after confirm ;succ | State 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
job3
in job stream misdly(1200 02/17/06)
,
run the following command: confirm misdly(1200 02/17/06).job3;succ
confirm 234;abend
job4
and
set MYOUTPUTCOND
to true in the daily(1130
02/17/2016)
job stream, run the following command:confirm daily(1130 02/17/2016).job4;succ if MYOUTPUTCOND
79765613
job
and its output conditions. The 79765613
job completed
in SUCC status:- Type the showjobs;info command to retrieve information about the
job:
The following sample output is a subset of the information you obtain by running the command:sj 79765613;info
Workstation Job Stream SchedTime Job NC050239 #DUBAIJS1 1908 10/23 (NC050239_1#)JS2 oc: OUT1 false "RC=2" oc: OUT2 true "RC=1500"
The first output condition,
OUT1
is false and the second one,OUT2
, is true. - Type the confirm command to confirm the ABEND status on
condition
OUT1
:confirm 79765613 ABEND; IF OUT1
- Type the showjobs;info command again. The following sample output is a subset of the
information you obtain by running the
command:
Workstation Job Stream SchedTime Job NC050239 #DUBAIJS1 1908 10/23 (NC050239_1#)JS2 oc: OUT1 true "RC=2" oc: OUT2 false "RC=1500"
The first output condition,
OUT1
has now changed to true and the second one,OUT2
, has changed to false.