ibm-information-center/dist/eclipse/plugins/i5OS.ic.rzaiw_5.4.0.1/rzaiwreqparam.htm

101 lines
6.1 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="reference" />
<meta name="DC.Title" content="Telnet exit point format INIT0100: Required parameter group" />
<meta name="abstract" content="You can read this topic for detailed definitions of the required parameter group." />
<meta name="description" content="You can read this topic for detailed definitions of the required parameter group." />
<meta name="DC.Relation" scheme="URI" content="rzaiwdevinit.htm" />
<meta name="copyright" content="(C) Copyright IBM Corporation 1998, 2006" />
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 1998, 2006" />
<meta name="DC.Format" content="XHTML" />
<meta name="DC.Identifier" content="rzaiwreqparam" />
<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>Telnet exit point format INIT0100: Required parameter group</title>
</head>
<body id="rzaiwreqparam"><a name="rzaiwreqparam"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">Telnet exit point format INIT0100: Required parameter group</h1>
<div><p>You can read this topic for detailed definitions of the required
parameter group.</p>
<div class="section"><dl><dt class="dlterm">User description information</dt>
<dd> I/O; CHAR(*) Information about the user that the system will use as part
of the auto-signon process.</dd>
<dt class="dlterm">Device description information</dt>
<dd> I/O; CHAR(*) Information that the system will use to create or change
the device that it uses for this Telnet session.</dd>
<dt class="dlterm">Connection description information</dt>
<dd>I/O; CHAR(*) Information about the client connection that the exit program
can use.</dd>
<dt class="dlterm">Environment options</dt>
<dd>INPUT; CHAR(*) An array containing all the RFC 2877 environment options
negotiated by the client. These will be in the exact format that they were
in when received from the client and specified by RFC 2877. The array will,
in general, consist of 1 or more pairs of environment variable names and associated
values. The RFC specifies that each variable name will always be preceded
by either an X'01' or X'03' depending on whether it is an RFC 2877 defined
VAR, or an application specific defined USERVAR. If a value is to be associated
with a VAR (or USERVAR), that value will appear next in the array preceded
by the RFC 1572 defined VALUE character - X'01'. This sequence of VAR/VALUE
pairs will be repeated up to a maximum of 1024 total bytes of negotiation
data.<p>RFC 2877 and the more general Telnet negotiation RFCs also allow for
control characters to appear within the VAR/USERVAR variable names or their
associated values. This is allowed through the use of the ESC character X'02'
and rules that apply when the ESC character itself or Telnet IAC control characters
must appear in the negotiation sequence. Refer to RFC 1572 for a more complete
description of control character escaping rules.</p>
<p>While the environment
options buffer will show negotiations by the client, including passwords,
Telnet will always overlay any clear-text or encrypted password values in
the buffer to avoid security exposures.</p>
</dd>
<dt class="dlterm">Length of environment options</dt>
<dd>The length of the environment options referenced in the preceding paragraph
is typically 1024 bytes. Because option negotiations are of undefined length,
any negotiations that exceed the length specified might be truncated
to fit in the environment options buffer.</dd>
<dt class="dlterm">Allow connection</dt>
<dd> OUTPUT; CHAR(1) Applies to all devices and indicates to the Telnet server
whether it should allow the client to connect. If the device type is DISPLAY
and you have enabled auto-signon, then this client may also bypass the sign-on
panel on the iSeries™ server.
The valid values are as follows:<ul class="simple"><li><span class="uicontrol">0</span> - Reject the request from the client</li>
<li><span class="uicontrol">1</span> - Accept the request from the client</li>
</ul>
</dd>
<dt class="dlterm">Allow auto-signon</dt>
<dd>OUTPUT; CHAR(1) Applies to DISPLAY device types, and indicates to the
Telnet server whether the auto-signon operation should be allowed to proceed
for this particular client. If auto-signon is allowed, then this client can
bypass the sign-on panel on the iSeries server. The valid values are
as follows:<ul class="simple"><li><span class="uicontrol">0</span> - Reject the application request from the client.
The system will ignore the User profile, Current<sup>®</sup> library, Program to call, Initial
menu, and Device name output parameters.</li>
<li><span class="uicontrol">1</span> - Accept the application request from the client.
The system may consider the User profile, Current library, Program to call, Initial
menu, and Device Name output parameters valid if the exit program returns
them.</li>
</ul>
</dd>
</dl>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaiwdevinit.htm" title="This program allows you to associate your custom exit program with exit points on the iSeries Telnet server.">Device initialization exit program</a></div>
</div>
</div>
</body>
</html>