McKown, John wrote:
Ed Jaffe wrote:
Issue a daily SET TIMEZONE= command to adjust the local time
as necessary.
Well, we are planning on doing a T CLOCK=. In what way would a T
TIMEZONE= be better? Oh, and just to myself, I don't really like this
too very much. But then, I'm just an old grump.
SET TIMEZONE is superior to SET CLOCK because the amount of time
required to process the command is not a factor.
Suppose you have a single system and you queue the command at exactly
the right time. The local time will be ever so slightly behind because
there is always a delay between the time you issue the command and when
it is recognized and processed by the system. Even worse, suppose you
have a 3-way sysplex and you issue RO *ALL,SET CLOCK=12.00.00. Each
system will process the command at a slightly different time than will
the other two. Therefore, all three systems' local times will be
slightly out-of-sync even if they are all sharing the same TOD!
These problems cannot occur with SET TIMEZONE. That's why I authored the
SHARE requirement asking for it.
--
Edward E Jaffe
Phoenix Software International, Inc
5200 W Century Blvd, Suite 800
Los Angeles, CA 90045
310-338-0400 x318
[EMAIL PROTECTED]
http://www.phoenixsoftware.com/
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
