I have a problem.
insert_job: TEST-AGA-BD-10-SQL job_type: boxdescription: descriptionowner: autosysmax_run_alarm: 0alarm_if_fail: yavg_runtime: 15232date_conditions: ydays_of_week: tu,we,th,fr,sastart_times: "01:30"
contained job jil:
insert_job: TEST-AGA-CD-10-SQL-SWS_SOA job_type: cmddescription: descriptionmachine: AGASRVowner: service_autosysbox_name: TEST-AGA-BD-10-SQLgroup: SQLapplication: AGAmax_run_alarm: 0alarm_if_fail: yavg_runtime: 15std_out_file: "E:\Packages\SSAS\log\TEST-AGA-CD-10-SQL-SWS_SOA.out"command: "E:\Packages\SSAS\scripts\TEST-AGA-CD-10-SQL-sp_start_swsdb_job.bat"
the problem is that box does not fail if the contained job fails.
According to the manual - it should fail..
Could you please tell me whats wrong here?
there are more jobs in this box, and their fail trigger box failure normally. Only this one job is problematic.
How many other jobs are in it?
All jobs have to complete for a box to complete.
Nothing in this message is intended to constitute an electronic signature unless a specific statement to the contrary is included in this message.
Confidentiality Note: This message is intended only for the person or entity to which it is addressed. It may contain confidential and/or privileged material. Any review, transmission, dissemination or other use, or taking of any action in reliance upon this message by persons or entities other than the intended recipient is prohibited and may be unlawful. If you received this message in error, please contact the sender and delete it from your computer.
there are 4 jobs but they are dependents.
The job which fails is the first job from the tree...so the rest have no chance to startTEST-AGA-CD-10-SQL-SWS_SOA|JOB2 - JOB4|JOB3
Like i said all the jobs have to complete you have to fix the failed jobs for the rest to run if the last fails the box fails.
This is HOW boxes work.
The problem is that TEST-AGA-CD-10-SQL-SWS_SOA fails and the box DOES NOT fail. We have alarm sending job tied up with the box. It should send email in case of box failure - but....there is no box failure - box does not change its status even if TEST-AGA-CD-10-SQL-SWS_SOA has failed.
YOU ARE NOT LISTENING
The box doesn’t fail unless all jobs are completed in the box and there is a failure unless you add box_terminator(to the job) or box_failure (to the box)
Autosys doesn’t fail a box just because a job fails. Fix the job the rest will run.
Has no one taught you the rules of a box?
Listen very carefully for i will say this only once (points to people who know where this is from):
When using boxes it is important to understand the 3 rules of a box.
Rule 1: A job in a box may only run when the job’s parent box is running. This makes the parent box’s schedule the primary schedule. If no jobs inside the box have additional starting conditions then the jobs run in parallel.
Rule 2: The default completion of a box is all the jobs within it must complete. The completions states are (SUCCESS, FAILURE, TERMINATED)
Rule 3: A job in a box may run only once per iteration of the job’s parent box, no matter how you schedule the job. This means that if a job in a box is scheduled for every 10 minutes, but the box only runs at 3pm. Then the job will run once at 3pm schedule its next start, but never run until the next run of the box.
This has been the case since the 1990s
Ok just to confirm if I understood well.
Example 1) I have 10 non related jobs in the box.
1 fails, 9 succeed = BOX FAILS
Example 2) I have 5 related jobs (dependents) 1->2->3->4-5
"1" fails....Box does not change its status...
whole chain must end to change box status.
it makes sense from the logical point of view (phew!)
10 jobs are running in box, 3 succeeded - it wont change status of the box to success because the rest is running and may be crucial for box dependents
Sorry for being such an annoying student sir and Thank You.
No apologies necessary.
Glad to have helped clear things up.