Network Working Group T. Murphy, Jr.
Request for Comments: 2877 P. Rieth
Category: Informational J. Stevens
Updates: 1205 IBM Corporation
July 2000
Network Working Group T. Murphy, Jr.
Request for Comments: 2877 P. Rieth
Category: Informational J. Stevens
Updates: 1205 IBM Corporation
July 2000
5250 Telnet Enhancements
5250 Telnet增强功能
Status of this Memo
本备忘录的状况
This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited.
本备忘录为互联网社区提供信息。它没有规定任何类型的互联网标准。本备忘录的分发不受限制。
Copyright Notice
版权公告
Copyright (C) The Internet Society (2000). All Rights Reserved.
版权所有（C）互联网协会（2000年）。版权所有。
Abstract
摘要
This memo describes the interface to the IBM 5250 Telnet server that allows client Telnet to request a Telnet terminal or printer session using a specific device name. If a requested device name is not available, a method to retry the request using a new device name is described. Methods to request specific Telnet session settings and auto-signon function are also described.
本备忘录描述了IBM 5250 Telnet服务器的接口，该接口允许客户端Telnet使用特定设备名称请求Telnet终端或打印机会话。如果请求的设备名称不可用，则说明使用新设备名称重试请求的方法。还描述了请求特定Telnet会话设置和自动登录功能的方法。
By allowing a Telnet client to select the device name, the 5250 Telnet server opens the door for applications to set and/or extract useful information about the Telnet client. Some possibilities are 1) selecting a customized device name associated with a particular user profile name for National Language Support or subsystem routing, 2) connecting PC and network printers as clients and 3) auto-signon using clear-text or DES-encrypted password exchange.
通过允许Telnet客户端选择设备名称，5250 Telnet服务器为应用程序设置和/或提取有关Telnet客户端的有用信息打开了大门。一些可能性包括：1）为国家语言支持或子系统路由选择与特定用户配置文件名称关联的自定义设备名称；2）将PC和网络打印机连接为客户端；3）使用明文或DES加密密码交换进行自动登录。
Applications may need to use system API's on the AS/400 in order to extract Telnet session settings from the device name description. Refer to the Retrieve Device Description (QDCRDEVD) API described in the AS/400 System API book [3] on how to extract information using the DEVD0600 and DEVD1100 templates.
应用程序可能需要使用AS/400上的系统API，以便从设备名称描述中提取Telnet会话设置。关于如何使用DEVD0600和DEVD1100模板提取信息，请参阅AS/400系统API手册[3]中描述的检索设备说明（QDCRDEVD）API。
This memo describes how the IBM 5250 Telnet server supports Work Station Function (WSF) printers using 5250 Display Station Pass-Through. A response code is returned by the Telnet server to indicate success or failure of the WSF printer session.
本备忘录描述了IBM 5250 Telnet服务器如何使用5250显示站直通支持工作站功能（WSF）打印机。Telnet服务器返回一个响应代码，以指示WSF打印机会话的成功或失败。
Table of Contents
目录
1. Enhancing Telnet Negotiations...................... 3
2. Standard Telnet Option Negotiation................. 3
3. Enhanced Telnet Option Negotiation................. 4
4. Enhanced Display Emulation Support................. 7
5. Enhanced Display Auto-Signon and Password
Encryption......................................... 8
5.1 Password Substitutes Processing.............. 12
5.2 Handling passwords of length 9 and 10........ 14
5.3 Example Password Substitute Calculation...... 15
6. Device Name Collision Processing................... 15
7. Enhanced Printer Emulation Support................. 16
8. Telnet Printer Terminal Types...................... 18
9. Telnet Printer Startup Response Record for Printer
Emulators.......................................... 20
9.1 Example of a Success Response Record......... 20
9.2 Example of an Error Response Record.......... 21
9.3 Response Codes............................... 22
10. Printer Steady-State Pass-Through Interface........ 23
10.1 Example of a Print Record.................... 25
10.2 Example of a Print Complete Record........... 27
10.3 Example of a Null Print Record............... 27
11. End-to-End Print Example........................... 28
12. Authors' Note...................................... 33
13. References......................................... 33
14. Security Considerations............................ 35
15. Authors' Addresses................................. 35
16. Relation to Other RFC's............................ 35
17. Full Copyright Statement........................... 36
1. Enhancing Telnet Negotiations...................... 3
2. Standard Telnet Option Negotiation................. 3
3. Enhanced Telnet Option Negotiation................. 4
4. Enhanced Display Emulation Support................. 7
5. Enhanced Display Auto-Signon and Password
Encryption......................................... 8
5.1 Password Substitutes Processing.............. 12
5.2 Handling passwords of length 9 and 10........ 14
5.3 Example Password Substitute Calculation...... 15
6. Device Name Collision Processing................... 15
7. Enhanced Printer Emulation Support................. 16
8. Telnet Printer Terminal Types...................... 18
9. Telnet Printer Startup Response Record for Printer
Emulators.......................................... 20
9.1 Example of a Success Response Record......... 20
9.2 Example of an Error Response Record.......... 21
9.3 Response Codes............................... 22
10. Printer Steady-State Pass-Through Interface........ 23
10.1 Example of a Print Record.................... 25
10.2 Example of a Print Complete Record........... 27
10.3 Example of a Null Print Record............... 27
11. End-to-End Print Example........................... 28
12. Authors' Note...................................... 33
13. References......................................... 33
14. Security Considerations............................ 35
15. Authors' Addresses................................. 35
16. Relation to Other RFC's............................ 35
17. Full Copyright Statement........................... 36
LIST OF FIGURES
数字一览表
Figure 1. Example of a success status response
record....................................... 20
Figure 2. Example of an error response record.......... 21
Figure 3. Layout of the printer pass-through
header....................................... 23
Figure 4. Server sending client data with a print
record....................................... 26
Figure 5. Client sending server a print complete
record....................................... 27
Figure 6. Server sending client a null print
record....................................... 28
Figure 1. Example of a success status response
record....................................... 20
Figure 2. Example of an error response record.......... 21
Figure 3. Layout of the printer pass-through
header....................................... 23
Figure 4. Server sending client data with a print
record....................................... 26
Figure 5. Client sending server a print complete
record....................................... 27
Figure 6. Server sending client a null print
record....................................... 28
The 5250 Telnet server enables clients to negotiate both terminal and printer device names through Telnet Environment Options Negotiations, defined in the Standards Track RFC 1572 [13].
5250 Telnet服务器使客户端能够通过Telnet环境选项协商（在标准跟踪RFC 1572[13]中定义）协商终端和打印机设备名称。
The purpose of RFC 1572 is to exchange environment information using a set of standard or custom variables. By using a combination of both standard VAR's and custom USERVAR's, the 5250 Telnet server allows client Telnet to request a pre-defined specific device by name.
RFC 1572的目的是使用一组标准或自定义变量交换环境信息。通过结合使用标准VAR和自定义USERVAR，5250 Telnet服务器允许客户端Telnet按名称请求预定义的特定设备。
If no pre-defined device exists then the device will be created, with client Telnet having the option to negotiate device attributes, such as the code page, character set, keyboard type, etc.
如果不存在预定义设备，则将创建该设备，客户端Telnet可以选择协商设备属性，如代码页、字符集、键盘类型等。
Since printers can now be negotiated as a device name, new terminal types have been defined to request printers. For example, you can now negotiate "IBM-3812-1" and "IBM-5553-B01" as valid TERMINAL-TYPE options [11].
由于现在可以将打印机协商为设备名称，因此定义了新的终端类型以请求打印机。例如，您现在可以协商“IBM-3812-1”和“IBM-5553-B01”作为有效的终端类型选项[11]。
Finally, the 5250 Telnet server will allow exchange of user profile and password information, where the password may be in either clear-text or encrypted form. If a valid combination of profile and password is received, then the client is allowed to bypass the sign-on panel. The setting of the QRMTSIGN system value must be either *VERIFY or *SAMEPRF for the bypass of the sign-on panel to succeed.
最后，5250 Telnet服务器将允许交换用户配置文件和密码信息，其中密码可以是明文或加密形式。如果收到配置文件和密码的有效组合，则允许客户端绕过登录面板。QRMTSIGN系统值的设置必须为*VERIFY或*SAMEPRF，才能成功绕过登录面板。
Telnet server option negotiation typically begins with the issuance, by the server, of an invitation to engage in terminal type negotiation with the Telnet client (DO TERMINAL-TYPE) [11]. The client and server then enter into a series of sub-negotiations to determine the level of terminal support that will be used. After the terminal type is agreed upon, the client and server will normally negotiate a required set of additional options (EOR [12], BINARY [10], SGA [15]) that are required to support "transparent mode" or full screen 5250/3270 block mode support. As soon as the required options have been negotiated, the server will suspend further negotiations, and begin with initializing the actual virtual device on the AS/400. A typical exchange might start like the following:
Telnet服务器选项协商通常始于服务器发出邀请，邀请与Telnet客户端进行终端类型协商（DO terminal-type）[11]。然后，客户机和服务器进入一系列子协商，以确定将使用的终端支持级别。在商定终端类型后，客户机和服务器通常会协商一组所需的附加选项（EOR[12]、二进制[10]、SGA[15]），这些选项是支持“透明模式”或全屏5250/3270块模式所需的。一旦协商了所需的选项，服务器将暂停进一步协商，并开始初始化As/400上的实际虚拟设备。典型的交换可能会如下所示开始：
AS/400 Telnet server Enhanced Telnet client
-------------------------- -------------------------
IAC DO TERMINAL-TYPE -->
<-- IAC WILL TERMINAL-TYPE
IAC SB TERMINAL-TYPE SEND
IAC SE -->
IAC SB TERMINAL-TYPE IS
<-- IBM-5555-C01 IAC SE
IAC DO EOR -->
<-- IAC WILL EOR
<-- IAC DO EOR
IAC WILL EOR -->
.
.
(other negotiations) .
AS/400 Telnet server Enhanced Telnet client
-------------------------- -------------------------
IAC DO TERMINAL-TYPE -->
<-- IAC WILL TERMINAL-TYPE
IAC SB TERMINAL-TYPE SEND
IAC SE -->
IAC SB TERMINAL-TYPE IS
<-- IBM-5555-C01 IAC SE
IAC DO EOR -->
<-- IAC WILL EOR
<-- IAC DO EOR
IAC WILL EOR -->
.
.
(other negotiations) .
Actual bytes transmitted in the above example are shown in hex below.
在上述示例中传输的实际字节以十六进制表示。
AS/400 Telnet server Enhanced Telnet client
-------------------------- -------------------------
FF FD 18 -->
<-- FF FB 18
FF FA 18 01 FF F0 -->
FF FA 18 00 49 42 4D 2D
35 35 35 35 2D 43 30 31
<-- FF F0
FF FD 19 -->
<-- FF FB 19
<-- FF FD 19
FF FB 19 -->
.
.
(other negotiations) .
AS/400 Telnet server Enhanced Telnet client
-------------------------- -------------------------
FF FD 18 -->
<-- FF FB 18
FF FA 18 01 FF F0 -->
FF FA 18 00 49 42 4D 2D
35 35 35 35 2D 43 30 31
<-- FF F0
FF FD 19 -->
<-- FF FB 19
<-- FF FD 19
FF FB 19 -->
.
.
(other negotiations) .
Some negotiations are symmetrical between client and server and some are negotiated in one direction only. Also, it is permissible and common practice to bundle more than one response or request, or combine a request with a response, so the actual exchange may look different in practice to what is shown above.
有些协商在客户端和服务器之间是对称的，有些协商只在一个方向上进行。另外，捆绑多个响应或请求，或者将一个请求与一个响应结合起来，这是允许的，也是常见的做法，因此实际的交换在实践中可能与上面所示的不同。
In order to accommodate the new environment option negotiations, the server will bundle an environment option invitation along with the standard terminal type invitation request to the client.
为了适应新的环境选项协商，服务器将把环境选项邀请与标准终端类型邀请请求捆绑到客户端。
A client should either send a negative acknowledgment (WONT NEW-ENVIRON), or at some point after completing terminal-type negotiations, but before completing the full set of negotiations required for 5250 transparent mode, engage in environment option sub-negotiation with the server. A maximum of 1024 bytes of environment strings may be sent to the server. A recommended sequence might look like the following:
客户端应发送否定确认（不会是NEW-ENVIRON），或在完成终端类型协商后的某个时间点，但在完成5250透明模式所需的整套协商之前，与服务器进行环境选项子协商。最多可向服务器发送1024字节的环境字符串。建议的顺序可能如下所示：
AS/400 Telnet server Enhanced Telnet client
-------------------------- -------------------------
IAC DO NEW-ENVIRON
IAC DO TERMINAL-TYPE -->
(2 requests bundled)
<-- IAC WILL NEW-ENVIRON
IAC SB NEW-ENVIRON SEND
VAR IAC SE -->
IAC SB NEW-ENVIRON IS
VAR "USER" VALUE "JONES"
USERVAR "DEVNAME"
VALUE "MYDEVICE07"
<-- IAC SE
<-- IAC WILL TERMINAL-TYPE
(do the terminal type
sequence first)
IAC SB TERMINAL-TYPE SEND
IAC SE -->
IAC SB TERMINAL-TYPE IS
<-- IBM-5555-C01 IAC SE
(terminal type negotiations
completed)
IAC DO EOR -->
(server will continue
with normal transparent
mode negotiations)
<-- IAC WILL EOR
.
.
(other negotiations) .
AS/400 Telnet server Enhanced Telnet client
-------------------------- -------------------------
IAC DO NEW-ENVIRON
IAC DO TERMINAL-TYPE -->
(2 requests bundled)
<-- IAC WILL NEW-ENVIRON
IAC SB NEW-ENVIRON SEND
VAR IAC SE -->
IAC SB NEW-ENVIRON IS
VAR "USER" VALUE "JONES"
USERVAR "DEVNAME"
VALUE "MYDEVICE07"
<-- IAC SE
<-- IAC WILL TERMINAL-TYPE
(do the terminal type
sequence first)
IAC SB TERMINAL-TYPE SEND
IAC SE -->
IAC SB TERMINAL-TYPE IS
<-- IBM-5555-C01 IAC SE
(terminal type negotiations
completed)
IAC DO EOR -->
(server will continue
with normal transparent
mode negotiations)
<-- IAC WILL EOR
.
.
(other negotiations) .
Actual bytes transmitted in the above example are shown in hex below.
在上述示例中传输的实际字节以十六进制表示。
AS/400 Telnet server Enhanced Telnet client
-------------------------- -------------------------
FF FD 27
FF FD 18 -->
(2 requests bundled)
<-- FF FB 27
FF FA 27 01 00 FF F0 -->
AS/400 Telnet server Enhanced Telnet client
-------------------------- -------------------------
FF FD 27
FF FD 18 -->
(2 requests bundled)
<-- FF FB 27
FF FA 27 01 00 FF F0 -->
FF FA 27 00 00 55 53 45 52 01 4A 4F 4E 45 53 03 44 45 56 4E 41 4D 45 01 4D 59 44 45 56 49 43 45 <-- 30 37 FF F0 <-- FF FB 18 (do the terminal type sequence first) FF FA 18 01 FF F0 --> FF FA 18 00 49 42 4D 2D 35 35 35 35 2D 43 30 31 <-- FF F0 FF FD 19 --> (server will continue with normal transparent mode negotiations) <-- FF FB 19 . . (other negotiations) .
FF FA 27 00 00 55 53 45 52 01 4A 4F 4E 45 53 03 44 45 56 4E 41 4D 45 01 4D 59 44 45 56 43 45<--30 37 FF F0<--FF FB 18（首先执行终端类型序列）FF FA 18 01 FF F0-->FF FA 18 00 49 42 4D 2D 35 35 35 2D 43 30 31<--FF F0 FF FD 19-->（服务器将继续进行正常透明模式协商）<--FF FB 19。（其他谈判）。
RFC 1572 defines 6 standard VAR's: USER, JOB, ACCT, PRINTER, SYSTEMTYPE, and DISPLAY. The USER standard VAR will hold the value of the AS/400 user profile name to be used in auto-signon requests. The Telnet server will make no direct use of the additional 5 VAR's, nor are any of them required to be sent. All standard VAR's and their values that are received by the Telnet server will be placed in a buffer, along with any USERVAR's received (described below), and made available to a registered initialization exit program to be used for any purpose desired.
RFC1572定义了6个标准变量：用户、作业、帐户、打印机、系统类型和显示。用户标准变量将保存自动登录请求中使用的AS/400用户配置文件名的值。Telnet服务器不会直接使用额外的5个VAR，也不需要发送其中任何一个。Telnet服务器接收到的所有标准VAR及其值将与接收到的任何USERVAR（如下所述）一起放置在缓冲区中，并可供注册的初始化退出程序用于任何预期目的。
There are some reasons you may want to send NEW-ENVIRON negotiations prior to TERMINAL-TYPE negotiations. With AS/400 TELNET server, several virtual device modes can be negotiated: 1) VTxxx device 2) 3270 device 3) 5250 device (includes Network Station). The virtual device mode selected depends on the TERMINAL-TYPE negotiated plus any other TELNET option negotiations necessary to support those modes. The AS/400 TELNET server will create the desired virtual device at the first opportunity it thinks it has all the requested attributes needed to create the device. This can be as early as completion of the TERMINAL-TYPE negotiations.
在终端类型协商之前，您可能希望发送新环境协商，这有一些原因。使用AS/400 TELNET服务器，可以协商几种虚拟设备模式：1）VTxxx设备2）3270设备3）5250设备（包括网络站）。选择的虚拟设备模式取决于协商的终端类型以及支持这些模式所需的任何其他TELNET选项协商。AS/400 TELNET服务器将在其认为具有创建设备所需的所有请求属性的第一时间创建所需的虚拟设备。这可以尽早完成终端式谈判。
For the case of Transparent mode (5250 device), then the moment TERMINAL-TYPE, BINARY, and EOR options are negotiated the TELNET server will go create the virtual device. Receiving any NEW-ENVIRON negotiations after these option negotiations are complete will result in the NEW-ENVIRON negotiations having no effect on device attributes, as the virtual device will have already been created.
对于透明模式（5250设备），一旦协商终端类型、二进制和EOR选项，TELNET服务器将创建虚拟设备。在这些选项协商完成后接收任何新环境协商将导致新环境协商对设备属性没有影响，因为虚拟设备已经创建。
So, for Transparent mode, NEW-ENVIRON negotiations are effectively closed once EOR is negotiated, since EOR is generally the last option done.
因此，对于透明模式，一旦协商EOR，新环境谈判将有效结束，因为EOR通常是最后一个选择。
For other devices modes (such as VTxxx or 3270), you cannot be sure when the AS/400 TELNET server thinks it has all the attributes to create the device. Recall that NEW-ENVIRON negotiations are optional, and therefore the AS/400 TELNET server need not wait for any NEW-ENVIRON options prior to creating the virtual device. It is in the clients best interest to send NEW-ENVIRON negotiations as soon as possible, preferably before TERMINAL-TYPE is negotiated. That way, the client can be sure the requested attributes were received before the virtual device is created.
对于其他设备模式（如VTxxx或3270），您无法确定as/400 TELNET服务器何时认为它具有创建设备的所有属性。回想一下，NEW-ENVIRON协商是可选的，因此AS/400 TELNET服务器在创建虚拟设备之前无需等待任何NEW-ENVIRON选项。为了客户的最大利益，应尽快发送NEW-ENVIRON谈判，最好在终端类型谈判之前发送。这样，客户端可以确保在创建虚拟设备之前收到请求的属性。
RFC 1572 style USERVAR variables have been defined to allow a compliant Telnet client more control over the Telnet server virtual device on the AS/400. These USERVAR's allow the client Telnet to create or select a previously created virtual device. If the virtual device does not exist and must be created, then the USERVAR variables are used to create and initialize the device attributes. If the virtual device already exists, the device attributes are modified.
已定义RFC 1572样式的USERVAR变量，以允许兼容的Telnet客户端对AS/400上的Telnet服务器虚拟设备进行更多控制。这些USERVAR允许客户端Telnet创建或选择以前创建的虚拟设备。如果虚拟设备不存在且必须创建，则使用USERVAR变量创建和初始化设备属性。如果虚拟设备已存在，则修改设备属性。
The USERVAR's defined to accomplish this are:
为实现这一点而定义的用户变量包括：
USERVAR VALUE EXAMPLE DESCRIPTION
-------- ---------------- ---------------- -------------------
DEVNAME us-ascii char(x) MYDEVICE07 Display device name
KBDTYPE us-ascii char(3) USB Keyboard type
CODEPAGE us-ascii char(y) 437 Code page
CHARSET us-ascii char(y) 1212 Character set
USERVAR VALUE EXAMPLE DESCRIPTION
-------- ---------------- ---------------- -------------------
DEVNAME us-ascii char(x) MYDEVICE07 Display device name
KBDTYPE us-ascii char(3) USB Keyboard type
CODEPAGE us-ascii char(y) 437 Code page
CHARSET us-ascii char(y) 1212 Character set
x - up to a maximum of 10 characters y - up to a maximum of 5 characters
x-最多10个字符y-最多5个字符
For a description of the KBDTYPE, CODEPAGE and CHARSET parameters and their permissible values, refer to Chapter 8 in the Communications Configuration Reference [5] and also to Appendix C in National Language Support [16].
有关KBDTYPE、CODEPAGE和CHARSET参数及其允许值的说明，请参阅通信配置参考[5]中的第8章以及国家语言支持[16]中的附录C。
The CODEPAGE and CHARSET USERVAR's must be associated with a KBDTYPE USERVAR. If either CODEPAGE or CHARSET are sent without KBDTYPE, they will default to system values. A default value for KBDTYPE can be sent to force CODEPAGE and CHARSET values to be used.
代码页和字符集USERVAR必须与KBDTYPE USERVAR相关联。如果发送的代码页或字符集没有KBDTYPE，它们将默认为系统值。可以发送KBDTYPE的默认值以强制使用代码页和字符集值。
AS/400 system objects such as device names, user profiles, clear-text passwords, programs, libraries, etc. are required to be specified in English Upper Case (EUC). This includes:
AS/400系统对象，如设备名称、用户配置文件、明文密码、程序、库等，需要以英文大写字母（EUC）指定。这包括：
Any letter (A-Z), any number (0-9), special characters (# $ _ @)
任意字母（A-Z）、任意数字（0-9）、特殊字符（#$@）
Therefore, where us-ascii is specified for VAR or USERVAR values, it is recommended that upper-cased ASCII values be sent, which will be converted to EBCDIC by the Telnet server.
因此，如果为VAR或USERVAR值指定us ascii，建议发送大写ascii值，Telnet服务器将其转换为EBCDIC。
A special case occurs for encrypted passwords (described in the next section), where both the initial password and user profile used to build the encrypted password must be EBCDIC English Upper Case, in order to be properly authenticated by the Telnet server.
加密密码有一种特殊情况（将在下一节中介绍），其中用于生成加密密码的初始密码和用户配置文件都必须是EBCDIC英语大写字母，以便由Telnet服务器正确验证。
Several 5250 Telnet server specific USERVAR's will be defined. One will carry a random seed to be used in Data Encryption Standard (DES) password encryption, and another will carry the encrypted copy of the password. This would use the same 7-step DES-based password substitution scheme as APPC and Client Access. For a description of DES encryption, refer to Federal Information Processing Standards Publications (FIPS) 46-2 [17] and 81 [18], which can be found at the Federal Information Processing Standards Publications link:
将定义几个5250 Telnet服务器特定的用户变量。其中一个将携带随机种子用于数据加密标准（DES）密码加密，另一个将携带密码的加密副本。这将使用与APPC和客户端访问相同的7步DES密码替换方案。有关DES加密的说明，请参阅联邦信息处理标准出版物（FIPS）46-2[17]和81[18]，可在联邦信息处理标准出版物链接中找到：
http://www.itl.nist.gov/div897/pubs/by-num.htm
http://www.itl.nist.gov/div897/pubs/by-num.htm
For a description of the 7-step password substitution scheme, refer to these IBM Customer Support FTP Server links:
有关7步密码替换方案的说明，请参阅以下IBM客户支持FTP服务器链接：
ftp://ftp.networking.ibm.com/pub/standards/ciw/sig/sec/pwsubciw.ps
ftp://ftp.networking.ibm.com/pub/standards/ciw/sig/sec/pwsubciw.ps.Z
ftp://ftp.networking.ibm.com/pub/standards/ciw/sig/sec/pwsubciw.zip
ftp://ftp.networking.ibm.com/pub/standards/ciw/sig/sec/pwsubciw.ps
ftp://ftp.networking.ibm.com/pub/standards/ciw/sig/sec/pwsubciw.ps.Z
ftp://ftp.networking.ibm.com/pub/standards/ciw/sig/sec/pwsubciw.zip
If encrypted password exchange is not required, clear-text password exchange is permitted using the same USERVAR's defined for encryption. For this case, the random client seed should be set to either an empty value (RFC 1572 preferred method) or to hexadecimal zeros to indicate the password is not encrypted, but is clear-text.
如果不需要加密密码交换，则允许使用为加密定义的相同用户变量进行明文密码交换。对于这种情况，应将随机客户端种子设置为空值（RFC 1572首选方法）或十六进制零，以指示密码未加密，而是明文。
It should be noted that security of clear-text password exchange cannot be guaranteed unless the network is physically protected or a trusted network (such as an intranet). If your network is vulnerable to IP address spoofing or directly connected to the Internet, you should engage in encrypted password exchange to validate a clients identity.
应注意的是，除非网络受到物理保护或是受信任的网络（如内部网），否则无法保证明文密码交换的安全性。如果您的网络容易受到IP地址欺骗或直接连接到Internet的攻击，则应进行加密密码交换以验证客户端身份。
Additional VAR's and USERVAR's have also been defined to allow an auto-signon user greater control over their startup environment, similar to what is supported using the Open Virtual Terminal (QTVOPNVT) API [3].
还定义了其他VAR和USERVAR，以允许自动登录用户更好地控制其启动环境，类似于使用开放虚拟终端（QTVOPNVT）API支持的方式[3]。
The standard VAR's supported to accomplish this are:
为实现这一点，支持的标准VAR包括：
VAR VALUE EXAMPLE DESCRIPTION
-------- ---------------- ---------------- -------------------
USER us-ascii char(x) USERXYZ User profile name
VAR VALUE EXAMPLE DESCRIPTION
-------- ---------------- ---------------- -------------------
USER us-ascii char(x) USERXYZ User profile name
x - up to a maximum of 10 characters
x-最多10个字符
The custom USERVAR's defined to accomplish this are:
为实现此目的而定义的自定义用户变量包括：
USERVAR VALUE EXAMPLE DESCRIPTION
-------- ---------------- ---------------- -------------------
IBMRSEED binary(8) 8-byte hex field Random client seed
IBMSUBSPW binary(10) 10-byte hex field Substitute password
IBMCURLIB us-ascii char(x) QGPL Current library
IBMIMENU us-ascii char(x) MAIN Initial menu
IBMPROGRAM us-ascii char(x) QCMD Program to call
USERVAR VALUE EXAMPLE DESCRIPTION
-------- ---------------- ---------------- -------------------
IBMRSEED binary(8) 8-byte hex field Random client seed
IBMSUBSPW binary(10) 10-byte hex field Substitute password
IBMCURLIB us-ascii char(x) QGPL Current library
IBMIMENU us-ascii char(x) MAIN Initial menu
IBMPROGRAM us-ascii char(x) QCMD Program to call
x - up to a maximum of 10 characters
x-最多10个字符
In order to communicate the server random seed value to the client, the server will request a USERVAR name made up of a fixed part (the 8 characters "IBMRSEED" immediately followed by an 8-byte hexadecimal variable part, which is the server random seed. The client generates its own 8-byte random seed value, and uses both seeds to encrypt the password. Both the encrypted password and the client random seed value are then sent to the server for authentication. RFC 1572 rules will need to be adhered to when transmitting the client random seed and substituted password values to the server. Specifically, since a typical environment string is a variable length hexadecimal field, the hexadecimal fields are required to be escaped and/or byte stuffed according to the RFC 854 [8], where any single byte could be mis-construed as a Telnet IAC or other Telnet option negotiation control character. The client must escape and/or byte stuff any bytes which could be seen as a RFC 1572 [13] option, specifically VAR, VALUE, ESC and USERVAR.
为了将服务器随机种子值传递给客户端，服务器将请求一个由固定部分组成的USERVAR名称（8个字符“IBMRSEED”）紧接着是一个8字节的十六进制变量部分，即服务器随机种子。客户端生成自己的8字节随机种子值，并使用两个种子对密码进行加密。然后将加密的密码和客户端随机种子值发送到服务器进行身份验证。在n将客户端随机种子和替换密码值传输到服务器。具体而言，由于典型的环境字符串是长度可变的十六进制字段，因此十六进制字段需要根据RFC 854[8]进行转义和/或字节填充，其中任何单个字节都可能被错误地解释为Telnet IAC或其他Telnet选项协商控制字符。客户端必须转义和/或字节填充任何可能被视为RFC 1572[13]选项的字节，特别是VAR、VALUE、ESC和USERVAR。
The following illustrates the encrypted case:
以下说明了加密的案例：
AS/400 Telnet server Enhanced Telnet client
-------------------------- -------------------------------
IAC DO NEW-ENVIRON -->
<-- IAC WILL NEW-ENVIRON
IAC SB NEW-ENVIRON SEND
USERVAR "IBMRSEEDxxxxxxxx"
USERVAR "IBMSUBSPW"
VAR USERVAR IAC SE -->
IAC SB NEW-ENVIRON IS
VAR "USER" VALUE "DUMMYUSR"
USERVAR "IBMRSEED" VALUE "yyyyyyyy"
USERVAR "IBMSUBSPW" VALUE "zzzzzzzz"
<-- IAC SE
.
.
(other negotiations) .
AS/400 Telnet server Enhanced Telnet client
-------------------------- -------------------------------
IAC DO NEW-ENVIRON -->
<-- IAC WILL NEW-ENVIRON
IAC SB NEW-ENVIRON SEND
USERVAR "IBMRSEEDxxxxxxxx"
USERVAR "IBMSUBSPW"
VAR USERVAR IAC SE -->
IAC SB NEW-ENVIRON IS
VAR "USER" VALUE "DUMMYUSR"
USERVAR "IBMRSEED" VALUE "yyyyyyyy"
USERVAR "IBMSUBSPW" VALUE "zzzzzzzz"
<-- IAC SE
.
.
(other negotiations) .
In this example, "xxxxxxxx" is an 8-byte hexadecimal random server seed, "yyyyyyyy" is an 8-byte hexadecimal random client seed and "zzzzzzzz" is an 8-byte hexadecimal encrypted password. If the password is not valid, then the sign-on panel is displayed. If the password is expired, then the Change Password panel is displayed.
在本例中，“xxxxxxxx”是一个8字节的十六进制随机服务器种子，“yyyyyyy”是一个8字节的十六进制随机客户端种子，“zzzzzz”是一个8字节的十六进制加密密码。如果密码无效，则会显示登录面板。如果密码过期，则显示更改密码面板。
Actual bytes transmitted in the above example are shown in hex below, where the server seed is "7D3E488F18080404", the client seed is "4E4142334E414233" and the encrypted password is "DFB0402F22ABA3BA". The user profile used to generate the encrypted password is "44554D4D59555352" (DUMMYUSR), with a clear-text password of "44554D4D595057" (DUMMYPW).
上述示例中传输的实际字节如下所示，其中服务器种子为“7D3E488F18080404”，客户端种子为“4E4142334E414233”，加密密码为“DFB0402F22F22ABA3BA”。用于生成加密密码的用户配置文件为“44554D59555352”（DUMMYUSR），明文密码为“44554D595057”（DUMMYPW）。
AS/400 Telnet server Enhanced Telnet client
-------------------------- -------------------------
FF FD 27 -->
<-- FF FB 27
FF FA 27 01 03 49 42 4D
52 53 45 45 44 7D 3E 48
8F 18 08 04 04 03 49 42
4D 53 55 42 53 50 57 03
00 FF F0 -->
FF FA 27 00 00 55 53 45
52 01 44 55 4D 4D 59 55
53 52 03 49 42 4D 52 53
45 45 44 01 4E 41 42 33
4E 41 42 33 03 49 42 4D
AS/400 Telnet server Enhanced Telnet client
-------------------------- -------------------------
FF FD 27 -->
<-- FF FB 27
FF FA 27 01 03 49 42 4D
52 53 45 45 44 7D 3E 48
8F 18 08 04 04 03 49 42
4D 53 55 42 53 50 57 03
00 FF F0 -->
FF FA 27 00 00 55 53 45
52 01 44 55 4D 4D 59 55
53 52 03 49 42 4D 52 53
45 45 44 01 4E 41 42 33
4E 41 42 33 03 49 42 4D
53 55 42 53 50 57 01 DF B0 40 2F 22 AB A3 BA FF <-- F0
53 55 42 53 50 57 01 DF B0 40 2F 22 AB A3 BA FF<--F0
The following illustrates the clear-text case:
以下说明了明文案例：
AS/400 Telnet server Enhanced Telnet client
-------------------------- -------------------------
IAC DO NEW-ENVIRON -->
<-- IAC WILL NEW-ENVIRON
IAC SB NEW-ENVIRON SEND
USERVAR "IBMRSEEDxxxxxxxx"
USERVAR "IBMSUBSPW"
VAR USERVAR IAC SE -->
IAC SB NEW-ENVIRON IS
VAR "USER" VALUE "DUMMYUSR"
USERVAR "IBMRSEED" VALUE
USERVAR "IBMSUBSPW" VALUE "yyyyyyyy"
<-- IAC SE
.
.
(other negotiations) .
AS/400 Telnet server Enhanced Telnet client
-------------------------- -------------------------
IAC DO NEW-ENVIRON -->
<-- IAC WILL NEW-ENVIRON
IAC SB NEW-ENVIRON SEND
USERVAR "IBMRSEEDxxxxxxxx"
USERVAR "IBMSUBSPW"
VAR USERVAR IAC SE -->
IAC SB NEW-ENVIRON IS
VAR "USER" VALUE "DUMMYUSR"
USERVAR "IBMRSEED" VALUE
USERVAR "IBMSUBSPW" VALUE "yyyyyyyy"
<-- IAC SE
.
.
(other negotiations) .
In this example, "xxxxxxxx" is an 8-byte hexadecimal random server seed, "yyyyyyyyyy" is a 10-byte us-ascii client clear-text password. If the password has expired, then the sign-on panel is displayed.
在本例中，“xxxxxxxx”是一个8字节的十六进制随机服务器种子，“YYYYYYYY”是一个10字节的美国ascii客户端明文密码。如果密码已过期，则会显示登录面板。
Actual bytes transmitted in the above example are shown in hex below, where the server seed is "7D3E488F18080404", the client seed is empty and the clear-text password is "44554D4D595057" (DUMMYPW). The user profile used is "44554D4D59555352" (DUMMYUSR).
上面示例中传输的实际字节如下所示，其中服务器种子为“7D3E488F18080404”，客户端种子为空，明文密码为“44554D45950507”（DUMMYPW）。使用的用户配置文件是“44554D59555352”（DUMMYUSR）。
AS/400 Telnet server Enhanced Telnet client
-------------------------- -------------------------
FF FD 27 -->
<-- FF FB 27
FF FA 27 01 03 49 42 4D
52 53 45 45 44 7D 3E 48
8F 18 08 04 04 03 49 42
4D 53 55 42 53 50 57 03
00 FF F0 -->
FF FA 27 00 00 55 53 45
52 01 44 55 4D 4D 59 55
53 52 03 49 42 4D 52 53
45 45 44 01 03 49 42 4D
53 55 42 53 50 57 01 44
<-- 55 4D 4D 59 50 57 FF F0
AS/400 Telnet server Enhanced Telnet client
-------------------------- -------------------------
FF FD 27 -->
<-- FF FB 27
FF FA 27 01 03 49 42 4D
52 53 45 45 44 7D 3E 48
8F 18 08 04 04 03 49 42
4D 53 55 42 53 50 57 03
00 FF F0 -->
FF FA 27 00 00 55 53 45
52 01 44 55 4D 4D 59 55
53 52 03 49 42 4D 52 53
45 45 44 01 03 49 42 4D
53 55 42 53 50 57 01 44
<-- 55 4D 4D 59 50 57 FF F0
Both APPC and Client Access use well-known DES encryption algorithms to create encrypted passwords. A Network Station or Enhanced Client can generate compatible encrypted passwords if they follow these steps, details of which can be found in the Federal Information Processing Standards 46-2 [17].
APPC和客户端访问都使用众所周知的DES加密算法来创建加密密码。如果遵循这些步骤，网络站或增强型客户端可以生成兼容的加密密码，其详细信息可在联邦信息处理标准46-2[17]中找到。
1. Padded_PW = Left justified user password padded to the right with '40'X to 8 bytes.
1. Padded_PW=左对齐的用户密码，用“40”X到8字节填充到右侧。
The users password must be left justified in an 8 byte variable and padded to the right with '40'X up to an 8 byte length. If the users password is 8 bytes in length, no padding would occur. For computing password substitutes for passwords of length 9 and 10 see section "Handling passwords of length 9 and 10" below. Passwords less than 1 byte or greater than 10 bytes in length are not valid. Please note, if password is not in EBCDIC, it must be converted to EBCDIC uppercase.
用户密码必须在8字节变量中左对齐，并在右侧填充“40”X，最大长度为8字节。如果用户密码长度为8字节，则不会出现填充。有关计算长度为9和10的密码替代品的信息，请参见下文“处理长度为9和10的密码”一节。长度小于1字节或大于10字节的密码无效。请注意，如果密码不在EBCDIC中，则必须将其转换为EBCDIC大写字母。
2. XOR_PW = Padded_PW xor '5555555555555555'X
2. XOR_PW=填充_PW XOR'555555555555'X
The padded password is Exclusive OR'ed with 8 bytes of '55'X.
填充的密码是独占的或，包含8个字节的'55'X。
3. SHIFT_RESULT = XOR_PW << 1
3. 移位结果=XOR\U PW<<1
The entire 8 byte result is shifted 1 bit to the left; the leftmost bit value is discarded, and the rightmost bit value is cleared to 0.
整个8字节结果向左移位1位；最左边的位值被丢弃，最右边的位值被清除为0。
4. PW_TOKEN = DES_ECB_mode(SHIFT_RESULT, /* key */ userID_in_EBCDIC_uppercase /* data */ )
4. PW_TOKEN=DES_ECB_mode（SHIFT_RESULT，/*key*/userID_in_EBCDIC_大写/*data*/）
This shifted result is used as key to the Data Encryption Standard (Federal Information Processing Standards 46-2 [17]) to encipher the user identifier. When the user identifier is less than 8 bytes, it is left justified in an 8 byte variable and padded to the right with '40'X. When the user identifier is 9 or 10 bytes, it is first padded to the right with '40'X to a length of 10 bytes. Then bytes 9 and 10 are "folded" into bytes 1-8 using the following algorithm:
该移位结果用作数据加密标准（联邦信息处理标准46-2[17]）的密钥，以加密用户标识符。当用户标识符小于8字节时，将在8字节变量中左对齐，并用“40”X向右填充。当用户标识符为9或10字节时，首先用“40”X向右填充，长度为10字节。然后使用以下算法将字节9和10“折叠”为字节1-8：
Bit 0 is the high-order bit (i.e. has value of '80'X).
位0是高阶位（即值为'80'X）。
Byte 1, bits 0 and 1 are replaced with byte 1, bits 0 and 1 Exclusive OR'ed with byte 9, bits 0 and 1. Byte 2, bits 0 and 1 are replaced with byte 2, bits 0 and 1 Exclusive OR'ed with byte 9, bits 2 and 3.
字节1、位0和1替换为字节1，位0和1异或替换为字节9、位0和1。字节2、位0和1替换为字节2，位0和1与字节9、位2和3异或。
Byte 3, bits 0 and 1 are replaced with byte 3, bits 0 and 1 Exclusive OR'ed with byte 9, bits 4 and 5. Byte 4, bits 0 and 1 are replaced with byte 4, bits 0 and 1 Exclusive OR'ed with byte 9, bits 6 and 7. Byte 5, bits 0 and 1 are replaced with byte 5, bits 0 and 1 Exclusive OR'ed with byte 10, bits 0 and 1. Byte 6, bits 0 and 1 are replaced with byte 6, bits 0 and 1 Exclusive OR'ed with byte 10, bits 2 and 3. Byte 7, bits 0 and 1 are replaced with byte 7, bits 0 and 1 Exclusive OR'ed with byte 10, bits 4 and 5. Byte 8, bits 0 and 1 are replaced with byte 8, bits 0 and 1 Exclusive OR'ed with byte 10, bits 6 and 7.
字节3、位0和1替换为字节3，位0和1与字节9、位4和5异或。字节4、位0和1替换为字节4，位0和1与字节9、位6和7异或。字节5、位0和1替换为字节5，位0和1与字节10、位0和1异或。字节6、位0和1替换为字节6，位0和1与字节10、位2和3异或。字节7、位0和1替换为字节7，位0和1与字节10、位4和5异或。字节8、位0和1替换为字节8，位0和1与字节10、位6和7异或。
User identifier greater than 10 bytes or less than 1 byte are not the result of this encryption id known as PW_TOKEN in the paper.
大于10字节或小于1字节的用户标识符不是本文中称为PW_令牌的加密id的结果。
5. Increment PWSEQs and store it.
5. 增加PWSEQs并存储它。
Each LU must maintain a pair of sequence numbers for ATTACHs sent and received on each session. Each time an ATTACH is generated, (and password substitutes are in use on the session) the sending sequence number, PWSEQs, is incremented and saved for the next time. Both values are set to zero at BIND time. So the first use of PWSEQs has the value of 1, and increases by one with each use. A new field is added to the ATTACH to carry this sequence number. However, in certain error conditions, it is possible for the sending side to increment the sequence number and the receiver may not increment it. When the sender sends a subsequent ATTACH, the receiver will detect a missing sequence. This is allowed. However the sequence number received must always be larger than the previous one, even if some are missing.
每个LU必须为每个会话上发送和接收的附件维护一对序列号。每次生成附加时（会话中使用密码替代项），发送序列号PWSEQs将递增并保存，以备下次使用。这两个值在绑定时都设置为零。因此，PWSEQs的第一次使用值为1，每次使用增加1。附加中添加了一个新字段以携带此序列号。然而，在某些错误条件下，发送端可能增加序列号，而接收方可能不增加序列号。当发送方发送后续附加时，接收方将检测到丢失的序列。这是允许的。但是，接收到的序列号必须始终大于前一个序列号，即使缺少一些序列号。
The maximum number of consecutive missing sequence numbers allowed is 16. If this is exceeded, the session is unbound with a protocol violation.
允许的最大连续缺失序号数为16。如果超过此值，会话将因协议冲突而解除绑定。
Note: The sequence number must be incremented for every ATTACH sent. However, the sequence number field is only required to be included in the FMH5 if a password substitute is sent (byte 4, bit 3 on).
注意：对于发送的每个附加，序列号必须递增。但是，如果发送了密码替换（字节4，第3位开启），则仅要求在FMH5中包含序列号字段。
6. RDrSEQ = RDr + PWSEQs /* RDr is server seed. */
6. RDrSEQ=RDr+PWSEQs/*RDr是服务器种子*/
The current value of PWSEQs is added to RDr, the random value received from the partner LU on this session, yielding RDrSEQ, essentially a predictably modified value of the random value received from the partner LU at BIND time.
PWSEQs的当前值被添加到RDr中，RDr是在该会话上从伙伴LU接收的随机值，产生RDrSEQ，基本上是绑定时从伙伴LU接收的随机值的可预测修改值。
7. PW_SUB = DES_CBC_mode(PW_TOKEN, /* key */ (RDrSEQ, /* 8 bytes */ RDs, /* 8 bytes */ ID xor RDrSEQ, /* 16 bytes */ PWSEQs, /* 8 bytes */ ) /* data */ )
7. PW_SUB=DES_CBC_模式（PW_令牌，/*密钥*/（RDrSEQ，/*8字节*/RDs，/*8字节*/ID xor RDrSEQ，/*16字节*/PWSEQs，/*8字节*/）/*数据*/）
The PW_TOKEN is used as a key to the DES function to generate a 8 bytes value for the following string of inputs. The DES CBC mode Initialization Vector (IV) used is 8 bytes of '00'X.
PW_标记用作DES函数的键，为以下输入字符串生成8字节的值。使用的DES CBC模式初始化向量（IV）为8字节的'00'X。
RDrSEQ: the random data value received from the partner LU plus the sequence number.
RDrSEQ：从伙伴LU接收的随机数据值加上序列号。
RDs: the random data value sent to the partner LU on BIND for this session.
RDs：此会话绑定时发送给伙伴LU的随机数据值。
A 16 byte value created by:
由以下内容创建的16字节值：
- padding the user identifier with '40'X to a length of 16 bytes.
- 用“40”X填充用户标识符，长度为16字节。
- Exclusive OR the two 8 byte halves of the padded user identifier with the RDrSEQ value.
- 异或两个8字节的填充用户标识符的一半，带有RDrSEQ值。
Note: User ID must first be converted to EBCDIC upper case.
注意：用户ID必须首先转换为EBCDIC大写字母。
PWSEQs: the sequence number.
PWSEQs：序列号。
This is similar to the process used on LU-LU verification as described in the Enhanced LU-LU Bind Security. The resulting enciphered random data is the 'password substitute'.
这类似于增强的LU-LU绑定安全性中描述的LU-LU验证过程。由此产生的加密随机数据是“密码替代”。
1. Generate PW_TOKENa by using characters 1 to 8 of the password and steps 1-4 from the previous section.
1. 使用密码中的字符1到8以及上一节中的步骤1到4生成PW_令牌。
2. Generate PW_TOKENb by using characters 9 and 10 and steps 1-4 from the previous section. In this case Padded_PW from step 1 will be characters 9 and 10 padded to the right with '40'X, for a total length of 8.
2. 使用上一节中的字符9和10以及步骤1-4生成PW_令牌B。在这种情况下，第1步中的填充_PW将是字符9和10，在右侧填充“40”X，总长度为8。
3. PW_TOKEN = PW_TOKENa xor PW_TOKENb
3. PW_令牌=PW_令牌A异或PW_令牌B
4. Now compute PW_SUB by performing steps 5-7 from the previous section.
4. 现在通过执行上一节中的步骤5-7计算PW_SUB。
ID: USER123 Password: ABCDEFG Server seed: '7D4C2319F28004B2'X Client seed: '08BEF662D851F4B1'X PWSEQs: 1 (PWSEQs is a sequence number needed in the 7-step encryption, and it is always one)
ID:USER123密码：ABCDEFG服务器种子：“7D4C2319F28004B2'X客户端种子：'08BEF662D851F4B1'X PWSEQs:1（PWSEQs是七步加密中需要的序列号，始终为一）
Encrypted Password should be : '5A58BD50E4DD9B5F'X
加密密码应为：“5A58BD50E4DD9B5F'X
Device name collision occurs when a Telnet client sends the Telnet server a virtual device name that it wants to use, but that device is already in use on the server. When this occurs, the Telnet server sends a request to the client asking it to try another device name. The environment option negotiation uses the USERVAR name of DEVNAME to communicate the virtual device name. The following shows how the Telnet server will request the Telnet client to send a different DEVNAME when device name collision occurs.
当Telnet客户端向Telnet服务器发送它想要使用的虚拟设备名，但该设备已在服务器上使用时，就会发生设备名冲突。发生这种情况时，Telnet服务器会向客户端发送一个请求，要求它尝试另一个设备名。环境选项协商使用DEVNAME的USERVAR名称来传递虚拟设备名称。下面显示了当发生设备名称冲突时，Telnet服务器将如何请求Telnet客户端发送不同的DEVNAME。
AS/400 Telnet server Enhanced Telnet client
-------------------------- -------------------------
IAC SB NEW-ENVIRON SEND
VAR USERVAR IAC SE -->
AS/400 Telnet server Enhanced Telnet client
-------------------------- -------------------------
IAC SB NEW-ENVIRON SEND
VAR USERVAR IAC SE -->
Server requests all environment variables be sent.
服务器请求发送所有环境变量。
IAC SB NEW-ENVIRON IS USERVAR "DEVNAME" VALUE "MYDEVICE1" USERVAR "xxxxx" VALUE "xxx" ... <-- IAC SE
IAC SB NEW-ENVIRON是用户变量“DEVNAME”值“MYDEVICE1”用户变量“xxxxx”值“xxx”…<--IAC SE
Client sends all environment variables, including DEVNAME. Server tries to select device MYDEVICE1. If the device is already in use, server requests DEVNAME be sent again.
客户端发送所有环境变量，包括DEVNAME。服务器尝试选择设备MYDEVICE1。如果设备已在使用中，服务器将再次发送DEVNAME请求。
IAC SB NEW-ENVIRON SEND USERVAR "DEVNAME" IAC SE -->
IAC SB新环境发送用户变量“DEVNAME”IAC SE-->
Server sends a request for a single environment variable: DEVNAME
服务器发送对单个环境变量的请求：DEVNAME
IAC SB NEW-ENVIRON IS USERVAR <-- "DEVNAME" VALUE "MYDEVICE2" IAC SE
IAC SB NEW-ENVIRON是USERVAR<--“DEVNAME”值“MYDEVICE2”IAC SE
Client sends one environment variable, calculating a new value of MYDEVICE2. If MYDEVICE2 is different from the last request, then server tries to select device MYDEVICE2, else server disconnects client. If MYDEVICE2 is also in use, server will send DEVNAME request again, and keep doing so until it receives a device that is not in use, or the same device name twice in row.
客户端发送一个环境变量，计算MYDEVICE2的新值。如果MYDEVICE2与上次请求不同，则服务器将尝试选择设备MYDEVICE2，否则服务器将断开与客户端的连接。若MYDEVICE2也在使用中，服务器将再次发送DEVNAME请求，并继续发送，直到它收到一个未使用的设备，或者收到两次相同的设备名。
RFC 1572 style USERVAR variables have been defined to allow a compliant Telnet client more control over the Telnet server virtual device on the AS/400. These USERVAR's allow the client Telnet to select a previously created virtual device or auto-create a new virtual device with requested attributes.
已定义RFC 1572样式的USERVAR变量，以允许兼容的Telnet客户端对AS/400上的Telnet服务器虚拟设备进行更多控制。这些USERVAR允许客户端Telnet选择以前创建的虚拟设备，或使用请求的属性自动创建新的虚拟设备。
This makes the enhancements available to any Telnet client that chonoses to support the new negotiations.
这使得任何选择支持新谈判的Telnet客户端都可以使用这些增强功能。
The USERVAR's defined to accomplish this are:
为实现这一点而定义的用户变量包括：
USERVAR VALUE EXAMPLE DESCRIPTION
------------- ---------------- ---------------- -------------------
DEVNAME us-ascii char(x) PRINTER1 Printer device name
IBMIGCFEAT us-ascii char(6) 2424J0 IGC feature (DBCS)
IBMMSGQNAME us-ascii char(x) QSYSOPR *MSGQ name
IBMMSGQLIB us-ascii char(x) QSYS *MSGQ library
IBMFONT us-ascii char(x) 12 Font
IBMFORMFEED us-ascii char(1) C | U | A Formfeed
IBMTRANSFORM us-ascii char(1) 1 | 0 Transform
IBMMFRTYPMDL us-ascii char(x) *IBM42023 Mfg. type and model
IBMPPRSRC1 binary(1) 1-byte hex field Paper source 1
IBMPPRSRC2 binary(1) 1-byte hex field Paper source 2
IBMENVELOPE binary(1) 1-byte hex field Envelope hopper
IBMASCII899 us-ascii char(1) 1 | 0 ASCII 899 support
IBMWSCSTNAME us-ascii char(x) *NONE WSCST name
IBMWSCSTLIB us-ascii char(x) *LIBL WSCST library
USERVAR VALUE EXAMPLE DESCRIPTION
------------- ---------------- ---------------- -------------------
DEVNAME us-ascii char(x) PRINTER1 Printer device name
IBMIGCFEAT us-ascii char(6) 2424J0 IGC feature (DBCS)
IBMMSGQNAME us-ascii char(x) QSYSOPR *MSGQ name
IBMMSGQLIB us-ascii char(x) QSYS *MSGQ library
IBMFONT us-ascii char(x) 12 Font
IBMFORMFEED us-ascii char(1) C | U | A Formfeed
IBMTRANSFORM us-ascii char(1) 1 | 0 Transform
IBMMFRTYPMDL us-ascii char(x) *IBM42023 Mfg. type and model
IBMPPRSRC1 binary(1) 1-byte hex field Paper source 1
IBMPPRSRC2 binary(1) 1-byte hex field Paper source 2
IBMENVELOPE binary(1) 1-byte hex field Envelope hopper
IBMASCII899 us-ascii char(1) 1 | 0 ASCII 899 support
IBMWSCSTNAME us-ascii char(x) *NONE WSCST name
IBMWSCSTLIB us-ascii char(x) *LIBL WSCST library
x - up to a maximum of 10 characters
x-最多10个字符
The "IBM" prefix on the USERVAR's denotes AS/400 specific attributes.
USERVAR上的“IBM”前缀表示为/400特定属性。
The DEVNAME USERVAR is used both for displays and printers. The IBMFONT and IBMASCII899 are used only for SBCS environments.
DEVNAME USERVAR用于显示器和打印机。IBMFONT和IBMASCII899仅用于SBCS环境。
For a description of most of these parameters (drop the "IBM" from the USERVAR) and their permissible values, refer to Chapter 8 in the Communications Configuration Reference [5].
有关大多数参数（从USERVAR中删除“IBM”）及其允许值的描述，请参阅《通信配置参考文献》[5]中的第8章。
The IBMIGCFEAT supports the following variable DBCS language identifiers in position 5 (positions 1-4 must be '2424', position 6 must be '0'):
IBMIGCFEAT在位置5支持以下变量DBCS语言标识符（位置1-4必须为“2424”，位置6必须为“0”）：
'J' = Japanese 'K' = Korean
'C' = Traditional Chinese 'S' = Simplified Chinese
'J' = Japanese 'K' = Korean
'C' = Traditional Chinese 'S' = Simplified Chinese
The IBMTRANSFORM and IBMASCII899 values correspond to:
IBMTRANSFORM和IBMASCII899值对应于：
'1' = Yes '2' = No
“1”=是“2”=否
The IBMFORMFEED values correspond to:
IBMFORMFEED值对应于：
'C' = Continuous 'U' = Cut 'A' = Autocut
'C' = Continuous 'U' = Cut 'A' = Autocut
The IBMPPRSRC1, IBMPPRSRC2 and IBMENVELOPE custom USERVAR's do not map directly to their descriptions in Chapter 8 in the Communications Configuration Reference [5]. To map these, use the index listed here:
IBMPPRSRC1、IBMPPRSRC2和ibmendevelope自定义用户变量没有直接映射到通信配置参考[5]第8章中的描述。要映射这些，请使用此处列出的索引：
IBMPPRSRC1 HEX IBMPPRSRC2 HEX IBMENVELOPE HEX
---------- ----- ---------- ----- ----------- -----
*NONE 'FF'X *NONE 'FF'X *NONE 'FF'X
*MFRTYPMDL '00'X *MFRTYPMDL '00'X *MFRTYPMDL '00'X
*LETTER '01'X *LETTER '01'X *B5 '06'X
*LEGAL '02'X *LEGAL '02'X *MONARCH '09'X
*EXECUTIVE '03'X *EXECUTIVE '03'X *NUMBER9 '0A'X
*A4 '04'X *A4 '04'X *NUMBER10 '0B'X
*A5 '05'X *A5 '05'X *C5 '0C'X
*B5 '06'X *B5 '06'X *DL '0D'X
*CONT80 '07'X *CONT80 '07'X
*CONT132 '08'X *CONT132 '08'X
*A3 '0E'X *A3 '0E'X
*B4 '0F'X *B4 '0F'X
*LEDGER '10'X *LEDGER '10'X
IBMPPRSRC1 HEX IBMPPRSRC2 HEX IBMENVELOPE HEX
---------- ----- ---------- ----- ----------- -----
*NONE 'FF'X *NONE 'FF'X *NONE 'FF'X
*MFRTYPMDL '00'X *MFRTYPMDL '00'X *MFRTYPMDL '00'X
*LETTER '01'X *LETTER '01'X *B5 '06'X
*LEGAL '02'X *LEGAL '02'X *MONARCH '09'X
*EXECUTIVE '03'X *EXECUTIVE '03'X *NUMBER9 '0A'X
*A4 '04'X *A4 '04'X *NUMBER10 '0B'X
*A5 '05'X *A5 '05'X *C5 '0C'X
*B5 '06'X *B5 '06'X *DL '0D'X
*CONT80 '07'X *CONT80 '07'X
*CONT132 '08'X *CONT132 '08'X
*A3 '0E'X *A3 '0E'X
*B4 '0F'X *B4 '0F'X
*LEDGER '10'X *LEDGER '10'X
Note 1: For IBMPPRSRC2, *CONT80 and *CONT132 support starts at V3R7.
注1：对于IBMPPRSRC2，*CONT80和*CONT132支持从V3R7开始。
Note 2: For IBMPPRSRC1 and IBMPPRSRC2, *A3, *B4 and *LEDGER support starts at V3R7.
注2：对于IBMPPRSRC1和IBMPPRSRC2，*A3、*B4和*分类账支持从V3R7开始。
New Telnet options are defined for the printer pass-through mode of operation. To enable printer pass-through mode, both the client and server must agree to at least support the Transmit-Binary, End-Of-Record, and Terminal-Type Telnet options. The following are new terminal types for printers:
为打印机直通操作模式定义了新的Telnet选项。要启用打印机直通模式，客户端和服务器必须同意至少支持传输二进制、记录结束和终端类型Telnet选项。以下是打印机的新终端类型：
TERMINAL-TYPE DESCRIPTION
------------- -------------------
IBM-5553-B01 Double-Byte printer
IBM-3812-1 Single-Byte printer
TERMINAL-TYPE DESCRIPTION
------------- -------------------
IBM-5553-B01 Double-Byte printer
IBM-3812-1 Single-Byte printer
Specific characteristics of the IBM-5553-B01 or IBM-3812-1 printers are specified through the USERVAR IBMMFRTYPMDL, which specifies the manufacturer type and model.
IBM-5553-B01或IBM-3812-1打印机的特定特性通过USERVAR IBMMFRTYPMDL指定，该文件指定了制造商类型和型号。
An example of a typical negotiation process to establish printer pass-through mode of operation is shown below. In this example, the server initiates the negotiation by sending the DO TERMINAL-TYPE request.
建立打印机直通操作模式的典型协商过程示例如下所示。在本例中，服务器通过发送DO终端类型请求来启动协商。
For DBCS environments, if IBMTRANSFORM is set to 1 (use Host Print Transform), then the virtual device created is 3812, not 5553. Therefore, IBM-3812-1 should be negotiated for TERMINAL-TYPE, and not IBM-5553-B01.
对于DBCS环境，如果IBMTRANSFORM设置为1（使用主机打印转换），则创建的虚拟设备为3812，而不是5553。因此，应针对终端类型协商IBM-3812-1，而不是IBM-5553-B01。
AS/400 Telnet server Enhanced Telnet client
-------------------------- --------------------------
IAC DO NEW-ENVIRON -->
<-- IAC WILL NEW-ENVIRON
IAC SB NEW-ENVIRON SEND
VAR USERVAR IAC SE -->
IAC SB NEW-ENVIRON IS
USERVAR "DEVNAME" VALUE "PCPRINTER"
USERVAR "IBMMSGQNAME" VALUE "QSYSOPR"
USERVAR "IBMMSGQLIB" VALUE "*LIBL"
USERVAR "IBMTRANSFORM" VALUE "0"
USERVAR "IBMFONT" VALUE "12"
USERVAR "IBMFORMFEED" VALUE "C"
USERVAR "IBMPPRSRC1" VALUE ESC '01'X
USERVAR "IBMPPRSRC2" VALUE '04'X
USERVAR "IBMENVELOPE" VALUE IAC 'FF'X
<-- IAC SE
IAC DO TERMINAL-TYPE -->
<-- IAC WILL TERMINAL-TYPE
IAC SB TERMINAL-TYPE SEND
IAC SE -->
AS/400 Telnet server Enhanced Telnet client
-------------------------- --------------------------
IAC DO NEW-ENVIRON -->
<-- IAC WILL NEW-ENVIRON
IAC SB NEW-ENVIRON SEND
VAR USERVAR IAC SE -->
IAC SB NEW-ENVIRON IS
USERVAR "DEVNAME" VALUE "PCPRINTER"
USERVAR "IBMMSGQNAME" VALUE "QSYSOPR"
USERVAR "IBMMSGQLIB" VALUE "*LIBL"
USERVAR "IBMTRANSFORM" VALUE "0"
USERVAR "IBMFONT" VALUE "12"
USERVAR "IBMFORMFEED" VALUE "C"
USERVAR "IBMPPRSRC1" VALUE ESC '01'X
USERVAR "IBMPPRSRC2" VALUE '04'X
USERVAR "IBMENVELOPE" VALUE IAC 'FF'X
<-- IAC SE
IAC DO TERMINAL-TYPE -->
<-- IAC WILL TERMINAL-TYPE
IAC SB TERMINAL-TYPE SEND
IAC SE -->
IAC SB TERMINAL-TYPE IS IBM-3812-1 <-- IAC SE IAC DO BINARY --> <-- IAC WILL BINARY IAC DO EOR --> <-- IAC WILL EOR
IAC SB终端类型为IBM-3812-1<--IAC SE IAC DO BINARY--><--IAC WILL BINARY IAC DO EOR--><--IAC WILL EOR
Some points about the above example. The IBMPPRSRC1 value requires escaping the value using ESC according to RFC 1572 [13]. The IBMPPRSRC2 does not require an ESC character since '04'X has no conflict with RFC 1572 options. Finally, to send 'FF'X for the IBMENVELOPE value, escape the 'FF'X value by using another 'FF'X (called "doubling"), so as not to have the value interpreted as a Telnet character per RFC 854 [8].
关于上述示例的一些要点。根据RFC 1572[13]，IBMPPRSRC1值需要使用ESC转义该值。IBMPPRSRC2不需要ESC字符，因为'04'X与RFC 1572选项没有冲突。最后，要为ibmendevelope值发送'FF'X，请使用另一个'FF'X（称为“加倍”）对'FF'X值进行转义，以免根据RFC 854[8]将该值解释为Telnet字符。
Actual bytes transmitted in the above example are shown in hex below.
在上述示例中传输的实际字节以十六进制表示。
AS/400 Telnet server Enhanced Telnet client
-------------------------- --------------------------
FF FD 27 -->
<-- FF FB 27
FF FA 27 01 00 03 FF F0 -->
FF FA 27 00 03 44 45 56
4E 41 4D 45 01 50 43 50
52 49 4E 54 45 52 03 49
42 4D 4D 53 47 51 4E 41
4D 45 01 51 53 59 53 4F
50 52 03 49 42 4D 4D 53
47 51 4C 49 42 01 2A 4C
49 42 4C 03 49 42 4D 54
52 41 4E 53 46 4F 52 4D
01 30 03 49 42 4D 46 4F
4E 54 01 31 32 03 49 42
4D 46 4F 52 4D 46 45 45
44 01 43 03 49 42 4D 50
50 52 53 52 43 31 01 02
01 03 49 42 4D 50 50 52
53 52 43 32 01 04 03 49
42 4D 45 4E 56 45 4C 4F
<-- 50 45 01 FF FF FF F0
FF FD 18 -->
<-- FF FB 18
FF FA 18 01 FF F0 -->
FF FA 18 00 49 42 4D 2D
<-- 33 38 31 32 2D 31 FF F0
FF FD 00 -->
<-- FF FB 00
FF FD 19 -->
AS/400 Telnet server Enhanced Telnet client
-------------------------- --------------------------
FF FD 27 -->
<-- FF FB 27
FF FA 27 01 00 03 FF F0 -->
FF FA 27 00 03 44 45 56
4E 41 4D 45 01 50 43 50
52 49 4E 54 45 52 03 49
42 4D 4D 53 47 51 4E 41
4D 45 01 51 53 59 53 4F
50 52 03 49 42 4D 4D 53
47 51 4C 49 42 01 2A 4C
49 42 4C 03 49 42 4D 54
52 41 4E 53 46 4F 52 4D
01 30 03 49 42 4D 46 4F
4E 54 01 31 32 03 49 42
4D 46 4F 52 4D 46 45 45
44 01 43 03 49 42 4D 50
50 52 53 52 43 31 01 02
01 03 49 42 4D 50 50 52
53 52 43 32 01 04 03 49
42 4D 45 4E 56 45 4C 4F
<-- 50 45 01 FF FF FF F0
FF FD 18 -->
<-- FF FB 18
FF FA 18 01 FF F0 -->
FF FA 18 00 49 42 4D 2D
<-- 33 38 31 32 2D 31 FF F0
FF FD 00 -->
<-- FF FB 00
FF FD 19 -->
FF FB 19
FF FB 19
Once Telnet negotiation for a 5250 pass-through mode is completed, the 5250 Telnet server will initiate a virtual printer power-on sequence on behalf of the Telnet client. The Telnet server will supply a Startup Response Record to the Telnet client with the status of the printer power-on sequence, indicating success or failure of the virtual printer power-on sequence.
完成5250直通模式的Telnet协商后，5250 Telnet服务器将代表Telnet客户端启动虚拟打印机开机序列。Telnet服务器将向Telnet客户端提供一个启动响应记录，其中包含打印机开机顺序的状态，指示虚拟打印机开机顺序的成功或失败。
This section shows an example of two Startup Response Records. The source device is a type 3812 model 01 printer with name "PCPRINTER" on the target system "TARGET".
本节显示了两个启动响应记录的示例。源设备是目标系统“target”上名为“PCPRINTER”的3812型01打印机。
Figure 1 shows an example of a successful response; Figure 2 shows an example of an error response.
图1显示了一个成功响应的示例；图2显示了一个错误响应的示例。
The response record in Figure 1 was sent by an AS/400 at Release V4R2. It is an example of the target sending back a successful Startup Response Record.
图1中的响应记录是由版本V4R2上的AS/400发送的。这是目标发送回成功启动响应记录的示例。
+------------------------------------------------------------------+
| +----- Pass-Through header |
| | +--- Response data |
| | | +---- Start diagnostic information|
| | | | |
| +----------++----------++--------------------------------------- |
| | || || |
| 004912A090000560060020C0003D0000C9F9F0F2E3C1D9C7C5E34040D7C3D7D9 |
| | | T A R G E T P C P R |
| +------+ |
| Response Code (I902) |
| |
| ---------------------------------------------------------------- |
| |
| C9D5E3C5D9400000000000000000000000000000000000000000000000000000 |
| I N T E R |
| |
| +------- End of diagnostic information |
| | |
| -----------------+ |
| | |
| 000000000000000000 |
+------------------------------------------------------------------+
Figure 1. Example of a success response record.
+------------------------------------------------------------------+
| +----- Pass-Through header |
| | +--- Response data |
| | | +---- Start diagnostic information|
| | | | |
| +----------++----------++--------------------------------------- |
| | || || |
| 004912A090000560060020C0003D0000C9F9F0F2E3C1D9C7C5E34040D7C3D7D9 |
| | | T A R G E T P C P R |
| +------+ |
| Response Code (I902) |
| |
| ---------------------------------------------------------------- |
| |
| C9D5E3C5D9400000000000000000000000000000000000000000000000000000 |
| I N T E R |
| |
| +------- End of diagnostic information |
| | |
| -----------------+ |
| | |
| 000000000000000000 |
+------------------------------------------------------------------+
Figure 1. Example of a success response record.
- '0049'X = Length pass-through data, including this length field - '12A0'X = GDS LU6.2 header - '90000560060020C0003D0000'X = Fixed value fields - 'C9F9F0F2'X = Response Code (I902) - 'E3C1D9C7C5E34040'X = System Name (TARGET) - 'D7C3D7D9C9D5E3C5D940'X = Object Name (PCPRINTER)
- “0049”X=长度传递数据，包括此长度字段-“12A0”X=GDS LU6.2标头-“90000560020C0003D0000”X=固定值字段-“C9F9F0F2”X=响应代码（I902）-“E3C1D9C7C5E34040”X=系统名称（目标）-“D7C3D7D9C9D5E3C5D940”X=对象名称（PCPRINTER）
The response record in Figure 2 is one that reports an error. The virtual device named "PCPRINTER", is not available on the target system "TARGET", because the device is not available. You would normally see this error if the printer was already assigned to another Telnet session.
图2中的响应记录报告了一个错误。名为“PCPRINTER”的虚拟设备在目标系统“target”上不可用，因为该设备不可用。如果打印机已分配给另一个Telnet会话，则通常会看到此错误。
+------------------------------------------------------------------+
| +----- Pass-Through header |
| | +--- Response data |
| | | +---- Start diagnostic information|
| | | | |
| +----------++----------++--------------------------------------- |
| | || || |
| 004912A09000056006008200003D0000F8F9F0F2E3C1D9C7C5E34040D7C3D7D9 |
| | | T A R G E T P C P R |
| +------+ |
| Response Code (8902) |
| |
| ---------------------------------------------------------------- |
| |
| C9D5E3C5D9400000000000000000000000000000000000000000000000000000 |
| I N T E R |
| |
| +------- End of diagnostic information |
| | |
| -----------------+ |
| | |
| 000000000000000000 |
+------------------------------------------------------------------+
Figure 2. Example of an error response record.
+------------------------------------------------------------------+
| +----- Pass-Through header |
| | +--- Response data |
| | | +---- Start diagnostic information|
| | | | |
| +----------++----------++--------------------------------------- |
| | || || |
| 004912A09000056006008200003D0000F8F9F0F2E3C1D9C7C5E34040D7C3D7D9 |
| | | T A R G E T P C P R |
| +------+ |
| Response Code (8902) |
| |
| ---------------------------------------------------------------- |
| |
| C9D5E3C5D9400000000000000000000000000000000000000000000000000000 |
| I N T E R |
| |
| +------- End of diagnostic information |
| | |
| -----------------+ |
| | |
| 000000000000000000 |
+------------------------------------------------------------------+
Figure 2. Example of an error response record.
- '0049'X = Length pass-through data, including this length field - '12A0'X = GDS LU6.2 header - '90000560060020C0003D0000'X = Fixed value fields - 'F8F9F0F2'X = Response Code (8902) - 'E3C1D9C7C5E34040'X = System Name (TARGET) - 'D7C3D7D9C9D5E3C5D940'X = Object Name (PCPRINTER)
- “0049”X=长度传递数据，包括此长度字段-“12A0”X=GDS LU6.2标头-“90000560020C0003D0000”X=固定值字段-“F8F9F0F2”X=响应代码（8902）-“E3C1D9C7C5E34040”X=系统名称（目标）-“D7C3D7D9C9D5E3C5D940”X=对象名称（PCPRINTER）
The Start-Up Response Record success response codes:
启动响应记录成功响应代码：
CODE DESCRIPTION
---- ------------------------------------------------------
I901 Virtual device has less function than source device
I902 Session successfully started
I906 Automatic sign-on requested, but not allowed.
Session still allowed; a sign-on screen will be
coming.
CODE DESCRIPTION
---- ------------------------------------------------------
I901 Virtual device has less function than source device
I902 Session successfully started
I906 Automatic sign-on requested, but not allowed.
Session still allowed; a sign-on screen will be
coming.
The Start-Up Response Record error response codes:
启动响应记录错误响应代码：
CODE DESCRIPTION
---- ------------------------------------------------------
2702 Device description not found.
2703 Controller description not found.
2777 Damaged device description.
8901 Device not varied on.
8902 Device not available.
8903 Device not valid for session.
8906 Session initiation failed.
8907 Session failure.
8910 Controller not valid for session.
8916 No matching device found.
8917 Not authorized to object.
8918 Job canceled.
8920 Object partially damaged.
8921 Communications error.
8922 Negative response received.
8923 Start-up record built incorrectly.
8925 Creation of device failed.
8928 Change of device failed.
8929 Vary on or vary off failed.
8930 Message queue does not exist.
8934 Start-up for S/36 WSF received.
8935 Session rejected.
8936 Security failure on session attempt.
8937 Automatic sign-on rejected.
8940 Automatic configuration failed or not allowed.
I904 Source system at incompatible release.
CODE DESCRIPTION
---- ------------------------------------------------------
2702 Device description not found.
2703 Controller description not found.
2777 Damaged device description.
8901 Device not varied on.
8902 Device not available.
8903 Device not valid for session.
8906 Session initiation failed.
8907 Session failure.
8910 Controller not valid for session.
8916 No matching device found.
8917 Not authorized to object.
8918 Job canceled.
8920 Object partially damaged.
8921 Communications error.
8922 Negative response received.
8923 Start-up record built incorrectly.
8925 Creation of device failed.
8928 Change of device failed.
8929 Vary on or vary off failed.
8930 Message queue does not exist.
8934 Start-up for S/36 WSF received.
8935 Session rejected.
8936 Security failure on session attempt.
8937 Automatic sign-on rejected.
8940 Automatic configuration failed or not allowed.
I904 Source system at incompatible release.
The information in this section applies to the passthrough session after the receipt of startup confirmation records is complete.
本节中的信息适用于接收启动确认记录完成后的直通会话。
Following is the printer header interface used by Telnet.
以下是Telnet使用的打印机标题界面。
+------------------------------------------------------------------+
| +-- Length of structure (LLLL) |
| | |
| | +-- GDS identifier |
| | | |
| | | +-- Data flow record |
| | | | |
| | | | +-- Length of pass-through specific header (LL) |
| | | | | |
| | | | | +-- Flags |
| | | | | | |
| | | | | | +-- Printer operation code |
| | | | | | | |
| | | | | | | +-- Diagnostic field - zero pad to|
| | | | | | | | LL specified |
| | | | | | | | |
| | | | | | | | +-- Printer data |
| | | | | | | | | |
| +--+ +--+ +--+ ++ +--+ ++ +----------+ +----------------+ |
| | | | | | | || | | || | | | | |
| xxxx 12A0 xxxx xx xxxx xx xxxxxxxxxxxx ... print data ... |
| |
+------------------------------------------------------------------+
Figure 3. Layout of the printer pass-through header
+------------------------------------------------------------------+
| +-- Length of structure (LLLL) |
| | |
| | +-- GDS identifier |
| | | |
| | | +-- Data flow record |
| | | | |
| | | | +-- Length of pass-through specific header (LL) |
| | | | | |
| | | | | +-- Flags |
| | | | | | |
| | | | | | +-- Printer operation code |
| | | | | | | |
| | | | | | | +-- Diagnostic field - zero pad to|
| | | | | | | | LL specified |
| | | | | | | | |
| | | | | | | | +-- Printer data |
| | | | | | | | | |
| +--+ +--+ +--+ ++ +--+ ++ +----------+ +----------------+ |
| | | | | | | || | | || | | | | |
| xxxx 12A0 xxxx xx xxxx xx xxxxxxxxxxxx ... print data ... |
| |
+------------------------------------------------------------------+
Figure 3. Layout of the printer pass-through header
BYTES 0-1: Length of structure including this field (LLLL)
字节0-1：包含此字段的结构长度（LLLL）
BYTES 2-3: GDS Identifier ('12A0'X)
字节2-3:GDS标识符（'12A0'X）
BYTE 4-5: Data flow record
字节4-5：数据流记录
This field contains flags that describe what type of data pass-through should expect to find following this header. Generally, bits 0-2 in the first byte are mutually exclusive (that is, if one of them is set to ' 1'B, the rest will be set to '0'B.) The bits, and their meanings follow.
此字段包含标志，这些标志描述了在该标头之后应该找到的数据传递类型。通常，第一个字节中的位0-2是互斥的（即，如果其中一个被设置为“1”B，其余的将被设置为“0”B）。这些位及其含义如下。
BIT DESCRIPTION
位描述
0 Start-Up confirmation 1 Termination record 2 Start-Up Record 3 Diagnostic information included 4 - 5 Reserved 6 Reserved 7 Printer record 8 - 13 Reserved 14 Client-originated (inbound) printer record 15 Server-originated (outbound) printer record
0启动确认1终止记录2启动记录3诊断信息包括4-5保留6保留7打印机记录8-13保留14客户端起源（入站）打印机记录15服务器起源（出站）打印机记录
BYTE 6: Length printer pass-through header including this field (LL)
字节6：包含此字段的打印机通过页眉长度（LL）
BYTES 7-8: Flags
字节7-8：标志
BYTE 7 BITS: xxxx x111 --> Reserved
xxxx 1xxx --> Last of chain
xxx1 xxxx --> First of chain
xx1x xxxx --> Printer now ready
x1xx xxxx --> Intervention Required
1xxx xxxx --> Error Indicator
BYTE 7 BITS: xxxx x111 --> Reserved
xxxx 1xxx --> Last of chain
xxx1 xxxx --> First of chain
xx1x xxxx --> Printer now ready
x1xx xxxx --> Intervention Required
1xxx xxxx --> Error Indicator
BYTE 8 BITS: xxxx xxxx --> Reserved
BYTE 8 BITS: xxxx xxxx --> Reserved
BYTE 9: Printer operation code
字节9：打印机操作代码
'01'X Print/Print complete '02'X Clear Print Buffers
'01'X打印/打印完成'02'X清除打印缓冲区
BYTE 10-LL: Diagnostic information (1)
字节10-LL：诊断信息（1）
If BYTE 7 = xx1x xxxx then bytes 10-LL may contain: Printer ready C9 00 00 00 02
如果字节7=xx1x xxxx，则字节10-LL可能包含：打印机就绪C9 00 02
If BYTE 7 = x1xx xxxx then bytes 10-LL may contain: (2) Command/parameter not valid C9 00 03 02 2x Print check C9 00 03 02 3x Forms check C9 00 03 02 4x Normal periodic condition C9 00 03 02 5x Data stream error C9 00 03 02 6x Machine/print/ribbon check C9 00 03 02 8x
如果字节7=x1xx xxxx，则字节10-LL可能包含：（2）命令/参数无效C9 00 03 02 2x打印检查C9 00 03 02 3x表格检查C9 00 03 02 4x正常周期条件C9 00 03 02 5x数据流错误C9 00 03 02 6x机器/打印/色带检查C9 00 03 02 8x
If BYTE 7 = 1xxx xxxx then bytes 10-LL may contain: (3) Cancel 08 11 02 00 Invalid print parameter 08 11 02 29
如果字节7=1xxx xxxx，则字节10-LL可能包含：（3）取消08 11 02 00无效打印参数08 11 02 29
Invalid print command 08 11 02 28
无效的打印命令08 11 02 28
Diagnostic information notes:
诊断信息注释：
1. LL is the length of the structure defined in Byte 6. If no additional data is present, the remainder of the structure must be padded with zeroes.
1. LL是字节6中定义的结构的长度。如果没有其他数据，则必须用零填充结构的其余部分。
2. These are printer SIGNAL commands. Further information on these commands may be obtained from the 5494 Remote Control Unit Functions Reference guide [2]. Refer to your AS/400 printer documentation for more specific information on these data stream exceptions. Some 3812 and 5553 errors that may be seen:
2. 这些是打印机信号命令。有关这些命令的更多信息，请参阅5494《远程控制单元功能参考指南》[2]。有关这些数据流异常的更多具体信息，请参阅AS/400打印机文档。可能会看到一些3812和5553错误：
Machine check C9 00 03 02 11 Graphics check C9 00 03 02 26 Print check C9 00 03 02 31 Form jam C9 00 03 02 41 Paper jam C9 00 03 02 47 End of forms C9 00 03 02 50 Printer not ready C9 00 03 02 51 Data stream - class 1 C9 00 03 02 66 loss of text Data stream - class 2 C9 00 03 02 67 text appearance Data stream - class 3 C9 00 03 02 68 multibyte control error Data stream - class 4 C9 00 03 02 69 multibyte control parm Cover unexpectedly open C9 00 03 02 81 Machine check C9 00 03 02 86 Machine check C9 00 03 02 87 Ribbon check C9 00 03 02 88
机器检查C9 00 03 02 11图形检查C9 00 03 02 26打印检查C9 00 03 02 31表格堵塞C9 00 03 02 41卡纸C9 00 03 02 47表格结束C9 00 03 02 50打印机未就绪C9 00 03 02 51数据流-类别1 C9 00 03 02 66文本数据流丢失-类别2 C9 00 03 02 67文本外观数据流-类别3 C9 00 02 68多字节控制错误数据流-4级C9 00 03 02 69多字节控制参数盖意外打开C9 00 03 02 81机器检查C9 00 03 02 86机器检查C9 00 03 02 87功能区检查C9 00 03 02 88
3. These are printer negative responses. Further information on these commands may be obtained from the 5494 Remote Control Unit Functions Reference guide [2].
3. 这些都是否定的回答。有关这些命令的更多信息，请参阅5494《远程控制单元功能参考指南》[2]。
The print data will start in byte LL+1.
打印数据将从字节LL+1开始。
Figure 4 shows the server sending the client data with a print record. This is normally seen following receipt of a Success Response Record, such as the example in Figure 1.
图4显示了服务器发送带有打印记录的客户端数据。这通常在收到成功响应记录后出现，如图1中的示例。
+--------------------------------------------------------------------+
| +-- Length of structure (LLLL) |
| | +-- GDS identifier |
| | | +-- Data flow record |
| | | | +-- Length of pass-through specific header (LL) |
| | | | | +-- Flags |
| | | | | | +-- Printer operation code |
| | | | | | | +-- Zero pad to LL specified (0A) |
| | | | | | | | +-- Printer data |
| | | | | | | | | |
| +--+ +--+ +--+ ++ +--+ ++ +----------+ +---------------------------|
| | | | | | | || | | || | | | |
| 0085 12A0 0101 0A 1800 01 000000000000 34C4012BD20345FF2BD2044C0002|
| |
| ------------------------------------------------------------ |
| |
| 2BD2040D00002BD20A8501010201030204022BD20309022BD2061100014A |
| |
| ------------------------------------------------------------ |
| |
| 402BD20601010000012BD306F60000FFFF2BD20A48000001000000010100 |
| |
| ------------------------------------------------------------ |
| |
| 2BD10705000B0090012BD2044900F02BD206404A403DE02BD2041500F034 |
| |
| end of printer data |
| -------------------------+ |
| | |
| C4012BD10381FF002BC8034001 |
+--------------------------------------------------------------------+
Figure 4. Server sending client data with a print record
+--------------------------------------------------------------------+
| +-- Length of structure (LLLL) |
| | +-- GDS identifier |
| | | +-- Data flow record |
| | | | +-- Length of pass-through specific header (LL) |
| | | | | +-- Flags |
| | | | | | +-- Printer operation code |
| | | | | | | +-- Zero pad to LL specified (0A) |
| | | | | | | | +-- Printer data |
| | | | | | | | | |
| +--+ +--+ +--+ ++ +--+ ++ +----------+ +---------------------------|
| | | | | | | || | | || | | | |
| 0085 12A0 0101 0A 1800 01 000000000000 34C4012BD20345FF2BD2044C0002|
| |
| ------------------------------------------------------------ |
| |
| 2BD2040D00002BD20A8501010201030204022BD20309022BD2061100014A |
| |
| ------------------------------------------------------------ |
| |
| 402BD20601010000012BD306F60000FFFF2BD20A48000001000000010100 |
| |
| ------------------------------------------------------------ |
| |
| 2BD10705000B0090012BD2044900F02BD206404A403DE02BD2041500F034 |
| |
| end of printer data |
| -------------------------+ |
| | |
| C4012BD10381FF002BC8034001 |
+--------------------------------------------------------------------+
Figure 4. Server sending client data with a print record
- '0085'X = Logical record length, including this byte (LLLL)
- '12A0'X = GDS LU6.2 header
- '0101'X = Data flow record (server to client)
- '0A'X = Length of pass-through specific header (LL)
- '1800'X = First of chain / Last of chain indicators
- '01'X = Print
- '000000000000'X = Zero pad header to LL specified
- '34C401'X = First piece of data for spooled data
- Remainder is printer data/commands/orders
- '0085'X = Logical record length, including this byte (LLLL)
- '12A0'X = GDS LU6.2 header
- '0101'X = Data flow record (server to client)
- '0A'X = Length of pass-through specific header (LL)
- '1800'X = First of chain / Last of chain indicators
- '01'X = Print
- '000000000000'X = Zero pad header to LL specified
- '34C401'X = First piece of data for spooled data
- Remainder is printer data/commands/orders
Figure 5 shows the client sending the server a print complete record. This would normally follow receipt of a print record, such as the example in Figure 4. This indicates successful completion of a print request.
图5显示了向服务器发送打印完整记录的客户端。这通常是在收到打印记录之后进行的，如图4中的示例。这表示打印请求已成功完成。
+-------------------------------------------------------------------+
| +-- Length of structure (LLLL) |
| | +-- GDS identifier |
| | | +-- Data flow record |
| | | | +-- Length of pass-through specific header (LL) |
| | | | | +-- Flags |
| | | | | | +-- Printer operation code |
| | | | | | | |
| +--+ +--+ +--+ ++ +--+ ++ |
| | | | | | | || | | || |
| 000A 12A0 0102 04 0000 01 |
+-------------------------------------------------------------------+
Figure 5. Client sending server a print complete record
+-------------------------------------------------------------------+
| +-- Length of structure (LLLL) |
| | +-- GDS identifier |
| | | +-- Data flow record |
| | | | +-- Length of pass-through specific header (LL) |
| | | | | +-- Flags |
| | | | | | +-- Printer operation code |
| | | | | | | |
| +--+ +--+ +--+ ++ +--+ ++ |
| | | | | | | || | | || |
| 000A 12A0 0102 04 0000 01 |
+-------------------------------------------------------------------+
Figure 5. Client sending server a print complete record
- '000A'X = Logical record length, including this byte (LLLL) - '12A0'X = GDS LU6.2 header - '0102'X = Data flow response record (client to server) - '04'X = Length of pass-through specific header (LL) - '0000'X = Good Response - '01'X = Print Complete
- '000A'X=逻辑记录长度，包括此字节（LLLL）-'12A0'X=GDS LU6.2标头-'0102'X=数据流响应记录（客户端到服务器）-'04'X=通过特定标头的长度（LL）-'0000'X=良好响应-'01'X=打印完成
Figure 6 shows the server sending the client a null print record. The null print record is the last print command the server sends to the client for a print job, and indicates to the printer there is no more data. The null data byte '00'X is optional, and in some cases may be omitted (in particular, this scenario occurs in DBCS print streams).
图6显示了服务器向客户端发送空打印记录。null print record是服务器为打印作业向客户端发送的最后一个打印命令，它向打印机指示没有更多数据。空数据字节'00'X是可选的，在某些情况下可以省略（特别是，这种情况发生在DBCS打印流中）。
This example would normally follow any number of print records, such as the example in Figure 4. This indicates successful completion of a print job. The client normally responds to this null print record with another print complete record, such as in Figure 5.
此示例通常会遵循任意数量的打印记录，如图4中的示例。这表示打印作业已成功完成。客户机通常使用另一个完整的打印记录来响应这个空打印记录，如图5所示。
+------------------------------------------------------------------+
| +-- Length of structure (LLLL) |
| | +-- GDS identifier |
| | | +-- Data flow record |
| | | | +-- Length of pass-through specific header (LL) |
| | | | | +-- Flags |
| | | | | | +-- Printer operation code |
| | | | | | | +-- Zero pad to LL specified (0A) |
| | | | | | | | +-- Printer data |
| | | | | | | | | |
| +--+ +--+ +--+ ++ +--+ ++ +----------+ ++ |
| | | | | | | || | | || | | || |
| 0011 12A0 0101 0A 0800 01 000000000000 00 |
+------------------------------------------------------------------+
Figure 6. Server sending client a null print record
+------------------------------------------------------------------+
| +-- Length of structure (LLLL) |
| | +-- GDS identifier |
| | | +-- Data flow record |
| | | | +-- Length of pass-through specific header (LL) |
| | | | | +-- Flags |
| | | | | | +-- Printer operation code |
| | | | | | | +-- Zero pad to LL specified (0A) |
| | | | | | | | +-- Printer data |
| | | | | | | | | |
| +--+ +--+ +--+ ++ +--+ ++ +----------+ ++ |
| | | | | | | || | | || | | || |
| 0011 12A0 0101 0A 0800 01 000000000000 00 |
+------------------------------------------------------------------+
Figure 6. Server sending client a null print record
- '0011'X = Logical record length, including this byte - '12A0'X = GDS LU6.2 header - '0101'X = Data flow record - '0A'X = Length of pass-through specific header (LL) - '0800'X = Last of Chain - '01'X = Print - '000000000000'X = Zero pad header to LL specified - '00'X = Null data byte
- '0011'X=逻辑记录长度，包括此字节-'12A0'X=GDS LU6.2标头-'0101'X=数据流记录-'0A'X=通过特定标头的长度（LL）-'0800'X=链的最后一个-'01'X=打印-'000000000000'X=零填充标头到LL指定-'00'X=空数据字节
The next example shows a full print exchange between a Telnet client and server for a 526 byte spooled file. Selective translation of the hexadecimal streams into 1) Telnet negotiations and 2) ASCII/EBCDIC characters are done to aid readability. Telnet negotiations are delimited by '(' and ')' parenthesis characters; ASCII/EBCDIC conversions are bracketed by '|' vertical bar characters.
下一个示例显示了Telnet客户端和服务器之间对526字节假脱机文件的完整打印交换。有选择地将十六进制数据流翻译成1）Telnet协商和2）ASCII/EBCDIC字符，以提高可读性。Telnet协商由“（”和“）”括号字符分隔；ASCII/EBCDIC转换用“|”竖线字符括起来。
AS/400 Telnet server Enhanced Telnet client
------------------------------- ---------------------------------
FFFD27 -->
AS/400 Telnet server Enhanced Telnet client
------------------------------- ---------------------------------
FFFD27 -->
(IAC DO NEW-ENVIRON) <-- FFFB27
（IAC DO NEW-ENVIRON）<--FFFB27
(IAC WILL NEW-ENVIRON)
（IAC将与新环境合作）
FFFD18FFFA270103 49424D5253454544 7EA5DFDDFD300404 0003FFF0 -->
FFFD18FFFA270103 49424D5253454544 7EA5DFDDFD300404 0003FFF0-->
(IAC DO TERMINAL-TYPE IAC SB NEW-ENVIRON SEND USERVAR
（IAC DO终端类型IAC SB新环境发送用户变量
IBMRSEED xxxxxxxx VAR USERVAR IAC SE)
IBMRSEED xxxxxxxx VAR USERVAR IAC SE）
<-- FFFB18
<--FFFB18
(IAC WILL TERMINAL-TYPE)
（IAC将为终端类型）
FFFA1801FFF0 -->
FFFA1801FF0-->
(IAC SB TERMINAL-TYPE SEND IAC SE)
（IAC SB终端类型发送IAC SE）
FFFA27000349424D 52534545447EA5DF DDFD300404000344 45564E414D450144 554D4D5950525403 49424D4D5347514E 414D450151535953 4F50520349424D4D 5347514C4942012A 4C49424C0349424D 464F4E5401313103 49424D5452414E53 464F524D01310349 424D4D4652545950 4D444C012A485049 490349424D505052 5352433101020103 49424D5050525352 433201040349424D 454E56454C4F5045 01FFFF0349424D41 5343494938393901 <-- 30FFF0
FFFA27000349424D 52534545447EA5DF DDFD3004040003445564E414D450144 554D595052503 49424D5347514E 414D4501515353 4F50520349424D 5347514C4942012A 4C49424C0349424D464E5401313103 49424D5452414E53 464D45454D01310349 424D464D4552545950 4D444C012A 485049 49349424D50522 5352433101020103 49424D5054454501FFFF0349424D41 5343494938393901<--30FFF0
(IAC SB NEW-ENVIRON IS USERVAR IBMRSEED xxxxxxxx VAR USERVAR DEVNAME VALUE DUMMYPRT USERVAR IBMMSGQNAME VALUE QSYSOPR USERVAR IBMMSGQLIB VALUE *LIBL USERVAR IBMFONT VALUE 11 USERVAR IBMTRANSFORM VALUE 1 USERVAR IBMMFRTYPMDL VALUE *HPII USERVAR IBMPPRSRC1 VALUE ESC '01'X USERVAR IBMPPRSRC2 VALUE '04'X USERVAR IBMENVELOPE VALUE IAC USERVAR IBMASCII899 VALUE 0 IAC SE)
（IAC SB NEW-ENVIRON是USERVAR IBMRSEED xxxxxxxx VAR USERVAR DEVNAME值DUMMYPRT USERVAR IBMMSGQNAME值QSYSOPR USERVAR IBMMSGQLIB值*LIBL USERVAR IBMFONT值11 USERVAR ibm转换值1 USERVAR IBMMFRTYPMDL值*HPII USERVAR IBMPPRSRC1值ESC'01'X USERVAR IBMPPRSRC2值'04'X USERVAR ibmendevelope值IAC USERVAR ibmasci899值（0 IAC SE）
<-- FFFA180049424D2D 333831322D31FFF0
<--FFFA180049424D2D 333831322D31FFF0
(IAC SB TERMINAL-TYPE IS IBM-3812-1 IAC SE) FFFD19 -->
（IAC SB终端类型为IBM-3812-1 IAC SE）FFFD19-->
(IAC DO EOR) <-- FFFB19
（IAC DO EOR）<--FFFB19
(IAC WILL EOR)
（IAC将提高采收率）
FFFB19 -->
FFFB19-->
(IAC WILL EOR) <-- FFFD19
（IAC将提高采收率）<--FFFD19
(IAC DO EOR) FFFD00 -->
（IAC DO EOR）FFFD00-->
(IAC DO BINARY) <-- FFFB00
（IAC DO二进制）<--FFFB00
(IAC WILL BINARY) FFFB00 -->
（IAC将二进制）FFFB00-->
(IAC WILL BINARY) <-- FFFD00
（IAC将为二进制）<--FFFD00
(IAC DO BINARY)
（IAC DO二进制文件）
004912A090000560 060020C0003D0000 | - { |
C9F9F0F2C5D3C3D9 E3D7F0F6C4E4D4D4 |I902ELCRTP06DUMM| (EBCDIC)
E8D7D9E340400000 0000000000000000 |YPRT |
0000000000000000 0000000000000000 | |
0000000000000000 00FFEF --> | |
004912A090000560 060020C0003D0000 | - { |
C9F9F0F2C5D3C3D9 E3D7F0F6C4E4D4D4 |I902ELCRTP06DUMM| (EBCDIC)
E8D7D9E340400000 0000000000000000 |YPRT |
0000000000000000 0000000000000000 | |
0000000000000000 00FFEF --> | |
(73-byte startup success response
record ... IAC EOR)
00DF12A001010A18 0001000000000000 | |
03CD1B451B283130 551B287330703130 | E (10U (s0p10| (ASCII)
2E30306831327630 733062303033541B |.00h12v0s0b003T |
287330421B266440 1B266C304F1B266C |(s0B &d@ &l0O &l|
303038431B266C30 3035431B28733070 |008C &l005C (s0p|
31372E3130683130 7630733062303030 |17.10h10v0s0b000|
541B283130551B28 73307031372E3130 |T (10U (s0p17.10|
6831307630733062 303030541B287330 |h10v0s0b000T (s0|
421B2664401B266C 314F1B266C303035 |B &d@ &l1O &l005|
431B287330703137 2E31306831307630 |C (s0p17.10h10v0|
733062303030541B 266C314F1B287330 |s0b000T &l1O (s0|
7031372E31306831 3076307330623030 |p17.10h10v0s0b00|
30541B2873307031 372E313068313076 |0T (s0p17.10h10v|
3073306230303054 1B266C30303543FF |0s0b000T &l005C |
EF --> | |
(73-byte startup success response
record ... IAC EOR)
00DF12A001010A18 0001000000000000 | |
03CD1B451B283130 551B287330703130 | E (10U (s0p10| (ASCII)
2E30306831327630 733062303033541B |.00h12v0s0b003T |
287330421B266440 1B266C304F1B266C |(s0B &d@ &l0O &l|
303038431B266C30 3035431B28733070 |008C &l005C (s0p|
31372E3130683130 7630733062303030 |17.10h10v0s0b000|
541B283130551B28 73307031372E3130 |T (10U (s0p17.10|
6831307630733062 303030541B287330 |h10v0s0b000T (s0|
421B2664401B266C 314F1B266C303035 |B &d@ &l1O &l005|
431B287330703137 2E31306831307630 |C (s0p17.10h10v0|
733062303030541B 266C314F1B287330 |s0b000T &l1O (s0|
7031372E31306831 3076307330623030 |p17.10h10v0s0b00|
30541B2873307031 372E313068313076 |0T (s0p17.10h10v|
3073306230303054 1B266C30303543FF |0s0b000T &l005C |
EF --> | |
(... 223-byte print record ... ... first of chain ... ... last of chain ... IAC EOR)
（…223字节打印记录……链的第一个……链的最后一个……IAC EOR）
<-- 000A12A001020400 0001FFEF
<--000A12A0001020400 0001FFEF
(10-byte print complete header)
031012A001010A10 0001000000000000 | |
03FFFF1B451B2831 30551B2873307031 | E (10U (s0p1| (ASCII)
372E313068313076 3073306230303054 |7.10h10v0s0b000T|
1B287330421B2664 401B266C314F1B26 | (s0B &d@ &l1O &|
6C303035431B266C 31481B266C314F1B |l005C &l1H &l1O |
266C3032411B266C 31431B266C303030 |&l02A &l1C &l000|
38451B266C303038 431B266C30303439 |8E &l008C &l0049|
461B266130521B26 6C303035430A0A0A |F &a0R &l005C |
0A0A0A0A1B26612B 3030303130561B26 | &a+00010V &|
6C303035431B2661 2B30303231364820 |l005C &a+00216H |
2020202020202020 2020202020202020 | |
2020202020205072 696E74204B657920 | Print Key |
4F75747075742020 2020202020202020 |Output |
2020202020202020 2020202020202020 | |
2020202020205061 6765202020310D0A | Page 1 |
1B26612B30303231 3648202020203537 | &a+00216H 57|
3639535331205634 52334D3020393830 |69SS1 V4R3M0 980|
373203FFFF392020 2020202020202020 |72 9 |
202020202020454C 4352545030362020 | ELCRTP06 |
2020202020202020 202030332F33312F | 03/31/|
3939202031363A33 303A34350D0A1B26 |99 16:30:45 &|
612B303032313648 0D0A1B26612B3030 |a+00216H &a+00|
3231364820202020 446973706C617920 |216H Display |
4465766963652020 2E202E202E202E20 |Device . . . . |
2E203A2020515041 444556303033510D |. : QPADEV003Q |
0A1B26612B303032 3136482020202055 | &a+00216H U|
73657220202E202E 202E202E202E202E |ser . . . . . .|
202E202E202E202E 203A202052434153 | . . . . : RCAS|
54524F0D0A1B2661 2B3030323136480D |TRO &a+00216H |
0A1B26612B303032 313648204D41494E | &a+00216H MAIN|
2020202020202020 2020202020202020 | |
2020202020202020 20202041532F3430 | AS/40|
30204D61696E204D 656E750D0A1B2661 |0 Main Menu &a|
2B30303203FFFF31 3648202020202020 |+002 16H |
2020202020202020 2020202020202020 | |
2020202020202020 2020202020202020 | |
2020202020202020 2020202020202020 | |
2020202020202053 797374656D3A2020 | System: |
20454C4352545030 360D0A1B26612B30 | ELCRTP06 &a+0|
3032313648205365 6C656374206F6E65 |0216H Select one|
206F662074686520 666F6C6C6F77696E | of the followin|
673A0D0A1B26612B 3030323136480D0A |g: &a+00216H |
1B26612B30303231 3648202020202020 | &a+00216H |
312E205573657220 7461736B730D0A1B |1. User tasks |
26612B3030323136 4820202020202032 |&a+00216H 2|
(10-byte print complete header)
031012A001010A10 0001000000000000 | |
03FFFF1B451B2831 30551B2873307031 | E (10U (s0p1| (ASCII)
372E313068313076 3073306230303054 |7.10h10v0s0b000T|
1B287330421B2664 401B266C314F1B26 | (s0B &d@ &l1O &|
6C303035431B266C 31481B266C314F1B |l005C &l1H &l1O |
266C3032411B266C 31431B266C303030 |&l02A &l1C &l000|
38451B266C303038 431B266C30303439 |8E &l008C &l0049|
461B266130521B26 6C303035430A0A0A |F &a0R &l005C |
0A0A0A0A1B26612B 3030303130561B26 | &a+00010V &|
6C303035431B2661 2B30303231364820 |l005C &a+00216H |
2020202020202020 2020202020202020 | |
2020202020205072 696E74204B657920 | Print Key |
4F75747075742020 2020202020202020 |Output |
2020202020202020 2020202020202020 | |
2020202020205061 6765202020310D0A | Page 1 |
1B26612B30303231 3648202020203537 | &a+00216H 57|
3639535331205634 52334D3020393830 |69SS1 V4R3M0 980|
373203FFFF392020 2020202020202020 |72 9 |
202020202020454C 4352545030362020 | ELCRTP06 |
2020202020202020 202030332F33312F | 03/31/|
3939202031363A33 303A34350D0A1B26 |99 16:30:45 &|
612B303032313648 0D0A1B26612B3030 |a+00216H &a+00|
3231364820202020 446973706C617920 |216H Display |
4465766963652020 2E202E202E202E20 |Device . . . . |
2E203A2020515041 444556303033510D |. : QPADEV003Q |
0A1B26612B303032 3136482020202055 | &a+00216H U|
73657220202E202E 202E202E202E202E |ser . . . . . .|
202E202E202E202E 203A202052434153 | . . . . : RCAS|
54524F0D0A1B2661 2B3030323136480D |TRO &a+00216H |
0A1B26612B303032 313648204D41494E | &a+00216H MAIN|
2020202020202020 2020202020202020 | |
2020202020202020 20202041532F3430 | AS/40|
30204D61696E204D 656E750D0A1B2661 |0 Main Menu &a|
2B30303203FFFF31 3648202020202020 |+002 16H |
2020202020202020 2020202020202020 | |
2020202020202020 2020202020202020 | |
2020202020202020 2020202020202020 | |
2020202020202053 797374656D3A2020 | System: |
20454C4352545030 360D0A1B26612B30 | ELCRTP06 &a+0|
3032313648205365 6C656374206F6E65 |0216H Select one|
206F662074686520 666F6C6C6F77696E | of the followin|
673A0D0A1B26612B 3030323136480D0A |g: &a+00216H |
1B26612B30303231 3648202020202020 | &a+00216H |
312E205573657220 7461736B730D0A1B |1. User tasks |
26612B3030323136 4820202020202032 |&a+00216H 2|
2E204F6666696365 207461736B730D0A |. Office tasks | 1B26612B30303231 36480D0A1B26612B | &a+00216H &a+| 3030323136482020 20202020342E2046 |00216H 4. F| 696C65732C206C69 627261726965732C |iles, libraries,| 20616EFFEF | an |
2E204F6666696365 207461736B730D0A |。办公室任务| 1B26612B30303231 36480D0A1B26612B |和a+00216H&a+3030323136482020 2020200342E2046 | 00216H 4。F | 696C65732C206C69 627261726965732C |文件、库| 20616EFFEF | an|
(... 784-byte print record ... ... first of chain ... IAC EOR) <-- 000A12A001020400 0001FFEF
（…784字节打印记录…链的第一个…IAC EOR）<--000A12A0001020400 0001FFEF
(10-byte print complete header)
（10字节打印完整标题）
020312A001010A00 0001000000000000 | |
64206603FFFF6F6C 646572730D0A1B26 |d f olders &| (ASCII)
612B303032313648 0D0A1B26612B3030 |a+00216H &a+00|
3231364820202020 2020362E20436F6D |216H 6. Com|
6D756E6963617469 6F6E730D0A1B2661 |munications &a|
2B3030323136480D 0A1B26612B303032 |+00216H &a+002|
3136482020202020 20382E2050726F62 |16H 8. Prob|
6C656D2068616E64 6C696E670D0A1B26 |lem handling &|
612B303032313648 202020202020392E |a+00216H 9.|
20446973706C6179 2061206D656E750D | Display a menu |
0A1B26612B303032 3136482020202020 | &a+00216H |
31302E20496E666F 726D6174696F6E20 |10. Information |
417373697374616E 74206F7074696F6E |Assistant option|
730D0A1B26612B30 3032313648202020 |s &a+00216H |
202031312E20436C 69656E7420416363 | 11. Client Acc|
6573732F34303020 7461736B730D0A1B |ess/400 tasks |
26612B3030323136 480D0A1B26612B30 |&a+00216H &a+0|
303231364803ED20 2020202039302E20 |0216H 90. |
5369676E206F6666 0D0A1B26612B3030 |Sign off &a+00|
323136480D0A1B26 612B303032313648 |216H &a+00216H|
2053656C65637469 6F6E206F7220636F | Selection or co|
6D6D616E640D0A1B 26612B3030323136 |mmand &a+00216|
48203D3D3D3E0D0A 1B26612B30303231 |H ===> &a+0021|
36480D0A1B26612B 3030323136482046 |6H &a+00216H F|
333D457869742020 2046343D50726F6D |3=Exit F4=Prom|
707420202046393D 5265747269657665 |pt F9=Retrieve|
2020204631323D43 616E63656C202020 | F12=Cancel |
4631333D496E666F 726D6174696F6E20 |F13=Information |
417373697374616E 740D0A1B26612B30 |Assistant &a+0|
3032313648204632 333D53657420696E |0216H F23=Set in|
697469616C206D65 6E750D0A1B26612B |itial menu &a+|
3030323136480D0A 1B26612B30303231 |00216H &a+0021|
36480D0CFFEF |6H |
020312A001010A00 0001000000000000 | |
64206603FFFF6F6C 646572730D0A1B26 |d f olders &| (ASCII)
612B303032313648 0D0A1B26612B3030 |a+00216H &a+00|
3231364820202020 2020362E20436F6D |216H 6. Com|
6D756E6963617469 6F6E730D0A1B2661 |munications &a|
2B3030323136480D 0A1B26612B303032 |+00216H &a+002|
3136482020202020 20382E2050726F62 |16H 8. Prob|
6C656D2068616E64 6C696E670D0A1B26 |lem handling &|
612B303032313648 202020202020392E |a+00216H 9.|
20446973706C6179 2061206D656E750D | Display a menu |
0A1B26612B303032 3136482020202020 | &a+00216H |
31302E20496E666F 726D6174696F6E20 |10. Information |
417373697374616E 74206F7074696F6E |Assistant option|
730D0A1B26612B30 3032313648202020 |s &a+00216H |
202031312E20436C 69656E7420416363 | 11. Client Acc|
6573732F34303020 7461736B730D0A1B |ess/400 tasks |
26612B3030323136 480D0A1B26612B30 |&a+00216H &a+0|
303231364803ED20 2020202039302E20 |0216H 90. |
5369676E206F6666 0D0A1B26612B3030 |Sign off &a+00|
323136480D0A1B26 612B303032313648 |216H &a+00216H|
2053656C65637469 6F6E206F7220636F | Selection or co|
6D6D616E640D0A1B 26612B3030323136 |mmand &a+00216|
48203D3D3D3E0D0A 1B26612B30303231 |H ===> &a+0021|
36480D0A1B26612B 3030323136482046 |6H &a+00216H F|
333D457869742020 2046343D50726F6D |3=Exit F4=Prom|
707420202046393D 5265747269657665 |pt F9=Retrieve|
2020204631323D43 616E63656C202020 | F12=Cancel |
4631333D496E666F 726D6174696F6E20 |F13=Information |
417373697374616E 740D0A1B26612B30 |Assistant &a+0|
3032313648204632 333D53657420696E |0216H F23=Set in|
697469616C206D65 6E750D0A1B26612B |itial menu &a+|
3030323136480D0A 1B26612B30303231 |00216H &a+0021|
36480D0CFFEF |6H |
(... 515-byte print record ... IAC EOR)
（…515字节打印记录…IAC EOR）
<-- 000A12A001020400 0001FFEF
<--000A12A0001020400 0001FFEF
(10-byte print complete header)
001412A001010A00 0001000000000000 | |
03021B45FFEF | E | (ASCII)
(10-byte print complete header)
001412A001010A00 0001000000000000 | |
03021B45FFEF | E | (ASCII)
(... 20-byte print record ... IAC EOR) <-- 000A12A001020400 0001FFEF
（…20字节打印记录…IAC EOR）<--000A12A0001020400 0001FFEF
(10-byte print complete header) 001112A001010A08 0001000000000000 00FFEF -->
（10字节打印完整标题）001112A001010A08 0001000000000000FFEF-->
(... 17-byte NULL print record ... ... last of chain ... IAC EOR) <-- 000A12A001020400 0001FFEF
（…17字节空打印记录…链的最后一个…IAC EOR）<--000A12A0001020400 0001FFEF
(10-byte print complete header)
（10字节打印完整标题）
Discussion of this memo should occur in one of these mailing lists:
本备忘录的讨论应在下列邮件列表中进行：
TN3270E List (Roger Fajman raf@cu.nih.gov). Send subscription requests as e-mail with "subscribe tn3270e your_full_name" to listserv@list.nih.gov.
TN3270E名单（罗杰·法曼）raf@cu.nih.gov). 将带有“subscribe tn3270e your_full_name”的订阅请求通过电子邮件发送至listserv@list.nih.gov.
Midrange-L List (David Gibbs david@midrange.com). Send subscription requests as email with "subscribe midrange-l your_internet_address" to majordomo@midrange.com.
中端-L列表（David Gibbs）david@midrange.com). 以电子邮件形式将订阅请求发送至“订阅中端-l您的互联网地址”majordomo@midrange.com.
Telnet Working Group Mailing List: Send subscription requests as email with "subscribe telnet-ietf" to telnet-ietf-request@bsdi.com.
Telnet工作组邮件列表：通过电子邮件向Telnet ietf发送带有“订阅Telnet ietf”的订阅请求-request@bsdi.com.
[1] IBM, "IBM 5250 Information Display System, Functions Reference Manual", SA21-9247-6, March 1987.
[1] IBM，“IBM 5250信息显示系统，功能参考手册”，SA21-9247-61987年3月。
[2] IBM, "5494 Remote Control Unit, Functions Reference", SC30- 3533-04, August 1995.
[2] IBM，“5494远程控制单元，功能参考”，SC30-3533-041995年8月。
[3] IBM, "AS/400 System API Reference", SC41-5801-01, February 1998.
[3] IBM，“AS/400系统API参考”，SC41-5801-01，1998年2月。
[4] IBM, "AS/400 TCP/IP Configuration and Reference", SC41-5420-02, September 1998.
[4] IBM，“AS/400 TCP/IP配置和参考”，SC41-5420-021998年9月。
[5] IBM, "AS/400 Communications Configuration", SC41-5401-00, August 1997.
[5] IBM，“AS/400通信配置”，SC41-5401-00，1997年8月。
[6] IBM, "SNA Formats", GA27-3136-13, November 1993.
[6] IBM，“SNA格式”，GA27-3136-131993年11月。
[7] IBM, "Using the Pageprinter 3812 with System/36 or System/38", S544-3343-01, September 1997.
[7] IBM，“将页式打印机3812与System/36或System/38配合使用”，S544-3343-01，1997年9月。
[8] Postel, J. and J. Reynolds, "Telnet Protocol Specification", STD 8, RFC 854, May 1983.
[8] Postel，J.和J.Reynolds，“Telnet协议规范”，STD 8，RFC 854，1983年5月。
[9] Postel, J. and J. Reynolds, "Telnet Option Specifications", STD 8, RFC 855, May 1983.
[9] Postel，J.和J.Reynolds，“Telnet选项规范”，标准8，RFC 855，1983年5月。
[10] Postel, J. and J. Reynolds, "Telnet Binary Transmission", STD 27, RFC 856, May 1983.
[10] Postel，J.和J.Reynolds，“Telnet二进制传输”，STD 27，RFC 856，1983年5月。
[11] VanBokkeln, J., "Telnet Terminal-Type Option", RFC 1091, February 1989.
[11] VanBokkeln，J.，“Telnet终端类型选项”，RFC 109119989年2月。
[12] Postel, J. and J. Reynolds, "Telnet End of Record Option", RFC 885, December 1983.
[12] Postel，J.和J.Reynolds，“Telnet记录结束选项”，RFC 885，1983年12月。
[13] Alexander, S., "Telnet Environment Option", RFC 1572, January 1994.
[13] Alexander，S.，“Telnet环境选项”，RFC 1572，1994年1月。
[14] Chmielewski, P., "5250 Telnet Interface", RFC 1205, February 1991.
[14] Chmielewski，P.，“5250 Telnet接口”，RFC12051991年2月。
[15] Postel, J. and J. Reynolds, "Telnet Supress Go Ahead Option", STD 29, RFC 858, May 1983.
[15] Postel，J.和J.Reynolds，“Telnet Suppress前进选项”，STD 29，RFC 858，1983年5月。
[16] IBM, "AS/400 National Language Support", SC41-5101-01, February 1998.
[16] IBM，“AS/400国家语言支持”，SC41-5101-01，1998年2月。
[17] Data Encryption Standard (DES), Federal Information Processing Standards Publication 46-2, January 22, 1988.
[17] 数据加密标准（DES），联邦信息处理标准出版物46-2，1988年1月22日。
[18] DES Modes of Operation, Federal Information Processing Standards Publication 81, December 1980.
[18] DES操作模式，联邦信息处理标准出版物81，1980年12月。
[19] Reynolds, J. and J. Postel, "Assigned Numbers", STD 2, RFC 1700, October 1994.
[19] Reynolds，J.和J.Postel，“分配的数字”，标准2，RFC 1700，1994年10月。
[20] IBM, "IBM Pageprinter 3812 Programming Reference", S544-3268.
[20] IBM，“IBM Pageprinter 3812编程参考”，S544-3268。
Security considerations of passwords are discussed in Section 6.
第6节讨论了密码的安全注意事项。
Thomas E. Murphy, Jr. IBM Corporation 1701 North Street Endicott, NY 13760
纽约州恩迪科特北街1701号小托马斯·E·墨菲IBM公司，邮编13760
Phone: (607) 752-5482 Fax: (607) 752-5421 EMail: murphyte@us.ibm.com
电话：（607）752-5482传真：（607）752-5421电子邮件：murphyte@us.ibm.com
Paul F. Rieth IBM Corporation 1701 North Street Endicott, NY 13760
Paul F.Rieth IBM Corporation纽约州恩迪科特北街1701号，邮编13760
Phone: (607) 752-5474 Fax: (607) 752-5421 EMail: rieth@us.ibm.com
电话：（607）752-5474传真：（607）752-5421电子邮件：rieth@us.ibm.com
Jeffrey S. Stevens IBM Corporation 1701 North Street Endicott, NY 13760
Jeffrey S.Stevens IBM Corporation纽约州恩迪科特北街1701号，邮编13760
Phone: (607) 752-5488 Fax: (607) 752-5421 EMail: jssteven@us.ibm.com
电话：（607）752-5488传真：（607）752-5421电子邮件：jssteven@us.ibm.com
UPDATES
更新
This memo is an update to RFC 1205 [14], which describes the 5250 Telnet Interface. This update enhances that description to include device negotiation as well as printer support.
本备忘录是对RFC 1205[14]的更新，其中描述了5250 Telnet接口。此更新增强了该描述，包括设备协商和打印机支持。
This memo makes use of RFC 1572 [13] to enhance communications with 5250 Telnet clients. RFC 1572 is currently on the Standards Track as a Proposed Standard, and is listed in Assigned Numbers [19].
本备忘录利用RFC 1572[13]加强与5250 Telnet客户端的通信。RFC 1572目前作为一项拟议标准列入标准轨道，并在指定编号中列出[19]。
Copyright (C) The Internet Society (2000). All Rights Reserved.
版权所有（C）互联网协会（2000年）。版权所有。
This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English.
本文件及其译本可复制并提供给他人，对其进行评论或解释或协助其实施的衍生作品可全部或部分编制、复制、出版和分发，不受任何限制，前提是上述版权声明和本段包含在所有此类副本和衍生作品中。但是，不得以任何方式修改本文件本身，例如删除版权通知或对互联网协会或其他互联网组织的引用，除非出于制定互联网标准的需要，在这种情况下，必须遵循互联网标准过程中定义的版权程序，或根据需要将其翻译成英语以外的其他语言。
The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns.
上述授予的有限许可是永久性的，互联网协会或其继承人或受让人不会撤销。
This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
本文件和其中包含的信息是按“原样”提供的，互联网协会和互联网工程任务组否认所有明示或暗示的保证，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。
Acknowledgement
确认
Funding for the RFC Editor function is currently provided by the Internet Society.
RFC编辑功能的资金目前由互联网协会提供。