DBLibThresholdTime parameter reload requirements in AutoSys

Products

• Autosys Workload Automation

Issue/Introduction

This article explains the requirements for reloading the DBLibThresholdTime parameter within the AutoSys configuration file. It addresses whether a kill -HUP signal to the event_demon process is sufficient or if a service restart is required.

Does sending a kill -HUP signal to the event_demon process reload changes made to the DBLibThresholdTime parameter in the config.$AUTOSERV file?

Environment

• Product: AutoSys Workload Automation
• Operating System: UNIX, Linux, AIX

Resolution

No, sending a kill -HUP signal to the event_demon process does not trigger the scheduler to re-read the DBLibThresholdTime parameter. While kill -HUP reloads specific environment variables and debug settings (such as ISDBGACTIV), it does not apply to core database threshold parameters.

To apply changes to DBLibThresholdTime, perform a full stop and start (recycle) of the AutoSys Scheduler service. This requires a planned outage window.

Steps to update the parameter:

1. Modify the DBLibThresholdTime value in the $AUTOUSER/config.$AUTOSERV file.
2. Stop the AutoSys Scheduler (event_demon) service.
3. Start the AutoSys Scheduler service.
4. Monitor the scheduler logs to confirm the service starts without errors.

Additional Information

• For assistance, see  Contact Support . Scroll to the bottom of the page and click on your respective region.