Re: WRKACTJOB still a resource pig?

If IBM did change that, it is not easy to find. I wonder if it was about
iNav performance information, which uses a lot of the collected performance
data for charts, etc..

The problem with interrogating system information is usually that it runs at
a higher priority. An interactive job running WRKMBRPDM, for example, would
be subject to the standard RUNPTY+TIMESLICE+POOL etc.. Your F21 job will not
be a hog if the system is tuned right - it certainly would be a heavy
resource user, but performance tuning is about balance and throughput - you
cannot make the CPU run any "faster".

So, using WRKACTJOB means you are using a tool that has to continue to run
at a system task level. This is not something you want to do when your
business is needing those resources.

Regardless, .1% of a system for something you just sit there is .1% too much
- even over two hours. Ask this question - would the company prefer that .1%
to be doing business work, or letting someone watch what is happening - for
no apparent benefit?

Of course, your "big brother" is probably wasting more resources watching
what you and everyone else are doing!! Again, not a justification for you
:-)



On 12/28/07 1:23 PM, "Dan" <dan27649@xxxxxxxxx> wrote:

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