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.
The QYRMJOBSEL uses the information that is specified in the General page of the Job Monitor definition () with Collection Services data (QYPSPFRCOL) to determine what specific jobs need to be monitored. These jobs are then shown in the bottom half of the Job Monitor status window.
Even if only one job is running, QYRMJOBSEL still examines all of the active job data from Collection Services to determine how many jobs are running, if new instances have started or if instances that were running during the previous interval have ended. The QYRMJOBSEL job does this analysis at each interval. Thus, the amount of CPU resource that is needed for QYRMJOBSEL to complete this function is determined by how many active jobs are on the system. The more active jobs, the more jobs for QYRMJOBSEL to analyze.
Additionally, the QYRMJOBSEL job registers with Collection Services the needed probe data, but it cannot provide the notification interval. So it is always at the lowest interval at which Collection Services is running. Thus, a smaller collection interval means that this processing is performed more frequently.
For example, suppose the job monitor server starts a job monitor at 5 minute collection intervals. Then another monitor that is using Collection Services starts, but uses a smaller interval. As a result, the QYRMJOBSEL receives the data at the smaller or more frequent interval. If the smaller interval is 30 seconds, there will be a 10 time increase in the amount of data QYRMJOBSEL processes, thereby increasing the need for CPU resources.
When the job monitor is stopped, its associated QYRMJOBSEL job receives an ENDJOB immediate and terminates with a CPC1125 Completion 50 severity. This is the normal way that the QYRMJOBSEL is removed from the system.