Using application commands with daylight saving time

When daylight saving time starts, the transition day has only 23 hours. When daylight saving time ends, the transition day has 25 hours. It includes two numerically identical hours:

  • 1:30 A.M. daylight saving time (occurs first)
  • 1:30 A.M. standard time (occurs an hour later)

Hence, for one hour each year, timekeeping must distinguish between repeated hours.

Related topic

Business-Time-2-0-commands

The dates that daylight saving time starts and ends change year by year and city by city. To accommodate this fluctuation:

  1. Convert all times to Greenwich mean time (GMT).
  2. Calculate your elapsed time.
  3. Use locale tables to convert the displayed times to local time.

The Java Timezone class contains the locale-specific information for these calculations.

In the following examples, assume that the AR System server is in Pacific Standard Time (US and Canada, GMT -8:00) and daylight saving time occurs on March 11, 2007, 2:00:00 A.M.

"Work" defines the available time window at Level 1 on March 11, 2007, from 12:00 A.M. to 5:00 A.M. on the Business Time Segment form.

Adding 1 hour to the start time scenario

$PROCESS$ Application-Bus-Time2-Add "3/11/2007 1:00:00 AM" "1" "3" "Work"

This command adds 1 hour to the start time and returns 1173607200 (that is, Sunday, March 11 03:00:00 A.M. PDT 2007).

Difference of 1 hour between start time and end time scenario

$PROCESS$ Application-Bus-Time2-Diff "3/11/2007 1:00:00 AM" "3/11/2007 3:00:00 AM" "Work"

The return value is 3600 seconds (that is, 1 hour).

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*