Job monitors and Collection Services

In order to avoid creating a negative performance impact on your system, you should understand how the different metrics in the job monitor uses Collection Services.

The data for the job numeric and summary numeric values metrics come from Collection Services. The overhead for obtaining this data is minimal and is not affected by the number of specific jobs that are being monitored. It takes two intervals of Collection services data before the first point or data metric value can be calculated. For example, if the collection interval is 5 minutes it will take more than 5 minutes before the first metric value is known.

The overhead for the job log message and job status metrics is much more costly in terms of the CPU resources required to obtain the information. Additionally, the number of jobs that are being monitored as well as the collection interval, affect the amount of CPU overhead that is required. For example, a job Monitor with a 5 minute interval will have six times the amount of overhead process to complete versus if the collection interval was set to 30 minutes.

• The QYRMJOBSEL job
  For every job monitor that runs, a QYRMJOBSEL job starts. This topic explains the purpose of the QYRMJOBSEL job and what causes it to end.
• QZRCSRVS jobs and their impact on performance
  Job monitors connect to a QZRCSRVS job for each job that is being monitored for the Job Log Messages and the Job Status metrics. The more jobs that are being monitored for these metrics, the more QZRCSRVS jobs are used.