Hi All,

Environment:
        ARServer 6.3 Patch 21, Aix 5.2.0.9, Oracle 9.2.0.4.0 (local database), 
JDK 1.4.0_SR6
        Mid-Tier 6.3 Patch 21, Windows Server 2003 SP1, IIS 6, ServletExec 
5.0.0.13, JDK 1.6.0-b105
        User 6.03.00 Patch 20, Windows XP SP2, Internet Explorer 7.0.5730.11, 
JDK 1.6.0-b105
        Eastern Time - Currently EDT

I'm doing a bit of testing on our Dev Server for the upcoming DST change later 
this year.  I'm noticing something a bit odd with some of the math.

Here's are the values I'm seeing under the WUT:
        Database [Timestamp]
        1194152399 [11/4/2007 12:59:59 AM EDT]
        1194152400 [11/4/2007 1:00:00 AM EDT]
        1194156000 [11/4/2007 1:00:00 AM EST]
        1194156001 [11/4/2007 1:00:01 AM EST]
        1194159600 [11/4/2007 2:00:00 AM EST]

Here's what I'm seeing under Mid-Tier:
        Database [Timestamp]
        1194152399 [11/4/2007 12:59:59 AM EDT]
        1194152400 [11/4/2007 1:00:00 AM EDT]
        1194156000 [11/4/2007 2:00:00 AM EDT] Should be 1:00:00 AM (EST)
        1194156001 [11/4/2007 1:00:01 AM EST]
        1194159600 [11/4/2007 2:00:00 AM EST]

I'm also seeing something odd with the calculations for Remedy User, when 
subtracting Start Time from End Time to find Elapsed Time:
        Start Time: 1194152400 [11/4/2007 1:00:00 AM EDT] 
        End Time: 1194156000 [11/4/2007 1:00:00 AM EST]
        Elapsed Time: 0 seconds, which should be 3600 seconds

        Start Time: 1194156000 [11/4/2007 1:30:00 AM EDT] 
        End Time: 1194156000 [11/4/2007 1:00:00 AM EST]
        Elapsed Time: -1800 seconds, which should be 1800 seconds

And something similar for Mid-Tier:
        Start Time: 1194156000 [11/4/2007 should be 1:00:00 AM EST]
        End Time: 1194159600 [11/4/2007 2:00:00 AM EST]
        Elapsed Time: 0 seconds, which should be 3600 seconds

We had a problem last Fall from 1:00 AM EST to 1:59:59 EST, where Cases which 
were created between 1:00 AM EDT and 1:59:59 EDT were giving users an error 
when they tried modified them.  That error stopped being an issue at 2:00:00 
EST.  The error was that Remedy User was trying to update the Create Time 
field, and users did not have write access to do that, as our permissions only 
allowed write access to this field for Submitter.  Looking back at that, I'm 
thinking this above issues may have been a problem prior to Patch 20/21, but I 
am not certain.

Is anyone else having problems with the way the above dates are displayed, or 
the above calculations?

Eric Cleereman

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the 
Answers Are"

Reply via email to