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



Rob,

I agree that missing the library/name of the message file is major flaw in
the API error structure, and has caused me grief many times in the past!

I don't think that the MSG or SECLVL data are needed, however.  Those two
items would take up a significant amount of memory, and for every API to
have to add code to populate them seems a little silly when we can easily
retrieve them w/QMHRTVM if we want them -- or simply send a program
message to our caller.

But in order to really use the API error structure with either QMHRTVM or
with QMHSNDPM, we REALLY need that message file name and library!!


On Tue, 6 Jan 2004 rob@xxxxxxxxx wrote:
>
> Missing these makes it hard to take the exception data and parse
> it down into meaningful information.  Perhaps I need to make a DCR to add
> another structure that also contains the following of RCVMSG:  MSGF,
> MSGFLIB, MSG, SECLVL.  What do y'all think?
>

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.