top - download
⟦6b9d34afc⟧ Wang Wps File
Length: 21746 (0x54f2)
Types: Wang Wps File
Notes: CPS/SDS/001
Names: »1380A «
Derivation
└─⟦2c95d9416⟧ Bits:30006059 8" Wang WCS floppy, CR 0091A
└─ ⟦this⟧ »1380A «
WangText
…02…CPS/SDS/001
…02…BBC/811020…02……02…
CAMPS SYSTEM DESIGN SPECIFICATION
…02…ISSUE 1.1…02…CAMPS
T̲A̲B̲L̲E̲ ̲O̲F̲ ̲C̲O̲N̲T̲E̲N̲T̲S̲
5.15 TERMINAL PACKAGE ........................
610
5.15.1 General .............................
610
5.15.1.1 Purpose and Scope ...............
610
5.15.1.2 Applicable Documents and Project
References Special for Section
5.15 ............................
610
5.15.1.3 Terms and Abbreviations Special
for Section 5.15 ................
610
5.15.1.3.1 Terms .......................
610
5.15.1.3.2 Abbreviations ...............
611
5.15.2 Summary of Requirements .............
613
5.15.2.1 Package Description .............
613
5.15.2.2 Package Functions ...............
618
5.15.2.2.1 Main Functions (Normal
Operation) ..................
618
5.15.2.2.1.1 VDU's ...................
618
5.15.2.2.1.2 Printers ................
625
5.15.2.2.1.3 OCR's ...................
626
5.15.2.2.2 Functional Responsibilities .
626
5.15.2.2.2.1 Initialization Close-Down
and Restart .............
626
5.15.2.2.2.2 Checkpointing and
Recovery ................
627
5.15.2.2.2.3 Error Detection and
Error Handling ..........
628
5.15.2.2.2.4 Integrity of Operation ..
628
5.15.2.2.2.5 Data Collection
(Log, Statistics and
Reports) ................
629
5.15.2.2.2.6 Security ................
629
5.15.2.3 Characteristics .................
630
5.15.2.3.1 Timing ......................
630
5.15.2.3.2 Throughput ..................
631
5.15.2.3.3 Flexibility .................
632
5.15.2.3.4 Accuracy ....................
633
5.15.3 Functions Maintained by Other
Packages ............................
634
5.15 T̲E̲R̲M̲I̲N̲A̲L̲ ̲P̲A̲C̲K̲A̲G̲E̲
5.15.1 G̲e̲n̲e̲r̲a̲l̲
5.15.1.1 P̲u̲r̲p̲o̲s̲e̲ ̲a̲n̲d̲ ̲S̲c̲o̲p̲e̲
N/A.
5.15.1.2 A̲p̲p̲l̲i̲c̲a̲b̲l̲e̲ ̲D̲o̲c̲u̲m̲e̲n̲t̲s̲ ̲a̲n̲d̲ ̲P̲r̲o̲j̲e̲c̲t̲ ̲R̲e̲f̲e̲r̲e̲n̲c̲e̲s̲,̲ ̲S̲p̲e̲c̲i̲a̲l̲
̲f̲o̲r̲ ̲S̲e̲c̲t̲i̲o̲n̲ ̲5̲.̲1̲5̲
N/A.
5.15.1.3 T̲e̲r̲m̲s̲ ̲a̲n̲d̲ ̲A̲b̲b̲r̲e̲v̲i̲a̲t̲i̲o̲n̲s̲,̲ ̲S̲p̲e̲c̲i̲a̲l̲ ̲f̲o̲r̲ ̲S̲e̲c̲t̲i̲o̲n̲ ̲5̲.̲1̲5̲
1.3.1 T̲e̲r̲m̲s̲
N/A.
5.15.1.3.2 A̲b̲b̲r̲e̲v̲i̲a̲t̲i̲o̲n̲s̲
DIDIA Delivery Dialogue Coroutine
DIFCO Delivery Function Control Coroutine
DIRT Delivery Retrieval Coroutine
DIVCO Delivery VDU Control Coroutine
DELCO Delivery Control Coroutine
MDO VDU MDCO Package
MDOS VDU MDCO Subprocess
MSO VDU Message Service Package
MSOS VDU Message Service Subprocess
OCCO OCR Control Coroutine
OCIP OCR Input Coroutine
OCP OCR Package
ORF Outstanding Reports File
PAC Preparation Data Base Access Control Coroutine
PPF Print Format File
PRI Printer Package
PRIS User Printer Process
PROP Printer Output Coroutine
RESCO Request Control Coroutine
RETR Retrieval Coroutine
SEDIA Message Service Dialogue Coroutine
SEFCO Message Service Function Control Coroutine
SERT Message Service Retrieval Coroutine
SEVCO Message Service VDU Control Coroutine
SFCO Supervisor Function Control Coroutine
SPICO Supervisor Printer Control Coroutine
SPIP Supervisor Printer Process
SPR Supervisor Printer Package
SRETR Supervisor Retrieval Coroutine
SUP Supervisor VDU Package Coroutine
SVCO Supervisor VDU Control Coroutine
SVDIA Supervisor Dialogue Coroutine
SVUP Supervisor VDU Process
UFCO User Function Control
UMAM User Message Access Monitoring Process
UPCO User Print Control Coroutine
VCO User VDU Control Coroutine
VDIA User VDU Dialogue Coroutine
VUP VDU User Package.
5.15.2 S̲u̲m̲m̲a̲r̲y̲ ̲o̲f̲ ̲R̲e̲q̲u̲i̲r̲e̲m̲e̲n̲t̲s̲
5.15.2.1 P̲a̲c̲k̲a̲g̲e̲ ̲D̲e̲s̲c̲r̲i̲p̲t̲i̲o̲n̲
a) The Terminal Package (TEP) constitutes the interface
between the terminals and devices listed below
and the CAMPS System.
1) VDU
2) Printers
3) Optical Character Reader (OCR).
b) The VDU is the only means by which CAMPS personnel
may gain access to the services of the CAMPS FUNCTION,
which include:
- The CAMPS Supervisor Function.
- The CAMPS Message Distribution Control Function.
- The CAMPS Message Service Function.
- The CAMPS User Function, i.e. Preparation,
Reception and Release.
c) TEP is responsible for all requirements directly
related to the the CAMPS FUNCTIONS.
d) TEP is responsible for print-out of traffic queued
to:
- printers logically associated with a VDU
- printers addressable by SCD's
- supervisor printers.
e) TEP is responsible for receiving messages entered
via OCR and directing them to the Traffic Handling
Package.
f) The packages to which TEP interfaces are:
1) Kernel
2) I/O control Software
3) CAMPS Systems Functions
4) Storage and File Management
5) SS&C Software
6) Traffic Handling
7) Distribution
8) Table Management
9) Storage and Retrieval
10) Log and Accountability
11) Statistics
g) In fig. 5.15.2.1-1 an overview of the interfaces
of TEP is depicted.
h) In fig. 5.15.2.1-2, the message flow between TEP
and the CAMPS SYSTEM is shown.
i) In fig. 5.15.2.1-3, the information flow between
TEP and the CAMPS SYSTEM is depicted.
Fig. 5.15.2.1-1 TEP Interface Overview
Fig. 5.15.2.1-2 Message Flow between TEP and CAMPS SYSTEM
Fig. 5.15.2.1-3 Information Flow between TEP and CAMPS SYSTEM
5.15.2.2 P̲a̲c̲k̲a̲g̲e̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲s̲
In this section the functions to be performed by TEP
are outlined. As stated in section 5.15.2.1, the main
task of TEP is to interface VDU's, printers and OCR
to the CAMPS system. In the following subsection, the
main functions to be performed for each of the above
mentioned terminal types will be described.
5.15.2.2.1 M̲a̲i̲n̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲ ̲(̲N̲o̲r̲m̲a̲l̲ ̲O̲p̲e̲r̲a̲t̲i̲o̲n̲)̲
5.15.2.2.1.1 V̲D̲U̲s̲
a) The main functions to be implemented by TEP with
respect to VDUs are those of the CAMPS FUNCTIONS.
b) The CAMPS FUNCTION consists of:
1) The Supervisor Function.
2) The Message Distribution Control (MDCO) Function.
3) The Message Service (MSO) Function.
4) The User Function.
c) When a person signs-on on a VDU he will gain access
to as many of the functions listed above in b1)
to b4) as assigned to him and the VDU in common
by the supervisor.
d) When a person has access to more than one of the
functions listed in (b), he shall inform the system
which one he wants to gain access to, using the
command SELECT CAMPS FUNCTION.
e) The person may at any time issue the SELECT CAMPS
FUNCTION, and thereby gain access to the specified
function, i.e. a switch between the functions is
possible.
f) The CAMPS User Function consists of three sub-functions:
Preparation, Reception and Release, and access
shall be granted explicitly for each of the sub-functions
before access to it may be achieved.
g) The command SELECT CAMPS FUNCTION is, however,
only relevant for the functions listed in (b).
If a person, who has signed-on on a VDU has access
to two or more sub-functions of the CAMPS user
function, he may freely access the services of
either, where access is achieved to the User Function.
h) In fig. 5.15.2.2-1, an overview of the CAMPS FUNCTION
is depicted.
i) The VDU interface to the CAMPS system for which
TEP is responsible and to which the requirements
are given through the requirements to the CAMPS
FUNCTION, implies the following TEP responsibilities:
1) Man/Machine I/F support and monitoring.
2) Presentation of traffic queued to VDUs.
3) Directing all entered requests/commands to
the relevant package within CAMPS.
4) Allowing for preparation of messages/comments.
j) In figs. 5.15.2.2-2 through 5.15.2.2-6, an overview
of the services for each of the functions constituting
the CAMPS FUNCTION is depicted (for details of
the functions ref. CPS/230/ICD/0002).
Fig. 5.15.2.2-1 Camps Function Overview
Fig. 5.15.2.2-2
Functional Structure Supervisor System Control Functions
Fig. 5.15.2.2-3…01…Supv. Msgh.Function Overview
Fig. 5.15.2.2-4…01…MDCO Function Overview
Fig. 5.15.2.2-5…01…MSO Function Overview
5.15.2.2.1.2 P̲r̲i̲n̲t̲e̲r̲s̲
a) Low speed teleprinters may be used as PTR, PTP,
printer. TEP is only responsible for implementation
of functions applicable to the device, when it
is used as ROP.
b) Functionally, three types of printers exist:
Supervisor printers.
Shared printers.
Stand alone printers.
c) The supervisor printers are used for:
1) Print-out of reports.
2) Print-out of log.
3) Print-out of statistics
4) Print-out of supervisory print.
d) One to four printers may at system generation be
allocated to supervisor printers.
e) The supervisor may dynamically assign one or more
of the print types listed in (c) above to be printed
on a specific one of his printers.
f) If more than one print-out function is assigned
to one printer, print-out is per priority as defined
below:
1) Report print.
2) Supervisor print-out.
3) Statistics print.
4) Log print.
g) A printer is denoted a shared printer if it is
logically associated with a VDU, i.e. where the
function key "Print" of the VDU keyboard is activated,
the item to be printed is queued for print-out
at the logically associated printer, defined in
the VDU profile (terminal profile).
h) Stand alone printers are addressable by SCDs, i.e.
traffic may be queued to such printers on the same
criteria as for VDUs.
i) A printer may functionally act as stand alone printer
and shared printer at the same time.
j) Traffic belonging to the precedence level FLASH
(or above) shall cause pre-emption.
k) Thus pre-emption is applicable to:
1) The supervisor printer assigned supervisory
print.
2) Shared printers.
3) Stand alone printers.
as print is queued for these per precedence level.
l) Any printed output printed at stand alone printers,
shared printers and the supervisor printer assigned
supervisory print, shall carry a document control
number and at the top and bottom of each page the
classification of the output shall be printed.
5.15.2.2.1.3 O̲C̲R̲s̲
TEP is responsible for validating and releasing messages
entered via the OCR and allocation of release number.
5.15.2.2.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̲
5.15.2.2.2.1 I̲n̲i̲t̲i̲a̲l̲i̲z̲a̲t̲i̲o̲n̲,̲ ̲C̲l̲o̲s̲e̲-̲D̲o̲w̲n̲ ̲a̲n̲d̲ ̲R̲e̲s̲t̲a̲r̲t̲
a) TEP is controlled by the SSC software, and shall
implement the functions listed below to be executed
on command from SSC:
- Initialization.
- Close-Down.
- Restart.
a1) Initialization.
On command from SSC, TEP shall initialize the TEP
software. The initialization refers to the functions
to be performed after load or reload of TEP and
which must be executed before TEP can initiate
its normal operation.
a2) Close-Down.
On command from SSC, TEP shall terminate its current
processing in an ordered manner and bring itself
into a state, where it can respond to a restart
command.
a3) Restart.
On command from SSC, TEP shall be able to execute
a restart function. Restart is commanded following
close-down, switch-over or total system failure.
TEP shall implement functions necessary to restart
after each situation listed above.
5.15.2.2.2.2 C̲h̲e̲c̲k̲p̲o̲i̲n̲t̲i̲n̲g̲ ̲a̲n̲d̲ ̲R̲e̲c̲o̲v̲e̲r̲y̲
a) Checkpointing is performed in accordance with the
overall definition for the CAMPS system (ref. CAMPS
Message Flow).
b) Recovery:
When TEP is restarted by SSC software following
close-down, switch-over or total system failure,
"recovery required" is specified by SSC.
Relevant queues will then have a contents according
to latest checkpoint and TEP shall inspect the
queues to re-establish the TEP state.
5.15.2.2.2.3 E̲r̲r̲o̲r̲ ̲D̲e̲t̲e̲c̲t̲i̲o̲n̲ ̲a̲n̲d̲ ̲E̲r̲r̲o̲r̲ ̲H̲a̲n̲d̲l̲i̲n̲g̲
a) Error Detection:
TEP has no explicit responsibility for detection
of hardware errors.
The general principle for error detection is that
a module detecting an error reports it and possibly
deals with it.
b) Error Handling:
Errors detected by TEP shall be reported to the
SSC software together with information as to whether
TEP was able to handle the error itself or not.
Detection of an error which TEP cannot handle itself
shall cause TEP to stop its activities and transfer
control to SSC for further handling of the situation.
Control will be returned from SSC in cases where
continued operation is possible after SSC handling
of error.
5.15.2.2.2.4 I̲n̲t̲e̲g̲r̲i̲t̲y̲ ̲o̲f̲ ̲O̲p̲e̲r̲a̲t̲i̲o̲n̲
TEP shall contain credibility check to limit the effects
of corrupt or inacurate data to the extent that this
does not introduce redundant processing which will
decrease the system throughput.
It shall be a design aim that wherever possible the
consequence of a single software fault incident will
not affect more than one transaction. The detection
of an inconsistency indicating a fault shall initiate
a report and the re-processing from a validated check-point
in an attempt to recover with a minimum of discontinuity.
Only after further failures should major recovery or
operator intervention action be invoked.
5.15.2.2.2.5 D̲a̲t̲a̲ ̲C̲o̲l̲l̲e̲c̲t̲i̲o̲n̲ ̲(̲L̲o̲g̲,̲ ̲S̲t̲a̲t̲i̲s̲t̲i̲c̲s̲ ̲a̲n̲d̲ ̲R̲e̲p̲o̲r̲t̲s̲)̲
a) L̲o̲g̲ ̲C̲o̲l̲l̲e̲c̲t̲i̲o̲n̲
a1) Log information on user, MDCO, MSO and supervisor
transactions on VDUs shall be collected by TEP
and reported to the log package.
a2) Log information on printer transactions shall be
collected by TEP and reported to the log package.
a3) Log information on OCR transactions shall be collected
by TEP and reported to the log package.
b) S̲t̲a̲t̲i̲s̲t̲i̲c̲s̲ ̲I̲n̲f̲o̲r̲m̲a̲t̲i̲o̲n̲
Statistics information on transactions on VDUs
included in the CAMPS User Function shall be collected
by TEP and reported to the statistics package.
c) R̲e̲p̲o̲r̲t̲s̲
c1) When a user issues a deletion request on a message,
which the user is not allowed to delete, TEP shall
generate a deletion request report and queue it
in the supervisor's report queue.
5.15.2.2.2.6 S̲e̲c̲u̲r̲i̲t̲y̲
a) The terminal package shall implement the security
related functions listed below:
a1) When a user (person with access to the User Sub-function
Release) requests a message to be released, the
Terminal Package shall request TEMCO to perform
a Release Security Interrogation. The Terminal
Package shall await the answer from TEMCO and only
release the message if the security interrogation
is reported successfully completed by TEMCO.
a2) For each CAMPS User Subfunction, i.e. Preparation,
Release and Reception, the VDU User Package shall
check each command entered by the user against
the assigned subfunction, and prevent illegal transactions
from being initiated.
5.15.2.3 C̲h̲a̲r̲a̲c̲t̲e̲r̲i̲s̲t̲i̲c̲s̲
The following characteristics are extracted from the
CPS/230/SYS/0001 sec. 3.4.
5.15.2.3.1 T̲i̲m̲i̲n̲g̲
User Terminal Interaction:
a) Transmission to terminals of a response or other
output shall be at cadence speed once commenced.
b) Non interactive transactions shall in 90% of all
cases commence not later than 5 seconds after the
event which gives rise to the transaction, assuming
the terminal facility required is available.
c) During interactive transactions at VDUs, the response
time shall be measured as the time delay from transmission
of the last character of the input to the system
and the start of display of response/next format/menu.
1) Response times for entry in the command line
shall not exceed 1 second in 90% of all cases.
2) Response times for validation of a request
(e.g. retrieval, status) shall not exceed 5
seconds in 90% of all cases.
3) Response times for validation of information
(e.g. message, edited message) shall not exceed
10 seconds per VDU page in 90% of all cases.
d) Once an interactive transaction has been completed
or terminated/aborted the succeeding action(s)
by the system shall commence within 5 seconds in
90% of all cases.
e) Update of queue status in the VDU header area shall
take place each minute. If a message of precedence
FLASH (or above) arrives, the queue status shall
be updated immediately.
Supervisory Command Response:
f) Response time shall be measured as of 5.15.2.3.1.c.
The response time is time to acceptance of command
parameters (i.e. request for new input).
g) Response time for commands entered via the command
line or via a format display shall be less than
5 seconds for 99% of all commands.
h) The above time shall never exceed 10 seconds.
5.15.2.3.2 T̲h̲r̲o̲u̲g̲h̲p̲u̲t̲
a) The busy second character flow from/to a CAMPS
of maximum equipment configuration employing formats
applicable to messages not yet released shall never
exceed:
To CAMPS ............... 200 Chars/sec
From CAMPS ............. 1400 Chars/sec
b) Messages will on average be sent for coordination
twice.
c) Messages will on average give rise to two comments.
d) A comment will on average be of 69 characters excluding
heading information.
e) Messages will on average be edited twice.
f) Maximum operator keying rate is assumed to be 10
IA5 character/s.
g) The channel capacity for transmission from VDU
to system and for system response output is 120
IA5 characters per second.
h) Release terminal positions release messages at
a rate of max. six per minute.
The throughput in this section is specified for
a CAMPS of maximum equipment configuration as defined
in 3.4.1.2.1.
i) Throughput requirements in this section shall for
a CAMPS of less than maximum configuration be reduced
as follows:
M̲a̲x̲.̲ ̲c̲o̲n̲f̲i̲g̲u̲r̲a̲t̲i̲o̲n̲:̲
VDU (32) 32 x 120 chars/s
TPs (as TRC) 24 x 10 char/s
j) For a CAMPS with less than max. configuration the
theoretical flow shall be calculated as above and
the throughput requirements in this section be
reduced accordingly.
k) Channels used in operator communication with computer
are assumed to be idle 60% of the time due to operator
keying and loaded by the transmission to computer
or computer response 40% of the time.
l) The message header (ACP127 FL1-FL11) comprises
25% in average of the total length of a message.
5.15.2.3.3 F̲l̲e̲x̲i̲b̲i̲l̲i̲t̲y̲
a) Precedences:
Four levels of precedences shall be distinguished
by the system. To accomodate a possible increase
in the number of precedence levels used, allowance
shall be made in the design for two other levels.
Defined Precedences Precedences Foreseen
highest
Superflash
Flash Flash
Immediate Immediate
Superpriority
Priority Priority
Routine Routine
lowest
b) Formats:
Changes in formats, new formats, changes in format
tolerances and improvements in Man/Machine I/F
shall be flexibility requirements during TEP design.
c) Specific character strings:
The design shall allow for changes to the external
representation of character strings by allocation
of internal value for these.
5.15.2.3.4 A̲c̲c̲u̲r̲a̲c̲y̲
a) Accuracy of input data:
Time shall be exact within 500 ms, i.e. a tolerance
of +/- 500 ms is acceptable.
All other input data shall be exact.
b) Accuracy of output data:
Output-data shall be exact, except for time where
the tolerance mentioned in (a) above applies.
5.15.3 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̲
a) Security control of TEP transactions is performed
by TEMCO (SSC software) and system software in
common.
b) TEMCO is responsible for:
1) Sign-on, sign-off, select camps function procedures.
2) Security interrogations and warnings of VDU
users without the knowledge (i.e. without TEP
interaction) of TEP.
3) For setting of access profiles for each active
TEP device.
c) System software is responsible for:
1) Monitoring that TEP does not access objects
not allowed by TEMCO via access profile settings.
2) Notifying TEMCO when a security interrogation
or warning shall be performed.
