Incorrect Job start and end time in WCC
Article ID: 115643
Updated On:
Products
CA Workload Automation AE - Business Agents (AutoSys)
CA Workload Automation AE - Scheduler (AutoSys)
Workload Automation Agent
Issue/Introduction
In our new Autosys/WCC instance, we've noticed that the jobs show incorrect start and end times.
The Linux server where Autosys & WCC run is set on Eastern time zone. In WCC configuration, We have set to use Mountain Time(Denver). But the time stamps on the jobs show 3 hours behind mountain time. Eg: A job run at 10:00 AM Mountain Time would show 07:00 AM.
The Linux server where Autosys & WCC run is set on Eastern time zone. In WCC configuration, We have set to use Mountain Time(Denver). But the time stamps on the jobs show 3 hours behind mountain time. Eg: A job run at 10:00 AM Mountain Time would show 07:00 AM.
Environment
Release: WAAGTA99000-11.4-Workload Automation-Agent AE-MSP
Component:
Component:
Resolution
Oracle DB sever was running in Pacific time while Autosys server was running in timezone America/New_York.
Both Oracle server and Autosys server must resides in same timezone.
After changing the Autosys server to America/Los_Angeles there was still an issue as environmental variable TZ was set in .bash_profile and afterwards overwritten in the $AUTOUSER/autosys.*sh. files.
Both Oracle server and Autosys server must resides in same timezone.
After changing the Autosys server to America/Los_Angeles there was still an issue as environmental variable TZ was set in .bash_profile and afterwards overwritten in the $AUTOUSER/autosys.*sh. files.
Feedback
Yes
No
Powered by
