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



Hi Dan,

I used to have a boss that was quite moronic and paranoid about this very
same thing. She could never tell me WHY she thought WRKACTJOB was a problem,
just that it was, and that I should never use it for any reason.

On the other hand, this was part of a larger trust issue with her where she
didn't trust anyone who worked for her and would pour over every single job
log on the system every day, especially her programmers so she could know at
all times what they were doing.

If you're dealing with a mental health issue here like the one I described
with my former boss, then there is nothing you can say that will change that
person's mind.

Shannon O'Donnell




-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Dan
Sent: Friday, December 28, 2007 11:14 AM
To: Midrange Systems Technical Discussion
Subject: WRKACTJOB still a resource pig?

In the early, EARLY days of my AS/400 experience, I seem to recall that
WRKACTJOB was a resource pig, and could adversely affect performance. In
fact, there were a few shops I worked in that restricted access to that
command but had *ALLOBJ authority for everything else by default. And, I
also seem to recall that, instead of using F3 or F12 to exit the command,
you were supposed to use the System Request key, then take option 2 to "End
previous request"; that way, WRKACTJOB supposedly ceased to run in the
background.

I also seem to recall that all of this changed somewhere along the way to
V5R3, so that it is no longer a resource pig, and system performance is not
adversely affected by someone having it up on their screen all day,
refreshing it every few minutes or so.

The reason for this post is because I'm getting hammered by an aggressive
system cop/idiot (how this guy ever got hired here is a complete mystery;
think Dilbert's Mordac, "Preventer of Information Technology") who thinks
that our system's performance is in the crapper because I have WRKACTJOB up
all day when I'm on call for a particular production application, and I
refresh at 5 minute intervals. This is on a model 550 with, I believe, 8 GB
of memory (based on the sum of all Pool Sizes as shown on DSPSYSSTS; I can't
remember if this is accurate, or whether there is a better source of
information for this).

Right now, after having a job running this for over two hours, WRKACTJOB
shows the system's CPU at 70.7% and my job using 0.1%.
The total processing unit time used by my job thus far is 10.3 seconds.
Are there any other metrics that would be useful.

Ammo, anyone?

TIA,
- 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.