![](https://pdfstore-manualsonline.prod.a.ki/pdfasset/1/cf/1cff7c4d-621c-4eb6-bc3e-9de70e5199ff/1cff7c4d-621c-4eb6-bc3e-9de70e5199ff-bg72.png)
BMC Software, Inc., Confidential and Proprietary Information
6-4 PATROL
®
Database Administration Installation Guide
How Jobs Are Monitored
The following scenario describes how the PATROL KM
™
monitors jobs:
1. From a client console running PATROL Database Administration
products, users specify changes or migrations to objects, analyze
those requests, and generate a script (or for DB2*, a worklist) to
implement the changes.
For example, you can use PATROL DB-Change Manager to specify
changes to objects in your databases.
2. After successful analysis, users submit the generated script to a job
scheduler for execution at a PATROL database server (PDB-Server).
For example, you can use the Job Scheduler that is provided with the
PATROL Database Administration products to schedule the
execution of jobs and groups of jobs.
3. When a job begins execution, the PATROL DB-Admin KM running
at the consolidation agent receives an event that registers the job.
During job execution, the PATROL KM registers an event for each
change in job status.
For example, if the job halts, resumes, restarts, or is completed, the
PATROL KM receives an event. The PATROL KM also receives
checkpoint events that notify you of the state of a running job at a
specified time interval.
4. The PATROL DB-Admin KM at a PATROL Agent processes and
consolidates the events and displays them at the PATROL Console.
Users view the status of jobs and services across the entire network
enterprise.