ibm-information-center/dist/eclipse/plugins/i5OS.ic.rzajq_5.4.0.1/endbmon.htm

128 lines
8.5 KiB
HTML
Raw Permalink Normal View History

2024-04-02 14:02:31 +00:00
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html lang="en-us" xml:lang="en-us">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<meta name="security" content="public" />
<meta name="Robots" content="index,follow" />
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
<meta name="DC.Type" content="reference" />
<meta name="DC.Title" content="End Database Monitor (ENDDBMON) command" />
<meta name="abstract" content="The End Database Monitor (ENDDBMON) command ends the collection of database performance statistics for a specified job, all jobs on the system or a selected set of jobs (for example, a generic job name)." />
<meta name="description" content="The End Database Monitor (ENDDBMON) command ends the collection of database performance statistics for a specified job, all jobs on the system or a selected set of jobs (for example, a generic job name)." />
<meta name="DC.subject" content="command, End Database Monitor (ENDDBMON), database monitor, end, monitor (, ENDDBMON, ENDDBMON (end database monitor), commands, End Database Monitor (ENDDBMON)" />
<meta name="keywords" content="command, End Database Monitor (ENDDBMON), database monitor, end, monitor (, ENDDBMON, ENDDBMON (end database monitor), commands, End Database Monitor (ENDDBMON)" />
<meta name="DC.Relation" scheme="URI" content="dms.htm" />
<meta name="DC.Relation" scheme="URI" content="../cl/enddbmon.htm" />
<meta name="copyright" content="(C) Copyright IBM Corporation 1998, 2006" />
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 1998, 2006" />
<meta name="DC.Format" content="XHTML" />
<meta name="DC.Identifier" content="endbmon" />
<meta name="DC.Language" content="en-us" />
<!-- All rights reserved. Licensed Materials Property of IBM -->
<!-- US Government Users Restricted Rights -->
<!-- Use, duplication or disclosure restricted by -->
<!-- GSA ADP Schedule Contract with IBM Corp. -->
<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
<link rel="stylesheet" type="text/css" href="./ic.css" />
<title>End Database Monitor (ENDDBMON) command</title>
</head>
<body id="endbmon"><a name="endbmon"><!-- --></a>
<img src="./delta.gif" alt="Start of change" /><!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1"><span class="cmdname">End Database Monitor (ENDDBMON)</span> command</h1>
<div><p>The <span class="cmdname">End Database Monitor (ENDDBMON)</span> command
ends the collection of database performance statistics for a specified job,
all jobs on the system or a selected set of jobs (for example, a generic job
name).</p>
<div class="section"><p>To end a monitor, you can specify the job or the monitor ID or
both. If only the JOB parameter is specified, the monitor that was started
using the same exact JOB parameter is ended - if there is only one monitor
which matches the specified JOB. If more than one monitor is active which
matches the specified JOB, then the user uniquely identifies which monitor
is to be ended by use of the MONID parameter. When only the MONID parameter
is specified, the specified MONID is compared to the monitor ID of the monitor
for the current job and to the monitor ID of all active public monitors (monitors
that are open across multiple jobs). The monitor matching the specified MONID
is ended.</p>
</div>
<div class="section"><p>The monitor ID is returned in the informational message CPI436A.
This message is generated for each occurrence of the STRDBMON command. Look
in the joblog for message CPI436A to find the system generated monitor ID,
if needed. The monitor ID can also be found in column QQC101 of the QQQ3018
database monitor record.</p>
</div>
<div class="section"><h4 class="sectiontitle">Restrictions</h4><ul><li>If a specific job name and number or JOB(*) was specified on the <span class="cmdname">Start
Database Monitor (STRDBMON)</span> command, the monitor can only be ended
by specifying the same job name and number or JOB(*) on the ENDDBMON command.</li>
<li>If JOB(*ALL) was specified on the <span class="cmdname">Start Database Monitor (STRDBMON)</span> command,
the monitor can only be ended by specifying ENDDBMON JOB(*ALL). The monitor
cannot be ended by specifying ENDDBMON JOB(*).</li>
</ul>
</div>
<div class="section"><p>When monitoring is ended for all jobs, all of the jobs on the
server will be triggered to close the database monitor output table. However,
the ENDDBMON command can complete before all of the monitored jobs have written
their final statistic records to the log. Use the <span class="cmdname">Work with Object
Locks (WRKOBJLCK)</span> command to determine that all of the monitored
jobs no longer hold locks on the database monitor output table before assuming
the monitoring is complete.</p>
</div>
<div class="example"><h4 class="sectiontitle">Example 1: End Monitoring for a Specific Job</h4><pre>ENDDBMON JOB(*)</pre>
<p>This
command ends database monitoring for the current job.</p>
</div>
<div class="example"><h4 class="sectiontitle">Example 2: End Monitoring for All Jobs</h4><pre>ENDDBMON JOB(*ALL)</pre>
<p>This
command ends the monitor open across all jobs on the system. If more than
one monitor with JOB(*ALL) is active, then the MONID parameter must also be
specified to uniquely identify which specific public monitor to end.</p>
</div>
<div class="example"><h4 class="sectiontitle">Example 3: End Monitoring for an Individual Public Monitor
with MONID Parameter</h4><pre>ENDDBMON JOB(*ALL) MONID(061601001)</pre>
<p>This
command ends the monitor that was started with JOB(*ALL) and
that has a monitor ID of 061601001. Because there were multiple monitors
started with JOB(*ALL), the monitor ID must be specified to uniquely identify
which monitor that was started with JOB(*ALL) is to be ended.</p>
</div>
<div class="example"><h4 class="sectiontitle">Example 4: End Monitoring for an Individual Public Monitor
with MONID Parameter</h4><pre>ENDDBMON MONID(061601001)</pre>
<p>This
command performs the same function as the previous example. It ends the monitor
that was started with JOB(*ALL) or JOB(*) and that has a monitor ID of 061601001.</p>
</div>
<div class="example"><h4 class="sectiontitle">Example 5: End Monitoring for All JOB(*ALL) Monitors</h4><pre>ENDDBMON JOB(*ALL/*ALL/*ALL) MONID(*ALL)</pre>
<p>This
command ends all monitors that are active across multiple jobs. It will not
end any monitors open for a specific job or the current job.</p>
</div>
<div class="example"><h4 class="sectiontitle">Example 6: End Monitoring for a Generic Job</h4><pre>ENDDBMON JOB(QZDA*)</pre>
<p>This
command ends the monitor that was started with JOB(QZDA*). If more than one
monitor with JOB(QZDA*) is active, then the MONID parameter must also be specified
to uniquely identify which individual monitor to end.</p>
</div>
<div class="example"><h4 class="sectiontitle">Example 7: End Monitoring for an Individual Monitor with a
Generic Job</h4><pre>ENDDBMON JOB(QZDA*) MONID(061601001)</pre>
<p>This
command ends the monitor that was started with JOB(QZDA*) and has a monitor
ID of 061601001. Because there were multiple monitors started with JOB(QZDA*),
the monitor ID must be specified to uniquely identify which JOB(QZDA*) monitor
is to be ended.</p>
</div>
<div class="example"><h4 class="sectiontitle">Example 8: End Monitoring for a Group of Generic Jobs</h4><pre>ENDDBMON JOB(QZDA*) MONID(*ALL)</pre>
<p>This
command ends all monitors that were started with JOB(QZDA*).</p>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="dms.htm" title="Start Database Monitor (STRDBMON) command gathers information about a query in real time and stores this information in an output table. This information can help you determine whether your system and your queries are performing as they should, or whether they need fine tuning. Database monitors can generate significant CPU and disk storage overhead when in use.">Monitoring your queries using Start Database Monitor (STRDBMON)</a></div>
</div>
<div class="relinfo"><strong>Related information</strong><br />
<div><a href="../cl/enddbmon.htm">End Database Monitor (ENDDBMON) command</a></div>
</div>
</div>
<img src="./deltaend.gif" alt="End of change" /></body>
</html>