Re: How is it possible to have invalid time in a time field?

On 03/11/2007, at 2:12 AM, Booth Martin wrote:

I get the information from debug. it says the value is '24.00.00'

24:00:00 is a valid time. It is effectively equivalent to 00:00:00-- although one can think of 00:00:00 as beginning of day and 24:00:00 as end of day. Search the archives for a discussion on these two time values (and, if I recall correctly, example code showing the effect of calculations using them).

The field is filled with the statement " eval wTime = %time(*hival)

That's not valid syntax (although I can see why you might try that). Simply assign *LOVAL or *HIVAL to the time field. Don't bother wrapping it with the built-in function.

EVAL wTime = *HIVAL;

will work.

Documentation of %TIME says nothing about using figurative constants but attempting it results in a compiler error: RNF7511 - The operand *HIVAL is too small to contain a complete *ISO time.

How did you manage to get your code to compile?

Regards,
Simon Coulter.
--------------------------------------------------------------------
FlyByNight Software OS/400, i5/OS Technical Specialists

http://www.flybynight.com.au/
Phone: +61 2 6657 8251 Mobile: +61 0411 091 400 /"\
Fax: +61 2 6657 8251 \ /
X
ASCII Ribbon campaign against HTML E-Mail / \
--------------------------------------------------------------------