Since summer time (DST=Daylight Savings Time) CHASE Command always return MSG:
Article ID: 212718
Updated On:
Products
Issue/Introduction
Since our server has switched to summer time, that generate us ALARMs each time that job is executed:
Message:
<CAUAJM_I_50162 Job has been in the STARTING state more than 120 seconds. Manual intervention may be required.>
$ autorep -j %CHASE% -q
/* ----------------- AUTOSYS_ADMIN_CHASE ----------------- */
insert_job: AUTOSYS_ADMIN_CHASE job_type: CMD
command: chase -A -E
machine: localhost
owner: autosys
permission:
date_conditions: 1
days_of_week: mo,tu,we,th,fr,sa,su
start_mins: 00,15,30,45
term_run_time: 10
alarm_if_fail: 1
alarm_if_terminated: 0
- 1st Alarm took place on : event_demon.ACE.03282021:[2021/03/28 02:00:02] CAUAJM_I_40245 EVENT: ALARM ALARM: CHASE JOB: MY_JOB MACHINE: MY_MACHINE
- TimeZone for this instance is Europe/London
- DST occured on Sunday March 28 2021 @2:00AM
[2021/04/08 11:15:02] CAUAJM_I_40245 EVENT: ALARM ALARM: CHASE JOB:
[2021/04/08 11:30:02] CAUAJM_I_40245 EVENT: ALARM ALARM: CHASE JOB:
[2021/04/08 11:30:02] CAUAJM_I_40245 EVENT: ALARM ALARM: CHASE JOB:
[2021/04/08 11:30:02] CAUAJM_I_40245 EVENT: ALARM ALARM: CHASE JOB:
[2021/04/08 11:45:02] CAUAJM_I_40245 EVENT: ALARM ALARM: CHASE JOB:
[2021/04/08 12:00:02] CAUAJM_I_40245 EVENT: ALARM ALARM: CHASE JOB:
[2021/04/08 12:00:02] CAUAJM_I_40245 EVENT: ALARM ALARM: CHASE JOB:
[2021/04/08 12:00:02] CAUAJM_I_40245 EVENT: ALARM ALARM: CHASE JOB:
[2021/04/08 12:15:02] CAUAJM_I_40245 EVENT: ALARM ALARM: CHASE JOB:
[2021/04/08 12:15:02] CAUAJM_I_40245 EVENT: ALARM ALARM: CHASE JOB:
$ grep "ALARM: CHASE" *|wc -l
2457
$ grep -l "ALARM: CHASE" *|xargs ls -1tr| xargs grep "ALARM: CHASE"|head -1
event_demon.ACE.03282021:[2021/03/28 02:00:02] CAUAJM_I_40245 EVENT: ALARM ALARM: CHASE JOB: MY_JOB MACHINE: AGENT_MACHINE
When we launch chase -A -E manually, we don't have ALARM
$ chase -A -E|grep -e CAUAJM_I_50162 -e CAUAJM_I_40245|wc -l
0
Already done:
- Delete job AUTOSYS_ADMIN_CHASE and re-create.
- Restart Agents on Scheduler server & agent/client.
- sendevent -E KILLJOB -J AUTOSYS_ADMIN_CHASE
- sendevent -E CHANGE_STATUS -s TERMINATED -J AUTOSYS_ADMIN_CHASE
- sendevent -E FORCE_STARTJOB -J AUTOSYS_ADMIN_CHASE
Environment
Release : 11.3.6
Component : CA Workload Automation AE (AutoSys)
Cause
$ autorep -J AUTOSYS_ADMIN_CHASE -d
Job Name Last Start Last End ST/Ex Run/Ntry Pri/Xit
________________________________________________________________ ____________________ ____________________ _____ ________ _______
AUTOSYS_ADMIN_CHASE 2021/04/09 11:30:00 2021/04/09 11:30:01 SU 23866/1 0
Status/[Event] Time Ntry ES ProcessTime Machine
-------------- --------------------- -- -- --------------------- ----------------------------------------
STARTING 2021/04/09 11:30:00 1 PD 2021/04/09 10:30:01
RUNNING 2021/04/09 11:30:00 1 PD 2021/04/09 10:30:02
<Executing at WA_AGENT>
[*** ALARM ***]
CHASE 2021/04/09 11:30:01 0 PD 2021/04/09 10:30:02
<CAUAJM_I_50162 Job has been in the STARTING state more than 120 seconds. Manual intervention may be required.>
SUCCESS 2021/04/09 11:30:01 1 PD 2021/04/09 10:30:03
[CHK_TERM_RUNTIME] 2021/04/09 11:40:00 1 PD 2021/04/09 10:30:03
[STARTJOB] 2021/04/09 11:45:00 0 UP
<Event was scheduled based on job definition.>
The ProcessTime in the autorep output shows an hour difference with the Time.
This ProcessTime is coming when Autosys writes the event into the database.
As the STARTING and RUNNING event has ProcessTime of 1 hour difference, which means that for Autosys it is already 1 hour in this state, the chase will send an alarm.
Scheduler server:
$ date
Fri Apr 9 13:20:43 BST 2021
$ env | grep TZ
TZ=Europe/London
DB server:
# date
Fri Apr 9 12:21:58 GMT 2021
Resolution
DB server needs to be in same timezone as autosys server
Feedback
