The ENDDBMON command ends the Database Monitor for a specific job or all jobs on the system. If an attempt to end the monitor on all jobs is issued, there must have been a previous STRDBMON issued for all jobs. If a particular job is specified on this command, the job must have the monitor started explicitly and specifically on that job.
For example, consider the following sequence of events:
In this sequence, the specific job monitor continues to run because an explicit start of the monitor was done on it. It continues to run until an ENDDBMON on the specific job is issued.
Consider the following sequence:
In this sequence, monitoring continues to run for all jobs, even over the specific job, until an ENDDBMON for all jobs is issued.
In the following sequence:
In this sequence, monitoring continues to run for the specific job until you issue an ENDDBMON for that job.
In the following sequence:
In this sequence, monitoring continues to run for all jobs, including the specific job.
When monitoring is ended for all jobs, all of the jobs on the system will be triggered to close the output table, however, the ENDDBMON command can complete before all of the monitored jobs have written their final performance rows to the log. Use the Work with Object Locks (WRKOBJLCK) command to see that all of the monitored jobs no longer hold locks on the output table before assuming the monitoring is complete.