Example 1: Time zones

This example shows how a specific location is assigned to a time zone and how this location's time is reflected in reports.

The figure shows the contents of the LOCDATA member of DPMPARMS. In this example, we want to report data from a DB2 subsystem in San Francisco. The location name of the DB2 subsystem is USIBMSTOSQL1.
Figure 1. Time Zone Data 1

 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   1           00   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 column shows the time zone of the location relative to GMT. San Francisco is 8 hours west of Greenwich.

No value is specified in the CPU Clock column to indicate that the CPU clock is set to GMT. If you do not specify a value for the CPU clock, you do not have to change the default direction (1).

In this example a default (*) is specified for locations that do not have an individual entry. If you do not specify a default, no time zone adjustment is made to data from locations that do not have an entry.

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 applied during OMEGAMON for Db2 Performance Expert processing:
  • Data from location USIBMSTOSQL1 is adjusted -8 hours because its CPU clock is set to GMT and its local time is eight 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.

The reported data reflects San Francisco local time.

The local time is used in FROM/TO processing, printed on reports, and stored in the File and Save data sets.