rfc2877.txt
来自「中、英文RFC文档大全打包下载完全版 .」· 文本 代码 · 共 1,533 行 · 第 1/5 页
TXT
1,533 行
Murphy, et al. Informational [Page 22] RFC 2877 5250 Telnet Enhancements July 200010. Printer Steady-State Pass-Through Interface 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. +------------------------------------------------------------------+ | +-- 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) BYTES 2-3: GDS Identifier ('12A0'X) BYTE 4-5: Data flow record 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.Murphy, et al. Informational [Page 23] RFC 2877 5250 Telnet Enhancements July 2000 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 BYTE 6: Length printer pass-through header including this field (LL) BYTES 7-8: Flags 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 9: Printer operation code '01'X Print/Print complete '02'X Clear Print Buffers BYTE 10-LL: Diagnostic information (1) If BYTE 7 = xx1x xxxx then bytes 10-LL may contain: Printer ready C9 00 00 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 If BYTE 7 = 1xxx xxxx then bytes 10-LL may contain: (3) Cancel 08 11 02 00 Invalid print parameter 08 11 02 29Murphy, et al. Informational [Page 24] RFC 2877 5250 Telnet Enhancements July 2000 Invalid print command 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. 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: 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 3. These are printer negative responses. Further information on these commands may be obtained from the 5494 Remote Control Unit Functions Reference guide [2]. The print data will start in byte LL+1.10.1 Example of a Print Record 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.Murphy, et al. Informational [Page 25] RFC 2877 5250 Telnet Enhancements July 2000 +--------------------------------------------------------------------+ | +-- 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/ordersMurphy, et al. Informational [Page 26] RFC 2877 5250 Telnet Enhancements July 200010.2 Example of a Print Complete Record 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. +-------------------------------------------------------------------+ | +-- 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 Complete10.3 Example of a Null Print Record 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). 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.Murphy, et al. Informational [Page 27] RFC 2877 5250 Telnet Enhancements July 2000 +------------------------------------------------------------------+ | +-- 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 | +------------------------------------------------------------------+ ⌨️ 快捷键说明
复制代码Ctrl + C
搜索代码Ctrl + F
全屏模式F11
增大字号Ctrl + =
减小字号Ctrl + -
显示快捷键?