84 lines
6.5 KiB
HTML
84 lines
6.5 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="Configure an interactive subsystem" />
|
||
|
|
<meta name="abstract" content="The information in this section explains how to set up a new interactive subsystem." />
|
||
|
|
<meta name="description" content="The information in this section explains how to set up a new interactive subsystem." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksmanagesbs1.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakssbsintactconfig1.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksbsintactconfi2.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakssbsintactconfig3.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksbsintactconfig4.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakssbsintactconfig5.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakssbsintactconfig6.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakssbsintactconfig7.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksbsintactconfi8.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakssbsasignuser.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="rzakssbsintactconfig" />
|
||
|
|
<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>Configure an interactive subsystem</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzakssbsintactconfig"><a name="rzakssbsintactconfig"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Configure an interactive subsystem</h1>
|
||
|
|
<div><p>The information in this section explains how to set up a new interactive
|
||
|
|
subsystem.</p>
|
||
|
|
<div class="p">These steps are described as if the commands are entered manually.
|
||
|
|
However, you should use a CL program to create your subsystems so that you
|
||
|
|
can easily recreate your configurations for recovery purposes.<p>When you
|
||
|
|
set up a new interactive subsystem you should consider how many devices will
|
||
|
|
be allocated to that subsystem. Since the subsystem performs device management
|
||
|
|
functions, such as presenting the signon display and handling device error
|
||
|
|
recovery, you might want to limit the number of devices allocated to a single
|
||
|
|
subsystem. See the <a href="../rzamp/rzampcomm.htm">Communication
|
||
|
|
limits</a> topic for more information.</p>
|
||
|
|
<div class="note"><span class="notetitle">Note:</span> This information
|
||
|
|
provides a synopsis of what is involved in configuring interactive subsystems.
|
||
|
|
The experience reports about subsystems contain detailed explanations of each
|
||
|
|
step and additional options available for each step. </div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<ol>
|
||
|
|
<li class="olchildlink"><a href="rzakssbsintactconfig1.htm">Configure an interactive subsystem: Create a library</a><br />
|
||
|
|
Create a library in which you store your subsystem configuration objects.</li>
|
||
|
|
<li class="olchildlink"><a href="rzaksbsintactconfi2.htm">Configure an interactive subsystem: Create a class</a><br />
|
||
|
|
Create a class. The class defines certain performance characteristics for your interactive subsystem.</li>
|
||
|
|
<li class="olchildlink"><a href="rzakssbsintactconfig3.htm">Configure an interactive subsystem: Create the subsystem description</a><br />
|
||
|
|
Create the subsystem description. Repeat this step for each subsystem that you need to define.</li>
|
||
|
|
<li class="olchildlink"><a href="rzaksbsintactconfig4.htm">Configure an interactive subsystem: Create a job queue</a><br />
|
||
|
|
Create a job queue for the subsystem using the same name as the subsystem name and add a job queue entry to the subsystem description.</li>
|
||
|
|
<li class="olchildlink"><a href="rzakssbsintactconfig5.htm">Configure an interactive subsystem: Add a routing entry</a><br />
|
||
|
|
Add a routing entry to the subsystem.</li>
|
||
|
|
<li class="olchildlink"><a href="rzakssbsintactconfig6.htm">Configure an interactive subsystem: Add workstation entries</a><br />
|
||
|
|
Add workstation entries to the subsystem description. This is the key step for assigning which devices are allocated to which subsystem.</li>
|
||
|
|
<li class="olchildlink"><a href="rzakssbsintactconfig7.htm">Configure an interactive subsystem: Customize QINTER</a><br />
|
||
|
|
When you begin using your own set of subsystems, you might not need to use QINTER. However, if you have a reason to continue to use QINTER, you need to ensure that QINTER is set up NOT to allocate the workstations that you want to run under your other subsystems. There are two possible ways to do this.</li>
|
||
|
|
<li class="olchildlink"><a href="rzaksbsintactconfi8.htm">Configure an interactive subsystem: Configure the console</a><br />
|
||
|
|
A final, but VERY important consideration regarding QINTER is the workstation type entry of *CONS for the console. Make sure that you do not accidentally prevent someone from signing on at the console. You prevent this from happening by not adding any workstation entries for the console to your custom interactive subsystems.</li>
|
||
|
|
<li class="olchildlink"><a href="rzakssbsasignuser.htm">Assigning users to a specific subsystem</a><br />
|
||
|
|
This topic section discusses several techniques that can be used for assigning device names and then associating those device names with users. After this is accomplished, you can use the workstation entries to get the user to the correct subsystem.</li>
|
||
|
|
</ol>
|
||
|
|
|
||
|
|
<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>
|
||
|
|
</body>
|
||
|
|
</html>
|