70 lines
4.1 KiB
HTML
70 lines
4.1 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="Routing entries" />
|
|
<meta name="abstract" content="An i5/OS job is routed to a subsystem by using the routing entries in the subsystem description. The routing entry for the listener job in the QSYSWRK subsystem is present after i5/OS is installed. This job is started under the QUSER user profile, and the QSYSNOMAX job queue is used." />
|
|
<meta name="description" content="An i5/OS job is routed to a subsystem by using the routing entries in the subsystem description. The routing entry for the listener job in the QSYSWRK subsystem is present after i5/OS is installed. This job is started under the QUSER user profile, and the QSYSNOMAX job queue is used." />
|
|
<meta name="DC.Relation" scheme="URI" content="rbal1usepsj.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="rbal1routing" />
|
|
<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>Routing entries</title>
|
|
</head>
|
|
<body id="rbal1routing"><a name="rbal1routing"><!-- --></a>
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<h1 class="topictitle1">Routing entries</h1>
|
|
<div><p>An <span class="keyword">i5/OS™</span> job
|
|
is routed to a subsystem by using the routing entries in the subsystem description.
|
|
The routing entry for the listener job in the QSYSWRK subsystem is present
|
|
after <span class="keyword">i5/OS</span> is installed.
|
|
This job is started under the QUSER user profile, and the QSYSNOMAX job queue
|
|
is used.</p>
|
|
<div class="section"><p>Prior to V5R2, the server jobs ran in the QSYSWRK subsystem. In
|
|
V5R2, the server jobs run by default in QUSRWRK. The characteristics of the
|
|
server jobs are taken from their prestart job entry which also comes automatically
|
|
configured with <span class="keyword">i5/OS</span>.
|
|
If this entry is removed so that prestart jobs are not used for the servers,
|
|
then the server jobs are started using the characteristics of their corresponding
|
|
listener job.</p>
|
|
</div>
|
|
<div class="section"><p>The following list provides the initial configuration
|
|
in the QSYSWRK subsystem for the listener job.</p>
|
|
</div>
|
|
<div class="section"><div class="p"> <dl><dt class="dlterm">Subsystem</dt>
|
|
<dd>QSYSWRK</dd>
|
|
<dt class="dlterm">Job Queue</dt>
|
|
<dd>QSYSNOMAX</dd>
|
|
<dt class="dlterm">User</dt>
|
|
<dd>QUSER</dd>
|
|
<dt class="dlterm">Routing Data</dt>
|
|
<dd>QRWTLSTN</dd>
|
|
<dt class="dlterm">Job Name</dt>
|
|
<dd>QRWTLSTN</dd>
|
|
<dt class="dlterm">Class</dt>
|
|
<dd>QSYSCLS20</dd>
|
|
</dl>
|
|
</div>
|
|
</div>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbal1usepsj.htm" title="Server information that pertains to prestart jobs, such as the Display Active Prestart Jobs (DSPACTPJ) command, uses the term program start request exclusively to indicate requests made to start prestart jobs, even though the information might pertain to a prestart job that was started as a result of a TCP/IP connection request.">DRDA and DDM prestart jobs</a></div>
|
|
</div>
|
|
</div>
|
|
</body>
|
|
</html> |