# Regarding Autosys job alerts

**URL:** <https://community.unix.com/t/regarding-autosys-job-alerts/391277>\
**Category:** UNIX for Advanced & Expert Users\
**Created:** [June 20, 2023, 9:20am UTC](https://community.unix.com/t/regarding-autosys-job-alerts/391277 "2023-06-20T09:20:56Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![munkeHoller](https://community.unix.com/user_avatar/community.unix.com/munkeholler/32/7431_2.png) [@munkeHoller](https://community.unix.com/u/munkeHoller)\
**Post date:** [June 21, 2023, 6:33am UTC](https://community.unix.com/t/regarding-autosys-job-alerts/391277/6 "2023-06-21T06:33:44Z")

</div>

@UnixNerd , I see you've asked on at least 1 other forum ( the forum rules request no cross posting [Simple rules of the UNIX.COM forums:](https://community.unix.com/t/simple-rules-of-the-unix-com-forums/140168) )

> <https://stackoverflow.com/questions/76513361/autosys-job-failing-to-set-job-status-to-failed-and-not-sending-alerts>

that aside, but with the dialog in the stackoverflow request, it appears that `command: XXXXXXXX.sh` is exiting with a 0 (success) status.  
this needs to exit with a non-zero status for the **alarm\_if\_fail: y**  
condition to be met such that an alarm is thrown.

you need to fix the check in your script that detects an error in the logs such that **XXXXXXXX.sh** exits with a non zero status.

**I will not respond further whilst you have the stackoverflow request open**

---

_[View the full topic](https://community.unix.com/t/regarding-autosys-job-alerts/391277)._