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

67 lines
5.1 KiB
HTML
Raw Permalink 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="task" />
<meta name="DC.Title" content="Device selection exit point" />
<meta name="abstract" content="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." />
<meta name="description" content="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." />
<meta name="DC.Relation" scheme="URI" content="rzakssbsasignuser.htm" />
<meta name="DC.Relation" scheme="URI" content="rzakssbsasignuser1.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="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="rzaksbsasignuser2" />
<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>Device selection exit point</title>
</head>
<body id="rzaksbsasignuser2"><a name="rzaksbsasignuser2"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">Device selection exit point</h1>
<div><p>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.</p>
<div class="section"><p>With this exit point you can specify different naming conventions
for automatically created devices used by Telnet, 5250 Display Station Pass-through,
and the virtual terminal APIs.</p>
<p>In addition, you can manage the Pass-through
devices and Telnet (QAUTOVRT) system value in a more precise manner. For example,
you can allow one value for automatically created devices for Telnet and allow
a different value for 5250 Display Station Pass-through devices. </p>
<p>This
exit point gives you the ability to control the default naming conventions
used for devices (such as QPADEV*) but it alone will not allow you to specify
a particular device for a particular user. This exit point is most useful
if you are using a mix of ways to connect to the system (Telnet, 5250 Display
Station Pass-through, WebFacing, and so on) because it allows you to use different
device naming conventions and precise QAUTOVRT management for
different access methods.</p>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzakssbsasignuser.htm" title="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.">Assigning users to a specific subsystem</a></div>
</div>
<div class="reltasks"><strong>Related tasks</strong><br />
<div><a href="rzakssbsasignuser1.htm" title="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.">Telnet device initialization and terminal exit points</a></div>
<div><a href="rzakssbsasignuser3.htm" title="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.">PC5250 (iSeries Access) workstation ID support</a></div>
<div><a href="rzaksbsasignuser4.htm" title="Using the OS/400 Telnet Client command (STRTCPTELN or TELNET), you can specify the device name that is used to sign on to the server system.">OS/400 Telnet Client</a></div>
<div><a href="rzakssbsasignuser5.htm" title="You can manually create your virtual controllers and devices.">Manually create virtual controllers and devices</a></div>
</div>
</div>
</body>
</html>