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

69 lines
5.9 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="concept" />
<meta name="DC.Title" content="Subsystem description" />
<meta name="abstract" content="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." />
<meta name="description" content="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." />
<meta name="DC.Relation" scheme="URI" content="rzaksaboutsbs.htm" />
<meta name="DC.Relation" scheme="URI" content="rzaksaboutsbsdattributes.htm" />
<meta name="DC.Relation" scheme="URI" content="rzaksaboutworkentries.htm" />
<meta name="DC.Relation" scheme="URI" content="rzaksaboutroutingentries.htm" />
<meta name="DC.Relation" scheme="URI" content="rzakschangesubsytmdesc.htm" />
<meta name="DC.Relation" scheme="URI" content="rzakscreatesubsystemdef.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="rzakssbsd" />
<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>Subsystem description</title>
</head>
<body id="rzakssbsd"><a name="rzakssbsd"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">Subsystem description</h1>
<div><p>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.</p>
<p> Like a set of detailed blueprints, each subsystem description is unique,
containing the specific characteristics that describe the subsystem.
The description includes where work can enter the subsystem, how much work
the subsystem can handle, how much main storage (memory) will be used, and
how quickly jobs in the subsystem can run. </p>
<p>You can use a subsystem description supplied with your system (with or
without making changes to it), or you can create your own. </p>
</div>
<div>
<ul class="ullinks">
<li class="ulchildlink"><strong><a href="rzaksaboutsbsdattributes.htm">Subsystem description attributes</a></strong><br />
Subsystem description attributes are common overall system attributes. When you create a subsystem, the first step is to define the subsystem attributes.</li>
<li class="ulchildlink"><strong><a href="rzaksaboutworkentries.htm">Work entries</a></strong><br />
Work entries identify the sources where jobs can enter a subsystem. Specific types of work entries are used for different types of jobs. Work entries are part of the subsystem description.</li>
<li class="ulchildlink"><strong><a href="rzaksaboutroutingentries.htm">Routing entries</a></strong><br />
The routing entry identifies the main storage subsystem pool to use, the controlling program to run (typically the system-supplied program QCMD), and additional run-time information (stored in the class object). Routing entries are stored in the subsystem description.</li>
</ul>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaksaboutsbs.htm" title="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.">Subsystems</a></div>
</div>
<div class="reltasks"><strong>Related tasks</strong><br />
<div><a href="rzakschangesubsytmdesc.htm" title="The Change Subsystem Description (CHGSBSD) command changes the operational attributes of the specified subsystem description. You can change the subsystem description while the subsystem is active. To change a subsystem description, use the character based interface.">Change a subsystem description</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>
</body>
</html>