top - download
⟦76f16a79e⟧ Wang Wps File
Length: 19432 (0x4be8)
Types: Wang Wps File
Notes: Rovsing
Names: »1265V «
Derivation
└─⟦740f46985⟧ Bits:30006253 8" Wang WCS floppy, CR 0097K
└─ ⟦this⟧ »1265V «
WangText
…00……00……00……00……00……0a……02……00……00……0a…
…09……0b……09……0e……07……86…1 …02… …02… …02… …02…
CHAPTER 6
Page #
DOCUMENT III TECHNICAL PROPOSAL Apr. 29, 1982
S̲A̲I̲
U̲n̲i̲v̲a̲c̲ ̲C̲h̲a̲n̲n̲e̲l̲ ̲H̲a̲n̲d̲l̲e̲r̲
The channel to the UNIVAC ll00/xx host is based upon
the CR8037D UNIVAC I/F as described in CSD/005/PSP//052
and CR8079D
UNIVAC I/F Adaptor (UIA) as described in CSD/005/PSP/0053.
The hardware meets the specifications of SP-2025 UNIVAC
lll0 Procesor I/O interface.
The Univac Channel Driver can be seen located between
the Univac Link Manager (ULM) and the Univac I/F connected
to the channel. The driver implements the SAI protocol
to insure the data transmission.
The driver permits to send and to receive data blocks
through the channel, and also to manage the Read-Write
operations coming from the ULM.
The ULM informs the driver by means of system messages
from the I/O system. The Univac I/F sends interrupts
indicating an I/O operator done on the channel.
To control the data transmission and to present the
loss of data, several queues are implemented. One serves
the Receive and Read side of the driver. The Sub Port
Data Units (SPDU's) coming from the channel enter a
list until they all form a single Port Data Unit (PDU).
Then, this PDU becomes ready to be read (read command)
by the ULM.
On the other side, the driver controls the Send and
Write operation. PDU's are received from the ULM. They
are separated into SPDU's and placed in a queue ready
to enter a special queue called "window". The window
controls the number of messages sent, but not yet acknowledged.
This process prevents a loss of data.
When a read command or a write command can not be satisfied,
by lack of PDU or lack of buffer space, the event is
saved and restored later when it can be performed.
Data and messages can always be received from the channel.
When a Receive operation is done, the data is read,
analyzed and the receive process is reactivated. Data
can then be received.
U̲n̲i̲v̲a̲c̲ ̲T̲r̲u̲n̲k̲ ̲H̲a̲n̲d̲l̲e̲r̲
The trunk connection from a CR80 to DCP/40 (running
Telcon) is based upon the CR80-LTU (Line Terminating
Unit). The level 2 (ISO-OSI-model) connection of a
trunk uses the X.25 LAPB (Link Access Procedure Balanced)
which is a subset of the UDLC (Universal Data Link
Control) procedure of UNIVAC. A further description
of the implementation of the X.25 LAPB is found in
"X.25 LAPB (level l and 2), Product Specification,
CSS-MIC/00l4/PSP/l003".
The LTU-driver for the X.25 LAPB-LTU will have to be
specified if and when the ACNC HAS is supposed to support
trunk-connections to a DCP/40 - Telcon - network.
T̲e̲r̲m̲i̲n̲a̲t̲i̲o̲n̲ ̲S̲y̲s̲t̲e̲m̲
The implementation of the TS' in the ACNC is done in
the HAS. The protocol logically is parted in two sub-layers
called Line Port Nultiplexor (LPM) and Port Flow Control
(PFC).
The functions of the LPM are implemented in the driver
of the SAI. The functions of the PFC are implemented
in the End User Process (EUP) in the HAS.
The protocol part of the TS' called LPM is also referred
to as the TS/TN-protocol. The implementation of this
protocol covers the full TS/TN-protocol as described
in ealier chapters with one exception: The packet type
called "switch reset" is not implemented.
The PFC-protocol implements the HIC's listed in the
following table:
HIC HIC Variant Parameter Hex
name value value
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲
Receive Ready 00ll 000l 3l
Receive Not Ready 00ll 00l0 32
Resync Numbers 00ll 00ll 33
End of Header 0l00 4
Space (pad) 0l0l 5
Retransmit 0lll 7
Send # l00l 00l0 ssss ssss(PDU#) 92ss
Send # l00l 0l00 ssss ssssFLaa aaaa 94aa#A
Receive Number l0l0 00l0 00aa aaaa(ACKSET#) A2AA
Set class l ll00 0000 00l0 0000 000l CO20l
Set class 2 ll00 0000 00l0 0000 00l0 CO202
Set Class 6 ll00 0000 00l0 0000 0ll0 CO206
Solicit status ll0l 0000 0000 D00
ssss ssss is an 8-bit send PDU#.
FL are first/last PDU of ACKSET flags.
aa aaaa is 6-bit ACKSET #.
The receive number is the number of the latest ACKSET correctly
received.
The PFC interfaces the protocol called Transport Station
User (TSU) which is a layer that converts (maps) the
addressing scheme of the logical subchannels of the
UNIVAC Telcon network into the addressing scheme provided
by the transport system in the ACDN.
D̲a̲t̲a̲ ̲U̲n̲i̲t̲ ̲C̲o̲n̲t̲r̲o̲l̲ ̲(̲D̲U̲C̲)̲
R̲e̲m̲o̲t̲e̲ ̲T̲r̲u̲n̲k̲ ̲C̲o̲n̲t̲r̲o̲l̲ ̲(̲R̲T̲C̲)̲
T̲r̲u̲n̲k̲ ̲C̲o̲n̲t̲r̲o̲l̲ ̲(̲T̲C̲)̲
The protocol layors DUC, RTC and TC are not yet implemented
in the ACDN. To interface a network based upon the
DCP/40 hardware and the Telcon software these protocol
layers will have to exist.
C̲o̲m̲m̲u̲n̲i̲c̲a̲t̲i̲o̲n̲ ̲S̲y̲s̲t̲e̲m̲ ̲U̲s̲e̲r̲ ̲(̲C̲S̲U̲)̲
The CSU protocol level is implemented in the Terminal
Access Subsystem (TAS). It supports the functions necessary
to establish dynamic system sessions (class 3) upon
logical subchannels predefined in the host (see the
following chapter). The CSU supports the DMF protocol
to an extent that is defined in the TSU/CSU product
specification.
E̲m̲u̲l̲a̲t̲o̲r̲s̲
R̲B̲2̲/̲N̲T̲R̲
The emulator RB2/NTR supports the mapping between the
RB2 protocol and the Nine Thousand Remote (NTR) protocol.
The functionality of the NTR-station supported in the
ACNC, is full support. This is reflected from the users
point of view by the following list of NTR-console-commands
available.
N̲T̲R̲ ̲C̲o̲n̲s̲o̲l̲e̲ ̲C̲o̲m̲m̲a̲n̲d̲s̲ ̲f̲o̲r̲ ̲C̲o̲m̲m̲u̲n̲i̲c̲a̲t̲i̲o̲n̲ ̲w̲i̲t̲h̲ ̲A̲C̲D̲N̲
The following console commands are supported by the
Network (The Local Commands are not included in this
specification, it is up to the NTR-station).
INITIATE-DEVICE
The NTR-stations sends an Initialize-device to the
Host.
SIGN-ON msg.
It is the first message to the Host.
TERMINATE FILE
Terminate file for a device.
TERMINATE-SITE
Request Host to terminate site.
DISPLAY-BYTE
Send a byte to the Nost.
REQUEST REPRINT/REPUNCH
Transmit a request to the Host for reprint/repunch
of a number of pages/cards for a device.
SKIP PAGES
Transmit a request to the Host to skip a number of
pages (in multipla of l0).
SET lines pr inch
Direct printer to print with 8 or 6 lines pr inch (!).
RESUME OUTPUT on Device.
START LINE TEST. (system dependent). A max. 63 bytes
long buffer received from the network is returned to
the network.
LOCK AND TERM.
Transmits an EOF to the Host, and lock out the device.
REQUEUE
Let the Host requeue the file being processed at the
device.
LOCK AND REQUEUE
Let the host requeue the file being processed and lock
the device.
UNLOCK
Let the Host initiate the previously locked device.
REQUEUE AND TERM.
The Host will requeue the outputfiles and terminate
the site.
COMP-ACT/TERM
The Host will complete the current activities and terminate
the site.
COMP-QUEUE/TERM
The Host will process all files queued and terminate
the site.
LOCKOUT
The Host will lockout the device, and after the current
file is finished, no file will be sent to the device.
RESUME
The Host will resume previously suspended device.
SUSPEND
The Host will immediately suspend operation on a device.
TERMINATE FILE
The Host will terminate the file being output to a
device. (Display Queue) and Display File.
R̲B̲2̲/̲3̲7̲8̲0̲
The emulator RB2/3780 supports the mapping between
the RB2 protocol and the IBM3780 station. The functionality
supported in the LMENET covers access from a UNIVAC
ll00/xx-host to a printer, a card reader and a console.
In the host the station is supported as an NTR-station.
2̲7̲8̲0̲/̲3̲7̲8̲0̲ ̲t̲o̲ ̲R̲B̲2̲ ̲E̲m̲u̲l̲a̲t̲i̲o̲n̲
The IBM 2780/3780 devices are presented to the UNIVAC
host as stations similar to NTR stations via the RB2
protocol (with translation ASCII/EBCDIC).
To enable the 2780/3780 console operator to issue NTR-equivalent
commands, input card images are scanned for cards beginning
with $$.
The following NTR equivalent commands are defined:
$$ TERM PRINTER terminate current printer file
$$ LOCK PRINTER AND REQUEUE
lock out printer, requeue current file
$$ LOCK PRINTER AND TERMINATE
lock out printer, terminate current file
$$ LOCK PRINTER complete current file and lock
printer
$$ UNLOCK PRINTER printer is unlocked
$$ RESUME PRINTER resume printer output, (ex.
after forms change).
$$ REQUEUE requeue current output file
$$ REPRINT nn reprint nn pages
$$ DISPLAY QUEUE display number of files queued
$$ DISPLAY FILES display files queued for printer.
I̲N̲T̲1̲/̲T̲T̲Y̲
I̲N̲T̲1̲/̲3̲2̲7̲0̲
The emulator for mapping TTY-type devices and 3270
type devices into INTl presents these terminals as.
o Conversational devices (category 3)
o Buffered, printing (class 2)
o Type: DCTl000 (Type l)
To support the emulation of 3270 into INTl, a special
3270 screen handling is implemented.
The basics of the screen handling is:
o Maintain formatted screen
o Display format: PAGE or WRAP AROUND
o Optional "FREEZE" area
o Conversion to ASCII.
Figures 6.7.3.8 to 6.7.3.11 show examples off the screen
handling features.
figure
*
104
figure
F̲u̲n̲c̲t̲i̲o̲n̲ ̲K̲e̲y̲s̲ ̲u̲s̲e̲d̲ ̲t̲o̲ ̲C̲o̲n̲t̲r̲o̲l̲ ̲D̲i̲s̲p̲l̲a̲y̲ ̲F̲o̲r̲m̲a̲t̲
PF l FREEZE screen above cursor (area below
must be at least 2 lines)
PF 2 PAGE/WRAP: Toggle between page mode and
wrap around mode.
PF 3 CLEAN: Clear and reformat non frozen part
of screen.
PF 4 HELP: Display information about function
key assignment.
PA 1 is used as BREAK Key
H̲o̲s̲t̲ ̲C̲o̲n̲f̲i̲g̲u̲r̲a̲t̲i̲o̲n̲
The following is a model of a configuration file for
a CMS-ll00 system that shall interface the ACDN.
CMSll00 Configuration file containing Symbolic Configuration
Statements (SCS's) defining a CMS to Telcon network
with one TTY terminal running TIP, one TTY terminal
running DEMAND and one NTR station running remote batch.
. .... The ENVIRONMENT statement specifies the logical
processes of CMSll00 to be initialized.
ENVIRONMENT DCP,DEMAND,BATCH,TIP . Default supplied
. .... The INFO statement contains values for system
use.
INFO BMMIN,20000 ;
BMMAX,l00000 ;. All default
$$CHARS,$$ ; supplied
RT-LEVEL,2 ;
BMTHRESHOLDS,5,l0,l5,20,25;
CONSOLECLASS,2
. .... The CONSOLE statement contains information on
the console message file
CONSOLE CMSll00 CMSFILE.CNSLMSGS . Check !
. .... The LOG and TRACE SCS's define the LOG and TRACE
mediums
LOG ASG,CMSll00 LOG(+l) .
TRACE ASG,CMSll00 LOG(+l) .
. .... The TIP statement defines TIPCSU to TIP interface
TIP OWNER,DCP ;
CMS-NUMBER,l ; . CMS7R2 has no 0
CONNECTS,IFC ; . COMPOOL interface
UPA-SIZE,# ;
MAX-QUEUE-ENTRIES,l0 ; . Rest default
CORE-BUFFERS,20 ; supplied
CORE-BLOCK-SIZE,56 ; . See TIP config.
DRUM-BLOCK-SIZE,56 ; . See TIP config.
MAX-CONCURRENCY,3 ;
CHECKSUM,OFF ;
UDM-TRACE,SYSPRT ; .
. .... The FEP statement defines the FRONT END PROCESSOR
FEP,FEPl OWNER,DCP ;
PATHS,CRIPl ;
LOAD,CMSll00 LOAD ;
DUMP,CMSll00 DUMP ; . Optional
HOST-WINDOW,7 ; . Default
TYPE,DCP ;
STATE,UP ; .
. .... The PATCH scs defines the paths from the ll00
to the DCP.
PATH,CRIPl OWNER,FEPl ;
INPUT-NODE,DCP0l ; . See OS config.
OUTPUT-NODE,DCP02 ; . See OS config.
STATUS,UP ; .
. .... The EU statements are used to identify the CSU
which serves the logical end user.
EU,NTRCONSOLE OWNER,RSBCSU ;
TYPE,RB-CONSOLE .
EU,NTRREADER OWNER,RSBCSU ;
TYPE,RB-READER .
EU,NTRPUNCH OWNER,RSBCSU ;
TYPE,RB-PUNCH .
EU,NTRPRINTER OWNER,RSBCSU ;
TYPE,RB-PRINTER .
. .... The GROUP statement is used to group the NTR
end users.
GROUP,NTRGROUP OWNER,RSBCSU ;
TYPE,EU ;
MEMBERS,NTRCONSOLE,NTRREADER,NTRPUNCH,- NTRPRINTER
. .... The PORT statement defines the logical connec-
tion between two CSU's.
PORT,BEGIN WINDOW,4,4 ;
SAI-PROCESS,FEPl ;
CLASS,RECOVERY,BASIC ; . PFC Classes
ACKSET-SIZE,l ;
MAX-STATUS-WATT,30 ; . Default supplied
MAX-STATUS-RETRYS,2 ; . Default supplied
OP-PROTOCOL,INT-l ; . Interactive
SSC-CLASS,DYNANIC ; protocol
MAX-UDU-SIZE,2*96 ;
MAX-SYS-SESSIONS,20
PORT,ACTIP LPN,l ; . The TIP port CSU-PROCESS,TIPCSU
logical port nbr matches lsch in
Telcon SESSN stmt.
PORT,ACDEMAND
LPN,2 ; . The DEMAND port
CSU-PROCESS,RSDSCU .
PORT,ACBATCH
LPN,3 ; . The BATCH port
CSU-PROCESS,RSBCSU ;
DP-PROTOCOL,RB-2 .
PORT END .
. .... The PID statement relates TIP position identifiers
and End Users
PID,200l OWNER,TICSU ;
EU-NAME,ACTIPO1 . ACTIPO1 matches name in
Telcon TERM statement
O̲p̲e̲r̲a̲t̲i̲o̲n̲ ̲o̲f̲ ̲t̲h̲e̲ ̲D̲C̲A̲ ̲N̲e̲t̲w̲o̲r̲k̲
C̲o̲n̲f̲i̲g̲u̲r̲a̲t̲i̲o̲n̲ ̲o̲f̲ ̲t̲h̲e̲ ̲A̲C̲D̲N̲
In the ACDN, the following entities must be known to
enable the CR80 to emulate a DCP/40 FEP (Front End
Processor):
a: The logical names of the entities in the Host-
configured network:
1: The FEP name
2: The PATH name
3: The NTR EU name
4: The NTR GROUP name
5: The PORT names (3)
6: The TIP EU name
b: The logical port numbers used by the ports (3)
c: In general all fields in the SCS's that are different
from the documented default values.
S̲i̲g̲n̲-̲o̲n̲
N̲T̲R̲ ̲8̲2̲7̲8̲0̲
The sign-on of NTR-stations is covered in the following
way:
1) The NTR-station sends the Sign-on buffer to the
device-handler/line handler.
2) The device-handler/line-handler sends it to the
Emulator task in the End User Process (if the emulator
is not existing yet, it will be created by network
control functions before the sign-on is sent).
3) The emulator embeds the sign-on text item in the
UDU-text (6) field and sends it to the TSU/CSU-task.
4) The TSU/CSU-tasR initializes the system sessions
to the UNIVAC-host and submits the sign-on on the
System session that is corresponding to the console
device number (i.e. zero).
5) The UNIVAC ll00/xx-host will answer with an initialize
site command in the UDU-TEXT(3) item.
T̲T̲Y̲ ̲a̲n̲d̲ ̲3̲2̲7̲0̲
The sign-on of a TTY-device is done in the following
sequence:
1) The user issues a connects to the line-handler
device-handler.
2) The line-handler/device-handler sends it to the
User-/Session-Service (US/SS) in the NCC to be
evaluated.
3) The SS signals back to the Node Session Manager
(NSM) with information regarding the HOST and the
type of connection wanted.
4) NSM and the Host Session Manager (MSM) exchange
knowledge to set up a logical sub-channel in the
network if necessary (includes the CSU/TSU-task
in the TIP).
5) NSM creates and connects an emulator to a CSU/TSU.
6) The CSU/TSU sets up the system session to the UNIVAC
Host issuing a sequence of SSC-commands
7) The Emulator issues the DDP-O device control commands
to inform the host of the type of terminal using
the system session, and sends the sign-on message
(based upon the log-on message) to the Host.
8) The security system of the host will answer back
to the emulator (or the terminal user) prompting
him to issue his user-id/password (the normal session
with the application is started).
N̲C̲C̲ ̲o̲n̲ ̲N̲M̲S̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲s̲
The operation of the ACDN part of the network will
be maintained via the consoles of the network.
Any interactive terminal connected to the ACDN may
act as a remote console in the UNIVAC ll00/xx-hosts
running CMS/1100, thus enabling the operator commands,
allowed for a specific USERID, to be issued.
To support the NMS-functions in the ACDN, that from
the hosts point of view looks like a Telcon-network
of DCP/40's, an NMS-logical subchannel and systems
session is implemented. The termination point of the
NMS-session is the HAS, where a number of tables are
kept and updated to fulfil the needs of status-information
from any terminal or host with valid access-rights.
F̲u̲t̲u̲r̲e̲ ̲E̲x̲t̲e̲n̲s̲i̲o̲n̲ ̲P̲o̲s̲s̲i̲b̲i̲l̲i̲t̲i̲e̲s̲
The future extension possibilities of the interface
between the ACNC and the UNIVAC ll00/xx- host may be
grouped in three main categories.
o extension of existing functions already provided,
o extensions based upon new releases from UNIVAC
that support new enhanced functions,
o extensions based upon implementation of new services
in the ACNC.
E̲x̲t̲e̲n̲s̲i̲o̲n̲ ̲o̲f̲ ̲E̲x̲i̲s̲t̲i̲n̲g̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲
In this group the UNIVAC interface could be extended
at the PFC-level to support the class 6 protocol. On
the NMS-side the functionality of the ACNC could be
to support a mapping of all possible NCC-information
on their equivalent NMS- tables residing in the HAS's
or the NCC.
E̲x̲t̲e̲n̲s̲i̲o̲n̲s̲ ̲b̲a̲s̲e̲d̲ ̲u̲p̲o̲n̲ ̲N̲e̲w̲ ̲r̲e̲l̲e̲a̲s̲e̲ ̲f̲r̲o̲m̲ ̲U̲n̲i̲v̲a̲c̲
In this group, the items like the new interactive protocol
INT-2 and change on the fly of the Host- CMS-configuration,
will be found.
E̲x̲t̲e̲n̲s̲i̲o̲n̲s̲ ̲b̲a̲s̲e̲d̲ ̲u̲p̲o̲n̲ ̲I̲m̲p̲l̲e̲m̲e̲n̲t̲a̲t̲i̲o̲n̲
To this category belongs the implementation of support
for the DCA-terminal, the support of a DCP/40-based
network, and the implementation of UTS4020 cluster
controller support in the ACNC.
