Example 3: Time zones and CPU clock settings
This example shows how to report data from two locations. The first location, USIBMSTOSQL1, is situated in San Francisco, the second, USIBMSTOSQL2, in New York.
- The time zone of location USIBMSTOSQL1 is San Francisco, 8 hours less than the GMT.
- The time zone of location USIBMSTOSQL2 is New York, 5 hours less than the GMT.
- The CPU clock of location USIBMSTOSQL1 is set to zero to indicate GMT.
- The CPU clock of location USIBMSTOSQL2 is set to five to indicate the New York local time.
GLOBAL TIMEZONE (USIBMSTOSQL1)
- Data from location USIBMSTOSQL1 is adjusted -8 hours because its CPU clock is set to GMT.
- Data from location USIBMSTOSQL2 is adjusted -3 hours because its CPU clock is set to New York local time, which is 5 hours less than GMT.
- Data from locations that do not have an entry is adjusted -8 hours because the default CPU clock setting (*) is GMT, as shown in Figure 1.
As a result, data from all locations reflects San Francisco local time.
For more information about time zone processing, refer to the description of the GLOBAL command in the Report Command Reference.