top - download
⟦7452581c5⟧ Wang Wps File
Length: 43217 (0xa8d1)
Types: Wang Wps File
Notes: CPS/SDS/001 ISSUE 1
Names: »0688A «
Derivation
└─⟦2d517f7c3⟧ Bits:30006011 8" Wang WCS floppy, CR 0046A
└─ ⟦this⟧ »0688A «
WangText
…0a……08……0a……09……0a……0e……0a…
…0a……07……09……86…1
…02… …02…
…02…
…02…CPS/SDS/001
…02…BBC/810227…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.13 TERMINAL PACKAGE .........................
579
5.13.1 Summary of Requirements ..............
579
5.13.1.1 Package Description ..............
590
5.13.1.2 Package Function .................
593
5.13.1.2.1 Activation/Deactivation ......
593
5.13.1.2.2 General Mapping of Function
onto Units ...................
594
5.13.1.2.3 Terminal Package Basic
Functions ....................
599
5.13.1.2.4 VDU - Terminal Manager .......
606
5.13.1.2.5 PRINT - Terminal Manager .....
606
5.13.1.2.6 PTR - Terminal Manager .......
606
5.13.1.2.7 PTP - Terminal Manager .......
606
5.13.1.2.8 OCR - Terminal Manager .......
606
5.13.1.2.9 Recovery Functions ...........
612
5.13.1.3 Package Control ..................
612
5.13.1.4 Characteristics ..................
612
5.13.1.5 Design and Construction ..........
612
5.13.1.6 Documentation ....................
612
5.13.2 Environment ..........................
613
5.13.2.1 External Interfaces ..............
613
5.13.2.2 Package Interfaces ...............
613
5.13.2.2.1 Traffic Handling .............
613
5.13.2.2.2 Distribution .................
618
5.13.2.2.3 Storage and Retrieval ........
624
5.13.2.2.4 Log and Accountability .......
630
5.13.2.2.5 Statistics ...................
636
5.13.2.2.6 SS&C .........................
639
5.13.2.2.7 Table Management .............
643
5.13 T̲E̲R̲M̲I̲N̲A̲L̲ ̲P̲A̲C̲K̲A̲G̲E̲
5.13.1 S̲u̲m̲m̲a̲r̲y̲ ̲o̲f̲ ̲R̲e̲q̲u̲i̲r̲e̲m̲e̲n̲t̲s̲
The Terminal Package constitutes the only means by
which users may get access to the services of the CAMPS
system. The devices TEP service are listed below:
- VDUs
- Printers
- PTR
- PTP
- OCR
a) V̲D̲U̲ ̲R̲e̲l̲a̲t̲e̲d̲ ̲R̲e̲q̲u̲i̲r̲e̲m̲e̲n̲t̲s̲
The following CAMPS functions are serviced by TEP:
- Supervisor Functions
- Message Distribution Control Functions
- Message Service Functions
- User Functions, i.e. Preparation, Reception,
and Release.
1) Supervisor Functions
The supervisor functions are the following
(ref. fig. 5.13.1-1):
Command Control
Device Control
User Profile Control
Security Control
Queue Control at Restart
Table Update
Abbreviated Service Message
Retrieval
ACP 127 parameter control
Message distribution control
Engineering function.
2) Message Distribution Control Functions
The MDCO functions are the following
(ref. fig. 5.13.1-2):
Local Distribution assignment
Alternative Distribution assignment
Redistribution
Figure 5.13.1-1
CAMPS Supervisor Functions
Figure 5.13.1-2…01…MDCO Function
3) Message Service Function
The MSO functions are the following
(ref. fig. 5.13.1-3):
Garble Correction
RI Assignment
Relay Determination
Operating Signals Assignment
Group Count Verification
4) Preparation Function (Ref. fig. 5.13.1-4)
Message/Comment preparation
Retrieval
Deletion
Reception of Messages for coordination
Reception of Comments
Reception of notifications of release
Status
5) Reception function (ref. fig. 5.13.1-4)
Reception of incoming messages
Reception of copies of outgoing messages
Status
6) Release function (ref. fig. 5.13.1-4)
Comment preparation and reception
Reception of messages for coordination
Release of messages sent for release decision
Status.
Figure 5.13.1-3…01…Message Service Function
Figure 5.13.1-4…01…User Functions
b) P̲r̲i̲n̲t̲e̲r̲ ̲R̲e̲l̲a̲t̲e̲d̲ ̲R̲e̲q̲u̲i̲r̲e̲m̲e̲n̲t̲s̲
Following message types can be printed out on a
printer:
- incoming messages
- outgoing messages/comments
- service messages
- status
- statistics
- reports
- log
- supervisory print
- notifications
c) P̲T̲R̲ ̲R̲e̲l̲a̲t̲e̲d̲ ̲R̲e̲q̲u̲i̲r̲e̲m̲e̲n̲t̲s̲
Entering of complete messages in ACP 127 format.
d) P̲T̲P̲ ̲R̲e̲l̲a̲t̲e̲d̲ ̲R̲e̲q̲u̲i̲r̲e̲m̲e̲n̲t̲s̲
Output complete messages in ACP 127 format.
e) O̲C̲R̲ ̲R̲e̲l̲a̲t̲e̲d̲ ̲R̲e̲q̲u̲i̲r̲e̲m̲e̲n̲t̲s̲
Entering of complete messages in format A.
f) I̲n̲f̲o̲r̲m̲a̲t̲i̲o̲n̲ ̲F̲l̲o̲w̲
In fig. 5.13.1-5 to 5.13.1-8 the message flow between
the functions implemented by the Terminal Package
and the other packages of CAMPS are depicted.
Figure 5.13.1-6…01…Message Flow for Terminal Type VDU
L̲e̲g̲e̲n̲d̲ ̲f̲o̲r̲ ̲f̲i̲g̲.̲ ̲5̲.̲1̲3̲.̲1̲-̲5̲ ̲o̲n̲ ̲p̲r̲e̲v̲i̲o̲u̲s̲ ̲p̲a̲g̲e̲
1 Messages rejected during ACP127 analysis, i.e.
messages for Message service.
2 Service messages prepared by supervisor and messages
for rerun
3 Service messages presented to supervisor
4 Messages to be redistributed
5 Message Distribution control, i.e. messages which
for some reason cannot be distributed automatically
by CAMPS
6 Messages released by the release officer
7 Notification of Release and comments
8 Messages for release decision, Messages for coordination
and comments
9 Messages sent for Release decision, Messages for
coordination and comments
10 Notification of Release, Messages for coordination
and comments.
11 Incoming messages and copies of outgoing messages
L̲e̲g̲e̲n̲d̲ ̲f̲o̲r̲ ̲f̲i̲g̲.̲ ̲5̲.̲1̲3̲.̲1̲-̲6̲ ̲o̲n̲ ̲p̲r̲e̲v̲i̲o̲u̲s̲ ̲p̲a̲g̲e̲
1 Storage of released message
2 Storage of initial version and release notifications
3 Message Retrieval, Append Message, Message Deletion
4 Storage of received version
5 Message retrieval for rerun and redistribution
6 Message retrieval for redistribution
Figure 5.13.1-7 og -8
5.13.1.1 P̲a̲c̲k̲a̲g̲e̲ ̲D̲e̲s̲c̲r̲i̲p̲t̲i̲o̲n̲
a) The Terminal Package performs the following tasks:
1) Interfaces the user of a terminal, i.e. VDU,
Printer, Teleprinter, PTR, PTP, OCR to the
CAMPS System.
2) Man/Machine IF support and monitoring.
3) Directs user input to the relevant package
within CAMPS, and presents to the user information
sent to a terminal.
b) For each device mentioned in 1) above, the Terminal
Package (TEP) implements a Terminal Manager.
c) The Terminal Manager consists of the following
units:
- Function Control
- Dialogue Control
- Validation
- Terminal IF Software
1) Function Control performs/initiates all interaction
with the various packages of CAMPS and controls
the transactions on the terminal.
2) Dialogue Control is responsible for the input/output
part of the Man/Machine interface support and
monitoring
3) Validation software has the task of validating
input related to a format.
4) Terminal IF Software constitutes the interface
to the I/O control software making a high level
interface against terminals for the rest of
the Terminal package.
d) The packages to which the Terminal System 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
e) The Terminal package interfaces with CAMPS VDU,
OCR and PTR/PTP users and thus the following external
interfaces apply.
1) Supervisor (ref. CPS/230/ICD/0002)
2) Message Distribution Control Operator (MDCO)
ref. CPS/230/ICD/0002)
3) Message Service Operator (MSO)
ref. CPS/230/ICD/0002)
4) Users (ref. CPS/230/ICD/0001)
5) OCR (ref. CPS/ICD/008)
6) PTR/PTP
7) Printer, Teleprinter
f) In fig. 5.13.1.1-1 an overview of the interfaces
of TEP are depicted.
Figure 5.13.1.1-1…01…Terminals: VDU, Printer, PTR, PTP, OCR
5.13.1.2 P̲a̲c̲k̲a̲g̲e̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲s̲
5.13.1.2.1 A̲c̲t̲i̲v̲a̲t̲i̲o̲n̲/̲D̲e̲a̲c̲t̲i̲v̲a̲t̲i̲o̲n̲
a) Each active terminal is serviced by a Terminal
Manager dedicated especially to that terminal.
The Terminal Manager is activated/deactivated by
the SS&C Package, Terminal Monitoring and Control.
b) The Terminal Manager of a VDU is activated by the
Terminal Monitoring and Control (SSC) with access
rights and information of hardware configuration
of the terminal position as determined by Terminal
Monitoring and Control. Activation occurs after
sign-on.
Access rights include:
1) The CAMPS functions which may be performed
by the user/supervisor at that terminal position,
and which may be one or more of the following:
- Supervisor Function
- MDCO Function
- MSO Function
- Release Function
- Reception Function
- Preparation Function
2) Each group of functions as listed in 1) above
further implies the access right to certain
queues and/or system tables.
The Terminal Manager may be deactivated by
the Terminal Monitoring and Control software
then withdrawing all access rights handed over
at the time of activation. Deactivation occurs
due to sign-off, key-off, Supervisor block
or invalid replies to security interrogations.
b) The Terminal Manager of a Stand Alone Device (Printer,
Teleprinter used as PTR/PTP, PTR, PTP, OCR) is
activated by the SS&C Package, when the terminal
device is opened by the Supervisor. For printers
equipped with locking mechanism, this will be in
the ON position too.
The Terminal Manager is activated with access rights
as determined by the SS&C Package.
Access rights include:
1) Formats and tables.
For printers addressable by SCDs, these are handed
over as well.
5.13.1.2.2 G̲e̲n̲e̲r̲a̲l̲ ̲M̲a̲p̲p̲i̲n̲g̲ ̲o̲f̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲s̲ ̲o̲n̲t̲o̲ ̲U̲n̲i̲t̲s̲
a) This section describes the principal tasks of each
of the Top Level Functions:
- Function Control
- Dialogue Control
- Validation
for each of the types of Terminal Manager:
- VDU - Terminal Manager
- PRINT - Terminal Manager
- PTR - Terminal Manager
- PTP - Terminal Manager
- OCR - Terminal Manager
- TP/PTR - Terminal Manager
- TP/PTP - Terminal Manager
b) The main functions recognized at this level are:
1) Transaction Handling:
Command interpretation, transaction accounting
and error response.
Fig. 5.13.1.2.2-1…01…Terminal Package Top Level Breakdown
2) Item Handling:
Operations on items and their control blocks.
3) Table Handling:
Access to tables, system parameters and global
number series.
4) Status, Log, and Statistics Handling:
Collection and maintenance of status log and
statistics information.
5) Queue and Request Handling:
Operations on queues and inter system communication
via requests/replies.
6) Start, Stop, and Error Handling:
Start up, restart, close down, and local error
handling.
7) Format Handling:
Input, output, and validation of data for terminals.
These functions are mapped onto the Top Level Functions
as follows:
c) VDU - Terminal Manager
The Terminal Managers for the various functions
(Supervisor, MDCO, MSO, User) will be different
with respect to commands and detailed functions
and thus inherently prevented from unauthorized
activities. The precise mapping of low level functions
onto Terminal Managers and their Top Level Functions
are beyond the scope of this document and will
be defined at a later stage in the design process.
1) Function Control.
The tasks of Function Control are:
- Transaction Handling
- Item Handling
- Table Handling
- Status, Log, and Statistics Handling
- Queue and Request Handling
- Start, Stop, and Error Handling
2) Dialogue Control.
The tasks of Dialogue Control are:
- Format Input/Output and Status display.
3) Validation.
The tasks of validation are:
- Format Validation and Conversion.
d) PRINT - Terminal Manager.
The Terminal Manager for print-out controls low
- and medium-speed printers.
1) Function Control.
The tasks of Function Control are:
- Table Handling
- Queue and Request Handling
- Start, Stop, and Error Handling
2) Dialogue Control.
The tasks of Dialogue Control are:
- Format output.
3) Validation.
- N/A.
e) PTR - Terminal Manager.
The Terminal Manager for paper tape input controls
stand alone PTR and teleprinters used as PTR device.
1) Function Control.
The tasks of Function Control are:
- Transaction Handling.
- Item Handling.
- Table Handling.
- Queue and Request Handling.
- Start, Stop, and Error Handling.
2) Dialogue Control.
The tasks of Dialogue Control are:
- Format Reception.
3) Validation.
The tasks of Validation are:
- Format Validation.
f) PTP - Terminal Manager.
The Terminal Manager for paper tape output controls
stand alone PTP and teleprinters used as PTP device.
1) Function Control.
The tasks of Function Control are:
- Table Handling
- Queue and Request Handling
- Start, Stop, and Error Handling
2) Dialogue Control.
The tasks of Dialogue Control are:
- Format Output.
3) Validation.
N/A.
g) OCR - Terminal Manager.
The Terminal Manager for document input controls
the stand alone OCR.
1) Function Control.
The tasks of Function Control are:
- Transaction Handling
- Item Handling
- Table Handling
- Queue and Request Handling
- Start, Stop, and Error Handling
2) Dialogue Control.
The tasks of Dialogue Control are:
- Format Reception.
3) Validation.
The tasks of Validation are:
- Format Validation and Conversion.
h) Terminal IF Software.
The Tasks of Terminal IF software are to implement
high level features for device access.
5.13.1.2.3 T̲e̲r̲m̲i̲n̲a̲l̲ ̲P̲a̲c̲k̲a̲g̲e̲ ̲B̲a̲s̲i̲c̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲s̲
The TEP is broken down, as mentioned in the previous
section, into Main Functions and these are further
broken down into Basic Functions as shown on fig. 5.13.1.2.3-1.
This figure shows a grouping of the Basic Functions
based upon their relation. The selection of the functions
required for construction of the individual Terminal
Managers is described later in this section.
The Basic Functions are:
a) Transaction Handling.
1) Interpret Command.
This function inputs and interprets the commands
from terminals and validates them against the
list of commands allowed for the particular
Terminal Manager.
Fig. 5.13.1.2.3-1…01…Terminal Package Basic Functional Breakdown
2) Create Transaction.
This function creates local work space and
data specific to the current transaction
3) Terminate Transaction.
This function frees local workspace and performs
"clean-up" when the current transaction is
finished.
4) Display Error Message.
This function converts the error codes to plain
text and displays this on the response line
on the VDU when requested.
b) Item Handling.
1) Create New Item.
This function creates (via the Message Monitor)
a new item (message, comment etc.), in Short
Term Storage ready for storing data in.
2) Create Next Version.
This function creates (via Message Monitor)
a new version of an already existing item.
3) Open Item.
This function gets (via Message Monitor) access
to an existing item in Short Term Storage.
4) Close Item.
This function terminates (via Message Monitor)
access to an item.
5) Update Item.
This function stores data (via Message Monitor)
in an item.
6) Send Item.
This function sends (via Message Monitor) an
item to one or more queues.
7) Delete item.
This function removes (via Message Monitor)
an item.
8) Inspect Control Block.
This function obtains (via Message Monitor)
information from the specified Control Block
(associated with an item).
9) Update Control Block.
This function updates (via Message Monitor),
the contents of the specified Control Block.
c) Table Handling.
1) Table Access.
This function operates on all tables controlled
by the Table Management Package.
2) System Parameter Access.
This function operates on all system parameters
controlled by the Table Management Package.
3) Global Number Series Access.
This function operates on all global number
series controlled by the Table Management Package.
d) Status, Log, and Statistics Handling.
1) Log.
This function generates the information to
be delivered to the Log & Accountability Package.
2) Statistics.
This function generates the information to
be delivered to the Statistics Package.
3) Status.
This function generates and maintains the status
information required by the TEP for response
to status requests.
4) VDU Status Update.
This function generates and maintains the status
information to be displayed in the VDU status
area.
e) Queue and Request Handling.
1) Look-up Q-Element.
This function obtains (via Queue Monitor) next
element in the specified queue.
2) Return Q-Element.
This function returns (via Queue Monitor) the
specified queue element to the queue from where
it originated.
3) Send Q-Element.
This function enters (via Queue Monitor) an
element into a specified queue.
4) Dismantle Q-Element.
This function removes (via Queue Monitor) an
element from a queue.
5) Auxiliary Queue Functions.
These functions deal with the remaining part
of the queue handling functions (defined in
Queue Monitor) applicable to TEP.
6) Send Request.
This function sends (via Queue Monitor) a request
to another package within CAMPS.
7) Send Reply.
This function delivers a reply (via Queue Monitor)
corresponding to a request received from another
package within CAMPS.
8) Receive Request.
This function waits for and receives (via Queue
Monitor) requests from other packages within
CAMPS.
9) Receive Reply.
This function waits for and receives (via Queue
Monitor) replies to requests sent to other
packages within CAMPS.
f) Start, Stop, and Error Handling.
1) Start-up.
This function is activated (by SSC) when an
instance of the Terminal Manager is created
and performs required initialisation.
2) Restart.
This function is activated (by SSC) when an
instance of the Terminal manager is created
following a system failure or switch-over to
standby PU.
3) Close Down.
This function is performed when a close down
operation is requested (by SSC).
4) Local Error Handling.
This function performs error actions for all
errors specified as local to TEP.
g) Format Handling.
1) Format Selection.
This function calls upon the Terminal IF Software
for access to the required format corresponding
to the type of terminal and the output operation
in question.
2) Format Completion.
This function hands over to the IO Control
Software data to be filled into the format
to be output.
3) Format Output.
This function calls upon the IO Control Software
for output of the specified format to the terminal
in question.
4) Format Reception.
This function receives from the IO Control
Software the contents of a format input from
a terminal.
5) Format Compare.
This function compares the contents of a format
sent to a terminal with the contents received
from the same terminal to identify changes
performed by the user.
6) Format Validation.
This function performs the syntax and semantic
validation of the contents of the format received.
7) Format Conversion.
This function performs the conversion of the
specified format to Internal Message Format.
8) Predefined Message Handling.
This function handles all operations on predefined
messages.
9) Status Display.
This function displays the current status in
the status area on the VDU.
5.13.1.2.4 V̲D̲U̲ ̲-̲ ̲T̲e̲r̲m̲i̲n̲a̲l̲ ̲M̲a̲n̲a̲g̲e̲r̲
The mapping of Basic Functions onto the Top Level Functions
for this Terminal Manager is shown on fig. 5.13.1.2.4-1.
5.13.1.2.5 P̲R̲I̲N̲T̲ ̲-̲ ̲T̲e̲r̲m̲i̲n̲a̲l̲ ̲M̲a̲n̲a̲g̲e̲r̲
The mapping of Basic functions onto the Top Level Functions
for this Terminal Manager is shown on fig. 5.13.1.2.5-1.
5.13.1.2.6 P̲T̲R̲ ̲-̲ ̲T̲e̲r̲m̲i̲n̲a̲l̲ ̲M̲a̲n̲a̲g̲e̲r̲
The mapping of Basic Functions onto the Top Level Functions
for this Terminal Manager is shown on fig. 5.13.1.2.6-1.
5.13.1.2.7 P̲T̲P̲ ̲-̲ ̲T̲e̲r̲m̲i̲n̲a̲l̲ ̲M̲a̲n̲a̲g̲e̲r̲
The mapping of Basic Functions onto the Top Level Functions
for this Terminal Manager is shown on fig. 5.13.1.2.7-1.
5.13.1.2.8 O̲C̲R̲ ̲-̲ ̲T̲e̲r̲m̲i̲n̲a̲l̲ ̲M̲a̲n̲a̲g̲e̲r̲
The mapping of Basic Functions onto the Top Level Functions
for this Terminal Manager is shown on fig. 5.13.1.2.8-1.
TERMINAL MANAGER…01…FIGS. 5.13.1.2.4-1/5-1/6-1/7-1/8-1
5.13.1.2.9 R̲e̲c̲o̲v̲e̲r̲y̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲s̲
When the Terminal Package is restarted by SS&C following
close down, switch-over or total system failure "recovery
required" is specified (by SS&C).
Relevant queues will then contain contents according
to last checkpoint and Terminal package will inspect
the queues to re-establish the system state.
For detailed recovery levels ref. sec. 4.7.
5.13.1.3 P̲a̲c̲k̲a̲g̲e̲ ̲C̲o̲n̲t̲r̲o̲l̲
TEP is as a whole controlled by the SS&C Software,
refer subsection 5.13.1.2.1.
The only parameters shared between TEP and other packages
are the System Parameters to which access is controlled
by the Table Management package.
Errors detected by TEP are reported to SS&C by means
of a queue mechanism. Errors of this kind will be
defined during detailed design.
5.13.1.4 C̲h̲a̲r̲a̲c̲t̲e̲r̲i̲s̲t̲i̲c̲s̲
Refer CPS/210/SYS/0001.
5.13.1.5 D̲e̲s̲i̲g̲n̲ ̲a̲n̲d̲ ̲C̲o̲n̲s̲t̲r̲u̲c̲t̲i̲o̲n̲
Refer section 2.5.
5.13.1.6 D̲o̲c̲u̲m̲e̲n̲t̲a̲t̲i̲o̲n̲
Refer section 2.6.
5.13.2 E̲n̲v̲i̲r̲o̲n̲m̲e̲n̲t̲
5.13.2.1 E̲x̲t̲e̲r̲n̲a̲l̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲s̲
User Procedures ref. doc. no. CPS/230/ICD/0001…02…MDCO
Procedures ref. doc. no. CPS/230/ICD/0002
Message Service Procedures ref. doc. no.
CPS/230/ICD/0002
Supervisor Commands and Procedures ref. doc. no.
CPS/230/ICD/0002
Optical Character Reader ref. doc no.
CPS/ICD/008
PTR/PTP
5.13.2.2 P̲a̲c̲k̲a̲g̲e̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲s̲
In the following sections, the interfaces of the Terminal
Package to other packages are described.
Each section describes the interface to one package
and contains for each terminal type (VDU, Printer,
PTR, PTP, OCR) the interface between the Terminal Manager
of the device type and the Package.
For VDUs the interface is further described per CAMPS
function, i.e. Supervisor Function, Message Distribution
Control Function, Message Service Function, User Functions.
It should however, be understood that for each active
VDU terminal, an interface of the described type exists,
i.e. if two MDCOs are signed-on, two instances of MDCO
interfaces exist, one for each MDCO terminal position.
Further, if a terminal position has access to two
or more CAMPS functions, that terminal position or
instance of the Terminal Package will have all the
interfaces described for the CAMPS functions to which
access is granted.
5.13.2.2.1 T̲r̲a̲f̲f̲i̲c̲ ̲H̲a̲n̲d̲l̲i̲n̲g̲ ̲(̲T̲H̲P̲)̲
The Traffic Handling Package performs analysis of incoming
and outgoing messages, as well as routing of outgoing
messages.
5.13.2.2.1.1 V̲D̲U̲ ̲-̲ ̲T̲e̲r̲m̲i̲n̲a̲l̲ ̲M̲a̲n̲a̲g̲e̲r̲
a) S̲u̲p̲e̲r̲v̲i̲s̲o̲r̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲
Abbreviated Service Messages prepared by the Supervisor
are queued by TEP in the Traffic Handling Package
queue for outgoing service messages.
Outgoing Messages retrieved for rerun by the Supervisor
are queued by TEP in the Traffic Handling Package
queue for outgoing messages.
Incoming Service Messages which shall be presented
to the Supervisor are queued by the Traffic Handling
Package in the supervisor's queue for service messages.
Security reports, warning reports, and channel
reports for print-out at the printer(s) associated
the supervisor VDU are placed in the supervisor's
queue for reports by the Traffic Handling Package.
Refer fig. 5.13.2.2.1-1.
b) M̲e̲s̲s̲a̲g̲e̲ ̲D̲i̲s̲t̲r̲i̲b̲u̲t̲i̲o̲n̲ ̲C̲o̲n̲t̲r̲o̲l̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲
No interface to Traffic Handling.
c) M̲e̲s̲s̲a̲g̲e̲ ̲S̲e̲r̲v̲i̲c̲e̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲
Incoming and outgoing Messages, which are not automatically
accepted by Traffic Handling are queued for Message
Service, in the incoming respective outgoing message
service queues.
TEP places the message in the Traffic Handling
Package queue for messages having been to Message
Service. Refer fig. 5.13.2.2.1-2.
d) U̲s̲e̲r̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲s̲
When the Release Officer releases a message, TEP
places the message in the Message Routing Queue
(MRQ) of the Traffic Handling Package.
Refer fig. 5.13.2.2.1-3.
Figs. 5.13.2.2.1-1/2/3
5.13.2.2.1.2 P̲r̲i̲n̲t̲e̲r̲ ̲-̲ ̲T̲e̲r̲m̲i̲n̲a̲l̲ ̲M̲a̲n̲a̲g̲e̲r̲
No interface to Traffic Handling.
5.13.2.2.1.3 P̲T̲R̲ ̲-̲ ̲T̲e̲r̲m̲i̲n̲a̲l̲ ̲M̲a̲n̲a̲g̲e̲r̲
ACP127 messages received by the Terminal Manager from
a PTR are placed in the Message Routing Queue (MRQ)
of the Traffic Handling Package for routing assignment.
5.13.2.2.1.4 P̲T̲P̲ ̲-̲ ̲T̲e̲r̲m̲i̲n̲a̲l̲ ̲M̲a̲n̲a̲g̲e̲r̲
When the Traffic Handling Package detects an outgoing
message, which shall be output on the PTP, the Traffic
Handling Package queues the message to the PTP.
5.13.2.2.1.5 O̲C̲R̲ ̲-̲ ̲T̲e̲r̲m̲i̲n̲a̲l̲ ̲M̲a̲n̲a̲g̲e̲r̲
Messages received in format A from the OCR - Terminal
Manager are placed in the Message Routing Queue (MRQ)
of the Traffic Handling Package for Routing assignment
and ACP127 conversion.
5.13.2.2.2 D̲i̲s̲t̲r̲i̲b̲u̲t̲i̲o̲n̲ ̲(̲M̲D̲P̲)̲
The Distribution Package is responsible for internal
distribution of information.
5.13.2.2.2.1 V̲D̲U̲ ̲-̲ ̲T̲e̲r̲m̲i̲n̲a̲l̲ ̲M̲a̲n̲a̲g̲e̲r̲
a) S̲u̲p̲e̲r̲v̲i̲s̲o̲r̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲
When the Supervisor retrieves an incoming or released
message for internal re-distribution, the message
is placed by TEP in the Distribution Packages queue
assigned to this purpose.
Refer fig. 5.13.2.2.2-1.
Figure 5.13.2.2.2-1
b) M̲D̲C̲O̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲
Incoming messages for which distribution cannot
be determined by the Distribution Package are queued
to TEP in the MDCO queue.
Distribution instructions to the Distribution Package
leading to delivery of information to a terminal
position not active are delivered in this queue
as well.
The decision for distribution made by the MDCO
is communicated to the Distribution Package, which
if the ordered distribution cannot be executed,
returns the message to the MDCO.
The MDCO may retrieve messages for distribution.
Such messages are by TEP queued for the Distribution
Package in the appropriate queue.
The information which the MDCO requests to be printed
is queued to the Distribution Package for queuing
to the printer associated the MDCO VDU.
Refer fig. 5.13.2.2.2-2.
b) M̲e̲s̲s̲a̲g̲e̲ ̲S̲e̲r̲v̲i̲c̲e̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲
The information for which the MSO request a print-out
at his own printer are queued to the Distribution
Package for queuing to the printer associated with
the MSO VDU.
Incoming messages for which the MSO requests print-out
at terminal positions allocated to specified Staff
Cells are queued to the Distribution Package.
Fig. 5.13.2.2.2-2
d) U̲s̲e̲r̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲s̲
TEP queues messages for coordination, messages
for release, comments, and release notifications
to be distributed to the Distribution Package.
Information for which the user requests a print-out
is queued to the Distribution Package for queuing
to the shared printer associated with the user
VDU.
The Distribution Package queues information addressed
to a user position in the Receive Queue and messages
for release in the Release Officers Release Queue
(RLQ) in accordance with the precedence of the
delivered information.
The precedence levels of the queues are SUPER FLASH,
FLASH, IMMEDIATE, SUPER PRIORITY, PRIORITY, and
ROUTINE.
Figure 5.13.2.2.2-3
5.13.2.2.2.2 P̲r̲i̲n̲t̲e̲r̲ ̲-̲ ̲T̲e̲r̲m̲i̲n̲a̲l̲ ̲M̲a̲n̲a̲g̲e̲r̲
The Distribution Package queues information addressed,
either by SCD or device designator, to the printer
position in the queue of the Printer Terminal Manager
in accordance with the precedence of the delivered
information.
5.13.2.2.2.3 P̲T̲R̲ ̲-̲ ̲T̲e̲r̲m̲i̲n̲a̲l̲ ̲M̲a̲n̲a̲g̲e̲r̲
NA
5.13.2.2.2.4 P̲T̲P̲ ̲-̲ ̲T̲e̲r̲m̲i̲n̲a̲l̲ ̲M̲a̲n̲a̲g̲e̲r̲
Messages for which the supervisor has specified output
on PTP are queued by the Distribution Package in the
PTP Terminal Manager queue.
5.13.2.2.2.5 O̲C̲R̲ ̲-̲ ̲T̲e̲r̲m̲i̲n̲a̲l̲ ̲M̲a̲n̲a̲g̲e̲r̲
NA
5.13.2.2.3 S̲t̲o̲r̲a̲g̲e̲ ̲a̲n̲d̲ ̲R̲e̲t̲r̲i̲e̲v̲a̲l̲ ̲(̲S̲A̲R̲)̲
The Storage and Retrieval Package handles the storage/retrieval
of all items of information, which are stored on long
term storage.
5.13.2.2.3.1 V̲D̲U̲ ̲-̲ ̲T̲e̲r̲m̲i̲n̲a̲l̲ ̲M̲a̲n̲a̲g̲e̲r̲
a) S̲u̲p̲e̲r̲v̲i̲s̲o̲r̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲
Supervisor retrieve requests are by TEP inserted
in the SAR retrieve request queue. When the SAR
Package has processed the request, the result is
placed in the Terminal Package supervisor queue
for delivery.
When the Supervisor has requested a disk dismount,
this is reported to SFM and to SAR via the SAR
request queue. This request is acknowledged by
SAR by queuing an acknowledge in the proper queue.
When the Supervisor has performed a disk mount
this is communicated to SFM and to SAR by the Terminal
Manager.
Dump activities commanded or acknowledged by the
supervisor are communicated to the SAR by the Terminal
Manager.
Reports, mount request reports, dump request reports
for print-out at the printer(s) associated the
supervisor VDU are placed in the Terminal Package
queue for reports by SAR.
Refer fig. 5.13.2.2.3-1.
Figure 5.13.2.2.3-1
b) M̲e̲s̲s̲a̲g̲e̲ ̲D̲i̲s̲t̲r̲i̲b̲u̲t̲i̲o̲n̲ ̲C̲o̲n̲t̲r̲o̲l̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲
When the MDCO wants to retrieve a message, TEP
inserts the retrieve request in the SAR Packages
retrieve request queue. SAR inserts the result
of the processing of the request in the MDCO delivery
queue.
Refer fig. 5.13.2.2.3-2.
c) M̲e̲s̲s̲a̲g̲e̲ ̲S̲e̲r̲v̲i̲c̲e̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲
No interface to SAR.
d) U̲s̲e̲r̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲s̲
When a user issues a retrieval or message append
request, TEP inserts the request in SAR retrieval
request queue.
When SAR has processed the request, it inserts
the result of it in the Terminal Package delivery
queue.
When a user Terminal Manager detects a transaction
(An initial version of a message, a message released,
a comment transmitted) which results in information
being stored, the Terminal Manager reports the
retrieval keys and information to SAR.
Refer fig. 5.13.2.2.3-3.
5.13.2.2.3.2 P̲r̲i̲n̲t̲e̲r̲ ̲-̲ ̲T̲e̲r̲m̲i̲n̲a̲l̲ ̲M̲a̲n̲a̲g̲e̲r̲
No interface to SAR.
5.13.2.2.3.3 P̲T̲R̲ ̲-̲ ̲T̲e̲r̲m̲i̲n̲a̲l̲ ̲M̲a̲n̲a̲g̲e̲r̲
Messages received from the PTR are automatically
released by the Terminal Manager.
The Terminal Manager reports the retrieval key
of the message automatically released to SAR.
Figure 5.13.2.2.3-2
Figure 5.13.2.2.3-3
5.13.2.2.3.4 P̲T̲P̲ ̲-̲ ̲T̲e̲r̲m̲i̲n̲a̲l̲ ̲M̲a̲n̲a̲g̲e̲r̲
No interface to SAR.
5.13.2.2.3.5 O̲C̲R̲ ̲-̲ ̲T̲e̲r̲m̲i̲n̲a̲l̲ ̲M̲a̲n̲a̲g̲e̲r̲
Messages received from the OCR are released automatically
by the Terminal Manager. The retrieval keys of the
message are reported to SAR.
5.13.2.2.4 L̲o̲g̲ ̲a̲n̲d̲ ̲A̲c̲c̲o̲u̲n̲t̲a̲b̲i̲l̲i̲t̲y̲ ̲P̲a̲c̲k̲a̲g̲e̲ ̲(̲L̲O̲G̲)̲
The Log and Accountability Package collects log records
reported from various package and stores them on disk.
Upon request from the Supervisor trace of log is performed
by the Log and Accountability Package.
5.13.2.2.4.1 V̲D̲U̲ ̲-̲ ̲T̲e̲r̲m̲i̲n̲a̲l̲ ̲M̲a̲n̲a̲g̲e̲r̲
a) S̲u̲p̲e̲r̲v̲i̲s̲o̲r̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲
Log records of Supervisor activities are communicated
to the Log and Accountability Package through CAMPS
System Functions.
The Log and Accountability Package queues log records
to TEP for print-out at the supervisor's terminal
as they arrive.
The supervisor may request various traces of log
records. The Terminal Package queues such requests
in the request queue of the Log and Accountability
Package.
When the Log and Accountability Package has traced
the requested log records, they are placed in the
Supervisor's queue for traced log. Then the Log
and Accountability package places a command completion
code in the Terminal Package queue assigned to
this purpose, so that TEP can generate a command
completion report. Warning reports are placed
in the warning queue by Log and Accountability
Package. Refer fig. 5.13.2.2.4-1.
Fig. 15.13.2.2.4-1
b) M̲e̲s̲s̲a̲g̲e̲ ̲D̲i̲s̲t̲r̲i̲b̲u̲t̲i̲o̲n̲ ̲C̲o̲n̲t̲r̲o̲l̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲
Log records of MDCO activities are communicated
to the Log and Accountability Package through CAMPS
System Functions.
Refer fig. 5.13.2.2.4-2.
c) M̲e̲s̲s̲a̲g̲e̲ ̲S̲e̲r̲v̲i̲c̲e̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲
Log records of MSO activities are communicated
to the Log and Accountability Package through CAMPS
System Functions.
Refer fig. 5.13.2.2.4-3.
d) U̲s̲e̲r̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲s̲
Log records of user activities are communicated
by the Terminal Package to the Log and Accountability
Package through CAMPS System Functions.
Refer fig. 5.13.2.2.4-4.
5.13.2.2.4.2 P̲r̲i̲n̲t̲e̲r̲ ̲-̲ ̲T̲e̲r̲m̲i̲n̲a̲l̲ ̲M̲a̲n̲a̲g̲e̲r̲
Log records of information distributed by SCD to a
printer are communicated by the Terminal Package to
the Log and Accountability Package through CAMPS System
Functions.
5.13.2.2.4.3 P̲T̲R̲ ̲-̲ ̲T̲e̲r̲m̲i̲n̲a̲l̲ ̲M̲a̲n̲a̲g̲e̲r̲
No interface to log and accountability.
5.13.2.2.4.4 P̲T̲P̲ ̲-̲ ̲T̲e̲r̲m̲i̲n̲a̲l̲ ̲M̲a̲n̲a̲g̲e̲r̲
No interface to log and accountability.
5.13.2.2.4.5 O̲C̲R̲ ̲-̲ ̲T̲e̲r̲m̲i̲n̲a̲l̲ ̲M̲a̲n̲a̲g̲e̲r̲
No interface to log and accountability.
Figure 5.13.2.2.4-2
5.13.2.2.5 S̲t̲a̲t̲i̲s̲t̲i̲c̲s̲ ̲(̲S̲T̲P̲)̲
The Statistics Package collects statistical information
from many packages and makes statistics based on the
collected information. The Statistics Package extracts
on request from the supervisor specified statistics
and queues them in the supervisor's statistics print
queue.
5.13.2.2.5.1 V̲D̲U̲ ̲-̲ ̲T̲e̲r̲m̲i̲n̲a̲l̲ ̲M̲a̲n̲a̲g̲e̲r̲
a) S̲u̲p̲e̲r̲v̲i̲s̲o̲r̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲
No statistics information flows from the Terminal
Package to the Statistics Package.
The Terminal Package requests statistics from the
Statistics Package by giving a command to the Statistics
Package.
When the Statistics Package has retrieved the commanded
statistics, it queues it in the TEP statistics
print queue. Then the Statistics queues a command
completion code in the supervisor queue dedicated
to this purpose so TEP can generate a command completion
report.
Refer fig. 5.13.2.2.5-1.
b) M̲e̲s̲s̲a̲g̲e̲ ̲D̲i̲s̲t̲r̲i̲b̲u̲t̲i̲o̲n̲ ̲C̲o̲n̲t̲r̲o̲l̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲
No interface to Statistics.
c) M̲e̲s̲s̲a̲g̲e̲ ̲S̲e̲r̲v̲i̲c̲e̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲
No interface to Statistics.
d) U̲s̲e̲r̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲s̲
The Terminal Package collects statistics information
on user formats and communicates such statistics
records to the Statistics Package by invoking the
appropriate CAMPS system function.
Refer fig. 5.13.2.2.5-2.
Figure 5.13.2.2.5-1
Figure 5.13.2.2.5-2
5.13.2.2.5.2 P̲r̲i̲n̲t̲e̲r̲ ̲-̲ ̲T̲e̲r̲m̲i̲n̲a̲l̲ ̲M̲a̲n̲a̲g̲e̲r̲
The Terminal Manager collects statistics information
on formats distributed on SCDs to the printer and communicates
such statistics records to the Statistics Package by
invoking the appropriate CAMPS System Function.
5.13.2.2.5.3 P̲T̲R̲ ̲-̲ ̲T̲e̲r̲m̲i̲n̲a̲l̲ ̲M̲a̲n̲a̲g̲e̲r̲
No interface to Statistics.
5.13.2.2.5.4 P̲T̲P̲ ̲-̲ ̲T̲e̲r̲m̲i̲n̲a̲l̲ ̲M̲a̲n̲a̲g̲e̲r̲
No interface to Statistics.
5.13.2.2.5.5 O̲C̲R̲ ̲-̲ ̲T̲e̲r̲m̲i̲n̲a̲l̲ ̲M̲a̲n̲a̲g̲e̲r̲
No interface to Statistics.
5.13.2.2.6 S̲S̲C̲ ̲P̲a̲c̲k̲a̲g̲e̲
The SSC software monitors and controls the CAMPS system,
hardware as well as software. The SSC software acts
as operating system.
The SSC software initializes an instance of the Terminal
Package (Terminal Manager) each time the state of a
terminal changes from Unmanned to Manned/Attended.
The instance, i.e. type of Terminal Manager, activated
is device dependent.
5.13.2.2.6.1 V̲D̲U̲ ̲-̲ ̲T̲e̲r̲m̲i̲n̲a̲l̲ ̲M̲a̲n̲a̲g̲e̲r̲
For VDUs, the initialization procedure is similar for
all CAMPS functions, except that the supervisor function
is not handed over before the ASSIGN command has been
issued.
The Terminal Package is initiated with information
about the access rights determined by the SSC Package
and include:
- CAMPS functions which may be accessed by the user
from the given terminal position.
- System tables which may be accessed.
The interface to the SSC software further covers the
following special areas:
a) Error Reporting.
Errors that cannot be handled by the Terminal Package
are reported to SSC and appropriate action taken
here. Control will be returned from SSC in the
cases where continued operation is possible, otherwise
switchover or restart will be performed.
b) Ordered close-down.
When a close-down command is received from SSC
the following actions are taken:
1) Warning sent to all manned terminals specifying
when close-down will take place.
2) Commands are ignored when current activities
are completed and all flash messages have been
displayed.
3) Suspension of transactions still active at
terminals when warning time has elapsed.
4) Notify SSC that close-down actions are complete.
c) S̲u̲p̲e̲r̲v̲i̲s̲o̲r̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲
The supervisor may issue some commands to the SSC
Package, such as integrity check, change profile
(external channel, terminal, user). Such commands
are by TEP inserted in the command queue of the
SSC Package.
When the SSC Package has executed a command, it
places a command completion code in TEP queue assigned
to this purpose, so TEP can generate a command
completion report.
Reports for the supervisor generated by the SSC
Package (e.g. system integrity check unsuccessfull)
are placed in TEP queue for supervisor reports.
Refer fig. 5.13.2.2.6-1.
d) M̲D̲C̲O̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲
No special interface.
e) M̲e̲s̲s̲a̲g̲e̲ ̲S̲e̲r̲v̲i̲c̲e̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲
No special interface.
f) U̲s̲e̲r̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲
No special interface.
5.13.2.2.6.2 S̲t̲a̲n̲d̲ ̲A̲l̲o̲n̲e̲ ̲D̲e̲v̲i̲c̲e̲s̲ ̲-̲ ̲T̲e̲r̲m̲i̲n̲a̲l̲ ̲M̲a̲n̲a̲g̲e̲r̲s̲
No special interfaces to the SSC Package exist.
Fig. 5.13.2.2.6-1
5.13.2.2.7 T̲a̲b̲l̲e̲ ̲M̲a̲n̲a̲g̲e̲m̲e̲n̲t̲ ̲P̲a̲c̲k̲a̲g̲e̲ ̲(̲T̲M̲P̲)̲
TMP provides access to tables, global number series
and system parameters and validates update-requests
to these as well as ensuring continuity and integrity
in case of system failures. Back-up/reload facilities
are also supplied. The tables accessed by TEP include:
AIG
PLA
RI
CH
SDL
SCD
SIC
Command Control Tables
MDCO Control Tables
Term. prof. (read via TMP, update via SSC)
User. prof. (read via TMP, update via SSC)
Global no. series:
Document control no.
Transaction serial no.
Release serial no.
Report print no.
System Parameters:
5.13.2.2.7.1 V̲D̲U̲ ̲-̲ ̲T̲e̲r̲m̲i̲n̲a̲l̲ ̲M̲a̲n̲a̲g̲e̲r̲
a) S̲u̲p̲e̲r̲v̲i̲s̲o̲r̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲
In addition to the supervisor facilities for read
and update implemented as commands, the Terminal
Package reads the relevant tables, numbers, and
system parameters required for its functions.
b) M̲D̲C̲O̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲
No interface to TMP.
Figure 5.13.2.2.7-1
c) M̲S̲O̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲
No interface to TMP.
d) U̲s̲e̲r̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲s̲
Increments the transaction serial no.
After release TMP increments the release serial
no.
During validation of user entries tables are read
by TEP.
5.13.2.2.7.2 P̲r̲i̲n̲t̲e̲r̲s̲ ̲-̲ ̲T̲e̲r̲m̲i̲n̲a̲l̲ ̲M̲a̲n̲a̲g̲e̲r̲
Increments document control no.
5.13.2.2.7.3 P̲T̲R̲ ̲-̲ ̲T̲e̲r̲m̲i̲n̲a̲l̲ ̲M̲a̲n̲a̲g̲e̲r̲
Increments release serial no.
5.13.2.2.7.4 P̲T̲P̲ ̲-̲ ̲T̲e̲r̲m̲i̲n̲a̲l̲ ̲M̲a̲n̲a̲g̲e̲r̲
Increments document control no.
5.13.2.2.7.5 O̲C̲R̲ ̲-̲ ̲T̲e̲r̲m̲i̲n̲a̲l̲ ̲M̲a̲n̲a̲g̲e̲r̲
Increments release serial no.
