Box job is stuck in running state due to two active jobs
search cancel

Box job is stuck in running state due to two active jobs

book

Article ID: 411190

calendar_today

Updated On:

Products

Autosys Workload Automation

Issue/Introduction

There is a have a Box with 3 jobs:

1. Job1 -> File pull job

    Success codes set to 0,5
    If the file is not found, it exits with code 5 (treated as success)

2. Job 2 -> has a start condition exitcode (Job1) =0

    Should only run when job1 exits with 0.

3. Job3 -> Dependent on Job2 

Box-> configure with box_terminator:1

Issue:
When Job1 ends successfully with exit code 5( configured as success), Job2 does not meet the condition(since it only wants exit code 0).
In this case, Job2 and Job3 move to the activated state, but the box does not terminate.
It stays running until manually forced to end.

 

Expected Behavior:
Because Job2's condition is not satisfied and box terminator =1 ,
We expect Job2 and Job3 to be skipped and the box to terminate.

Environment

Autosys 12.x 24.x

Resolution

 example

insert_job : Box
job_type : box
box_success : e(JobA)=5 or (e(jobA)=0 and s(jobB) and s(jobC))

insert_job : JobA
command : as_test -e $$ecode
machine : localhost
box_name : Box
success_codes : 0,5

insert_job : JobB
command : echo
machine : localhost
box_name : Box
condition : e(JobA) = 0

insert_job : JobC
command : echo
machine : localhost
box_name : Box
condition : s(JobB)

Additional Information