Restrict multiple FORCE_STARTJOB events on jobs which are in RUNNING state
Article ID: 33546
Updated On:
Products
Issue/Introduction
How to prevent the users from sending multiple FORCE_STARTJOB events inadvertently?
Environment
CA Workload Automation AE 11.3.6
Resolution
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. This env script is called by the startup scripts for the Scheduler and Application server. Setting the variable in this script ensures that it is always set every time those services are started.
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.
Additional Information
Feedback
