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.

Figure 1. Time Zone Data 3

 DGOPPLDS                  Time Zone Data Editor                Row 1 to 3 of 3

 Direction (1=East 2=West)
 Action  Location           --   Time Zone  --   --   CPU Clock   --

                            Direction   HH   MM   Direction   HH   MM
 ____    USIBMSTOSQL1       2           08   00   1           00   00
 ____    USIBMSTOSQL2       2           05   00   2           05   00
 ____    *                  1           00   00   1           00   00
 ******************************* Bottom of data ********************************




 Command ===> ______________________________________________________________
  F1=Help    F2=Split   F3=Exit    F7=Up      F8=Down    F9=Swap   F12=Cancel
The time zone settings for both locations reflect the local time at that site:
  • 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 one location is set to GMT and the other to the local time:
  • 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.
Again, if you want to use San Francisco local time in your reporting, specify location USIBMSTOSQL1 as your TIMEZONE location: 
 
GLOBAL
   TIMEZONE (USIBMSTOSQL1)
The following adjustments are made during Performance Expert processing:
  • 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.