× 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'm a little new to this, but it seems the QMHRCVPM can only receive
messages within a job, not for another job (or thread, even). There's been
mention of losing call stack entries, otherwise the Retrieve Call Stack API
(only in v5r1) gives you the library. So far, that's the only place I can
see where this info is.

About the library list, I'm curious about how it would not be in effect
when you handler is called.

Ignore me if I'm nuts.  <bg>

At 05:55 PM 4/18/02 -0600, you wrote:

>From: Vernon Hamberg
>
> > You have to be IN the job, right? Actually in the same thread? Are you
> > looking for something that runs as a separate job?
>
>I'm not sure what you mean.
>
>The error handler is simply a procedure that's bound by reference into a
>number of different programs. The handler can do it's own logging, and one
>of the things that I needed to log was the program which cratered, and the
>library that it was executed from.
>
>Regards,
>
>John Taylor
>
>
>
>_______________________________________________
>This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
>To post a message email: MIDRANGE-L@midrange.com
>To subscribe, unsubscribe, or change list options,
>visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
>or email: MIDRANGE-L-request@midrange.com
>Before posting, please take a moment to review the archives
>at http://archive.midrange.com/midrange-l.



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.