top - download
⟦f5f0e5f5f⟧ Wang Wps File
Length: 42311 (0xa547)
Types: Wang Wps File
Notes: CPS/SDS/012
Names: »1122A «
Derivation
└─⟦af7ebed0d⟧ Bits:30006042 8" Wang WCS floppy, CR 0067A
└─ ⟦this⟧ »1122A «
WangText
#…00……00……00……00…,…0a……00……00…,…0b… …0b… …00… …06……11…
…11……06……10……0a……10……0d……10……02……10… …10……05……10……06……10……07……0f……0d……0f……02……0f…
…0f… …0f……05……0f……06……0f……86…1 …02… …02… …02…
…02…CPS/SDS/012
…02…BBC/810801…02……02…
TERMINAL PACKAGE
…02……02…CAMPS
T̲A̲B̲L̲E̲ ̲O̲F̲ ̲C̲O̲N̲T̲E̲N̲T̲S̲
1 GENERAL .......................................
5
1.1 PURPOSE AND SCOPE .........................
5
1.2 APPLICABLE DOCUMENTS AND PROJECT
REFERENCES ................................
6
1.2.1 Applicable Documents ..................
6
1.2.2 Reference Documents ...................
6
1.3 TERMS AND ABBREVIATIONS ...................
7
1.3.1 Terms .................................
7
1.3.2 Abbreviations .........................
8
2 SUMMARY OF REQUIREMENTS .......................
10
2.1 PACKAGE DESCRIPTION .......................
10
2.2 PACKAGE FUNCTIONS .........................
15
2.2.1 Main Functions (Normal Operation) .....
15
2.2.1.1 VDU's .............................
15
2.2.1.2 Printers ..........................
23
2.2.1.3 OCR's .............................
24
2.2.2 Functional Responsibilities ...........
23
2.2.2.1 Initialization Close-Down
and Restart .......................
24
2.2.2.2 Checkpointing and Recovery ........
25
2.2.2.3 Error Detection and
Error Handling ....................
26
2.2.2.4 Integrity of Operation ............
26
2.2.2.5 Data Collection
(Log, Statistics and Reports) .....
27
2.2.2.6 Security ..........................
27
2.3 CHARACTERISTICS ...........................
28
2.3.1 Timing ................................
28
2.3.2 Throughput ............................
29
2.3.3 Flexibility ...........................
30
2.3.4 Accuracy ..............................
31
3 FUNCTIONS MAINTAINED BY OTHER PACKAGES ........
32
4 PACKAGE DESIGN ................................
33
4.1 Package Overview ..........................
33
4.1.1 Supervisor VDU Package ................
33
4.1.2 Supervisor Printer Package ............
36
4.1.3 VDU MDCO Package ......................
39
4.1.4 VDU MSO Package .......................
42
4.1.5 VDU USER Package ......................
45
4.1.5.1 VDU USER Subprocess ...............
45
4.1.5.2 USER Message Access
Monitoring Process ................
46
4.1.6 OCR Package ...........................
50
4.1.7 USER Printer Package ..................
52
4.2 Terminal Package Interfaces ...............
54
4.2.1 External Interfaces ...................
54
4.2.2 Package Interfaces ....................
54
4.2.3 Internal Interfaces ...................
54
1̲ ̲G̲E̲N̲E̲R̲A̲L̲
1.1 P̲U̲R̲P̲O̲S̲E̲ ̲A̲N̲D̲ ̲S̲C̲O̲P̲E̲
a) The Terminal Package Specification for the CAMPS
Project/4040 is written to fulfil the following
objectives:
1) To provide detailed definition of the package
functions and software architecture.
2) To provide user opererational and development
personnel with details of the ongoing analysis.
3) To define the interfaces with other packages
and to describe their facilities.
b) The Terminal Package Specification is an overview
document defining the major functions and software
architecture of the package to a level sufficient
to start preliminary design of each major function.
(As an overview document the general table of contents
does not apply fully).
b1) The Terminal Package constitutes one of the building
blocks of the CAMPS System. For an overall description
of the CAMPS System, refer CAMPS System Design
Specification, doc. no. CPS/SDS/001.
b2) The preliminary design of each major function referenced
in (b) is described in the documents listed below:
- Supervisor VDU Package doc. no. CPS/SDS/023
- Supervisor Printer Package doc. no. CPS/SDS/024
- VDU MDCO Package doc. no. CPS/SDS/025
- VDU MSO Package doc. no. CPS/SDS/026
- VDU User Package doc. no. CPS/SDS/027
- OCR Package doc. no. CPS/SDS/028
- Printer Package doc. no. CPS/SDS/029
b3) All TEP Package internal data and interfaces are
defined within this document and the documents
referenced in (b2) above. For a detailed data description
of data external to the Terminal Package and interfaces
to other packages, refer to the Database Design
Document CPS/DBD/001 and the Software I/F control
document CPS/ICD/009.
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̲
1.2.1 A̲p̲p̲l̲i̲c̲a̲b̲l̲e̲ ̲D̲o̲c̲u̲m̲e̲n̲t̲s̲
1. CAMPS System Design Requirement Specification,
doc. no. CPS/210/SYS/0001.
2. Supervisor Commands and Procedures,
doc. no. CPS/230/ICD/0002.
3. User Procedure,
doc. no. CPS/230/ICD/0001.
4. OCR Interface,
doc. no. CPS/ICD/008.
5. CAMPS System Design Specification,
doc. no. CPS/SDS/001.
6. CAMPS Data Base Design Document,
doc. no. CPS/DBD/001
7. CAMPS Software Interface Control Document,
doc. no. CPS/ICD/009.
1.2.2 R̲e̲f̲e̲r̲e̲n̲c̲e̲ ̲D̲o̲c̲u̲m̲e̲n̲t̲s̲
Document Name Document Number
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲
Camps System Functions CPS/SDS/002
Message Management CPS/SDS/003
System Status and Control CPS/SDS/004
Table Management CPS/SDS/005
Input / Output Control CPS/SDS/006
Storage and Retrieval CPS/SDS/007
Statistics CPS/SDS/008
Logging CPS/SDS/009
Traffic Handling CPS/SDS/010
Message Distribution Package CPS/SDS/011
VDU Supervisor Package CPS/SDS/023
Supervisor Printer Package CPS/SDS/024
VDU MDCO Package CPS/SDS/025
VDU MSO Package CPS/SDS/026
VDU User Package CPS/SDS/027
OCR Package CPS/SDS/028
Printer Package CPS/SDS/029
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 T̲e̲r̲m̲s̲
N/A.
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.
2̲ ̲ ̲S̲U̲M̲M̲A̲R̲Y̲ ̲O̲F̲ ̲R̲E̲Q̲U̲I̲R̲E̲M̲E̲N̲T̲S̲
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. 2.1-1 an overview of the interfaces of
TEP is depicted.
h) In fig. 2.1-2, the message flow between TEP and
the CAMPS SYSTEM is shown.
i) In fig. 2.1-3, the information flow between TEP
and the CAMPS SYSTEM is depicted.
Fig. 2.1-1 TEP Interface Overview
Fig. 2.1-2 Message Flow between TEP and CAMPS SYSTEM
Fig. 2.1-3 Information Flow between TEP and CAMPS SYSTEM
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 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.
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̲)̲
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. 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. 2.2-2 through 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. 2.2-1 Camps Function Overview
Fig. 2.2-2
Functional Structure Supervisor System Control Functions
Fig. 2.2-3…01…Supv. Msgh.Function Overview
Fig. 2.2-4…01…MDCO Function Overview
Fig. 2.2-5…01…MSO Function Overview
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.
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.
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̲
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.
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.
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.
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.
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.
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.
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.
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 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.
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.
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.
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.
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.
4̲ ̲ ̲P̲A̲C̲K̲A̲G̲E̲ ̲D̲E̲S̲I̲G̲N̲
4.1 P̲A̲C̲K̲A̲G̲E̲ ̲O̲V̲E̲R̲V̲I̲E̲W̲
The Terminal Package (TEP) consists of the following
packages:
Supervisor VDU Package (SUP)
Supervisor Printer Package (SPR)
VDU MDCO Package (MDO)
VDU MSO Package (MSO)
VDU User Package (VUP)
OCR Package (OCP)
User Printer Package (PRI)
For each of the packages the structuring in coroutines
and semaphores (S1, S2, S3) is described in the following
sections (for specification of coroutines and semaphores
ref. CPS/SDS/002 CSF).
4.1.1 S̲u̲p̲e̲r̲v̲i̲s̲o̲r̲ ̲V̲D̲U̲ ̲P̲a̲c̲k̲a̲g̲e̲
The S̲u̲pervisor VDU-P̲ackage (SUP) consists of two processes,
one process containing the software required to support
the VDU handling and one containing software to control
the Preparation Database. The latter UMAN is shared
with the V̲DU U̲ser P̲ackage (VUP) (as will be specified
later) and is only used in connection with preparation
of Service Messages.
An overview of the S̲upervisor V̲DU̲ P̲rocess (SVUP) is
shown on fig. 4.1-1. It consists of four subpackages
(implemented as coroutines).
a) SVCO (S̲upervisor V̲DU C̲o̲ntrol) which reacts upon
commands from TEMCO and controls the other coroutines
as well as maintaining the VDU Header Status Area.
b) SFCO (S̲upervisor F̲unction C̲o̲ntrol) which reacts
upon commands from SVCO, F/C Keys (Function Keys)
from keyboard and input from the Answer Queue and
Response Queue. It also receives input from the
Retrieve Coroutine (SRETR) and controls the Dialogue
Routine (SVDIA).
It contains all the functions for c̲o̲n̲t̲r̲o̲l̲ of the
M̲an M̲achine I̲nterface (MMI) and interfacing to
other packages as well as command execution.
c) SVDIA (S̲upervisor V̲DU D̲i̲a̲logue) which performs
input and output to and from the VDU Format Area
and validation of input data on command from SFCO.
d) SRETR (S̲upervisor R̲e̲t̲r̲ieval) which receives answers
(messages or error codes) from SAR on requests
sent to SAR from SFCO. It communicates on-line
retrieved messages to SFCO and off-line retrieved
messages to the Response Queue.
Communication with other packages (apart from Monitor
Calls) is done via queues. The SVUP has four input
queues:
Command Queue:
Commands from TEMCO and time events from Timer
Monitor.
Answer Queue:
Answers to requests to other packages.
Response Queue:
Off-line Retrieval Results (placed in the queue
by SRETR).
Retrieve Queue:
Retrieval results (off-line and on-line) from SAR.
The detailed analysis leading to the breakdown
of SVUP into these 4 sub-packages is similar to
the one presented in CPS/SDS/027 (VUP) and thus
shall not be repeated in this document.
Fig. 4.1-1 SVUP Structure
4.1.2 S̲u̲p̲e̲r̲v̲i̲s̲o̲r̲ ̲P̲r̲i̲n̲t̲e̲r̲ ̲P̲a̲c̲k̲a̲g̲e̲
This package consists of up to five processes, ref.
fig. 4.1-2. One process contains the software for handling
print queued for the supervisor printers and distributing
it to the appropriate processes performing the actual
print-out. Up to four processes (subprocesses) identical
to the User Printer Subprocess (PRIS) drive the printer,
taking print items from the queues where SPIP has delivered
them.
The S̲upervisor P̲ri̲nt P̲rocess (SPIP) consists of three
subpackages (coroutines):
a) SPICO (S̲upervisor P̲ri̲nt C̲o̲ntrol) which reacts upon
SSC commands and controls the other coroutines.
b) DELCO (D̲e̲l̲ivery C̲o̲ntrol) which reacts upon commands
from SPICO, input from the Supervisor Print Queue,
the Report Queue, the Log Print Queue and the Statistics
Print Queue. From RESCO it receives information
requested by RESCO for delivery to the Supervisor
Printer. DELCO controls the outstanding Reports
File (ORF):
Storage of reports.
Removal of reports for print.
Clearance of reports on request.
DELCO distributes items for print to the printer
process currently assigned for the various types
of print. For Supervisor Print of Flash precedence,
DELCO signals the PRIS currently assigned Supervisor
Print by command to the Command Queue for the process.
c) RESCO (R̲e̲ques̲t C̲o̲ntrol) which receives the following
print requests from the Supervisor VDU Process
(SVUP):
System Information Extract Requests
Table Print Requests
and obtains the requested items by request to TMP
or LOG. When obtained, the item is passed to DELCO
for delivery to the Supervisor Print Process.
d) Communication with other packages (apart from Monitor
Calls) is done via queues. The SPIP has four main
queues:
1) Command Queue:
Commands from SSC and notification that a message
of flash precedence has been sent to the Supervisor
Print Queue.
2) Supervisor Print Queue:
This consists of six subqueues, one for each
precedence level. To this queue items for print
at the Supervisor Printer are sent.
A main queue consisting of three subqueues:
3) Report Queue:
Reports sent from other packages for print
at the Report Printer.
4) Log Print Queue:
Log records sent from the log package for print
at the the Log Printer.
5) Statistics Print Queue:
Statistics information sent from the Statistics
Package for print at the Statistics Printer.
6) Request Queue:
Print requests sent from the Supervisor VDU
Package for print at the Supervisor Printer.
Fig. 4.1-2 SPR-Structure
4.1.3 V̲D̲U̲ ̲M̲D̲C̲O̲ ̲P̲a̲c̲k̲a̲g̲e̲
This package consists of two processes, one process
containing the software required to support the VDU
handling and one containing the software to control
the Preparation Database. The latter is shared with
the VDU User Package (VUP) and is used in connection
with Service Message Preparation.
An overview of the M̲D̲CO̲ S̲ubprocess (MDOS) is shown
on fig. 4.1-3. It consists of four subpackages (coroutines):
a) DIVCO (D̲eli̲v̲ery C̲o̲ntrol) which reacts upon commands
from TEMCO and controls the other coroutines as
well as maintaining the VDU Header Status Area.
b) DIFCO (D̲eli̲very F̲unction C̲o̲ntrol) which reacts
upon commands from DIVCO, F/C keys from keyboard
and input from the Answer Queue, the Receive Queue
and the Response Queue. It also receives input
from DIRT and controls DIDIA. It contains all the
functions for c̲o̲n̲t̲r̲o̲l̲ of the M̲an M̲achine I̲nterface
(MMI) and interfacing to other packages as well
as command execution.
c) DIDIA (D̲eli̲very D̲i̲a̲logue) which reacts upon command
from DIFCO and performs input and output to and
from the VDU Format Area and validation of input
data.
d) DIRT (D̲eli̲very R̲et̲rieval) which receives answers
from SAR (messages or error codes) on request sent
to SAR from DIFCO. It communicates on-line retrieval
results to DIFCO and off-line retrieval results
to the Response Queue.
Communication with other packages (apart from Monitor
Calls) is done via queues. The MDOS has five queues:
Command Queue:
Commands from TEMCO, timer events from Timer Monitor
and flash notifications.
Answer Queue:
Answers to requests to other packages. Messages
for continued assistance.
Message Distribution Queue:
This consists of six subqueues, one for each precedence
level.
Messages for MDCO assistance are sent to this queue.
Response Queue:
Off-line Retrieval Results (placed in the queue
by DIRT).
Retrieve Queue:
Retrieval results (off-line and on-line from SAR).
Fig. 4.1-3 MDO-Structure
4.1.4 V̲D̲U̲ ̲M̲S̲O̲ ̲P̲a̲c̲k̲a̲g̲e̲
This package consists of two processes, one process
containing the software required to support the VDU
handling and one containing the software to control
the Preparation Database. The latter is shared with
the VDU User Package (VUP) and is used in connection
with Service Message Preparation.
An overview of the M̲S̲O̲ S̲ubprocess (MSOS) is shown
on fig. 4.1-4. It consists of four subpackages (coroutines):
a) SEVCO (message S̲e̲rvice V̲DU C̲o̲ntrol) which reacts
upon commands from TEMCO and controls the other
coroutines as well as maintaining the VDU Header
Status Area.
b) SEFCO (Message S̲e̲rvice F̲unction C̲o̲ntrol) which
reacts upon commands from SEVCO, F/C keys from
keyboard and input from the Answer Queue, the Incoming
Message Queue, the Outgoing Message Queue and the
Response Queue. It also receives input from SERT
and controls SEDIA. It contains all the functions
for c̲o̲n̲t̲r̲o̲l̲ of the MMI and interfacing with other
packages as well as command execution.
c) SEDIA (Message S̲e̲rvice D̲i̲a̲logue) which reacts upon
commands from SEFCO and performs input and output
to and from the VDU Format Area and validation
of input data.
d) SERT (Message S̲e̲rvice R̲et̲rieval) which receives
answers from SAR (messages or error codes) on request
sent to SAR from SEFCO. It communicates on-line
retrieval results to SEFCO and off-line retrieval
results to the Response Queue.
Communication with other packages (apart from monitor
calls) is done via queues. The MSOS has six queues:
Command Queue:
Commands from TEMCO, Timer Events from Timer Monitor
and flash notifications .
Answer Queue:
Answers to requests to other packages. Messages
for continued assistance.
Incoming Message Queue:
This consists of six subqueues, one for each precedence
level. Incoming messages for Message Service are
sent to this queue.
Outgoing Message Queue:
This queue consists of six subqueues, one for each
precedence level. Outgoing messages for Message
Service are sent to this queue.
Response Queue:
Offline Retrieval Results (placed in the queue
by SERT).
Retrieve Queue:
Retrieval Results (off-line and on-line) from SAR.
Fig. 4.1-4 MSO-Structure
4.1.5 V̲D̲U̲ ̲U̲S̲E̲R̲ ̲P̲a̲c̲k̲a̲g̲e̲
This package consists of two processes, one process
containing the software required to support the VDU
handling and one containing the software to control
the Preparation Database.
Overviews of these two processes are shown on fig.
4.1-5 and fig. 4.1-6.
4.1.5.1 V̲D̲U̲ ̲U̲S̲E̲R̲ ̲S̲u̲b̲p̲r̲o̲c̲e̲s̲s̲ ̲(̲V̲U̲S̲)̲
This consists of four subpackages (coroutines) ̲
a) VCO (USER V̲DU C̲o̲ntrol ) which reacts upon commands
from TEMCO and controls the other coroutines as
well as maintaining the VDU Header Status Area.
b) UFCO (U̲SER F̲unction C̲o̲ntrol) which reacts upon
commands from VCO, F/C keys from keyboard and input
from the Answer Queue, the Receive Queue, the Release
Queue and the Response Queue. It also receives
input from RETR and controls VDIA. It contains
all the functions for c̲o̲n̲t̲r̲o̲l̲ of the MMI and interfacing
to other packages as well as command execution.
c) VDIA (V̲DU D̲i̲a̲logue) which reacts upon commands
from UFCO and performs input and output to and
from the VDU Format Area and validation of input
data.
d) RETR (R̲e̲t̲r̲ieval) which receives answers from SAR
(messages or error codes) on request sent to SAR
from UFCO. It communicates on-line retrieval results
to UFCO and off-line retrieval results to UMAM.
Communication with other Packages (apart from Monitor
Calls) is done via queues. The VUS has six queues:
Command Queue:
Commands from TEMCO, timer events from Timer Monitor
and flash notification.
Answer Queue:
Answers to requests to other packages.
Receive Queue:
This consists of six subqueues, one for each precedence
level. Messages/comments for presentation at the
USER VDU are sent to this queue.
Release Queue:
Messages for release.
Response Queue:
Release Notifications, Off-line Retrieval Results
(placed in the queue by RETR), Off-line Append
Results and Deletion Notifications.
Retrieval Queue:
Retrieval Results (off-line and on-line from SAR).
4.1.5.2 U̲S̲E̲R̲ ̲M̲e̲s̲s̲a̲g̲e̲ ̲A̲c̲c̲e̲s̲s̲ ̲M̲o̲n̲i̲t̲o̲r̲i̲n̲g̲ ̲P̲r̲o̲c̲e̲s̲s̲ ̲(̲U̲M̲A̲M̲)̲
This consists of two subpackages (coroutines):
a) PAC (P̲reparation A̲ccess C̲ontrol) which reacts upon
SSC commands and controls the other coroutine.
It receives input from the Preparation Queue and
the Request Queue and controls all messages/comments
under preparation and their status changes.
b) USFM (U̲ser S̲tatus F̲ile M̲aintenance) which reacts
upon commands from PAC and performs the actual
access to the Preparation Database.
UMAM has two queues:
- Preparation Queue:
Messages/comments prepared are sent to this queue
from SVUP, MDOS, MSOS and VUS.
- Request Queue:
The following requests are sent to this queue:
- CMD's from SSC
- Outgoing Message Status Request
- Outgoing Service Message Status Request
- Delivery Status Request
- Release Status Request.
- Access state changes (e.g. "sent for release"
changes to "released").
Also access keys to messages to be appended are sent
to this queue by VUS.
Fig. 4.1-5 VUS Structure
Fig. 4.1-6 UMAM Structure
4.1.6 O̲C̲R̲ ̲P̲a̲c̲k̲a̲g̲e̲
This package consists of one process, ref. fig. 4.1-7.
The O̲C̲R̲ P̲rocess (OCP) consists of two subpackages (coroutines):
a) OCCO (O̲C̲R C̲O̲NTROL) which reacts upon commands from
SSC and control signals from the OCR (via IOC).
It controls the other coroutine.
b) OCIP (O̲C̲R I̲np̲ut) which reacts upon commands from
OCCO and receives input from the OCR and validates
it. The input is stored in a CIF and is automatically
released and sent to THP and possibly MDP.
OCP has one queue:
c) Command Queue:
Commands from SSC.
Fig. 4.1-7 OCP-Structure
4.1.7 U̲S̲E̲R̲ ̲P̲r̲i̲n̲t̲e̲r̲ ̲P̲a̲c̲k̲a̲g̲e̲
This package consists of one process, ref. fig. 4.1-8.
The USER P̲r̲i̲nt S̲ubprocess (PRIS) consists of two subpackages
(coroutines):
a) UPCO (U̲SER P̲rint C̲o̲ntrol) which reacts upon commands
from SSC and control signals from the Printer.
It receives items for print in the Print Queue
and flash notifications in the Command Queue. It
controls the other coroutine.
b) PROP (P̲r̲inter O̲utp̲ut) which reacts upon commands
from UPCO and performs the actual printing. The
format for printout is obtained from the P̲rint
F̲ormat F̲ile (PFF).
PRIS has two queues:
c) Command Queue:
Commands from SSC and flash notifications.
Print Queue:
Items for printout.
Fig. 4.1-8 PRIS-Structure
4.2 T̲E̲R̲M̲I̲N̲A̲L̲ ̲P̲A̲C̲K̲A̲G̲E̲ ̲I̲N̲T̲E̲R̲F̲A̲C̲E̲
4.2.1 E̲x̲t̲e̲r̲n̲a̲l̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲
All TEP external interfaces are described in:
CPS/230/ICD/001
CPS/230/ICD/002
CPS/230/ICD/008
4.2.2 P̲a̲c̲k̲a̲g̲e̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲s̲
All interfaces between TEP and other packages are described
in CPS/ICD/009.
4.2.3 I̲n̲t̲e̲r̲n̲a̲l̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲s̲
These are shown on fig. 4.2-1.
Fig. 4.2-1 TEP-Package Interfaces
(1) Messages and Comments for editing
Appended messages
Status
(2) Release Notifications
(3) Items for printing
(4) Messages for release
(5) Messages and Comments for editing
Appended messages
Status
(6) Service Messages for editing
Status
(7) Items for print
(8) Service Messages for editing
Status
(9) Items for print
(10) Prepared Service Messages
Status Requests
(11) Prepared Service Messages
Status Requests
(12) Prepared Messages and Comments
Status Change Information
Append requests
Status Requests
(13) Prepared Messages and Comments
Append Requests
Status Requests
(14) Prepared Service Messages
Status Requests
(15) Status for print at Supervisor Printer
(16) Deletion Requests
(17) Items for print at Supervisor Printer
System Info print requests
Table print requests
Queue length requests
(18) Items for print at Supervisor Printer
(19) Items for print at Report Printer
(20) Items for print at Log Printer
(21) Items for print at Statistics Printer
(22) Items for print at associated printer
(23) Queue length info
(24) Service Messages for editing
(25) Queue length info
(26) Queue length requests
