125 lines
8.6 KiB
HTML
125 lines
8.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="task" />
|
|
<meta name="DC.Title" content="Stop a subsystem" />
|
|
<meta name="abstract" content="You can use iSeries Navigator or the character-based interface to stop one or more active subsystems and specify what happens to active work being processed. No new jobs or routing steps are started in the subsystem after the subsystem is stopped." />
|
|
<meta name="description" content="You can use iSeries Navigator or the character-based interface to stop one or more active subsystems and specify what happens to active work being processed. No new jobs or routing steps are started in the subsystem after the subsystem is stopped." />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakssbsyscomntsks.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksaccessjoblog.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksjobendcontrolled.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="../rzakz/rzakzqendjoblmt.htm" />
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 2004-2006" />
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 2004-2006" />
|
|
<meta name="DC.Format" content="XHTML" />
|
|
<meta name="DC.Identifier" content="rzakshowsbsstop" />
|
|
<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>Stop a subsystem</title>
|
|
</head>
|
|
<body id="rzakshowsbsstop"><a name="rzakshowsbsstop"><!-- --></a>
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<h1 class="topictitle1">Stop a subsystem</h1>
|
|
<div><p>You can use iSeries™ Navigator or the character-based interface
|
|
to stop one or more active subsystems and specify what happens to active work
|
|
being processed. No new jobs or routing steps are started in the subsystem
|
|
after the subsystem is stopped. </p>
|
|
<div class="p">When a subsystem is stopped, you can specify what happens to active
|
|
work that is being processed by the system. For example, you can specify for
|
|
all jobs in the subsystem to be ended immediately (Immediate), or you can
|
|
specify that jobs are allowed to finish processing before the subsystem ends
|
|
(Controlled). <div class="important"><span class="importanttitle">Important:</span> It is recommended that subsystems be
|
|
stopped using the Controlled option whenever possible. This allows active
|
|
jobs to end themselves. Use this option to ensure that jobs finish before
|
|
the subsystems end. This allows the programs that are running to perform cleanup
|
|
(end-of-job processing). Specifying the Immediate value can cause undesirable
|
|
results, such as data that has been partially updated.</div>
|
|
<div class="p">There are
|
|
two types of stops.<dl><dt class="dlterm">Controlled (Recommended)</dt>
|
|
<dd> Ends the subsystem in a controlled manner. The jobs are also ended in
|
|
a controlled manner. This allows the programs that are running to perform
|
|
cleanup (end of job processing). When a job being ended has a signal handling
|
|
procedure for the asynchronous signal SIGTERM, the SIGTERM signal is generated
|
|
for that job. The application has the amount of time specified for the <span class="parmname">DELAY</span> parameter
|
|
to complete cleanup before the job is ended.</dd>
|
|
<dt class="dlterm">Immediate</dt>
|
|
<dd>Ends the subsystem immediately. The jobs are also ended immediately. When
|
|
a job being ended has a signal handling procedure for the asynchronous signal
|
|
SIGTERM, the SIGTERM signal is generated for that job and the QENDJOBLMT system
|
|
value specifies a time limit. Other than handling the SIGTERM signal, the
|
|
programs that are running are not allowed to perform any cleanup.</dd>
|
|
</dl>
|
|
</div>
|
|
</div>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzakssbsyscomntsks.htm" title="This information discuss the most common tasks that you can perform on a subsystem.">Common subsystem tasks</a></div>
|
|
</div>
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
|
<div><a href="rzaksjobendcontrolled.htm" title="Ending a job in a controlled manner allows programs that are running in the job to perform their end-of-job cleanup. A delay time can be specified to allow the job to end in a controlled manner. If the delay time ends before the job ends, the job is ended immediately.">End a job: controlled</a></div>
|
|
</div>
|
|
<div class="reltasks"><strong>Related tasks</strong><br />
|
|
<div><a href="rzaksaccessjoblog.htm" title="You can see a job log from any place within work management that you access jobs, such as through the Subsystem area or the Memory Pool area. You can use iSeries Navigator or the character-based interface to display job logs.">How to display job logs</a></div>
|
|
</div>
|
|
<div class="relinfo"><strong>Related information</strong><br />
|
|
<div><a href="../rzakz/rzakzqendjoblmt.htm">Jobs system values: Maximum time for immediate end</a></div>
|
|
</div>
|
|
</div><div class="nested1" xml:lang="en-us" id="navshowsbsstop"><a name="navshowsbsstop"><!-- --></a><h2 class="topictitle2">iSeries Navigator</h2>
|
|
<div><div class="section">To use the iSeries Navigator, do the following:</div>
|
|
<ol><li><span>In iSeries Navigator,
|
|
expand <span class="menucascade"><span class="uicontrol">My Connections </span> > <span class="uicontrol">server</span> > <span class="uicontrol">Work Management </span> > <span class="uicontrol">Subsystems</span> > <span class="uicontrol">Active
|
|
Subsystems</span></span>. </span></li>
|
|
<li><span>Right-click the subsystem or subsystems you want to stop, and then
|
|
click <span class="uicontrol">Stop</span>.</span></li>
|
|
<li><span>Specify the options to be used when the subsystem is stopped.</span></li>
|
|
<li><span>Click <span class="uicontrol">Stop</span>. </span></li>
|
|
</ol>
|
|
</div>
|
|
</div>
|
|
<div class="nested1" xml:lang="en-us" id="cbishowsbsstop"><a name="cbishowsbsstop"><!-- --></a><h2 class="topictitle2">Character-based interface</h2>
|
|
<div><div class="p">To use the character-based interface, type in the following command:</div>
|
|
<div class="section"><strong>Command</strong>: End Subsystem (<span class="cmdname">ENDSBS</span> )</div>
|
|
<div class="example"><strong>Example</strong>: This command ends all active jobs in the QBATCH subsystem
|
|
and ends the subsystem. The active jobs are allowed 60 seconds to perform
|
|
application-provided end-of-job processing.<div class="p"><blockquote><pre>ENDSBS SBS(QBATCH) OPTION(*CNTRLD) DELAY(60)</pre>
|
|
</blockquote>
|
|
</div>
|
|
</div>
|
|
<div class="section">Use the End Subsystem Option (<span class="parmname">ENDSBSOPT</span>) parameter
|
|
to improve the performance for ending a subsystem. If you specify ENDSBSOPT(*NOJOBLOG),
|
|
the subsystem will end, but a job log will not be produced for every job that
|
|
was in the subsystem. <p>If a problem occurs in a job, but you specified *NOJOBLOG,
|
|
problem diagnosis may be difficult or impossible because the problem is not
|
|
recorded in the job log. If you used the LOGOUTPUT(*PND) job attribute then
|
|
the job log is placed in a pending state, but is not written. However, the
|
|
job log is still available if it is needed. See the related topics on job
|
|
logs for more information about job log pending.</p>
|
|
<p>If you specify ENDSBSOPT(*CHGPTY
|
|
*CHGTSL), the run priority and time slice will change for all jobs that end
|
|
in this subsystem. The jobs will compete less aggressively for processor cycles
|
|
and will end with less of an impact on jobs that are still running in other
|
|
subsystems.</p>
|
|
You can specify all three options (*NOJOBLOG, *CHGPTY, and
|
|
*CHGTSL) on the <span class="parmname">ENDSBSOPT</span> parameter, for example:<blockquote><pre>ENDSBSOPT(*NOJOBLOG *CHGPTY *CHGTSL)</pre>
|
|
</blockquote>
|
|
<div class="note"><span class="notetitle">Note:</span> If
|
|
you specify *ALL for the subsystem name and have any jobs running under QSYSWRK,
|
|
you should use *CNTRLD to prevent a subsystem from ending abnormally.</div>
|
|
</div>
|
|
</div>
|
|
</div>
|
|
|
|
</body>
|
|
</html> |