|
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: 130944 (0x1ff80)
Types: RcTekst
Names: »99110409.WP«
└─⟦6fdfe4d4d⟧ Bits:30005866/disk5.imd Dokumenter i RcTekst format (RCSL 99-1-*)
└─⟦this⟧ »99110409.WP«
╱04002d4e0a000600000000030c4731400000000000000000000000000000000000000000000000000c16202a343e48525c66707a848e98ff04╱
════════════════════════════════════════════════════════════════════════
↓
┆a1┆┆b0┆┆a1┆RC3931 Communications Processor↲
┆b0┆┆a1┆User's Guide↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
┆b0┆February 1986↲
┆b0┆RCSL No. 991 10409↲
┆b0┆Development Department↲
┆b0┆RC Computer A/S↲
════════════════════════════════════════════════════════════════════════
↓
Copyright (C) 1985↲
A/S Regnecentralen af 1979 / RC Computer A/S↲
┆a1┆Published by A/S Regnecentralen af 1979, Copenhagen↲
↲
Users of this document are cautioned that the specifications ↓
contained herein are subject to change by RC at any time ↓
without prior notice. RC is not responsible for typograph┄↓
ical or arithmetic errors which may appear in this document ↓
and shall not be responsible for any damage caused by ↓
reliance on any of the material presented.↲
════════════════════════════════════════════════════════════════════════
↓
┆14┆┆b3┆↲
┆14┆┆b1┆┆b0┆ RC3931 Communications Processor┆05┆Contents ↲
┆14┆┆b2┆┆b0┆ Contents┆05┆RC3931 Communications Processor ↲
┆15┆┆b3┆↲
┆15┆┆b3┆↲
┆15┆┆b3┆↲
┆15┆┆b1┆┆b0┆ Update 1/86┆05┆Page Contents-┆0b┆ ↲
┆15┆┆b2┆┆b0┆ Page Contents-┆0b┆┆05┆Update 1/86 ↲
╱04002d4e0a000600000000030c4731400000000000000000000000000000000000000000000000000c0f121416202a343e48525c66707aff04╱
╱04002d4e0a000600000000030c4731400000000000000000000000000000000000000000000000000c16202a343e48525c66707a848e98ff04╱
↓
┆a1┆CONTENTS↲
↲
A.╞ ┆a1┆Introduction┆e1┆ Page A-1↲
↲
B.╞ ┆a1┆System Overview┆e1┆ B.1-1↲
╞ 1.╞ ┆a1┆Basic Functions┆e1┆ B.1-1↲
╞ ╞ LAN communication B.1-1↲
╞ ╞ RcCircuit communication B.1-2↲
╞ ╞ Terminal download B.1-2↲
╞ 2. ┆a1┆IBM 3270 Emulation┆e1┆ B.2-1↲
╞ ╞ Linking the CU to a host computer B.2-1↲
╞ ╞ ╞ Multiple links B.2-1↲
╞ ╞ ╞ Host link selection B.2-2↲
╞ ╞ ╞ ╞ Skipping the host link menu B.2-2↲
╞ ╞ ╞ Remote host links B.2-3↲
╞ ╞ ╞ ╞ IBM-compatible links B.2-3↲
╞ ╞ ╞ ╞ X.21-BSC B.2-3↲
╞ ╞ ╞ ╞ Dual host configuration B.2-4↲
╞ ╞ ╞ Local host links B.2-4↲
╞ ╞ Emulated 3270 devices B.2-4↲
↲
C. ┆a1┆Software Installation┆e1┆ C-1↲
╞ ╞ After installation C-1↲
╞ ╞ ╞ SW3882 (ANSI X3.64 terminal program) C-1↲
╞ ╞ ╞ SW3802 (Teletex) C-2↲
SW3803 and (3270 emulation) C-2↲
╞ ╞ SW3804 (3270 Programmer's toolkit)↲
↲
D.╞ ┆a1┆System Customization┆e1┆ D.1-1↲
╞ 1.╞ ┆a1┆Configuration┆e1┆ D.1-2↲
╞ ╞ Basic functions D.1-2↲
╞ ╞ IBM 3270 emulation D.1-3↲
╞ ╞ ╞ Remote host links D.1-3↲
╞ ╞ ╞ Local host links D.1-4↲
╞ ╞ ╞ Soft devices D.1-4↲
╞ Teletex D.1-4↲
════════════════════════════════════════════════════════════════════════
↓
╞ 2.╞ ┆a1┆Customization, Parameter Files┆e1┆ Page D.2-1↲
╞ ╞ Parameter file syntax D.2-1↲
╞ ╞ Download menus (MENUDL.CST) D.2-2↲
╞ ╞ ╞ Frame text: FTEXT D.2-4↲
╞ ╞ ╞ Error text: ETEXT D.2-4↲
╞ ╞ ╞ Terminal program: TPRG D.2-4↲
╞ ╞ ╞ Terminal menu: TMENU D.2-4↲
╞ ╞ ╞ Example D.2-5↲
╞ ╞ Conversion tables (CONV.CST) D.2-6↲
╞ ╞ ╞ Conversion to internal code: INTCODE D.2-7↲
╞ ╞ ╞ Conversion to EBCDIC code: EBCDIC D.2-8↲
╞ ╞ Displayable texts (TEXTS.CST) D.2-8↲
╞ ╞ ╞ Host link menu heading: HOSTMENU D.2-8↲
╞ ╞ ╞ BSC link name: BSCID D.2-8↲
╞ ╞ ╞ SNA/SDLC link name: SNAID D.2-9↲
╞ ╞ ╞ Device status message: DSTEXT D.2-9↲
╞ ╞ ╞ Communication status message: CSTEXT D.2-10↲
╞ ╞ Communication parameters (COMM.CST) D.2-10↲
╞ ╞ ╞ Parameters for BSC links D.2-11↲
╞ ╞ ╞ ╞ BSC link kind: BSCKIND D.2-11↲
╞ ╞ ╞ ╞ EBCDIC code for BSC link: BSCCONV D.2-11↲
CU number: BSCCU D.2-12↲
╞ ╞ ╞ ╞ DTR handling: BSCDTR D.2-12↲
╞ ╞ ╞ ╞ Half/full duplex: BSCDUP D.2-13↲
╞ ╞ ╞ ╞ BSC printer timeout: BSCPTIME D.2-13↲
X.21 subscriber number: BSCXNO D.2-13↲
╞ ╞ ╞ Parameters for SNA/SDLC links D.2-13↲
╞ ╞ ╞ ╞ SNA/SDLC link kind: SDLCKIND D.2-14↲
╞ ╞ ╞ ╞ EBCDIC code for SNA/SDLC link D.2-14↲
SDLC address: SDLCADDR D.2-14↲
╞ ╞ ╞ ╞ Terminal ID: TERMID D.2-15↲
╞ ╞ ╞ ╞ NRZI encoding: SDLCNRZI D.2-15↲
╞ ╞ ╞ ╞ Printer sharing: PSHARING D.2-15↲
╞ ╞ ╞ ╞ DTR handling: SDLCDTR D.2-16↲
════════════════════════════════════════════════════════════════════════
↓
╞ ╞ ╞ ╞ Half/full duplex: SDLCDUP D.2-16↲
╞ ╞ ╞ ╞ Point-to-point/multipoint: MPOINT D.2-16↲
╞ ╞ ╞ ╞ Host subscriber number: SDLCHXNO D.2-16↲
╞ ╞ ╞ ╞ Own subscriber number: SDLCCXNO D.2-17↲
╞ ╞ ╞ Printer authorization Page D.2-17↲
╞ ╞ ╞ ╞ Printer mode: PMODE D.2-18↲
╞ ╞ ╞ ╞ Printer class: PCLASS D.2-18↲
╞ ╞ ╞ ╞ Printer source device list: PSRCLIST D.2-18↲
╞ ╞ ╞ Cluster size D.2-19↲
╞ ╞ ╞ ╞ Maximum device number: MAXDEVNO D.2-19↲
╞ ╞ ╞ ╞ Number of terminals: NOTERMS D.2-19↲
╞ ╞ Local host links D.2-19↲
╞ ╞ ╞ ╞ Number of local host links: CULCONS D.2-20↲
╞ ╞ ╞ ╞ ┆84┆Output message size host links: CULOSIZE D.2-20↲
Input message size host links: CULOSIZE D.2-20↲
╞ ╞ ╞ ╞ CU port name for local host link: CULIPORT D.2-20↲
╞ ╞ Soft devices D.2-21↲
╞ ╞ ╞ ╞ Device numbers: SOFTDEVS D.2-21↲
╞ ╞ ╞ ╞ Soft device timeout: SOFTMOUT D.2-21↲
╞ ╞ ╞ Parameters for Teletex D.2-21↲
╞ ╞ ╞ ╞ Class 0 pages: CLASS0P D.2-21↲
╞ ╞ ╞ ╞ Number of letters: MAXL D.2-21↲
╞ ╞ ╞ ╞ Address of Telex conversion facility: ↲
CFADDR D.2-22↲
↲
E.╞ ┆a1┆System Management┆e1┆ E-1↲
╞ ╞ Resetting the CP E-1↲
╞ ╞ Files belonging to the CP E-2↲
╞ ╞ ╞ Auxiliary files E-2↲
╞ ╞ ╞ Selecting character conversion E-4↲
╞ ╞ External cable connections E-4↲
╞ ╞ Device number management (3270) E-7↲
╞ ╞ CP log file E-7↲
╞ ╞ Lamps on the front panel E-8↲
↲
════════════════════════════════════════════════════════════════════════
↓
F. ┆a1┆Normal Use┆e1┆ F-1↲
╞ Error messages during download F-1↲
╞ ╞ 3270 emulator status messages F-3↲
╞ ╞ ╞ Device status messges F-3↲
╞ ╞ ╞ Communication status messages F-7↲
↲
H. ┆a1┆Appendices┆e1┆ H.1-1↲
╞ 1. ┆a1┆References┆e1┆ H.1-1↲
╞ 2. ┆a1┆Character Sets┆e1┆ H.2-1↲
╞ 3. ┆a1┆EBCDIC Character Codes┆e1┆ H.3-1↲
╞ 4.╞ ┆a1┆V.24/X.21 Connectors┆e1┆ H.4-1↲
╞ 5. ┆a1┆Host Link Information Displays┆e1┆ H.5-1↲
╞ ╞ ╞ BSC Link Information H.5-1↲
╞ ╞ ╞ SNA/SDLC Link Information H.5-2↲
╞ ╞ ╞ ╞ SNA statistics H.5-2↲
╞ ╞ ╞ ╞ SDLC statistics H.5-5↲
╞ ╞ ╞ ╞ X.21 statistics H.5-7↲
↲
┆a1┆Figures↲
↲
B-1.╞ ╞ Example: configuration of 3270 host links B.2-5↲
B-2.╞ ╞ Example: cluster of 3270 devices B.2-7↲
D-1.╞ ╞ Default terminal download menu D.2-3↲
E-1.╞ ╞ RC39 connector panel Page E-5↲
E-2.╞ ╞ RC39 front panel E-8↲
H.2-1.╞ US English character set H.2-1↲
H.2-2.╞ UK English character set H.2-2↲
H.2-3.╞ German character set H.2-3↲
H.2-4.╞ Swedish character set H.2-4↲
H.2-5.╞ Standard Danish character set H.2-5↲
H.2-6.╞ Danish OS (public sector) character set H.2-6↲
H.3-1.╞ US English EBCDIC codes H.3-1↲
H.3-2.╞ UK English EBCDIC codes H.3-2↲
H.3-3.╞ German EBCDIC codes H.3-3↲
H.3-4.╞ German alternate EBCDIC codes H.3-4↲
H.3-5.╞ Swedish EBCDIC codes H.3-5↲
════════════════════════════════════════════════════════════════════════
↓
H.3-6.╞ Swedish alternate EBCDIC codes H.3-6↲
H.3-7.╞ Standard Danish EBCDIC codes H.3-7↲
H.3-8.╞ Standard Danish alternate EBCDIC codes H.3-8↲
H.3-9.╞ Danish OS EBCDIC codes H.3-9↲
H.3-10.╞ Danish OS alternate EBCDIC codes H.3-10↲
H.5-1.╞ SNA statistics display for an inactive PU↲
H.5-2.╞ SNA statistics display for an active PU↲
H.5-3.╞ SDLC statistics display for an SDLC-V.24 link↲
H.5-4.╞ SDLC statistics display for an SDLC-X.21 link↲
H.5-5.╞ X.21 statistics display for an SDLC-X.21 link↲
════════════════════════════════════════════════════════════════════════
↓
↲
════════════════════════════════════════════════════════════════════════
↓
┆14┆┆b3┆↲
┆14┆┆b1┆┆b0┆ RC3931 Communications Processor┆05┆Introduction A↲
┆14┆┆b2┆┆b0┆ A Introduction┆05┆RC3931 Communications Processor ↲
┆15┆┆b3┆↲
┆15┆┆b1┆┆b0┆ Update 1/86┆05┆Page A-┆0b┆ A↲
┆15┆┆b2┆┆b0┆ A Page A-┆0b┆┆05┆Update 1/86 ↲
╱04002d4e0a000600000000030c4731400000000000000000000000000000000000000000000000000c151b284648525c66707a848effffff04╱
╱04002d4e0a000600000000030c4731400000000000000000000000000000000000000000000000000c0f121416202a343e48525c66707aff04╱
↓
┆a1┆A. INTRODUCTION↲
↲
The RC3931 Communications Processor (CP) is a subsystem for ↓
the RC39 Multi-User Computer System (MUCS).↲
The basic element of the RC39 MUCS is a processor which ↓
can execute application programs in the local environment, ↓
i.e. with locally connected terminals and data stored on the ↓
built-in disk unit. We refer to this processor as the Local ↓
Applications Processor (LAP). In its ability to execute ↓
application programs locally, the LAP is a completely ↓
independent system.↲
The CP is an additional, separate processor subsystem ↓
which can be built into an RC39 system. It may perform a ↓
number of communication functions, some of which are ↓
integrated with the functions of the LAP, while others, ↓
which do not involve the LAP, are equivalent to the ↓
functions of a stand-alone communication control unit, such ↓
as the RC890 or RC891 CU.↲
Through the CP, the LAP may interact with remote systems, ↓
e.g. with a mainframe host computer system. Utilizing this ↓
feature the RC39 MUCS may be used as an element in distri┄↓
buted application systems, where some functions and some ↓
data reside within a large central mainframe installation, ↓
while other functions as well as part of the data base ↓
reside locally in one or more RC39 systems.↲
Most users will not be aware of using the CP since it does ↓
not perform a user-visible function of its own, but trans┄↓
parently enables various components of a total system, both ↓
local and remote, to communicate and cooperate.↲
In this guide as well as in the user's guide which covers ↓
the RC39 MUCS in general (ref. 1), one user at each in┄↓
stallation site is designated the system administrator. A ↓
number of tasks concerning the CP are described as system ↓
administrator responsibilities. It is not the intention to ↓
imply that these tasks must necessarily all be carried out ↓
by the same person, although such an arrangement would be ↓
very practical. In general it can be said that most of the ↓
┆8c┆┆83┆┆bc┆↓
information in this guide is addressed to the system ↓
administrator.↲
The CP consists of both hardware and software. The primary ↓
hardware element of the CP is a printed circuit board which ↓
holds a single board microcomputer. This board is of the ↓
same shape and size as the other boards which are used in ↓
the RC39 MUCS. The microprocessor, RAM, and many other ↓
components on the CP board are also similar to the compo┄↓
nents on the other boards in the system. However, the CP is ↓
distinguished by containing communication control components ↓
and circuitry for receiving and transmitting data on the ↓
various communication lines which are utilized to connect ↓
the RC39 MUCS to terminals and other local or remote com┄↓
puter systems.↲
Depending on the required functions, additional adapter ↓
boards are likely to be needed, so that the CP subsystem ↓
typically consists of a total of two or three boards.↲
This guide does not cover hardware details such as board ↓
installation and fault diagnostics. Nor does it discuss ↓
which adapters etc. are needed for the various functions. In ↓
other words, it is assumed that the hardware elements which ↓
are needed for the required functions have been properly ↓
installed.↲
The program to be executed by the CP is configured in a ↓
flexible fashion from a number of available software ↓
modules. Basic functions are performed by software modules ↓
which are distributed together with the XENIX Timesharing ↓
System, while additional specific functions are performed by ↓
modules distributed in separate packages. The SW packages ↓
covered by this guide are:↲
↲
┆a1┆package╞ ╞ ╞ contents╞ ↲
SW3910╞ ╞ Software modules for basic CP functions.↲
SW3802 ┆84┆Software modules for the CP as well as the ↓
┆19┆┆8f┆┄┄LAP to provide the Teletex service.↲
SW3803╞ ╞ ┆84┆IBM 3270 emulation software enabling the CP ↓
┆19┆┆8f┆┄┄to act as an IBM 3274 Control Unit.↲
════════════════════════════════════════════════════════════════════════
↓
┆a1┆package╞ ╞ ╞ contents╞ ↲
SW3804 ┆84┆Software modules for the CP as well as the ↓
┆19┆┆8f┆┄┄LAP which enables the LAP to access a host ↓
┆19┆┆8f┆┄┄appli┄cation via the 3274 CU function of the ↓
┆19┆┆8f┆┄┄CP.↲
↲
╱04002d4e0a000600000000020c4731400000000000000000000000000000000000000000000000000c16202a343e48525c66707a848e98ff04╱
╱04002d4e0a000600000000030c4731400000000000000000000000000000000000000000000000000c151b284648525c66707a848effffff04╱
↓
The basic functions of the CP are:↲
↲
╱04002d4e0a000600000000030c4731400000000000000000000000000000000000000000000000000c16202a343e48525c66707a848e98ff04╱
╱04002d4e0a000600000000020c4731400000000000000000000000000000000000000000000000000c16202a343e48525c66707a848e98ff04╱
↓
- ┆84┆to enable the RC39 MUCS to be attached to a local area ↓
┆19┆┆82┆┄┄network (LAN) in order to communicate and interact with ↓
┆19┆┆82┆┄┄other units attached to the LAN. These units may be other ↓
┆19┆┆82┆┄┄RC39 systems, RC8000 mainframe computers, and RC750 or ↓
╱04002d4e0a000600000000020c4731400000000000000000000000000000000000000000000000000c16202a343e48525c66707a848e98ff04╱
╱04002d4e0a000600000000030c4731400000000000000000000000000000000000000000000000000c16202a343e48525c66707a848e98ff04╱
↓
┆19┆┆82┆┄┄RC45 personal computers┆81┆1┆82┆.↲
↲
╱04002d4e0a000600000000030c4731400000000000000000000000000000000000000000000000000c16202a343e48525c66707a848e98ff04╱
╱04002d4e0a000600000000020c4731400000000000000000000000000000000000000000000000000c16202a343e48525c66707a848e98ff04╱
↓
- ┆84┆to enable block-mode communication with RC45 and/or RC855 ↓
┆19┆┆82┆┄┄terminals connected to the RC39 MUCS via RcCircuit. This ↓
┆19┆┆82┆┄┄mode of communication is the basis for all terminal-↓
╱04002d4e0a000600000000020c4731400000000000000000000000000000000000000000000000000c16202a343e48525c66707a848e98ff04╱
╱04002d4e0a000600000000030c4731400000000000000000000000000000000000000000000000000c16202a343e48525c66707a848e98ff04╱
↓
┆19┆┆82┆┄┄oriented functions involving the CP.↲
↲
╱04002d4e0a000600000000030c4731400000000000000000000000000000000000000000000000000c16202a343e48525c66707a848e98ff04╱
╱04002d4e0a000600000000020c4731400000000000000000000000000000000000000000000000000c16202a343e48525c66707a848e98ff04╱
↓
- ┆84┆to present the terminal operator with a menu of programs ↓
┆19┆┆82┆┄┄which can be downloaded to run on the terminal and to ↓
┆19┆┆82┆┄┄perform the load as selected. Menus may include various ↓
┆19┆┆82┆┄┄emulators and may be customized for the individual ↓
┆19┆┆82┆┄┄terminal. Note that terminal programs to be downloaded are ↓
┆19┆┆82┆┄┄distributed as separate packages (not included among the ↓
╱04002d4e0a000600000000020c4731400000000000000000000000000000000000000000000000000c16202a343e48525c66707a848e98ff04╱
╱04002d4e0a000600000000030c4731400000000000000000000000000000000000000000000000000c16202a343e48525c66707a848e98ff04╱
↓
┆19┆┆82┆┄┄packages mentioned above).↲
↲
╱04002d4e0a000600000000030c4731400000000000000000000000000000000000000000000000000c16202a343e48525c66707a848e98ff04╱
╱04002d4e0a000600000000020c4731400000000000000000000000000000000000000000000000000c16202a343e48525c66707a848e98ff04╱
↓
This guide covers the basic functions of the CP as well as ↓
those aspects of 3270 emulation and Teletex communication ↓
that pertain to the CP. Information about 3270 emulation re┄↓
levant for the terminal operator may be found in the user's ↓
guide for the terminal or PC emulator in question (refs. ↓
2,3,4)┆81┆2┆82┆. Information about accessing the communication ↓
╱04002d4e0a000600000000020c4731400000000000000000000000000000000000000000000000000c16202a343e48525c66707a848e98ff04╱
╱04002d4e0a000600000000030c4731400000000000000000000000000000000000000000000000000c16202a343e48525c66707a848e98ff04╱
↓
______↲
↲
1. ┆84┆The abbreviation PC is used in this guide to refer to any ↓
┆19┆┆83┆┄┄RC Personal Computer, i.e. either the RC750 PC or the ↓
┆19┆┆83┆┄┄RC45 PC.↲
2. ┆84┆The available emulator operating guide may have been ↓
┆19┆┆83┆┄┄written before the release of the RC3931 CP with support ↓
┆19┆┆83┆┄┄for IBM 3270 emulation. It may therefore not mention the ↓
┆19┆┆83┆┄┄CP. However, from the point of view of a terminal ↓
┆19┆┆83┆┄┄emulator, the CP behaves exactly like the RC890 or RC891 ↓
┆19┆┆83┆┄┄Control Unit which the guide will refer to.↲
════════════════════════════════════════════════════════════════════════
↓
╱04002d4e0a000600000000030c4731400000000000000000000000000000000000000000000000000c16202a343e48525c66707a848e98ff04╱
╱04002d4e0a000600000000020c4731400000000000000000000000000000000000000000000000000c16202a343e48525c66707a848e98ff04╱
↓
functions from programs running on the LAP (XENIX programs) ↓
may be found in ref. 5.↲
From the point of view of a terminal operator the terminal ↓
download and 3270 emulation functions performed by the CP ↓
are completely equivalent to those of an RC890 or RC891 ↓
control unit (CU). For the sake of consistency we shall ↓
therefore use the abbreviation CU to refer to the CP when ↓
speaking of these functions.↲
With respect to the Teletex service only the customization ↓
of the CP-part of the software is described in this guide. ↓
The user interaction with the service through the software ↓
running on the LAP is described in ref. 7.↲
Main section B contains a general description of the ↓
functions of the CP emphasizing how the CP will interact ↓
with terminals, other units attached to a LAN, a public data ↓
network, and remote host computers.↲
SW packages for the CP are distributed on diskettes. The ↓
installation of the files on these diskettes is the subject ↓
of main section C. Some hints are also given on the most ↓
important aspects of system customization to check and/or ↓
update after installation of each package.↲
By editing a number of text files containing a specifi┄↓
cation of the functional configuration and a number of ↓
operational parameters, the system administrator may tailor ↓
the CP to the needs of the particular installation. The ↓
configuration possibilities and customization parameters are ↓
explained in main section D.↲
The responsibilities of the system administrator with ↓
respect to the CP and the tools available for accomplishing ↓
these tasks are the subjects of main section E.↲
As mentioned above, the CP is almost invisible to the ↓
normal user. However, it is the source of a number of ↓
messages, i.e. brief texts, which appear in the status line ↓
of a terminal or PC display when the downloader or an ↓
emulation system is used. The meaning of these messages is ↓
discussed in main section F.↲
════════════════════════════════════════════════════════════════════════
↓
┆14┆┆b3┆↲
┆14┆┆b1┆┆b0┆ RC3931 Communications Processor┆05┆System Overview B↲
┆14┆┆b2┆┆b0┆ B System Overview┆05┆RC3931 Communications Processor ↲
╱04002d4e0a00060000000003014c3140000000000000000000000000000000000000000000000000050f19232d37414b555f69737d8791ff04╱
╱04002d4e0a000600000000030c4731400000000000000000000000000000000000000000000000000c16202a343e48525c66707a848e98ff04╱
↓
┆15┆┆b3┆↲
┆15┆┆b1┆┆b0┆ Update 1/86┆05┆Page B.1-┆0b┆ B↲
┆15┆┆b2┆┆b0┆ B Page B.1-┆0b┆┆05┆Update 1/86 ↲
╱04002d4e0a000600000000030c4731400000000000000000000000000000000000000000000000000c16202a343e48525c66707a848e98ff04╱
╱04002d4e0a00060000000003014c3140000000000000000000000000000000000000000000000000050f19232d37414b555f69737d8791ff04╱
↓
┆a1┆B. SYSTEM OVERVIEW↲
↲
The purpose of this main section is to provide a general ↓
understanding of the working of the CP subsystem and to ↓
establish a frame of reference for the specific information ↓
given in main section D on the customization of a CP. The ↓
first section deals with the basic functions: LAN communi┄↓
cation, communication with terminals via RcCircuit, and ↓
download of terminals. The second section deals with IBM ↓
3270 emulation. When defining the functional configuration ↓
of the CP the system administrator may choose to activate or ↓
not activate each of these functions separately.↲
↲
┆a1┆B.1 Basic Functions↲
↲
The software modules performing the basic functions are ↓
included among the files (SW3901) which are installed ↓
together with the RC3931 hardware.↲
↲
┆a1┆LAN Communication↲
↲
When an RC39 MUCS is attached to a local area network, all ↓
messages transmitted to or received from other units on the ↓
LAN pass through the CP. The CP provides a complete ↓
transport service allowing communication for several ↓
independent purposes to take place simultaneously on the ↓
LAN.↲
The basic transport service allows programs running on ↓
separate units attached to the LAN to exchange data messages ↓
(blocks of data). LAN communication is also used in ↓
conjunction with IBM 3270 emulation when devices are ↓
emulated on PCs or when an RC8000 mainframe computer is ↓
connected to the CP using local links (see section B.2).↲
↲
════════════════════════════════════════════════════════════════════════
↓
┆a1┆RcCircuit Communication↲
↲
The transport service mentioned under LAN communication ↓
above is extended to programs running on terminals connected ↓
to the RC39 MUCS by means of RcCircuit. This block-mode ↓
communication is different from the character-at-a-time ↓
communication which is used when terminals log in to the ↓
(XENIX) operating system or application programs running on ↓
the RC39 LAP. It utilizes a separate twisted wire pair in ↓
the RcCircuit cable.↲
The twisted pair used for block-mode communication is ↓
referred to as RcCircuit-I, while the pair used for ↓
character-mode communication is referred to as RcCircuit-II.↲
Block-mode communication on the RcCircuit-I is the basis ↓
for all terminal-oriented functions involving the CP. ↓
Specifically, it is used for downloading and for 3270 ↓
emulation.↲
↲
┆a1┆Terminal Download↲
↲
RC45 and RC855 terminals may be connected to the CP and to ↓
the RC39 MUCS in general by means of the RcCircuit. These ↓
terminals are based on a soft-programmed microcomputer. In ↓
order to perform a useful function they must therefore be ↓
loaded with a program. A terminal may be configured to ↓
expect its program to be downloaded from a CU which may be ↓
an RC890 or RC891 CU, or the CP. In the latter case the ↓
program is transferred from a file on the RC39 disk to the ↓
program execution memory of the terminal by transmission on ↓
the RcCircuit-I.↲
Alternatively, terminals may be configured to load from ↓
built-in permanent memory (PROM) or from a local diskette ↓
unit (RC855 only).↲
Download is a little slower than load from a built-in ↓
PROM, but more flexible, since several different terminal ↓
programs may be downloaded to the same terminal, e.g. an IBM ↓
3270 emulator to be used in cooperation with a CU (i.e. the ↓
┆8c┆┆83┆┆bc┆↓
3274 CU emulator function of the CP) and an ANSI X3.64 ↓
terminal program used when the terminal is to communicate ↓
with the RC39 LAP.↲
The selection of the program to be downloaded to a termi┄↓
nal is made by means of a menu. The default menus are very ↓
simple. However, menus may be extended by the system ↓
administrator.↲
It is possible for one emulator program to appear more ↓
than once in the same menu in different disguises. This is ↓
meaningful if different parameters are supplied for the ↓
program in each instance, causing it to behave differently. ↓
See section B.2, Host line selection, for a description of ↓
how parameters are used with the 3270 emulator programs.↲
Terminal menus may be customized for each installation, ↓
see section D.2, Download menus. It is possible to specify a ↓
different menu for each individual terminal. It is also ↓
possible, independent of the functional configuration of the ↓
CP, to install additional terminal programs and include them ↓
in the menu for any desired terminal.↲
════════════════════════════════════════════════════════════════════════
↓
↲
════════════════════════════════════════════════════════════════════════
↓
┆14┆┆b3┆↲
┆14┆┆b1┆┆b0┆ RC3931 Communications Processor┆05┆System Overview B↲
┆14┆┆b2┆┆b0┆ B System Overview┆05┆RC3931 Communications Processor ↲
┆15┆┆b3┆↲
┆15┆┆b1┆┆b0┆ Update 0/85┆05┆Page B.2-┆0b┆ B↲
┆15┆┆b2┆┆b0┆ B Page B.2-┆0b┆┆05┆Update 0/85 ↲
╱04002d4e0a000600000000030c4731400000000000000000000000000000000000000000000000000c16202a343e48525c66707a848e98ff04╱
╱04002d4e0a000600000000030c4731400000000000000000000000000000000000000000000000000c16202a343e48525c66707a848e98ff04╱
↓
┆a1┆B.2 IBM 3270 Emulation↲
↲
Together with a number of terminals and/or personal compu┄↓
ters the CP may emulate an IBM 3274 Control Unit with a ↓
cluster of attached devices. This emulation requires the ↓
3270 emulation software modules to be installed and running ↓
on the CP, and similarly each terminal or PC which is to ↓
emulate one or more 3270 devices must run the appropriate ↓
emulator. In the context of 3270 emulation we use the ↓
abbreviation CU to refer to the CP.↲
The emulation system provides a number of functions beyond ↓
those of a traditional 3270-type device cluster. However, ↓
the central purpose remains: to allow communication to take ↓
place between a host computer-based application and a number ↓
of devices. The devices may be printers or displays with ↓
keyboards; they may also include "soft devices", i.e. ↓
software modules with no direct physical representation.↲
↲
┆a1┆Linking the CU to a host computer↲
↲
A link is needed between the CU and the host computer in ↓
order to exchange data between the application program ↓
running on the host and devices attached to the CU. Such a ↓
link may be established in several different ways, and a CU ↓
may support communication on several links simultaneously.↲
The concept of a ┆a1┆host link┆e1┆ is important in order to under┄↓
stand the host link menus and link names that occur in the ↓
emulation system, particularly when the CU is configured and ↓
customized to support multiple links.↲
A host link may be ┆a1┆remote┆e1┆, utilizing telephone lines or a ↓
public data network, or ┆a1┆local┆e1┆, utilizing a LAN.↲
↲
┆a1┆Multiple links↲
When the CU supports multiple links simultaneously it must ↓
establish correspondences between active devices and links. ↓
We say that a device is attached to a link. In general, any ↓
device may be attached to any link, but not to more than one ↓
┆8c┆┆83┆┆bc┆↓
link at a time. A display device is always attached to a ↓
link; an idle printer need not be.↲
When a device is attached to a given host link, the CU ↓
will report to other hosts attempting to access the device ↓
that it is unavailable, as if it were switched off.↲
In some cases the host may later be notified when the ↓
device becomes available, e.g. when a printer has completed ↓
its operation.↲
↲
┆a1┆Host link selection↲
Consider the situation when an emulated display device ↓
belonging to a cluster with multiple host links is activated ↓
in a terminal or PC. The CU must then attach the device to a ↓
host link. This is done by presenting a menu on the terminal ↓
display allowing the operator to select any one of the host ↓
links.↲
Host links must therefore have names which can be shown in ↓
the host link menu. The name of the host link to which the ↓
device is attached is shown in the status line of the ↓
display during normal emulator operation.↲
If there is only one host link, an activated display ↓
device is automatically attached to this link. No menu is ↓
shown, but the link name will appear in the status line.↲
For remote links, the link names may be defined as part of ↓
CU customization. For local links, the names are received ↓
from the host, and cannot be changed at the CU.↲
↲
┆a1┆Skipping the host link menu┆e1┆. It is possible to supply a host ↓
link name as a parameter when the 3270 emulator program for ↓
RC45 or RC855 terminal is loaded. If such a name is present ↓
the emulator will skip the menu presentation and automa┄↓
tically attach the device to the link. This feature is only ↓
relevant if multiple links exist. See the description of ↓
download menu customization (section D.2, Download menus) ↓
for information on how to pass parameters to the terminal ↓
emulators.↲
↲
┆8c┆┆83┆┆bc┆↓
┆a1┆Remote host links↲
A remote host link can be established via a permanent ↓
(leased) or dial-up telephone line to the host computer. The ↓
CU must be connected to the telephone line by means of a ↓
modem according to CCITT interface standard V.24.↲
Alternatively, a remote host link can be established via a ↓
circuit-switched public data network. In this case the CU ↓
must be connected to the network by means of a DCE according ↓
to CCITT interface standard X.21.↲
The communication protocol used on the host link can be ↓
either BSC or SNA/SDLC.↲
↲
┆a1┆IBM-compatible links┆e1┆. Three combinations of line kind and ↓
protocol, viz. V.24-BSC, V.24-SNA/SDLC and X.21-SNA/SDLC, ↓
enable the CU to communicate with standard IBM products and ↓
compatible products from other vendors. In these cases there ↓
is a one-to-one relationship between the modem (V.24 signal ↓
cable) or DCE (X.21 signal cable) and a host link. Notice ↓
that such a host link may provide access to several appli┄↓
cations running on the same host computer, or in fact to ↓
several host computers in the case of an SNA network. ↓
However, from the point of view of the CU and the terminal ↓
emulator there is only one host link.↲
The CU communicates with each remote host as if it were an ↓
IBM 3274 control unit. When multiple host links exist the ↓
hosts need not be aware of each other.↲
↲
┆a1┆X.21-BSC┆e1┆. The fourth combination of line kind and protocol, ↓
X.21-BSC, is not supported by IBM or IBM-compatible vendors. ↓
This combination therefore requires a special front-end (FE) ↓
computer, the RC3803, at the host site. By utilizing the ↓
fast switching capability of the public network - assuming ↓
it is indeed fast - to hold a line only when there is actual ↓
data traffic, the CU is able to maintain communication with ↓
up to 4 FEs simultaneously per DCE, i.e. per X.21 subscriber ↓
attachment (in IBM termi┄nology this technique is referred to ↓
as "short-hold mode with multiple port sharing").↲
┆8c┆┆83┆┆bc┆↓
As in the case of IBM-compatible links we shall refer (in ↓
main sections D and E) to the connection between the CU and ↓
the X.21 DCE as a link. However, with respect to host link ↓
selection this link has up to four ┆a1┆sublinks┆e1┆, one per RC3803 ↓
FE, each with its own link name.↲
↲
┆a1┆Dual host configuration┆e1┆. The CU may be configured with ↓
connections to one or two modems or X.21 DCEs. A config┄↓
uration with two such connections is referred to as "dual ↓
host". The various combinations of line kind and protocol ↓
may be freely mixed on the two connections of a dual host ↓
configured CU. It should be clear from the discussion above ↓
that if the X.21-BSC combination is used on (at least) one ↓
of the two connections the number of host links may be ↓
greater than two. The phrase "dual host" is therefore ↓
slightly misleading.↲
Figure B-1 shows an example configuration with three ↓
remote host links.↲
↲
┆a1┆Local host links↲
Local host links are established on a LAN. The host computer ↓
must be an RC8000 attached to the LAN by means of a so-↓
called Attached Device Processor (ADP). The number of host ↓
links is customized in the ADP. It is possible to customize ↓
so that each one of possibly several applications on the ↓
RC8000 host has its own link. Local links are logical in ↓
nature since they all share the same physical LAN.↲
↲
┆a1┆Emulated 3270 devices↲
↲
3270-type devices can be emulated on several different kinds ↓
of equipment which of course must be connected to the CU. ↓
The different emulators may be freely combined in a cluster.↲
An RC45 or RC855 terminal, which is connected to the CU ↓
via RcCircuit and runs the 3270 emulator program, supports ↓
up to two display devices and one printer device. Only one ↓
┆8c┆┆83┆┆b0┆↓
┆0e┆↓
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
╞ < Figure B-1 >↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
┆0f┆↓
of the display devices is visible, but the operator can ↓
switch display device at any time.↲
A PC, which is connected to the CU via a LAN and runs its ↓
version of the 3270 emulator program, supports up to four ↓
display devices and four printer devices. Normally, the ↓
operator sees only one display device at a time, but can ↓
switch among them. By means of windows, parts of two or more ↓
display devices may be visible simultaneously. It is not ↓
possible to connect four printers directly to the same PC, ↓
so some of them may be reached via re-routing through the ↓
════════════════════════════════════════════════════════════════════════
↓
LAN. This re-routing is handled by the emulator program ↓
running on the PC and is unknown to the CU.↲
In addition to emulated devices which are mapped to ↓
physical devices by emulator programs in terminals or PCs, ↓
the CP itself may be configured to maintain a number of ↓
"soft devices". The soft devices have no physical mani┄↓
festation, but they behave exactly like other devices toward ↓
the host. Operations on soft devices can be performed by ↓
application programs running on the RC39 LAP or possibly on ↓
another processor connected to the CP by a LAN. The soft ↓
devices allow such programs to access host computers as if ↓
they were terminal operators.↲
An example system with several different kinds of emulated ↓
devices is shown in Figure B-2. The letter D indicates a ↓
display device and the letter P a printer device.↲
The device numbers used to address the individual devices ↓
in an emulated 3270 cluster are in general ┆a1┆not┆e1┆ customized ↓
as parameters of the CU, but as parameters of the units, ↓
i.e. terminals or PCs, where the devices reside. Soft ↓
devices, however, are customized as CP parameters, since ↓
these devices do reside within the CP.↲
This customization method is intended to be flexible and ↓
easy to use: it is not necessary to change the customization ↓
of the CU because a new terminal is added to the cluster. As ↓
a consequence, the CU, when it begins operation upon load, ↓
has no knowledge of the device configuration of the cluster. ↓
If configuration errors exist, i.e. if the same device ↓
number has been used for emulated devices in two or more ↓
units or twice in the same unit, this will not be uncovered ↓
until both devices become active simultaneously. When such a ↓
situation arises, the CU will reject the second device which ↓
attempts to use the contested device number.↲
┆8c┆┆83┆┄↓
┆0e┆↓
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
╞ < Figure B-2 >↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
┆0f┆↓
════════════════════════════════════════════════════════════════════════
↓
↓
════════════════════════════════════════════════════════════════════════
↓
┆14┆┆b3┆↲
┆14┆┆b1┆┆b0┆ RC3931 Communications Processor┆05┆Software Installation C↲
┆14┆┆b2┆┆b0┆ C Software Installation┆05┆RC3931 Communications Processor ↲
┆15┆┆b3┆↲
┆15┆┆b1┆┆b0┆ Update 1/86┆05┆Page C-┆0b┆ C↲
┆15┆┆b2┆┆b0┆ C Page C-┆0b┆┆05┆Update 1/86 ↲
╱04002d4e0a000600000000030c4731400000000000000000000000000000000000000000000000000c16202a343e48525c66707a848e98ff04╱
╱04002d4e0a000600000000030c4731400000000000000000000000000000000000000000000000000c16202a343e48525c66707a848e98ff04╱
↓
┆a1┆C. Software Installation↲
↲
Like other SW packages for the RC39 MUCS the packages for ↓
the CP are distributed on diskettes. There is a general SW ↓
installation utility program for the RC39 MUCS which is used ↓
to move the files present on a distribution diskette to the ↓
disk of the RC39 system. This program is also used for the ↓
SW packages involving the CP, including programs to be ↓
downloaded to terminals. It helps the person installing a SW ↓
package by prompting, instructing, and displaying informa┄↓
tive messages as it goes along. A general description of the ↓
installation procedure is found in ref. 1.↲
The installation program may be entered through the system ↓
administration menu or simply by logging in to the XENIX ↓
operating system as root (super user) and typing the install ↓
command.↲
↲
┆a1┆After installation↲
↲
In most situations it will be necessary to customize an ↓
installed package after the files have been read. A detailed ↓
discussion of this subject is found in main section D. Only ↓
some hints about the most important items are given here.↲
Note that after installation and customization the CP must ↓
be reset before the new functions can be used, cf. section ↓
E, Resetting the CP.↲
↲
┆a1┆SW3882 (ANSI X3.64 terminal ↓
┆19┆┄┄┆84┆program)┆e1┆: Check that all terminals can be downloaded; try to ↓
load the ANSI X3.64 terminal program. If unsuccessful, check ↓
that the secondary address of the failing terminal is in the ↓
range 0..15.↲
↲
════════════════════════════════════════════════════════════════════════
↓
┆a1┆SW3802 (Teletex)┆e1┆: Make sure the signal cables are correctly ↓
mounted, connecting the CP to the X.21 DCE, cf. section E, ↓
External cable connections.↲
↲
┆a1┆SW3803 and SW3881 (3270 emulation)┆e1┆: Check device numbers in all ↓
terminals using the downloaded configurator (not one loaded ↓
from PROMs in the terminal), cf. section E, Device number ↓
management.↲
Update the configuration file (CONFIG.CST) to include the ↓
appropriate 3270 configuration switch(es).↲
Update the parameters for the remote host link(s) in the ↓
file COMM.CST, cf. sections D.2, Parameters for BSC links ↓
and/or Parameters for SNA/SDLC links. Unless the kind of the ↓
link(s) (V.24/X.21) is specified appropriately and the CU ↓
number (BSC) and SDLC address (SNA/SDLC) and other essential ↓
communication parameter are correctly specified, communi┄↓
cation cannot take place. The parameters which can be ↓
specified in the remaining *.CST files are less critical.↲
Make sure the signal cables are correctly mounted, ↓
connecting the CP to the V.24 modem or X.21 DCE, cf. section ↓
E, External cable connections.↲
↲
┆a1┆SW3804 (3270 programmer's toolkit)┆e1┆: Select and customize ↓
device numbers for soft devices, cf. section E, Device ↓
number management, and D.2, Soft devices.↲
Activate the soft device function by setting the SOFTDEV ↓
switch in the configuration file (CONFIG.CST), cf. section ↓
D.1, Soft devices.↲
════════════════════════════════════════════════════════════════════════
↓
┆14┆┆b3┆↲
┆14┆┆b1┆┆b0┆ RC3931 Communications Processor┆05┆System Customization D↲
┆14┆┆b2┆┆b0┆ D System Customization┆05┆RC3931 Communications Processor ↲
┆15┆┆b3┆↲
┆15┆┆b1┆┆b0┆ Update 1/86┆05┆Page D.1-┆0b┆ D↲
┆15┆┆b2┆┆b0┆ D Page D.1-┆0b┆┆05┆Update 1/86 ↲
╱04002d4e0a000600000000030c4731000000000000000000000000000000000000000000000000000c16202a343e48525c66707a848e98ff04╱
╱04002d4e0a000600000000030c4731400000000000000000000000000000000000000000000000000c16202a343e48525c66707a848e98ff04╱
↓
┆a1┆D. System Customization↲
↲
The RC3931 Communications Processor can be configured and ↓
customized in a simple and flexible manner. All information ↓
concerning the configuration and customization of a CP is ↓
collected in a number of text files which are read by the CP ↓
when its software is loaded.↲
The term configuration is used to refer to the selection ↓
of functions in a given CP system. The configuration of a CP ↓
determines which software modules are loaded and activated. ↓
By customization, on the other hand, we refer to the control ↓
at a detailed level of operational parameters for the ↓
modules which have been selected for a configuration.↲
There is one file, the ┆a1┆configuration file┆e1┆, which contains ↓
a description of the CP configuration, and a number of ↓
files, the ┆a1┆parameter files┆e1┆, which contain specifications of ↓
customization parameters. This main section is concerned ↓
with the form and meaning of the contents of these files. ↓
Practical aspects, such as finding the files and editing ↓
them, are discussed in main section E.↲
Whenever the CP is reset (cf. section E, Resetting the ↓
CP), an initial program is executed which reads the con┄↓
figuration file, determines which software modules to load, ↓
and then reads the parameter files to obtain parameters for ↓
the activation of these modules. Default values for all the ↓
parameters are built into the initial program, and these ↓
values remain in effect in all cases where no modification ↓
is read from the appropriate parameter file. Consequently, ↓
the parameter files need only contain specifications of ↓
deviations from the default parameter values for those ↓
functions which are active.↲
As a general rule all the files have a name of the form ↓
*.CST, where * stands for some sequence of letters, and CST ↓
is intended as a mnemonic for "CuSTomization". Similarly the ↓
* part of the name is chosen so as to give a clue to the ↓
subject of the contents of the file.↲
════════════════════════════════════════════════════════════════════════
↓
Another rule is that semicolons (;) may be used in the ↓
files to introduce comments; i.e. the part of a text line ↓
which follows a semicolon is ignored, when the files are ↓
read during load of the CP, and may contain explanatory ↓
information for the system administrator who will be ↓
responsible for editing the files.↲
↲
┆a1┆D.1 Configuration↲
↲
The significant part of the configuration file - excluding ↓
comments - is a list of so-called configuration switches, ↓
each of which causes a particular function or set of ↓
functions to be activated or deactivated. Syntactically, a ↓
configuration switch is just a sequence of characters. In ↓
the list, the configuration switches may be separated by ↓
commas (,) and/or newline characters.↲
Configuration switches requesting functions for which the ↓
necessary software has not been installed will, in general, ↓
not have any effect.↲
The name of the configuration file is CONFIG.CST. The ↓
distributed version of this file is empty. There is another ↓
file, DEFAULT.CFG, which contains a number of comment lines ↓
explaining how to set configuration switches. The intention ↓
is that the user (system administrator) may create the ↓
proper configuration file by editing the DEFAULT.CFG file. ↓
The remaining part of this section goes into more detail ↓
than the explanation found in the distributed file.↲
↲
┆a1┆Basic functions↲
↲
The basic transport service across a LAN is activated by the ↓
configuration switch LAN.↲
The other basic functions: RcCircuit-I communication and ↓
download to terminals are activated by default, since they ↓
are normally always required to be active. It is possible to ↓
deactivate these functions by means of the configuration ↓
switches -1CIRC and -MDLL, respectively. Beware, however, ↓
┆8c┆┆83┆┆bc┆↓
that deactivation of RcCircuit-I commu┄nication will disable ↓
any form of communication between terminals and the CP.↲
↲
┆a1┆IBM 3270 emulation↲
↲
There are two aspects of 3270 emulation which are configured ↓
independently: 1) the ability to communicate with one or ↓
more host computers via one or more links, and 2) soft ↓
devices which reside within the CP and may be accessed from ↓
programs running on the RC39 LAP or other processors ↓
attached to the LAN (if there is one).↲
↲
┆a1┆Remote host links↲
A "dual host" configuration is one which supports two remote ↓
links (with possible sublinks in the X.21-BSC case). For ↓
each link there is a connection to a V.24 modem or an X.21 ↓
DCE. A "high performance" configur┄ation supports only one ↓
remote link, but allows a data transfer rate up to 19200 ↓
bps. The maximum data transfer rate in dual host as well as ↓
ordinary single host configur┄ations is 9600 bps.↲
Because the protocols BSC and SNA/SDLC are handled by ↓
different software modules, protocol selection is also a ↓
configuration issue, whereas line kind selection (V.24 or ↓
X.21) is handled by means of a customization parameter.↲
There are seven configuration switches which activate 3270 ↓
emulation with remote link support. At most one of these may ↓
be present in the configuration file. The switches are:↲
↲
┆a1┆conf.switch╞ description╞ ╞ ↲
3270B╞ Single host BSC, ordinary↲
3270BH╞ Single host BSC, high performance↲
3270BD╞ Dual host, both BSC↲
3270S╞ Single host SNA/SDLC, ordinary↲
3270SH╞ Single host SNA/SDLC, high performance↲
3270SD╞ Dual host, both SNA/SDLC↲
3270BS╞ Dual host, one BSC, one SNA/SDLC↲
↲
┆8c┆┆83┆┆bc┆↓
In order to distinguish the links in dual host configur┄↓
ations the specifications of customization parameters (see ↓
section D.2) use the concept of a link number which can be 1 ↓
or 2. Link number 2 will apply only to dual host configur┄↓
ations where the same protocol is used for both links ↓
(3270BD or 3270SD). In single host configurations and mixed ↓
protocol dual host configurations the link/both links is/are ↓
defined to be link number 1, and the link number may be ↓
omitted from parameter specifications as it is not needed to ↓
identify the link (the BSCID and BSCXNO parameters are ↓
exceptions from this general rule).↲
↲
┆a1┆Local host links↲
The configuration switch CULANI (3270 ┆a1┆CU┆e1┆ emulation with ┆a1┆LAN┆e1┆ ↓
┆a1┆I┆e1┆nterface) will activate 3270 emulation with support for ↓
local host links. This switch may be present together with ↓
any one of the switches mentioned under remote host links, ↓
or with none of them.↲
↲
┆a1┆Soft devices↲
The configuration switch SOFTDEV will activate one or more ↓
soft 3270 devices. The device numbers of soft devices must ↓
be specified by a customization parameter. Unless either ↓
remote or local host links are also activated, the soft ↓
devices will not be able to communicate with a host.↲
↲
┆a1┆Teletex↲
↲
The Teletex service is activated by the configuration switch ↓
TTX.↲
════════════════════════════════════════════════════════════════════════
↓
┆14┆┆b3┆↲
┆14┆┆b1┆┆b0┆ RC3931 Communications Processor┆05┆System Customization D↲
┆14┆┆b2┆┆b0┆ D System Customization┆05┆RC3931 Communications Processor ↲
┆15┆┆b3┆↲
┆15┆┆b1┆┆b0┆ Update 1/86┆05┆Page D.2-┆0b┆ D↲
┆15┆┆b2┆┆b0┆ D Page D.2-┆0b┆┆05┆Update 1/86 ↲
╱04002d4e0a000600000000030c4731400000000000000000000000000000000000000000000000000c161b202a343e48525c66707a848eff04╱
╱04002d4e0a000600000000030c4731000000000000000000000000000000000000000000000000000c16202a343e48525c66707a848e98ff04╱
↓
┆a1┆D.2 Customization, Parameter Files↲
↲
In order to simplify the task of customization by text file ↓
editing, the customization parameters have been divided into ↓
groups according to subject. A parameter file is defined for ↓
each group of parameters. A value for a given parameter must ↓
be specified in the file to which the parameter has been ↓
assigned. If a parameter specification is placed in a wrong ↓
file it will have no effect.↲
There are five parameter files. These, and the associated ↓
╱04002d4e0a000600000000020c4731000000000000000000000000000000000000000000000000000c161b202a343e48525c66707a848eff04╱
╱04002d4e0a000600000000030c4731400000000000000000000000000000000000000000000000000c161b202a343e48525c66707a848eff04╱
↓
subjects are:↲
↲
╱04002d4e0a000600000000030c4731000000000000000000000000000000000000000000000000000c161b202a343e48525c66707a848eff04╱
╱04002d4e0a000600000000020c4731000000000000000000000000000000000000000000000000000c161b202a343e48525c66707a848eff04╱
↓
MENUDL.CST╞ Download menus.↲
CONV1.CST╞ ╞ Conversion between EBCDIC character code used↲
(CONV.CST)╞ for transmission on remote host links and the↲
CONV2.CST╞ ╞ ┆84┆internal character code used by the CP and ↓
┆19┆┆8f┆┄┄emulated 3270 devices.↲
TEXTS.CST╞ ╞ Texts for status lines and host link menus.↲
COMM.CST╞ ╞ ┆84┆Communication, both local and remote, and ↓
┆19┆┆8f┆┄┄device cluster control.↲
↲
┆a1┆Parameter file syntax↲
↲
Each line in one of the parameter files contains the speci┄↓
fication of a parameter value, or just a comment if the line ↓
begins with a semicolon. A parameter specification line ↓
always begins with the name of the parameter, which is a ↓
sequence of letters (at most 8), possibly followed by some ↓
further information to identify the desired parameter, ↓
typically an index when several similar parameters are ↓
organized in a table. Then follows an equals sign and the ↓
value to be used for the parameter in question.↲
In the subsections dealing with the individual parameter ↓
files each parameter specification line is shown in a ↓
generic form which indicates the proper syntax. In these ↓
lines parentheses are used to delimit optional parts, ↓
slashes (/) to delimit alternatives, and words or phrases ↓
════════════════════════════════════════════════════════════════════════
↓
written in small case letters to indicate parts whose syntax ↓
is explained in subsequent paragraphs.↲
On the other hand, the parameter name which occurs at the ↓
beginning of each parameter line written in capital letters, ↓
comma (,), equals sign (=) and binary digits (0/1) shall be ↓
used literally in actual parameter lines.↲
Whenever a parameter specification includes a text ↓
(character string), each character following the preceeding ↓
delimiter (comma or equals sign) is significant, i.e. a ↓
character string may include leading blanks. On the other ↓
hand, a numeric parameter may be preceeded by blanks, which ↓
in this case have no significance.↲
In the following subsections, the generic form of each ↓
parameter specification line is shown as the part to the ↓
right of the colon in the headline introducing the de┄↓
scription of the parameter.↲
↲
┆a1┆Download menus (MENUDL.CST)↲
↲
The menu-based terminal downloader identifies terminals by ↓
their addresses as secondary stations on the RcCircuit-I (SA ↓
parameter in the configuration of the terminal). The default ↓
menus are identical for all terminals. Figure D-1 shows the ↓
default menu as it appears on a terminal. Three texts frame ↓
╱04002d4e0a000600000000020c4731000000000000000000000000000000000000000000000000000c161b202a343e48525c66707a848eff04╱
╱04002d4e0a000600000000030c4731000000000000000000000000000000000000000000000000000c161b202a343e48525c66707a848eff04╱
↓
the menu:↲
↲
╱04002d4e0a000600000000030c4731000000000000000000000000000000000000000000000000000c161b202a343e48525c66707a848eff04╱
╱04002d4e0a000600000000020c4731000000000000000000000000000000000000000000000000000c161b202a343e48525c66707a848eff04╱
↓
1. TERMINAL FUNCTION MENU↲
2. Key Description↲
╱04002d4e0a000600000000020c4731000000000000000000000000000000000000000000000000000c161b202a343e48525c66707a848eff04╱
╱04002d4e0a000600000000030c4731000000000000000000000000000000000000000000000000000c161b202a343e48525c66707a848eff04╱
↓
3. Press function key to select application↲
↲
╱04002d4e0a000600000000030c4731000000000000000000000000000000000000000000000000000c161b202a343e48525c66707a848eff04╱
╱04002d4e0a000600000000020c4731000000000000000000000000000000000000000000000000000c161b202a343e48525c66707a848eff04╱
↓
These "frame texts" appear in fixed positions on the ↓
display, but may be modified using the FTEXT parameter ↓
specification. They will appear identically on all terminals ↓
connected to the CU. The key names (PF1, PF2, PF3) cannot be ↓
modified; they correspond to engravings on the keys. Each ↓
line centered underneath the two frame lines at the top ↓
represents a terminal program which can be selected for↲
════════════════════════════════════════════════════════════════════════
↓
╞ ╞ TERMINAL FUNCTION MENU↲
↲
╞ ╞ Key Description↲
↲
╞ ╞ PF1 ANSI X3.64 Terminal↲
╞ ╞ PF2 IBM 3270 Emulator↲
╞ ╞ PF3 Terminal Configurator↲
↲
↲
↲
↲
↲
↲
Press function key to select application↲
↲
↲
Figure D-1. Default terminal download menu.↲
↲
download. The CU must know three things, each represented by ↓
╱04002d4e0a000600000000020c4731000000000000000000000000000000000000000000000000000c161b202a343e48525c66707a848eff04╱
╱04002d4e0a000600000000030c4731000000000000000000000000000000000000000000000000000c161b202a343e48525c66707a848eff04╱
↓
a character string, about a terminal program:↲
↲
╱04002d4e0a000600000000030c4731000000000000000000000000000000000000000000000000000c161b202a343e48525c66707a848eff04╱
╱04002d4e0a000600000000020c4731000000000000000000000000000000000000000000000000000c161b202a343e48525c66707a848eff04╱
↓
1. ┆84┆A file name whereby the file containing the program to be ↓
┆19┆┆83┆┄┄downloaded will be retrieved. These names are automati┄↓
┆19┆┆83┆┄┄cally extended with ".855" or ".S45" for an RC855 or RC45 ↓
┆19┆┆83┆┄┄terminal, respectively, to obtain the actual file name. ↓
┆19┆┆83┆┄┄For example, if the file name is specified as CONFI the ↓
┆19┆┆83┆┄┄actual name of the program file which is downloaded to an ↓
┆19┆┆83┆┄┄RC45 terminal is CONFI.S45. Because of the automatic ↓
┆19┆┆83┆┄┄extension, the same terminal program specifications may ↓
╱04002d4e0a000600000000020c4731000000000000000000000000000000000000000000000000000c161b202a343e48525c66707a848eff04╱
╱04002d4e0a000600000000030c4731000000000000000000000000000000000000000000000000000c161b202a343e48525c66707a848eff04╱
↓
┆19┆┆83┆┄┄be used for both RC855 and RC45 terminals.↲
↲
╱04002d4e0a000600000000030c4731000000000000000000000000000000000000000000000000000c161b202a343e48525c66707a848eff04╱
╱04002d4e0a000600000000020c4731000000000000000000000000000000000000000000000000000c161b202a343e48525c66707a848eff04╱
↓
2. ┆84┆A description to appear in the menu line representing the ↓
╱04002d4e0a000600000000020c4731000000000000000000000000000000000000000000000000000c161b202a343e48525c66707a848eff04╱
╱04002d4e0a000600000000030c4731000000000000000000000000000000000000000000000000000c161b202a343e48525c66707a848eff04╱
↓
┆19┆┆83┆┄┄terminal program, e.g. "IBM 3270 Emulator".↲
↲
╱04002d4e0a000600000000030c4731000000000000000000000000000000000000000000000000000c161b202a343e48525c66707a848eff04╱
╱04002d4e0a000600000000020c4731000000000000000000000000000000000000000000000000000c161b202a343e48525c66707a848eff04╱
↓
3. ┆84┆(optional) A parameter to be supplied to the terminal ↓
┆19┆┆83┆┄┄program subsequent to download. See section B.2, Skipping ↓
┆19┆┆83┆┄┄the host link menu, for a description of how the 3270 ↓
┆19┆┆83┆┄┄terminal emulators use such a parameter.↲
↲
════════════════════════════════════════════════════════════════════════
↓
┆a1┆Frame text┆e1┆: FTEXT,ftno=text↲
FTEXT specifies one of the frame texts of the download menu. ↓
Ftno is a number: 1, 2 or 3, which identifies the particular ↓
text. The numbering is as indicated above for the default ↓
texts. The text may be at most 45 characters long.↲
↲
┆a1┆Error text┆e1┆: ETEXT,etno=text↲
ETEXT specifies a text which may occur as an error message ↓
in the status (bottom) line of the terminal in case of an ↓
error during download. Etno must be a number in the range ↓
1..4, and the text may be at most 25 characters long. The ↓
four default texts are shown in the example below. The error ↓
situations they refer to are described in section F, Error ↓
messages during download.↲
↲
┆a1┆Terminal program┆e1┆: TPRG,tpno=fname,desc(,param)↲
TPRG specifies a terminal program which may be referred to ↓
in terminal menu specifications (TMENU, see below) by its ↓
number, given as tpno, which must be in the range 0..25. ↓
Thus there can be at most 26 terminal programs. Fname is the ↓
file name, at most 8 characters; desc is the description, at ↓
most 25 characters; the optional part param is the character ↓
string which, if present, will be passed to the downloaded ↓
program, at most 89 characters.↲
If fname is specified as A: no program will be downloaded; ↓
instead the terminal, which must be an RC855 workstation, ↓
will load the CP/M operating system from the local diskette. ↓
A program to be loaded from the floppy disk may be specified ↓
in the param part using capital letters. This feature may be ↓
used to combine local programs with down┄loaded programs ↓
providing a unified method of selecting ↓
╱04002d4e0a000600000000020c4731000000000000000000000000000000000000000000000000000c161b202a343e48525c66707a848eff04╱
╱04002d4e0a000600000000030c4731000000000000000000000000000000000000000000000000000c161b202a343e48525c66707a848eff04╱
↓
terminal function. Example:↲
↲
TPRG,7=A:,RcTekst,RCTEKST↲
↲
╱04002d4e0a000600000000030c4731000000000000000000000000000000000000000000000000000c161b202a343e48525c66707a848eff04╱
╱04002d4e0a000600000000020c4731000000000000000000000000000000000000000000000000000c161b202a343e48525c66707a848eff04╱
↓
The same file name may be used in several terminal program ↓
specifications. This can be meaningful if the desc and param ↓
parts are different.↲
↲
┆8c┆┆83┆┆c4┆↓
┆a1┆Terminal menu┆e1┆: TMENU,secaddr=tpnolist↲
TMENU specifies the menu for a terminal whose secondary ↓
address is given as secaddr, a number in the range 0..31. ↓
Tpnolist is a list of terminal program numbers. It must ↓
consist of numbers which have appeared in TPRG parameter ↓
specification lines prior to the TMENU line. The numbers ↓
must be separated by commas.↲
A number may be immediately preceeded by D to indi┄cate a ↓
default terminal program. If a terminal is configured for ↓
default download and its menu contains a default terminal ↓
program, then no menu is shown when the terminal is powered ↓
on or reset. Instead, the default program is loaded without ↓
requiring selection by the operator.↲
↲
┆a1┆Example↲
As an example, the following lines could be used to specify ↓
the default menu (also found in the distributed file ↓
DEFAULT.MDL):↲
↲
FTEXT,1=TERMINAL FUNCTION MENU; default download menu↲
FTEXT,2=Key Description↲
FTEXT,3=Press function key to select application↲
ETEXT,1=Disk access error↲
ETEXT,2=CU disconnected↲
ETEXT,3=Checksum error↲
ETEXT,4=Program not found↲
TPRG,0=CONFI,Terminal Configurator↲
TPRG,1=3270,IBM 3270 Emulator↲
TPRG,2=ANSI,ANSI X3.64 Terminal↲
TMENU,0=D2,1,0↲
TMENU,1=D2,1,0↲
TMENU,2=D2,1,0↲
TMENU,3=D2,1,0↲
...↲
TMENU,31=D2,1,0↲
↲
════════════════════════════════════════════════════════════════════════
↓
┆a1┆Conversion tables (CONV1.CST, CONV2.CST)↲
↲
Two different kinds of character encoding are used by the ↓
3270 emulation system. Externally, when characters are ↓
transmitted on remote host links in BSC or SNA/SDLC ↓
protocol, the character code is EBCDIC according to IBM ↓
convention. Displayable characters have EBCDIC codes in the ↓
range 64..255 (40┆82┆Hex┆81┆..FF┆82┆Hex┆81┆). Internally, when characters ↓
are stored and manipulated in device buffers within the CU ↓
as well as by terminal emulator programs, characters have ↓
codes in accordance with ISO standard 646 (7-bit coded ↓
character set for information processing interchange), i.e. ↓
ASCII-like. In this encoding displayable characters have ↓
codes in the range 32..126 (20┆82┆Hex┆81┆..7E┆82┆Hex┆81┆).↲
As a consequence of the two kinds of encoding the CU must ↓
perform a conversion. Characters received from a remote host ↓
are converted from EBCDIC representation to internal code ↓
using a table called the intcode-table (because its output ↓
is internal code). Conversely, before transmission to a ↓
remote host, characters are converted from the internal ↓
representation to EBCDIC using another table, the ebcdic-↓
table.↲
The internal character set, i.e. character repertoire and ↓
encoding, is implemented in terminals by means of character ↓
image generators and tables in PROMs. A number of national ↓
versions of the internal character set are supported with RC ↓
terminal products, see appendix H.2. The character set must ↓
be the same for all terminals in a cluster. Once chosen, it ↓
must be regarded as fixed for the installation.↲
Given the internal character set, the same character ↓
repertoire, or a subset thereof, must necessarily be ↓
employed in communication with remote hosts. However, by ↓
modifying the conversion tables it is possible to customize ↓
the EBCDIC encoding of the available characters.↲
In the case of multiple remote host links (dual host ↓
confi┄guration) it may not be appropriate to use the same ↓
EBCDIC code in communication with all/both hosts. The CU ↓
┆8c┆┆83┆┆bc┆↓
therefore supports two different EBCDIC codes, called EBCDIC ↓
code 1 and EBCDIC code 2, implemented by means of two pairs ↓
of conversion tables, each pair consisting of an intcode ↓
table and an ebcdic table. The EBCDIC code to be used on a ↓
given remote host link is selected by means of the BSCCONV ↓
or SNACONV parameter specification; see the section Commu┄↓
nication parameters (COMM.CST) below.↲
The default conversion, identical for both pairs of ↓
tables, is between US English (ASCII) internal code (see ↓
appendix H.2) and US English EBCDIC code (see appendix H.3). ↓
Each displayable character entry in each of the conversion ↓
tables may be modified by means of an appropriate parameter ↓
specification line. The modifications specifying EBCDIC code ↓
1 are defined in the file CONV1.CST (or in the absence of ↓
such a file, by the file CONV.CST), and those specifying ↓
EBCDIC code 2 in the file CONV2.CST. The same syntax applies ↓
to both of these files; see below.↲
Those modifications to the default conversion tables ↓
which are necessary in order to support a given internal ↓
character set and a corresponding EBCDIC encoding may be ↓
derived from a com┄parison of charts for the codes in ↓
question with the default code charts as shown in the ↓
appendices mentioned above. The number of changes that are ↓
necessary will depend on how different the code charts are ↓
from the default ones.↲
When the internal character sets supported with RC ↓
terminal products and the corresponding standard EBCDIC ↓
encodings are used (see appendix H.3) it is not necessary ↓
for the user to devise conversion table modifications, as ↓
all standard sets of modifications are provided in the form ↓
of files distributed in the basic SW package for the CP (cf. ↓
section E, Selecting character conversion).↲
↲
┆a1┆Conversion to internal code┆e1┆: INTCODE,ecode=icode↲
Each INTCODE parameter line specifies one entry in the ↓
intcode-table. Ecode is the EBCDIC code, i.e. the input to ↓
the table lookup; it must be written as a hexadecimal number ↓
┆8c┆┆83┆┆bc┆↓
in the range 40..FF. Icode is the internal code, i.e. the ↓
output of the table lookup; it must be written as a hexa┄↓
decimal number in the range 20..7E.↲
When a particular EBCDIC code is not used it is appro┄↓
priate to specify the internal code as null (0).↲
↲
┆a1┆Conversion to EBCDIC code┆e1┆: EBCDIC,icode=ecode↲
Each EBCDIC parameter line specifies one entry in the ↓
ebcdic-table. Icode is the internal code, i.e. the input to ↓
the table lookup; it must be written as a hexadecimal number ↓
in the range 20..7E. Ecode is the EBCDIC code, i.e. the ↓
output of the table lookup; it must be written as a hexa┄↓
decimal number in the range 40..FF.↲
↲
┆a1┆Displayable texts (TEXTS.CST)↲
↲
Messages shown to the operator of a terminal or PC which ↓
emulates a 3270 display device in the host link menu or in ↓
the status line may be customized in the file TEXTS.CST. All ↓
the parameters described in this section are specified as ↓
character strings.↲
↲
┆a1┆Host link menu heading┆e1┆: HOSTMENU=htext↲
HOSTMENU specifies the text to be written as a heading in ↓
the host link menu. The maximum length of htext is 32 ↓
characters.↲
The default text is: Host link menu↲
↲
┆a1┆BSC link name┆e1┆: BSCID(,linkno(,sublinkno))=lname↲
BSCID specifies the name of a remote BSC host link or sub┄↓
link.↲
Sublinkno must be present if the link kind is X.21 and ↓
must be left out if it is V.24. If present, it identifies ↓
the sublink and must be a number in the range 1..4.↲
Linkno may be omitted unless the configuration is dual ↓
host with two BSC links. However, in the case of an X.21 ↓
link, i.e. if sublinkno is present, linkno must not be ↓
┆8c┆┆83┆┆bc┆↓
omitted even if there is only one BSC link. It specifies the ↓
number of the link and must be 1 or 2.↲
Lname is the link name which will be shown in the host ↓
link menu and in the status line of display devices which ↓
are attached to the link. The maximum length of lname is 12 ↓
characters.↲
The same name may not be given to two different links.↲
↲
┆a1┆SNA/SDLC link name┆e1┆: SNAID(,linkno)=lname↲
SNAID specifies the name of a remote SNA/SDLC host link.↲
Linkno may be omitted unless the configuration is dual ↓
host with two SNA/SDLC links. It specifies the number of the ↓
link and must be 1 or 2.↲
Lname is the link name which will be shown in the host ↓
link menu and in the status line of display devices which ↓
are attached to the link. The maximum length of lname is 12 ↓
characters.↲
The same name may not be given to two different links.↲
↲
┆a1┆Device status message┆e1┆: DSTEXT,dstno=dsmsg↲
DSTEXT specifies one of the messages which may be shown in ↓
the status line of an emulated 3270 display device to inform ↓
the operator of the status of the display device or of ↓
another device (printer or card reader) on which an ↓
operation was attempted.↲
Dstno is the number of the status message and must be in ↓
the range 1..12. The maximum length of dsmsg is 21 charac┄↓
ters. The default status messages and their numbers are ↓
╱04002d4e0a000600000000020c4731000000000000000000000000000000000000000000000000000c161b202a343e48525c66707a848eff04╱
╱04002d4e0a000600000000030c4731000000000000000000000000000000000000000000000000000c161b202a343e48525c66707a848eff04╱
↓
shown below. Note that they all begin with a blank.↲
↲
╱04002d4e0a000600000000030c4731000000000000000000000000000000000000000000000000000c161b202a343e48525c66707a848eff04╱
╱04002d4e0a000600000000020c4731000000000000000000000000000000000000000000000000000c161b202a343e48525c66707a848eff04╱
↓
1= Printer not ready↲
2= Print cancelled↲
3= Printer offline↲
4= Printer unavailable↲
5= Printer busy↲
6= Protected field↲
7= Card read error↲
8= Card format error↲
┆8c┆┆83┆┆c0┆↓
9= Field size error↲
10= Configuration error↲
11= CU disconnected↲
╱04002d4e0a000600000000020c4731000000000000000000000000000000000000000000000000000c161b202a343e48525c66707a848eff04╱
╱04002d4e0a000600000000030c4731000000000000000000000000000000000000000000000000000c161b202a343e48525c66707a848eff04╱
↓
12= Illegal position↲
↲
╱04002d4e0a000600000000030c4731000000000000000000000000000000000000000000000000000c161b202a343e48525c66707a848eff04╱
╱04002d4e0a000600000000020c4731000000000000000000000000000000000000000000000000000c161b202a343e48525c66707a848eff04╱
↓
An explanation of the meaning of the messages is given in ↓
section F, Device status messages.↲
↲
┆a1┆Communication status message┆e1┆: CSTEXT,cstno=csmsg↲
CSTEXT specifies one of the messages which may be shown in ↓
the status line of an emulated 3270 display device to inform ↓
the operator of the status of the remote host link to which ↓
the device is attached.↲
Cstno is the number of status message and must be in the ↓
range 1..8.↲
The default status messages and their numbers are shown ↓
below. Shown in parentheses is the maximum number of ↓
characters to be included in a message specified as a ↓
replacement for each default message. Note that all the ↓
╱04002d4e0a000600000000020c4731000000000000000000000000000000000000000000000000000c161b202a343e48525c66707a848eff04╱
╱04002d4e0a000600000000030c4731000000000000000000000000000000000000000000000000000c161b202a343e48525c66707a848eff04╱
↓
texts begin with a blank.↲
↲
╱04002d4e0a000600000000030c4731000000000000000000000000000000000000000000000000000c161b202a343e48525c66707a848eff04╱
╱04002d4e0a000600000000020c4731000000000000000000000000000000000000000000000000000c161b202a343e48525c66707a848eff04╱
↓
1= Modem off╞ ╞ ╞ (19)↲
2= Line not ready╞ ╞ (15)↲
3= System not available╞ (24)↲
4= Cabling error╞ ╞ (19)↲
5= Device not supported╞ (24)↲
6= Call status CP╞ ╞ (15)↲
7= Call error╞ ╞ ╞ (15)↲
╱04002d4e0a000600000000020c4731000000000000000000000000000000000000000000000000000c161b202a343e48525c66707a848eff04╱
╱04002d4e0a000600000000030c4731000000000000000000000000000000000000000000000000000c161b202a343e48525c66707a848eff04╱
↓
8= Waiting for menu╞ (24)↲
↲
╱04002d4e0a000600000000030c4731000000000000000000000000000000000000000000000000000c161b202a343e48525c66707a848eff04╱
╱04002d4e0a000600000000020c4731000000000000000000000000000000000000000000000000000c161b202a343e48525c66707a848eff04╱
↓
An explanation of the meaning of the messages is given in ↓
section F, Communication status messages.↲
↲
┆a1┆Communication parameters (COMM.CST)↲
↲
Parameters for detailed control of communication functions ↓
and the organization of device clusters may be customized in ↓
the file COMM.CST.↲
════════════════════════════════════════════════════════════════════════
↓
Note that for many of the parameters discussed in this ↓
section it is essential that they be specified in agreement ↓
with those specified when the (IBM or IBM compatible) host ↓
and FE systems are generated.↲
↲
┆a1┆Parameters for BSC links↲
The major parameter for a BSC link is BSCKIND which speci┄↓
fies the kind of the link as either V.24 or X.21. Of the ↓
remaining parameters BSCCU, BSCDTR, BSCDUP and BSCPTIME will ↓
only affect a V.24 link, and BSCXNO will only affect an X.21 ↓
link. Specifying one of these parameters for a link of the ↓
wrong kind is not treated as an error, but has no effect.↲
The four possible sublinks of an X.21-BSC link do not ↓
exist by default. Unless the subscriber number of the ↓
Front-End computer associated with each sublink is specified ↓
using the BSCXNO parameter the link is treated as non-↓
existing. There is no parameter to inform the CU of its own ↓
subscriber number; it does not need this information.↲
↲
┆a1┆┆a1┆BSC link kind┆e1┆: BSCKIND(,linkno)=0/1↲
BSCKIND specifies the kind of a BSC link as V.24 (0, ↓
default) or X.21 (1).↲
Linkno may be omitted unless the configuration is dual ↓
host with two BSC links. It specifies the number of the link ↓
and must be 1 or 2.↲
Note that the kind of a link should only be specified as ↓
X.21 if automatic call handling and subscriber number ↓
signalling is required. In case of an X.21 bis interface ↓
(DATEX-L) the link should be specified as V.24 and the ↓
BSCDTR parameter set to 2 (see below).↲
↲
┆a1┆EBCDIC code for BSC link┆e1┆: BSCCONV(,linkno(,sublinkno))=1/2↲
BSCCONV specifies whether EBCDIC code 1 or 2 (cf. the ↓
section Conversion tables above) is to be used on a remote ↓
BSC host link or sub┄link.↲
════════════════════════════════════════════════════════════════════════
↓
Sublinkno must be present if the link kind is X.21 and ↓
must be left out if it is V.24. If present, it identifies ↓
the sublink and must be a number in the range 1..4.↲
Linkno may be omitted unless the configuration is dual ↓
host with two BSC links. However, in the case of an X.21 ↓
link, i.e. if sublinkno is present, linkno must not be ↓
omitted even if there is only one BSC link. It specifies the ↓
number of the link and must be 1 or 2.↲
↲
┆a1┆CU number┆e1┆: BSCCU(,linkno)=cuno↲
BSCCU specifies the CU number of a V.24-BSC link. It is ↓
given as cuno, which must be a decimal number in the range ↓
0..31. The CU number determines the addressing sequences ↓
(poll and select) to which the CU will respond. The default ↓
value is 0, corresponding to polling address 40┆82┆Hex┆81┆ and ↓
selection address 60┆82┆Hex┆81┆.↲
Linkno may be omitted unless the configuration is dual ↓
host with two BSC links. It specifies the number of the link ↓
and must be 1 or 2.↲
↲
┆a1┆DTR handling┆e1┆: BSCDTR(,linkno)=dtrspec↲
BSCDTR specifies how the DTR signal of the V.24 interface is ↓
to be handled for a V.24-BSC link. Dtrspec must be 0 (de┄↓
╱04002d4e0a000600000000020c4731000000000000000000000000000000000000000000000000000c161b202a343e48525c66707a848eff04╱
╱04002d4e0a000600000000030c4731000000000000000000000000000000000000000000000000000c161b202a343e48525c66707a848eff04╱
↓
fault), 1 or 2, and is interpreted as follows:↲
↲
0. Nonswitched line, DTR is always set.↲
↲
╱04002d4e0a000600000000030c4731000000000000000000000000000000000000000000000000000c161b202a343e48525c66707a848eff04╱
╱04002d4e0a000600000000020c4731000000000000000000000000000000000000000000000000000c161b202a343e48525c66707a848eff04╱
↓
1. ┆84┆Manual call. DTR is set initially, and the CU waits for ↓
┆19┆┆83┆┄┄DSR. If DSR subsequently disappears, DTR is reset for 5 ↓
╱04002d4e0a000600000000020c4731000000000000000000000000000000000000000000000000000c161b202a343e48525c66707a848eff04╱
╱04002d4e0a000600000000030c4731000000000000000000000000000000000000000000000000000c161b202a343e48525c66707a848eff04╱
↓
┆19┆┆83┆┄┄seconds and thereafter set again.↲
↲
╱04002d4e0a000600000000030c4731000000000000000000000000000000000000000000000000000c161b202a343e48525c66707a848eff04╱
╱04002d4e0a000600000000020c4731000000000000000000000000000000000000000000000000000c161b202a343e48525c66707a848eff04╱
↓
2. ┆84┆Automatic call (X.21 bis). DTR is set and the CU waits up ↓
┆19┆┆83┆┄┄to 5 seconds for DSR. If DSR fails to appear or sub┄↓
┆19┆┆83┆┄┄sequently disappears, DTR is reset for 5 seconds, where┄↓
┆19┆┆83┆┄┄upon the procedure is repeated. After 8 unsuccessful ↓
┆19┆┆83┆┄┄attempts there is a 30 seconds pause, in which DTR is ↓
╱04002d4e0a000600000000020c4731000000000000000000000000000000000000000000000000000c161b202a343e48525c66707a848eff04╱
╱04002d4e0a000600000000030c4731000000000000000000000000000000000000000000000000000c161b202a343e48525c66707a848eff04╱
↓
┆19┆┆83┆┄┄reset.↲
↲
╱04002d4e0a000600000000030c4731000000000000000000000000000000000000000000000000000c161b202a343e48525c66707a848eff04╱
╱04002d4e0a000600000000020c4731000000000000000000000000000000000000000000000000000c161b202a343e48525c66707a848eff04╱
↓
Linkno may be omitted unless the configuration is dual host ↓
with two BSC links. It specifies the number of the link and ↓
must be 1 or 2.↲
↲
┆8c┆┆83┆┆d8┆↓
┆a1┆Half/full duplex┆e1┆: BSCDUP(,linkno)=0/1↲
BSCDUP specifies half duplex (0) or full duplex (1, default) ↓
treatment of a V.24-BSC link. The parameter affects the use ↓
of the RTS signal of the V.24 interface.↲
Linkno may be omitted unless the configuration is dual ↓
host with two BSC links. It specifies the number of the link ↓
and must be 1 or 2.↲
↲
┆a1┆BSC printer timeout┆e1┆: BSCPTIME(,linkno)=timeout↲
BSCPTIME specifies for a V.24-BSC link how long a printer ↓
shall be reserved for the host after completion of a ↓
printout operation initiated by the host. While the printer ↓
is reserved it cannot be used for local hard-copy. Moreover, ↓
the CU monitors that the printer is not switched offline. ↓
This mechanism is provided to avoid mixing up printed data ↓
originating from different sources.↲
Timeout specifies the reservation period in seconds and ↓
must be in the range 1..60. The default value is 15.↲
Linkno may be omitted unless the configuration is dual ↓
host with two BSC links. It specifies the number of the link ↓
and must be 1 or 2.↲
↲
┆a1┆X.21 subscriber number┆e1┆: BSCXNO,linkno,sublinkno=xno↲
BSCXNO specifies the subscriber number in the public data ↓
network of the FE associated with an X.21-BSC sublink.↲
Linkno specifies the number of the link and must be 1 or ↓
2. It must be present even if there is only one BSC link. ↓
Sublinkno identifies the sublink and must be a number in the ↓
range 1..4.↲
Xno is the subscriber number. It must consist of up to 16 ↓
decimal digits, and will be extended with zeroes. Other ↓
characters appearing among the digits are ignored.↲
↲
┆a1┆Parameters for SNA/SDLC links↲
The major parameter for an SNA/SDLC link is SDLCKIND which ↓
specifies the kind of the link as either V.24 or X.21. Of ↓
the remaining parameters SDLCDTR, SDLCDUP and MPOINT will ↓
┆8c┆┆83┆┆bc┆↓
only affect a V.24 link, and SDLCHXNO and SDLCCXNO will only ↓
affect an X.21 link. Specifying one of these parameters for ↓
a link of the wrong kind is not treated as an error, but has ↓
no effect.↲
In case of an X.21-SNA/SDLC link the CU must know the ↓
subscriber number of the host computer as well as its own ↓
subscriber number. These numbers are specified using the ↓
SDLCHXNO and SDLCCXNO parameters, respectively.↲
↲
┆a1┆SNA/SDLC link kind┆e1┆: SDLCKIND(,linkno)=0/1↲
SDLCKIND specifies the kind of a SNA/SDLC link as V.24 (0, ↓
default) or X.21 (1).↲
Linkno may be omitted unless the configuration is dual ↓
host with two SNA/SDLC links. It specifies the number of the ↓
link and must be 1 or 2.↲
Note that the kind of a link should only be specified as ↓
X.21 if automatic call handling and subscriber number ↓
signalling is required. In case of an X.21 bis interface ↓
(DATEX-L) the link should be specified as V.24 and the ↓
SDLCDTR parameter set to 2 (see below).↲
↲
┆a1┆EBCDIC code for SNA/SDLC link┆e1┆: SNACONV(,linkno)=1/2↲
SNACONV specifies whether EBCDIC code 1 or 2 (cf. the ↓
section Conversion tables above) is to be used on a remote ↓
SNA/SDLC host ┄link.↲
Linkno may be omitted unless the configuration is dual ↓
host with two SNA/SDLC links. It specifies the number of the ↓
link and must be 1 or 2.↲
↲
┆a1┆SDLC address┆e1┆: SDLCADDR(,linkno)=saddr↲
SDLCADDR specifies the SDLC address for an SNA/SDLC link ↓
(V.24 or X.21). It is given as saddr, which must be a ↓
hexadecimal number in the range 0..FF. The SDLC address ↓
identifies the frames to which the CU will respond. The ↓
default value is C1.↲
════════════════════════════════════════════════════════════════════════
↓
Linkno may be omitted unless the configuration is dual ↓
host with two SNA/SDLC links. It specifies the number of the ↓
link and must be 1 or 2.↲
↲
┆a1┆Terminal ID┆e1┆: TERMID(,linkno)=tid↲
TERMID specifies the terminal ID for an SNA/SDLC link (V.24 ↓
or X.21). It is given as tid, which must be a sequence of 5 ↓
hexadecimal digits. The terminal ID is transmitted to the ↓
host computer in response to XID. The default value is ↓
00000.↲
Linkno may be omitted unless the configuration is dual ↓
host with two SNA/SDLC links. It specifies the number of the ↓
link and must be 1 or 2.↲
↲
┆a1┆NRZI encoding┆e1┆: SDLCNRZI(,linkno)=0/1↲
SDLCNRZI specifies whether NRZI encoding is to be used (1) ↓
or not used (0, default) on an SNA/SDLC link (V.24 or X.21).↲
Linkno may be omitted unless the configuration is dual ↓
host with two SNA/SDLC links. It specifies the number of the ↓
link and must be 1 or 2.↲
↲
┆a1┆Printer sharing┆e1┆: PSHARING(,linkno)=0/1↲
PSHARING applies to printer devices which can be activated ↓
by a host computer (not in local mode, cf. the PMODE ↓
parameter discussed in the following subsection, Printer ↓
authorization) as seen by the host computer with which the ↓
CU communicates on an SNA/SDLC link (V.24 or X.21).↲
The parameter specifies whether the printer is to be ↓
shared between this host and other sources of printout ↓
operations only between sessions (0, default) or between ↓
brackets (1).↲
Linkno may be omitted unless the configuration is dual ↓
host with two SNA/SDLC links. It specifies the number of the ↓
link and must be 1 or 2.↲
↲
════════════════════════════════════════════════════════════════════════
↓
┆a1┆DTR handling┆e1┆: SDLCDTR(,linkno)=dtrspec↲
SDLCDTR specifies how the DTR signal of the V.24 interface ↓
is to be handled for a V.24-SNA/SDLC link. Dtrspec must be 0 ↓
(de┄fault), 1 or 2. It has the same interpretation as de┄↓
scribed for the BSCDTR parameter (cf. the preceeding ↓
subsection, Parameters for BSC links).↲
↲
┆a1┆Half/full duplex┆e1┆: SDLCDUP(,linkno)=0/1↲
SDLCDUP specifies half duplex (0) or full duplex (1, de┄↓
fault) treatment of a V.24-SNA/SDLC link. The parameter ↓
affects the use of the RTS signal of the V.24 interface.↲
Linkno may be omitted unless the configuration is dual ↓
host with two SNA/SDLC links. It specifies the number of the ↓
link and must be 1 or 2.↲
↲
┆a1┆Point-to-point/multipoint┆e1┆: MPOINT(,linkno)=0/1↲
MPOINT specifies whether a V.24-SNA/SDLC link is established ↓
on a point-to-point line (0, default), or an a multipoint ↓
line (1).↲
Linkno may be omitted unless the configuration is dual ↓
host with two SNA/SDLC links. It specifies the number of the ↓
link and must be 1 or 2.↲
↲
┆a1┆Host subscriber number┆e1┆: SDLCHXNO(,linkno)=xno↲
SDLCHXNO specifies the subscriber number in the public data ↓
network of the host computer with which the CU communicates ↓
on an X.21-SNA/SDLC link.↲
Linkno may be omitted unless the configuration is dual ↓
host with two SNA/SDLC links. It specifies the number of the ↓
link and must be 1 or 2.↲
Xno is the subscriber number. It must consist of up to 16 ↓
decimal digits, and will be extended with zeroes. Other ↓
characters appearing among the digits are ignored.↲
↲
════════════════════════════════════════════════════════════════════════
↓
┆a1┆Own subscriber number┆e1┆: SDLCCXNO(,linkno)=xno↲
SDLCCXNO specifies the local subscriber number in the public ↓
data network, i.e. the number of the CU itself, for an X.21-↓
SNA/SDLC link.↲
Linkno may be omitted unless the configuration is dual ↓
host with two SNA/SDLC links. It specifies the number of the ↓
link and must be 1 or 2.↲
Xno is the subscriber number. It must consist of up to 16 ↓
decimal digits, and will be extended with zeroes. Other ↓
characters appearing among the digits are ignored.↲
↲
┆a1┆Printer authorization↲
The use of printer devices in an emulated 3270 cluster is ↓
controlled by printer authorization parameters. There are ↓
╱04002d4e0a000600000000020c4731000000000000000000000000000000000000000000000000000c161b202a343e48525c66707a848eff04╱
╱04002d4e0a000600000000030c4731000000000000000000000000000000000000000000000000000c161b202a343e48525c66707a848eff04╱
↓
three aspects of printer authorization.↲
↲
╱04002d4e0a000600000000030c4731000000000000000000000000000000000000000000000000000c161b202a343e48525c66707a848eff04╱
╱04002d4e0a000600000000020c4731000000000000000000000000000000000000000000000000000c161b202a343e48525c66707a848eff04╱
↓
1. ┆84┆For each printer a ┆a1┆mode┆e1┆ is specified which determines ↓
┆19┆┆83┆┄┄whether the printer is to be used exclusively for local ↓
┆19┆┆83┆┄┄hard-copy (local mode), or exclusively for printout ↓
┆19┆┆83┆┄┄operations initiated by a host (system mode), or for both ↓
╱04002d4e0a000600000000020c4731000000000000000000000000000000000000000000000000000c161b202a343e48525c66707a848eff04╱
╱04002d4e0a000600000000030c4731000000000000000000000000000000000000000000000000000c161b202a343e48525c66707a848eff04╱
↓
┆19┆┆83┆┄┄of these types of printing (shared mode).↲
↲
╱04002d4e0a000600000000030c4731000000000000000000000000000000000000000000000000000c161b202a343e48525c66707a848eff04╱
╱04002d4e0a000600000000020c4731000000000000000000000000000000000000000000000000000c161b202a343e48525c66707a848eff04╱
↓
2. ┆84┆Up to 16 ┆a1┆classes┆e1┆ of printers may be defined. A class is a ↓
┆19┆┆83┆┄┄group of printers. The concept allows the hard-copy ↓
┆19┆┆83┆┄┄printer for a terminal (configured in each terminal) to ↓
┆19┆┆83┆┄┄be specified as a class rather than an individual ↓
┆19┆┆83┆┄┄printer. A hard-copy printout requested for the display ↓
┆19┆┆83┆┄┄may be performed on any printer in the class. The printer ↓
┆19┆┆83┆┄┄classes are numbered from 0 to 15. When configuring a ↓
┆19┆┆83┆┄┄terminal, printer class n is specified by using device ↓
╱04002d4e0a000600000000020c4731000000000000000000000000000000000000000000000000000c161b202a343e48525c66707a848eff04╱
╱04002d4e0a000600000000030c4731000000000000000000000000000000000000000000000000000c161b202a343e48525c66707a848eff04╱
↓
┆19┆┆83┆┄┄number 130+n, i.e. a number in the range 130..145.↲
↲
╱04002d4e0a000600000000030c4731000000000000000000000000000000000000000000000000000c161b202a343e48525c66707a848eff04╱
╱04002d4e0a000600000000020c4731000000000000000000000000000000000000000000000000000c161b202a343e48525c66707a848eff04╱
↓
3. ┆84┆For each printer a ┆a1┆source device list┆e1┆ is defined. This is ↓
┆19┆┆83┆┄┄a list of display devices for which the printer may ↓
┆19┆┆83┆┄┄execute local hard-copy operations. If a display device ↓
┆19┆┆83┆┄┄does not belong to the source device list of a given ↓
┆19┆┆83┆┄┄printer, hard-copy cannot take place on that printer even ↓
┆19┆┆83┆┄┄if it is selected as the hard-copy printer for the ↓
╱04002d4e0a000600000000020c4731000000000000000000000000000000000000000000000000000c161b202a343e48525c66707a848eff04╱
╱04002d4e0a000600000000030c4731000000000000000000000000000000000000000000000000000c161b202a343e48525c66707a848eff04╱
↓
┆19┆┆83┆┄┄device, either individually or as a member of a class.↲
↲
╱04002d4e0a000600000000030c4731000000000000000000000000000000000000000000000000000c161b202a343e48525c66707a848eff04╱
╱04002d4e0a000600000000020c4731000000000000000000000000000000000000000000000000000c161b202a343e48525c66707a848eff04╱
↓
┆8c┆┆83┆┆c0┆↓
Notice that the parameter specifications described below ↓
include device numbers which in each case must identify ↓
either a printer or a display device. Since the CU does not ↓
know the devices in a cluster or their numbers when the ↓
parameter file is read, some of the information in these ↓
parameter specifications may turn out to be meaningless, in ↓
which case it will have no effect.↲
↲
┆a1┆Printer mode┆e1┆: PMODE,devno=pmo↲
PMODE specifies the mode of the printer whose device number ↓
is given as devno, which must be a number in the range ↓
╱04002d4e0a000600000000020c4731000000000000000000000000000000000000000000000000000c161b202a343e48525c66707a848eff04╱
╱04002d4e0a000600000000030c4731000000000000000000000000000000000000000000000000000c161b202a343e48525c66707a848eff04╱
↓
0..127. Pmo must be 0, 1 or 2, meaning:↲
↲
╱04002d4e0a000600000000030c4731000000000000000000000000000000000000000000000000000c161b202a343e48525c66707a848eff04╱
╱04002d4e0a000600000000020c4731000000000000000000000000000000000000000000000000000c161b202a343e48525c66707a848eff04╱
↓
0 local mode↲
1 system mode ↲
2 shared mode (default)↲
↲
┆a1┆Printer class┆e1┆: PCLASS,clno=devno-list↲
PCLASS specifies that the listed (printer) devices belong to ↓
the printer class whose number is given as clno, which must ↓
be a number in the range 0..15. Devno-list must be a list of ↓
device numbers in the range 0..127, separated by commas or ↓
hyphens. If two device numbers in the list, the first one ↓
smaller than the second one, are separated by a hyphen, then ↓
all device numbers in the interval between them are also ↓
included. By default, all printer classes are empty.↲
As an example: PCLASS,7=2,4,8-12↲
specifies that the printers with device numbers 2, 4, 8, 9, ↓
10, 11 and 12 belong to printer class number 7.↲
↲
┆a1┆Printer source device list┆e1┆: PSRCLIST,devno=devno-list↲
PSRCLIST specifies that the source device list for the ↓
printer whose device number is given as devno, which must be ↓
a number in the range 0..127, comprises precisely the listed ↓
(display) devices. Devno-list is written in the same way as ↓
for the PCLASS parameter (see above). By default, all ↓
display devices belong to the source lists of all printers.↲
↲
┆8c┆┆83┆┆c0┆↓
┆a1┆Cluster size↲
There are two parameters related to the size of a cluster: ↓
the maximum 3270 device number and the number of terminals ↓
with which the CP will communicate on RcCircuit-I. 3270 ↓
devices include devices emulated in PCs connected to the CP ↓
via a LAN and soft devices resident in the CP itself as well ↓
as devices in terminals connected to the CP via RcCircuit-I.↲
↲
┆a1┆Maximum device number┆e1┆: MAXDEVNO=mno↲
MAXDEVNO specifies the maximum number which the CU will ↓
accept as a valid device number. Mno gives this number, ↓
which must be in the range 1..127. The default value is 63. ↓
If a device is activated with a device number greater than ↓
the one specified by MAXDEVNO it will be rejected by the CU.↲
Note that regardless of the value specified by MAXDEVNO ↓
devices with device numbers greater than 63 cannot commu┄↓
nicate with a host computer via a remote BSC link because of ↓
limitations in the BSC protocol.↲
↲
┆a1┆Number of terminals┆e1┆: NOTERMS=tno↲
NOTERMS specifies the number of terminals with which the CP ↓
will communicate via RcCircuit-I. The number is given as ↓
Tno, which must in the range 1..32. A terminal whose ↓
secondary address is configured to be equal to or greater ↓
than the value specified by NOTERMS will not be able to ↓
communicate with the CP. The default value is 16.↲
A value greater than 16 may only be specified if the ↓
configuration is "dual host" or "high performance"; ↓
otherwise it will be ignored, i.e. the default value will ↓
remain in effect.↲
↲
┆a1┆Local host links↲
When configured to support local host links the CP acts as a ↓
3270 ┆a1┆CU┆e1┆ with ┆a1┆L┆e1┆AN ┆a1┆I┆e1┆nterface (CUL/CULI). As such, it may ↓
interact with the 3270 device handler function of an RC8000 ↓
ADP (cf. ref. 6). The customization parameters for local ↓
┆8c┆┆83┆┆b0┆↓
host links must be set in agreement with those chosen for ↓
the ADP.↲
↲
┆a1┆Number of local host links┆e1┆: CULCONS=n↲
CULCONS specifies the maximum number of local host links ↓
which can be active simultaneously. Each 3270 device handler ↓
pair on an RC8000 ADP (representing an RC8000 application) ↓
requires its own link. N gives the number, which must be in ↓
the range 0..10. The default value is 2.↲
↲
┆a1┆Output message size for local host links┆e1┆: CULOSIZE=n↲
CULOSIZE specifies the maximum size of individual messages ↓
transmitted from the RC8000 ADP to the CU (number of bytes). ↓
The actual size is negotiated with the device handler on the ↓
ADP when the link is established; to avoid waste, the same ↓
size should be specified for the CU and the ADP. N gives the ↓
number, which must be in the range 100..3860. The default ↓
value is 1024.↲
↲
┆a1┆Input message size for local host links┆e1┆: CULISIZE=n↲
CULISIZE specifies the maximum size of individual messages ↓
transmitted from the CU to the RC8000 ADP (number of bytes). ↓
The actual size is negotiated with the device handler on the ↓
ADP when the link is established; to avoid waste, the same ↓
size should be specified for the CU and the ADP. N gives the ↓
number, which must be in the range 256..3860. The default ↓
value is 256.↲
↲
┆a1┆CU port name for local host link┆e1┆: CULIPORT=pname↲
Every CU attached to the LAN has a port name by which it is ↓
known to the RC8000 ADP. CULIPORT specifies this name. Pname ↓
must be a string of at most 12 characters. The ADP requires↲
port names to have the form CUxx, where xx is a decimal ↓
number starting from 00; i.e. the names of the CUs attached ↓
to a given LAN must be specified as CU00, CU01, CU02 etc. ↓
The default port name is CU00.↲
↲
┆8c┆┆83┆┆bc┆↓
┆a1┆Soft devices↲
If the soft device function of the CP is activated, it is ↓
necessary to specify the numbers of the desired soft devices ↓
(cf. section E, Device number management).↲
↲
┆a1┆Device numbers┆e1┆: SOFTDEVS=devno-list↲
SOFTDEVS specifies the numbers of soft devices to be ↓
activated on the CP. Devno-list must be a list of device ↓
numbers in the range 0..127, separated by commas. By ↓
default there are no soft devices.↲
↲
┆a1┆Soft device timeout┆e1┆: SOFTMOUT=t↲
SOFTMOUT specifies the timeout period used by soft devices ↓
(when the local application program is waiting for a locked ↓
keyboard or a USM order, cf. ref. 5). T, which must a number ↓
in the range 1..255, gives the timeout period in seconds.↲
↲
┆a1┆Parameters for Teletex↲
If the Teletex service is activated the following three ↓
parameters will be effective:↲
↲
┆a1┆Class 0 pages┆e1┆: CLASS0P=c0p↲
CLASS0P specifies the maximum length in pages of a class 0 ↓
document. A higher priority is assigned to class 0 documents ↓
than to longer documents. C0p must be a number in the range ↓
0..32675. The default value is 10.↲
↲
┆a1┆Number of letters┆e1┆: MAXL=n↲
MAXL specifies the maximum number of letters which the ↓
Teletex communication service can handle simultaneously. All ↓
letters queued for transmission and not yet completely ↓
transmitted as well as all partially received letters count ↓
against this maximum. The default value for n, which must be ↓
a number in the range 0..32675, is 30.↲
════════════════════════════════════════════════════════════════════════
↓
┆a1┆Address of Telex conversion facility┆e1┆: CFADDR=addr↲
CFADDR specifies the Teletex address to which Telex ↓
documents should be sent (Telex conversion facility). Addr ↓
must be given as a string of at most 24 characters. The ↓
default value is 2381-01=CFTELEX.↲
↲
════════════════════════════════════════════════════════════════════════
↓
┆14┆┆b3┆↲
┆14┆┆b1┆┆b0┆ RC3931 Communications Processor┆05┆System Management E↲
┆14┆┆b2┆┆b0┆ E System Management┆05┆RC3931 Communications Processor ↲
┆15┆┆b3┆↲
┆15┆┆b1┆┆b0┆ Update 1/86┆05┆Page E-┆0b┆ E↲
┆15┆┆b2┆┆b0┆ E Page E-┆0b┆┆05┆Update 1/86 ↲
╱04002d4e0a000600000000030c4731000000000000000000000000000000000000000000000000000c16202a343c48525c66707a848effff04╱
╱04002d4e0a000600000000030c4731000000000000000000000000000000000000000000000000000c161b202a343e48525c66707a848eff04╱
↓
┆a1┆E. System Management↲
↲
The responsibilities of the system administrator in con┄↓
╱04002d4e0a000600000000020c4731000000000000000000000000000000000000000000000000000c16202a343c48525c66707a848effff04╱
╱04002d4e0a000600000000030c4731000000000000000000000000000000000000000000000000000c16202a343c48525c66707a848effff04╱
↓
junction with the CP are:↲
↲
╱04002d4e0a000600000000030c4731000000000000000000000000000000000000000000000000000c16202a343c48525c66707a848effff04╱
╱04002d4e0a000600000000020c4731000000000000000000000000000000000000000000000000000c16202a343c48525c66707a848effff04╱
↓
- ┆84┆configuring and customizing the CP by editing the ↓
┆19┆┆82┆┄┄configuration and customization parameter files,↲
- ┆84┆managing the assignment of device numbers to devices in an ↓
┆19┆┆82┆┄┄emulated 3270 cluster,↲
╱04002d4e0a000600000000020c4731000000000000000000000000000000000000000000000000000c16202a343c48525c66707a848effff04╱
╱04002d4e0a000600000000030c4731000000000000000000000000000000000000000000000000000c16202a343c48525c66707a848effff04╱
↓
- reporting errors.↲
↲
╱04002d4e0a000600000000030c4731000000000000000000000000000000000000000000000000000c16202a343c48525c66707a848effff04╱
╱04002d4e0a000600000000020c4731000000000000000000000000000000000000000000000000000c16202a343c48525c66707a848effff04╱
↓
Some of the information provided in this main section is ↓
intended to help the system administrator with respect to ↓
finding and editing the configuration and customization ↓
parameter files. The remaining part of the section aims to ↓
enable the system administrator to determine whether a ↓
malfunction of the CP is due to improper customization or ↓
installation, or whether the product is defective, so that ↓
an error report should be made.↲
↲
┆a1┆Resetting the CP↲
↲
In order to reset the CP, thereby causing it to read the ↓
configuration and parameter files and activate its functions ↓
accordingly, it is necessary to reset the complete RC39 ↓
system. This is done by switching power on or pressing the ↓
reset button.↲
Note that the standard procedure for shutting down the ↓
XENIX operating system should always be followed before ↓
power is switched off or the system reset, cf. ref. 1.↲
It is important to note that when the configuration or ↓
parameter files have been changed, and/or when a new SW ↓
package for the CP has been installed, the CP must be reset ↓
before the changes will take effect. The configuration and ↓
parameter files are ┆a1┆only┆e1┆ read by the CP when it is reset.↲
↲
════════════════════════════════════════════════════════════════════════
↓
┆a1┆Files belonging to the CP↲
↲
When a SW package for the CP is installed, a number of files ↓
are copied from the distribution diskette to the RC39 disk ↓
utilizing the disk filing functions of the XENIX operating ↓
system which governs the LAP.↲
All files that belong to the CP are kept in the directory ↓
/usr/cp. These files include: software modules to be loaded ↓
and executed on the CP including adapter boards, program ↓
files for download to terminals, customization files to be ↓
read by the CP during load, and auxiliary files (see below).↲
In the sense of the XENIX operating system the CP files ↓
belong to the root and are protected against access by other ↓
users. However, by logging in as root (super user), the ↓
system administrator may manipulate the CP files using any ↓
available tools such as XENIX utility programs, text editor ↓
or word processor etc.↲
All CP files have names of the form "name.ext", where name ↓
consists of at most 8 characters and ext, the file name ↓
extension, is at most 3 characters. Files with same file ↓
name extension are referred to collectively as "*.ext" ↓
files. The form "name.*" is used similarly.↲
The names of CP files are relative to the directory ↓
/usr/cp, so that the complete path name of a CP file is ↓
/usr/cp/name.ext.↲
↲
┆a1┆Auxiliary files↲
For each customization parameter file read by the CP (cf. ↓
section D.2, Customization, Parameter Files) one or more ↓
auxiliary files ("help files") are distributed as part of ↓
the operating system package (SW3910). The auxiliary files ↓
are ┆a1┆not┆e1┆ read or otherwise accessed by the CP. They are only ↓
intended as an aid to the system administrator when ↓
customizing the CP.↲
All the auxiliary files for a given parameter file have ↓
the same file name extension which is derived from the name ↓
of the parameter file. The correspondence is shown in the ↓
following table:↲
↲
┆8c┆┆83┆┆d4┆↓
╱04002d4e0a000600000000030c4731000000000000000000000000000000000000000000000000000c13202a343c48525c66707a848effff04╱
╱04002d4e0a000600000000030c4731000000000000000000000000000000000000000000000000000c16202a343c48525c66707a848effff04╱
↓
╞ ┆a1┆Parameter file╞ Auxiliary files↲
╞ MENUDL.CST╞ ╞ ╞ *.MDL↲
╞ CONV1.CST (CONV.CST), CONV2.CST╞ *.CNV↲
╞ TEXTS.CST╞ ╞ ╞ *.TXT↲
╞ COMM.CST╞ ╞ ╞ *.CMM↲
↲
Three auxiliary files: DEFAULT.MDL, DEFAULT.TXT, and ↓
DEFAULT.CMM, contain parameter lines which show how the ↓
default parameter values may be specified. It may be ↓
convenient for the system administrator to create parameter ↓
(*.CST) files for a given CP installation by editing and ↓
renaming the DEFAULT.* files rather than starting from ↓
scratch. It is recommended that superfluous lines and lines ↓
that do not apply to the chosen configur┄ation be deleted ↓
when this is done.↲
The file DEFAULT.CFG, which explains how to set configur┄↓
ation switches (cf. section D.1, Configuration), is similar ↓
to the other DEFAULT.* files in that it is intended to be ↓
edited and renamed, in this case as CONFIG.CST.↲
The file DMENU.MDL contains a Danish language version of ↓
the default download menu. Similarly, the file DANSK.TXT ↓
contains standard Danish texts for status line messages and ↓
host link menus. If these two files are renamed as ↓
MENUDL.CST and TEXTS.CST, respectively, all messages ↓
pertaining to CP functions will be shown to the terminal ↓
operator in Danish.↲
↲
┆a1┆Selecting character conversion↲
When performing 3270 emulation the CP converts between two ↓
encodings of characters: internal code and EBCDIC code. A ↓
general discussion of this topic is found in section D.2, ↓
Conversion tables.↲
The default conversion tables are appropriate only if the ↓
internal character set is US English (ASCII) and the desired ↓
EBCDIC code is US English. Often this will not be the case, ↓
and modifications will therefore be necessary.↲
════════════════════════════════════════════════════════════════════════
↓
Conversion table modifications suitable for a number of ↓
standard combinations of internal and EBCDIC encodings are ↓
found in the *.CNV files. When one of these standard com┄↓
binations is applicable, customization of the character ↓
conversion is achieved simply by renaming the proper *.CNV ↓
file as CONV1.CST (EBCDIC code 1) or CONV2.CST (EBCDIC code ↓
2).↲
Code tables for all standard internal character sets and ↓
the corresponding standard EBCDIC encodings are included as ↓
appendices H.2 and H.3. The following table shows which ↓
*.CNV file to select for a given standard combination:↲
↲
╱04002d4e0a000600000000030c4731000000000000000000000000000000000000000000000000000c16202a343c48525c66707a848effff04╱
╱04002d4e0a000600000000030c4731000000000000000000000000000000000000000000000000000c13202a343c48525c66707a848effff04╱
↓
internal cha-╞ EBCDIC encoding╞ ╞ file↲
┆a1┆┆e1┆ ┆a1┆ racter set╞ ╞ ╞ ╞ ↲
US English╞ US English╞ ╞ default↲
UK English╞ UK English╞ ╞ ENGLISH.CNV↲
German╞ ╞ German╞ ╞ ╞ GERMAN.CNV↲
German╞ ╞ German, alternate╞ ╞ GERMANA.CNV↲
Swedish╞ ╞ Swedish╞ ╞ ╞ SWEDISH.CNV↲
Swedish╞ ╞ Swedish, alternate╞ ╞ SWEDISHA.CNV↲
Standard Danish╞ Standard Danish╞ ╞ STDK.CNV↲
Standard Danish╞ Standard Danish, alternate╞ STDKA.CNV↲
Danish OS╞ Danish OS╞ ╞ ╞ DOS.CNV↲
Danish OS╞ Danish OS, alternate╞ DOSA.CNV↲
↲
┆a1┆External cable connections↲
↲
Normally the signal cables which connect the CP to units ↓
which are external to the RC39 system are mounted when the ↓
CP hardware is installed. The present brief description is ↓
intended to enable the system administrator to ascertain by ↓
inspection that the connections are properly in place.↲
Figure E-1 shows the connector panel located behind the ↓
rear cover of the RC39 cabinet.↲
Connector J51 must be used for the RcCircuit signal cable. ↓
Notice that this cable contains two twisted wire pairs. One ↓
twisted pair is used for character-mode communication ↓
════════════════════════════════════════════════════════════════════════
↓
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
╞ < Figure E-1 >↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
Figure E-1. RC39 connector panel.↲
↲
between terminals and the RC39 LAP, a function which does ↓
not involve the CP. The other twisted pair is used for ↓
════════════════════════════════════════════════════════════════════════
↓
block-mode communication between terminals and the CP, i.e. ↓
for the functions which are described in this guide.↲
When the CP is connected to a LAN, connector J2 must be ↓
used for the transceiver cable. The transceiver cables used ↓
for the two kinds of LAN, Ethernet and RcMicronet, are ↓
different, but both cables fit the J2 connector.↲
The connectors J11, J12, J13 and J14, marked V.24/X.21 ↓
COMM., are for the signal cables used to establish remote ↓
3270 host links. The connectors are used as follows, ↓
depending on the configuration (cf. section D.1, remote host ↓
links):↲
↲
┆a1┆configuration╞ connector(s) used↲
╱04002d4e0a000600000000020c4731000000000000000000000000000000000000000000000000000c16202a343c48525c66707a848effff04╱
╱04002d4e0a000600000000030c4731000000000000000000000000000000000000000000000000000c16202a343c48525c66707a848effff04╱
↓
3270B╞ J11 - BSC link 1↲
↲
3270BH╞ J13 - BSC link 1↲
↲
3270BD╞ J11 - BSC link 1↲
╞ ╞ J13 - BSC link 2↲
↲
3270S╞ J12 - SNA/SDLC link 1↲
↲
3270SH╞ J14 - SNA/SDLC link 1↲
↲
3270SD╞ J12 - SNA/SDLC link 1↲
╞ ╞ J14 - SNA/SDLC link 2↲
↲
3270BS╞ J12 - SNA/SDLC link 1↲
╱04002d4e0a000600000000030c4731000000000000000000000000000000000000000000000000000c16202a343c48525c66707a848effff04╱
╱04002d4e0a000600000000020c4731000000000000000000000000000000000000000000000000000c16202a343c48525c66707a848effff04╱
↓
╞ ╞ J13 - BSC link 1↲
↲
The connector used for a link is independent of whether the ↓
kind of the link is V.24 or X.21, but the signal cables used ↓
to connect the CP to a V.24 modem or to an X.21 DCE, ↓
respectively, are different (see Appendix H.4 for details). ↓
Both kinds of signal cable fit all four J1X connectors.↲
The connector J1, marked X.21, is for the signal cable ↓
used to connect the CP to an X.21 DCE to obtain Teletex ↓
service.↲
↲
┆a1┆┆a1┆Device number management (3270)↲
↲
As discussed in section B.2, Emulated 3270 devices, device ↓
numbers are not customized in the parameter files of the CP, ↓
════════════════════════════════════════════════════════════════════════
↓
but in the various units which emulate the devices. It is ↓
the responsibility of the system administrator to assign the ↓
available device numbers to devices and to oversee that ↓
device numbers are properly configured in the various units, ↓
i.e. terminals and PCs. Only the device numbers for soft ↓
devices which reside within the CP are part of CP custom┄↓
ization.↲
It is recommended for the system administrator to maintain ↓
a list showing the use of each device number: physical ↓
location, type of terminal or other use etc.↲
It is also the responsibility of the system administrator ↓
to coordinate the assignment of device numbers within an ↓
emulated 3270 cluster with the customization of the remote ↓
host computer(s). Often fairly rigid rules are applied to ↓
the selection of device numbers within the host computer ↓
system. It is therefore recommended that cooperation with ↓
host computer operating staff be established before device ↓
numbers are assigned.↲
↲
┆a1┆CP log file↲
↲
The CP logs certain types of information in a log file. This ↓
happens when the configuration and customization files are ↓
read, during load of software modules, and when errors are ↓
detected while the CP is in operation. The CP log file is ↓
named ERRORLOG. Upon reset of the CP the previous log file ↓
is renamed as ERRORLOG.BAK before a new log is opened.↲
In general, the information in the system log is intended ↓
for RC software maintenance staff and not for the user. It ↓
may, however, be useful to read the log if the customization ↓
parameters prepared in the *.CST files by the system admini┄↓
strator do not have the intended effect.↲
When a parameter specification line in one of the files is ↓
not acceptable to the CP, either because of a syntax error, ↓
or because the parameter does not apply to the configuration ↓
as specified in the CONFIG.CST file, a line is written in ↓
the log file. This line will contain the name of the para┄↓
════════════════════════════════════════════════════════════════════════
↓
meter file and the parameter name found at the beginning of ↓
the rejected line. All information about rejected parameter ↓
specification lines will appear in the first lines of the ↓
log. The system administrator may therefore read the ↓
beginning of the log as a report on the acceptability of the ↓
attempted customization.↲
Whether or not the system administrator considers it ↓
useful to read the log, it is recommended practice to print ↓
out the ERRORLOG file in case of a malfunction attributable ↓
to the CP. Such a printout should be submitted with any ↓
error report concerning a CP function.↲
↲
┆a1┆Lamps on the front panel↲
↲
Eight small lamps, organized in two rows of four, are ↓
visible on the front panel of the RC39 cabinet; see Figure ↓
E-2. The lamps in the bottom row, marked ERROR, HOST 1, HOST ↓
2 and LTN, and the lamp in the top row which is marked LAN, ↓
indicate the status of the CP.↲
┆0e┆↓
↲
↲
↲
↲
↲
↲
↲
╞ < Figure E-2 >↲
↲
↲
↲
↲
↲
↲
↲
↲
Figure E-2. RC39 front panel.↲
┆0f┆↓
↲
════════════════════════════════════════════════════════════════════════
↓
Note that the lamps in the bottom row are inoperative - ↓
never lit - unless at least one communication adapter is ↓
installed as part of the CP subsystem.↲
The ERROR lamp only lights to indicate that the CP has ↓
ceased to operate. This may occur during the self-test ↓
sequence which follows a reset, or it may occur when an ↓
unrecoverable error is detected during normal operation. In ↓
the latter case the CP will attempt to write diagnostic ↓
information about the fault in the log before it halts.↲
When the CP ERROR lamp lights the CP can only be activated ↓
by reset, cf. section E, Resetting the CP.↲
The remaining CP status lamps indicate activity on the ↓
various serial communication lines. The HOST 1 and HOST 2 ↓
lamps show activity on the remote 3270 host link(s): HOST 1 ↓
corresponds to the link which uses a signal cable mounted on ↓
connector J11 or J12, and HOST 2 similarly corresponds to ↓
connector J13 or J14. Refer to section E, External cable ↓
connections, to see how host links are assigned to connec┄↓
tors for the various possible configurations.↲
The LTN (local terminal network) lamp shows activity on ↓
RcCircuit-I, and the LAN lamp shows activity on the local ↓
area network.↲
════════════════════════════════════════════════════════════════════════
↓
↲
════════════════════════════════════════════════════════════════════════
↓
┆14┆┆b3┆↲
┆14┆┆b1┆┆b0┆ RC3931 Communications Processor┆05┆Normal Use F↲
┆14┆┆b2┆┆b0┆ F Normal Use┆05┆RC3931 Communications Processor ↲
┆15┆┆b3┆↲
┆15┆┆b1┆┆b0┆ Update 1/86┆05┆Page F-┆0b┆ F↲
┆15┆┆b2┆┆b0┆ F Page F-┆0b┆┆05┆Update 1/86 ↲
╱04002d4e0a000600000000030c4731400000000000000000000000000000000000000000000000000c16202a343e48525c66707a848e98ff04╱
╱04002d4e0a000600000000030c4731000000000000000000000000000000000000000000000000000c16202a343c48525c66707a848effff04╱
↓
┆a1┆F. Normal Use↲
↲
During normal use the CP will not be visible to the user. ↓
The functions of the CP will appear either as functions of ↓
the terminal or PC or as functions of the RC39 LAP. As long ↓
as all components in the system work correctly, the user ↓
will not be aware of the CP. In general, the information ↓
needed by users of the terminal emulator programs is ↓
found in the relevant user's guides and not in this guide.↲
The CP, however, also has a monitoring function: it ↓
discovers when errors or abnormal situations arise in the ↓
various types of communication it supports. In these ↓
instances operator messages issued by the CP will be shown ↓
on the relevant terminal or PC display.↲
The term error is used here not to indicate a fault on the ↓
part of the CP, but rather in the external part of the ↓
system or in the configuration and customization of the ↓
system as set up by the user (system administrator).↲
The situations which are indicated by operator messages ↓
are discussed in the following two subsections, one dealing ↓
with download of terminals, the other with 3270 emulation. ↓
All the messages discussed may be customized, i.e. modified ↓
according to user taste or preference, e.g. translated to a ↓
different language, cf. section D.2, Customization, ↓
Parameter Files.↲
In the following subsections the default versions of the ↓
messages are shown with an indication, given in parentheses, ↓
of the parameter name and text number to be used when custo┄┄↓
mizing a replacement text.↲
↲
┆a1┆Error messages during download↲
↲
The error messages which occur in conjunction with download ↓
of terminals may be customized in the file MENUDL.CST.↲
↲
┆a1┆Disk access error┆e1┆ (ETEXT,1)↲
The CU attempted to gain access to the disk filing system on ↓
the RC39 LAP, but failed. This could be due to a temporary ↓
════════════════════════════════════════════════════════════════════════
↓
lack of resources in case of many simultaneous interactions ↓
between the CP and the LAP. A couple of retries should be ↓
attempted before the error is reported.↲
↲
┆a1┆Program not found┆e1┆ (ETEXT,4)↲
The CU accessed the disk filing system of the LAP correctly, ↓
but only to find that the selected program file did not ↓
exist. The relationship between selection lines in the ↓
download menu and file names is explained in section D.2, ↓
Download menus.↲
The most obvious reason for a program file to be missing ↓
is that it has not been installed. Terminal programs are ↓
distributed in separate packages which must be installed ↓
before the programs can be loaded.↲
↲
┆a1┆CU disconnected┆e1┆ (ETEXT,2)↲
The connection between the CU and the terminal was broken. A ↓
couple of retries should be attempted before the error is ↓
reported, since the problem may be only temporary, e.g. when ↓
the RC39 MUCS is reset.↲
A program file is downloaded as a number of data messages ↓
(blocks). Each data message is protected during transmission ↓
on the RcCircuit-I by a cyclic redundancy check and retrans┄↓
mitted in case of error. An excessive number of retrans┄↓
missions, which may occur if the cable is in very poor ↓
condition or poorly connected, causes the CU connection to ↓
be broken.↲
The connection is also broken, as observed from the ↓
terminal, if the CP ceases to operate (cf. section E, Lamps ↓
on the front panel).↲
Note that this message will not appear if the connection ↓
has not been established at all, e.g. if no physical ↓
connection (RcCircuit-I) exists.↲
↲
┆a1┆Checksum error┆e1┆ (ETEXT,3)↲
An error was detected when a checksum was computed on the ↓
complete program after all blocks had been transferred to ↓
════════════════════════════════════════════════════════════════════════
↓
the terminal. This message therefore does not indicate a ↓
transmission problem. The reason may be that a bad program ↓
file was read from the RC39 disk, or a RAM error within the ↓
terminal. Some prelease program files may not be furnished ↓
with a checksum at all, in which case the message has no ↓
significance. In spite of the checksum error, the downloaded ↓
program will be started in the terminal.↲
↲
┆a1┆3270 emulator status messages↲
↲
The status messages which occur in conjunction with 3270 ↓
emulation may be customized in the file TEXTS.CST.↲
↲
┆a1┆Device status messages↲
The status messages which concern an individual device ↓
within a cluster or the relationship between the CU and one ↓
or more devices without relating to host links are shown a ↓
little to the right of the center of the status line ↓
(positions 35 through 55). This is true for all terminals or ↓
PCs which emulate 3270 display devices.↲
The last five messages discussed in this subsection ↓
concern the use of a magnetic card reader. The card reader ↓
is not monitored by the CU, but the messages are mentioned ↓
here, because they appear in the same part of the status ↓
line and are customizable in the same fashion as the other ↓
device status messages.↲
↲
┆a1┆Configuration error┆e1┆ (DSTEXT,10)↲
A device was activated with an illegal device number. The ↓
device need not be a display device; it could also be a ↓
printer device.↲
A device number is illegal if it is larger than the ↓
maximum device number customized for the cluster, cf. ↓
section D.2, Cluster size.↲
A device number is also illegal if there is already an ↓
active device with the same number. The problem must be ↓
════════════════════════════════════════════════════════════════════════
↓
solved by appropriately assigning device numbers to physical ↓
equipment and configuring the terminals and PCs accordingly, ↓
cf. section E, Device number management.↲
↲
┆a1┆CU disconnected┆e1┆ (DSTEXT,11)↲
The connection between the 3270 CU emulator module and the ↓
terminal emulator program was broken. This may occur for ↓
several different reasons:↲
The RC39 MUCS may have been reset in which case the ↓
message will disappear when the CP has been reloaded.↲
An error may have occurred which caused the CP to cease to ↓
operate, cf. section E, Lamps on the front panel.↲
The condition of the cable or its connections may be so ↓
poor that an excessive number of retransmissions occurred, ↓
causing the CU to abandon the connection. In this case, the ↓
connection is likely to go on and off, since the CU and the ↓
terminal automatically attempt to reestablish communication.↲
↲
┆a1┆Printer unavailable┆e1┆ (DSTEXT,4)↲
Hard-copy printout was requested by the operator, but no ↓
printer was available to execute the request. The printer ↓
configured as hard-copy printer is either not active, i.e. ↓
the terminal or PC to which the printer is attached is not ↓
running the 3270 emulator program, or the display device ↓
does not belong to the source list of the printer (cf. ↓
section D.2, Printer authorization). If the hard-copy ↓
printer is specified as a printer class, the message ↓
indicates that none of the printers in the class are ↓
available.↲
In response to this message the operator should check the ↓
hard-copy printer configuration in the terminal or PC.↲
↲
┆a1┆Printer busy┆e1┆ (DSTEXT,5)↲
Hard-copy printout was requested by the operator, but the ↓
printer was busy. It may be that the printer is performing a ↓
hard-copy printout for another display device, or it may be ↓
performing a host-initiated printout operation. If the hard-↓
════════════════════════════════════════════════════════════════════════
↓
copy printer is specified as a printer class, the message ↓
indicates that all printers in the class are temporarily ↓
occupied.↲
When this message is shown, the printout request is queued ↓
within the CU until the printer becomes ready to execute it. ↓
While the request remains in the queue the keyboard will be ↓
locked. It can be reset in the usual way, whereby the ↓
printout request is dropped from the queue.↲
If the printer device is emulated on a PC (cf. section ↓
B.2, Emulated 3270 devices) and the actual printer is ↓
reserved by another PC application, e.g. a word processor, ↓
the printout request is dropped and not queued.↲
↲
┆a1┆Print cancelled┆e1┆ (DSTEXT,2)↲
A command was received in the 3270 data stream from the host ↓
computer while a hard-copy printout request was queued. This ↓
caused the request to be cancelled, because the received ↓
command is likely to cause the display image to change. If a ↓
hard-copy of the updated image is desired, the operator must ↓
press the PRINT key again.↲
↲
┆a1┆Printer offline┆e1┆ (DSTEXT,3)↲
A printout operation initiated by a hard-copy request went ↓
wrong and was given up. Part of the display image may have ↓
been printed.↲
The operation went wrong because the online signal from ↓
the printer to the terminal or PC to which it is attached ↓
went off. The reason for this may have been that the printer ↓
was selected locally, was powered off, or ran out of paper; ↓
or the printer may simply be poorly connected. This is the ↓
message which will normally occur in case of printer mal┄↓
function.↲
↲
┆a1┆Printer not ready┆e1┆ (DSTEXT,1)↲
A printout operation initiated by a hard-copy request went ↓
wrong and was given up. Part of the display image may have ↓
been printed.↲
════════════════════════════════════════════════════════════════════════
↓
The situation is similar to the one discussed above ↓
(Printer offline). It occurs when the online signal from the ↓
printer remains on, but a timeout occurs while the control ↓
logic of the terminal to which the printer is attached is ↓
waiting for the printer busy signal to go off, allowing the ↓
next character to be transmitted. This situation should ↓
occur very rarely and most likely indicates that the ↓
terminal emulator program is not well adjusted to the ↓
printer in question.↲
↲
┆a1┆Protected field┆e1┆ (DSTEXT,6)↲
An attempt was made to read data from the magnetic card ↓
reader into the display buffer while the cursor was ↓
positioned in a protected field. The cursor must be moved to ↓
an input field before the card can be read.↲
↲
┆a1┆Card read error┆e1┆ (DSTEXT,7)↲
An unsuccessful attempt was made to read a magnetic card. ↓
The card may have been incompletely inserted, or it may have ↓
been inserted at an uneven speed. The card should be re┄↓
inserted.↲
↲
┆a1┆Card format error┆e1┆ (DSTEXT,8)↲
A magnetic card was read, and the card was rejected because ↓
of invalid data. Most likely the card is invalid, and it ↓
will do no good to reinsert it.↲
↲
┆a1┆Field size error┆e1┆ (DSTEXT,9)↲
A magnetic card was read, but the input field into which the ↓
data were read was too small. The cursor must be moved to a ↓
larger field, or be backspaced so as to leave more input ↓
positions before end-of-field.↲
↲
┆a1┆Illegal position┆e1┆ (DSTEXT,12)↲
This message will only occur when the display device is in ↓
session with the SSCP (SNA). When the SSCP expects input, ↓
════════════════════════════════════════════════════════════════════════
↓
the input area is defined as starting from the cursor ↓
position - as left by the SSCP - and extending 256 character ↓
positions or to the end of the display. The message indi┄↓
cates that the cursor was moved before a magnetic card was ↓
read so that the card data, starting from the current cursor ↓
position, would not fit into the input area.↲
↲
┆a1┆Communication status messages, remote host links↲
The status messages which concern the host link to which a ↓
display device is attached are shown in the rightmost part ↓
of the status line (positions 57 through 80). This is true ↓
for all terminals or PCs which emulate 3270 display devices.↲
The messages discussed in this subsection concern remote ↓
host links, i.e. they indicate an error or status pertaining ↓
to a V.24 modem, an X.21 DCE, or the remote host computer or ↓
RC3803 FE. The messages which may appear when a display ↓
device is attached to a local link (cf. section B.2, Local ↓
host links) are discussed in the following subsection.↲
↲
┆a1┆Modem off┆e1┆ (CSTEXT,1)↲
V.24 link: ┆84┆The Data Set Ready (DSR) signal from the modem is ↓
┆19┆┆8b┆┄┄off. The reason may be that the modem is powered ↓
┆19┆┆8b┆┄┄off or not present, or that the signal cable is ↓
┆19┆┆8b┆┄┄not correctly connected.↲
↲
X.21 link: ┆84┆The DCE fails to indicate the DCE ready state, ↓
┆19┆┆8b┆┄┄i.e. call establishment cannot be initiated. The ↓
┆19┆┆8b┆┄┄reason may be that the DCE is powered off or not ↓
┆19┆┆8b┆┄┄present.↲
↲
┆a1┆Line not ready┆e1┆ (CSTEXT,2)↲
BSC link: ┆84┆No polling sequences issued by the host computer ↓
┆19┆┆8a┆┄┄or FE can be detected.↲
↲
SNA/SDLC l┆84┆ink: Communication with the host computer cannot ↓
┆19┆┆8a┆┄┄be established; one of the following codes - which ↓
┆19┆┆8a┆┄┄refer to events in the SDLC protocol or X.21 call ↓
════════════════════════════════════════════════════════════════════════
↓
┆19┆┆8a┆┄┄establishment - is shown to indicate the reason:↲
1:╞ ┆84┆The host computer stopped polling (20 seconds ↓
┆19┆┆8a┆┄┄timeout).↲
4:╞ Disconnect Frame received.↲
5: ┆84┆The host committed a protocol error, FRMR (Frame ↓
┆19┆┆8a┆┄┄Reject) was transmitted.↲
6:╞ Transmitter malfunction.↲
8: ┆84┆Link disconnected by SNRM (Set Normal Response ↓
┆19┆┆8a┆┄┄Mode) received from the host computer.↲
10:╞ Initialization problem:↲
╞ V.24: ┆84┆SNRM not received within 5 seconds after ↓
┆19┆┆90┆┄┄DSR. Likely reasons are:↲
╞ - The link has not been started at the host.↲
╞ - ┆84┆SDLC address or NRZI encoding not custo┄↓
┆19┆┆92┆┄┄mized correctly, i.e. not in agreeement ↓
┆19┆┆92┆┄┄with the host.↲
╞ X.21: ┆84┆The CU gave up trying to establish a call, ↓
┆19┆┆90┆┄┄in which case the "Call status CP" or "Call ↓
┆19┆┆90┆┄┄error" message (see below) will have been ↓
┆19┆┆90┆┄┄displayed previously, or the call was ↓
┆19┆┆90┆┄┄cleared by the network before SNRM was ↓
┆19┆┆90┆┄┄received.↲
↲
┆a1┆System not available┆e1┆ (CSTEXT,3)↲
Polling and/or selection sequences from the host computer or ↓
FE are detected, but not received by the CU, because the ↓
address they contain does not match the CU number. The most ↓
likely reasons are: improper customization of the CU number ↓
or improper generation of a multidropped line at the host ↓
site. Host computer operating staff should be consulted.↲
This message applies to BSC links only.↲
↲
┆a1┆Cabling error┆e1┆ (CSTEXT,4)↲
This message indicates that an X.21 signal cable has been ↓
connected to a connector for a link which has been custo┄↓
mized as V.24, or vice versa. The correspondence between ↓
════════════════════════════════════════════════════════════════════════
↓
links and signal cable connectors is discussed in section E, ↓
External cable connections.↲
The message may also appear in conjunction with an X.21 ↓
link if the cable is not mounted. If the link is V.24 a ↓
missing cable will cause the "Modem off" message to be ↓
shown.↲
↲
┆a1┆Device not supported┆e1┆ (CSTEXT,5)↲
An attempt was made to attach a display device with a device ↓
number greater than 63 to a BSC link. The device was ↓
rejected.↲
↲
┆a1┆Call status CP┆e1┆ (CSTEXT,6)↲
An attempt by the CU to establish a call through the public ↓
data network to the host computer or FE failed. The network ↓
delivered a Call Progress (CP) signal with a code indicating ↓
the reason for the failure. The code is shown as a two-digit ↓
number adjacent to the text. Information on the meaning of ↓
specific CP codes should be obtained from the provider of ↓
the network service.↲
This message will not appear if the link is customized as ↓
V.24.↲
↲
┆a1┆Call error┆e1┆ (CSTEXT,7)↲
An attempt to establish a call through the public data ↓
network failed, but no CP code was received. One of the ↓
following codes is shown to indicate the reason (the meaning ↓
of these codes will be obscure to the user; they are for the ↓
use of RC technicians and should be included in the error ↓
╱04002d4e0a000600000000020c4731400000000000000000000000000000000000000000000000000c16202a343e48525c66707a848e98ff04╱
╱04002d4e0a000600000000030c4731400000000000000000000000000000000000000000000000000c16202a343e48525c66707a848e98ff04╱
↓
report, should the problem persist):↲
↲
╱04002d4e0a000600000000030c4731400000000000000000000000000000000000000000000000000c16202a343e48525c66707a848e98ff04╱
╱04002d4e0a000600000000020c4731400000000000000000000000000000000000000000000000000c16202a343e48525c66707a848e98ff04╱
↓
00: ┆84┆A call is properly established, but is then ↓
┆19┆┆8a┆┄┄cleared illegally - by the FE, the network, or the ↓
┆19┆┆8a┆┄┄DCE - out of step with the BSC protocol (BSC ↓
┆19┆┆8a┆┄┄only).↲
01:╞ Clear from DCE during call establishment↲
02:╞ Receiver overrun↲
════════════════════════════════════════════════════════════════════════
↓
03:╞ Receiver parity error↲
04:╞ Unexpected interrupt↲
06:╞ Time limit T1↲
07:╞ Time limit T2↲
08:╞ Time limit T3A/T3B↲
09:╞ Time limit T4↲
10:╞ Time limit T5/T6↲
╱04002d4e0a000600000000020c4731400000000000000000000000000000000000000000000000000c16202a343e48525c66707a848e98ff04╱
╱04002d4e0a000600000000030c4731400000000000000000000000000000000000000000000000000c16202a343e48525c66707a848e98ff04╱
↓
11:╞ Time limit T11↲
↲
╱04002d4e0a000600000000030c4731400000000000000000000000000000000000000000000000000c16202a343e48525c66707a848e98ff04╱
╱04002d4e0a000600000000020c4731400000000000000000000000000000000000000000000000000c16202a343e48525c66707a848e98ff04╱
↓
This message will not appear if the link is customized as ↓
V.24.↲
↲
┆a1┆Waiting for menu┆e1┆ (CSTEXT,8)↲
The display device is attached to a sublink of an X.21-BSC ↓
host link, i.e. a specific RC3803 FE has been selected, but ↓
the menu shown by this FE to indicate the hosts or appli┄↓
cations available at the remote site has not yet been ↓
received by the CU. This message will only be shown for a ↓
brief time until the FE menu has been obtained. If the CU ↓
fails to communicate with the remote FE, the message will be ↓
replaced by another message (typically "Call status CP") ↓
indicating the reason for the failure.↲
This message can only appear if the link is customized as ↓
X.21-BSC.↲
↲
┆a1┆Communication status messages, local host links↲
When an emulated 3270 terminal is attached to a local host ↓
link, i.e. communicates with an RC8000 host via an ADP, ↓
there is only one message which may appear in the commu┄↓
nication status part of the status line (positions 57 ↓
through 80), viz:↲
╞ Host timeout, data lost↲
This message indicates that the RC8000 has failed to receive ↓
input data from the ADP, most likely because the RC8000 has ↓
ceased to operate properly. The message cannot be custo┄↓
mized.↲
════════════════════════════════════════════════════════════════════════
↓
┆14┆┆b3┆↲
┆14┆┆b1┆┆b0┆ RC3931 Communications Processor┆05┆Appendices H↲
┆14┆┆b2┆┆b0┆ H Appendices┆05┆RC3931 Communications Processor ↲
┆15┆┆b3┆↲
┆15┆┆b1┆┆b0┆ Update 1/86┆05┆Page H.1-┆0b┆ H↲
┆15┆┆b2┆┆b0┆ H Page H.1-┆0b┆┆05┆Update 1/86 ↲
╱04002d4e0a000600000000030c4731000000000000000000000000000000000000000000000000000c1116202a343e48525c66707a848eff04╱
╱04002d4e0a000600000000030c4731400000000000000000000000000000000000000000000000000c16202a343e48525c66707a848e98ff04╱
↓
┆a1┆H.1 References↲
↲
(1)╞ RCSL No.991 10413↲
╞ ┆a1┆Users Guide for the RC39↲
↲
╞ ┆84┆The general user's guide for the RC39 MUCS describing ↓
┆19┆┆85┆┄┄the RC39 LAP.↲
↲
(2)╞ RCSL No.991 10412↲
╞ ┆a1┆Partner IBM 3270 Emulator, Operation Guide↲
↲
(3)╞ RCSL No.991 10338↲
╞ ┆a1┆RC45 IBM 3180 Emulator, User's Guide↲
↲
(4)╞ RCSL No.991 09859↲
╞ ┆a1┆RC855 IBM 3270 Emulator, Betjeningsvejledning↲
↲
╞ ┆84┆User's guide for the 3270 terminal emulator program for ↓
┆19┆┆85┆┄┄the RC 855 terminal. Published in Danish.↲
↲
(5)╞ RCSL No.991 10266↲
╞ ┆a1┆RC39 Programmer's Toolkit for 3270 Communication↲
↲
╞ ┆84┆The toolkit is a library of routines which allow an ↓
┆19┆┆85┆┄┄application program running on the RC39 LAP to interact ↓
┆19┆┆85┆┄┄with a remote host as if it were a 3270 display device. ↓
┆19┆┆85┆┄┄The manual, intended for programmers, describes these ↓
┆19┆┆85┆┄┄routines.↲
↲
(6)╞ RCSL No.991 10227↲
╞ ┆a1┆RC8000 Attached Device Processor, User's Guide↲
↲
╞ ┆84┆A description of the Attached Device Processor which is ↓
┆19┆┆85┆┄┄used to attach an RC8000 mainframe computer to a LAN.↲
↲
════════════════════════════════════════════════════════════════════════
↓
(7) RCSL No.991 0710↲
╞ ┆a1┆RC39 Teletex, Brugervejledning↲
↲
╞ ┆84┆User's guide for the Teletex service. Published in ↓
┆19┆┆85┆┄┄Danish.↲
════════════════════════════════════════════════════════════════════════
↓
┆14┆┆b3┆↲
┆14┆┆b1┆┆b0┆ RC3931 Communications Processor┆05┆Appendices H↲
┆14┆┆b2┆┆b0┆ H Appendices┆05┆RC3931 Communications Processor ↲
┆15┆┆b3┆↲
┆15┆┆b1┆┆b0┆ Update 0/85┆05┆Page H.2-┆0b┆ H↲
┆15┆┆b2┆┆b0┆ H Page H.2-┆0b┆┆05┆Update 0/85 ↲
╱04002d4e0a000600000000030c4731400000000000000000000000000000000000000000000000000c16202a343e48525c66707a848e98ff04╱
╱04002d4e0a000600000000030c4731000000000000000000000000000000000000000000000000000c1116202a343e48525c66707a848eff04╱
↓
┆a1┆H.2 Character Sets↲
↲
This appendix contains charts showing the different national ↓
character sets that are available with RC terminal products. ↓
Each chart shows which characters belong to the character ↓
set in question and how they are encoded.↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
Figure H.2-1. US English character set↲
════════════════════════════════════════════════════════════════════════
↓
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
Figure H.2-2. UK English character set↲
════════════════════════════════════════════════════════════════════════
↓
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
Figure H.2-3. German character set↲
════════════════════════════════════════════════════════════════════════
↓
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
Figure H.2-4. Swedish character set↲
════════════════════════════════════════════════════════════════════════
↓
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
Figure H.2-5. Standard Danish character set↲
↲
The Standard Danish character set is only available on RC855 ↓
terminals.↲
════════════════════════════════════════════════════════════════════════
↓
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
Figure H.2-6. Danish OS (public sector) character set↲
↲
The Danish OS character set as shown in Figure H.2-6 is ↓
known under the abbreviation DOS3. It is supported as shown ↓
on RC45 terminals and RC750 PCs. On RC855 terminals two ↓
versions of the Danish OS character set are available, both ↓
of which differ from DOS3 in the representation of the ↓
character with code 60┆82┆Hex┆81┆, i.e. grave accent (┆a8┆Æ┆e8┆). In DOS1 ↓
the replacement character is o umlaut (@), in DOS2 it is up ↓
arrow (`).↲
════════════════════════════════════════════════════════════════════════
↓
┆14┆┆b3┆↲
┆14┆┆b1┆┆b0┆ RC3931 Communications Processor┆05┆Appendices H↲
┆14┆┆b2┆┆b0┆ H Appendices┆05┆RC3931 Communications Processor ↲
┆15┆┆b3┆↲
┆15┆┆b1┆┆b0┆ Update 0/85┆05┆Page H.3-┆0b┆ H↲
┆15┆┆b2┆┆b0┆ H Page H.3-┆0b┆┆05┆Update 0/85 ↲
╱04002d4e0a000600000000030c4731400000000000000000000000000000000000000000000000000c16202a343e48525c66707a848e98ff04╱
╱04002d4e0a000600000000030c4731400000000000000000000000000000000000000000000000000c16202a343e48525c66707a848e98ff04╱
↓
┆a1┆H.3 EBCDIC Character Codes↲
↲
This appendix contains charts showing the standard EBCDIC ↓
encodings of the various national character sets which are ↓
used for 3270 remote host communication. It is possible to ↓
customize the CP to support differing encodings. Those shown ↓
in this appendix are supported by the *.CNV auxiliary files ↓
distributed as part of the basic SW package for the CP ↓
(SW3901), cf. section E, Selecting character conversion.↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
Figure H.3-1. US English EBCDIC codes.↲
↲
US English EBCDIC code may be used if the character set of ↓
the terminal cluster is US English, cf. appendix H.2.↲
════════════════════════════════════════════════════════════════════════
↓
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
Figure H.3-2. UK English EBCDIC codes.↲
↲
UK English EBCDIC code may be used if the character set of ↓
the terminal cluster is UK English, cf. appendix H.2.↲
════════════════════════════════════════════════════════════════════════
↓
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
Figure H.3-3. German EBCDIC codes.↲
↲
German EBCDIC code may be used if the character set of the ↓
terminal cluster is German, cf. appendix H.2.↲
════════════════════════════════════════════════════════════════════════
↓
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
Figure H.3-4. German alternate EBCDIC codes.↲
↲
German alternate EBCDIC code may be used if the character ↓
set of the terminal cluster is German, cf. appendix H.2.↲
The German character set includes five characters which do ↓
not appear in the chart above ($┆a8┆YÆ┆e8┆#"). The conversion table ↓
modifications distributed as file GERMANA.CNV cause these ↓
characters to be transmitted to a remote host as blanks ↓
(code 40┆82┆Hex┆81┆).↲
════════════════════════════════════════════════════════════════════════
↓
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
Figure H.3-5. Swedish EBCDIC codes.↲
↲
Swedish EBCDIC code may be used if the character set of the ↓
terminal cluster is Swedish, cf. appendix H.2.↲
════════════════════════════════════════════════════════════════════════
↓
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
Figure H.3-6. Swedish alternate EBCDIC codes.↲
↲
Swedish (alternate) EBCDIC code may be used if the character ↓
set of the terminal cluster is Swedish, cf. appendix H.2.↲
════════════════════════════════════════════════════════════════════════
↓
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
Figure H.3-7. Standard Danish EBCDIC codes.↲
↲
Standard Danish EBCDIC code may be used if the character set ↓
of the terminal cluster is Standard Danish, cf. appendix ↓
H.2.↲
════════════════════════════════════════════════════════════════════════
↓
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
Figure H.3-8. Standard Danish alternate EBCDIC codes.↲
↲
Standard Danish alternate EBCDIC code may be used if the ↓
character set of the terminal cluster is Standard Danish, ↓
cf. appendix H.2.↲
The conversion table modifications distributed as file ↓
STDKA.CNV cause both Å and $ to be transmitted to a remote ↓
host as code 5B┆82┆Hex┆81┆. When this code is received from a remote ↓
host it is converted to the internal code for Å (5D┆82┆Hex┆81┆). ↓
Similarly, Æ and ┆a8┆Y┆e8┆ are both transmitted as code 7B┆82┆Hex┆81┆, and ↓
════════════════════════════════════════════════════════════════════════
↓
when this code is received it is converted to the internal ↓
code for Æ (5B┆82┆Hex┆81┆).↲
The Standard Danish character set is only available on ↓
RC855 terminals.↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
Figure H.3-9. Danish OS EBCDIC codes.↲
↲
Danish OS EBCDIC code may be used if the character set of ↓
the terminal cluster is Danish OS, cf. appendix H.2.↲
════════════════════════════════════════════════════════════════════════
↓
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
↲
Figure H.3-10. Danish OS alternate EBCDIC codes.↲
↲
Danish OS alternate EBCDIC code may be used if the character ↓
set of the terminal cluster is Danish OS, cf. appendix H.2.↲
The conversion table modifications distributed as file ↓
DOSA.CNV cause both Å and $ to be transmitted to a remote ↓
host as code 5B┆82┆Hex┆81┆. When this code is received from a remote ↓
host it is converted to the internal code for Å (5D┆82┆Hex┆81┆).↲
════════════════════════════════════════════════════════════════════════
↓
┆14┆┆b3┆↲
┆14┆┆b1┆┆b0┆ RC3931 Communications Processor┆05┆V.24/X.21 Connectors H↲
┆14┆┆b2┆┆b0┆ H V.24/X.21 Connectors┆05┆RC3931 Communications Processor ↲
┆15┆┆b3┆↲
┆15┆┆b3┆↲
┆15┆┆b1┆┆b0┆ Update 0/85┆05┆Page H.4-┆0b┆ H↲
┆15┆┆b2┆┆b0┆ H Page H.4-┆0b┆┆05┆Update 0/85 ↲
╱04002d4e0a000600000000030c4731400000000000000000000000000000000000000000000000000c16202a343e48525c66707a848e98ff04╱
╱04002d4e0a000600000000030c4731400000000000000000000000000000000000000000000000000c16202a343e48525c66707a848e98ff04╱
↓
┆a1┆H.4 V.24/X.21 Connectors↲
↲
The connectors used to mount the signal cables for external ↓
communications according to the V.24 or X.21 interface ↓
standards are located on the connector panel of the RC39 ↓
cabinet as described in section E, External cable connec┄↓
tions. The present description applies to the connectors ↓
marked J11, J12, J13 and J14. Standard 25-pin D-connectors ↓
are used with pin assignments allowing the same connector to ↓
be used for either V.24 or X.21 connections by means of ↓
different cables.↲
The correspondence between connector pins and those V.24 ↓
interface circuits which are used complies with ISO standard ↓
╱04002d4e0a000600000000020c4731400000000000000000000000000000000000000000000000000c16202a343e48525c66707a848e98ff04╱
╱04002d4e0a000600000000030c4731400000000000000000000000000000000000000000000000000c16202a343e48525c66707a848e98ff04╱
↓
2110 as shown below:↲
↲
┆a1┆pin no.╞ ╞ V.24 interface circuit↲
1╞ ╞ protective ground↲
2╞ ╞ transmitted data (103)↲
3╞ ╞ received data (104)↲
4╞ ╞ request to send (105)↲
5╞ ╞ ready for sending (106)↲
6╞ ╞ data set ready (107)↲
7╞ ╞ signal ground (102)↲
8╞ ╞ carrier (109)↲
15╞ ╞ transmit clock (114)↲
17╞ ╞ receive clock (115)↲
20╞ ╞ data terminal ready (108/2)↲
↲
╱04002d4e0a000600000000030c4731400000000000000000000000000000000000000000000000000c16202a343e48525c66707a848e98ff04╱
╱04002d4e0a000600000000020c4731400000000000000000000000000000000000000000000000000c16202a343e48525c66707a848e98ff04╱
↓
The X.21 interface circuits are assigned to the pins no┄t ↓
╱04002d4e0a000600000000020c4731400000000000000000000000000000000000000000000000000c16202a343e48525c66707a848e98ff04╱
╱04002d4e0a000600000000030c4731400000000000000000000000000000000000000000000000000c16202a343e48525c66707a848e98ff04╱
↓
used for V.24 signals as shown below:↲
↲
┆a1┆pin no.╞ ╞ X.21 interface circuit↲
1╞ ╞ protective ground↲
7╞ ╞ signal ground (G)↲
9╞ ╞ transmit (T) A↲
10╞ ╞ indication (I) A↲
12╞ ╞ transmit (T) B↲
14╞ ╞ control (C) B↲
16╞ ╞ signal element timing (S) B↲
18╞ ╞ signal element timing (S) A↲
19╞ ╞ receive (R) B↲
21╞ ╞ receive (R) A↲
24╞ ╞ indication (I) B↲
25╞ ╞ control (C) A↲
↲
╱04002d4e0a000600000000030c4731400000000000000000000000000000000000000000000000000c16202a343e48525c66707a848e98ff04╱
╱04002d4e0a000600000000020c4731400000000000000000000000000000000000000000000000000c16202a343e48525c66707a848e98ff04╱
↓
════════════════════════════════════════════════════════════════════════
↓
Pin 11 is used to distinguish a cable intended for a V.24 ↓
interface from one intended for X.21. The signal should be ↓
ON for V.24, OFF for X.21.↲
════════════════════════════════════════════════════════════════════════
↓
┆14┆┆b3┆↲
┆14┆┆b1┆┆b0┆ RC3931 Communications Processor┆05┆Appendices H↲
┆14┆┆b2┆┆b0┆ H Appendices┆05┆RC3931 Communications Processor ↲
┆15┆┆b3┆↲
┆15┆┆b1┆┆b0┆ Update 1/85┆05┆Page H.5-┆0b┆ H↲
┆15┆┆b2┆┆b0┆ H Page H.5-┆0b┆┆05┆Update 1/85 ↲
╱04002d4e0a000600000000030c4731000000000000000000000000000000000000000000000000000c161824263e48525c66707a84ffffff04╱
╱04002d4e0a000600000000030c4731400000000000000000000000000000000000000000000000000c16202a343e48525c66707a848e98ff04╱
↓
┆a1┆H.5 Host Link Information Displays↲
↲
Information about the current state of a remote host link ↓
may be displayed on an emulated display device, i.e. a ↓
terminal or PC running the appropriate emulator program, ↓
working in ┆a1┆link information mode┆e1┆. Information is obtained ↓
about the link to which the device is attached. Only one ↓
device per link may be active in link information mode at a ↓
time. The key combination which is used to enter link ↓
information mode depends on the terminal (or PC) as follows:↲
↲
╞ ┆a1┆terminal╞ key combination↲
╞ ╞ RC45╞ ╞ ALT+TEST↲
╞ ╞ RC855╞ ╞ SELECT T↲
╞ ╞ RC750╞ ╞ CTRL+T↲
↲
The same key combination is used to leave link information ↓
mode and return to normal emulation.↲
Note that the contents of the device buffer is abandoned ↓
when link information mode is entered. The display will ↓
therefore be cleared when the return is made to normal ↓
emulation.↲
The information displays which are available are different ↓
for BSC and SNA/SDLC. The two cases are dealt with in the ↓
two sections that follow.↲
↲
┆a1┆H.5.1 BSC Link Information↲
↲
Two functions are available: display BSC statistics and ↓
reset BSC statistics, i.e. counters. The choice is made ↓
from a menu which is shown when link information mode is ↓
entered and again whenever the CLEAR key is pressed.↲
The BSC statistics display is self-explanatory.↲
↲
════════════════════════════════════════════════════════════════════════
↓
┆a1┆H.5.2 SNA/SDLC Link Information↲
↲
Three displays are available: SNA statistics, SDLC stati┄↓
stics and X.21 statistics, the latter only for an SDLC-X.21 ↓
link. The choice is made from a menu which is shown when ↓
link information mode is entered and again whenever the ↓
CLEAR key is pressed.↲
The menu also provides a reset statistics function, which ↓
causes all the statistics (counters) pertaining to the link ↓
to be reset. Each of the statistics displays shows the time ↓
in minutes and seconds since the last time the statistics ↓
were reset (or the CU was loaded).↲
The three displays are discussed in detail below.↲
↲
┆a1┆SNA statistics↲
↲
This display contains information about the customizations ↓
of printer sharing and maximum device number and about the ↓
state of the Physical Unit (PU), the Logical Units (LU) and ↓
the LU-LU sessions. If the PU is inactive, the SNA stati┄↓
stics will appear as shown in Figure H.5.1. If the PU is ↓
active the display is extended with a line for each LU that ↓
has been activated by the host, see Figure H.5.2.↲
↲
╱04002d4e0c000600000000020c5b31400000000000000000000000000000000000000000000000000c0f19232d37414b525c66707a848eff04╱
╱04002d4e0a000600000000030c4731000000000000000000000000000000000000000000000000000c161824263e48525c66707a84ffffff04╱
↓
↲
╞ S N A S T A T I S T I C S 1 MIN. 18 SEC.↲
↲
╞ PU INACTIVE↲
╞ Max. number of devices = 64↲
╞ Printer sharing is between brackets↲
↲
↲
↲
↲
↲
╞ Press CLEAR to return to statistics menu↲
↲
╱04002d4e0a000600000000030c4731400000000000000000000000000000000000000000000000000c16202a343e48525c66707a848e98ff04╱
╱04002d4e0c000600000000020c5b31400000000000000000000000000000000000000000000000000c0f19232d37414b525c66707a848eff04╱
↓
↲
Figure H.5.1. SNA statistics display for an inactive PU.↲
↲
════════════════════════════════════════════════════════════════════════
↓
╱04002d4e0c000600000000020c5c31600000000000000000000000000000000000000000000000000f19232d37414b56606a747e8892ffff04╱
╱04002d4e0a000600000000030c4731400000000000000000000000000000000000000000000000000c16202a343e48525c66707a848e98ff04╱
↓
↲
╞ S N A S T A T I S T I C S 1 MIN. 18 SEC.↲
↲
╞ PU ACTIVE↲
╞ Max. number of devices = 64↲
╞ Printer sharing is between brackets↲
↲
╞ LU DEV LU-LU SESSION DIV INTERNAL↲
↲
╞ ╞ ╞ type hostname pacing bracket chain ss dir↲
↲
╞ 2 0 C ACTIVE-2 2 TESTIMS 0 0 0 0 BETB BETC C N XXX...XX↲
╞ 3 1 D INACTIVE↲
╞ 4 2 D INACTIVE↲
╞ 5 3 D INACTIVE↲
↲
↲
↲
↲
╞ Press CLEAR to return to statistics menu↲
↲
╱04002d4e0a000600000000020c473160000000000000000000000000000000000000000000000000141e242e38424c56606a747e8892ffff04╱
╱04002d4e0c000600000000020c5c31600000000000000000000000000000000000000000000000000f19232d37414b56606a747e8892ffff04╱
↓
↲
Figure H.5.2. SNA statistics display for an active PU.↲
↲
↲
Each LU line (cf. Figure H.5.2) should be interpreted as:↲
↲
LU╞ is the LU number as specified in the host (2-129)↲
↲
DEV╞ ┆84┆is the corresponding device number (0-127) and the ↓
┆19┆┆88┆┄┄state of the device↲
↲
╞ C╞ device is connected,↲
╞ D╞ device is disconnected,↲
╞ R╞ device is reserved (printer only).↲
↲
LU-LU SESSION↲
╞ ┆84┆gives the state of a session between the LU and an ↓
┆19┆┆88┆┄┄application in the host↲
↲
╞ INACTIVE╞ ┆84┆no session exists; the rest of the line ↓
┆19┆┆92┆┄┄will be empty.↲
↲
╞ ACTIVE-1╞ ┆84┆session exists but data cannot be sent ↓
┆19┆┆92┆┄┄because no Start Data Traffic command has ↓
┆19┆┆92┆┄┄been sent by the host.↲
↲
╞ ACTIVE-2╞ ┆84┆session exists and data can be sent. This ↓
┆19┆┆92┆┄┄is the normal active state of a session.↲
↲
╞ ACTIVE-3╞ ┆84┆session exists and is closing down after ↓
┆19┆┆92┆┄┄Shutdown command is received from the ↓
┆19┆┆92┆┄┄host.↲
↲
╞ CLEARING╞ session is about to be removed.↲
↲
════════════════════════════════════════════════════════════════════════
↓
type╞ is the type of the session↲
↲
╞ 1╞ SNA character stream printer↲
╞ 2╞ 3270 display↲
╞ 3╞ 3270 printer↲
↲
hostname↲
╞ is the name of the application in the host↲
↲
pacing╞ ┆84┆4 numbers giving receive pacing count, transmit ↓
┆19┆┆88┆┄┄pacing count, current allowed receive count, current ↓
┆19┆┆88┆┄┄allowed transmit count. If zeroes are shown, pacing ↓
┆19┆┆88┆┄┄is not used for this session.↲
↲
bracket╞ is the bracket state↲
↲
╞ BETB╞ between brackets↲
╞ INB╞ in bracket↲
╞ PEND╞ pending begin bracket↲
↲
chain╞ is the chain state↲
↲
╞ BETC╞ between chains↲
╞ INC╞ in chain↲
↲
ss╞ is the session state↲
↲
╞ C╞ contention↲
╞ E╞ error↲
╞ R╞ receive↲
╞ S╞ send↲
↲
dir╞ is the direction↲
↲
╞ F╞ from host↲
╞ N╞ neutral↲
╞ T╞ to host↲
↲
DIV INT.↲
╞ ┆84┆14 characters with internal information about ↓
┆19┆┆88┆┄┄program states etc.↲
╱04002d4e0a000600000000030c473160000000000000000000000000000000000000000000000000141e242e38424c56606a747e8892ffff04╱
╱04002d4e0a000600000000020c473160000000000000000000000000000000000000000000000000141e242e38424c56606a747e8892ffff04╱
↓
↲
Each SNA statistics display has room for 10 lines of LU ↓
information. If there is more information than shown, this ↓
is indicated in the bottom part of the display, and PA1/PF1 ↓
can be used to retrieve subsequent lines.↲
↲
════════════════════════════════════════════════════════════════════════
↓
┆a1┆SDLC statistics↲
↲
This display contains information about the customization of ↓
the link (SDLC-address, terminal-ID, X.21/V.24, nrzi, COM ↓
board number, and host link identification; for V.24 also ↓
half/full duplex, point-to-point/multi-point and Data ↓
Terminal Ready handling) and the activity on the link ↓
(received/transmitted frames etc.).↲
The display for an SDLC-V.24 link is shown in Figure H.5.3 ↓
and the display for an SDLC-X.21 link in Figure H.5.4.↲
↲
↲
╱04002d4e0c000600000000020c5731600000000000000000000000000000000000000000000000000f3037414b56606a747e8892ffffffff04╱
╱04002d4e0a000600000000030c473160000000000000000000000000000000000000000000000000141e242e38424c56606a747e8892ffff04╱
↓
╞ S D L C / L I N K S T A T I S T I C S 0 MIN. 38 SEC.↲
↲
╞ SDLC-addr = C1↲
╞ NRZI = yes↲
╞ Term-id = 01043↲
↲
╞ V.24 / Full duplex / Point-to-point / Nonswitched↲
╞ COM board = 1 / SNA link 1↲
↲
╞ Received I-frames╞ 1752↲
╞ Transmitted I-frames╞ 1587↲
╞ Received RNR╞ 0↲
╞ Transmitted RNR╞ 0↲
╞ Received TEST╞ 0↲
╞ Transmitted TEST╞ 0↲
╞ Receiver overrun╞ 0↲
╞ Transmitter underrun╞ 0↲
╞ Received CRC-errors╞ 0↲
╞ Received aborts╞ 0↲
╞ Retransmitted I-frames╞ 0↲
╞ CD failures╞ 0↲
╞ CTS failures╞ 0↲
↲
╞ Press CLEAR to return to statistics menu↲
↲
↲
╱04002d4e0c000600000000020c4731600000000000000000000000000000000000000000000000000f1a242e38424c56606a747e88929cff04╱
╱04002d4e0c000600000000020c5731600000000000000000000000000000000000000000000000000f3037414b56606a747e8892ffffffff04╱
↓
╞ ↓
╱04002d4e0a000600000000030c473160000000000000000000000000000000000000000000000000101a242e38424c56606a747e88929cff04╱
╱04002d4e0c000600000000020c4731600000000000000000000000000000000000000000000000000f1a242e38424c56606a747e88929cff04╱
↓
↲
Figure H.5.3. SDLC statistics display for an SDLC-V.24 link↲
↲
┆a1┆┆e1┆If the link uses a dial-up line, no attention should be paid ↓
to the CD failures counter.↲
════════════════════════════════════════════════════════════════════════
↓
╱04002d4e0c000600000000020c5731600000000000000000000000000000000000000000000000000f3037414b56606a747e88929cffffff04╱
╱04002d4e0a000600000000030c473160000000000000000000000000000000000000000000000000101a242e38424c56606a747e88929cff04╱
↓
↲
╞ S D L C / L I N K S T A T I S T I C S 2 MIN 57 SEC↲
↲
╞ SDLC-addr = C1↲
╞ NRZI = no↲
╞ Term-id = 23CBF↲
↲
╞ X.21↲
╞ COM board = 2 / SNA link 1↲
↲
╞ Received I-frames╞ 12↲
╞ Transmitted I-frames╞ 8↲
╞ Received RNR╞ 0↲
╞ Transmitted RNR╞ 0↲
╞ Received TEST╞ 0↲
╞ Transmitted TEST╞ 0↲
╞ Receiver overrun╞ 0↲
╞ Transmitter underrun╞ 0↲
╞ Received CRC-errors╞ 0↲
╞ Received aborts╞ 0↲
╞ Retransmitted I-frames╞ 0↲
↲
↲
↲
╞ Press CLEAR to return to statistics menu↲
↲
╱04002d4e0a000600000000030c473160000000000000000000000000000000000000000000000000101a242e38424c56606a747e88929cff04╱
╱04002d4e0c000600000000020c5731600000000000000000000000000000000000000000000000000f3037414b56606a747e88929cffffff04╱
↓
↲
Figure H.5.4. SDLC statistics display for an SDLC-X.21 link↲
↲
════════════════════════════════════════════════════════════════════════
↓
┆a1┆X.21 statistics↲
↲
This display contains information about the activity at the ↓
X.21 interface level (outgoing calls, incoming calls, ↓
received call progress codes and error codes). The ↓
subscriber numbers of the CU and the host, and the state of ↓
the X.21 Short Hold Mode session are also shown (cf. Figure ↓
H.5.5).↲
↲
╱04002d4e0c000600000000020c5331600000000000000000000000000000000000000000000000000f19232d37414b56606a747e8892ffff04╱
╱04002d4e0a000600000000030c473160000000000000000000000000000000000000000000000000101a242e38424c56606a747e88929cff04╱
↓
╞ X 2 1 S T A T I S T I C S 3 MIN. 44 SEC.↲
↲
╞ CU-DX = 125333 HOST-DX = 125334↲
╞ Short Hold Mode Session = active↲
↲
╞ Outgoing calls OK╞ ╞ 4↲
╞ Outgoing calls CP code╞ 1↲
╞ Outgoing calls Error╞ 0↲
╞ Incoming calls OK╞ ╞ 2↲
╞ Incoming calls Error╞ 0↲
↲
╞ CP codes:↲
╞ 45= 1↲
╞ Error codes: none↲
↲
↲
↲
↲
╞ Press CLEAR to return to statistics menu↲
↲
╱04002d4e0a000600000000030c473160000000000000000000000000000000000000000000000000101a242e38424c56606a747e88929cff04╱
╱04002d4e0c000600000000020c5331600000000000000000000000000000000000000000000000000f19232d37414b56606a747e8892ffff04╱
↓
↲
Figure H.5.5. X.21 statistics display for an SDLC-X.21 link↲
════════════════════════════════════════════════════════════════════════
↓
↲
┆1a┆┆1a┆ ↓
Terminal Ready handlinginformatitirmal emulation.↲
Note that the contents of the device