Actions parameters

Actions parameters are used to describe actions to be performed if the job is not submitted, actions to be performed after the job has finished executing, handling of the job’s log (Output), notification messages to various users, and rerun conditions. Based on the job’s execution status codes, Control‑M automatically assigns the following completion status:

OK: Job ended OK. The job finished executing with a successful operating system completion status. This status can be overridden with the Set to Ok parameter (as a result of an On Statement/Code evaluation).
NOTOK: Job did not end OK. The job finished executing with an unsuccessful operating system completion status or due to a submission failure (for example, queue does not exist). This status can be overridden with the Set to Ok parameter (as a result of an On Statement/Code evaluation).

Steps parameters can also be defined for SMART folders.

Actions to be performed if a SMART folder finished OK are performed only if all the jobs in the SMART folder finished OK.
Actions to be performed if a SMART folder finished NOTOK are performed only if one or more jobs in the SMART folders finished NOTOK.

Post-processing of a SMART folder occurs when the last job in the SMART folder ends. A SMART folder may become active again after the post-processing has been completed, if one or more jobs are rerun, or if a new job is added to the SMART folder and submitted. In this case, when the last job in the SMART folder ends again, the completion status of the SMART folder is rechecked and the appropriate post-processing actions are performed.

For more information about SMART folders, see Job definition in Control-M .

Parameter	Description
Auto-Archive	Determines whether SYSDATA (job output) must be archived.
CTB Step	Adds Control‑M/Analyzer steps as the first and/or last step of the job’s execution.
On/Do Actions	Automatic interventions, such as rerunning a job or ordering a remedial job, if a job ends with a particular error code.
Code values	Code values can be condition codes, user abend codes, system abend codes, various end codes and statuses, and certain keywords. They can also be prefaced by certain qualifiers.
Out Condition	Specifies prerequisite conditions to be added or deleted after the job completes.
Action	Indicates how the job’s log file (Output) should be handled after the job ends with a status of OK.
Retention Days	Determines the number of days to retain the job in the History Jobs file. For z/OS jobs only.
Retention Generations	Maximum number of generations of the job to keep in the History Jobs file. For z/OS jobs, only.
Specific Range Name	Specifies a range of steps in the steps of an On PGMST statement.
Pre-Notifications	The Pre-Notifications parameter gives you the ability to create a message that is sent to one or more specified destinations when certain conditions are encountered.
Final Notifications	Sends a notification if a job terminates with a completion status of OK or NOTOK.