83 lines
6.5 KiB
HTML
83 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="Assigning users to a specific subsystem" />
|
||
|
|
<meta name="abstract" content="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." />
|
||
|
|
<meta name="description" content="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." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakssbsintactconfig.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksbsintactconfi8.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakssbsasignuser1.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksbsasignuser2.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakssbsasignuser3.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksbsasignuser4.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakssbsasignuser5.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakswrkstationallocationa.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../experience/work1abstract.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../rzaiw/rzaiwprogramtypes.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="rzakssbsasignuser" />
|
||
|
|
<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>Assigning users to a specific subsystem</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzakssbsasignuser"><a name="rzakssbsasignuser"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Assigning users to a specific subsystem</h1>
|
||
|
|
<div><p>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.</p>
|
||
|
|
<div class="p">The system has a default naming convention that is used for display
|
||
|
|
sessions. At times this proves insufficient for routing workstation entries
|
||
|
|
across multiple subsystems by user profile.</div>
|
||
|
|
<div class="section">You can make changes on your system to enhance the system's default
|
||
|
|
behavior by assigning and managing your own device naming conventions. There
|
||
|
|
are several ways of doing this. Each approach has its own set of advantages
|
||
|
|
and disadvantages.</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<ul class="ullinks">
|
||
|
|
<li class="ulchildlink"><strong><a href="rzakssbsasignuser1.htm">Telnet device initialization and terminal exit points</a></strong><br />
|
||
|
|
Telnet Device Initialization and Terminal Exit Points. These exit points provide the ability to assign device names based upon the client signing on to the system.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzaksbsasignuser2.htm">Device selection exit point</a></strong><br />
|
||
|
|
This exit point allows you to specify the naming convention used for automatically created virtual devices and virtual controllers and to specify the automatic creating limit used for the special requests.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzakssbsasignuser3.htm">PC5250 (iSeries Access) workstation ID support</a></strong><br />
|
||
|
|
You can configure iSeries™ Access to connect with a specific workstation
|
||
|
|
name. If you click the help button from this window, the various
|
||
|
|
options for specifying the workstation ID, like generating a new name if the
|
||
|
|
one specified is already in use, are displayed.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzaksbsasignuser4.htm">OS/400 Telnet Client</a></strong><br />
|
||
|
|
Using the OS/400<sup>®</sup> Telnet Client command (STRTCPTELN or TELNET),
|
||
|
|
you can specify the device name that is used to sign on to the server system.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzakssbsasignuser5.htm">Manually create virtual controllers and devices</a></strong><br />
|
||
|
|
You can manually create your virtual controllers and devices.</li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzakssbsintactconfig.htm" title="The information in this section explains how to set up a new interactive subsystem.">Configure an interactive subsystem</a></div>
|
||
|
|
<div class="previouslink"><strong>Previous topic:</strong> <a href="rzaksbsintactconfi8.htm" title="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.">Configure an interactive subsystem: Configure the console</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><a href="rzakswrkstationallocationa.htm" title="Subsystems attempt to allocate all workstation devices in its subsystem description for AT(*SIGNON) workstation entries.">How workstation devices are allocated</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relinfo"><strong>Related information</strong><br />
|
||
|
|
<div><a href="../experience/work1abstract.htm">Subsystem Configuration experience report</a></div>
|
||
|
|
<div><a href="../rzaiw/rzaiwprogramtypes.htm">Use Telnet exit point programs</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|