On 5/11/2021 1:40 AM, Steve Austin wrote:
And apparently, "someone pointed out that the hardware clock was 1 minute
out, so a minute was added". I don't know, but my guess is that the person
setting up the Jenkins builds noticed the clock was wrong.
We experienced significant clock drift on our z13s. (I can't understand
why IBM makes STP optional and pricey. All Z machines should be able to
synchronize to NIST.)
This discrepancy wreaked havoc for our folks trying to use the mainframe
as a GIT repository, so we decided to correct the issue in CLOCKxx
exactly as described in this thread.
Where a shop with STP and no clock drift might see this in their CLOCKxx
member:
TIMEZONE W.08.00.00
ours would say (for example):
TIMEZONE W.07.58.12
and this would be adjusted roughly every month to keep us within a
second or two of the real time shown on every Windows workstation in our
Enterprise.
Our z15 has gone through a full POR several times since being installed
in August 2020 (see the video https://youtu.be/uis-8s_O1K8), the most
recent one being just a few weeks ago. So, it's difficult to know yet if
similar adjustments will be required. If they are, we stand ready to
adjust our CLOCKxx member as needed.
--
Phoenix Software International
Edward E. Jaffe
831 Parkview Drive North
El Segundo, CA 90245
https://www.phoenixsoftware.com/
--------------------------------------------------------------------------------
This e-mail message, including any attachments, appended messages and the
information contained therein, is for the sole use of the intended
recipient(s). If you are not an intended recipient or have otherwise
received this email message in error, any use, dissemination, distribution,
review, storage or copying of this e-mail message and the information
contained therein is strictly prohibited. If you are not an intended
recipient, please contact the sender by reply e-mail and destroy all copies
of this email message and do not otherwise utilize or retain this email
message or any or all of the information contained therein. Although this
email message and any attachments or appended messages are believed to be
free of any virus or other defect that might affect any computer system into
which it is received and opened, it is the responsibility of the recipient
to ensure that it is virus free and no responsibility is accepted by the
sender for any loss or damage arising in any way from its opening or use.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
