top - download
⟦c57cf8249⟧ Wang Wps File
Length: 12431 (0x308f)
Types: Wang Wps File
Notes: CMS/SDS/003
Names: »4557A «
Derivation
└─⟦2e54efd14⟧ Bits:30006189 8" Wang WCS floppy, CR 0430A
└─ ⟦this⟧ »4557A «
WangText
…0d… …86…1
…02…
…02…
…02…
…02…CMS/SDS/003
…02…840201…02……02…#
TDS SYSTEM
DESIGN
…02……02…CAMPS
T̲A̲B̲L̲E̲ ̲O̲F̲ ̲C̲O̲N̲T̲E̲N̲T̲S̲
1 GENERAL ........................................
4
1.1 PURPOSE ....................................
4
1.2 PROJECT REFERENCES .........................
4
1.2.1 Applicable Documents: .................
4
1.2 2 REFERENCE DOCUMENTS ...................
4
1.3 TERMS AND ABBREVIATIONS ....................
5
1.3.1 All Defined in CPS/210/SYS/001 .........
5
1.3.2 All defined in CPS/210/SYS/001 .........
5
2 SUMMARY REQUIREMENTS .........................
6
2.1 SYSTEM DESCRIPTION .........................
6
2.2 SYSTEM FUNCTION ............................
6
2.2.1 Test Drive Package (TDP) ...............
6
2.2.2 Message Traffic on External Channels ...
6
2.2.1.1 Main Functions .....................
6
2.2.1.2 Functional responsibilities ........
7
2.2.1.2.1 Initialisation and Termination .
7
2.2.1.2.2 Checkpointing and Recovery .....
7
2.2.1.2.3 Errordetecting and Recovery ....
7
2.2.1.2.4 Datacollection .................
7
2.2.1.2.5 Security .......................
7
2.2.2.1 Main Functions .....................
7
2.2.2.1.2 Functionally Responsibilities ...
8
2.3 CHARACTERISTICS ............................
8
2.3.1 Timing .................................
8
2.3.2 Throughput ............................
9
3 ENVIRONMENT ..................................
10
3.1 EQUIPMENT ..................................
10
3.2 SOFTWARE ...................................
12
3.2.1 System Software .......................
12
3.2.2 Development Software ...................
12
3.3 INTERFACES .................................
14
3.3.1 External Interfaces ....................
14
3.4 FUNCTIONS MAINTAINED BY OTHER PACKAGES .....
17
4 SYSTEM DESIGN ..................................
18
4.1 SYSTEM OVERWIEW ...........................
18
4.1.1 Test Drive Package .....................
18
4.1.2 External Traffic Generation and
Reception ..............................
21
1̲ ̲ ̲G̲E̲N̲E̲R̲A̲L̲
1.1 P̲U̲R̲P̲O̲S̲E̲
The puppose of this "TDS System Design" document is
to give a high level overview of the TDS System.
It should be possible within this document to find
information necessary to
- understand the interface between TDS and CAMPS
- identify major parts (packages) in TDS
- understand major limits in the overall system.
1.2 P̲R̲O̲J̲E̲C̲T̲ ̲R̲E̲F̲E̲R̲E̲N̲C̲E̲S̲
1.2.1 A̲p̲p̲l̲i̲c̲a̲b̲l̲e̲ ̲D̲o̲c̲u̲m̲e̲n̲t̲s̲:
CAMPS system requirements - CPS/210/SYS/001
CAMPS design documents, especially
User procedures and associated formats CPS/230/ICD/0001
CAMPS Input Output Control - CPS/SCD/028
Delta Reference Manual
CAMPS Test Drive System outline - CPS/TCN/016
TDS system design + note (LN/FAH)
1.2.2 R̲E̲F̲E̲R̲E̲N̲C̲E̲ ̲D̲O̲C̲U̲M̲E̲N̲T̲S̲
CR80 Handbook,
Damos PSP's (IOS/TMS/TOS/RTC/PCF),
CR80 LTU I/F CSS-MIC/040/FNC/0001.
1.3 T̲E̲R̲M̲S̲ ̲A̲N̲D̲ ̲A̲B̲B̲R̲E̲V̲I̲A̲T̲I̲O̲N̲S̲
1.3.1 A̲l̲l̲ ̲D̲e̲f̲i̲n̲e̲d̲ ̲i̲n̲ ̲C̲P̲S̲/̲2̲1̲0̲/̲S̲Y̲S̲/̲0̲0̲1̲
1.3.2 A̲l̲l̲ ̲d̲e̲f̲i̲n̲e̲d̲ ̲i̲n̲ ̲C̲P̲S̲/̲2̲1̲0̲/̲S̲Y̲S̲/̲0̲0̲1̲
2̲ ̲ ̲S̲U̲M̲M̲A̲R̲Y̲ ̲R̲E̲Q̲U̲I̲R̲E̲M̲E̲N̲T̲S̲
2.1 S̲Y̲S̲T̲E̲M̲ ̲D̲E̲S̲C̲R̲I̲P̲T̲I̲O̲N̲
The Test Drive System (TDS) generates/accepts traffic
on external as well as local lines. On external lines
messages are sent and received via CCIS/SCARS, NICS/TARE
and TRC/P-T-P. Locally, TDS simulates a mumber of VDU's,
preparing messages and comments as well as receiving
messages sent for local distribution.
The goal is to stress a CAMPS-system by generating
traffic up to busy-hour-load-maximum.
2.2 S̲Y̲S̲T̲E̲M̲ ̲F̲U̲N̲C̲T̲I̲O̲N̲
TDS is divided in two functionally separated parts:
- The VDU-simulation part, named the Test Drive
Package (TDP), described shortly in 2.2.1.
- Message Traffic on external channels discribed
in 2.2.2.
2.2.1 T̲e̲s̲t̲ ̲D̲r̲i̲v̲e̲ ̲P̲a̲c̲k̲a̲g̲e̲ ̲(̲T̲D̲P̲)̲
2.2.1.1 M̲a̲i̲n̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲s̲
In simulating a CAMPS-VDU, the main VDU-functions are
- sign on
- message preparation
- comment preparation
- message release
- message reception
- sign off
- receiving of queue updates, time etc.…86…1
…02… …02… …02… …02…
2.2.1.2 F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲R̲e̲s̲p̲o̲n̲s̲i̲b̲i̲l̲i̲t̲i̲e̲s̲
2.2.1.2.1 I̲n̲i̲t̲i̲a̲l̲i̲s̲a̲t̲i̲o̲n̲ ̲a̲n̲d̲ ̲T̲e̲r̲m̲i̲n̲a̲t̲i̲o̲n̲
TDP is started up under TOS, by first starting the
STI-assigning part, second the LTUX-part and third
the VDU-simulating part.
Close down will be done automatically, by command or
after a serious error.
2.2.1.2.2 C̲h̲e̲k̲p̲o̲i̲n̲t̲i̲n̲g̲ ̲a̲n̲d̲ ̲R̲e̲c̲o̲v̲e̲r̲y̲
TDP contains no checkpointing or recovery facilities.
2.2.1.2.3 E̲r̲r̲o̲r̲d̲e̲t̲e̲c̲t̲i̲n̲g̲ ̲a̲n̲d̲ ̲R̲e̲c̲o̲v̲e̲r̲y̲
On errordetecting, TDP will display a message indicating
the kind of error, and terminate the simulation.
2.2.1.2.4 D̲a̲t̲a̲c̲o̲l̲l̲e̲c̲t̲i̲o̲n̲
All imput and output from/to CAMPS are timetagged and
logged in the format in which it is received or sent
(LDU-format).
2.2.1.2.5 S̲e̲c̲u̲r̲i̲t̲y̲
NA
2.2.2 M̲e̲s̲s̲a̲g̲e̲ ̲T̲r̲a̲f̲f̲i̲c̲ ̲o̲n̲ ̲E̲x̲t̲e̲r̲n̲a̲l̲ ̲C̲h̲a̲n̲n̲e̲l̲s̲
2.2.2.1 M̲a̲i̲n̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲s̲
On the external channel part the main functions are
to
- transmit messages to a CAMPS site
- receive messages from the same site.
Traffic on the external channels are generated by sending
pre-formatted messages, using normal CAMPS packages
THP, handlers etc., with a minor change in THP to be
able to cortinuously reuse the pre-formatted messages.
See CAMPS documentation for details.
Reception of messages, reuses normal CAMPS packages
(THP,MDP,handlers etc.). Messages are routed to printer
only. See CAMPS documentation for details.
2.2.2.1.2 F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲l̲y̲ ̲R̲e̲s̲p̲o̲n̲s̲i̲b̲i̲l̲i̲t̲i̲e̲s̲
See CAMPS documentation as cited above.
2.3 C̲H̲A̲R̲A̲C̲T̲E̲R̲I̲S̲T̲I̲C̲S̲
2.3.1 T̲i̲m̲i̲n̲g̲
Local VDU-simulation (TDP):
Constants affecting timing directly
- TDX-bus bandwidth = 3200 bps
- Line speed btw. TDP/CAMPS = 2400 bps
- delays in-all levels = unknown.
Duration for preparation of one average-message (1500
characters) is in praxis (one proces) - 1 1/2 minutes
- 120 com's/hour.
Praxis for one average-comment (69 characters) shows
a duration of (one proces) - 1/2 minute - 120 com's/hour.
External channels:
Constants affecting timing directly
- CCIS/SCARS = 2 x 9600 bps
- NICS/TARE = 4 x 2400 bps
- TRC/P-T-P = 24 x 110 bps
Measurement of transmission in praxis not yet available.
2.3.2 T̲h̲r̲o̲u̲g̲h̲p̲u̲t̲
The goal is to load a CAMPS site up to busy hour load
maximum.
Busy hour load are as follows:
Local channels, output from TDP,
- preparation of 60 msgs/hour
- preparation of 130 comments/hour.
Local channels, input (from CAMPS to TDP),
- presentation of messages from
- CCIS - 140 msgs/hour
- SCARS - 15 msgs/hour
- P-T-P - 180 msgs/hour
- TARE - 1440 msgs/hour
- VDU's for coordination/release/local disbr)
560+ msgs/hour
- presentation of comments from
- CCIS - 10 com's/hour
- SCARS - 5 com's/hour
- VDU's - 130 com's/hour
- presentation of 45 vdu pages from CCIS/SCARS
External channels, output from TDS
via CCIS - 30 msgs/hour
- via SCARS - 10 msgs/hour
- via P-T-P - 60 msgs/hour
- via NICS/TARE - 500 msgs/hour
- via CCIS/SCARS - 45 vdu pages
External channels, imput to TDS
- VDU prepared - 60 msgs/hour
- OCR - 60 msgs/hour
- PTR - 5 msgs/hour
- CCIS relayed - 20 msgs/hour
- SCARS relayed - 5 msgs/hour
- TARE relayed - 30 msgs/hour
Average messagelength is 1500 characters.
Average commentlength is 69 characters.
To achieve the busy hour load, TDP is started up in
several processes.
For further details, see SRS, 3.5.11.5.2, 3.4.1.1.1
& 3.4.1.2.1.
3̲ ̲ ̲E̲N̲V̲I̲R̲O̲N̲M̲E̲N̲T̲
3.1 E̲Q̲U̲I̲P̲M̲E̲N̲T̲
TDS will run on 2 CR80D machines, one for external
traffic and one for TDP.
The TDP-machine will have
- 1 MW memory
- 1 dual floppy disk drive
- 1 80 MB SMD disk drive
- up to 5 TDS-LTUX'es for VDU-simulation with
async lines - 2400 bps
- 6 VDU's for test control.
The CR80D for extenal traffic will have
- 1.5 MW memory
- 1 dual floppy disk drive
- 80 MB SMD disk drive
- 4 VDU's for test control & supervisor
- 1 CCIS channel - 9600 bps
- 1 SCARS channel - 9600 bps
- 4 NICS/TARE channels - 2400 bps/ch
- 24 teletype channels - 110 bps/ch
- 5 printers.…86…1 …02… …02… …02… …02…
Figure 3.1-1
3.2 S̲O̲F̲T̲W̲A̲R̲E̲
3.2.1 S̲y̲s̲t̲e̲m̲ ̲S̲o̲f̲t̲w̲a̲r̲e̲
DAMOS, TOS, CAMPS Kernel,
See TDP in relation to above on next page.
3.2.2 D̲e̲v̲e̲l̲o̲p̲m̲e̲n̲t̲ ̲S̲o̲f̲t̲w̲a̲r̲e̲
DAMOS, TOS, SWELL, LDLINK, EDITOR,
SWELL-debugger, TCI.
Figure 3.2.1.-1
3.3 I̲N̲T̲E̲R̲F̲A̲C̲E̲S̲
3.3.1 E̲x̲t̲e̲r̲n̲a̲l̲ ̲i̲n̲t̲e̲r̲f̲a̲c̲e̲s̲
System interfaces.
TDS interfaces directly to a CAMPS site via external
and local channels as described in 3.1.
See figure 3.3.1.1-1 & 3.3.1.1-2 on next page.
Figure 3.3.1.1-1
Figure 3.3.1.1-2
3.4 F̲U̲N̲C̲T̲I̲O̲N̲S̲ ̲M̲A̲I̲N̲T̲A̲I̲N̲E̲D̲ ̲B̲Y̲ ̲O̲T̲H̲E̲R̲ ̲P̲A̲C̲K̲A̲G̲E̲S̲
1. Functions performed by reused CAMPS packages.
2. Routing of buffers in Transparent TDS-LTUX-HANDLER.
3. Routing, transmission and flow-control performed
by LTUX-FW (special TDS-Version).
4̲ ̲ ̲S̲Y̲S̲T̲E̲M̲ ̲D̲E̲S̲I̲G̲N̲
4.1 S̲Y̲S̲T̲E̲M̲ ̲O̲V̲E̲R̲W̲I̲E̲W̲
Teh Test Drive System (TDS) consists of 2 major subsystems
-
- VDU-simulation (Test Drive Package)
- External Traffic generator.
All off-line log analysing are based on reusing CAMPS
log-trace facilities, texteditor, hexdumps etc.
TDS reuses packages from
- operating system software, such as
- Kernel & TOS
- I/0 Control with handlers and TDX, TMS, IOS
- Storage and File Management
- Table Management
- System Status and Control
- Camp System Functions
- CAMPS envionment, such as
- Traffic Handling Package
- Message Distribution Package
- Terminal Package
- Storage & Retrieval
- Log Package
Further package description - refer to CAMPS System
Design (CPS/SDS/001).
4.1.1 T̲e̲s̲t̲ ̲D̲r̲i̲v̲e̲ ̲P̲a̲c̲k̲a̲g̲e̲
TDP performs the VDU-oriented main functions described
in 2.2.1, based on a script (command- and data-file).
Test-command-files (in the following referred to as
script-files) contains-
- instructions to the TDP, such as DELAY, STOP,
TERMINATE
- on-going-test messages to keep the operator
informed of test propagation
- textcontents to message- and comment - generation,
including addressing information
- function-keys
- verification-texts to test for valid CAMPS
responses.
TDP reads testcommands from the script-commandfile,
textcontents in the script-datafile if required, and
sends function-keys, data, answers etc. to CAMPS, just
as a "normal" operator/VDU.
Test Control VDU
4.1.2 E̲x̲t̲e̲r̲n̲a̲l̲ ̲T̲r̲a̲f̲f̲i̲c̲ ̲G̲e̲n̲e̲r̲a̲t̲i̲o̲n̲ ̲a̲n̲d̲ ̲R̲e̲c̲e̲p̲t̲i̲o̲n̲
The external traffic simulation part of TDS, prepares
and releases messages to be sent via external channels
to the CAMPS installation. Messages are logged in TDS
before sending (in THP).
Incoming traffic (from CAMPS) are logged and routed
to printer, only.
