top - download
⟦ad0a73cbf⟧ Wang Wps File
Length: 28061 (0x6d9d)
Types: Wang Wps File
Notes: CPS/SDS/001
Names: »0549A «
Derivation
└─⟦c2ca659c9⟧ Bits:30006002 8" Wang WCS floppy, CR 0037A
└─ ⟦this⟧ »0549A «
WangText
8…08…8…0b…8…0c…8…0d…8 7…09…7…0e…7…0f…7
…02…CPS/SDS/001
…02…HKI/810115…02……02…
CAMPS SYSTEM DESIGN SPECIFICATION
…02……02…CAMPS
T̲A̲B̲L̲E̲ ̲O̲F̲ ̲C̲O̲N̲T̲E̲N̲T̲S̲
5.7 IO CONTROL SOFTWARE PACKAGE ..............
5.7.1 Summary of Requirement ...............
5.7.1.1 Package Description ..............
5.7.1.1.1 Summary of Function ..........
5.7.1.1.2 Summary of External Interfaces
5.7.1.2 Package Functions ................
5.7.1.2.1 IO System ....................
5.7.1.2.2 Line Interface Control .......
5.7.1.2.3 Device and Line Control ......
5.7.1.3 Package Control ..................
5.7.1.4 Characteristics ..................
5.7.1.5 Design and Construction ..........
5.7.1.6 Documentation ....................
5.7.2 Environment ..........................
5.7.2.1 Standard Hardware, Firmware, and
Software .........................
5.7.2.2 External Interfaces ..............
5.7.2.3 Package Interfaces ...............
5.7 I̲O̲ ̲C̲O̲N̲T̲R̲O̲L̲ ̲S̲O̲F̲T̲W̲A̲R̲E̲ ̲P̲A̲C̲K̲A̲G̲E̲
5.7.1 S̲u̲m̲m̲a̲r̲y̲ ̲o̲f̲ ̲R̲e̲q̲u̲i̲r̲e̲m̲e̲n̲t̲
5.7.1.1 P̲a̲c̲k̲a̲g̲e̲ ̲D̲e̲s̲c̲r̲i̲p̲t̲i̲o̲n̲
The IO control SW package provides the interface between
CAMPS application software and terminals, lines, file
management and message management system.
The IO control functions can be divided into a number
of destinct functions:
a) I/O command transfer (IO system)
b) Line interface control
c) Device and line control
An overview of the IO control SW with the three main
groups is shown in figure 5.7.1.1-1.
The IO control software break down is shown in figure
5.7.1.1-2.
FIGURE 5.7.1.1-1
Figure 5.7.1.1-2
5.7.1.1.1 S̲u̲m̲m̲a̲r̲y̲ ̲o̲f̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲s̲
I̲O̲ ̲S̲y̲s̲t̲e̲m̲
The I/O System validates I/O requests and transforms
them into interprocess message to the Terminal Handling
System, File Management System, Message Management
System, device handlers and device drivers.
L̲i̲n̲e̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲ ̲C̲o̲n̲t̲r̲o̲l̲
The Line Interface Control covers common software for
interface to lines via LTUXs, LTUs, and the SSC driver.
It is divided into:
T̲e̲r̲m̲i̲n̲a̲l̲ ̲H̲a̲n̲d̲l̲i̲n̲g̲ ̲S̲y̲s̲t̲e̲m̲
The Terminal Handling System controls logical channels
to LTUXs via the TDX system and logical channels
to the LTUs via a standard LTU handler. The THS
supports inclusion of device/line specific handlers.
T̲D̲X̲ ̲S̲y̲s̲t̲e̲m̲
The TDX System provides communication on logical
lines from the TDX driver via the TDX Host Interface
to a number of LTUXs or other host interfaces.
The communication is controlled by the TDX controller
firmware.
S̲t̲a̲n̲d̲a̲r̲d̲ ̲L̲T̲U̲ ̲H̲a̲n̲d̲l̲e̲r̲
The standard LTU Handler provides the means for
the Terminal Handling System to interface to LTUs
on the IO BUS. One incarnation of the Standard
LTU handler serves one LTU with up to 16 communication
lines. The standard LTU Handler interfaces up to
16 device specific Handlers.
S̲S̲C̲ ̲D̲r̲i̲v̲e̲r̲
The SSC Driver provides the software interface
to the Memory MAP console interface in such a way
that communication with the SSC Computer is supported.
The SSC driver emulates a system console driver
concerning on-line standard system software.
S̲t̲a̲n̲d̲a̲r̲d̲ ̲L̲T̲U̲ ̲M̲i̲c̲r̲o̲-̲P̲r̲o̲c̲e̲s̲s̲o̲r̲ ̲S̲o̲f̲t̲w̲a̲r̲e̲
The Standard LTU micro-processor software supports
implementation of communication line protocol software
in the CR8066D LTU. It is the IO Bus interface
for data and control information input/output.
D̲e̲v̲i̲c̲e̲ ̲&̲ ̲L̲i̲n̲e̲ ̲C̲o̲n̲t̲r̲o̲l̲
The Device & Line Control consists of all line, channel
and device specific software and firmware.
It is divided into:
T̲A̲R̲E̲ ̲C̲o̲n̲t̲r̲o̲l̲
The TARE control implements the level 2 interface
of the TARE communication (i.e. the LITSYNC protocol).
S̲C̲A̲R̲S̲ ̲C̲o̲n̲t̲r̲o̲l̲
The SCARS Control implements the level 2 interface
of the SCARS communication (X25 protocol).
C̲C̲I̲S̲ ̲C̲o̲n̲t̲r̲o̲l̲
The CCIS Control implements the level 2 interface
of the CCIS communication (X.25).
T̲R̲C̲/̲T̲P̲ ̲C̲o̲n̲t̲r̲o̲l̲
The TRC/TP control implements the device interface
to TRC and Teleprinter lines. This includes conversion
to and from internal format as well as character
sequence recognition. ITA2/ITA5 Conversion.
P̲T̲P̲/̲P̲T̲R̲ ̲C̲o̲n̲t̲r̲o̲l̲
The PTP/PTR Control implements the device interface
to PTP/PTR. This includes conversion to and from
internal formats as well as character sequence
recognition. ITA/2/ITA5 Conversion.
M̲e̲d̲i̲u̲m̲ ̲S̲p̲e̲e̲d̲ ̲T̲e̲l̲e̲p̲r̲i̲n̲t̲e̲r̲ ̲C̲o̲n̲t̲r̲o̲l̲
The Medium Speed Teleprinter control implements
the device interface to the MSTP including conversion
from internal format.
O̲C̲R̲ ̲C̲o̲n̲t̲r̲o̲l̲
The OCR Control implements the device interface
to the OCR including generation of internal format.
V̲D̲U̲ ̲C̲o̲n̲t̲r̲o̲l̲
The VDU Control implements the device interface
for user terminal VDUs and Supervisory terminal
VDUs. It consists of the format handler, VDU handler,
and VDU LTUX firmware.
S̲o̲f̲t̲w̲a̲r̲e̲ ̲D̲e̲v̲e̲l̲o̲p̲m̲e̲n̲t̲ ̲V̲D̲U̲ ̲C̲o̲n̲t̲r̲o̲l̲
The Software Development VDU Control implements
the device interface for the software development
VDU.
L̲i̲n̲e̲ ̲P̲r̲i̲n̲t̲e̲r̲ ̲H̲a̲n̲d̲l̲e̲r̲
The Line Printer Handler provides the device interface
to the line printer.
5.7.1.1.2 S̲u̲m̲m̲a̲r̲y̲ ̲o̲f̲ ̲E̲x̲t̲e̲r̲n̲a̲l̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲s̲ ̲(̲F̲i̲g̲.̲ ̲5̲.̲7̲.̲1̲.̲1̲.̲2̲-̲1̲)̲
The IO control SW interfaces to the following external
lines (see figure).
1) NICS TARE
2) CCIS
3) SCARS
5) TRC
and the following devices:
4) OCR
6) TP
7) USER/SUPV VDU
8) PTP/PTR
9) MSP (Medium Speed Printer)
10) LINE PRINTER
11) SOFTWARE DEV VDU
FIGURE 5.7.1.1.2-1
5.7.1.2 P̲a̲c̲k̲a̲g̲e̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲s̲
5.7.1.2.1 I̲O̲ ̲S̲y̲s̲t̲e̲m̲
The IO System is the interface from CAMPS application,
CAMPS System Function, and CAMPS Operating System to:
- External line interfaces SW
- Terminal and device interface SW
- File management and Message Management Systems
The IO System supports validation of requests and communication
with serving processes.
Fig. 5.7.1.2.1-1 illustrates the method of interfacing.
The IO System communicates on behalf of the requesting
process via synchronization elements with a serving
process. An example of a serving process is the Terminal
Handling System (THS - See 5.7.1.2.2). The Requestor
may either separately request and then wait at a later
stage (sequence INIT - WAIT) or may await completion
(sequence with await completion).
The IO system supports wait for the first occuring
of Answer Sync-el and any other event.
The IO system supports wait with timeout.
Fig. 5.7.1.2.1-1
For the File Management and Message Management system
the following commands are transferred:
F̲o̲r̲ ̲a̲p̲p̲l̲i̲c̲a̲t̲i̲o̲n̲ ̲a̲n̲d̲ ̲S̲y̲s̲t̲e̲m̲ ̲S̲o̲f̲t̲w̲a̲r̲e̲ ̲S̲u̲b̲s̲y̲s̲t̲e̲m̲s̲:
APPEND BYTES/APPEND BYTES IN FIELD
CREATE FILE/MESSAGE
CREATE NEXT VERSION
COPY FIELD
DELETE MESSAGE
DESCENT
DISMANTLE
ENTER
GET FILE INFORMATION
GET ROOT
LOOKUP/LOOKUP MESSAGE
MODIFY BYTES/MODIFY BYTES IN FIELD
PROTECT
READ BYTES/READ BYTES IN FIELD
REMOVE
RESET/RESET FIELD
STORE MESSAGE
DUMP MESSAGE
RETRIEVE MESSAGE
SET FILE THRESHOLD
UPDATE
The commands above are supported in both modes described
in fig. 5.7.1.2.1.
F̲o̲r̲ ̲S̲y̲s̲t̲e̲m̲ ̲S̲o̲f̲t̲w̲a̲r̲e̲ ̲S̲u̲b̲s̲y̲s̲t̲e̲m̲:
DISMOUNT
FORMAT
GET VOLUME THRESHOLD
MOUNT
SET VOLUME THRESHOLD
USER ON
USER OFF
READ SECTORS
WRITE SECTORS
WRITE AND MARK
WRITE AND PROTECT
ASSIGN
DEASSIGN
The Commands above are supported in both modes described
fig. 5.7.1.2.1.
For the Terminal Handling System, the IO System transfers
the following commands:
A̲v̲a̲i̲l̲a̲b̲l̲e̲ ̲t̲o̲ ̲A̲p̲p̲l̲i̲c̲a̲t̲i̲o̲n̲ ̲a̲n̲d̲ ̲S̲y̲s̲t̲e̲m̲ ̲S̲o̲f̲t̲w̲a̲r̲e̲ ̲S̲u̲b̲s̲y̲s̲t̲e̲m̲s̲:
OPEN
CLOSE
READ BYTES
APPEND BYTES
MODIFY BYTES
The Commands above are supported in both modes described
fig. 5.7.1.2.1.
F̲o̲r̲ ̲S̲y̲s̲t̲e̲m̲ ̲S̲o̲f̲t̲w̲a̲r̲e̲ ̲S̲u̲b̲s̲y̲s̲t̲e̲m̲ ̲
ASSIGN LTU/LTUX
ASSIGN (Line & Channel)
DEASSIGN
USERON
USEROFF
The Commands above are supported in both modes described
in fig. 5.7.1.2.1.
5.7.1.2.2 L̲i̲n̲e̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲ ̲C̲o̲n̲t̲r̲o̲l̲
The Line Interface Control Software interfaces the
device control software with the CR80D computer system.
For the Processor Unit, the Terminal Handling System
performs the overall conversion from logical line names
to LTU or LTUX and line addresses.
The Standard LTU handlers perform the communication
with the LTUs located in the IO-crates and the TDX
driver performs the communication with the LTUX connected
to the TDX bus.
For the LTUs, a Z80 microprocessor operating system
and the CR80 interface software are common.
For the TDX, the Host interface firmware, the TDX controller
firmware, and the LTUX firmware interfacing to the
TDX bus are independent of actual devices.
Fig. 5.7.1.2.2-1 illustrates the Line Interface Control
Software/Firmware as distributed in a CR80D system
with LTUs on IO bus and LTUXs on the TDX bus.
Fig. 5.7.1.2.2-1
T̲e̲r̲m̲i̲n̲a̲l̲ ̲H̲a̲n̲d̲l̲i̲n̲g̲ ̲S̲y̲s̲t̲e̲m̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲s̲
The Terminal Handling System hides the physical line
characteristics for the application. The application
accesses lines by name.
The SSC package defines the relationship between names
and physical addresses, the baud rate for the extern
V24 lines, the logical linespeed, protocol/device type
and security classifications. Further, the SSC package
identifies the applications to the Terminal Handling
System.
The approach is shown in fig. 5.7.1.2.2-2.
Command exists for the SSC Package to define LTUs,
LTUXs lines and applications.
Command exists for the application to open and close
channels and to perform data transfer.
The THS supports inclusion of device specific Handlers.
FIGURE 5.7.1.2.2-2
T̲D̲X̲ ̲S̲y̲s̲t̲e̲m̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲
The TDX system performs multiplexed data transfers
(logical lines) between the two processor units and
between the processor units and up to 242 LTUXs. It
transfers up to 819200 bps. on max. 4096 logical lines.
The transmission on the TDX bus is controlled by the
TDX controller. In the processor unit the TDX Driver
is the interface to the TDX Host Interface.
Figure 5.7.1.2.2-3 illustrates the TDX system.
FIGURE 5.7.1.2.2-3
L̲T̲U̲X̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲ ̲a̲n̲d̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲
The LTUX is the standard interface between the TDX
Bus and terminals e.g. VDU, PTP, and OCR. At the TDX
side the TDX packet protocol is used for data transport.
The smallest unit, with which the unit works, is a
TDX frame. A frame contains one protocol byte, a three
bit sequence number, five bit byte counts and up to
sixteen data bytes. (Extended HDLC protocol with CRC
check). A TDX packet may contain several frames. The
frames are numbered contiguously (module 8) in order
to ensure correct transmission.
Each LTUX interfaces to four CCITT V24/V28 external
lines and is able to handle ITA no. 2 and no. 5. The
maximum transmission speed on the external lines are
4 x 2400 bps. or 1 x 9600 bps.
The TDX Controller multiplexes the data stream on the
TDX bus in a way to allow a logical line transmission
speed up to 819200 bps. (this number depends on the
firmware configuration in the LTUX).
Each LTUX is able to interface up to 16 logical lines
by multiplexing the data stream from/to the TDX bus.
T̲D̲X̲ ̲H̲o̲s̲t̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲
All traffic between a processor unit and the TDX bus
are executed by the TDX Host Interface.
The Host Interface is a high band width device that
interface directly to the CR80D main bus.
T̲D̲X̲ ̲C̲o̲n̲t̲r̲o̲l̲l̲e̲r̲
The traffic on the TDX bus is controlled by the TDX
Controller.
The Controller receives all frames transmitted from
the Host Interface and LTUXs, executes CRC check and
retransmit the frames.
The main task for the TDX Controller is to control
the transmission speeds allocated by SSC for each TDX
device.
T̲D̲X̲ ̲E̲r̲r̲o̲r̲ ̲H̲a̲n̲d̲l̲i̲n̲g̲
All errors included CRC and missing frames will result
in rejection of the complete packet immediately, without
waiting for completion of the packet. The receiving
device then requests a retransmission by replying N
A K (No Acknowledge). Also the acknowledgement sent
to the transmitting device is checked for errors.
A TDX system error and switch over is handled by the
IOC and SSC in common. The watchdog continuously checks
the TDX-Controller clock and advices SSC in case of
error.
S̲t̲a̲n̲d̲a̲r̲d̲ ̲L̲T̲U̲ ̲H̲a̲n̲d̲l̲e̲r̲s̲
The Standard LTU Handlers perform the communication
to the LTUs located on the IO BUS. One incarnation
of the Handler services one LTU.
The Handler interfaces to the terminal handling system
receiving request herefrom. Figure 5.7.1.2.2-4 illustrates
the approach.
FIGURE 5.7.9.2.2-4
S̲t̲a̲n̲d̲a̲r̲d̲ ̲L̲T̲U̲ ̲M̲i̲c̲r̲o̲ ̲P̲r̲o̲c̲e̲s̲s̲o̲r̲ ̲S̲o̲f̲t̲w̲a̲r̲e̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲s̲
The Standard LTU micro processor software provides
the environment for the protocol software.
a) it provides LTU initialization
b) it provides LTU on-line diagnostics
c) it provides a micro processor operating system
for executing protocol software
d) it provides pool management for buffers
e) it provides a standard queue interface to the CR80D
processor unit
f) it provides V24 drivers
The concept is shown in figure 5.7.1.2.2-5.
Figure 5.7.1.2.2-5
5.7.1.2.3 D̲e̲v̲i̲c̲e̲ ̲a̲n̲d̲ ̲L̲i̲n̲e̲ ̲C̲o̲n̲t̲r̲o̲l̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲s̲
The Device and Line Control Functions are the functions
supporting specific devices and line protocols.
N̲I̲C̲S̲ ̲T̲A̲R̲E̲ ̲C̲o̲n̲t̲r̲o̲l̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲
The control function implements the level 2 interface.
The EDC protocol data frames are converted to the internal
message format an vice versa.
The protocol description is given in the document:
"TARE synchronous channel protocol performance specifications",
no. 177000-600, version F, 29th June 1979, updated
with DCN G 2 of 15th February 1980.
The character code is ITA no. 5,, synchronous, full
duplex, serial data transmission with odd parity.
Baud rates are 600, 1200, 2400 bps.
NICS TARE Interface: Refer CPS/ICD/004.
Electrical Interface: CCITT V24/V28 synchronous full
duplex.
CAMPS will be treated as DCE in case of local NICS
TARE and as DTE in case of remote NICS TARE.
V24 in case of local CAMPS/NICS TARE interface:
102 Signal ground
103 Transmitted data
104 Received data
106 Ready for sending
109 Data channel received line signal detector
114 Transmitter signal element timing
115 Receiver signal element timing + 6V.
V24 in case of remote CAMPS/NICS TARE interface:
The above mentioned plus
105 Request to send
108 Data terminal ready
xxx Control of crypto TBD
S̲C̲A̲R̲S̲/̲C̲C̲I̲S̲ ̲C̲o̲n̲t̲r̲o̲l̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲
Ref: Interface Specification CAMPS/SCARS II/ACCIS
The character code is NATO 7-bit code (ITA no. 5),
inclusive of convertion to/from ITA no. 2.
The baud rates are 600, 1200, 9600 bps.
The protocols used are X25 LAP B.
SCARS/CCIS Interface
Electrical interface: Ref. CPS/ICD/005-6 TBD.
CCITT V24/V28 Synchronous full duplex.
V24:
102 Common return
103 Transmtted data
104 Received data
107 Data set ready
108 Data terminal ready
113 Transmitter timing
115 Receiver signal element timing
T̲R̲C̲,̲ ̲P̲o̲i̲n̲t̲ ̲t̲o̲ ̲P̲o̲i̲n̲t̲ ̲C̲o̲n̲n̲e̲c̲t̲i̲o̲n̲ ̲C̲o̲n̲t̲r̲o̲l̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲
The character code is ITA no. 2 for TRC and ITA no.
5 for point to point connection. The character code
is a 10 bit code, serial data, character-by character
with odd parity: Start bit, 7 data bit, parity bit,
stop bit.
Baud rates are 50 or 75 bps. for TRC and 50, 75, 110,
300, 600 bps. for point to point connection.
The control function includes convertion from ITA no.
5 to ITA no. 2 and vice versa for TRC interface.
TRC, Point to Point Connection Interface. Refer CPS/ICD/007.
Electrical interface: CCITT V24/V28 Asynchronous half
duplex.
V24:
102 Signal ground
103 Transmitted data
104 Received data
105 Request to send
106 Ready for sending
108/2 Data terminal ready
109 Data channel received line signal detector
positive 6V.
O̲C̲R̲ ̲C̲o̲n̲t̲r̲o̲l̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲
The character code used is ITA no. 5, 10 bit code,
character-by-character with odd parity. Start bit,
7 data bit, parity bit, stop bit.
The baud rates are 2400, 4800, 9600 bps.
The OCR uses the following sparator marks:
SEP-(SP)- separate works, variable
separator
EOL-(CR)(LF)- separate text lines
EOLF-(CR)(CR)(LF)- separate format lines
It shall be possible to close and open for message
traffic from the OCR by use of circuit V24-106.
In case of parity check error and format error the
message will be sent for message service.
OCR Interface
Refer CPS/ICD/008
Electrical Interface: CCITT V24/V28 asynchronous simplex.
The Optical Character Reader interfaces via a LTUX.
V24:
102 Signal ground
103 Transmitted data
105 Request to send
108/2 Data terminal ready
T̲e̲l̲e̲p̲r̲i̲n̲t̲e̲r̲ ̲C̲o̲n̲t̲r̲o̲l̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲
The character code is ITA no 2/5.
The teleprinter configuration includes a paper tape
reader/puncher. The SSC decides the Teleprinter function.
Each teleprinter channel is opened and closed by the
SSC software.
TTY baud rates are 50, 75, 110, 300, 600 bps.
Electrical interface:
CCITT V24/V28 Asynchronous simplex.
P̲T̲P̲/̲P̲T̲R̲ ̲C̲o̲n̲t̲r̲o̲l̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲
Paper Tape Puncher
The PTP control converts the message record format
to a ITA no. 2/5 character code used by the PTP. The
baud rate is max. 1200 bps.
Paper Tape Reader
The PTR control converts the ITA no. 2/5 character
code, used by the PTR, to message record format. The
baud rate is max. 1200 bps.
Electrical Interface:
CCITT V24/V28 is used. Transmision mode is asynchronous.
M̲e̲d̲i̲u̲m̲ ̲S̲p̲e̲e̲d̲ ̲T̲e̲l̲e̲p̲r̲i̲n̲t̲e̲r̲ ̲C̲o̲n̲t̲r̲o̲l̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲
The medium speed teleprinter is a ROP device with paper
and control and physical security key.
The character code is ITA no. 5.
Electrical Interface
CCITT V24/V28 or OPTO link is used. The transmission
mode is asynchronous.
The Medium Speed Teleprinter interfaces via a LTUX.
V̲D̲U̲ ̲C̲o̲n̲t̲r̲o̲l̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲
The communication method and electrical interface are
TBD. Baud rates are 1200 and 2400 bps.
Application Software Interface to VDU.
The application S/W interfaces to the VDU on split
basis.
The VDU screen is divided into two splits:
VDU header area - split #0
VDU format area - split #1
VDU Format Area
The format area consists of a number of lines. If the
number of links is greater than the displayed format
area (22 lines) the user may page or scroll to see
the rest.
The maximum size of the split is 44 lines.
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
VDU SPLIT
----------------------------
PRESENT DISPLAYED VDU
FORMAT AREA SCREEN
----------------------------
SCROLL
DOWN
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
SPLIT CONCEPT
A split consists of protected and unprotected fields
in any order. When the VDU is in format mode the user
is able to write and update within the unprotected
fields. On transmit request, only the contents of the
unprotected fields is sent to the application. The
application is able to select which fields to be transmitted
from the VDU.
Addressing
The fields in both splits are addressed by line type
numbers, incarnation numbers and field numbers. A group
of repeatable lines have the same line type number,
but different incarnation number.
Line type, Incarnation Field No.
1,1 1 2 3
1,2 1 2 3
2,1 1 2 3 4
3,1 1 2 3
3,2 1 2 3
VDU SCREEN
LINE AND FIELD ADDRESSING
F̲o̲r̲m̲a̲t̲ ̲H̲a̲n̲d̲l̲e̲r̲
The Format Handler uses the format definitions to build
up empty or filled out standard formats on the VDU
screen.
The format definition resides in a format file. They
are fixed at system generation and contain information
about the different standard formats used by CAMPS.
The format definitions are maintained by the Offline
Package at the CSSI site.
The Format Handler keeps track on the different types
of lines in the present format and the number of lines.
A̲p̲p̲l̲i̲c̲a̲t̲i̲o̲n̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲s̲
The application functions listed below are given names
relative to their function, however, these names may
be redefined.
D̲e̲f̲i̲n̲e̲ ̲F̲o̲r̲m̲a̲t̲ ̲A̲r̲e̲a̲
This command defines the system format area to be used
in the VDU communication. An application may communicate
with more than one VDU and thus need a larger format
area than an application communicating with one VDU.
D̲e̲f̲i̲n̲e̲ ̲F̲o̲r̲m̲a̲t̲ ̲F̲i̲l̲e̲
This command defines to the system which format file
shall be used. Formats are obtained from this file
by the Get Format command.
G̲e̲t̲ ̲F̲o̲r̲m̲a̲t̲
This command prepares the specified format for modification
by insert lines and delete lines below as well as output
by Output Format.
O̲u̲t̲p̲u̲t̲ ̲F̲o̲r̲m̲a̲t̲
This command outputs the format obtained by Get Format
and modified as of insert and delete line. The page
now contains the text in the format with all fields
blank.
F̲i̲e̲l̲d̲s̲ ̲O̲u̲t̲p̲u̲t̲
Fields are assumed organized as a consecutive sequence
of records in a buffer. In parallel a list of field
identifiers (logical line, incarnation, field number)
shall be specified. The Field Output function moves
the first record to the first field in the list, the
second to the second, etc.
F̲i̲e̲l̲d̲s̲ ̲I̲n̲p̲u̲t̲
The Fields Input function inputs the requested number
of fields from and including the field specified as
the first. The field content is returned as records
in the way that trailing blanks within the records
are omitted. If the buffer specified is not sufficient
by long the input is terminated when the buffer is
full.
Note that fields are not input upon depression of TRANSMIT,
or ENTER, or RETURN, but that these keys are returned
to the application, which will reserve a buffer and
request the transmission. The input only of fields,
which are modified is TBD.
R̲e̲c̲e̲i̲v̲e̲ ̲C̲o̲n̲t̲r̲o̲l̲
Function keys destined for the application (TBD) are
received when the Receive Control function is requested
(pending read).
S̲e̲n̲d̲ ̲C̲o̲n̲t̲r̲o̲l̲
Control characters are transmitted to the VDU by this
function. An example is Bell.
C̲h̲a̲n̲g̲e̲ ̲F̲i̲e̲l̲d̲ ̲A̲t̲t̲r̲i̲b̲u̲t̲e̲s̲
If a field has been defined with changeable attributes,
they may be modified by this command. The attributes
are modified from the previous value to the specified
e.g. intensity change, flash.
I̲n̲s̲e̲r̲t̲ ̲L̲i̲n̲e̲s̲
This command inserts the specified number of lines
as incarnation of the specified line type. Calling
the specified incarnation N, the lines will be inserted
as incarnation N, N+1.... Insert Lines is allowed up
to the size of a split.
D̲e̲l̲e̲t̲e̲ ̲L̲i̲n̲e̲s̲
This command deletes the specified number of lines
from the incarnations of lines for the specified line
type calling the specified incarnation N incarnations
N, N+1.... will be deleted.
Insert Lines and Delete Lines have effect to redefine
the format obtained by Get Format and will have no
immediate effect on the VDU as long as Output Format
has not been executed. After Output Format the Insert
Lines imply an immediate shift-down of the lines on
the VDU and the Delete Lines an immediate shift-up
of lines on the VDU.
M̲e̲s̲s̲a̲g̲e̲ ̲R̲e̲c̲o̲r̲d̲ ̲F̲o̲r̲m̲a̲t̲
All incoming information is converted from the various
types of formats, used by the external equipment, to
a standard message record format. This record format
is again converted to the proper formats when information
is transmitted to the external equipment.
The maximum line length is 69/80 characters, therefore,
the record length is limited to max. 69/80 characters.
The ITA no. 5 code is used. The records are separated
by a record separator.
After the record separator is a character count byte.
This character is used for search in lines.
The byte before the text string is kept open for purposes
not yet defined.
FIGURE 5.7.1.2.3-1
S̲o̲f̲t̲w̲a̲r̲e̲ ̲D̲e̲v̲e̲l̲o̲p̲m̲e̲n̲t̲ ̲V̲D̲U̲ ̲C̲o̲n̲t̲r̲o̲l̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲
TBD
L̲i̲n̲e̲ ̲P̲r̲i̲n̲t̲e̲r̲ ̲H̲a̲n̲d̲l̲e̲r̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲
TBD
P̲h̲y̲s̲i̲c̲a̲l̲ ̲S̲e̲c̲u̲r̲i̲t̲y̲ ̲K̲e̲y̲
On each VDU and medium speed teleprinter there is a
physical locking key. A terminal is activated by turning
the locking key to "ON". This indicates whether the
terminal is manned or unmanned.
S̲S̲C̲ ̲D̲r̲i̲v̲e̲r̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲s̲
The SSC Driver supports Processor unit interface to
the SSC compatible with TP.
Line Speed 9600 baud
Printed line with 69 characters
No Echo of input characters
V24 lines are TBD.
5.7.1.3 P̲a̲c̲k̲a̲g̲e̲ ̲C̲o̲n̲t̲r̲o̲l̲
I̲n̲i̲t̲i̲a̲l̲i̲z̲a̲t̲i̲o̲n̲
The IO Control SW is initialized by the SSC Package
in two steps. The PU resident software is loaded with
the system software at time of Bootload.
The Protocol microprocessor software in the LTUs is
loaded when the lines served are defined.
E̲r̲r̲o̲r̲ ̲H̲a̲n̲d̲l̲i̲n̲g̲
Errors not handled by the application are returned
to the SSC SW.
For further information please refer to sec. 4.11.
5.7.1.4 C̲h̲a̲r̲a̲c̲t̲e̲r̲i̲s̲t̲i̲c̲s̲
TBD.
5.7.1.5 D̲e̲s̲i̲g̲n̲ ̲a̲n̲d̲ ̲C̲o̲n̲s̲t̲r̲u̲c̲t̲i̲o̲n̲
Refer to section 2.5.
5.7.1.6 D̲o̲c̲u̲m̲e̲n̲t̲a̲t̲i̲o̲n̲
Refer to section 2.6.
5.7.2 E̲n̲v̲i̲r̲o̲n̲m̲e̲n̲t̲
5.7.2.1 S̲t̲a̲n̲d̲a̲r̲d̲ ̲H̲a̲r̲d̲w̲a̲r̲e̲,̲ ̲F̲i̲r̲m̲w̲a̲r̲e̲,̲ ̲a̲n̲d̲ ̲S̲o̲f̲t̲w̲a̲r̲e̲
N.A.
5.7.2.2 E̲x̲t̲e̲r̲n̲a̲l̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲s̲
The external interface is an integrated part of IOC
functions, refer to section 5.7.1.2.3.
5.7.2.3 S̲u̲b̲s̲y̲s̲t̲e̲m̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲s̲
a) CR80D Subsystem
The IO control SW executes partly in the processor
units (refer fig. 5.7.1.2.2-1)
b) Kernel Subsystem. The IO Control SW uses the following
Kernel Functions:
Process communication, scheduling, security.
Data transfer by low level Handlers.
c) Storage & File Management
The IO Control SW transfers commands to the Storage
& File Management.
d) SSC SW
The SSC SW controls the IO control SW.
e) Other applications and system software packages
These packages interface to the IO Control SW as
described in the package.
