Paul Gilmartin wrote:
There is __no__ way to update the TOD clock other than via an ETR.
That z/OS can function as an NTP server, but not as an NTP client
is arrogant, perceived by non-mainframe-partisans as "radically
immature". Not everyone can be emperor.
That said, what are the practical considerations?
I know some of the IBMers will cringe at this, but the clock can be set
programmatically.
For example, consider the `operator prompt' line in the clockxx member.
This causes
message iea888a to be issued during ipl where `Resetting GMT time causes
the TOD
clock to be reset.' Manual also says the message is issued by
ieavrtod. Looking at this
module you can see that it does indeed issue the SCK (b204)
instruction. There are
considerations, such as getting the TOD clock synced on all CPUs, and if
the clock is fast,
you should probably spin for the appropriate interval instead of setting
the TOD clock into
the past.
Greg Smith
----------------------------------------------------------------------
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
