At 03:23 PM 6/15/2005, you wrote:
...
If doing a periodic "T CLOCK=hh.mm.ss" is sufficient, then I'd cheat.
I'd have a PC which is running a TN3270E emulator. This emulator would
connect to z/OS as a console (Visara, 2074, ICC, or SMCS console). Have
this PC sync its clock via the Internet. Have this PC run a script
periodically which issues the "T CLOCK=hh.mm.ss".
If you don't want a PC with a console, use a PC that somehow does the
same thing. But you will need a PC somehow telling something on z/OS to
issue the above command.
There is __no__ way to update the TOD clock other than via an ETR.
--
John McKown
Senior Systems Programmer
UICI Insurance Center
Information Technology
Ah, but the local time reported to users via the TIME macro, etc, is TOD
clock +/- CVTTZ or CVTLDTO, both of which come from the CLOCKxx member. A
tweak of these fields will tweak the reported local time. If there were a
time service client for MVS that would keep the time synced correctly,
presumably this is how it would do it.
The T CLOCK= idea is a good one; it may be that a rexx exec or small
program could get the time from the net and issue the command; it could
run periodically, and even limit the amount it adjusted the time by (so the
clock doesn't jump 5 minutes the first time it runs after an IPL :-)
-- Jim Blalock
z/OS Support, Clemson University
(864) 656-3680
[EMAIL PROTECTED]
----------------------------------------------------------------------
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
