In [EMAIL PROTECTED], on 04/23/2006
at 06:08 PM, John S. Giltner, Jr. [EMAIL PROTECTED] said:
Any OS can support the hardware clock for the platform it is running
on to be set to local time or UTC.
Where did I imply that a OS can support hardware that is not
there?
The text that you quoted
From: [EMAIL PROTECTED] Subject: Re: TOD Clock the
same as the BIOS clock in PCs?
Date: Date: Mon, Apr 24 2006 4:36 am
which was probably brought to you by the same people who have a bizarre
collating sequence where zero follows 9 (see your local keyboard or
telephone keypad for
Shmuel Metz , Seymour J. wrote:
In [EMAIL PROTECTED], on 04/21/2006
at 10:48 PM, John S. Giltner, Jr. [EMAIL PROTECTED] said:
The OS can't support hardware that isn't there. And BTW, the TOD clock
is only part of the timing facilities on zSeries.
My original statement was:
Any OS can
On Thu, 20 Apr 2006 22:40:57 -0400, John S. Giltner, Jr. [EMAIL PROTECTED]
wrote:
[EMAIL PROTECTED] wrote:
I just like it when people do not focus on a specific question on
mine...Now...ONCE AGAIN...
Well, understood, but wouldn't the question have better been asked
on a list other than one
We can't tell you. This is dependent on the system that they are using.
To put this as simple as I can, the way I understand it:
1) Any OS can support the hardware clock for the platform it is running
on to be set to local time or UTC.
2) If the OS supports the hardware clock set to UTC it
In [EMAIL PROTECTED], on 04/21/2006
at 03:48 PM, John S. Giltner, Jr. [EMAIL PROTECTED] said:
1) Any OS can support the hardware clock for the platform it is
running on to be set to local time or UTC.
Alas, no.
It does not matter if it is a mainframe, a RISC box, PC, MAC, or any
other
On Fri, 21 Apr 2006 15:48:02 -0400, John S. Giltner, Jr.
[EMAIL PROTECTED] wrote:
We can't tell you. This is dependent on the system that they are using.
...
It also depends on how the time is set on the system at hand.
If the time is manually set then all bets are off. The most accurate
Shmuel Metz , Seymour J. wrote:
In [EMAIL PROTECTED], on 04/21/2006
at 03:48 PM, John S. Giltner, Jr. [EMAIL PROTECTED] said:
1) Any OS can support the hardware clock for the platform it is
running on to be set to local time or UTC.
Alas, no.
I guess my wording is a bit unclear. I
In a recent note, john gilmore said:
Date: Wed, 19 Apr 2006 18:47:02 +
STCKCONV and CONVTOD both use a table, the current instance of which can be
examined on page 7-189 of the z/Architecture principles of operation
publ.ication, SA-227632-04. (Worth noting is that this manual,
[EMAIL PROTECTED] wrote:
I just like it when people do not focus on a specific question on
mine...Now...ONCE AGAIN...
PLEASE answer this question for me?
1. Suppose I were to install Linux or FreeBSD again and during the
installation it
will ask me if I want to set my Hardware Clock to UTC or
In a recent note, john gilmore said:
Date: Tue, 18 Apr 2006 14:50:27 +
Two other IBM-supplied callable services are available:
o STCKCONV converts arbitrary, in general non-current ETOD values into
date-time ones; and
o CONVTOD converts an STCKCONV date-time value [back]
Paul,
There are some very erudite responses in this thread but I think I can deal
with this query.
There is an absolute reference point for time[1] which deals with any
adjustments the astronomers deem necessary and there are local conventions
over how far a locality differs from this absolute
In a recent note, Chris Mason said:
Date: Wed, 19 Apr 2006 16:05:34 +0200
Now I have to guess, but I expect that the clever astronomers predict the
need for leap seconds sufficiently in advance - and have them
internationally agreed - for the conversions built into z/OS or whatever
STCKCONV and CONVTOD both use a table, the current instance of which can be
examined on page 7-189 of the z/Architecture principles of operation
publ.ication, SA-227632-04. (Worth noting is that this manual, published in
2005 September, already included the EOY 2005 leap-second entry.)
These
In a recent note, john gilmore said:
Date: Wed, 19 Apr 2006 18:47:02 +
STCKCONV and CONVTOD both use a table, the current instance of which can be
examined on page 7-189 of the z/Architecture principles of operation
publ.ication, SA-227632-04. (Worth noting is that this manual,
[EMAIL PROTECTED] wrote:
I still do not quite really understand on how the application on
Mainframes log theit times compared to home PCs running UNIX...
I have been told that the TOD clock similar to the RTC/CMOS clock
inside a PC is running in UTC time..I understand that part...Now, the
Tim Shoppa wrote:
Anne Lynn Wheeler wrote:
section 4.6.1.4 setting and inspecting the clock (including some
description of UTC)
http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/DZ9AR004/4.6.1.4?SHELF=EZ2HW125DT=19970613131822CASE=
Interesting. So the hardware clock is actual ticks
Tim Shoppa's contention,
I believe this means that the clock time is actually more directly
related to the TAI timescale or
GPS hex time than UTC.
is in fact right on.
Like most discussions of dates and times here, this thread has failed to
make some necessary distinctions. The
Because Unix (and Linux) allow the CMOS/RTC clock to be set to one time
and then use a time zone offset to adjust the local time.
Windows does NOT allow this, the CMOS/RTC clock must be set to your
local time.
[EMAIL PROTECTED] wrote:
So, even though my UNIX machine's CMOS/RTC clock is set
Joel C. Ewing wrote:
My impression of the PC clock is that it was never intended for any
purpose other than maintaining wall clock time, and as such has
appropriately low resolution. My other impression is that there is some
Operating system involvement in maintaining its value on the PC:
In [EMAIL PROTECTED], on 04/17/2006
at 12:19 AM, Joel C. Ewing [EMAIL PROTECTED] said:
On the original S/360 introduced in 1964, I believe a System Timer,
which also required periodic interrupt servicing, was used to track
clock time and it had similar drift problems.
The interval timer
for a detail description of architecture operations ... the reference is
principles of operation
http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/DZ9ZR003/CCONTENTS?SHELF=DZ9ZBK03DN=SA22-7832-03DT=2004050412120
section 4.6 timing
[EMAIL PROTECTED] wrote:
Speaking in terms of Mainframes, What is TRUE UTC mean?
1. What does this mean??? I am still lost like crazy here...When they
speak in terms of setting the times as TRUE UTC, do they mean the
Hardware clock (TOD) is set to UTC and the Displayed time (the desktop
clock)
The TOD clock on IBM mainframes is an 8-byte hardware register than can
be stored by a special hardware instruction. It can be used to derive
wall clock time, but its other function is to provide a unique
time-stamp value that can be used for tracking and ordering system
events. As such it
24 matches
Mail list logo
