|
DataMuseum.dkPresents historical artifacts from the history of: CP/M |
This is an automatic "excavation" of a thematic subset of
See our Wiki for more about CP/M Excavated with: AutoArchaeologist - Free & Open Source Software. |
top - metrics - download
Length: 37120 (0x9100)
Types: RcTekst
Names: »42-I2507.WP«
└─⟦481be0aa0⟧ Bits:30008870 Diskette med 42-I og 44-RT dokumenter
└─⟦this⟧ »42-I2507.WP«
└─⟦d6fd29e8c⟧ Bits:30005864 Manualer - tekstfiler 42-I og 44-RT afdelingerne
└─⟦this⟧ »42-I2507.WP«
╱04002d440a0006000000000201503140000000000000000000000000000000000000000000000000050a0f19232d37414b555f69737d87ff04╱
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
┆82┆↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
┆06┆┆b0┆RC855 IBM 2780/3780 BSC Emulator.↲
↲
┆06┆┆b0┆Reference Manual.↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
┆81┆↲
↲
↲
↲
↲
↲
↲
↲
╞ ╞ A/S REGNECENTRALEN af 1979╞ ╞ April 1984↲
╞ ╞ Information Department╞ ╞ ╞ RCSL nr. 42-i2507↲
↲
════════════════════════════════════════════════════════════════════════
↓
╱04002d440a0006000000000201463100000000000000000000000000000000000000000000000000050a0f1923282d37414b555f69737dff04╱
╱04002d440a0006000000000201503140000000000000000000000000000000000000000000000000050a0f19232d37414b555f69737d87ff04╱
↓
↲
↲
↲
╞ ╞ Author :╞ Hans Markvard Nielsen↲
↲
╞ ╞ Keywords :╞ ┆84┆┆84┆RC855 Work Station, IBM 2780/3780 BSC Emula┄↓
┆19┆┆98┆┄┄tor, Reference data.↲
↲
╞ ╞ Abstract :╞ ┆84┆┆84┆┆84┆This manual describes all the RC855 IBM ↓
┆19┆┆98┆┄┄2780/3780 BSC Emula┄tor characteristics, espe┄↓
┆19┆┆98┆┄┄cially those formal criteria which do not ne┄↓
┆19┆┆98┆┄┄cessarily need to be known in order to operate ↓
┆19┆┆98┆┄┄the emulator i.e. fileformats, record hand┄↓
┆19┆┆98┆┄┄ling, communication line characteristics, com┄↓
┆19┆┆98┆┄┄mand files, parameters etc.↲
↲
↲
↲
↲
↲
↲
╞ ╞ ╞ ╞ (52 Printed pages)↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
════════════════════════════════════════════════════════════════════════
↓
↲
╱04002d4e0a000600000000020a4a31000000000000000000000000000000000000000000000000000e1318222c3136404a545e68727c86ff04╱
╱04002d440a0006000000000201463100000000000000000000000000000000000000000000000000050a0f1923282d37414b555f69737dff04╱
↓
↲
┆06┆i↲
↲
┆a1┆┆b0┆FOREWORD ↲
↲
↲
First edition: RCSL No 42-i1699. ↲
↲
Second edition: RCSL No 42-i2142. ↲
The second edition reflects new and extended facilities available ↓
with the emulator software package. Text which has been added or ↓
basically changed is indicated by a vertical lines in the left ↓
margin. ↲
↲
Torben G. Rasmussen and Henning Christensen ↲
A/S REGNECENTRALEN af 1979, October 1982 ↲
↲
↲
Third edition: RCSL 42-i2507↲
┆84┆The third edition reflects changes in the configuration which is ↓
now always a stand alone terminal with some background storage. ↓
This background storage may be 8", 5.25" or hard disk in the con┄↓
figurations supported by the RC855 work station.↲
↲
Hans Markvard Nielsen↲
A/S REGNECENTRALEN af 1979, April 1984.↲
↲
════════════════════════════════════════════════════════════════════════
↓
↲
┆06┆ii↲
↲
════════════════════════════════════════════════════════════════════════
↓
↲
┆06┆iii↲
↲
↲
┆a1┆┆b0┆TABLE OF CONTENTS┆05┆PAGE↲
↲
1.╞ INTRODUCTION ........................................... 1 ↲
╞ 1.1╞ Emulator Specifications ........................... 1 ↲
╞ 1.2╞ Emulator Parameters and Commands .................. 2 ↲
↲
2.╞ FILE FORMAT AND RECORD HANDLING ........................ 3 ↲
╞ 2.1╞ Transmission ...................................... 3 ↲
╞ ╞ 2.1.1 Non-transparent ............................ 3 ↲
╞ ╞ 2.1.2 Transparent ................................ 4 ↲
╞ 2.2╞ Receival .......................................... 4 ↲
╞ ╞ 2.2.1 Non-transparent Print-data ................. 4 ↲
╞ ╞ 2.2.2 Non-transparent Punch-data ................. 5 ↲
╞ ╞ 2.2.3 Transparent Print- and Punch-data .......... 5 ↲
↲
3.╞ SIGNON FILE ............................................ 7 ↲
↲
4.╞ CONFIGURATION FILE ..................................... 8 ↲
↲
5.╞ CHARACTER CODE SETS .................................... 9 ↲
╞ 5.1 Conversion Table Changes .......................... 9 ↲
╞ 5.2╞ CCW Code Definitions .............................. 10↲
↲
6.╞ COMMAND FILE ........................................... 12 ↲
↲
7.╞ MODEM SIGNALS .......................................... 15 ↲
╞ 7.1 V.24 .............................................. 15 ↲
╞ 7.2 X.21 .............................................. 16 ↲
↲
↲
┆a1┆┆b0┆APPENDICES: ↲
↲
A.╞ REFERENCES ............................................. 19 ↲
╞ A.1 Additional References ............................. 19 ↲
↲
B.╞ EXAMPLES OF HOST GENERATION PARAMETERS ................. 21 ↲
╞ B.1 JES2 .............................................. 21 ↲
╞ B.2 DOS/VS POWER/VS ................................... 21 ↲
↲
C.╞ CHARACTER CODE SETS .................................... 22 ↲
╞ C.1 US English EBCDIC ................................. 22 ↲
╞ C.2╞ US English ASCII .................................. 23 ↲
╞ C.3 UK English EBCDIC ................................. 24 ↲
╞ C.4 UK English ASCII .................................. 25 ↲
╞ C.5 German EBCDIC ..................................... 26 ↲
╞ C.6 German Alternate EBCDIC ........................... 27 ↲
╞ C.7 German ASCII ...................................... 28 ↲
╞ C.8 Swedish EBCDIC .................................... 29 ↲
╞ C.9 Swedish Alternate EBCDIC .......................... 30 ↲
╞ C.10 Swedish ASCII ..................................... 31 ↲
╞ C.11 Danish Standard EBCDIC ............................ 32 ↲
╞ C.12 Danish Standard Alternate EBCDIC .................. 33 ↲
╞ C.13 Danish Standard ASCII ............................. 34 ↲
╞ C.14 Danish Public Sector EBCDIC ....................... 35 ↲
╞ C.15 Danish Public Sector Alternate EBCDIC ............. 36 ↲
╞ C.16 Danish Public Sector ASCII ........................ 37 ↲
↲
════════════════════════════════════════════════════════════════════════
↓
↲
┆06┆iv↲
↲
↲
↲
┆a1┆┆b0┆TABLE OF CONTENTS (Continued)┆05┆PAGE↲
↲
↲
D.╞ LINE CONNECTIONS ....................................... 38 ↲
╞ D.1 Modem Connection .................................. 38 ↲
╞ ╞ D.1.1 V.24 Interface ............................. 38 ↲
╞ ╞ D.1.2 X.21 Interface ............................. 38 ↲
╞ D.2 Printer Connection ................................ 39 ↲
↲
╞ E. INDEX .............................................. 40 ↲
↲
↲
════════════════════════════════════════════════════════════════════════
┆14┆┆b3┆↲
┆14┆┆b3┆┆06┆- ┆0b┆ -↲
┆14┆┆b3┆↲
↲
┆b0┆┆a1┆1.╞ ╞ INTRODUCTION ↲
↲
╞ ╞ ┆84┆The RC855 IBM 2780/3780 BSC Emulator software package is ↓
┆19┆┆89┆┄┄a┄vailable for use with the RC855 Work Station. ↲
↲
╞ ╞ ┆84┆Operating the work station from a hardware point of view ↓
┆19┆┆89┆┄┄is covered by the RC855 Operating Guide; ref. 1. ↲
↲
╞ ╞ ┆84┆Operation of the RC855 with CP/M is introduced by the ↓
┆19┆┆89┆┄┄RC855 WorkStation, User's Guide; ref 2. ↲
↲
╞ ╞ ┆84┆Loading of the emulator is explained in the RC855 IBM ↓
┆19┆┆89┆┄┄2780/3780BSC Emulator, Installation Guide; ref. 3. ↲
↲
╞ ╞ ┆84┆Operation of the emulator is explained in the RC855 IBM ↓
┆19┆┆89┆┄┄2780/3780BSC Emulator, Operating Guide; ref. 4. ↲
↲
╞ ╞ ┆84┆The present guide provides basic reference data of the ↓
┆19┆┆89┆┄┄emula┄tor. ↲
↲
↲
┆a1┆┆b0┆1.1╞ ╞ Emulator Specifications ↲
↲
╞ ╞ ┆84┆Communication link :╞ V.24 : ┆84┆Point to point (leased) ↓
┆19┆┆a9┆┄┄or switched (dial up) ↓
┆19┆┆a9┆┄┄connec┄┄tion. Often refer┄↓
┆19┆┆a9┆┄┄red to as Datel service. ↲
╞ ╞ ╞ ╞ ╞ ╞ ╞ X.21 : ┆84┆Connection through an ↓
┆19┆┆a9┆┄┄X.21 network. Mostly re┄↓
┆19┆┆a9┆┄┄ferred to as Datex ser┄↓
┆19┆┆a9┆┄┄vice. ↲
↲
╞ ╞ Communication types :╞ V.24 : ┆84┆┆84┆Synchroneous modems, ↓
┆19┆┆a9┆┄┄half or full duplex.↲
╞ ╞ ╞ ╞ ╞ ╞ ╞ X.21 : ┆84┆Synchroneous X.21 DCE. ↲
↲
╞ ╞ Communication mode : ╞ ╞ ╞ Half-duplex. ↲
↲
╞ ╞ Data rates ╞ ╞ :╞ ╞ ╞ Up to 9600 bps. ↲
↲
╞ ╞ Line protocol ╞ ╞ :╞ ╞ ╞ ┆84┆┆84┆Binary Synchroneous Com┄↓
┆19┆┆a9┆┄┄muni┄cation (BSC) proce┄↓
┆19┆┆a9┆┄┄dures; see references in ↓
┆19┆┆a9┆┄┄appendix A.1. ↲
↲
╞ ╞ Line buffer size ╞ : ╞ 2780 : 420 bytes↲
╞ ╞ ╞ ╞ ╞ ╞ ╞ 3780 : 530 bytes ↲
↲
╞ ╞ Transmission code ╞ : ╞ ╞ ╞ EBCDIC. ↲
┆8c┆┄┆b2┆↓
┆0e┆↓
↲
╞ ╞ Options supported ╞ :╞ 2780 : ┆84┆Multiple record trans┄┄↓
┆19┆┆a9┆┄┄mission ↲
↲
╞ ╞ ╞ ╞ ╞ ╞ ╞ 3780 : ┆84┆Space compression/expan┄↓
┆19┆┆a9┆┄┄sion ↲
↲
╞ ╞ ╞ ╞ ╞ ╞ 2780/3780 : EBCDIC transparency.↲
╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ┆84┆Printer horizontal for┄↓
┆19┆┆a9┆┄┄mat control (HT).↲
╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ┆84┆Printer carriage control ↓
┆19┆┆a9┆┄┄de┄coding (CCW).↲
╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ Component selection.↲
╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ┆84┆Terminal identification ↓
┆19┆┆a9┆┄┄(ID).↲
┆0f┆↓
↲
╞ ╞ ┆84┆Examples of host generation parameters are found in ap┄↓
┆19┆┆89┆┄┄pendix B. ↲
↲
↲
┆b0┆┆a1┆1.2╞ ╞ Emulator Parameters and Commands ↲
↲
╞ ╞ ┆84┆The execution of the emulator functions is controlled by ↓
┆19┆┆89┆┄┄a set of parameters and a set of commands (function ↓
┆19┆┆89┆┄┄keys). A detailed description of these is found in ref. ↓
┆19┆┆89┆┄┄4.↲
↲
╞ ╞ ┆84┆Initial values of the parameters can be assigned when ↓
┆19┆┆89┆┄┄ap┄ply┄ing the configuration file, otherwise a set of de┄↓
┆19┆┆89┆┄┄fault values is used by the emulator.↲
↲
════════════════════════════════════════════════════════════════════════
↓
↲
↲
┆a1┆┆b0┆2.╞ ╞ File format and record handling ↲
↲
↲
┆b0┆┆a1┆2.1╞ ╞ Transmission ↲
↲
╞ ╞ ┆84┆Data can be transmitted in two modes : ↲
↲
╞ ╞ ╞ non-transparent ↲
╞ ╞ ╞ transparent ↲
↲
╞ ╞ ┆84┆In either mode, the transmission of data is from CP/M ↓
┆19┆┆89┆┄┄files on a diskette. However, the record handling dif┄┄↓
┆19┆┆89┆┄┄fers according to the applied mode. These modes are se┄↓
┆19┆┆89┆┄┄lect┄able by the con┄figuration file parameter TRANSPA┄REN┄↓
┆19┆┆89┆┄┄CY as well as by the file name specifications /NT and /T ↓
┆19┆┆89┆┄┄- see ref. 4 : ↲
↲
↲
┆b0┆┆a1┆2.1.1╞ Non-transparent ↲
↲
╞ ╞ ┆84┆Each record is converted from ASCII to EBCDIC and trans┄↓
┆19┆┆89┆┄┄mitted as 1 record of 80 bytes. A record on the diskette ↓
┆19┆┆89┆┄┄is termina┄ted by CR, NL, FF, SUB or any possible combi┄↓
┆19┆┆89┆┄┄nation of these 4 characters. The termination charac┄┄↓
┆19┆┆89┆┄┄ter(s) is(are) neither conver┄ted nor transmitted.↲
↲
╞ ╞ ┆84┆If the termination characters contain more than one CR, ↓
┆19┆┆89┆┄┄an empty record (all spaces) is transmitted for each ad┄↓
┆19┆┆89┆┄┄ditional CR. Examples: ↲
↲
╞ ╞ ┆a1┆CP/M file on diskette ╞ ╞ ╞ ╞ ╞ Transmission↲
╞ ╞ 1) ↲
╞ ╞ <record1><CR><NL> ╞ ╞ ╞ ╞ ╞ ╞ <record1> ↲
╞ ╞ <record2><CR><NL><SUB> ╞ ╞ ╞ ╞ ╞ <record2> ↲
↲
╞ ╞ 2) ↲
╞ ╞ <record1><CR><NL><CR><NL>╞ ╞ ╞ ╞ <record1>,↲
╞ ╞ <record2><CR><NL><FF><FF><SUB> ╞ ╞ ╞ <empty record>,↲
╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ <record2>↲
↲
╞ ╞ ┆84┆Record handling further depends on the record size and ↓
┆19┆┆89┆┄┄the applied line procedure as follows :↲
↲
╞ ╞ record > 80 bytes :╞ 2780/3780 :╞ ┆84┆split into a number of ↓
┆19┆┆a9┆┄┄80-bytes records and ↓
┆19┆┆a9┆┄┄(possibly) a last record ↓
┆19┆┆a9┆┄┄of less than 80 bytes, ↓
┆19┆┆a9┆┄┄which is then treated ↓
┆19┆┆a9┆┄┄accordingly. ↲
↲
┆8c┆┄┆b4┆↓
╞ ╞ record < 80 bytes : 2780 ╞ : ┆84┆terminated with an EM ↓
┆19┆┆a9┆┄┄charac┄ter.↲
╞ ╞ ╞ ╞ ╞ ╞ 3780╞ ╞ : filled with spaces. ↲
↲
╞ ╞ ┆84┆The transmission is terminated when a SUB-character ↓
┆19┆┆89┆┄┄(1A┆82┆Hex┆81┆) or physical end of file is met. ↲
↲
╞ ╞ This mode is normally used when transmitting text files. ↲
↲
↲
┆a1┆┆b0┆2.1.2╞ Transparent ↲
↲
╞ ╞ ┆84┆All data (including CR, NL, FF and SUB) are transmitted ↓
┆19┆┆89┆┄┄with┄out conversion. The data is split into records of 80 ↓
┆19┆┆89┆┄┄bytes. The transmission is terminated at physical end of ↓
┆19┆┆89┆┄┄file.↲
↲
╞ ╞ ┆84┆This mode is normally used when transmitting binary ↓
┆19┆┆89┆┄┄files. ↲
↲
┆b0┆┆a1┆2.2╞ ╞ Receival ↲
↲
╞ ╞ ┆84┆Data received is classified as follows and given dif┄↓
┆19┆┆89┆┄┄ferent treatment accordingly: ↲
↲
╞ ╞ ╞ non-transparent, print-data ↲
╞ ╞ ╞ non-transparent, punch-data ↲
╞ ╞ ╞ transparent, print- or punch-data ↲
↲
╞ ╞ ┆84┆Non-transparent data is always converted from EBCDIC to ↓
┆19┆┆89┆┄┄ASCII. ↲
↲
╞ ╞ Transparent data is never converted.↲
↲
╞ ╞ ┆84┆The received data is written in CP/M files on a diskette ↓
┆19┆┆89┆┄┄or directly on the printer (determined by the configura┄↓
┆19┆┆89┆┄┄tion file parameters PRINT-DEV/PUNCH-DEV). If written on ↓
┆19┆┆89┆┄┄diskette in a CP/M file, writing takes place as follows: ↲
↲
╞ ╞ a) ┆84┆file does not exist - file is created and writing ↓
┆19┆┆8c┆┄┄starts from the beginning of the file. ↲
↲
╞ ╞ b) file exists - writing starts as follows: ↲
↲
╞ ╞ ╞ non-continous file╞ : ┆84┆from the beginning of the ↓
┆19┆┆a4┆┄┄file. ↲
╞ ╞ ╞ continous file ╞ : ┆84┆┆84┆from the end of the previous┄↓
┆19┆┆a4┆┄┄ly written part of the file. ↲
↲
↲
┆b0┆┆a1┆2.2.1╞ Non-transparent Print-data ↲
↲
╞ ╞ ┆84┆One transmission-line record is written as one record on ↓
┆19┆┆89┆┄┄the print device. If the 2 first characters constitute ↓
┆19┆┆89┆┄┄an ESC-sequence (CCW to the printer) this is interpreted ↓
┆19┆┆89┆┄┄as follows: ↲
↲
┆8c┆┄┆b9┆↓
╞ ╞ ╞ ESC M ╞ space 0 lines╞ ╞ ╞ CR ↲
╞ ╞ ╞ ESC / ╞ space 1 line ╞ ╞ ╞ CR.NL ↲
╞ ╞ ╞ ESC S ╞ space 2 lines╞ ╞ ╞ CR.NL.NL ↲
╞ ╞ ╞ ESC T ╞ space 3 lines╞ ╞ ╞ CR.NL.NL.NL ↲
╞ ╞ ╞ ESC A ╞ skip to channel 1╞ ↲
╞ ╞ ╞ ESC B╞ skip to channel 2╞ ↲
╞ ╞ ╞ :↲
╞ ╞ ╞ :↲
╞ ╞ ╞ :↲
╞ ╞ ╞ ESC L╞ skip to channel 12╞ ↲
╞ ╞ ╞ no ESC╞ space 1 line ╞ ╞ ╞ CR.NL ↲
↲
╞ ╞ ┆84┆The ESC-sequence is not written on the print-device, but ↓
┆19┆┆89┆┄┄the record is terminated with a sequence of CR-NL-VT or ↓
┆19┆┆89┆┄┄FF (in the following called the termination characters) ↓
┆19┆┆89┆┄┄in accor┄dance with the interpretation of the ESC-se┄↓
┆19┆┆89┆┄┄quence. ↲
↲
╞ ╞ ┆84┆If the print device is a CP/M file, a SUB character ↓
┆19┆┆89┆┄┄(1A┆82┆Hex┆81┆) is inserted after the last record. ↲
↲
╞ ╞ ┆84┆If the print-device is a CP/M file and the configuration ↓
┆19┆┆89┆┄┄file parameter PRINT-SIZE is different from zero, the ↓
┆19┆┆89┆┄┄record is padded with spaces/truncated to the given ↓
┆19┆┆89┆┄┄print-size. Pad┄ding/truncation is done immediately be┄↓
┆19┆┆89┆┄┄fore the termination characters. ↲
↲
↲
┆a1┆┆b0┆2.2.2╞ Non-transparent Punch-data ↲
↲
╞ ╞ ┆84┆1 transmission-line record is written as 1 record on the ↓
┆19┆┆89┆┄┄punch device. After each record CR-NL are inserted as ↓
┆19┆┆89┆┄┄ter┄mi┄nation characters. ↲
↲
╞ ╞ ┆84┆If the punch-device is a CP/M file, a SUB-char (1A┆82┆Hex┆81┆) ↓
┆19┆┆89┆┄┄is in┄serted after the last record. ↲
↲
╞ ╞ ┆84┆If the punch-device is a CP/M file and the configuration ↓
┆19┆┆89┆┄┄file parameter PUNCH-SIZE is different from zero, the ↓
┆19┆┆89┆┄┄record is padded with spaces/truncated to the given ↓
┆19┆┆89┆┄┄punch-size. Pad┄ding/truncation is done immediately be┄↓
┆19┆┆89┆┄┄fore the termination characters. ↲
↲
↲
┆a1┆┆b0┆2.2.3╞ Transparent Print- and Punch-data ↲
↲
╞ ╞ ┆84┆Data is written on the print-/punch-device exactly as it ↓
┆19┆┆89┆┄┄is received from the linie. No termination characters ↓
┆19┆┆89┆┄┄are inser┄ted. The last physical block on the CP/M file ↓
┆19┆┆89┆┄┄is padded out with binary zeroes.↲
↲
┆8c┆┄┆b3┆↓
╞ ╞ ┆84┆Print-/punch-device should be a CP/M file, because the ↓
┆19┆┆89┆┄┄trans┄parent data is normally binary data which makes no ↓
┆19┆┆89┆┄┄sense on a printer. ↲
↲
════════════════════════════════════════════════════════════════════════
↓
↲
┆a1┆┆b0┆3.╞ ╞ Signon file ↲
↲
╞ ╞ ┆84┆The signon file is a CP/M file with the name S2780.TXT ↓
┆19┆┆89┆┄┄or S3780.TXT, respectively. After loading the emulator, ↓
┆19┆┆89┆┄┄the file will be transmitted if it exists on the disket┄↓
┆19┆┆89┆┄┄te mounted in drive A. The file contains the signon-re┄↓
┆19┆┆89┆┄┄cord. ↲
↲
╞ ╞ The file must have the following format: ↲
↲
╞ ╞ ╞ <signon-record><CR><NL> ↲
╞ ╞ ╞ <SUB> ↲
↲
╞ ╞ ┆84┆The file can be created and written with the CP/M editor ↓
┆19┆┆89┆┄┄(or any other editor).↲
↲
╞ ╞ ┆84┆For a description of the signon-record, see the documen┄↓
┆19┆┆89┆┄┄tation covering the requirements of the host computer. ↲
↲
╞ ╞ ┆84┆If the host computer requires that the signon-record is ↓
┆19┆┆89┆┄┄transmitted in transparent mode, it can be achieved in ↓
┆19┆┆89┆┄┄two ways: ↲
↲
╞ ╞ ╞ 1) ┆84┆Set the configuration parameter TRANSPARENCY to ↓
┆19┆┆91┆┄┄ON. ↲
↲
╞ ╞ ╞ ┆84┆Send the signon-record as a command from the ↓
┆19┆┆91┆┄┄console (PA2 or PA3). ↲
↲
╞ ╞ ╞ ┆84┆Console commands are always converted from ASCII ↓
┆19┆┆91┆┄┄to EBCDIC independent of TRANSPARENCY setting. ↲
↲
╞ ╞ ╞ 2) ┆84┆Set the configuration parameter TRANSPARENCY to ↓
┆19┆┆91┆┄┄ON. ↲
↲
╞ ╞ ╞ ┆84┆Send the signon-record from a CP/M diskette file ↓
┆19┆┆91┆┄┄(PA1). ↲
↲
╞ ╞ ╞ ┆84┆Data files are not converted when transmitted in ↓
┆19┆┆91┆┄┄transparent mode and so the contents of the CP/M ↓
┆19┆┆91┆┄┄file in this case must be in EBCDIC code. ↲
↲
════════════════════════════════════════════════════════════════════════
↓
↲
┆a1┆┆b0┆4.╞ ╞ Configuration file ↲
↲
╞ ╞ ┆84┆The configuration file is a CP/M file with the name ↓
┆19┆┆89┆┄┄C2780.TXT or C3780.TXT, respectively. After loading the ↓
┆19┆┆89┆┄┄emulator, the file will be read if it exists on the dis┄↓
┆19┆┆89┆┄┄kette mounted in drive A. The file contains the configu┄↓
┆19┆┆89┆┄┄ration parameters; see ref 4. ↲
↲
╞ ╞ The file must have the format: ↲
↲
╞ ╞ ╞ <parameter-1>=<VALUE><CR><NL> ↲
╞ ╞ ╞ <parameter-2>=<VALUE><CR><NL> ↲
╞ ╞ ╞ . ↲
╞ ╞ ╞ . ↲
╞ ╞ ╞ . ↲
╞ ╞ ╞ <parameter-n>=<VALUE><CR><NL> ↲
╞ ╞ ╞ <SUB> ↲
↲
╞ ╞ ┆84┆The file can be created and written with the CP/M editor ↓
┆19┆┆89┆┄┄(or any other editor).↲
╞ ╞ ┆84┆The configuration file can be extended in order to spe┄↓
┆19┆┆89┆┄┄cify conversion table changes; see section 5.1. ↲
↲
╞ ╞ Example of configuration file: ↲
↲
╞ ╞ ╞ PUNCH-DEV=B:PUNCH.TXT<CR><NL> ↲
╞ ╞ ╞ PRINT-DEV=PRINT.TXT<CR><NL> ↲
╞ ╞ ╞ RECEIVE-ID=<CR><NL> ↲
╞ ╞ ╞ TRANSMIT-ID=RC01<CR><NL> ↲
╞ ╞ ╞ WAIT-TIME=3<CR><NL> ↲
╞ ╞ ╞ <SUB> ↲
↲
════════════════════════════════════════════════════════════════════════
↓
↲
┆a1┆┆b0┆5.╞ ╞ Character code sets ↲
↲
╞ ╞ ┆84┆The RC855 IBM 2780/3780 BSC Emulator has a number of na┄↓
┆19┆┆89┆┄┄tional versions. For each national version there is two ↓
┆19┆┆89┆┄┄code sets: ↲
↲
╞ ╞ 1) ┆84┆The EBCDIC code set used for communication with the ↓
┆19┆┆8c┆┄┄host computer, including BSC line control characters ↓
┆19┆┆8c┆┄┄and prin┄ter control characters. ↲
↲
╞ ╞ 2) ┆84┆The ASCII code set is used for data on diskettes and ↓
┆19┆┆8c┆┄┄prin┄ters. The ASCII code includes the four control ↓
┆19┆┆8c┆┄┄charac┄ters CR, NL, FF and VT, which all printers must ↓
┆19┆┆8c┆┄┄support. ↲
↲
╞ ╞ ┆84┆Detailed descriptions of EBCDIC- and ASCII-character ↓
┆19┆┆89┆┄┄sets for all national versions are found in appendix C. ↲
↲
╞ ╞ ┆84┆For some of the national versions an alternate EBCDIC ↓
┆19┆┆89┆┄┄code set exists. The RC855 configuration parameter CS ↓
┆19┆┆89┆┄┄(Character Set) is used to select which EBCDIC code set ↓
┆19┆┆89┆┄┄to use: ↲
↲
╞ ╞ CS = 0╞ EBCDIC code set is used ↲
╞ ╞ CS = 1╞ Alternate EBCDIC code set is used ↲
↲
╞ ╞ ┆84┆Appendix C holds information about which EBCDIC code set ↓
┆19┆┆89┆┄┄is commonly used when running IBM 2780/3780. The RC855 ↓
┆19┆┆89┆┄┄configuration parameters are described in ref. 2. ↲
↲
╞ ╞ ┆84┆With a few exceptions, each national character set con┄↓
┆19┆┆89┆┄┄tains 95 graphic characters, including the space (SP) ↓
┆19┆┆89┆┄┄character, with EBCDIC codes de┄fined for all 95 charac┄↓
┆19┆┆89┆┄┄ters. ↲
↲
↲
┆a1┆┆b0┆5.1╞ ╞ Conversion Table Changes ↲
↲
╞ ╞ ┆84┆It is possible to make changes in the EBCDIC character ↓
┆19┆┆89┆┄┄set. These changes are specified by adding a number of ↓
┆19┆┆89┆┄┄records to the configuration file (after the last para┄↓
┆19┆┆89┆┄┄meter assign┄ment). ↲
↲
╞ ╞ The records must have the following format : ↲
↲
╞ ╞ ╞ CONVERSION=<CR><NL> ↲
╞ ╞ ╞ <ASCII VALUE>,<EBCDIC VALUE><CR><NL> ↲
╞ ╞ ╞ <ASCII VALUE>,<EBCDIC VALUE><CR><NL> ↲
╞ ╞ ╞ . ↲
╞ ╞ ╞ . ↲
╞ ╞ ╞ . ↲
╞ ╞ ╞ <ASCII VALUE>,<EBCDIC VALUE><CR><NL> ↲
↲
↲
╞ ╞ <ASCII VALUE> must be in the range 0-127. ↲
┆8c┆┄┆b8┆↓
╞ ╞ <EBCDIC VALUE> must be in the range 0-255. ↲
↲
╞ ╞ ┆84┆When <ASCII VALUE> should have been transmitted, it is ↓
┆19┆┆89┆┄┄con┄verted to <EBCDIC VALUE> before transmission. ↲
↲
╞ ╞ ┆84┆When <EBCDIC VALUE> is received, it is converted to ↓
┆19┆┆89┆┄┄<ASCII VALUE> before writing on the diskette/printer. ↲
↲
╞ ╞ ┆84┆Example of a configuration file with conversion table ↓
┆19┆┆89┆┄┄chan┄ges: ↲
↲
╞ ╞ ╞ . ↲
╞ ╞ ╞ . ↲
╞ ╞ ╞ . ↲
╞ ╞ ╞ WAIT-TIME=3<CR><NL> ↲
╞ ╞ ╞ CONVERSION=<CR><NL> ↲
╞ ╞ ╞ 65,194<CR><NL> ↲
╞ ╞ ╞ 66,193<CR><NL> ↲
╞ ╞ ╞ 42,108<CR><NL> ↲
╞ ╞ ╞ 42,92<CR><NL> ↲
╞ ╞ ╞ <SUB> ↲
↲
╞ ╞ ┆84┆The following changes have been made in the character ↓
┆19┆┆89┆┄┄code sets : ↲
↲
╞ ╞ ┆a1┆ASCII╞ EBCDIC╞ ╞ ╞ ASCII╞ EBCDIC ↲
╞ ╞ ┆a1┆A (65)╞ ╞ ┆e1┆╞ ╞ ╞ ┆a1┆╞ ╞ ╞ B (194) ↲
╞ ╞ ┆a1┆╞ ╞ B (194)┆e1┆╞ ╞ ╞ ┆a1┆A (65) ╞ ╞ ↲
╞ ╞ ┆a1┆B (66)╞ ╞ ┆e1┆╞ ╞ ╞ ┆a1┆╞ ╞ ╞ A (193) ↲
╞ ╞ ┆a1┆╞ ╞ A (193)┆e1┆╞ is╞ ╞ ┆a1┆B (66) ╞ ╞ ↲
╞ ╞ ┆a1┆* (42)╞ ╞ ┆e1┆ converted╞ ┆a1┆╞ ╞ ╞ % (108) ↲
╞ ╞ ┆a1┆╞ ╞ % (108)┆e1┆ to╞ ╞ ┆a1┆* (42) ╞ ╞ ↲
╞ ╞ ┆a1┆* (42)╞ ╞ ┆e1┆╞ ╞ ╞ ┆a1┆╞ ╞ ╞ * (92) ↲
╞ ╞ ┆a1┆╞ ╞ * (92) ┆e1┆╞ ╞ ╞ ┆a1┆* (42) ╞ ╞ ↲
↲
╞ ╞ ┆84┆The four first lines means that A and B have been ↓
┆19┆┆89┆┄┄switched in the EBCDIC character code set. ↲
↲
╞ ╞ ┆84┆The four last lines means that % is changed to * in the ↓
┆19┆┆89┆┄┄EBCDIC character code set. ↲
↲
↲
┆a1┆┆b0┆5.2╞ ╞ CCW Code definitions ↲
↲
↲
╞ ╞ ┆84┆The user may specify sequences of up to eight characters ↓
┆19┆┆89┆┄┄to be sent to the printer upon reception of an ESC-↓
┆19┆┆89┆┄┄sequence, i.e. ESC followed by one of the letters B ↓
┆19┆┆89┆┄┄Through L. The default values can be seen from the table ↓
┆19┆┆89┆┄┄below : ↲
↲
┆8c┆┄┆b3┆↓
┆0e┆↓
↲
╞ ╞ ┆a1┆ESC-seq.┆e1┆╞ ┆a1┆Meaning┆e1┆┆a1┆ ┆e1┆╞ ┆a1┆Output to printer↲
↲
╞ ╞ ESC-M╞ space 0 lines╞ ╞ <cr>↲
╞ ╞ ESC-/╞ space 1 line╞ ╞ <cr>,<lf>↲
╞ ╞ ESC-S╞ space 2 lines╞ ╞ <cr>,<lf>,<lf>↲
╞ ╞ ESC-T╞ space 3 lines╞ ╞ <cr>,<lf>,<lf>,<lf>↲
╞ ╞ ESC-A╞ skip to channel 1╞ <cr>,<ff>↲
╞ ╞ ESC-B╞ skip to channel 2╞ <cr>,<vt>↲
╞ ╞ ESC-C╞ skip to channel 3╞ <cr>,<vt>↲
╞ ╞ ESC-D╞ skip to channel 4╞ <cr>,<vt>↲
╞ ╞ ESC-E╞ skip to channel 5╞ <cr>,<vt>↲
╞ ╞ ESC-F╞ skip to channel 6╞ <cr>,<vt>↲
╞ ╞ ESC-G╞ skip to channel 7╞ <cr>,<vt>↲
╞ ╞ ESC-H╞ skip to channel 8╞ <cr>,<vt>↲
╞ ╞ ESC-I╞ skip to channel 9╞ <cr>,<vt>↲
╞ ╞ ESC-J╞ skip to channel 10╞ <cr>,<vt>↲
╞ ╞ ESC-K╞ skip to channel 11╞ <cr>,<vt>↲
╞ ╞ ESC-L╞ skip to channel 12╞ <cr>,<vt>↲
┆0f┆↓
↲
╞ ╞ ┆84┆As can be seen from this table, skips to channel 2 to 12 ↓
┆19┆┆89┆┄┄are not supported unless the user specifies appropriate ↓
┆19┆┆89┆┄┄character sequences. Such sequences must be specified in ↓
┆19┆┆89┆┄┄the configuration file, and must have the following ↓
┆19┆┆89┆┄┄format :↲
↲
↲
↲
╞ ╞ CCW=<cr><lf>↲
╞ ╞ B=<character sequence><cr><lf>↲
╞ ╞ C=<character sequence><cr><lf>↲
╞ ╞ D=<character sequence><cr><lf>↲
╞ ╞ :↲
╞ ╞ :↲
╞ ╞ :↲
╞ ╞ L=<character sequence><cr><lf>↲
╞ ╞ <sub>↲
↲
↲
╞ ╞ ┆84┆The character sequence may consist of up to eight ↓
┆19┆┆89┆┄┄characters, they must be specified in decimal values and ↓
┆19┆┆89┆┄┄must be separated by commas.↲
↲
↲
════════════════════════════════════════════════════════════════════════
↓
↲
┆a1┆┆b0┆6.╞ ╞ Command file ↲
↲
╞ ╞ ┆84┆A command file is a CP/M file which contains file names ↓
┆19┆┆89┆┄┄of files to be transmitted and special commands to con┄↓
┆19┆┆89┆┄┄trol the transmission. ↲
↲
╞ ╞ ┆84┆A command file may contain up to 32 file names/commands, ↓
┆19┆┆89┆┄┄but ┆a1┆must not┆e1┆ exceed 512 bytes.↲
↲
╞ ╞ The command file has the following format: ↲
↲
╞ ╞ ╞ <file name or special command 1><CR><NL> ↲
╞ ╞ ╞ <file name or special command 2><CR><NL> ↲
╞ ╞ ╞ . ↲
╞ ╞ ╞ . ↲
╞ ╞ ╞ . ↲
╞ ╞ ╞ <file name or special command n><CR><NL> ↲
╞ ╞ ╞ <SUB> ↲
↲
╞ ╞ ┆84┆The file can be created and written with the CP/M-editor ↓
┆19┆┆89┆┄┄(or any other editor).↲
╞ ╞ ┆84┆For a description of file names, see ref. 4. ↲
↲
╞ ╞ Special commands are: ↲
↲
╞ ╞ TERM╞ ╞ ┆84┆When the last block in the file, given just ↓
┆19┆┆93┆┄┄before this command, is transmitted, it is ↓
┆19┆┆93┆┄┄terminated by ETX instead of ETB (normally on┄↓
┆19┆┆93┆┄┄ly the last block in the last file is termi┄na┄↓
┆19┆┆93┆┄┄ted by ETX). ↲
↲
╞ ╞ ┆84┆This command must be given, before one of the below men ↓
┆19┆┆89┆┄┄tioned commands can be given. If the receiving system ↓
┆19┆┆89┆┄┄uses ETX to detect end of file (non-IBM systems), it can ↓
┆19┆┆89┆┄┄be used to separate files,. ↲
↲
╞ ╞ DISC╞ ╞ ┆84┆Disconnect the line (send DLE-EOT and - if ↓
┆19┆┆93┆┄┄V.24: remove DTR (Data Terminal Ready) - if ↓
┆19┆┆93┆┄┄X.21: clear the connection). ↲
↲
╞ ╞ ┆84┆This command is only allowed after a TERM-command. It ↓
┆19┆┆89┆┄┄must be given if the following command is wanted.↲
↲
╞ ╞ EXIT╞ ╞ ┆84┆A soft reset of the RC855 is made (cold boot ↓
┆19┆┆93┆┄┄of CP/M). ↲
↲
╞ ╞ This command is only allowed after a DISC-command. ↲
↲
┆8c┆┄┆b1┆↓
┆0e┆↓
↲
╞ ╞ Examples of command files: ↲
↲
╞ ╞ 1) JCL1.TXT ↲
╞ ╞ B:DATA.TXT/T ↲
╞ ╞ JCL2.TXT ↲
╞ ╞ TERM ↲
╞ ╞ A:JCL1.TXT/NT ↲
╞ ╞ B:DATA.TXT/T ↲
╞ ╞ A:JCL2.TXT/NT ↲
┆0f┆↓
↲
╞ ╞ The following will happen: ↲
↲
╞ ╞ ┆84┆File JCL1.TXT on drive A will be transmitted in mode ac┄↓
┆19┆┆89┆┄┄cor┄ding to the configuration parameter TRANSPARENCY. ↲
↲
╞ ╞ ┆84┆File DATA.TXT on drive B will be transmitted in transpa┄↓
┆19┆┆89┆┄┄rent mode.↲
↲
╞ ╞ ┆84┆File JCL2.TXT on drive A will be transmitted in mode ac┄↓
┆19┆┆89┆┄┄cor┄ding to the configuration parameter TRANSPARENCY, the ↓
┆19┆┆89┆┄┄last block will be terminated by ETX. ↲
↲
╞ ╞ ┆84┆File JCL1.TXT on drive A will be transmitted in non-↓
┆19┆┆89┆┄┄trans┄parent mode. ↲
↲
╞ ╞ ┆84┆File DATA.TXT on drive B will be transmitted in transpa┄↓
┆19┆┆89┆┄┄rent mode.↲
↲
╞ ╞ ┆84┆File JCL2.TXT on drive A will be transmitted in non-↓
┆19┆┆89┆┄┄transpa┄rent mode. The last block will be terminated by ↓
┆19┆┆89┆┄┄ETX (because it is the last file to be transmitted). ↲
↲
↲
╞ ╞ 2) SIGNOFF.TXT/NT ↲
╞ ╞ TERM ↲
╞ ╞ DISC ↲
╞ ╞ EXIT ↲
↲
╞ ╞ The following will happen: ↲
↲
╞ ╞ ┆84┆File SIGNOFF.TXT on drive A will be transmitted in non-↓
┆19┆┆89┆┄┄trans┄parent mode, the last block will be terminated by ↓
┆19┆┆89┆┄┄ETX. ↲
↲
╞ ╞ The line is disconnected. ↲
↲
╞ ╞ A soft reset (CP/M cold boot) is made. ↲
↲
╞ ╞ ┆84┆In this example the contents of the file SIGNOFF.TXT ↓
┆19┆┆89┆┄┄most usually would be a signoff-record. For details on ↓
┆8c┆┄┆b3┆↓
┆19┆┆89┆┄┄sign-off records, see the documentation covering the ↓
┆19┆┆89┆┄┄host computer.↲
↲
════════════════════════════════════════════════════════════════════════
↓
↲
┆a1┆┆b0┆7.╞ ╞ Modem Signals ↲
↲
↲
┆a1┆┆b0┆7.1╞ ╞ V.24 ↲
↲
╞ ╞ ┆84┆The modem signals are used according to the CCITT V.24 ↓
┆19┆┆89┆┄┄recom┄mendation. The modem signals used by the emulator ↓
┆19┆┆89┆┄┄are shown in appendix D.1.1. ↲
↲
╞ ╞ ┆84┆Below is explained, how the emulator uses the signal Da┄↓
┆19┆┆89┆┄┄ta Terminal Ready (108).↲
↲
╞ ╞ ┆84┆Data Terminal Ready (DTR) is set by the emulator: ↲
↲
╞ ╞ 1) ┆84┆first time the line is to be used for transmission/re ↓
┆19┆┆8c┆┄┄ceival, or ↲
↲
╞ ╞ 2) ┆84┆if the function 'connect line' (PF13) is selected. ↲
↲
╞ ╞ ┆84┆DTR remains set until removed by the emulator due to one ↓
┆19┆┆89┆┄┄of the following events: ↲
↲
╞ ╞ 1) DLE-EOT is received from the host. ↲
↲
╞ ╞ 2) Data Set Ready (107) from the modem is off. ↲
↲
╞ ╞ 3) ┆84┆The function 'disconnect line' (PF12 or DISC in a com ↓
┆19┆┆8c┆┄┄mand file) is selected. ↲
↲
╞ ╞ ┆84┆The functions directly affecting the DTR signal work as ↓
┆19┆┆89┆┄┄fol┄lows: ↲
↲
╞ ╞ Connect line (PF13): ↲
↲
╞ ╞ ╞ ┆84┆On selection the emulator sets DTR on and waits for ↓
┆19┆┆8e┆┄┄DSR from the modem to be set on. ↲
↲
╞ ╞ Disconnect line (PF12): ↲
↲
╞ ╞ ╞ ┆84┆On selection the emulator transmits the controlse┄↓
┆19┆┆8e┆┄┄quence DLE-EOT and then removes DTR. ↲
↲
╞ ╞ Wait connection (PF14) : ↲
↲
╞ ╞ ╞ ┆84┆On selection the emulator waits for the signal Cal┄↓
┆19┆┆8e┆┄┄ling Indicator (125) from the modem to be set on. ↓
┆19┆┆8e┆┄┄Then the emulator sets DTR on and waits for DSR ↓
┆19┆┆8e┆┄┄from the modem to be set on. ↲
┆8c┆┄┆b1┆↓
┆0e┆↓
↲
┆a1┆┆b0┆7.2╞ ╞ X.21 ↲
↲
╞ ╞ ┆84┆The modem signals are used according to the CCITT X.21 ↓
┆19┆┆89┆┄┄recom┄mendation. The modem signals used by the emulator ↓
┆19┆┆89┆┄┄is shown in appendix D.1.2. ↲
┆0f┆↓
↲
╞ ╞ ┆84┆Below is explained how the emulator establishes/clears ↓
┆19┆┆89┆┄┄the X.21 connection. ↲
↲
╞ ╞ ┆84┆By making a call to the Datex-number specified in the ↓
┆19┆┆89┆┄┄confi┄guration file parameter CALL-ID, the emulator e┄↓
┆19┆┆89┆┄┄stablishes the X.21 connection: ↲
↲
╞ ╞ ╞ 1) ┆84┆first time the line is to be used for transmis┄↓
┆19┆┆91┆┄┄sion/receival, or ↲
↲
╞ ╞ ╞ 2) ┆84┆if the function 'connect line' (PF13) is selec┄↓
┆19┆┆91┆┄┄ted. ↲
↲
╞ ╞ ┆84┆The X.21 connection is cleared by the emulator due to ↓
┆19┆┆89┆┄┄one of the following events: ↲
↲
╞ ╞ ╞ 1) DLE-EOT is received from the host. ↲
↲
╞ ╞ ╞ 2) ┆84┆The modem signal connection is cleared (by the ↓
┆19┆┆91┆┄┄net┄work or the host) ↲
↲
╞ ╞ ╞ 3) ┆84┆The function 'disconnect line' (PF12) or DISC in ↓
┆19┆┆91┆┄┄a command file) is selected. ↲
↲
╞ ╞ ┆84┆The functions directly affecting the X.21 connection ↓
┆19┆┆89┆┄┄work as follows: ↲
↲
╞ ╞ Connect line (PF13) : ↲
↲
╞ ╞ ╞ ┆84┆On selection the emulator tries to establish a con┄↓
┆19┆┆8e┆┄┄nection by making an X.21-call to the Datex-number ↓
┆19┆┆8e┆┄┄specified in the configuration file parameter CALL-↓
┆19┆┆8e┆┄┄ID. If the first call is unsuccessful, the emulator ↓
┆19┆┆8e┆┄┄keeps calling at intervals of 3 seconds. A maximum ↓
┆19┆┆8e┆┄┄of 20 calls is performed, and if still unsuccess┄┄↓
┆19┆┆8e┆┄┄ful, the terminal enters the disconnected state. ↲
↲
╞ ╞ Disconnect line (PF12): ↲
↲
╞ ╞ ╞ ┆84┆On selection the emulator transmits the DLE-EOT ↓
┆19┆┆8e┆┄┄control sequence and the X.21 connection is ↓
┆19┆┆8e┆┄┄cleared. ↲
┆8c┆┄┆b1┆↓
┆0e┆↓
↲
╞ ╞ Wait connection (PF14): ↲
↲
╞ ╞ ╞ ┆84┆On selection the emulator waits for an X.21 incom┄↓
┆19┆┆8e┆┄┄ming call and establishes the connection when the ↓
┆19┆┆8e┆┄┄call is received.↲
↲
┆0f┆↓
════════════════════════════════════════════════════════════════════════
↓
↲
════════════════════════════════════════════════════════════════════════
↓
↲
┆a1┆┆b0┆A.╞ ╞ References ↲
↲
↲
╞ ╞ 1 RCSL No 42-i1686: ↲
╞ ╞ ╞ RC855 Operating Guide ↲
╞ ╞ ╞ Henning Christensen, April 1982 ↲
╞ ╞ ╞ Abstract: ┆84┆Operating Guide for the RC855 Terminal┄↓
┆19┆┆98┆┄┄/Work Stattion. Describes: connections ↓
┆19┆┆98┆┄┄and ope┄rator controls; keyboard features; ↓
┆19┆┆98┆┄┄start-up proce┄dures. Covers the general ↓
┆19┆┆98┆┄┄aspects and is ment to be used in con┄↓
┆19┆┆98┆┄┄junction with the application documenta┄↓
┆19┆┆98┆┄┄tion. ↲
↲
╞ ╞ 2 RCSL No 42-i2347: ↲
╞ ╞ ╞ RC855 Work Station, User's Guide ↲
╞ ╞ ╞ Jeffrey C. Snider, Leif Olsen, June 1983.↲
╞ ╞ ╞ Abstract: ┆84┆Describes how to install and operate the ↓
┆19┆┆98┆┄┄CP/M operating system on the RC855 Work ↓
┆19┆┆98┆┄┄Station.↲
↲
╞ ╞ 3 RCSL No 42-i2505: ↲
╞ ╞ ╞ ┆84┆RC855 IBM 2780/3780 BSC Emulator, Installation ↓
┆19┆┆8e┆┄┄Guide ↲
╞ ╞ ╞ ┆84┆Claus Terp, Hans M. Nielsen, April 1984.↲
╞ ╞ ╞ Abstract: ┆84┆This manual describes the installation of ↓
┆19┆┆98┆┄┄the RC855 IBM 2780/3780 BSC Emulator ↓
┆19┆┆98┆┄┄under the RC855 CP/M operating system.↲
↲
╞ ╞ 4 RCSL No 42-i2506: ↲
╞ ╞ ╞ RC855 IBM 2780/3780 BSC Emulator, Operating Guide ↲
╞ ╞ ╞ Claus Terp, Hans M. Nielsen, April 1984↲
╞ ╞ ╞ Abstract: ┆84┆This manual describes the operation of ↓
┆19┆┆98┆┄┄the RC855 IBM 2780/3780 BSC Emulator: ↓
┆19┆┆98┆┄┄keyboard functions, operating procedures, ↓
┆19┆┆98┆┄┄emulator messages. Further it contains ↓
┆19┆┆98┆┄┄descriptions concerning configuration ↓
┆19┆┆98┆┄┄file, command files, etc. ↲
↲
┆a1┆┆b0┆A.1╞ ╞ Additional references ↲
↲
↲
╞ ╞ IBM publications: ↲
↲
╞ ╞ ┆84┆GA27-3004 Component Description for the IBM 2780 Data ↓
┆19┆┆89┆┄┄Trans┄mission Terminal ↲
↲
╞ ╞ ┆84┆GA27-3005 General Information - Binary Synchronous Com┄↓
┆19┆┆89┆┄┄munica┄tions↲
↲
┆8c┆┄┆b3┆↓
╞ ╞ ┆84┆GA27-3063 Component Information for the IBM 3780 Data ↓
┆19┆┆89┆┄┄Com┄munication Terminal. ↲
↲
↲
════════════════════════════════════════════════════════════════════════
↓
↲
┆a1┆┆b0┆B.╞ ╞ Examples of host generation parameters ↲
↲
┆a1┆┆b0┆B.1╞ ╞ JES2 ↲
↲
╞ ╞ ╞ 2780: RMTnnn 2780, MRF, NUMPU=1, TRANSP ↲
↲
╞ ╞ ╞ 3780: RMTnnn 3780, COMP, NUMPU=1, TRANSP ↲
↲
↲
┆a1┆┆b0┆B.2╞ ╞ DOS/VS POWER/VS ↲
↲
╞ ╞ ╞ 2780: PRMT REMOTE=nnn ↲
╞ ╞ ╞ ╞ ╞ ,TYPE=2780 ↲
╞ ╞ ╞ ╞ ╞ ,MRF=YES ↲
╞ ╞ ╞ ╞ ╞ ,LIST=132 ↲
↲
╞ ╞ ╞ 3780: PRMT REMOTE=nnn ↲
╞ ╞ ╞ ╞ ╞ ,TYPE=3780 ↲
╞ ╞ ╞ ╞ ╞ ,SCE=YES ↲
╞ ╞ ╞ ╞ ╞ ,LIST=132 ↲
╞ ╞ ╞ ╞ ╞ ,CS=YES ↲
↲
↲
════════════════════════════════════════════════════════════════════════
↓
↲
┆a1┆┆b0┆C.╞ ╞ Character code sets ↲
↲
┆a1┆┆b0┆C.1╞ ╞ US English EBCDIC ↲
↲
════════════════════════════════════════════════════════════════════════
↓
↲
↲
┆a1┆┆b0┆C.2╞ ╞ US English ASCII ↲
↲
════════════════════════════════════════════════════════════════════════
↓
↲
↲
┆a1┆┆b0┆C.3╞ ╞ UK English EBCDIC ↲
↲
════════════════════════════════════════════════════════════════════════
↓
↲
↲
┆a1┆┆b0┆C.4╞ ╞ UK English ASCII ↲
↲
════════════════════════════════════════════════════════════════════════
↓
↲
↲
┆a1┆┆b0┆C.5╞ ╞ German EBCDIC ↲
↲
╞ ╞ Commonly used with the IBM 2780/3780 emulator. ↲
↲
↲
════════════════════════════════════════════════════════════════════════
↓
↲
↲
┆a1┆┆b0┆C.6╞ ╞ German alternate EBCDIC ↲
↲
╞ ╞ ┆84┆Only 90 codes are shown in the table below. The charac┄↓
┆19┆┆89┆┄┄ters "$", "┆a8┆#┆e8┆", "'", "#", and """ can be entered from the ↓
┆19┆┆89┆┄┄keyboard. However, when they are transmitted to the host ↓
┆19┆┆89┆┄┄computer, all of these characters are transmitted as ↓
┆19┆┆89┆┄┄blanks (40┆82┆Hex┆81┆). ↲
↲
↲
════════════════════════════════════════════════════════════════════════
↓
↲
↲
┆a1┆┆b0┆C.7╞ ╞ German ASCII ↲
↲
════════════════════════════════════════════════════════════════════════
↓
↲
↲
┆a1┆┆b0┆C.8╞ ╞ Swedish EBCDIC ↲
↲
╞ ╞ Commonly used with the IBM 2780/3780 emulator. ↲
════════════════════════════════════════════════════════════════════════
↓
↲
↲
┆a1┆┆b0┆C.9╞ ╞ Swedish alternate EBCDIC ↲
↲
════════════════════════════════════════════════════════════════════════
↓
↲
↲
┆a1┆┆b0┆C.10╞ Swedish ASCII ↲
↲
════════════════════════════════════════════════════════════════════════
↓
↲
↲
┆a1┆┆b0┆C.11╞ Danish Standard EBCDIC ↲
↲
════════════════════════════════════════════════════════════════════════
↓
↲
↲
┆a1┆┆b0┆C.12╞ Danish Standard Alternate EBCDIC ↲
↲
╞ ╞ Commonly used with the IBM 2780/3780 emulator. ↲
↲
╞ ╞ ┆84┆Only 93 EBCDIC codes are used for graphic characters. ↓
┆19┆┆89┆┄┄The characters "Å" and "$" can both be entered from the ↓
┆19┆┆89┆┄┄keyboard. However, when they are transmitted to the host ↓
┆19┆┆89┆┄┄computer, both "Å" and "$" are transmitted as 5B┆82┆Hex┆81┆. ↓
┆19┆┆89┆┄┄When the EBCDIC code 5B┆82┆Hex┆81┆ is received from the host, it ↓
┆19┆┆89┆┄┄is printed as "Å". The characters "Æ" and "#" are simil┄↓
┆19┆┆89┆┄┄arly treated. Both are transmitted as 7B┆82┆Hex┆81┆. When 7B┆82┆Hex┆81┆ ↓
┆19┆┆89┆┄┄is received, it is printed as "Æ".↲
════════════════════════════════════════════════════════════════════════
↓
↲
↲
┆a1┆┆b0┆C.13╞ Danish Standard ASCII ↲
↲
════════════════════════════════════════════════════════════════════════
↓
↲
↲
┆a1┆┆b0┆C.14╞ Danish public sector EBCDIC ↲
↲
════════════════════════════════════════════════════════════════════════
↓
↲
↲
┆a1┆┆b0┆C.15╞ Danish public sector alternate EBCDIC ↲
↲
╞ ╞ Commonly used with the IBM 2780/3780 emulator. ↲
↲
╞ ╞ ┆84┆Only 94 EBCDIC codes are used for graphic characters. ↓
┆19┆┆89┆┄┄The characters "Å" and "$" are treated as described for ↓
┆19┆┆89┆┄┄the Danish standard EBCDIC character codes; see C.11. ↲
↲
════════════════════════════════════════════════════════════════════════
↓
↲
↲
┆a1┆┆b0┆C.16╞ Danish public sector ASCII ↲
↲
════════════════════════════════════════════════════════════════════════
↓
↲
↲
┆a1┆┆b0┆D.╞ ╞ Line connections ↲
↲
┆a1┆┆b0┆D.1╞ ╞ Modem Connection ↲
↲
╞ ╞ ┆84┆The RC855 display terminal has a 25-pin type DB25-S con┄↓
┆19┆┆89┆┄┄nec┄tor marked LINE I. This connector is used for attach┄↓
┆19┆┆89┆┄┄ment of a signal cable to a modem. In IBM2780/3780 emu┄↓
┆19┆┆89┆┄┄lations the terminal can use either the V.24 or the X.21 ↓
┆19┆┆89┆┄┄interface stan┄dard in accordance with the emulator part ↓
┆19┆┆89┆┄┄loaded. ↲
↲
╞ ╞ ┆84┆The correspondence between connector pins and inter┄┄↓
┆19┆┆89┆┄┄change circuits are shown in the following subsections. ↲
↲
↲
┆a1┆┆b0┆D.1.1╞ V.24 Interface ↲
↲
╞ ╞ ┆84┆As defined in the CCITT V.24 recommendation (complies ↓
┆19┆┆89┆┄┄with ISO Standard No. 2110). Pins not shown are not used ↓
┆19┆┆89┆┄┄by the V.24-operating emulator parts. ↲
╱04002d440a0006000000000201463160000000000000000000000000000000000000000000000000050a0f14191e23282a2d32373c414bff04╱
╱04002d4e0a000600000000020a4a31000000000000000000000000000000000000000000000000000e1318222c3136404a545e68727c86ff04╱
↓
↲
╞ ╞ ╞ ╞ ╞ Pin V.24 ↲
╞ ╞ ╞ ╞ ╞ No. ╞ Interchange Circuit ↲
╞ ╞ ┆a1┆_╞ _┆e1┆╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ┆a1┆_ _↲
╞ ╞ ø╞ ┆a1┆ø_ _┆e1┆╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ┆a1┆_ ø┆e1┆ ø↲
╞ ╞ ø╞ ø ø┆a1┆╞ 1 protective ground (101)╞ _┆e1┆ø ø ø↲
╞ ╞ ø╞ ø ø┆a1┆╞ 2 transmitted data (103)╞ ╞ _┆e1┆ø ø ø↲
╞ ╞ ø╞ ø L ø┆a1┆╞ 3 received data (104)╞ ╞ _┆e1┆ø ø M ø↲
╞ ╞ ø RC855 ø I ø┆a1┆╞ 4 request to send (105)╞ ╞ _┆e1┆ø ø ø↲
╞ ╞ ø╞ ø N ø┆a1┆╞ 5 ready for sending (106)╞ _┆e1┆ø ø O ø↲
╞ ╞ øDisplay ø E ø┆a1┆╞ 6 data set ready (107)╞ ╞ _┆e1┆ø ø ø↲
╞ ╞ ø╞ ø ø┆a1┆╞ 7 signal ground (102)╞ ╞ _┆e1┆ø ø D ø↲
╞ ╞ øTerminalø I ø┆a1┆╞ 8 carrier (109)╞ ╞ ╞ _┆e1┆ø ø ø↲
╞ ╞ ø╞ ø ø┆a1┆╞ 15 transmit clock (114)╞ ╞ _┆e1┆ø ø E ø↲
╞ ╞ ø╞ ø ø┆a1┆╞ 17 receive clock (115)╞ ╞ _┆e1┆ø ø ø↲
╞ ╞ ø╞ ø ø┆a1┆╞ 20 data terminal ready (108/2)╞ _┆e1┆ø ø M ø↲
╞ ╞ ø╞ ø ø┆a1┆╞ 22 calling indicator (125)╞ _┆e1┆ø ø ø↲
╞ ╞ ø ┆a1┆ø┆a1┆_ ø┆e1┆╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ┆a1┆ø _ø┆e1┆ ø↲
┆a1┆ø ø┆e1┆╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ┆a1┆ø ø↲
╱04002d440a0006000000000201413160000000000000000000000000000000000000000000000000050a0f14191e23282a2d3237414b55ff04╱
╱04002d440a0006000000000201463160000000000000000000000000000000000000000000000000050a0f14191e23282a2d32373c414bff04╱
↓
↲
┆a1┆┆b0┆D.1.2╞ X.21 Interface ↲
↲
╞ ╞ ┆84┆As defined in the CCITT X.21 recommendation (complies with ↓
┆19┆┆89┆┄┄ISO Standard No. 4903). Pins not shown are not used by ↓
┆19┆┆89┆┄┄the ↓
┆19┆┆89┆┄┄X.21-operating emulator parts. ↲
┆8c┆┄┆b0┆↓
┆0e┆↓
↲
╱04002d440a0006000000000201463160000000000000000000000000000000000000000000000000050a0f14191e23282a2d32373c414bff04╱
╱04002d440a0006000000000201413160000000000000000000000000000000000000000000000000050a0f14191e23282a2d3237414b55ff04╱
↓
↲
╞ ╞ ╞ ╞ ╞ Pin X.21↲
╞ ╞ ╞ ╞ No. Interchange Circuit ↲
╞ ╞ ┆a1┆_╞ _┆e1┆╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ┆a1┆_ _↲
╞ ╞ ø╞ ┆a1┆ø_ _┆e1┆╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ┆a1┆_ ø┆e1┆ ø↲
╞ ╞ ø╞ ø ø┆a1┆┆e1┆ ╞ ┆e1┆ø ø ø↲
╞ ╞ ø╞ ø ø┆a1┆ 1 Protective Ground (G) 1 ┆e1┆ø ø ø↲
╞ ╞ ø╞ ø L ø┆a1┆┆e1┆ ╞ ╞ ┆e1┆ø ø M ø↲
╞ ╞ ø RC855 ø I ø┆a1┆ 9/12 Transmitted data (T) 2/9╞ ┆e1┆ø ø ø↲
╞ ╞ ø╞ ø N ø┆a1┆┆e1┆ ╞ ┆e1┆ø ø O ø↲
╞ ╞ øDisplay ø E ø┆81┆┆a1┆ 21/19 Received data (R) 4/11 ┆e1┆┆82┆ø ø ø↲
╞ ╞ ø╞ ø ø┆82┆┆a1┆ 10/24 Indicator (I) 5/11 ┆e1┆┆81┆ø ø D ø↲
╞ ╞ øTerminalø I ø┆a1┆┆e1┆ ╞ ┆e1┆ø ø ø↲
╞ ╞ ø╞ ø ø┆81┆┆a1┆ 7 Signal ground (GA) 8╞ ┆e1┆┆82┆ø ø E ø↲
╞ ╞ ø╞ ø ø┆82┆┆a1┆ 18/16 Signal element timing (S) 6/13┆e1┆┆81┆ø ø ø↲
╞ ╞ ø╞ ø ø┆a1┆┆e1┆ ╞ ┆e1┆ø ø M ø↲
╞ ╞ ø╞ ø ø┆a1┆ 25/14 Control (C) 3/10 ┆e1┆ø ø ø↲
╞ ╞ ø ┆a1┆ø┆a1┆_ ø┆e1┆╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ┆a1┆ø _ø┆e1┆ ø↲
┆a1┆ø ø┆e1┆╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ┆a1┆ø ø↲
↲
┆0f┆↓
┆a1┆┆b0┆D.2╞ ╞ Printer Connection ↲
↲
╞ ╞ ┆84┆The RC855 display terminal has a 25-pin type DB25-S con┄↓
┆19┆┆89┆┄┄nec┄ter marked LINE II. This connector is used for at┄↓
┆19┆┆89┆┄┄tachment of a printer.↲
↲
╞ ╞ ┆84┆The illustration below shows the correspondence between ↓
┆19┆┆89┆┄┄connector pins and interchange circuits as defined in ↓
┆19┆┆89┆┄┄the CCITT V.24 recommendation (complies with ISO Stan┄┄↓
┆19┆┆89┆┄┄dard No. 2110). Pins not shown are not used by the emu┄↓
┆19┆┆89┆┄┄lator. ↲
↲
╱04002d440a0006000000000201463160000000000000000000000000000000000000000000000000050a0f14191e23282a2d32373c414bff04╱
╱04002d440a0006000000000201463160000000000000000000000000000000000000000000000000050a0f14191e23282a2d32373c414bff04╱
↓
↲
╞ ╞ ╞ ╞ ╞ Pin V.24↲
╞ ╞ ╞ ╞ No. Interchange Circuit ↲
╞ ╞ ┆a1┆_╞ _┆e1┆╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ┆a1┆_ _↲
╞ ╞ ø╞ ┆a1┆ø_ _┆e1┆╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ┆a1┆_ ø┆e1┆ ø↲
╞ ╞ ø╞ ø ø┆a1┆┆e1┆ ╞ ┆e1┆ø ø ø↲
╞ ╞ ø╞ ø ø┆a1┆ 2 Transmitted data (103) ┆e1┆ø ø ø↲
╞ ╞ ø╞ ø L ø┆a1┆┆e1┆ ╞ ╞ ┆e1┆ø ø M ø↲
╞ ╞ ø RC855 ø I ø┆a1┆ 4 Request to send (105) ┆e1┆ø ø ø↲
╞ ╞ ø╞ ø N ø┆a1┆┆e1┆ ╞ ┆e1┆ø ø O ø↲
╞ ╞ øDisplay ø E ø┆a1┆ 5 Ready for sending (106) ┆e1┆ø ø ø↲
╞ ╞ ø╞ ø ø┆a1┆┆e1┆ ┆e1┆ø ø D ø↲
╞ ╞ øTerminalø I ø┆a1┆┆e1┆┆a1┆ 7 Signal ground (102)╞ ┆e1┆ø ø ø↲
╞ ╞ ø╞ ø ø┆a1┆┆e1┆ ╞ ┆e1┆ø ø E ø↲
╞ ╞ ø╞ ø ø┆a1┆ 8 Carrier (109) ┆e1┆ø ø ø↲
╞ ╞ !╞ ! !┆a1┆┆e1┆ ╞ ┆e1┆! ! M !↲
╞ ╞ !╞ ! !┆a1┆ 20 Data terminal ready (108/2) ┆e1┆! ! !↲
╞ ╞ ! ┆a1┆!┆a1┆_ !┆e1┆╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ┆a1┆! _!┆e1┆ !↲
┆a1┆! !┆e1┆╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ╞ ┆a1┆! !↲
╱04002d440a0006000000000201413160000000000000000000000000000000000000000000000000050a0f14191e23282a2d3237414b55ff04╱
╱04002d440a0006000000000201463160000000000000000000000000000000000000000000000000050a0f14191e23282a2d32373c414bff04╱
↓
↲
════════════════════════════════════════════════════════════════════════
↓
↲
↲
┆a1┆┆b0┆E.╞ ╞ Index ↲
↲
↲
╞ ╞ ┆a1┆┆b0┆╞ ╞ ╞ A╞ ╞ ╞ ↲
↲
╞ ╞ Additional references .................... 19 ↲
╞ ╞ alternate EBCDIC ......................... 9 ↲
╞ ╞ ASCII .................................... 9 ↲
↲
↲
╞ ╞ ┆a1┆┆b0┆╞ ╞ ╞ B╞ ╞ ╞ ↲
↲
↲
↲
╞ ╞ ┆a1┆┆b0┆╞ ╞ ╞ C╞ ╞ ╞ ↲
↲
╞ ╞ character code set ....................... 9, 22 ↲
╞ ╞ command file ............................. 12 ↲
╞ ╞ commands ................................. 2 ↲
╞ ╞ commands in a command file ............... 12 ↲
╞ ╞ configuration file ....................... 8 ↲
╞ ╞ connect line ............................. 15, 16 ↲
╞ ╞ continous file ........................... 4 ↲
╞ ╞ conversion table changes ................. 9 ↲
╞ ╞ ccw code definitions ..................... 10 ↲
↲
↲
╞ ╞ ┆a1┆┆b0┆╞ ╞ ╞ D╞ ╞ ╞ ↲
↲
╞ ╞ disconnect line .......................... 12, 13 ↲
↲
↲
╞ ╞ ┆a1┆┆b0┆╞ ╞ ╞ E╞ ╞ ╞ ↲
↲
╞ ╞ EBCDIC ................................... 9 ↲
╞ ╞ ESC-sequence ............................. 4, 10 ↲
↲
↲
╞ ╞ ┆a1┆┆b0┆╞ ╞ ╞ F╞ ╞ ╞ ↲
↲
╞ ╞ file format .............................. 3 ↲
╞ ╞ file names ............................... 12 ↲
╞ ╞ function keys ............................ 2, 15, 16 ↲
↲
↲
╞ ╞ ┆a1┆┆b0┆╞ ╞ ╞ G╞ ╞ ╞ ↲
↲
↲
┆8c┆┄┆b2┆↓
┆0e┆↓
↲
╞ ╞ ┆a1┆┆b0┆╞ ╞ ╞ H╞ ╞ ╞ ↲
↲
╞ ╞ host generation parameters ............... 21 ↲
↲
┆0f┆↓
↲
╞ ╞ ┆a1┆┆b0┆╞ ╞ ╞ I╞ ╞ ╞ ↲
↲
↲
↲
╞ ╞ ┆a1┆┆b0┆╞ ╞ ╞ J╞ ╞ ╞ ↲
↲
↲
↲
╞ ╞ ┆a1┆┆b0┆╞ ╞ ╞ K╞ ╞ ╞ ↲
↲
↲
↲
╞ ╞ ┆a1┆┆b0┆╞ ╞ ╞ L╞ ╞ ╞ ↲
↲
╞ ╞ line connections ......................... 38 ↲
╞ ╞ loading .................................. 1 ↲
↲
↲
╞ ╞ ┆a1┆┆b0┆╞ ╞ ╞ M╞ ╞ ╞ ↲
↲
╞ ╞ modem connection ......................... 38 ↲
╞ ╞ modem signals ............................ 15 ↲
↲
↲
╞ ╞ ┆a1┆┆b0┆╞ ╞ ╞ N╞ ╞ ╞ ↲
↲
╞ ╞ national variants of character sets ...... 9, 22 ↲
╞ ╞ non-continous file ....................... 4 ↲
╞ ╞ non-transparent .......................... 3 ↲
↲
↲
╞ ╞ ┆a1┆┆b0┆╞ ╞ ╞ O╞ ╞ ╞ ↲
↲
╞ ╞ operating ................................ 1 ↲
↲
↲
╞ ╞ ┆a1┆┆b0┆╞ ╞ ╞ P╞ ╞ ╞ ↲
↲
╞ ╞ padding .................................. 5 ↲
╞ ╞ parameters ............................... 2 ↲
╞ ╞ print-data ............................... 4 ↲
╞ ╞ printer connection ....................... 39↲
╞ ╞ printer control characters ............... 9 ↲
╞ ╞ punch-data ............................... 4 ↲
↲
↲
┆8c┆┄┆b4┆↓
╞ ╞ ┆a1┆┆b0┆╞ ╞ ╞ R╞ ╞ ╞ ↲
↲
╞ ╞ RC855 configuration parameter ............ 9 ↲
╞ ╞ receival ................................. 4 ↲
╞ ╞ references ............................... 19 ↲
╞ ╞ record handling .......................... 3 ↲
╞ ╞ record size .............................. 4 ↲
╞ ╞ record split ............................. 4 ↲
╞ ╞ reset .................................... 12 ↲
↲
↲
╞ ╞ ┆a1┆┆b0┆╞ ╞ ╞ S╞ ╞ ╞ ↲
↲
╞ ╞ signoff-record ........................... 13 ↲
╞ ╞ signon file .............................. 7 ↲
╞ ╞ specifications ........................... 1 ↲
↲
↲
╞ ╞ ┆a1┆┆b0┆╞ ╞ ╞ T╞ ╞ ╞ ↲
↲
╞ ╞ termination characters ................... 3, 9 ↲
╞ ╞ transmission ............................. 3 ↲
╞ ╞ transparent .............................. 3, 4, 5 ↲
╞ ╞ truncation ............................... 5 ↲
↲
↲
╞ ╞ ┆a1┆┆b0┆╞ ╞ ╞ U╞ ╞ ╞ ↲
↲
↲
↲
╞ ╞ ┆a1┆┆b0┆╞ ╞ ╞ V╞ ╞ ╞ ↲
↲
╞ ╞ V.24 ..................................... 15 ↲
╞ ╞ V.24 interface ........................... 38 ↲
↲
↲
╞ ╞ ┆a1┆┆b0┆╞ ╞ ╞ W╞ ╞ ╞ ↲
↲
╞ ╞ wait connection .......................... 17 ↲
↲
↲
╞ ╞ ┆a1┆┆b0┆╞ ╞ ╞ X╞ ╞ ╞ ↲
↲
╞ ╞ X.21 ..................................... 16 ↲
╞ ╞ X.21 interface ........................... 38 ↲
↲
┆8c┆┄┆ae┆↓
┆0e┆↓
↲
╞ ╞ ┆a1┆┆b0┆╞ ╞ ╞ Y╞ ╞ ╞ ↲
↲
↲
↲
╞ ╞ ┆a1┆┆b0┆╞ ╞ ╞ Z╞ ╞ ╞ ↲
┆0f┆↓
↲
════════════════════════════════════════════════════════════════════════
↓
↲
↲
════════════════════════════════════════════════════════════════════════
┆1a┆┆1a┆erminections ↲
↲
┆a1┆┆b0┆D.1╞ ╞ Modem Connection ↲
↲
╞ ╞ ┆84┆The RC855 display terminal has a 25-pin type DB25-S con┄↓
┆19┆┆89┆┄┄ne