Greenwich Mean Time adjustments

Different z/OS images (logical systems) in the same data center can use different time zone settings.

Applications running on these images can share hardware and software resources, such as CPU, DASD, Db2 databases and so on.

For effective performance management and capacity planning, it is important to compare the performance measurements of applications and systems using the same physical time intervals.


Related topics

Overview-of-UIE

UIE Concepts

To achieve this goal, UIE internally represents all intervals and timestamps in Greenwich Mean Time (GMT) and automatically converts local timestamps to GMT timestamps. However, for your convenience, by default, it is assumed that SDATE, STIME, EDATE, and ETIME commands specify the start and end of the processing intervals in the local time zone of the system on which the UIE back end job is running.

You might have, however, some situations when you want to override the default behavior, for example, when the UIE job is running off the main data center site.

In this case, you can override this default using the GMTOFF subparameter of the SDATE command as shown in the following example, where the user wants to process data that is collected from 0000 to 2400 on May 27, with GMT offset-6.

Example

SDATE 2007-05-27 GMTOFF=-6

In this case, Universal Information Exchange processes SMF records corresponding to GMT intervals from 6:00 A.M. on May 27 to 6:00 A.M. on May 28.

You can review GMT offsets for each system found in the SMF/RMF file printed in the Universal Information Exchange Summary Report.

 

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