Specific jobs are skipped or do not run at the mentioned time during DST switch.
This issue happens on all CA-WAAE supported OS.
This issue occurs only for jobs which have specific time zones like PST8DST.
During the DST switch, few jobs are running out of sequence and few are skipped.
If the jil of the job contains the “timezone” attribute (as below), where PST8DST is the timezone but this time zone does not exist at operating system level, the operating system cannot translate it to get the new time after the DST switch
timezone : PST8DST
Use Time Zone PST8PDT instead of PST8DST in the job definition
For example: timezone: PST8PDT
Timezone Attribute—Define the Time Zone
The timezone attribute defines the time zone for the job you are defining. For example, if you define a start time of 01:00 for a job running on a machine in Denver, and set timezone to San Francisco (which is in the Pacific time zone, one hour earlier than Denver), the job starts at 2:00 a.m. Denver time.
The start event for jobs with time-based starting conditions that do not specify a time zone is scheduled based on the time zone under which the scheduler is running. For more information about timezone attribute please refer the below link.
Release: ATSYHA99000-11.3.6-Workload Automation AE-High Availability Option