Example 2: CPU clock settings

This example demonstrates how to report data from location USIBMSTOSQL1. The only difference to example 1 is that the CPU clock of the location is set to New York local time. This is because the head office of the company is situated in New York.

Figure 1. Time Zone Data 2


 DGOPPLDS                  Time Zone Data Editor                Row 1 to 2 of 2

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

                            Direction   HH   MM   Direction   HH   MM
 ____    USIBMSTOSQL1       2           08   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 value specified in the CPU Clock column shows that the CPU clock of location USIBMSTOSQL1 is set to New York local time, which is five hours west of Greenwich.

A default (*) has been defined for locations that do not have an entry in the data set.

Suppose you again want to use San Francisco local time in your reporting. Specify location USIBMSTOSQL1 as your TIMEZONE location:

 
GLOBAL
   TIMEZONE (USIBMSTOSQL1)

Because the time zone for location USIBMSTOSQL1 is eight hours west of Greenwich, the following adjustments are made during Performance Expert processing:

Data from location USIBMSTOSQL1 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.