ibm-information-center/dist/eclipse/plugins/i5OS.ic.rzahx_5.4.0.1/rzahx3b6.htm

78 lines
5.3 KiB
HTML

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html lang="en-us" xml:lang="en-us">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<meta name="security" content="public" />
<meta name="Robots" content="index,follow" />
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
<meta name="DC.Type" content="concept" />
<meta name="DC.Title" content="Time zone considerations for Collection Services" />
<meta name="abstract" content="When you review and analyze performance data, the actual local time of the collection can be significant." />
<meta name="description" content="When you review and analyze performance data, the actual local time of the collection can be significant." />
<meta name="DC.Relation" scheme="URI" content="rzahx3b4.htm" />
<meta name="DC.Relation" scheme="URI" content="rzahxcollectdatacs.htm" />
<meta name="DC.Relation" scheme="URI" content="../rzakz/rzakzqtime.htm" />
<meta name="DC.Relation" scheme="URI" content="../rzakz/rzakzqutcoffset.htm" />
<meta name="copyright" content="(C) Copyright IBM Corporation 1998, 2006" />
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 1998, 2006" />
<meta name="DC.Format" content="XHTML" />
<meta name="DC.Identifier" content="rzahx3b6" />
<meta name="DC.Language" content="en-us" />
<!-- All rights reserved. Licensed Materials Property of IBM -->
<!-- US Government Users Restricted Rights -->
<!-- Use, duplication or disclosure restricted by -->
<!-- GSA ADP Schedule Contract with IBM Corp. -->
<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
<link rel="stylesheet" type="text/css" href="./ic.css" />
<title>Time zone considerations for Collection Services</title>
</head>
<body id="rzahx3b6"><a name="rzahx3b6"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">Time zone considerations for Collection Services</h1>
<div><p>When you review and analyze performance data, the actual local
time of the collection can be significant.</p>
<p>For example, you may need to be sure which data was collected during the
busiest period of the day so that it represents the heaviest workload experienced
by the system under review. If some of the systems from which you collect
performance data are located in different time zones, you should be aware
of these considerations:</p>
<ul><li>When you start Collection Services for a system group, you start Collection
Services at the same time on all systems in the group. Any differences in
system time and date settings due to some systems being located in different
time zones are not taken into account.</li>
<li>If you start Collection Services with the Management Central scheduler,
the time at which the scheduler starts the task is based on the system time
and date of your central system in Management Central.</li>
<li>The management collection objects for each endpoint system reflect start
and end times based on the QTIME and QUTCOFFSET (coordinated universal time
offset) system values of that endpoint system and your central system. If
the endpoint system is in a different time zone from your central system,
and these system values are correctly set on both systems, the start and end
times reported for collection objects are the actual times on the endpoint
system. In other words, the start and end times reflect the value of QTIME
on the endpoint system as it was at the actual point in time when those events
occurred.</li>
<li>The scheduling of a performance collection can cross a boundary from standard
time to daylight saving time or from daylight saving time to standard time.
If so, this time difference should be taken into account when scheduling the
start time. Otherwise, the actual start and end times can be an hour later
or earlier than expected. In addition, the reported start and end times for
management collection objects are affected by this difference unless the QUTCOFFSET
system value is adjusted each time the change to and from daylight saving
time takes effect.</li>
</ul>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzahx3b4.htm" title="When you use Collection Services to collect performance data, you control what data is collected and how often it is collected.">Customize data collections</a></div>
</div>
<div class="relconcepts"><strong>Related concepts</strong><br />
<div><a href="rzahxcollectdatacs.htm" title="Use Collection Services to collect performance data for later analysis by the Performance Tools for iSeries licensed program or other performance report applications, iSeries Navigator monitors, and the graph history function. (If you prefer viewing real-time performance data, system monitors provide an easy-to-use graphical interface for monitoring system performance.)">Collection Services</a></div>
<div><a href="../rzakz/rzakzqtime.htm">QTIME</a></div>
<div><a href="../rzakz/rzakzqutcoffset.htm">QUTCOFFSET (coordinated universal time offset)</a></div>
</div>
</div>
</body>
</html>