ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Jobs are being scheduled an hour later than time in JIL

book

Article ID: 199854

calendar_today

Updated On:

Products

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

Issue/Introduction

Hello, we have an issue with jobs being scheduled an hour later than they are indicated in the JIL.  Everything as far as timezones looks fine from a system and autosys perspective.

Example: 
insert_job: ASINHOUXXAD_AUTOSYS_DAILY_SENDEVENT_LOG   job_type: CMD 
command: /autosys/scheduling/scripts/sendeventlogs.sh
machine: localhost
owner: autosys
permission: gx
date_conditions: 1
run_calendar: GL_ALL_CDY_N
start_times: "11:30"
description: "Per Miguel"
std_out_file: "/autosys/scheduling/logs/AUTOSYS_SENDEVENT_LOG.out"
std_err_file: "/autosys/scheduling/logs/AUTOSYS_SENDEVENT_LOG.err"
max_run_alarm: 27
alarm_if_fail: 1
group: INHOU
application: INHOU

Job is scheduled to come in at 11:30 but does not run until 12:30.

doing an autorep with -d

ASINHOUXXAD_AUTOSYS_DAILY_SENDEVENT_LOG                          09/17/2020 11:30:00  09/17/2020 11:30:27  SU    167/1    0      

  Status/[Event]  Time                 Ntry ES  ProcessTime           Machine
  --------------  --------------------- --  --  --------------------- ----------------------------------------
  STARTING        09/17/2020 11:30:00    1  PD  09/17/2020 11:30:00   pdc8rbscwlaap01
  RUNNING         09/17/2020 11:30:00    1  PD  09/17/2020 11:30:01   pdc8rbscwlaap01
    <Executing at WA_AGENT_UAT>
  SUCCESS         09/17/2020 11:30:27    1  PD  09/17/2020 11:30:27   pdc8rbscwlaap01
  [CHK_MAX_ALARM]  09/17/2020 11:57:00    1  PD  09/17/2020 11:30:27   pdc8rbscwlaap01
  [STARTJOB]      09/18/2020 11:30:00    0  UP                        
    <Event was scheduled based on job definition.>

From eventlog:

[09/17/2020 12:30:00]      CAUAJM_I_40245 EVENT: STARTJOB         JOB: ASINHOUXXAD_AUTOSYS_DAILY_SENDEVENT_LOG
[09/17/2020 12:30:00]      CAUAJM_I_40245 EVENT: CHANGE_STATUS    STATUS: STARTING        JOB: ASINHOUXXAD_AUTOSYS_DAILY_SENDEVENT_LOG MACHINE: pdc8rbscwlaap01
[09/17/2020 12:30:00]      CAUAJM_I_10082 [pdc8rbscwlaap01 connected for ASINHOUXXAD_AUTOSYS_DAILY_SENDEVENT_LOG 172.167.1]
[09/17/2020 12:30:01]      CAUAJM_I_40245 EVENT: CHANGE_STATUS    STATUS: RUNNING         JOB: ASINHOUXXAD_AUTOSYS_DAILY_SENDEVENT_LOG MACHINE: pdc8rbscwlaap01
[09/17/2020 12:30:27]      CAUAJM_I_40245 EVENT: CHANGE_STATUS    STATUS: SUCCESS         JOB: ASINHOUXXAD_AUTOSYS_DAILY_SENDEVENT_LOG MACHINE: pdc8rbscwlaap01 EXITCODE:  0


$ echo $TZ
America/New_York


$ timedatectl
Warning: Ignoring the TZ variable. Reading the system's time zone setting only.

      Local time: Thu 2020-09-17 12:47:18 EDT
  Universal time: Thu 2020-09-17 16:47:18 UTC
        RTC time: Thu 2020-09-17 16:47:18
       Time zone: America/New_York (EDT, -0400)
     NTP enabled: yes
NTP synchronized: yes
 RTC in local TZ: no
      DST active: yes
 Last DST change: DST began at
                  Sun 2020-03-08 01:59:59 EST
                  Sun 2020-03-08 03:00:00 EDT
 Next DST change: DST ends (the clock jumps one hour backwards) at
                  Sun 2020-11-01 01:59:59 EDT
                  Sun 2020-11-01 01:00:00 EST

$ date
Thu Sep 17 12:50:17 EDT 2020














Environment

Release : 12

Component : CA Workload Automation AE (AutoSys)

Resolution

Issue was caused by a change to exadata time zone to CDT from EDT.

Times of AEDB and Scheduler are not in sync.
The following messages are observed from the scheduler log:

[09/17/2020 08:46:29] CAUAJM_I_40218 **** Time offset between AutoSys and Event Server 1 is 3,600 seconds. ****

[09/17/2020 08:46:30] CAUAJM_I_40211 Using TZ = America/New_York.


Scheduler:

$ date
Thu Sep 17 16:19:38 EDT 2020

Database:

SQL> SELECT SESSIONTIMEZONE, CURRENT_TIMESTAMP FROM DUAL;

SESSIONTIMEZONE
---------------------------------------------------------------------------
CURRENT_TIMESTAMP
---------------------------------------------------------------------------
-04:00
17-SEP-20 04.16.57.073879 PM -04:00

Note: The CURRENT_TIMESTAMP returns the current date and time in the session time zone not the system date and time.