RE: Strange behaviour on a numeric field in a DSPF

Can we step back a moment?  What is the business problem you're trying
to address?  What do the users want to happen if they type in "3 1.0"?
And why are they typing it that way?  In the 5250 world, you would
simply type in 3 and the field exit key; that's the way the 5250
interface works.

If you want your user's data entry to act like a browser, use a browser.
Then you can do whatever you want -- you can clear the field when the
user tabs into it, or when they type a character. 

On the 5250, however, it is working as designed, so you have one of
several options:

1. Use an alphameric field and test and convert the data yourself.

2. Display the data as output only, and have a second field where they
can key in the data to override the original field.  Always clear this
second field before displaying it to the user.

3. Redisplay the data and ask the user to verify that what they entered
is correct.

There are others.  The point is that the 5250 works the way it does and
has worked that way for decades.  It won't change.  So you have to write
your program to work with it.

Joe


> From: Krish Thirumalai
> 
> I did think of that, but the issue is the value the display file
> returns to the program is numerically valid 301.00.
> 
> IMHO, this should have stopped this in the first place before it even
> gets to the program. since 3 1.0 is not a valid numeric in a numeric
> field.