I hate to say it but this is much less sinister than that.
WRKACTJOB shows details for what it works with - for jobs.
But not everything that runs on system is a job. There are lots of SLIC
tasks - save/restore, asynchronous pagein/pageout, TCP/IP router, database
SMP support, performance statistics collection - to name just a few.
All these consume CPU - sometimes quite a lot.
But these are not jobs, so WRKACTJOB does *not* show them in details
section. But they *are* included in WRKACTJOB header, which is system
Bottom line - CFINT or not, you are about to see this effect every now and

WRKSYSACT is indeed a way to see all things which use CPU on system - it is
not limited to jobs.
You can also look at performance data collected by Performance Monitor
and/or Collection Services (it depends on release).
This data will also include SLIC tasks as well as jobs.

    Alexei Pytel

"No one can beat unbeatable"

                    "Leif Svalgaard"
                    <leif@leif.org>           To:     <midrange-l@midrange.com>
                    Sent by:                  cc:
                    midrange-l-admin@mi       Subject:     Re: WrkActJob 
percentages are way off

                    08/30/2001 06:18 PM
                    Please respond to

----- Original Message -----
From: Patrick Conner <pwconner@charter.net>
To: <midrange-l@midrange.com>
Sent: Thursday, August 30, 2001 6:18 PM
Subject: WrkActJob percentages are way off

> Sometimes when we WrkActJob the CPU utilization in the list
> does not come anywhere near what is being reported at the
> top of the display. Why is that?
> V4R5 with current ptfs.

CFINT rears its ugly head. If you run WRKSYSACT you'll see the missing
CPU cycles. CFINT is a "governor" that prevents you from using more
interactive "features" than you have paid for. See VERY many previous
posts on that.

This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

This thread ...

Return to Archive home page | Return to MIDRANGE.COM home page