Browse Prior Art Database

Usage of Two Timezone Parameters Per Location

IP.com Disclosure Number: IPCOM000122406D
Original Publication Date: 1991-Dec-01
Included in the Prior Art Database: 2005-Apr-04
Document File: 4 page(s) / 186K

Publishing Venue

IBM

Related People

Elliott, P: AUTHOR [+3]

Abstract

Disclosed is a process that allows increased ease of use and additional functionality when reporting on data from multiple locations in different timezones by specifying two timezone parameters for each location being reported upon.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 33% of the total text.

Usage of Two Timezone Parameters Per Location

      Disclosed is a process that allows increased ease of use
and additional functionality when reporting on data from multiple
locations in different timezones by specifying two timezone
parameters for each location being reported upon.

      When producing reports from a single location, it was only
necessary to have a single TIMEZONE parameter (at most).  However,
when we attempted to produce reports incorporating data from multiple
locations which could be from different timezones, and have
independent clocks, it became necessary to have not only one timezone
per location, but two timezones per location.

      One timezone parameter for the location can be thought of as
allowing the times collected in that timezone to be adjusted to a
common time (e.g., GMT).  The second timezone parameter for the
location can be thought of as adjusting the times collected for that
location to the timezone that they will be printed in.
Description

      A performance reporting system produces reports that can
include data from multiple Database Management System (DBMS)
locations.  The data is collected by the DBMS, and (most) time values
are STCK (store clock).  The definition of STCK is that it is the
time known to the hardware and should be set to GMT.  However, MVS
also keeps a local time. At IPL time, local time is originally set
based upon applying a timezone parameter from SYS1.PARMLIB to the
value of the STCK.  However, MVS also has a SET command that allows
an operator to adjust the local time of the system at any time.
After the local time has been reset, subsequent local times are still
based upon the STCK value, but the adjustment is no longer a simple
integer number of hours.

      The DBMS reports STCK values instead of local time, because if
the operator uses the MVS SET command to adjust the local times, the
local times reported before the SET command and those reported after
the SET command cannot be compared in any meaningful manner.

      Although the definition of STCK is that it is the time in GMT,
it is common for an installation to set the STCK to the current local
time.  These shops then specify a timezone of 0 in SYS1.PARMLIB.

      The data that the performance reporting system obtains from the
DBMS does not indicate whether or not the STCK values were correctly
set to GMT, nor what the difference between the STCK values and the
local time is for that system.
Adjust STCK value to print on report

      One of the two timezone parameters is essentially used to
convert the STCK value to the value that will print on a report.  The
value in the STCK can be either GMT, or the local time of the
location as described earlier.  (Note that it can also be any other
arbitrary value, but these are also handled and are not important).
The time that the user wants printed on the reports may be the local
time of the system that collected the data, the...