Browse Prior Art Database

TN3270 Enhancements (RFC1647)

IP.com Disclosure Number: IPCOM000002483D
Original Publication Date: 1994-Jul-01
Included in the Prior Art Database: 2000-Sep-12
Document File: 29 page(s) / 79K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

B. Kelly: AUTHOR

Abstract

This document describes a protocol that more fully supports 3270 devices than do the existing tn3270 practices. Specifically, it defines a method of emulating both the terminal and printer members of the 3270 family of devices via Telnet; it provides for the ability of a Telnet client to request that it be assigned a specific device- name (also referred to as "LU name" or "network name"); finally, it adds support for a variety of functions such as the ATTN key, the SYSREQ key, and SNA response handling.

This text was extracted from a ASCII Text document.
This is the abbreviated version, containing approximately 4% of the total text.

Network Working Group B. Kelly

Request for Comments: 1647 Auburn University

Category: Standards Track July 1994

TN3270 Enhancements

Status of this Memo

This document specifies an Internet standards track protocol for the

Internet community, and requests discussion and suggestions for

improvements. Please refer to the current edition of the "Internet

Official Protocol Standards" (STD 1) for the standardization state

and status of this protocol. Distribution of this memo is unlimited.

Abstract

This document describes a protocol that more fully supports 3270

devices than do the existing tn3270 practices. Specifically, it

defines a method of emulating both the terminal and printer members

of the 3270 family of devices via Telnet; it provides for the ability

of a Telnet client to request that it be assigned a specific device-

name (also referred to as "LU name" or "network name"); finally, it

adds support for a variety of functions such as the ATTN key, the

SYSREQ key, and SNA response handling.

This protocol would be negotiated and implemented under a new Telnet

Option and would be unrelated to the Telnet 3270 Regime Option as

defined in RFC 1041 [1].

TABLE OF CONTENTS

1. Introduction ............................................... 2

2. TN3270E OVERVIEW ........................................... 3

3. COMMAND NAMES AND CODES .................................... 4

4. COMMAND MEANINGS ........................................... 5

5. DEFAULT SPECIFICATION ...................................... 6

6. MOTIVATION ................................................. 7

7. TN3270E SUB-NEGOTIATION RULES .............................. 7

7.1 DEVICE-TYPE Negotiation ................................ 7

7.1.1 Device Pools ...................................... 8

7.1.2 CONNECT Command ................................... 9

7.1.3 ASSOCIATE Command ................................. 10

7.1.4 Device Selection Rules ............................ 10

7.1.5 Accepting a Request ............................... 11

7.1.6 REJECT Command .................................... 12

7.2 FUNCTIONS Negotiation .................................. 13

7.2.1 Commands .......................................... 13

7.2.2 List of TN3270E Functions ......................... 14

8. TN3270E DATA MESSAGES ...................................... 15

8.1 The TN3270E Message Header ............................. 16

8.1.1 DATA-TYPE Field ................................... 16

8.1.2 REQUEST-FLAG Field ................................ 17

8.1.3 RESPONSE-FLAG Field ............................... 17

8.1.4 SEQ-NUMBER Field .................................. 18

9. BASIC TN3270E ..............................