Debian Codegraph @

rfc1646.html

raw
1 <pre>Network Working Group C. Graves
2 Request for Comments: 1646 T. Butts
3 Category: Informational M. Angel
4 Open Connect Systems
5 July 1994
6
7
8 <span class="h1">TN3270 Extensions for LUname and Printer Selection</span>
9
10 Status of this Memo
11
12 This memo provides information for the Internet community. This memo
13 does not specify an Internet standard of any kind. Distribution of
14 this memo is unlimited.
15
16 Abstract
17
18 This document describes protocol extensions to TN3270. There are two
19 extensions outlined in this document. The first defines a way by
20 which a TN3270 client can request a specific device (LUname) from a
21 TN3270 server. The second extension specifies how a TN3270 printer
22 device can be requested by a TN3270 client and the manner in which
23 the 3270 printer status information can be sent to the TN3270 server.
24 Discussions and suggestions for improvements to these enhancements
25 should be sent to the TN3270E Working Group mailing list
26 [email protected] . These extensions will be called TN3287 in this
27 document. This information is being provided to members of the
28 Internet community that want to support the 3287 data stream within
29 the TELNET protocol.
30
31 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. INTRODUCTION</span>
32
33 The need to communicate with IBM mainframe systems has a number of
34 unique requirements associated with it. This document addresses
35 those needs in a TCP/IP communications network.
36
37 IBM terminals are generically referred to as 3270's which includes a
38 broad range of terminals and devices,not all of which actually begin
39 with the numbers 327x.
40
41 The 3270 family of terminals and the IBM mainframe applications
42 systems are VERY closely coupled and it is the nature of the way the
43 3270s and the applications interact which require that this document
44 be available to provide a consistent way for the TCP/IP environment
45 to interact effectively with the 3270 applications of the IBM
46 mainframe world.
47
48
49
50
51
52 <span class="grey">Graves, Butts &amp; Angel [Page 1]</span></pre>
53 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
54 <span class="grey"><a href="./rfc1646">RFC 1646</a> TN3270 Extensions July 1994</span>
55
56
57 IBM mainframe applications systems have existed for almost two
58 decades now and are used to serve tens of thousands of users daily.
59 For this reason it is usually the need of a mainframe environment to
60 add TCP/IP network support WITHOUT writing new applications to run
61 with the TCP network. The TN3270 series of documents addresses how
62 this can be done and maintain compatibility with those mainframe
63 application systems.
64
65 One of the unique characteristics of the 3270 terminals is their
66 ability to communicate status information in an out-of-band data
67 flow. These status's are in turn used by the applications systems to
68 support error recovery, and conflict resolutions, examples of these
69 are printer out of paper, and terminal powered up. The terminals are
70 also half duplex and block mode in their operations, which results in
71 the need to communicate when blocks are being sent, when they end,
72 and when they cannot be sent. This document describes these
73 characteristics in IBM VTAM/SNA terms. Some VM mainframe application
74 systems do not use VTAM, so for those systems these terms don't
75 apply. For any systems which use VTAM these terms apply and are
76 dealt with in some way by the TCP/IP to VTAM interface.
77
78 VTAM/SNA is a hierarchical network and some of that hierarchy needs
79 to be addressed by the TCP network attaching to it if the
80 applications systems are to continue to provide the same applications
81 support that they have provided to the 3270 terminals.
82
83 The 3270 terminal environment consists of a terminal controller with
84 terminals attached to that controller. In VTAM/SNA this controller
85 is called a PU (Physical Unit) and the terminals called LUs (Logical
86 Units). The PU is used to communicate management information to the
87 VTAM/SNA system, and the LU is used by the application to communicate
88 with the terminal. VTAM/SNA identifies each LU and PU in a network
89 by a unique name. These names are referred to as LUnames and
90 PUnames, and is how the network is managed and the applications
91 identify what terminals are being communicated with in the network.
92 The actual connection between a terminal and the applications is
93 referred to as a session, and it is this session which has both in-
94 band and out-of-band information flows sent between the applications
95 and the terminals.
96
97 VTAM/SNA 3270 terminals actually have two sessions when communicating
98 with the applications. One session is directly connected with the
99 application and the other session is connected directly to VTAM. It
100 is the session with VTAM, also called the SSCP, that is used to
101 communicate the out-of-band information flows. This session is
102 called the SSCP-LU session, and the session with the application is
103 called the LU-LU session (in VTAM an applications is just another
104 Logical Unit).
105
106
107
108 <span class="grey">Graves, Butts &amp; Angel [Page 2]</span></pre>
109 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
110 <span class="grey"><a href="./rfc1646">RFC 1646</a> TN3270 Extensions July 1994</span>
111
112
113 One such out-of-band flow is the LUSTAT message which tells the
114 application that the status of the terminal has changed, and is how a
115 printer or screen tells the application that it is ready, or is not
116 ready to receive data.
117
118 There are also flows which must be able to flow in the LU-LU session
119 to help control the use of the terminal by applications. The block
120 of information sent in a session is called an RU (Request Unit) and
121 it tells what type of data this block contains, how long it is and if
122 more data (RUs) is coming along. This is a gross over simplification
123 of what RUs are and do, but it should help understand their use in
124 the TN3270 documents. Some of the VTAM/SNA terms used to describe
125 what an RU is requesting are: Chains/chaining which tell a session
126 partner that another RU is being sent or not being sent in this
127 transmission. Brackets which are used to indicate that a unit of
128 work is complete, such as when a printout of a file is complete.
129
130 The determination of what part of the VTAM/SNA protocols such as
131 brackets and chaining are to be used are managed by VTAM tables
132 called LOGMODE tables. These tables are selected when an LU-LU
133 session is started and set up such things as bracket, and/or chaining
134 protocols; and the type of terminal data contained in the RUs, such
135 as printer data without screen formatting data (LU type 1), 3270
136 screen formatted data (LU type 2) and 3270 screen formatted data for
137 a printer (LU type 3). The LOGMODE tables also contain the size of
138 the RU to be sent and received. These tables also communicate the
139 screen size of 3270 terminals such as 24X80 (Model 2), 27X132 (Model
140 5), etc. Each LU has a LOGMODE table entry hard assigned to it as
141 part of the VTAM configuration (often called a GEN). The selection
142 of these table entries can't be controlled by the terminal LU or PU.
143 They can only be selected by the user at connection/logon time or by
144 the application when the connection is established. The actual
145 LOGMODE entries to be used during a session are sent at session logon
146 time, in a special type of RU called a BIND. Once the bind has been
147 sent then the rules for the use of the session have been set, can't
148 be changed, and must be followed.
149
150 The purpose of the TN3287 protocol is to provide a general IBM 3270
151 host printer communications facility. Its primary goal is to allow a
152 method of connecting printer devices and printer-oriented processes
153 to each other. This protocol will allow a TN3270 Client to process
154 3287 print data streams.
155
156 This memo supplements and extends the STD 8, <a href="./rfc854">RFC 854</a>, TELNET Protocol
157 Specification. This memo also presents an example of the correct
158 implementation.
159
160
161
162
163
164 <span class="grey">Graves, Butts &amp; Angel [Page 3]</span></pre>
165 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
166 <span class="grey"><a href="./rfc1646">RFC 1646</a> TN3270 Extensions July 1994</span>
167
168
169 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. GENERAL CONSIDERATIONS</span>
170
171 A TELNET connection is a Transmission Control Protocol (TCP)
172 connection used to transmit data with interspersed TELNET control
173 information.
174
175 The companion document, STD 8, <a href="./rfc854">RFC 854</a> -- "TELNET Protocol
176 Specification" should be consulted for further information about the
177 TELNET command, codes and code sequences referenced in this
178 specification.
179
180 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. CLIENT-SERVER NEGOTIATION</span>
181
182 The TN3270 Client and Server require a specific negotiation protocol.
183 After the negotiation is complete, all transmission between the
184 Client and Server is in TELNET Binary format with a TELNET "End-Of-
185 Record(EOR)" sequence at the end of each data stream.
186
187 Support for the TN3287 data stream requires that both sides:
188
189 A. Are able to exchange binary data.
190
191 B. Can establish the agreement between client and server on the
192 terminal type that will be used.
193
194 C. Agree to use the TELNET IAC EOR as a delimiter for inbound
195 and outbound TN3287 data streams
196
197 This implementation requires the options: TERMINAL-TYPE and BINARY be
198 successfully negotiated between the Client and Server before
199 processing of any print data streams.
200
201 This implementation supports host applications that can mix LU 1 and
202 LU 3 type data in the data stream.
203
204 <span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a> TN3287 SERVER</span>
205
206 The maximum Request Unit (RU) size is server specific, but should not
207 exceed 4 kilobytes.
208
209 The LU type is determined by the bind from the mainframe application.
210 The server, when bound, must remember LU 1 or LU 3 type.
211
212 The server will automatically unbind the session upon receipt of a
213 TELNET CLOSE command. The printer will be reported to VTAM as
214 powered down until a new TELNET connection is established.
215
216
217
218
219
220 <span class="grey">Graves, Butts &amp; Angel [Page 4]</span></pre>
221 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
222 <span class="grey"><a href="./rfc1646">RFC 1646</a> TN3270 Extensions July 1994</span>
223
224
225 <span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a> TN3287 CLIENT</span>
226
227 The TN3287 Client is a TN3270 client created specifically to print
228 mainframe 3270 print data. The client emulates the IBM device type
229 that it identifies itself to the TN3270 server as, in this case, an
230 IBM 3287 model 1 type printer. The design of this printer protocol
231 is aligned with the way printing occurs in the IBM host and how 3270
232 printers function. These printer extensions DO NOT support a 3270
233 printer client that cannot accept both types LU 1 and LU 3 printer
234 streams. No IBM printer operates in this fashion, and as a result,
235 no TN3270 server could function properly with mainframe applications
236 if it didn't allow for a mixing of LU 1 and LU 3 data streams. The
237 common way in which this can occur is printer sharing between
238 multiple IBM host applications, such as CICS and JES. Since there is
239 no restriction, the JES can be configured to output LU 1 data
240 streams, and the CICS can be configured for LU 3 data streams.
241 Therefore, the server will identify what LU type the current
242 application connected to the server is using. If that type is LU 1,
243 ALL message records sent to the Client will be preceded by one byte
244 of binary zeros (0x00). If the first byte is not zeros, then that
245 byte will be a valid LU type 3 Write-Command-Code(WCC), which can
246 NEVER be zeros. Thus, the client can tell the LU type of data as
247 each record is received.
248
249 This protocol does allow for the client to shutdown if the client
250 does not wish to support both LU types. This is accomplished by
251 detecting an invalid data type from the received record, and
252 notifying the user that the mainframe application has sent LU type x
253 print data and should be configured for LU type y printing.
254
255 <span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. COMMAND STRUCTURE</span>
256
257 1. All TELNET commands consist of at least a two-byte sequence:
258 the "Interpret-as-Command(IAC)" escape character followed by
259 the code for the command.
260
261 NOTE: Since the TELNET IAC character (255 decimal) is used as a
262 delimiter (together with EOR) in the inbound and outbound data
263 streams, a data byte within the data stream itself that has the same
264 value as the IAC command is sent as two bytes (255, 255) and one byte
265 is discarded.
266
267 <span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a> TELNET COMMANDS</span>
268
269 Command meaning - WILL and DO commands are used to obtain and grant
270 permission for the subsequent subnegotiation. Both sides must
271 exchange WILL TERM-TYPE and DO TERM-TYPE before subnegotiation.
272
273
274
275
276 <span class="grey">Graves, Butts &amp; Angel [Page 5]</span></pre>
277 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
278 <span class="grey"><a href="./rfc1646">RFC 1646</a> TN3270 Extensions July 1994</span>
279
280
281 The actual exchange of information is done within the option
282 subcommand.
283
284 &lt;IAC DO TERMINAL-TYPE&gt; Sender requests that the other party begin
285 terminal-type sub-negotiation.
286
287 &lt;IAC WILL TERMINAL-TYPE&gt; Sender is willing to send terminal-type
288 information in a subsequent sub-negotiation.
289
290 &lt;IAC SB TERMINAL-TYPE SEND IAC SE&gt; Sender requests the receiver to
291 transmit his terminal-type.
292
293 &lt;IAC SB TERM TYPE IS IBM-3287-1 IAC SE&gt; Sender is stating the name
294 of his terminal-type. The code for &lt;IS&gt; is 0. Optionally, a
295 specific Logical Unit (LU) can be requested by using the TERMINAL-
296 TYPE string below. If no LUname is specified, the first available
297 3287 LU is selected.
298
299 IAC SB TERM-TYPE IS IBM-3287-1 @ LUNAME IAC SE
300
301 &lt;IAC DO BINARY&gt; Sender requests that sender of the data starts
302 transmitting or confirms that the sender of data is expected to
303 transmit characters that are to be interpreted as 8 bits of binary
304 data by the receiver.
305
306 &lt;IAC WILL BINARY&gt; Sender requests permission to begin transmitting,
307 or confirms it will now begin transmitting binary data.
308
309 An &lt;EOR&gt; is sent at the end of each SNA Request Unit (RU) end of
310 chain, in either direction. The first byte following the &lt;EOR&gt; is a
311 Write-Command-Code(WCC) for LU 3 data streams.
312
313 An &lt;AO&gt; is sent at the end of the SNA RU and end of bracket. This
314 signifies the end of the print output or file by the IBM host
315 application and possibly a change of LU type.
316
317 <span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a> COMMAND VALUES</span>
318
319
320 TELNET COMMAND CODE
321 IAC Interpret as Command 255
322 DO 253
323 WILL 251
324 SB SuBnegotiation option 250
325 SE Subnegotiation End 240
326 TERMINAL-TYPE 24
327 SEND 1
328 IS 0
329
330
331
332 <span class="grey">Graves, Butts &amp; Angel [Page 6]</span></pre>
333 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
334 <span class="grey"><a href="./rfc1646">RFC 1646</a> TN3270 Extensions July 1994</span>
335
336
337 EOR End-Of-Record 25
338 BINARY 0
339 AO Abort Output 245
340 IP Interrupt Process 244
341 AYT Are You There 246
342 BREAK 243
343
344 NOTE: The above codes and code sequences have the indicated meaning
345 only when immediately preceded by an "Interpret as Command (IAC)".
346
347 <span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. TN3270 Printer Status Message</span>
348
349 The status message can be sent at any time. It must be sent every
350 time the TN3270 Server sends an End-of-Record(EOR) indicator to the
351 TN3270 Client, or when a printing error occurs at the Client. The
352 Printer Status Message is only sent by the TN3270 Client. Once the
353 End-Of-Record IAC is processed, the TN3270 Client sends the status
354 message to the server when it is ready to receive more print data.
355
356 MESSAGE DESCRIPTION: SOH % R S1 S2 IAC EOR
357
358
359 SOH = 0X01
360 % = 0X6C
361 R = 0XD9
362 S1 = Status/Sense Byte 0
363 S2 = Status/Sense Byte 1
364 IAC = Telnet IAC Character
365 EOR = Telnet EOR Character
366
367 <span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a> Status/Sense Byte description</span>
368
369 <span class="h4"><a class="selflink" id="section-5.1.1" href="#section-5.1.1">5.1.1</a>. S/S Byte 0:</span>
370
371 High Order Low Order
372
373
374 _____________________________________________________________
375 | |
376 | 0 1 2 3 4 5 6 7 |
377 |___________________________________________________________|
378
379
380 Bit Number: Bit Definition:
381
382 0 Always Zero
383
384 1 Always Zero
385
386
387
388 <span class="grey">Graves, Butts &amp; Angel [Page 7]</span></pre>
389 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
390 <span class="grey"><a href="./rfc1646">RFC 1646</a> TN3270 Extensions July 1994</span>
391
392
393 2 Always Zero
394
395 3 Always Zero
396
397 4 Always Zero
398
399 5 Unit Specify - is set due to an error
400 condition. The reason for the error
401 condition will be indicated in S/S Byte 1.
402 See Note 1*.
403
404 6 Device End - when this bit sent in response
405 to a data message it indicates the client
406 has successfully processed the data message
407 from the server and notifies the server to
408 send a new data message to the client when
409 available. See Note 2*.
410
411 7 Always Zero
412
413
414 Note 1*: A negative response to the Server's data message would be
415 S/S Byte 0 Bit 5 "Unit Specify condition". The possible Unit Specify
416 conditions are listed below. (See <a href="#section-3.2">Section 3.2</a> for bit settings for
417 the Unit Specify conditions listed below.)
418
419 Unit Specify Condition: SNA Sense Code sent to host:
420
421 Command Rejected 0X10030000
422 Intervention Required 0X08020000
423 Data Check 0X10010000
424 Operation Check 0X10050000
425 Component Disconnected (LU) 0X08020000
426
427 Note 2*: Device End - A positive response to the Server's data
428 message would be the "Device End" bit (S/S Byte 0 Bit 6) to indicate
429 a ready to receive data from the host condition. This will also be
430 sent after clearing a previous Unit Specify condition of
431 "Intervention Required".
432
433
434
435
436
437
438
439
440
441
442
443
444 <span class="grey">Graves, Butts &amp; Angel [Page 8]</span></pre>
445 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
446 <span class="grey"><a href="./rfc1646">RFC 1646</a> TN3270 Extensions July 1994</span>
447
448
449 <span class="h4"><a class="selflink" id="section-5.1.2" href="#section-5.1.2">5.1.2</a>. S/S Byte 1:</span>
450
451 High Order Low Order
452
453 ______________________________________________________________
454 | |
455 | 0 1 2 3 4 5 6 7 |
456 |____________________________________________________________|
457
458
459 Bit Number: Bit Definition:
460
461
462 0 Always Zero
463
464 1 Always Zero
465
466 2 Command Rejected (CR) -- This bit
467 indicates an invalid 3270 command
468 generated.
469
470 3 Intervention Required - Printer Not Ready.
471 See Note 3*.
472
473 4 Component Disconnected - Printer is powered
474 off or printer cable not connected. See
475 Note 4*.
476
477 5 Data Check - Invalid print data
478
479 6 Always Zero
480
481 7 Operation Check - An illegal buffer address
482 or incomplete order sequence
483
484 Note 3*: The Intervention Required is cleared by sending an S/S
485 message with the "Device End" bit (Bit 6 of S/S byte 0). The LUSTAT
486 sent to the host is 0X00010000. The IBM host interprets this as a
487 "printer now ready" condition.
488
489 Note 4*: The Component disconnected is cleared by sending an S/S
490 message with the "Device End" bit (Bit 6 of S/S byte 0). The LUSTAT
491 sent to the host is 0X082B0000. The IBM host interprets this as a
492 "printer now ready -- presentation space integrity may be lost"
493 condition.
494
495
496
497
498
499
500 <span class="grey">Graves, Butts &amp; Angel [Page 9]</span></pre>
501 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
502 <span class="grey"><a href="./rfc1646">RFC 1646</a> TN3270 Extensions July 1994</span>
503
504
505 <span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. The following is an example of the Client-Server negotiation</span>
506 <span class="h2"> process.</span>
507
508 Server: IAC DO TERMINAL-TYPE
509 Client: IAC WILL TERMINAL-TYPE
510 Server: IAC SB TERMINAL-TYPE SEND IAC SE
511 Client: IAC SB TERMINAL-TYPE IS IBM-3287-1 IAC SE
512
513 Note: To request a specific LU the TERMINAL-TYPE string would be:
514 IAC SB TERMINAL-TYPE IS IBM-3287-1 @ LUNAME IAC SE
515 (The client has specified its terminal type is an IBM-3287-1)
516
517
518 Server: IAC DO END-OF-RECORD
519 Client: IAC WILL END-OF-RECORD
520 Server: IAC WILL END-OF-RECORD
521 Client: IAC DO END-OF-RECORD
522
523 (The Server and Client have both agreed to transmit End-Of-Record
524 (EOR)).
525
526
527 Server: IAC DO TRANSMIT-BINARY
528 Client: IAC WILL TRANSMIT-BINARY
529 Server: IAC WILL TRANSMIT-BINARY
530 Client: IAC DO TRANSMIT-BINARY
531 (The Server and Client have both agreed to use binary
532 transmission)
533
534
535 Server: 0x00 (3270 PRINT DATA)
536 Client: (S/S with DEV END) IAC EOR
537 Server: 0x00 (3270 PRINT DATA) IAC EOR
538
539 NOTE: LU 1 type data is prefaced with a 0x00 character. LU 3
540 type data is not prefaced with a special character. This
541 character will precede print data in each chain, and should be
542 discarded before the print data is processed. An &lt;IAC EOR&gt; must
543 be received before changing to LU 1 or LU 3 type data.
544
545 Client: (S/S with IR) IAC EOR (This indicates a paper jam
546 at printer.)
547 Client: (S/S with DE) IAC EOR (This indicates the clearing
548 of above condition.)
549 Server: 0x00 (3270 PRINT DATA) (This indicates start of LU 1
550 data)
551
552 Server: (3270 PRINT DATA)
553
554
555
556 <span class="grey">Graves, Butts &amp; Angel [Page 10]</span></pre>
557 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
558 <span class="grey"><a href="./rfc1646">RFC 1646</a> TN3270 Extensions July 1994</span>
559
560
561 Server: (3270 PRINT DATA)
562 Server: (3270 PRINT DATA) IAC EOR
563 Client: (S/S with DE) IAC EOR
564 Server: 0x00 (LAST 3270 PRINT DATA) IAC EOR
565
566
567 Client: (S/S with DE) IAC EOR
568 Server: IAC AO
569 (The Abort Output &lt;AO&gt; signifies the end-of-bracket -- end of
570 print job)
571
572 <span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. SECURITY CONSIDERATIONS</span>
573
574 This document does not specify a security methodology to insure that
575 the client requesting a printer LU name is authorized to access that
576 LU. Currently, this is left up to individual server implementations.
577 The design of the protocols described in this document allow for the
578 future incorporation of the RFCs regarding encryptions and
579 authentication protocols and services. However, before this may
580 occur, certain extensions may be required to the protocols defined in
581 this document or to the encryptions and authentication services and
582 protocols.
583
584 <span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. ERROR CONDITIONS</span>
585
586 After a client and server have successfully completed negotiation, a
587 number of potential error conditions may be detected by the server
588 which require notifying the client and aborting the connection.
589
590 When an error condition is detected by the server, the client must be
591 negotiated back into NVT mode by the server sending a "WONT/DONT
592 BINARY" TELNET sequence and the client responding with the
593 appropriate "DONT/WONT BINARY" TELNET sequence.
594
595 The server should immediately send the appropriate error message to
596 the client as an ASCII string and then close the connection. The
597 error message should be prefixed by a numeric identifier to precisely
598 notify the client of the specific error condition. The error message
599 sent to the client should be routed to the proper console or log for
600 corrective action.
601
602 Below is a list of error conditions identified by numeric value,
603 error text, meaning of the error and recovery procedure.
604
605 Message: "01 No LU's of the type configured"
606
607 Meaning: The configuration definition on the server
608 does not include the LU type requested.
609
610
611
612 <span class="grey">Graves, Butts &amp; Angel [Page 11]</span></pre>
613 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
614 <span class="grey"><a href="./rfc1646">RFC 1646</a> TN3270 Extensions July 1994</span>
615
616
617 Recovery: Notify your Systems Administrator as this
618 is a permanent error condition.
619
620 Message: "02 Requested LU unavailable"
621
622 Meaning: The requested LU is not available at
623 this time.
624
625 Recovery: This may be a temporary error and may
626 be retried periodically. If the condition
627 persists contact your Systems Administrator.
628
629 Message: "03 Requested LU type is inconsistent with configuration"
630
631 Meaning: The LU requested does not match the terminal
632 type in the server configuration.
633
634 Recovery: Notify your Systems Administrator as this
635 is a permanent error condition.
636
637 Message: "04 Requested LU is not configured"
638
639 Meaning: The LU is not defined in server configuration.
640
641 Recovery: Notify your Systems Administrator as this
642 is a permanent error condition.
643
644 When a client receives a message not defined in the above list, the
645 message should be displayed to a console or log and the connection to
646 the server should be closed. No other recovery should be attempted
647 as this is most likely a fatal error condition. (Notify your Systems
648 Administrator.)
649
650 <span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. REFERENCES</span>
651
652 [<a id="ref-1">1</a>] Postel, J., and J. Reynolds, "TELNET Protocol Specification", STD
653 8, <a href="./rfc854">RFC 854</a>, USC/Information Services Institute, May 1983.
654
655 [<a id="ref-2">2</a>] VanBokkeln, J., "TELNET Terminal-Type Option" <a href="./rfc1091">RFC 1091</a>, FTP
656 Software Inc., February 1989.
657
658 [<a id="ref-3">3</a>] Postel, J., and J. Reynolds, "TELNET Binary Transmission", STD
659 27, <a href="./rfc856">RFC 856</a>, USC/Information Services Institute, May 1983.
660
661
662
663
664
665
666
667
668 <span class="grey">Graves, Butts &amp; Angel [Page 12]</span></pre>
669 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
670 <span class="grey"><a href="./rfc1646">RFC 1646</a> TN3270 Extensions July 1994</span>
671
672
673 Authors' Addresses
674
675 Cleve Graves
676 2711 LBJ Freeway
677 Dallas, Texas 75234
678
679 Phone: (214) 484-5200
680 EMail: [email protected]
681
682
683 Thomas Butts
684 2711 LBJ Freeway
685 Dallas, Texas 75234
686
687 Phone: (214) 484-5200
688 EMail: [email protected]
689
690
691 Michelle Angel
692 2711 LBJ Freeway
693 Dallas, Texas 75234
694
695 Phone: (214) 484-5200
696 EMail: [email protected]
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724 Graves, Butts &amp; Angel [Page 13]
725 </pre>