ibm-information-center/dist/eclipse/plugins/i5OS.ic.rzaku_5.4.0.1/rzakuwatchcmntrcscen.htm

96 lines
5.9 KiB
HTML
Raw 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="task" />
<meta name="DC.Title" content="Scenario: Use watch support with a communications trace" />
<meta name="abstract" content="You can use watch support with a communications trace." />
<meta name="description" content="You can use watch support with a communications trace." />
<meta name="DC.Relation" scheme="URI" content="rzakuwatchscenarios.htm" />
<meta name="copyright" content="(C) Copyright IBM Corporation 1997, 2006" />
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 1997, 2006" />
<meta name="DC.Format" content="XHTML" />
<meta name="DC.Identifier" content="watchcmntrcscen" />
<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>Scenario: Use watch support with a communications trace</title>
</head>
<body id="watchcmntrcscen"><a name="watchcmntrcscen"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">Scenario: Use watch support with a communications trace</h1>
<div><p>You can use watch support with a communications trace.</p>
<div class="section">You notice that Telnet sessions are dropping intermittently on the
system, but nothing else seems to be wrong. When the sessions drop, message
TCP2617 is sent to the QSYS/QSYSOPR message queue. <p>To solve the problem,
you need to perform a communications trace using watch support so that the
trace is automatically stopped when the TCP2617 message is sent to QSYSOPR.
This allows you to capture only the data that you need to analyze the problem
and prevents the trace from running longer than necessary.</p>
<p>To perform
the communications trace using watch support, follow these steps:</p>
</div>
<ol><li><span>Start the communications trace:</span><ol type="a"><li><span>At the command line, type <samp class="codeph">STRCMNTRC</samp> and press
F4.</span></li>
<li><span>For the <em>Configuration object</em> prompt, specify the name
of the line, such as TRNLINE.</span></li>
<li><span>For the <em>Type</em> prompt, specify the type of resource, such
as *LIN.</span></li>
<li><span>For the <em>Watch for message, Message identifier</em> prompt,
type <samp class="codeph">TCP2617</samp>.</span></li>
<li><span>For the <em>Watched message queue, Message queue</em> prompt,
type <samp class="codeph">*SYSOPR</samp>. This ensures that the communications trace
stops running when the TCP2617 message is sent to the QSYSOPR message queue.</span></li>
<li><span>For the <em>Length of time to watch</em> prompt, type <samp class="codeph">2880</samp>.
The value 2880 indicates that the communications trace runs for a maximum
of two days (2880 minutes) if the message does not occur. When two days elapse,
the trace ends. If you do not want the trace to end if the message does not
occur during the specified time, specify *NOMAX for this parameter.</span></li>
</ol>
</li>
<li><span>Verify that the watch support started:</span><ol type="a"><li class="substepexpand"><span>At the command line, type <samp class="codeph">DSPLOG</samp> and press
F4.</span></li>
<li class="substepexpand"><span>For the <em>Log</em> prompt, type <samp class="codeph">QHST</samp>.</span> You should see the following message: <p><samp class="codeph">Job <em>jobnumber</em>/<em>user</em>/QSCCMN<em>xxxx</em> started
on mm/dd/yy at hh:mm:ss in subsystem QUSRWRK in QSYS. Job entered system on
mm/dd/yy at hh:mm:ss</samp></p>
where user is the name of the user that runs
the STRCMNTRC command and where xxxx indicates a unique identifier for the
watch job. Note that CMN in the middle of the job name indicates that the
watch job was started by the STRCMNTRC command.</li>
</ol>
</li>
<li><span>Verify that the watch support is running:</span><ul><li>At the command line, type <samp class="codeph">WRKACTJOB SBS(QUSRWRK)</samp>.</li>
<li>You should see the watch job running in the QUSRWRK subsystem. The
job is typically in DEQW status if the watched message has not been sent.</li>
</ul>
</li>
<li><span>After the TCP2617 message is sent to the QSYS/QSYSOPR
message queue, you should verify that the trace has ended:</span><ul><li>At the command line, type <samp class="codeph">DSPMSG MSGQ(*SYSOPR)</samp>.</li>
<li>You should see the CPI3999 message which indicates that the STRCMNTRC
command was ended because of reason code 02. Reason code 02 indicates that <samp class="codeph">Watch
for event criteria met because of message id TCP2617 found in QSYS/QSYSOPR</samp>.</li>
</ul>
</li>
<li><span><a href="rzakuprintt.htm#printt">Format the trace output</a> using
the Print Communications Trace (PRTCMNTRC) command to analyze the collected
trace data. You might see that information is sent to the remote system but
a response is not sent back. This indicates that the problem lies outside
the local server.</span></li>
</ol>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzakuwatchscenarios.htm" title="You can learn how to use the watch function when you perform a trace from these scenarios.">Scenarios: Use watch support with traces</a></div>
</div>
</div>
</body>
</html>