Re: Strange behaviour on a numeric field in a DSPF

After looking at the documentation i realized that IBM has added a
keyword VALNUM that can be added to a numeric field that resolves this
issue.

VALNUM (Validate Numeric) keyword for display files 

Use this file-, record-, or field-level keyword to enhance the error
checking performed against fields with data type numeric only. When
specified on a numeric only field, this keyword causes an error
message to be returned if the user attempts to embed a SPACE, PLUS
SIGN or MINUS SIGN between numeric digits in the field or when the
PLUS SIGN or MINUS SIGN precedes the numeric digits.

The field containing the VALNUM keyword must be defined as an
input-capable field with the data type Y.

The business problem we were having is that our customer is expecting
the 5250 to function like a browser since the users he has on the
warehouse floor are expecting it to work that way. This is
particularly true for users who are seeing the 5250 screen on a small
RF gun.  The user on the floor keys a 1 realizes that is is a mistake
and then uses the arrow keys to navigate to the numeric field and keys
a 3 expecting the value to be 3, uses the arrow keys again does some
more data entry and then hits enter.

Now that we have used this keyword, we have resolved the issue, but
the next thing i have to worry about is how to add this keyword to all
our display files :-)

Thanks

Krish

On Wed, 2 Mar 2005 14:35:40 -0600, Joe Pluta <joepluta@xxxxxxxxxxxxxxxxx> wrote:
> 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.
> 
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
> 
>