When using timezone Europe/Moscow, the timestamps show a 1 hour time difference in the timestamps of commands autosyslog -e, autosyslog -s and autorep -J <job_name>.
Examples:
[[email protected] ~]$ autorep -j testjob -s -t
Job Name Last Start Last End ST/Ex Run/Ntry Pri/Xit
________________________________________________________________ ____________________ ____________________ _____ ________ _______
testjob 2021/03/29 18:05:00 ----- RU 15286/1
(Europe/Moscow)
[[email protected] ~]$ date
Mon Mar 29 17:10:05 MSK 2021
[[email protected] ~]$ timedatectl
Warning: Ignoring the TZ variable. Reading the system's time zone setting only.
Local time: Mon 2021-03-29 17:10:11 MSK
Universal time: Mon 2021-03-29 14:10:11 UTC
RTC time: Mon 2021-03-29 14:10:11
Time zone: Europe/Moscow (MSK, +0300)
NTP enabled: yes
NTP synchronized: yes
RTC in local TZ: no
DST active: n/a
[[email protected] ~]$ autosyslog -e
Monitoring CA WAAE Scheduler Log:
/opt/CA/WorkloadAutomationAE/autouser.ACE/out/event_demon.ACE
*** To break out type control-c (^c) ***
[2021/03/29 18:15:29] CAUAJM_I_80021 The agent inventory service has evaluated the statuses of 5 machine(s) in 0.101 seconds.
[2021/03/29 18:16:00] ----------------------------------------
[2021/03/29 18:16:30] CAUAJM_I_80021 The agent inventory service has evaluated the statuses of 5 machine(s) in 0.101 seconds.
[2021/03/29 18:17:00] ----------------------------------------
^C
[[email protected] ~]$ date
Mon Mar 29 17:17:12 MSK 2021
AutoSys 11.3.6 SP8 CUM1 or lower do not handle the Europe/Moscow timezone correctly.
Release : 11.3.6
Component : CA Workload Automation AE (AutoSys)
This issue is fixed in AutoSys 12.0 or higher.
For 11.3.6x releases, as a workaround, use timezone MSK-3 instead. This can be set using the TZ variable in the $AUTOUSER/autosys.sh.<hostname> file:
TZ=MSK-3
export MSK-3
Stop and start the Scheduler and Application Server for the change to take effect.