top - download
⟦18e3f8959⟧ Wang Wps File
Length: 16099 (0x3ee3)
Types: Wang Wps File
Notes: Spelunked
Names: »~ORPHAN53.08«
Derivation
└─⟦9a531dff6⟧ Bits:30006257 8" Wang WCS floppy, CR 0157A
└─ ⟦this⟧ »~ORPHAN53.08«
WangText
CHAPTER
6
Page
#
DOCUMENT
III TECHNICAL
PROPOSAL
Apr. 29,
1982
6.6 Terminal Access Software ...................
6.6.1 Introduction ...........................
6.6.2 Line Handlers ..........................
6.6.2.1 Asynchronous Start/Stop Protocols ..
6.6.2.2 BSC Protocol .......................
6.6.2.3 SDLC Protocol .....................
6.6.2.4 HDLC Protocol ......................
6.6.3 Device Handlers ........................
6.6.3.2 VDU Support ........................
6.6.3.2.1 IBM 3270 .......................
6..3.3.1 IBM 2780 and 3780 BSC ..........
6.6.3.3.2 IBM S3 HASP Work Station BSC ..
6.6.3.3.4 Univac NTR Work Station ........
6.6.4 Emulators ..............................
6.6.4.1 IBM 3270 BSC ......................
6.6.4.2 IBM 2780 & 3780 BSC ................
6.6.4.3 HASP Work Station BSC ..............
6.6.4.4 IBM SNA PU.T1 ......................
6.6.4.5 IBM SNA PU.T2 ......................
6.6.4.6 Transparen Interface ..............
6.6.4.7 Terminal Interface Support Summary .
6.6.5 External resources Manager .............
6.6.6 Node Logical Unit Services .............
6.6.7 Node Session Manager ...................
6.6.8 Connection and Allocation Services .....
6.6.9 Configuration Manager and Status Reporter
…86…1 …02… …02… …02… …02…
6.6 T̲e̲r̲m̲i̲n̲a̲l̲ ̲A̲c̲c̲e̲s̲s̲ ̲S̲o̲f̲t̲w̲a̲r̲e̲
The scope of this section is to present the functions
supported by the Terminal Access Software and to indicate
the underlying structure of the softwre package. The
description in this section indicates data flow, protocols,
and control sequences that can be associated with individual
software components.
6.6.1 I̲n̲t̲r̲o̲d̲u̲c̲t̲i̲o̲n̲
The Terminal Access Software is interfaced to the nodal
switch sotware (NSS). The interface can be either
with the Datagram services of the NSS or the virtual
transport services of the NSS.
The basic components of the TAS are Line handlers,
device handlers, emulators, connection allocation services,
and Node ogical unit services. External Resources Manager,
Configuration Manager and Status Reporter, and Node
Session Manager.
For the sole purpose of description in this chapter,
the basic components referenced above are equalled
to "tasks". The softwae packaging method employed
combines the tasks into appropriate processes. Fig.
6.6.-1 shows the typical software package.…86…1
…02… …02… …02… …02…
Fig. 6.6-1…01…Framework Package for Terminal Access Software…86…1 …02… …02… …02… …02…
6.6.2 L̲i̲n̲e̲ ̲H̲a̲n̲d̲l̲e̲r̲s̲
The TAS provides support for one asynchronous and two
synchronous line protocols. These protocols may work
in several modes.
6.6.2.1 A̲s̲y̲n̲c̲h̲r̲o̲n̲o̲u̲s̲ ̲S̲t̲a̲r̲t̲/̲S̲t̲p̲ ̲P̲r̲o̲t̲o̲c̲o̲l̲s̲
This protocol collects a string of characters from
the line and forwards it to the device handler, or
it receives a string of characters from the device
handler and outputs it, character by character on the
line.
The following charateristics apply:
o The line speed can be selected among one of the speeds
mentioned above in the range from
300 - 4800 bps.
o The number of bits per character can be specified
between 5 and 8. Characters are forwarded to the
device handler n 8-bit bytes, with the significant
bits in the low order positions, and the remaining
bits set to zero.
o Even, odd, or no parity can be specified. Parity
errors are signalled to the device handler and all
bits in the erroneous byte are set to ne.
o The stop bit can have a length of 1, 1 1/2, or 2
normal bits.
o When characters are received, they may or may not
be echoed back on the transmitting circuit.
o A time out value can be specified. When time out
occurs, any received charaters are forwarded to the
device handler.
o A data forwarding character can be specified. When
this character is encountered, all received characters
are sent to the device handler.
o The numbers of nulls to be sent as time fill characters
aftr a carriage return can be specified.
o The break condition, defines as the signal being
low min. 150 ms, can both be received and transmitted.…86…1
…02… …02… …02… …02…
The above parameter specification facilities are exploited
to realize the necessary implementations for ACDN.
6.6.2.2 B̲S̲C̲ ̲P̲r̲o̲t̲o̲c̲o̲l̲
The synchronous character oriented BSC protcol is supported
as defined in: the IBM publication General Information
- Binary Synchronous Communications, GA27-3004, with
the following provisions:
o Among the speeds mentioned above, the line speed
can be selected in the range from 1200 to 960 bps.
o The pad character used for line turn around can be
specified.
o The protocol can or cannot be in transparent mode,
i.e. all control characters being preceded by a DLE
character.
o Point-to-point or multipoint line discipline is maintined.
On a multipoint line, the line handler acts as a
master.
o The character set used is EBCDIC.
o The following parameters which have a direct impact
of the BSC protocol operation can be specified:
- the number of consecutive negative reponses to
polling which are accepted before scanning continues,
- the number of retries performed when a text block
is negatively acknowledged,
o The following parameters can be specified to manage
the traffic mix on a line:
- the poll timeinterval for devices not in sessions,
- service order for devices on the line,
- number of devices on the line which are considered
in each scan.
These parameters may be changed by the NCC operator
during normal operation.
6.6.2.3 S̲D̲L̲C̲ ̲P̲r̲o̲t̲o̲c̲o̲l̲
The synchronous bit oriented SDLC protocol is supported
as defined in: IBM SDLC General Information GA27-3093,
with the following provisions:
o Among thespeeds mentioned above, the line speed
can be selected in the range from 1200 to 19200
bps.
o The line handler acts as the master.
6.6.2.4 H̲D̲L̲C̲ ̲P̲r̲o̲t̲o̲c̲o̲l̲
The synchronous bit oriented protocol is supported
as defined in CCITT recommendations Yllow book (1980).
6.6.3 D̲e̲v̲i̲c̲e̲ ̲H̲a̲n̲d̲l̲e̲r̲s̲
The device handlers are individual tasks provided to
support attachment of different terminal types to the
ACDN. The device handlers are concerned with providing
the necessary device control functions an are not concerned
with presentation control and protocol functions for
a particular device. The following descriptions of
the device support for TTY presents the baseline facilities
for TTY with the following assumption:
o TTY terminals appear s IBM3767 terminals for IBM
host access.
o TTY terminals appear as conversational devices
(category 3, Buffered printing (class 2), DCT1000
terminals for Univac host access.
6.6.3.1 T̲T̲Y̲ ̲S̲u̲p̲p̲o̲r̲t̲
The TTY device handler has the following characteristics:
o The 7 bit ASCII character set is used.
o Two modes are supported: system mode and normal
mod.
o Device characteristics may be changed by commands.
The terminal is initially in system mode. When a Log
on has been carried out, the terminal enters normal
mode. As long as the terminal is engaged in a session,
it is possible to switch beween the two modes by pressing
the DLE key as first input character.
In normal mode, data is passed between the emulator
and the terminal according to the current setting of
the device characteristics which are explained below.
Device handler cmmands are used either to signal special
conditions to the emulator, or to change presentation
service functions. The following commands are defined:
*TTY Parameter-1: value-1, ...parameter-n: value-n,
where a combination of the parameters in tble
6.6-1 are allowed.
*TAB Set tabulator. The device handler will display
a line showing the current input tabulator
setting, if any. Each tabulator stop is indicated
by a non-blank character. If the user wants
to change the tabulator setting he can input
a line where non-blank characters will define
the tabulator stops.
E̲x̲a̲m̲p̲l̲e̲:
DLE
*TAB
x X (old set of tab stops)
x x x (new set of tab stops)
DLE
Tabulator stops can only beset by the user not from
the host. The tabulator function is performed when
the HT character is received from the terminal. The
HT character becomes part of the input string and,
if a tabulator stop is defined to the right of the
current input poition, a sufficient number of spaces
are output to reach the tabulator stop position. HT
characters received from the host do not cause special
processing.
P̲a̲r̲a̲m̲e̲t̲e̲r̲ F̲u̲n̲c̲t̲i̲o̲n̲ D̲e̲f̲a̲u̲l̲t̲ V̲a̲l̲u̲e̲
E Echo.
1
=
Echo
on,
=
echo
off
1 0/1
C Character
delete.
Te
previous
character
is
deleted
and
if
echo
is
on,
BS-SP-BS
is
echoed.
DEL character
L Line
delete.
The
input
line
is
discarded
and
if
echo
is
on,
-X-CR-LF
is
echoed.
CAN character
P Page
length
24 1
number
100
W Output
pae
width
80 1
number
256
I Maximum
input
line
length
80 1
number
256
R Roll/scroll
mode.
0=roll,
1=scroll roll 0/1
In
scroll
mode,
output
is
halted
when
a
whole
page
has
been
received.
Output
is
resumed
when
the
data
for-
wardin
character
is
input.
S Solicit.
Indication
of
ready
for
input
conduction
id
LF-solicit
character. character
T Data
forwarding
character.
This
character
terminates
the
input
line
and
causes
it
to
be
forwarded
to
the
emulator. CRcharacter
D Padding
after
carriage
return 0 0
number
7
Number
of
NUL
characters
send
after
carriage
return.
X XON
(DC1)
and
XOFF
(DC3)
control 0 0/1
1
=
used,
0
=
not
used
Note:
A
parameter
value
which
is
a
character
can
either
e
specified
directly,
or
by
its
decimal
or
octal
ASCII
value.
Octal
values
are
preceded
by
the
letter
0.
Table 6.6.-1…86…1…02… …02… …02… …02…
Fig. 6.6-2…01…Example of TTY Device Handler and Emulator Operations…86…1 …02… …02… …02… …02…
T̲e̲l̲e̲t̲y̲p̲e̲ ̲o̲n̲ ̲I̲B̲M̲
The IBM 3767 emulator accepts a BIND SNA-request
for a type 1 session with the same restrictions
as a proper IBM 3767. This means:
o Function
Management
(FM)
rofile
must
be
3.
o Transmission
Subsystem
(TS)
profile
must
be
3.
o No
FM
headers
are
allowed.
Input data is always sent as an Only-In-Chain
Request Unit, whereas output RUs may be
chained.
If the BREAK key is depressed, an SNA SIGNAL
reques is transmitted to the host.
Figure 6.6-3 shows a sequence of typical
operations on the terminal, the corresponding
states of the device handler and the SNA
requests sent and received by the emulator.
T̲e̲l̲e̲t̲y̲p̲e̲ ̲o̲f̲ ̲U̲N̲I̲V̲A̲C̲
Sessions between Teletpes and UNIVAC hosts
are fully supported via the INT-1 protocol.
Teletype devices are defined to the host
as:
o Conversational
Devices
(Category
3)
o Buffered,
Printing
(Class
2)
o Type:
DCT1000
(Type
1)
The support given by the devie handler is
as described in section 6.7.3. In addition,
the emulator will recognize a TTY commands
and set line handler parameters accordingly.…86…1
…02… …02… …02… …02…
Fig.6.6-3…86…1 …02… …02… …02… …02…
PF6 NETWORK used
to
toggle
between
network
control
mode
and
data
mode.
PA1 is used as break key.
6.6.3.2 V̲D̲U̲ ̲S̲u̲p̲p̲o̲r̲t̲
In support of interactive host access IBM
3270 BSC, IBM3270 SNA, U100, U200, UTS 4000
running under UNISCOPE line discipline device
handlers are provided.
6.6.3.2.1 I̲B̲M̲ ̲3̲2̲7̲0̲
The IBM 3270 Information Display System
consists of a variety of cluster controllers,
display stations and printers.
ACDN upports the models which are specified
for remote attachment according to the following
classification.
IBM 3270 BSC
o 3271
control
unit,
model
2
o 3274
control
unit,
model
1c
o 3275
control
unit,
model
2
o 3276
control
unit,
model
2
o assoiated
3277
display
stations
o associated
printers
IBM 3270 SNA
o 3274
Control
Unit,
model
1C
o 3276
Control
Unit,
model
12
o associated
3278
display
stations,
o associated
printers
All devices are given an SNA appearance.
Control units ae represented by a Physical
Unit and their attached display stations
and printers appear as associated Logical
Units.
I̲B̲M̲ ̲3̲2̲7̲0̲ ̲S̲N̲A̲
Since these device follow truly, the SNA
protocols, no special support needs to be
given. Control Units attach a PU.T2, display
stations as LU.T2, and printers as LU.T1
or LU.T3, depending on whether they must
support SNA Character String (SCS) control
codes or 3270 data streams.…86…1 …02…
…02… …02… …02…
6.6.3.3 B̲a̲t̲c̲h̲ ̲D̲e̲v̲i̲c̲e̲ ̲S̲u̲p̲p̲o̲r̲t̲
Batch mode access for the purposes of description
in this chapter is defined as an access
procedure in which bulk data transfer is
initiated.
The tpe of terminals that are supported
by the batch access procedure are IBM 3780,
IBM 2780, S/3 qualifying for HASP work station
support and the UNIVAC NTR.
From the IBM application program point of
view, the IBM 2780, 3780 and HASP work stations
ar supported by ACDN through the appearance
of IBM 3790.
From the Univac application program point
of view, the NTR and IBM 2780 are supported
by ACDN for batch access through RB2 protocol.
Minicomputers with installed emulators are
supported forbatch access as long as they
provide the standard HASP work station multileaving
protocol or the Univac NTR protocol.
Application to application file transfer
between IBM Univac hosts or between two
IBM hosts is supported by the above batch
acces procedures.
6.6.3.3.1 I̲B̲M̲ ̲2̲7̲8̲0̲ ̲a̲n̲d̲ ̲3̲7̲8̲0̲ ̲B̲S̲C̲
BSC batch devices can only be supported
by SNA if they are given the appearance
of the SNA batch terminal IBM 3790. JES3
is able to support an SNA work station with
the following characteristics:
o Physical Unit PU.T2
o plus
up
to
5
LU.T1s,
each
consisting
of:
- zero
or
more
console
devices,
- up
to
15
reader
devices,
- up
to
15
printer
devices
- up
to
15
punch
devices
o each
logical
unit
may
contain
up
to
15
consoles,
readersand
printers/punches,
where
at
any
time,
only
one
can
be
active
(i.e.
selected
by
a
Function
Management
Header
type
1
(FMH1)).
o supports
for
SNA
character
string
(SCS)
NL
(new
line)
CR
(carriage
return)
FF
(form
feed)
IRS
(inter
recod
separator)
SVF
(set
vertical
form)
SEL
(select)
TRN
(transparent)…86…1
…02…
…02…
…02…
…02…
o FM
Profile
is
3
o TS
Profile
is
3
Only Point to Point is implemented, but
multipoint may be installed, if required.
Consoles for 2780, 3780 are supported in
two ways:
1) Sared
on
the
same
device
(console
input
in
reader
stream,
output
on
printer)
as
currently
supported
by
JES3
for
BSC-devices
and
2) Shared
console
on
another
different
device
(TTY,
3270
or
another
batch
station).
Each
2780/3780
must
be
assigned
t
a
shared
console.
6.6.3.3.2 I̲B̲M̲ ̲S̲/̲3̲ ̲H̲A̲S̲P̲ ̲W̲o̲r̲k̲ ̲S̲t̲a̲t̲i̲o̲n̲ ̲B̲S̲C̲
A HASP work station is supported by the
HASP multi leaving BSC protocol where the
device handler in the TAS plays the role
of a central HASP station.
6.6.3.3.4 U̲n̲i̲v̲a̲c̲ ̲N̲T̲R̲ ̲W̲o̲r̲k̲ ̲S̲t̲a̲t̲i̲
