• Subject: RE: Validating a member name
  • From: "Kahn, David [JNJFR]" <DKahn1@xxxxxxxxxxxxx>
  • Date: Thu, 9 Sep 1999 16:35:19 +0200


>I considered using Joel's suggestion of CHECK(VN), but the field
>does not always have to be entered

That's why Charlie Massoglia suggested you use DSPATR(MDT) in addition to
CHECK(VN). It forces the system to treat the field as though it has been
entered so the validation is always performed even if the user doesn't touch
it. You might still want to check it out although Al's method is also a good
one. Another string to your bow and all that.

Dave Kahn
Johnson & Johnson International (Ethicon) France
Phone : +33 1 55 00 3180
Email :  dkahn1@jnjfr.jnj.com (work)
           dkahn@cix.co.uk      (home)

-----Message d'origine-----
De: Fisher, Don [mailto:DRF@HeiligMeyers.com]
Date: 09 September 1999 14:26
: 'MIDRANGE-L@midrange.com'
Objet: RE: Validating a member name

Thank you all for your insightful responses.  

I apologize for not being clear about my intent.  I am validating the member
name for syntax, not for existence.

For anyone who is interested, I defined a command as Al suggested with a CL
program that does nothing.  My RPGIV program then calls QCMDEXC with the
error return indicator specified.  Works marvelously.

I considered using Joel's suggestion of CHECK(VN), but the field does not
always have to be entered and CHECK(VN) cannot be conditioned based on a
value in another field on the screen.  At least, not to my knowledge,
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com

This thread ...

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].