Steve,

SETCLOCK will change the everything for you, but you have to do it
correctly.  You have to get TIMEZONE correct, and you have to have the TZ
variable set.  The biggest problem with how Cognos does this is that they
get the date this way and they get the time from the CLOCK intrinsic, so
around midnight you can really end up strange.  <plug>  our TimeWarp
software will allow you to change dates and times around without messing
with this kind of stuff, and for a 917 it's pretty darn cheap.  </plug>

shawn





Steve Hammond <[log in to unmask]> on 04/27/99 10:48:01 AM

Please respond to Steve Hammond <[log in to unmask]>

To:   [log in to unmask]
cc:    (bcc: Shawn Gordon/IS/FHM/FHS)
Subject:  Cognos and Hardware clock




I am doing Y2K testing on a leased 917. We are running through a yearly
processing cycle in about 2-3 months.

We use COBOL and PowerHouse for most of our applications.

Between 'nightly' runs, we use the SETCLOCK command to set the system date
to the next day.

But this sets the 'system' clock as opposed to the 'hardware' clock (as
reported to me by Cognos tech support). Cognos uses the 'hardware' clock
for reporting SYSDATE, therefore, even though a SHOWTIME tells me the
system date is 06/20/99, a QUIZ REPORT SYSDATE tells me the system date is
96/10/29.

Any hints on changing the hardware clock at the same time I change the
system clock?

steve hammond
aamc
washington dc