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

In one program I have a statement " eval RTIME = %time(*hival). In the next program the field RTIME is a parm for a procedure. The line to call a procedure fails before the attempt to make the call with the message that the value in the field is invalid. There is no user involvement.

At least, thats the way it appears to me. There may be a *duh* in there somewhere but it is stumping me at the moment.

Trevor Perry wrote:

Why do you have to show the customer the data from the file. If it is
00.00.00 in the file, you can always display 24.00.00 to the user... Or is
the user programming now?




On 11/2/07 11:40 AM, "Booth Martin" <booth@xxxxxxxxxxxx> wrote:

Thats the beginning of my problems. The customer wants midnight to be
24, not 0. The manual lists 24 as being valid.

RPG Format Name Description *LOVAL *HIVAL Default Value
*HMS Hours:Minutes:Seconds 00:00:00 24:00:00 00:00:00
*ISO International Standards Organization 00.00.00 24.00.00 00.00.00
*USA IBM USA Standard. AM and PM can be any mix of upper and lower
case. 00:00 AM 12:00 AM 00:00 AM
*EUR IBM European Standard 00.00.00 24.00.00 00.00.00
*JIS Japanese Industrial Standard Christian Era 00:00:00 24:00:00
00:00:00