Re: Is the *HIVAL & *LOVAL the same for a time field?

select time('24.00.00') - 
time('00.00.00') from sysibm/sysdummy1
240,000

Which is basically what you want with a *hival or a *loval comparison on 
time, right?

I guess they could have made *HIVAL be 23.59.59.  However what would be 
business case be for that?  If I want to now how much time I have before 
the next day wouldn't I want 
24.00.00-current time
and not
23.59.59-current time?
If I had a time in my database as 23.59.59 and I wanted to start at the 
end and read backwards with RPGLE I guess either would work.  However if I 
wanted to take that hival, convert it to a string and concatenate that on 
to a date against a possible timestamp of ...23.59.59.012345 I'd rather 
have the 24.00.00.

Rob Berendt