× 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.



Would it be possible, for interactive jobs, to do a *BEFORE trigger and handle the error in the trigger program itself with an error window? If the problem remains unresolved by the user then change the after-image to reflect the original image (no change made).



On Fri, Sep 19, 2014 at 2:34 PM, Nathan Andelin <nandelin@xxxxxxxxx> wrote:
Several pages in the new "modernization" redbook cover this topic. Rules
are written only once rather than embedding them in multiple applications
(ILE, Java, PHP, Ruby, .Net). The system enforces them, so you can't get
around them via utilities (such as DFU).

This idea makes sense to me from an architectural perspective. But I'm
struggling with exception handling.

I'm following Trigger coding examples from the following redbook:

http://www.redbooks.ibm.com/redbooks/pdfs/sg246503.pdf

Examples show using the QMHSNDPM API to signal *ESCAPE type messages. That
was causing a spooled program DUMP with every data validation exception - I
finally figured out how to prevent that.

I seems harsh to signal an exception which abnormally ends the Trigger
program - just for data validation errors. Error message appear in job
logs. But how do you get them to appear on the user's screen?

Nathan.
--





As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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

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.