ibm-information-center/dist/eclipse/plugins/i5OS.ic.rzaks_5.4.0.1/rzaksaboutsbs.htm

78 lines
6.3 KiB
HTML
Raw 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="concept" />
<meta name="DC.Title" content="Subsystems" />
<meta name="abstract" content="The subsystem is where work is processed on the iSeries server. A subsystem is a single, predefined operating environment through which the system coordinates the work flow and resource use. The system can contain several subsystems, all operating independently of each other. Subsystems manage resources." />
<meta name="description" content="The subsystem is where work is processed on the iSeries server. A subsystem is a single, predefined operating environment through which the system coordinates the work flow and resource use. The system can contain several subsystems, all operating independently of each other. Subsystems manage resources." />
<meta name="DC.Relation" scheme="URI" content="rzaksconcepts.htm" />
<meta name="DC.Relation" scheme="URI" content="rzakscontrollingsbs.htm" />
<meta name="DC.Relation" scheme="URI" content="rzakssbsmultiple.htm" />
<meta name="DC.Relation" scheme="URI" content="rzakssbsd.htm" />
<meta name="DC.Relation" scheme="URI" content="rzakswhathappenssbsstarts.htm" />
<meta name="DC.Relation" scheme="URI" content="rzakssbsyscomntsks.htm" />
<meta name="DC.Relation" scheme="URI" content="rzakscreatesubsystemdef.htm" />
<meta name="DC.Relation" scheme="URI" content="../experience/work1abstract.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="rzaksaboutsbs" />
<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>Subsystems </title>
</head>
<body id="rzaksaboutsbs"><a name="rzaksaboutsbs"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">Subsystems </h1>
<div><p>The subsystem is where work is processed on the iSeries™ server.
A subsystem is a single, predefined operating environment through which the
system coordinates the work flow and resource use. The system can contain
several subsystems, all operating independently of each other. Subsystems
manage resources. </p>
<p>All jobs, with the exception of system jobs, run within subsystems. Each
subsystem can run unique operations. For instance, one subsystem may be set
up to handle only interactive jobs, while another subsystem handles only batch
jobs. Subsystems can also be designed to handle many types of work. The system
allows you to decide the number of subsystems and what types of work each
subsystem will handle.</p>
<p>The run-time characteristics of a subsystem are defined in an object called
a subsystem description. For example, if you want to permanently change the
amount of work (number of jobs) coming from a job queue into a subsystem you
only need to change the job queue entry in the subsystem description.</p>
</div>
<div>
<ul class="ullinks">
<li class="ulchildlink"><strong><a href="rzakscontrollingsbs.htm">The controlling subsystem</a></strong><br />
The controlling subsystem is the interactive subsystem that starts automatically when the system starts, and it is the subsystem through which the system operator controls the system via the system console. It is identified in the Controlling subsystem/library (QCTLSBSD) system value.</li>
<li class="ulchildlink"><strong><a href="rzakssbsmultiple.htm">Why consider multiple subsystems</a></strong><br />
As the number of users on the system increases, a single subsystem for a set of work is often insufficient. By dividing your users into multiple subsystems you gain several advantages.</li>
<li class="ulchildlink"><strong><a href="rzakssbsd.htm">Subsystem description</a></strong><br />
A subsystem description is a system object that contains information defining the characteristics of an operating environment controlled by the system. The system-recognized identifier for the object type is *SBSD. A subsystem description defines how, where, and how much work enters a subsystem, and which resources the subsystem uses to perform the work. An active subsystem takes on the simple name of the subsystem description.</li>
<li class="ulchildlink"><strong><a href="rzakswhathappenssbsstarts.htm">How a subsystem starts</a></strong><br />
When a subsystem starts, the system allocates several items and starts autostart and prestart jobs before the subsystem is ready for work.</li>
</ul>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaksconcepts.htm" title="Whether you are new to work management or have been using work management tools for years, you will find something useful in the Concepts section of the Work management topic collection.">Concepts</a></div>
</div>
<div class="reltasks"><strong>Related tasks</strong><br />
<div><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><a href="rzakscreatesubsystemdef.htm" title="You can create a subsystem description in two ways. You can copy an existing subsystem description and change it, or you can create an entirely new description.">Create a subsystem description</a></div>
</div>
<div class="relinfo"><strong>Related information</strong><br />
<div><a href="../experience/work1abstract.htm">Subsystem Configuration experience report</a></div>
</div>
</div>
</body>
</html>