Restrict multiple FORCE_STARTJOB events on jobs which are in RUNNING state

Document ID : KB000033546
Last Modified Date : 09/03/2018
Show Technical Document Details
Introduction:
The application users unintentionally submitting more than one FORCE_STARTJOB event on a job which is already running. This often leads to a situation where multiple instances of the same job running simultaneously creating a huge impact. This technical document explains the necessary procedure to set up a global restriction on sending FORCE_STARTJOB events for jobs which are in STARTING, RUNNING, WAIT_REPLY, or SUSPENDED state.
Question:

How to prevent the users from sending multiple FORCE_STARTJOB events inadvertently?

Environment:
CA Workload Automation AE 11.3.5
CA Workload Automation AE 11.3.6
Answer:

The following environment variable on CA Workload Automation AE specifies that the scheduler restricts users from running multiple instances of a job while the job is in the STARTING, RUNNING, WAIT_REPLY, or SUSPENDED state.

RESTRICT_FORCE_STARTJOB=1

On UNIX or Linux environments, export the variable at the operating system prompt. 
 
 #RESTRICT_FORCE_STARTJOB=1; export RESTRICT_FORCE_STARTJOB

Alternatively, the same can be set in the file $AUTOUSER/autosys.sh.$HOSTNAME.

On Windows, define the variable in CA Workload Automation Administrator utility.
Manage System Environment Variables Using the Administrator Utility

A restart of both the scheduler, application server services is necessary to make the environment variable effective.

After setting up the variable, the users would see the following message if they attempt a FORCE_STARTJOB on a job which is running. 

CAUAJM_I_60001 Job (JobName) has already started. FORCE_STARTJOB has no effect.
Additional Information:
Restrict the Runtime Behavior of Jobs