×
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 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
As an Amazon Associate we earn from qualifying purchases.
This thread ...
Re: Logging when child-server jobs start and end, (continued)
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
