RE: WRKACTJOB still a resource pig?

My understanding and experience is same as Cary's - performance monitoring
is always on so WRKACTJOB overhead is minimal (fractions of a percent).

Based on my experience, performance problems are always somewhere else.

For the case you've described (3rd party app with poor error handling),
consider new (v5r4) job watcher support. Type STRWCH and hit F1 for more
details on this.

Elvis

Celebrating 10-Years of SQL Performance Excellence on IBM i5/OS and OS/400
www.centerfieldtechnology.com


-----Original Message-----
Subject: RE: WRKACTJOB still a resource pig?

Dan,

I remember in the old days, probably all the way back to the Sys/38,
that there was talk of wrkactjob being a performance pig and that sysreq
2 would stop it from running.

But if I remember correctly, someone had discounted that long ago. The
way I remember it is that the performance monitoring is always running
in the background, whether you are using wrkactjob or not, and
collecting data. The wrkactjob command is using the data that is already
being collected.

Bottom line as I remember it is that the wrkactjob command isn't a
resource hog.

-Cary