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

Re: WRKACTJOB still a resource pig?

On Dec 28, 2007 1:11 PM, Trevor Perry <trevor@xxxxxxxxxx> wrote:

WRKACTJOB (and WRKSYSSTS) has to interrogate the entire set of job control
tables to gather its data. And, it keeps collecting this information until
you sign off - or, some people believe when you use SysReq 2.


My understanding was that, as of some V4Rx release, the stats reported by
WRKACTJOB were collected by a system function that is always running
regardless of WRKACTJOB running or not. Be that as it may, do not the
particular stats of my job show that it is, in fact, not a resource hog?


WRKACTJOB is a low level system task - and if you have a lot of people
using
it, it IS going to step on some actual business work.


But this is true with any application. Let me bring up WRKMBRPDM, and sit
on F21 for ten minutes.

Ultimately, WRKACTJOB is just a habit :-)


Agreed. It is especially a habit from my sysadmin days.

- Dan

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.