Re: Anyone using Triggers to enforce data validation & business rules? -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

It seems to me that if you keep the error reporting and repairing/ignoring withing the controls of the trigger program you will have reported the error to the user, gotten the user's response, and have resolved as best as can be resoslved any error the user created. The user will have either fixed it, or the action will have been rejected. In either case the user is aware of the issue. I suppose the trigger program might have already sent an email to a supervisor too, if that was your desire?

On 9/20/2014 8:02 PM, Nathan Andelin wrote:

My concern with relying on the application to deal with the errors is that
DFU, DBU, and many other programs are all ready written and there is
nothing reasonable you can do about that.

Good point. Thanks for suggesting it. Deploying a Window overlay within the
trigger program would solve the problem of reporting appropriate error
messages to 5250 interfaces, at least. I can extract the Job Type via the
QUSRJOBI API - if "I" for Interactive then show the error using Window
overlay.

I tried sending a *STATUS message to the *EXT message queue, but that
didn't work.

Nathan.

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

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