119 lines
10 KiB
HTML
119 lines
10 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="Create a subsystem description" />
|
||
|
|
<meta name="abstract" content="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." />
|
||
|
|
<meta name="description" content="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." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksmanagesbs1.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksautostartentry.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksaddcommunentry.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksaddjobqentry.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksaddprestrtjobentry.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksaddroutentry.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksaddwrkstatntry.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakscreatesbsdispfile.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakschgsbsdspfiledesc.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksaboutsbs.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../experience/work1abstract.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakssbsd.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="rzakscreatesubsystemdef" />
|
||
|
|
<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>Create a subsystem description</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzakscreatesubsystemdef"><a name="rzakscreatesubsystemdef"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Create a subsystem description</h1>
|
||
|
|
<div><p>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. </p>
|
||
|
|
<div class="section">The following are two approaches that you can use:</div>
|
||
|
|
<ol><li><span>To copy an existing subsystem description, using the character-based
|
||
|
|
interface, do the following:</span><ol type="a"><li class="substepexpand"><span>Create a Duplicate Object (<span class="cmdname">CRTDUPOBJ</span>) of
|
||
|
|
an existing subsystem description. (You can also use the Work with Objects
|
||
|
|
(<span class="cmdname">WRKOBJ</span>) or Work with Objects using Programming Development
|
||
|
|
Manager (<span class="cmdname">WRKOBJPDM</span>) commands.)</span></li>
|
||
|
|
<li class="substepexpand"><span>Change the copy of the subsystem description so that it functions
|
||
|
|
in the manner that you require.</span> For example, you will need
|
||
|
|
to remove the job queue entry because it identifies the job queue that the
|
||
|
|
original subsystem uses. Then you will need to create a new job queue entry
|
||
|
|
that specifies the parameters that the new subsystem will use.<p>Remember
|
||
|
|
to review the autostart job entries, the workstation entries, the prestart
|
||
|
|
job entries, and the communication entries, and verify that there are no conflicts
|
||
|
|
between the two subsystems. For example, verify that the workstation entries
|
||
|
|
do not cause both subsystems to allocate the same display devices.</p>
|
||
|
|
</li>
|
||
|
|
</ol>
|
||
|
|
</li>
|
||
|
|
<li><span>To create an entirely new subsystem description, use the character-based
|
||
|
|
interface and do the following:</span><ol type="a"><li class="substepexpand"><span>Create a Subsystem Description (<span class="cmdname">CRTSBSD</span>).</span></li>
|
||
|
|
<li class="substepexpand"><span>Create a Job Description (<span class="cmdname">CRTJOBD</span>).</span></li>
|
||
|
|
<li class="substepexpand"><span>Create a Class (<span class="cmdname">CRTCLS</span>) for Add Prestart
|
||
|
|
Job Entry (<span class="cmdname">ADDPJE</span>) and Add Routing Entry (<span class="cmdname">ADDRTGE</span>).</span></li>
|
||
|
|
<li class="substepexpand"><span>Add Work Entries to the subsystem description.</span> <ul><li>Add Workstation Entry (<span class="cmdname">ADDWSE</span> )</li>
|
||
|
|
<li>Add Job Queue Entry (<span class="cmdname">ADDJOBQE</span>)</li>
|
||
|
|
<li>Add Communications Entry (<span class="cmdname">ADDCMNE</span>)</li>
|
||
|
|
<li>Add Autostart Job Entry (<span class="cmdname">ADDAJE</span>)</li>
|
||
|
|
<li>Add Prestart Job Entry (<span class="cmdname">ADDPJE</span>)</li>
|
||
|
|
</ul>
|
||
|
|
</li>
|
||
|
|
<li class="substepexpand"><span>Add Routing Entries (<span class="cmdname">ADDRTGE</span>) to the subsystem
|
||
|
|
description.</span></li>
|
||
|
|
</ol>
|
||
|
|
</li>
|
||
|
|
</ol>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<ul class="ullinks">
|
||
|
|
<li class="ulchildlink"><strong><a href="rzaksautostartentry.htm">Add autostart job entries</a></strong><br />
|
||
|
|
You use the character-based interface to add an autostart job entry. An autostart job starts automatically when the associated subsystem starts. These jobs generally perform initialization work that is associated with a particular subsystem. Autostart jobs can also perform repetitive work or provide centralized service functions for other jobs in the same subsystem.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzaksaddcommunentry.htm">Add communications entries</a></strong><br />
|
||
|
|
Each communication entry describes one or more communication device, device types, or remote location for which the subsystem will start jobs when program start requests are received. The subsystem can allocate a communication device if the device is not currently allocated to another subsystem or job. A communications device that is currently allocated may eventually be de-allocated, making it available to other subsystems. To add a communications entry to the subsystem description, use the character-based interface.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzaksaddjobqentry.htm">Add job queue entries</a></strong><br />
|
||
|
|
A job queue entry identifies a job queue from which jobs are selected for running in the subsystem. Jobs started from a job queue are batch jobs. You add a job queue entry using the character-based interface.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzaksaddprestrtjobentry.htm">Add prestart job entries</a></strong><br />
|
||
|
|
Prestart job entries identify prestart jobs that may be started
|
||
|
|
when the subsystem is started or when the Start Prestart Jobs (<span class="cmdname">STRPJ</span>)
|
||
|
|
command is entered. You can add prestart job entries to the subsystem
|
||
|
|
description by using the character-based interface.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzaksaddroutentry.htm">Add routing entries</a></strong><br />
|
||
|
|
Each routing entry specifies the parameters used to start a routing step for a job. Routing entries identify 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). To add a routing entry to a subsystem description, use the character-based interface.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzaksaddwrkstatntry.htm">Add workstation entries</a></strong><br />
|
||
|
|
A workstation entry is used when a job is started when a user signs on or transfers an interactive job from another subsystem. You can specify the following items in a workstation entry. Parameter names are given in parentheses. Use the character-based interface to add workstation entries.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzakscreatesbsdispfile.htm">Create a signon display file</a></strong><br />
|
||
|
|
The signon display file is used to show signon displays at workstations that are allocated to the subsystem. The signon display file can be changed when the subsystem is active. However, the new signon display file is not used until the next time the subsystem is started. To create a signon display file, use the character-based interface.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzakschgsbsdspfiledesc.htm">Specify the new signon display</a></strong><br />
|
||
|
|
A subsystem uses the signon display file that is specified in the <span class="parmname">SGNDSPF</span> parameter
|
||
|
|
of the subsystem description to create the signon display at a user workstation.
|
||
|
|
To change the signon display file from the default (QDSIGNON) to one that
|
||
|
|
you have created, use the character based interface.</li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaksmanagesbs1.htm" title="Because jobs run in subsystems, you might need to monitor subsystem activity for potential problems that can affect a job's ability to run.">Manage subsystems</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><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><a href="rzakssbsd.htm" title="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.">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>
|