Fixing Delay in AutoSys Job Restart

Fixing Delayed AutoSys Command Job Restart Scenario

In this article, we will discuss a common scenario in automating job execution using AutoSys, where a command job fails and needs to be retried with a delay of 10 minutes before the next retry attempt. Specifically, we will cover the following key concepts:

• Understanding AutoSys job execution and retry mechanisms
• Implementing a delayed retry strategy for failed command jobs
• Best practices for troubleshooting and debugging delayed AutoSys job restarts

Understanding AutoSys Job Execution and Retry Mechanisms

AutoSys is a popular job scheduling software that allows users to automate the execution of various tasks, including command-line programs, scripts, and other applications. When a job is created, it is assigned a set of attributes that determine how it should be executed, such as the command to run, the maximum number of retries, and the time interval between retries.

By default, AutoSys will retry a failed job up to a maximum number of times specified in its attributes. If the job still fails after all retries have been exhausted, AutoSys will mark it as failed and send a notification to the designated recipient. However, there may be situations where a job fails due to transient issues, such as network connectivity problems or resource contention, and the job itself is not inherently flawed. It is in these cases where a delayed retry strategy can be useful.

Implementing a Delayed Retry Strategy for Failed Command Jobs

To implement a delayed retry strategy for a failed command job, we can use the sleep command to introduce a 10-minute delay before the next retry attempt. Here is an example of how this can be done:

#!/bin/bash

# Command to be executed
command_to_run > /dev/null

# Check exit status of command
if [[ $? -ne 0 ]]; then
# Run sleep command to introduce delay and retry
for  i in {1..2}
do
sleep 600
command_to_run > /dev/null
if [[ $? -eq 0 ]]; then
break
fi
done
fi

In this example, the command_to_run is executed first. If the command fails, the script enters a loop that retries the command twice with a 10-minute delay between each attempt. If the command succeeds in any of the retry attempts, the loop is exited and the script continues. If the command fails after all retry attempts, the script exits with a non-zero exit code, indicating that the job has failed.

Best Practices for Troubleshooting and Debugging Delayed AutoSys Job Restarts

When implementing a delayed retry strategy for failed command jobs, it is important to follow best practices for troubleshooting and debugging. Here are some tips to keep in mind:

• Ensure that the command being executed is correct and has the necessary permissions to run
• Check the logs and error messages generated by the command to identify the root cause of the failure
• Monitor the system resources and network connectivity to ensure that they are not causing the failures
• Implement proper error handling and logging in the script to make it easier to diagnose issues

References

• Delaying Job Execution Using Sleep
• Job Retry Mechanism
• Job Error Handling

This article covers the scenario of retrying a failed AutoSys command job with a delay of 10 minutes. By understanding the AutoSys job execution and retry mechanisms, implementing a delayed retry strategy, and following best practices for troubleshooting and debugging, users can ensure that their jobs are executed successfully and minimize the impact of transient failures.