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


  1.  Home
  2. MIDRANGE-L
  3. May 2004

Re: Program Usage Accounting

And as I think more on this, the exit point is at for a job, not a program.

Performance is always a concern. If you did use this exit for something, a way to minimize the impact on an individual job is to immediately send the job entry argument you receive to another data queue, which you have monitored by a second job. Processing time is not critical in this second job, unless it matters that the job is still running when you get to it.

Then let the original job go - very quick.

Vern

At 07:29 AM 5/11/2004, you wrote: 
On Mon, 10 May 2004 15:21:05 -0500, Vern Hamberg
<vhamberg@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

>Gord
>
>There's a job notification exit point called QIBM_QWT_JOBNOTIFY. You
>actually define it over a subsystem. You also tell it a data queue. This
>DTAQ gets an entry every time the program goes on a job queue, start, or
>ends, according to what you've set the exit point for.
>
>Look in the API Finder for QIBM_QWT_JOBNOTIFY in InfoCenter.
>
>HTH
>Vern

Vern, Thanks I will have a look.

I think we've given this up as a lot of work and potentially a big impact on
system performance for some information that is more a 'nice to have' as
opposed to 'have to have'.

I seem to recall this being available in the performance data with a full
trace on in some previous release (we're on 5r2).  But this too is not worth
the impact on the system.

Thanks for the input.

Gord


--
Gord Hutchinson
Database Administrator, IT
TST Overland Express
ghutchinson@xxxxxxxxxxxxxxx
905-212-6330
fax: 905-602-8895



As an Amazon Associate we earn from qualifying purchases.

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