Re: WRKACTJOB

8% would be rather significant on a 12way processor.  That would mean you 
are eating up an entire processor.  So, unless you are using SMP, no 
individual job should exceed 8% on that 12 way.  Which is another good 
reason to get a multiprocessor.  One job will NOT take your entire system 
down (processor wise anyway).  :-)

How many processors are you running Vern?

Rob Berendt
-- 
"They that can give up essential liberty to obtain a little temporary 
safety deserve neither liberty nor safety." 
Benjamin Franklin 





Vern Hamberg <vhamberg@xxxxxxxxxxxxxxxxxxxxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
08/26/2003 01:49 PM
Please respond to Midrange Systems Technical Discussion
 
        To:     Midrange Systems Technical Discussion 
<midrange-l@xxxxxxxxxxxx>
        cc: 
        Fax to: 
        Subject:        Re: WRKACTJOB


Ken

Neither WRKUSRJOB or WRKSBSJOB have the performance data that WRKACTJOB 
has. This suggests that a lot more is being done. Unfortunately, WRKACTJOB 

cannot be filtered by user, only job name and/or subsystem, etc. There 
could be a custom command written that takes a subsystem description name, 

then calls WRKACTJOB with that filter.

I'm sure WRKACTJOB is recording times of refresh. I'm not sure that IT is 
actively collecting stats over that time - the system is, but that's going 

on at all times, anyway. Things like CPU seconds are kept in absolute 
values from IPL, e.g., or from job start. The delta needs to be 
calculated, 
based on times collected. CPU% is not stored anywhere, AFAIK. it is 
calculated.

I just tried it, sorting by CPU%. If I refresh often, the CPU% for my job 
that is running WRKACTJOB is 6-8%. If I wait a long time in between, the 
CPU% is less than 2% - the CPU time used is spread over a longer elapsed 
time. So I believe that the CPU is being used at the refresh time only. 
All 
the stats are collected into machine counters continually, not because of 
WRKACTJOB.

Also, if you say REFRESH(*NO) when running it again, the time interval 
includes the time when it was NOT running.

So I believe the intensity of WRKACTJOB occurs when refreshing, 
restarting, 
or resetting the data, F5, F10, or F13, resp.

A lot of people using this command at the same time will put a strain on 
things, of course.

HTH

Vern

At 09:55 AM 8/26/2003 -0700, you wrote:
>Can any of you provide reasons why it might be a good idea to restrict 
the
>use of the WRKACTJOB command to Sys Admin and Operator users?
>
>I'm trying to convince our large team of programmers that WRKUSRJOB is a
>better command to use...
>
>Kenneth
>
>****************************************
>Kenneth E. Graap
>IBM Certified Specialist
>AS/400e Professional System Administrator
>NW Natural (Gas Services)
>keg@xxxxxxxxxxxxx
>Phone: 503-226-4211 x5537
>FAX:    603-849-0591
>****************************************


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