162 lines
11 KiB
HTML
162 lines
11 KiB
HTML
|
<?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="Locate distributed relational database jobs" />
|
||
|
|
<meta name="abstract" content="When you are looking for information about a distributed relational database job on an application requester (AR) and you know the user profile that is used, you can find that job by using the Work with User Jobs (WRKUSRJOB) command." />
|
||
|
|
<meta name="description" content="When you are looking for information about a distributed relational database job on an application requester (AR) and you know the user profile that is used, you can find that job by using the Work with User Jobs (WRKUSRJOB) command." />
|
||
|
|
<meta name="DC.subject" content="administration task, finding a distributed relational database job, database administration, finding a distributed relational database job, message, DDM job start, DDM job start message, job log, finding a job, TCP/IP, finding server jobs, database accessed, target DDM job started" />
|
||
|
|
<meta name="keywords" content="administration task, finding a distributed relational database job, database administration, finding a distributed relational database job, message, DDM job start, DDM job start message, job log, finding a job, TCP/IP, finding server jobs, database accessed, target DDM job started" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbal1rdbactv.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../cl/dsplog.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../cl/wrkactjob.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../cl/wrkusrjob.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbal1appnotcomp.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbal1pjl.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="rbal1locatej" />
|
||
|
|
<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>Locate distributed relational database jobs</title>
|
||
|
|
</head>
|
||
|
|
<body id="rbal1locatej"><a name="rbal1locatej"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Locate distributed relational database jobs</h1>
|
||
|
|
<div><p>When you are looking for information about a distributed relational
|
||
|
|
database job on an application requester (AR) and you know the user profile
|
||
|
|
that is used, you can find that job by using the <span class="cmdname">Work with User Jobs
|
||
|
|
(WRKUSRJOB)</span> command.</p>
|
||
|
|
<div class="section"> <p>You can also use this command on the application server (AS),
|
||
|
|
but be aware that the user profile on the AS might be different from that
|
||
|
|
used by the AR. For TCP/IP servers, the user profile that qualifies the job
|
||
|
|
name will always be QUSER, and the job name will always be QRWTSRVR. The <span class="cmdname">Display
|
||
|
|
Log (DSPLOG)</span> command can be used to help find the complete server
|
||
|
|
job name. The message will be in the following form: </p>
|
||
|
|
<pre> DDM job 031233/QUSER/QRWTSRVR servicing user XY on 10/02/97 at 22:06</pre>
|
||
|
|
<p>If there are several jobs listed for the specified user profile and the
|
||
|
|
relational database is accessed using DRDA<sup>®</sup>, enter option 5 (Work with job) to
|
||
|
|
get the Work with Job display. From this display, enter option 10 (Display
|
||
|
|
job log) to see the job log. The job log shows you whether this is a distributed
|
||
|
|
relational database job and, if it is, to which remote server the job is connected.
|
||
|
|
Page through the job log looking for one of the following messages (depending
|
||
|
|
on whether the connection is using APPC or TCP/IP):</p>
|
||
|
|
<dl><dt class="dlterm">CPI9150</dt>
|
||
|
|
<dd>DDM job started.</dd>
|
||
|
|
<dt class="dlterm">CPI9160</dt>
|
||
|
|
<dd>Database connection started over TCP/IP or a local socket.</dd>
|
||
|
|
</dl>
|
||
|
|
<p>The second level text for message CPI9150 and CPI9160 contains
|
||
|
|
the job name for the AS job.</p>
|
||
|
|
<p>If you are on the AS and you do not know
|
||
|
|
the job name, but you know the user name, use the <span class="cmdname">Work with User
|
||
|
|
Jobs (WRKUSRJOB)</span> command. If you do not specify a user, the command
|
||
|
|
returns a list of the jobs under the user profile you are using. For TCP/IP,
|
||
|
|
the user profile in the job name will always be QUSER. On the Work with User
|
||
|
|
Jobs display, use these columns to help you identify the AS jobs that are
|
||
|
|
servicing APPC connections.</p>
|
||
|
|
<dl><dt class="dlterm"><strong><span>1</span></strong></dt>
|
||
|
|
<dd>The job type column shows jobs with the type that is listed as CMNEVK
|
||
|
|
for APPC communications jobs.</dd>
|
||
|
|
<dt class="dlterm"><strong><span>2</span></strong></dt>
|
||
|
|
<dd>The status column shows if the job is active or completed. Depending on
|
||
|
|
how the server is set up to log jobs, you might see only active jobs.</dd>
|
||
|
|
<dt class="dlterm"><strong><span>3</span></strong></dt>
|
||
|
|
<dd>The job column provides the job name. The job name on the AS is the same
|
||
|
|
as the device being used.</dd>
|
||
|
|
</dl>
|
||
|
|
<pre class="screen">Work with User Jobs KC105
|
||
|
|
03/29/92 16:15:33
|
||
|
|
Type options, press Enter.
|
||
|
|
2=Change 3=Hold 4=End 5=Work with 6=Release 7=Display message
|
||
|
|
8=Work with spooled files 13=Disconnect
|
||
|
|
|
||
|
|
Opt Job User Type -----Status------ Function
|
||
|
|
__ KC000 KCDBA CMNEVK OUTQ
|
||
|
|
__ MP000 KCDBA CMNEVK OUTQ
|
||
|
|
__ MP000 KCDBA CMNEVK OUTQ
|
||
|
|
__ KC000 KCDBA CMNEVK OUTQ
|
||
|
|
__ KC000 KCDBA CMNEVK ACTIVE
|
||
|
|
__ KC0001 KCDBA INTER ACTIVE CMD-WRKUSRJOB
|
||
|
|
<strong><span>3</span></strong> <strong><span>1</span></strong> <strong><span>2</span></strong></pre>
|
||
|
|
<p>If
|
||
|
|
you are looking for an active AS job and do not know the user name, the <span class="cmdname">Work
|
||
|
|
with Active Jobs (WRKACTJOB)</span> command gives you a list of those jobs
|
||
|
|
for the subsystems active on the server. The following example shows you some
|
||
|
|
items to look for: </p>
|
||
|
|
<pre class="screen">Work with Active Jobs KC105
|
||
|
|
03/29/92 16:17:45
|
||
|
|
CPU %: 41.7 Elapsed time: 04:37:55 Active jobs: 102
|
||
|
|
|
||
|
|
Type options, press Enter.
|
||
|
|
2=Change 3=Hold 4=End 5=Work with 6=Release 7=Display message
|
||
|
|
8=Work with spooled files 13=Disconnect
|
||
|
|
|
||
|
|
Opt Subsystem/Job User Type CPU % Function Status
|
||
|
|
__ QBATCH QSYS SBS .0 DEQW
|
||
|
|
<strong><span>4</span></strong> QCMN QSYS SBS .0 WDEQ
|
||
|
|
__ KC0001 KCCLERK EVK .0 * EVTW
|
||
|
|
<strong><span>5</span></strong> <strong><span>6</span></strong></pre>
|
||
|
|
<dl><dt class="dlterm"><strong><span>4</span></strong></dt>
|
||
|
|
<dd>Search the subsystem that is set up to handle the AS jobs. In this example,
|
||
|
|
the subsystem for AS jobs is QCMN. The subsystem for TCP/IP server jobs is
|
||
|
|
QSYSWRK prior to V5R2, and QUSRWRK after V5R1.</dd>
|
||
|
|
<dt class="dlterm"><strong><span>5</span></strong></dt>
|
||
|
|
<dd>For APPC AS jobs, the job name is the device name of the device that is
|
||
|
|
created for AS use.</dd>
|
||
|
|
<dt class="dlterm"><strong><span>6</span></strong></dt>
|
||
|
|
<dd>The job type listed is normally EVK, started by a program start request.
|
||
|
|
For TCP/IP AS jobs, the job type is PJ (unless DRDA prestart jobs are not active on the
|
||
|
|
server, in which case the job type is BCI).</dd>
|
||
|
|
</dl>
|
||
|
|
<p>When you have located a job that looks like a candidate,
|
||
|
|
enter option 5 to work with that job. Then select option 10 from the Work
|
||
|
|
with Job Menu to display the job log. Distributed database job logs for jobs
|
||
|
|
that are accessing the AS from a <span class="keyword">DB2 Universal Database™ for iSeries™</span> application
|
||
|
|
requester contain a statement near the top that reads: </p>
|
||
|
|
<dl><dt class="dlterm">CPI3E01</dt>
|
||
|
|
<dd>Local relational database accessed by <em>(system name)</em>.</dd>
|
||
|
|
</dl>
|
||
|
|
<p>After you locate a job working on the AS, you can also trace
|
||
|
|
it back to the AR if the AR is an <span class="keyword">iSeries server</span>.
|
||
|
|
One of the following messages will appear in your job log; place the cursor
|
||
|
|
on the message you received: </p>
|
||
|
|
<dl><dt class="dlterm">CPI9152</dt>
|
||
|
|
<dd>Target DDM job started by application requester (AR).</dd>
|
||
|
|
<dt class="dlterm">CPI9162</dt>
|
||
|
|
<dd>Target job assigned to handle DDM connection started by application requester
|
||
|
|
(AR) over TCP/IP.</dd>
|
||
|
|
</dl>
|
||
|
|
<p>When you press the help key, the detailed message for the
|
||
|
|
statement appears. The application requester (AR) job named is the job on
|
||
|
|
the AR that caused this job.</p>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbal1rdbactv.htm" title="You can rely on control language (CL) commands, all of which provide similar information, but in different ways, to give you a view of work on an iSeries server.">Monitor relational database activity</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="reltasks"><strong>Related tasks</strong><br />
|
||
|
|
<div><a href="rbal1pjl.htm" title="Every job on the iSeries server has a job log that contains information related to requests entered for that job. When a user is having a problem at an application requester (AR), the information in the job log might be helpful in diagnosing the problem.">Print a job log</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relref"><strong>Related reference</strong><br />
|
||
|
|
<div><a href="../cl/dsplog.htm">Display Log (DSPLOG) command</a></div>
|
||
|
|
<div><a href="../cl/wrkactjob.htm">Work with Active Jobs (WRKACTJOB) command</a></div>
|
||
|
|
<div><a href="../cl/wrkusrjob.htm">Work with User Jobs (WRKUSRJOB) command</a></div>
|
||
|
|
<div><a href="rbal1appnotcomp.htm" title="If the request takes longer than expected to complete, the first place to check is at the application requester (AR).">Application does not complete in the expected time</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|