Dependent job not starting after condition met when included under a box job

[Srini Venkat]

We have created & run other jobs successfully previously with a condition and also setting dependency under a box so that is what makes this so frustrating.

We have job B with condition S(job A).

When both of them defined with a box_name parameter (both under the same BOX job), then even after successful run of job A, job B does not start.

When I move them both out of the box - clear out the box name parameter - then if run job A, job B runs right after

job B is sql command job i.e. directly executes a stored procedure - that is the only thing that is different from our existing jobs with similar, prior successful setup (they are SSIS jobs). 

Any idea if I am doing something wrong? I tried d(job A) as the condition as well with no luck.

[Venkateshwar Goud Badrigari]

How are you starting the JobA? are you starting the box or JobA
individually using FORCE_STARTJOB? What is the status or Box job when the
JobA completes?

Regards,
*Venkat*

--
This electronic communication and the information and any files transmitted
with it, or attached to it, are confidential and are intended solely for
the use of the individual or entity to whom it is addressed and may contain
information that is confidential, legally privileged, protected by privacy
laws, or otherwise restricted from disclosure to anyone else. If you are
not the intended recipient or the person responsible for delivering the
e-mail to the intended recipient, you are hereby notified that any use,
copying, distributing, dissemination, forwarding, printing, or copying of
this e-mail is strictly prohibited. If you received this e-mail in error,
please return the e-mail to the sender, delete it from your computer, and
destroy any printed copy of it.

[Corrie Kantowski]

Could you share your job definitions for the box and 2 jobs that are in it?

[Srini Venkat]

Thank you for your replies.

Here are the JILs (some field values changed to mask confidential information). As I mentioned,

• If I Force StartJob A as is, after it successfully completes, Job B does not start
• If I update the box_name as blank (remove it from box) then FS Job A, Job B runs immediately after

insert_job: JOBA                job_type: CMD 
box_name: BOX1
command: \\<server_path>\JOBA.bat 
machine: <machine_name>
owner: <owner_name>
date_conditions: 1
run_calendar: Calendar_day_16
start_times: "09:00"
std_out_file: "\\<server_path>\JOBA.out"
std_err_file: "\\<server_path>\JOBA.err"
timezone: EST5EDT

insert_job: JOBB                  job_type: CMD 
box_name: BOX1
command: \\<server_path>\JOBB.bat 
machine: <machine_name>
owner: <owner_name>
date_conditions: 0
condition: s(JOBA)
std_out_file: "\\<server_path>\JOBB.out"
std_err_file: "\\<server_path>\JOBB.err"
timezone: EST5EDT

[Jeff Goodall]

You will need to put the schedule on the box, not the job within. That will put the box/jobs in an activated state and allow all jobs to start as sequenced. 

JobA will have no start conditions and will start when the box starts, then JobB start conditions based on JobA will trigger as expected.

[Srini Venkat]

I was hoping to use a "BOX" as only a grouping mechanism to keep like-purpose jobs together (more like a folder in a file system) but with each job having its own schedule / dependencies. Is that not possible? Does Autosys offer any other mechanism for my stated purpose? 

[Jeff Goodall]

not really, the box will always have to be started first so everything gets activated, then you can set up your other schedules/dependencies from there. Then the box will go success when all jobs within are success. 

[Srini Venkat]

Ok ... thank you for the clarification.