We have a team that is having an issue with their box job. All of the jobs in the box are completing successful, however, when the last job completes the box fails. Why would the box fail if all of the jobs completed successfully?
We are currently using CAWAAE 11.3 sp1inc2
Apparently, there is no reason but in order to diagnose such a behavior, it would be good to look into the 'autorep -J <box> -d' output to see if some abnormal sequence of events happened or any manual sendevent command had been executed.
Along the 'autorep -J <box> -d' output, we also have to look into the event_demon log to fully understand the sequence of event and the job definitions
Some other general tips:
- look into the job definitions for the max_exit_success attribute
- check if jobs are really in "success" status and not in "terminate" status
- we also fixed some problems in this area, like this one:
BOX ENDS INCORRECTLY WHEN FINAL ACTIVATED JOB GOES ON_ICE
- I would suggest to open a case at CA support and upload all the above documentation
Thanks and regards
More than likely there’s a box_failure:
Set at the box level. I have seen users put box failures on globals and jobs outside the box.
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.