Re: QMHRCVPM

["John Taylor" <jtaylor@xxxxxxxxxxxx>]

From: Vernon Hamberg


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

That's right. But the error handler does run within the same job -- it's
part of a service program.

I can receive the message just fine. The problem is that it doesn't return
the *qualified* program name as part of the sender information which it
provides. Even listing the job log (QMHLJOBL) doesn't provide it.

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

I think you're referring to my earlier mention of the fact that retrieving
the call stack is of no use because the program that failed is no longer
active. When the program fails with an exception, it's removed from the call
stack.

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

The library list is always in effect, but that doesn't mean that it was used
to resolve the qualified program name. Instead of coding:

call    'somePgm'

a programmer may be required to qualify it as:

call    'someLib/somePgm'

In which case, the program might not be found in the current libl at all, or
there may be multiple programs with the same name in different libs within
your list. Either way, you don't know which program actually sent the
message.


> Ignore me if I'm nuts.  <bg>

Nah... birds of a feather & all that.... ;-))


Regards,

John Taylor