×
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.
Hi Jim,
However, there is nothing in the ERRC0100 parms that include the message
file the message id came from (unlike most of the QMH API's which do).
FWIW, I completely agree with you. It's frustrating that the message
file name isn't in there somewhere.
My solution is to set the bytes provided field to 0, and let the API
send me an escape message. Then I trap the escape message and use the
QMHRCVPM API to read the message details -- which DOES include the
message file. Though, at that point, I don't really need it, because I
can retrieve the displayable text from the escape message directly, so
no longer need to call QMHRTVM.
This solution runs a little slower because the OS has to treat it as an
exception (Which isn't fast), plus I need to go back and clean up the
error messages from the job log (often there's the escape message as
well as some previous diagnostic messages, which can be a pain to clean
up.) But usually I'm not too concerned with the performance of
errors.... Usually if there's an error it means something is wrong, and
I can abort whatever I'm doing.
It's just really unfortunate that IBM couldn't have made this easier for us.
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
