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

[Booth Martin <booth@xxxxxxxxxxxx>]

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




Trevor Perry wrote:
> Booth,
>
> You might find that 24.00.00 is invalid. 00.00.00 and 23.59.59 are ok.
>
> Try that..
> Trevor
>
>
>
> On 11/2/07 11:12 AM, "Booth Martin" <booth@xxxxxxxxxxxx> wrote:
>
>   
> > I get the information from debug.  it says the value is '24.00.00'
> >
> > The field is filled with the statement " eval wTime = %time(*hival)
> >
> >
> >
> >
> > Wilt, Charles wrote:
> >     
> > > Note that this would mean the field doesn't actually contain 24:00:00.
> > >
> > > Where are you getting the diea that it does?
> > >
> > > Charles
> > >
> > >       
>
>
>