Re: Logging when child-server jobs start and end

James,

Look at the CEERTX / CEEUTX API's. Here's a description from the IBM manual:

The Register Call Stack Entry Termination User Exit Procedure (CEERTX) API registers a user-defined procedure that runs when the call stack entry for which it is registered is ended by anything other than a return to the caller.

It was introduced in V2R3.

If you want to log normal exits too, you can just call the procedure during your exit routine.

-mark

At 6/2/2011 05:44 PM, you wrote:

I see that QHST "log versions" are simply database files. But they look
kind of nasty, and have the added problem of figuring out which one to
look at.

I also see that as of V6R1 (which the customer in question may very well
be on), there's a QMHOLHST API, which can access (and filter) QHST
messages without needing to worry about which "log version" is current,
but the InfoCenter entry for it looks nasty, too, and I haven't been
able to find any examples.

Maybe this isn't the best approach for the task at hand, though.

We're not looking for "jobs in general"; we're looking very specifically
for Wintouch child-server jobs, which are always batch jobs, always
launched in the same way, and always running the same program. So when
that program starts, we know, within a split second, when the job started.

And if the job is ending because the user exited, or because it died of
request-starvation, we can log that as well, because the program is in
control of when it ends under these circumstances.

But is there something that can be set up so that a job calls something
when ABENDed?

--
JHHL