Hi,
U can try to make use of GLOBAL VARIABLE as a condition in the job definitions.
eg:
insert_job: JOB A
conditions: v(GV=1) and s (JOB 123)
days_of_week: daily
start_times: "7:00"
date_condition: 1
set the value of GV by using set_global_variable command to 0.
so in this case, since the job A has 4 starting conditions to satisfy, if any of the condition is not fulfilled this job will not run.
1. value of GV shd be 1
2. Success of JOB 123
3. time is 7AM
4. run day is daily
As using the send event command we have set the value of GV to 0, so this job will not run until the value of GV is set to 1, irrespective of other 3 conditions being satisfied. Hence the job will not be running and is kind of ON_HOLD situation.
This is the best possible option that I can think of w.r.t version 4.5, as GV is the attribute which is in picture in autosys from all versions starting from 4.0 till now.
Above is just an example, you can use GV without combining any other conditions as well.
However, a point of caution is:
if a job is defined to run on the specific value of GV, then that job definition wont be an adhoc job and runs immediately as soon as the value of GV met the job condition.
**** Job status will be ACTIVATING or INACTIVE and future actions (adhoc batch requests) will be taken according to job status.
Also,
if you would have been using latest version then we cud have used RESOURCE attribute which also works in same way as GV but handling of adhoc request / forcestarts varies as per resource type used.
**** I am not sure or confused with the job states, I think in above example, job will be in ACTIVATING STATE and be in AC state until the value of GV is set to 1.