64 lines
4.6 KiB
HTML
64 lines
4.6 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="reference" />
|
||
|
|
<meta name="DC.Title" content="Identify server jobs" />
|
||
|
|
<meta name="abstract" content="If you look at the server jobs started on the system, you might find it difficult to relate a server job to a certain application requester job or to a particular PC client. Being able to identify a particular job is a prerequisite to investigating problems and gathering performance data. iSeries Navigator provides support for these tasks that make the job much easier." />
|
||
|
|
<meta name="description" content="If you look at the server jobs started on the system, you might find it difficult to relate a server job to a certain application requester job or to a particular PC client. Being able to identify a particular job is a prerequisite to investigating problems and gathering performance data. iSeries Navigator provides support for these tasks that make the job much easier." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbae5mtserv.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbae5x400jbns.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbae5dpcjbss.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbae5dhislog.htm" />
|
||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 1999, 2006" />
|
||
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 1999, 2006" />
|
||
|
|
<meta name="DC.Format" content="XHTML" />
|
||
|
|
<meta name="DC.Identifier" content="rbae5idsjobs" />
|
||
|
|
<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>Identify server jobs</title>
|
||
|
|
</head>
|
||
|
|
<body id="rbae5idsjobs"><a name="rbae5idsjobs"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Identify server jobs</h1>
|
||
|
|
<div><p>If you look at the server jobs started on the system, you might
|
||
|
|
find it difficult to relate a server job to a certain application requester
|
||
|
|
job or to a particular PC client. Being able to identify a particular
|
||
|
|
job is a prerequisite to investigating problems and gathering performance
|
||
|
|
data. <span class="keyword">iSeries™ Navigator</span> provides support
|
||
|
|
for these tasks that make the job much easier.</p>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<ul class="ullinks">
|
||
|
|
<li class="ulchildlink"><strong><a href="rbae5x400jbns.htm">iSeries job names</a></strong><br />
|
||
|
|
The job name used on the <span class="keyword">iSeries</span> consists
|
||
|
|
of three parts: the simple job name, user ID, and job number (ascending order).</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbae5dpcjbss.htm">Display server jobs</a></strong><br />
|
||
|
|
There are several methods that can be used to aid in identifying
|
||
|
|
server jobs. One method is to use the <span class="cmdname">WRKACTJOB</span> command.
|
||
|
|
Another method is to use the <span class="cmdname">WRKUSRJOB</span> command. A third
|
||
|
|
method is to display the history log to determine which job is being used
|
||
|
|
by which client user.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbae5dhislog.htm">Display the history log</a></strong><br />
|
||
|
|
Each time a client user establishes a successful connection with
|
||
|
|
a server job, that job is swapped to run under the profile of that client
|
||
|
|
user. To determine which job is associated with a particular client user,
|
||
|
|
you can display the history log using the <span class="cmdname">DSPLOG</span> command. </li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbae5mtserv.htm" title="These topics describe how to manage the DRDA and DDM server jobs that communicate using sockets over TCP. It describes the subsystem in which the server runs, the objects that affect the server, and how to manage those resources.">Manage the TCP/IP server</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|