autorep -d command shows various time stamps, very useful.
apparently running the same autorep command from different time zones will change only some of the time stamps to local time.
Compare columns "Time" and "ProcessTime" in the example below.
Why ProcessTime is always appears in Scheduler (EP) time zone? what is the benefit?
for TZ in Asia/Seoul America/New_York America/Los_Angeles
echo "=== $TZ ================================="
autorep -dj pavelv-x | egrep 'ProcessTime|SUCCESS'
=== Asia/Seoul =================================
Wed Dec 10 01:12:50 KST 2014
Status/[Event] Time Ntry ES ProcessTime Machine
SUCCESS 12/09/2014 06:47:08 1 PD 12/08/2014 16:47:09 dz803c3n4
=== America/New_York =================================
Tue Dec 9 11:12:53 EST 2014
SUCCESS 12/08/2014 16:47:08 1 PD 12/08/2014 16:47:09 dz803c3n4
=== America/Los_Angeles =================================
Tue Dec 9 08:12:53 PST 2014
SUCCESS 12/08/2014 13:47:08 1 PD 12/08/2014 16:47:09 dz803c3n4
> Why ProcessTime is always appears in Scheduler (EP) time zone?
My assumption has always been that time perspective can change for job related events because the timezone on a job can be changed. The database and scheduler are running in fixed time zones, so there is no reason to view them from other perspectives.
I don't see a great need to report on these times in synchronized times. If I want to view them at the database level I will convert them with SQL functions.