All of our jobs run in the EZRAD.COM subsystem with a run priority of 60. This is one of the worst run priorities on the system. We should always be the last processes to get resources on a Production system. This job goes into a DEQW status for 15 minutes. Once it wakes up, it does consume some resources to collect information about every job that has run during the last 15 minute period and the jobs that are currently active.

If you use the WRKSYSACT or WRKACTJOB commands and repeatedly press the "F10=Restart statistics" function key, you will see this and other jobs consuming a large amount of CPU. This is not an accurate reflection of any jobs CPU impact. You need to press F10 once and then "F5=Refresh" repeatedly to accumulate some "Elapsed time" on the top of the screen. This will show you an average CPU utilization over this elapsed time.

Our default data collection jobs typically consume an average of 1% or less of your system CPU resources. Running at a 15 minute interval, this is a 1% average CPU hit over each 15 minute period. Much of that time our jobs are sitting idle. When awake, they do consume more resources but at a run priority of 60. Use the System Navigator and Workload Navigator PDFs and data on the green-screen to see a true illustration of any jobs impact - including ours.

The total CPU for the WORKNAV job will be high because the job runs continuously. It starts at IPL time and runs until the next IPL. This again does not present itself as an issue. The average CPU usage is a better reflection of any jobs impact.

There is also a WORKNAV job that is scheduled to run everyday in our "Automated Scheduling" module. This job does not "collect" any data. It simply extracts collected data and generates PDFs for the secured area of our web site. This job runs in the early morning and should not run for more than a few minutes.