RE: How did DST go for you

[<lgoodbar@xxxxxxxxxxxxxx>]

I feel for you. Kronos' instructions for updating Workforce Central were
not the clearest. I actually started my DST planning in January so I
could understand all the changes. Basically, for WFC and DCM, you needed
to update to the latest service pack, initialize the time clocks so they
receive the latest timezone data, and update the JRE on both the WFC
server and clients. With three locations to update, testing was very
important for us.

Kronos needs to be updated, but you could synchronize the clocks' time
with the communications PC. More important for WFC users was the Java
runtime updates that understand the new timezones.

I don't have the iSeries product, so can't say what procedures are
needed for DST compliance.

Loyd Goodbar
Senior programmer/analyst
BorgWarner
TS Water Valley
662-473-5713

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Scott Klement
Sent: Tuesday, March 13, 2007 12:00
To: Midrange Systems Technical Discussion
Subject: Re: How did DST go for you

We're having problems with Kronos and the 4500 clocks as well.  (Though,

that's the only type of clock we have.)  Apparently, the guy on our 
staff who maintains the Kronos system did not understand that anything 
had to be done for daylight savings time until it didn't work.  So now 
we have to update the software to a version that's compatible with the 
new daylight savings time changes..  Ugh... this is a lot of work just 
to change the clocks by an hour!!

Alberta Lochridge wrote:
> We had problems with the 4500 kronos clocks also.  No problems with
the
> older clocks