ibm-information-center/dist/eclipse/plugins/i5OS.ic.ddm_5.4.0.1/rbae5usepsj.htm

129 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="DDM prestart jobs" />
<meta name="abstract" content="System information that pertains to prestart jobs (such as DSPACTPJ) will use 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." />
<meta name="description" content="System information that pertains to prestart jobs (such as DSPACTPJ) will use 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." />
<meta name="DC.subject" content="prestart jobs, using" />
<meta name="keywords" content="prestart jobs, using" />
<meta name="DC.Relation" scheme="URI" content="rbae5subsyss.htm" />
<meta name="DC.Relation" scheme="URI" content="rbae5monpre.htm" />
<meta name="DC.Relation" scheme="URI" content="rbae5manpre.htm" />
<meta name="DC.Relation" scheme="URI" content="rbae5rvment.htm" />
<meta name="DC.Relation" scheme="URI" content="rbae5routeent.htm" />
<meta name="DC.Relation" scheme="URI" content="rbae5configss.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="rbae5usepsj" />
<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>DDM prestart jobs</title>
</head>
<body id="rbae5usepsj"><a name="rbae5usepsj"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">DDM prestart jobs</h1>
<div><p>System information that pertains to prestart jobs (such as DSPACTPJ)
will use the term <dfn class="term">program start request</dfn> 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.</p>
<div class="section"><p>The following list contains the prestart job entry attributes
with the initially configured value for the DDM TCP/IP server. They can be
changed with the <span class="cmdname">Change Prestart Job Entry (CHGPJE)</span> command.</p>
<ul><li>Subsystem description. The subsystem that contains the prestart job entries
is QUSRWRK.</li>
<li>Program library and name. The program that is called when the prestart
job is started is QSYS/QRWTSRVR.</li>
<li>User profile. The user profile that the job runs under is QUSER. This
is what the job shows as the user profile. When a request to connect to the
server is received from a client, the prestart job function swaps to the user
profile that is received in that request.</li>
<li>Job name. The name of the job when it is started is QRWTSRVR.</li>
<li>Job description. The job description used for the prestart job is *USRPRF.
Note that the user profile is QUSER so this will be whatever QUSER's job description
is. However, the attributes of the job are changed to correspond to the requesting
user's job description after the user ID and password (if present) are verified.</li>
<li>Start jobs. This indicates whether prestart jobs are to automatically
start when the subsystem is started. These prestart job entries are shipped
with a start jobs value of *YES. You can change these to *NO if the DDM TCP/IP
communications support is to be used. <div class="note"><span class="notetitle">Note:</span> If the DDM server jobs are not
running and the DDM listener job is batch, immediate DDM server
jobs will still be run under the QSYSWRK subsystem.</div>
</li>
<li>Initial number of jobs. As initially configured, the number of jobs that
are started when the subsystem is started is 1. This value can be adjusted
to suit your particular environment and needs.</li>
<li>Threshold. The minimum number of available prestart jobs for a prestart
job entry is set to 1. When this threshold is reached, additional prestart
jobs are automatically started. This is used to maintain a certain number
of jobs in the pool.</li>
<li>Additional number of jobs. The number of additional prestart jobs that
are started when the threshold is reached is initially configured at 2.</li>
<li>Maximum number of jobs. The maximum number of prestart jobs that can be
active for this entry is *NOMAX.</li>
<li>Maximum number of uses. The maximum number of uses of the job is set to
200. This value indicates that the prestart job will end after 200 requests
to start the server have been processed. In certain situations, you might
need to set the MAXUSE parameter to 1 in order for the TCP/IP server to function
properly. When the server runs certain ILE stored procedures, pointers to
destroyed objects might remain in the prestart job environment; subsequent
uses of the prestart job would cause MCH3402 exceptions.</li>
<li>Wait for job. The *YES setting causes a client connection request to wait
for an available server job if the maximum number of jobs is reached.</li>
<li>Pool identifier. The subsystem pool identifier in which this prestart
job runs is set to 1.</li>
<li>Class. The name and library of the class the prestart jobs will run under
is set to QSYS/QSYSCLS20.</li>
</ul>
</div>
<div class="section"><p>When the start jobs value for the prestart job entry has been
set to *YES, and the remaining values are as provided with their initial settings,
the following things happen for each prestart job entry:</p>
<ul><li>When the subsystem is started, one prestart job is started.</li>
<li>When the first client connection request is processed for the TCP/IP server,
the initial job is used and the threshold is exceeded.</li>
<li>Additional jobs are started for the server based on the number defined
in the prestart job entry.</li>
<li>The number of available jobs will not reach below 1.</li>
<li>The subsystem periodically checks the number of prestart jobs in a pool
that are unused and ends excess jobs. It always leaves at least the number
of prestart jobs specified in the initial jobs parameter.</li>
</ul>
</div>
</div>
<div>
<ul class="ullinks">
<li class="ulchildlink"><strong><a href="rbae5monpre.htm">Monitor prestart jobs</a></strong><br />
Prestart jobs can be monitored by using the <span class="cmdname">Display Active
Prestart Jobs (DSPACTPJ)</span> command.</li>
<li class="ulchildlink"><strong><a href="rbae5manpre.htm">Manage prestart jobs</a></strong><br />
The key is to ensure that there is an available prestart job for every sent request that starts a server job.</li>
<li class="ulchildlink"><strong><a href="rbae5rvment.htm">Remove prestart job entries</a></strong><br />
If you decide that you do not want the servers to use the prestart job function, you must follow these steps.</li>
<li class="ulchildlink"><strong><a href="rbae5routeent.htm">Routing entries</a></strong><br />
An <span class="keyword">i5/OS™</span> job
is routed to a subsystem by using the routing entries in the
subsystem description. </li>
</ul>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbae5subsyss.htm" title="This topic collection provides information for working with server jobs.">DDM server jobs</a></div>
</div>
<div class="reltasks"><strong>Related tasks</strong><br />
<div><a href="rbae5configss.htm" title="By default, the DDM TCP/IP server jobs run in the QUSRWRK subsystem. Using iSeries Navigator, you can configure DDM server jobs to run all or certain server jobs in alternate subsystems based on the client's IP address.">Configure the DDM server job subsystem</a></div>
</div>
</div>
</body>
</html>