Kris wrote:
As far as I understand, CICS uses the local time in its logs, not UTC (and
that's the reason that CICS must be kept down). So keeping CICS down for
an hour will be enough. What the HW clock is doesn't matter for CICS.
So I would need CICS to be down 1 hour *IF* I was
changing
SFS will anyhow scan its logs to check what it has to do at restart
(rollback/foward recovery from last checkpoint/xxx),
and this not only after the clock change,but maybe also a bit later if it
were to abend.
Maybe you can execute the procedure Replacing Both File Pool Log
Minidisks, chapter
Here in Israel we have already changed our clocks back,
but I need to understand a bit more about how CICS journaling
works with time changes.
Until now, we have always had our hardware on local time.
(As you may guess, the Israel Police Dept. is not exactly
a multinational globe-spanning
As far as I understand, CICS uses the local time in its logs, not UTC (and
that's the reason that CICS must be kept down). So keeping CICS down for an
hour will be enough. What the HW clock is doesn't matter for CICS.
But, if you'd have DB2, that will use UTC -or more exact: the HW clock- in
its
