×
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.
I tied a few error handling options on Saturday. I used QMHSNDPM to send
appropriate error messages, but DFU and STRSQL don't display them. DFU just
reports:
"Message CPF502B was issued."
STRSQL only reports that a Trigger failure occurred.
The "real" error message gets reported in the Job Log, but is not provided
to the user.
I tried using QMHRCVPM to cherry pick the message off the call stack
message queue, but that didn't really work either. The Trigger program
wouldn't know what call stack entry to send to. The tendency is to send to
the message queue of one of the database manager, but those message queues
are deleted before control is returned to the application. If you send to
an *ESCAPE to a queue too high in the call stack, that causes the
application to end, or even the 5250 session to end.
I tried Booth's suggestion of outputting messages to a Window overlay
defined in the Trigger. That works well for 5250 clients such as DFU and
STRSQL. But what about Web and PC application clients?
It appears that *ESCAPE messages issued by Constraints have the same
shortcomings as those issued by Triggers.
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.
midrange.com
