ibm-information-center/dist/eclipse/plugins/i5OS.ic.rzati_5.4.0.1/rzatitimemainapp.htm

97 lines
7.2 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 maintenance application" />
<meta name="abstract" content="Use this information to learn how a typical time maintenance application works. You can also view an example environment that uses Simple Network Time Protocol (SNTP) as a time maintenance application." />
<meta name="description" content="Use this information to learn how a typical time maintenance application works. You can also view an example environment that uses Simple Network Time Protocol (SNTP) as a time maintenance application." />
<meta name="DC.Relation" scheme="URI" content="rzaticoncepts.htm" />
<meta name="DC.Relation" scheme="URI" content="rzatitimeadj.htm" />
<meta name="DC.Relation" scheme="URI" content="rzatisetuptimemain.htm" />
<meta name="DC.Relation" scheme="URI" content="../rzakz/rzakzqtimadj.htm" />
<meta name="DC.Relation" scheme="URI" content="../rzakt/rzaktkickoff.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="rzatitimemainapp" />
<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 maintenance application</title>
</head>
<body id="rzatitimemainapp"><a name="rzatitimemainapp"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">Time maintenance application</h1>
<div><p>Use this information to learn how a typical time maintenance application
works. You can also view an example environment that uses Simple Network Time
Protocol (SNTP) as a time maintenance application.</p>
<p>A time maintenance application maintains the system time with an external
time source. Each time maintenance application is unique and is programmed
differently. However, the overall purpose of a time maintenance application
is to retrieve a time value from an external time source and compare it to
the system's time value. If the two values differ, a time adjustment begins.
The amount of time that the two values must differ before a time adjustment
begins is unique to the actual time maintenance application that you are using.</p>
<p>Use the time adjustment (QTIMADJ) system value to identify the software
to use to adjust the system clock to keep it synchronized with an external
time source. The system does not enforce the software specified; it only identifies
the software to use. This value should be maintained by the time adjustment
software and is intended as an aid to prevent having multiple time adjustment
applications conflict with each other. The system does not verify this value
or that this software is or is not performing time adjustments. IBM<sup>®</sup> time adjustment
offerings use identifiers that start with QIBM such as QIBM_OS400_SNTP. Other
software suppliers should follow a similar naming convention of company name
and product name.</p>
<p>Time adjustment software should check this system value before starting.
If this system value has an identifier for other time adjustment software,
then the software being started should notify the user of this potential conflict
and confirm that this time adjustment software should be started. When there
is no identifier associated with this system value, the software should update
this system value to identify that it is now responsible for adjusting the
system clock. Time adjustment software should check this system value again
before ending. This system value should be set to 'None' only if the current
value identifies this time adjustment software that is ending.</p>
<p>You can use the SNTP application to maintain your system time. The SNTP
application is an IBM-supplied time maintenance application that you can use
as a client, server, or both.</p>
<div class="fignone" id="rzatitimemainapp__client"><a name="rzatitimemainapp__client"><!-- --></a><span class="figcap">Figure 1. SNTP as a client and a server</span><br /><img src="rzati501.gif" alt="Server A is the SNTP server and client" /><br /></div>
<p>In <a href="#rzatitimemainapp__client">Figure 1</a>, the iSeries™ server
(Server A) uses the SNTP application as a client and a server. The SNTP client
retrieves a time value from an external time source. The external time source
is determined by what you specify to use. The SNTP application synchronizes
Server A's coordinated universal time (UTC) with the time value from the external
time source. Then, the SNTP server (Server A) sends the time value to all
SNTP client systems (iSeries Server B and Client A) connected to it.</p>
<div class="fignone" id="rzatitimemainapp__sntp"><a name="rzatitimemainapp__sntp"><!-- --></a><span class="figcap">Figure 2. SNTP as a server</span><img src="rzati502.gif" alt="Server A is the SNTP server" /></div>
<p>In <a href="#rzatitimemainapp__sntp">Figure 2</a>, the iSeries Server
A uses the SNTP server. In this situation, the UTC time is retrieved from
the iSeries server
rather than being synchronized with an external time source. This internal
time value is sent to all SNTP client systems (iSeries Server B and Client A) connected
to it.</p>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaticoncepts.htm" title="Use this information to understand time management concepts such as time zones, coordinated universal time (UTC), and daylight saving time (DST).">Concepts</a></div>
</div>
<div class="relconcepts"><strong>Related concepts</strong><br />
<div><a href="rzatitimeadj.htm" title="Learn how a time maintenance application automatically adjusts system time and how you can manually make time adjustments to the system time. Also, learn how a time adjustment is different from manually setting the time of day system value and why a time adjustment is the preferred method when changing the system time.">Time adjustment</a></div>
<div><a href="rzatisetuptimemain.htm" title="Find out how to use a time maintenance application to make the necessary adjustments to your system time.">Set up time maintenance</a></div>
</div>
<div class="relref"><strong>Related reference</strong><br />
<div><a href="../rzakz/rzakzqtimadj.htm">Time adjustment (QTIMADJ) system value</a></div>
<div><a href="../rzakt/rzaktkickoff.htm">Simple Network Time Protocol</a></div>
</div>
</div>
</body>
</html>