Force Starting a Job Outside of its Normal Schedule
Article ID: 16521
Updated On:
Products
Issue/Introduction
We have scheduled a job to force start outside of its normal schedule. In WCC, we do not see the forced start time - only the next scheduled job run time.
Q: Does this field take into consideration a future send event to start the job at a different date/time than scheduled for or is the 'Next Start Time' field only based on the job's defined schedule?
Q: Is there a way (if not in WCC job display) to see/ensure that the job will start tomorrow at 00:30 or is autotrack the only way to determine this?
Environment
Resolution
Q: Does this field take into consideration a future send event to start the job at a different date/time than scheduled for or is the 'Next Start Time' field only based on the job's defined schedule?
A: The Next Start Time is based upon the job's defined schedule. WCC gets this information from the Autosys DB (ujo_sched_info table).
Q: Is there a way (if not in WCC job display) to see/ensure that the job will start tomorrow at 00:30 or is autotrack the only way to determine this?
A: You can use the ECL tab to view the job's details (autorep -j <job_name> -d). You should see where the forced start job time occurs, as well as the next schedule job run. Autorack is not necessary to retrieve this information.
EXAMPLE
/* ----------------- next_start ----------------- */
insert_job: next_start job_type: CMD
command: ls
machine: redhat-1136sp3
owner: [email protected]
permission:
date_conditions: 1
days_of_week: all
start_mins: 00,10,20,30,40,50
alarm_if_fail: 1
[[email protected] ~]# sendevent -E FORCE_STARTJOB -J test_job -T "11/03/2017 15:35:00"
[[email protected] ~]# jr test_job -d
Job Name Last Start Last End ST Run/Ntry Pri/Xit
________________________________________________________________ ____________________ ____________________ __ ________ _______
test_job 11/03/2017 15:30:00 11/03/2017 15:30:00 SU 7/1 0
Status/[Event] Time Ntry ES ProcessTime Machine
-------------- --------------------- -- -- --------------------- ----------------------------------------
STARTING 11/03/2017 15:30:00 1 PD 11/03/2017 15:30:00 redhat-1136sp3
RUNNING 11/03/2017 15:30:00 1 PD 11/03/2017 15:30:01 redhat-1136sp3
<Executing at WA_AGENT>
SUCCESS 11/03/2017 15:30:00 1 PD 11/03/2017 15:30:01 redhat-1136sp3
[FORCE_STARTJOB] 11/03/2017 15:35:00 0 UP
[STARTJOB] 11/03/2017 15:40:00 0 UP
<Event was scheduled based on job definition.>
Feedback
