Timezone Mismatch: Job ProcessTime and Start Time discrepancy in AutoSys

Products

• CA Workload Automation AE - Business Agents (AutoSys)
• CA Workload Automation AE - Scheduler (AutoSys)
• Workload Automation Agent

Issue/Introduction

When running an autorep -d command, the Time (Event Time) and ProcessTime do not match. For example, a job force-started at 11:00 AM PST shows a ProcessTime that is 6 hours ahead (UTC).
This often occurs after migrating the AutoSys database to a new environment, such as AWS RDS Oracle.

Environment

• AutoSys Workload Automation (All Versions)
• Oracle Database (including AWS RDS)
• Microsoft SQL Server

Cause

The discrepancy occurs because the AutoSys Scheduler and the Database are not synchronized to the same timezone.

• Time (Event Time): The time provided by the Scheduler based on the server's Operating System time.
• ProcessTime: The time provided by the Database where the event was recorded.

In cloud migrations (AWS RDS), the database timezone often defaults to UTC, while the Scheduler server remains in a local timezone (e.g., PST).

Resolution

Synchronize the timezone settings between the AutoSys Scheduler server and the Database server.

1. Verify Scheduler Time: On Linux/Unix, run: timedatectl or date On Windows, run: time /T

2. Verify Database Time: For Oracle: SELECT systimestamp FROM dual; For MSSQL: SELECT CURRENT_TIMESTAMP AS current_date_time;

3. Correct the Discrepancy:

   • Work with your DBA to set the database timezone to match the primary scheduler's timezone.
   • If the database cannot be changed, ensure the TZ environment variable is correctly set in the AutoSys environment ($AUTOUSER/autosys.*sh files) and restart the AutoSys services.

 

 

Additional Information

To speak with a customer representative or a Support Engineer see Contact Support. Scroll to the bottom of the page and click on the respective region.