The agent dies when it tries to update DB2 with more characters in a field than it can contain. DB2 doesn't even get to really see it so the trigger program would never get fired off. Besides this is probably worse than the old batch processing environment since the user might type something to long and not find out about it till the next morning. Right now the "Input Validation" event tells them as soon as they exit the field and they have to try again.

Roger Vicker, CCP

On 1/23/2003 1:17 PM, wrote:


Any chance your iSeries can do field validation? For example, if you do your move, (via LS-ODBC or whatever the flavor of the day is), and the trigger program indicates a failure then report that back.

Rob Berendt

*** Vicker Programming and Service *** Have bits will byte *** ***
If it ain't broke yet, let me have a shot at it.

As an Amazon Associate we earn from qualifying purchases.

This thread ...


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

This mailing list archive is Copyright 1997-2021 by 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].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.