top - download
⟦6b35f74e5⟧ Wang Wps File
Length: 39570 (0x9a92)
Types: Wang Wps File
Notes: Spelunked
Names: »~ORPHAN73.00«
Derivation
└─⟦6f17b967f⟧ Bits:30006000 8" Wang WCS floppy, CR 0035A
└─ ⟦this⟧ »~ORPHAN73.00«
WangText
H…0b…H…0e…H…02…H…05…H…07…G…08…G…0d…G…0f…D D…07…C…08…C…0d…C
B…0a…B…00…B…02…B
B A…0a…A…01…A…02…A…86…1
…02…
…02…
…02…
…02…CPS/SDS/001
…02…MSN/810115…02……02…
CAMPS
SYSTEM
DESIGN
SPECIFICATION
…02……02…CAMPS
T̲A̲B̲L̲E̲ ̲O̲F̲ ̲C̲O̲N̲T̲E̲N̲T̲S̲
…02……02…5.13 TERMINAL SYSTEM .........................
…02……02……02…5.13.1 Summary of Requirements ............
…02……02……02……02…5.13.1.1 Subsystem Description ...........
…02……02……02……02…5.13.1.2 Subsystem Function ..............
…02……02……02……02……02…5.13.1.2.1 Activation/Deactivation .....
…02……02……02……02……02…5.13.1.2.2 General Mapping of Function
…02……02……02……02……02……02……02……02……02……02… into Units ..................
…02……02……02……02……02…5.131.2.3 Function Manager - Supervisor
…02……02……02……02……02… Functions ...................
…02……02……02……02……02…5.13.1.2.4 Dialogue Manager - Supervisor
…02……02……02……02……02… Function ....................
…02……02……02……02……02…5.13.1.2.5 Print/Display Manager -
Supervisor Fnction .........
…02……02……02……02……02…5.13.1.2.6 Function Manager - MDCO
…02……02……02……02……02… Function ....................
…02……02……02……02……02…5.13.1.2.7 Dialogue Manager - MDCO
…02……02……02……02……02… Function ....................
…02……02……02……02……02…5.13.1.2.8 Print/Display Manager - MDCO
…02……02……02……02……02… Function ....................
…02……02……02……02……02…5.13.1.2.9 Function Manager - MSO
…02……02……02……02……02… Function .....................
…02……02……02……02……02…5.13.1.2.10 Dialogue Manager - MSO
…02……02……02……02……02… Function .....................
…02……02……02……02……02…5.13.1.2.11 Print/DisplayManager
…02……02……02……02……02… MSO Function .................
…02……02……02……02……02…5.13.1.2.12 Function Manager - User
…02……02……02……02……02… Functions ....................
…02……02……02……02……02…5.13.1.2.13 Dialogue Manager - User
…02……02……02……02……02… Functions ....................
…02……02……02……02……02…5.13.1.2.4 Print/Display Manager - User
…02……02……02……02……02… Functions
…02……02……02……02……02…5.13.1.2.15 Recovery Functions ...........
…02……02……02……02……02…5.13.1.2.16 Special Devices ..............
…02……02……02……02…5.13.1.3 Subsystem Control ................
…02……02……02……02…5.13.1.4 Characteristics .................
…02……02……02……02…5.13.1.5 Design and Construction ..........
…02……02……02……02…5.13.1.6 Documentation ....................
…02……02……02…5.13.2 Environment ..........................
…02……02……02……02…5.13.2.1 External Interfaces ..............
…02……02……02……02…5.13.2.2 Subsystem Interfaces .............
…02……02……02……02……02…5.13.2.2.1 Traffic Handlin .............
…02……02……02……02……02…5.13.2.2.2 Distribution .................
…02……02……02……02……02…5.13.2.2.3 Storage and Retrieval ........
…02……02……02……02……02…5.13.2.2.4 Logging ......................
…02……02……02……02……02…5.13.2.2.5 Statistic ....................
…02……02……02……02……02…5.13.2.2.6 SS&C ........................
…02……02……02……02……02…5.13.2.2.7 Table Management .............
5.13…02…T̲E̲R̲M̲I̲N̲A̲L̲ ̲S̲Y̲S̲T̲E̲M̲
5.13.1…02…S̲u̲m̲m̲a̲r̲y̲ ̲o̲f̲ ̲R̲e̲q̲u̲i̲r̲e̲m̲e̲n̲t̲s̲
a) The Terminal System constitutes the only means
by which users may get access to the services of
the CAMPS system. The srvices in question are
listed below:
- Supervisor Functions
- Message Distribution Control Functions
- Message Service Functions
- User Functions, i.e. Preparation, Reception
and Release.
1) Supervisor Function
Command Control
Device Control
User Profile Update
Security Control
Access Control at Restart
Table Update
Abbreviated Service Message
Queue Access
Retrieval
ACP 127 parameter control
Message distribution control
Engineerin function.
2) Message Distribution Control Function
Local Distribution assignment
Alternative Distribution assignment
Redistribution
Message Service Function
Garble Corrction
RI Assignment
Relay Determination
Operating Signals Assignment
Group Count Verification
3) Preparation Function
Message/Comment preparation
Retrieval
Deletion
Reception of Mesages for coordination
Recepton of Comments
Reception of notifications of release
Status
4) Reception function
Reception of incoming messages
Reception of copies of outgoing messages
Status
5) Release function
Comment preparation and reception
Reception of messages for coordination
Release of messages sent for release decision
Status.
b) In fig. 5.3.1-1 the information flow between the
CAMPS functions implemented by the Terminal package
and the other packages of CAMPS is depicted.…86…1
…02… …02… …02… …02…
Fig. 5.13.1-1 Terminal System…86…1 …02… …02… …02… …02…
L̲e̲g̲e̲n̲d̲ ̲f̲o̲r̲ ̲f̲i̲g̲.̲ ̲5̲.̲1̲3̲.̲1̲-̲1̲ ̲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 messagesfor
rerun
3 Service messages presented to supervisor
4 Message retrieval for rerun, Message retrieval
for redistribution
5 Messages to be redistributed
6 Message retrieval for redistribution
7 Message Distribution control, i.e. messages wich
for some reason cannot be distributed automatically
by CAMPS
8 Messages released by the release officer
9 Notification of Release and comments
10 Messages for release decision, Messages for coordination
and comments
11 Message Retrieval Message Merge, Message Deletion
12 Messages sent for Release decision, Messages for
coordination and comments
13 Notification of Release, Messages for coordination
and comments.
14 Incoming messages and copies of outgoing messages
15 Transction status report and Release Status
16 Log of transactions for respective Release, Preparation
and Reception
17 Transaction status report and Message status
18 Transaction status report
19 Statistics information delivery for respectively
Release, Preparation and Reception.
20 Log of transactions for respectively Message Service,
Supervisor and MDCO
21 Trace o Log
22 Statistics delivery…86…1 …02… …02… …02… …02…
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 to the CAMPS System, i.e.
direct user input to the relevant subsystemwithin
CAMPS. Presents to the user information sent
by CAMPS to a terminal position.
2) Man/Machine IF Support and monitoring.
b) TEP consists of the following units
- Function Manager
- Dialogue Manager
- Print/Display Manager
- erminal IF Software
1) The Function Manager performs/initiates all
interaction with the various packages of CAMPS
and schedules the tasks of the Print/Display
Manager and the Dialogue Manager.
2) The Dialogue Manager is responsible for the
ineractive part of the Man/Machine interface
support and monitoring
3) The Print/Display Manager is responsible for
the man interactive part of the Man/Machine
interface support and monitoring.
4) Terminal IF Software constitutes the interface
o the I/O control software making a high level
interface against terminals for the rest of
the Terminal package.
c) 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 package
5) SS&C software
6) Traffic Handling
7) Distribution
8) Table Management
9) Storage and Retrieal
10) Log and Accountability
11) Statistics
d) The Terminal package interfaces with CAMPS users
and thus the following external interfaces apply.
1) Supervisor (ref. CPS/ICD/002)
2) Message Distribution Control Operator (MDCO)
rer CPS/ICD/002)-
3) Message Service Operator (MSO)
ref. CPS/ICD/002)
4) Users (ref. CPS/ICD/001)
e) In fig. 5.13.1.1-1 an overview of the interfaces
of TEP are depicted.…86…1 …02… …02… …02… …02…
Fig. 5.13.1.1-1
Operators: Supervisor, MDCO, MSO, Users…86…1 …02… …02… …02… …02…
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 manned terminal position is serviced by a
Function Manager, Dialogue Manager, and a Print/Display
Managerdedicated exclusively to that terminal position.
b) The three Managers are activated by the SS&C software,
Terminal monitoring and control, and are activated
with access rights and information of hardware
configuration of the terminal position asdetermined
by Terminal monitoring and control.
c) Access rights include which CAMPS functions may
be performed by the operator at that terminal position,
and which may be one or more of the following
1) Supervisor Functions
2) MDCO Function
3) MSO Functions
4) Release Functions
5) Reception Functions
6) Preparation Functions
d) Each of the above groups of functions further implies
the access right to certain queues and/or system
tables.
e) The three Managers may be dectivated by the Terminal
Monitoring and Control software then withdrawing
all access rights handed over at the time of activation.
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̲ ̲U̲n̲i̲t̲s̲
a) This section describes the tasks of each unit in
the Terminal System in general, i.e. independent
of supplied access rights toCAMPS functions.
b) Functions Manager.
The tasks of the Function Manager are the following:
- Command interpretion, initiation and termination.
- Delivery queuing and scheduling.
- Log/statistics functions.
- Terminal Status functios.
1) Command interpretation, initiation and termination.
Commands received by the Function Manager
are analysed to an extent necessary to determine
whether a function requiring a dialogue is
to be performed, or information accessible
are wante to be displayed/printed.
In the first case control is transferred to
the Dialogue Manager which will report back
upon termination of the dialogue.
In the latter case the Function Manager requests
the information demanded from the appropriae
package and transfers control to the Print/Display
Manager for output of the demanded information.
2) Delivery queuing and scheduling.
Any message which shall be distributed/redistributed
externally and/or internally will by the Function
Mnager be queued in the appropriate Traffic
Handling or Message Distribution queue. (E.g.
messages reentered by the MDCO or MSO, Messages
prepared and sent for coordination or released).
The Function Manager controls the activities
at the terminal positions, i.e. controls the
performance of tasks initiated by the operator
and system by scheduling the activities f the
Dialogue Manager and Print/Display Manager.
3) Log/Statistics information is collected by
the Function Manager and reported to the accountability
system, as well as all administrative information
such as transaction id's is maintained by te
Function Manager.
4) Terminal Control information is maintained
and collected by the Function Manager as well
as the constant display of part of this information.
c) Dialogue Manager.
The dialogue Manager performs the dialogue with
the teminal operator under direction of a format
descriptor for the dialogue. The format descriptor
describes the flowgram for the format, the validity
checks to be performed on the entered fields and
the position within the message/table/command where
he validated fields shall be stored. Validity
checks include field type check, field width check,
table look-up (if necessary) and some semantic
checks.
d) Print/Display Manager
The Print/Display Manager controls print on printers
and displayon VDU's. Print/display is performed
under direction of a format descriptor for the
information to be printed, and under direction
of a destination descriptor indicating the device
where the information shall be printed/displayed.
e) Terminal IFSoftware
The Terminal IF Software has the tasks of implementing
high level features for access to devices not covered
by IO control Software.
5.13.1.2.3 F̲u̲n̲c̲t̲i̲o̲n̲ ̲M̲a̲n̲a̲g̲e̲r̲ ̲-̲ ̲S̲u̲p̲e̲r̲v̲i̲s̲o̲r̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲s̲
a) The Function Manager performs in principle two
tasks in parallel.
1) Treatment of commands
2) Scanning of print queuesrefer fig. 5.13.1.2.3-1
and fig. 5.13.1.2.3-2
b) Treatment of commands
1) Upon entry of a command code from the supervisor,
the Function Manager checks if the command
code entered is valid by looking up the entered
command in its command table If the command
code entered is a mnemonic the full command
code is displayed. Detection of a valid command
code will cause control to be transferred to
the Dialogue Manager.
2) When the Function Manager gets control again
a syntactic and sematic correct command has
been entered. The Function Manager checks
if the command is protected in which case it
awaits the input of the Permissive Entry Code
(PEC).
3) The Function Manager checks if the command
is one of those with restrictive efect in which
case the appropriate text is displayed.
4) The Function Manager now awaits either the
confirmation code or a cancel.
5) In case a cancel request is received the entered
command is deleted and the Function Manager
awaits input ofthe next supervisor command.
6) If the confirmation code is received the transaction
id is displayed and a command utilization record
created and issued to the log and accountability
system.
7) If the command is of the type "Command Control"
or "Print Control" it is executed by the Function
Manager, otherwise the command is queued to
the proper package. In any case command completion
report is created, after command execution
and queued for printout at the report printer.
The completion report is based upon the command
completion code received from the executing
package.…86…1 …02… …02… …02… …02…
Fig. 5.13.1.2.3-1
CAMPS Supervisor Functions…86…1 …02… …02… …02… …02…
Fig. 5.13.1.2.3-2
Supervisor Print Queues…86…1 …02… …02… …02… …02…
c) S̲c̲a̲n̲n̲i̲n̲g̲ ̲o̲f̲ ̲P̲r̲i̲n̲t̲ ̲Q̲u̲e̲u̲e̲s̲ ̲
The supervisor position may be equipped with one
or more (max. four) printers. Activities on a
printer are controlled by a Print/Display Manager.
The Function Manager has a table connecting to
each printer the information type to the printed
at that printer. Four types of information to
be printed at the supervisor position has been
defined:
1) Supervisor Print
2) Report Print
3) Satistics print
4) Log Print.
The print types above are listed in the order of
precedence.
One or more print types may be assigned to one
printer by the supervisor.
The Function Manager scans the appropriate print
queues in order of precdence, when a Print/Display
Manager report itself to be idle. If any non empty
queue is found the Function Manager activates the
Print/Display Manager for printout of the information.
5.13.1.2.4 D̲i̲a̲l̲o̲g̲u̲e̲ ̲M̲a̲n̲a̲g̲e̲r̲ ̲-̲ ̲S̲u̲p̲e̲r̲v̲i̲s̲o̲r̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲s̲
The Diaogue Manager monitors the dialogue with the
supervisor, i.e. guide the supervisor in entering the
command/procedure parameters in the right sequence.
The Dialogue Manager performs the required syntax
and semantic checks on entered parameters and iforms
the supervisor accordingly. Upon entry of a complete
and valid command/procedure control is transferered
to the Function Manager together with the internal
representation of the entered command/procedure.
5.13.1.2.5 P̲r̲i̲n̲t̲/̲D̲i̲s̲p̲l̲a̲y̲ ̲M̲a̲n̲a̲g̲e̲r̲ ̲-̲ ̲S̲u̲p̲e̲r̲v̲i̲s̲o̲r̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲.̲
The Print/Display Manager controls print-out. It is
activated by the Function Manager, directing it from
which queue the utput to be printed shall be taken.
The Print/Display Manager checks up the type of the
print-out and prints the information under direction
of the associated print-format. If the print action
shall be preceded by a "bell" the Print/Display Manaer
is responsible for this. Upon completion of the print-action
which may involve print-out of one or more queue elements
the Print/Display Manager returns to the idle state
and reports this state to the Function Manager.
5.13.1.2.6 F̲u̲n̲c̲t̲i̲o̲n̲ ̲M̲a̲a̲g̲e̲r̲ ̲-̲ ̲M̲D̲C̲O̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲
The Function Manager upon entry of a command code checks
the command code against an internally held table of
commands (refer fig. 5.13.1.2.6-1).
If the command is MDQ (Correction of Message for Distribution)
the Function Mnager fetches the next message to be
handled from the MDCO queue, displays the transaction
id, and transfers control to the Dialogue Manager,
after the Print/Display Manager has displayed the message.
The Function Manager gets control again when he MDCO
has finished his corrections and these have been syntax
validated.
From the Dialogue Manager the applied corrections together
with commands for further treatment, i.e. output on
PTP, output on own printer, distribution, are handed
to theFunction Manager in validated form.
If output on own printer is specified the Print/Display
Manager is activated. If output on PTP or distribution
are commanded the message is queued to the PTP and/or
distribution, respectively.…86…1 …02… …02… …02… …02…
Fig. 5.13.1.2.6-1
MDCO Function…86…1 …02… …02… …02… …02…
The RDI command (Retrieve for local distribution) is
treated alike. The main difference is that upon entry
of the retrieve key a retrieve command is issued to
the Storage and Retieval package.
5.13.1.2.7 D̲i̲a̲l̲o̲g̲u̲e̲ ̲M̲a̲n̲a̲g̲e̲r̲ ̲-̲ ̲M̲D̲C̲O̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲
The Dialogue Manager monitors the dialogue with the
MDCO, i.e. guides the MDCO in entering the command
parameters in the correct sequence. The Dialogue Manager
performs the required sntax check on the entered parameter
and builds up an internal representation of entered
corrections and/or commands. After entry of all parameters
control is transferred to the Function Manager.
5.13.1.2.8 P̲r̲i̲n̲t̲/̲D̲i̲s̲p̲l̲a̲y̲ ̲M̲a̲n̲a̲g̲e̲r̲ ̲-̲ ̲M̲D̲C̲O̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲
The Print/Display Manager controls print-out on the
printer at the MDCO terminal position. Upon request
after a print-out from the MDCO the Function Manager
transfers control to the Print/Display Manager for
printout. Depending on the type of mesage/output the
Print/Display Manager fetches a system Print control
number and a special handling control number and prints
out the information under direction of the format descriptor
associated with the information.
5.13.1.2.9 F̲u̲n̲c̲t̲i̲o̲n̲ ̲M̲a̲n̲a̲g̲e̲r̲ ̲-̲ ̲M̲S̲O̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲
The Function Manager checks the entered command code
against an internally held command table. (Refer fig.
5.13.1.2.9-1).
If the comand is MSQ the Function Manager fetches the
next message queued for message service, and transfers
control to the Print/Display Manager, which displays
the message and returns control. Control is now transferred
to the Dialogue Manager. When contol is returned to
the Function Manager the MSO has entered his corrections,
and these have been validated (and transferred into
an internal form). The Function Manager now executes
the entered command which may be: print-out of message
at associatd printer, queue for local distribution,
queue for renewed incoming message processing.…86…1
…02… …02… …02… …02…
Fig. 5.13.1.2.9-1
Message Service Function…86…1 …02… …02… …02… …02…
5.13.1.2.10 D̲i̲a̲l̲o̲g̲u̲e̲ ̲M̲a̲n̲a̲g̲e̲r̲ ̲-̲ ̲M̲S̲O̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲
The Dialogue Manager monitors the dialogue with the
MSO, i.e. guides the MSO in entering the command parameters
in the correct sequenc. The Dialogue Manager performs
the required syntax check on the entered parameters
and builds up an internal representation of entered
corrections and/or commands. After entry of all parameters
control is transferred to the Function Manager.
513.1.2.11 P̲r̲i̲n̲t̲/̲D̲i̲s̲p̲l̲a̲y̲ ̲M̲a̲n̲a̲g̲e̲r̲ ̲-̲ ̲M̲S̲O̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲ ̲
The Print/Display Manager controls printout on the
printer at the MSO terminal position. Upon request
after a printout from the MSO the Function Manager
transfers control to the Print/Display Managr for printout.
Depending on the type of message/output the Print/Display
Manager fetches a system Print control number and
a special handling control number and prints out the
information under direction of the format descriptor
associated with he information.
5.13.1.2.12 F̲u̲n̲c̲t̲i̲o̲n̲ ̲M̲a̲n̲a̲g̲e̲r̲ ̲-̲ ̲U̲s̲e̲r̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲s̲
a) The term User Functions covers the three types
of user functions: Preparation, Reception, and
Release. Any subset of this set may be assigned
to a terminal position and an opertor by the supervisor
(refer fig. 5.12.1.2.12-3). The three types of
user functions do not diverge too much from each
other with respect to the general requirement and
thus they are treated in common in this description.
b) The Function Manager as the following main tasks:
- Command/procedure initiation and termination
- Submission of prepared information to the CAMPS
system.…86…1 …02… …02… …02… …02…
Fig. 5.13.1.2.12-1
User Functions…86…1 …02… …02… …02… …02…
- Delivery queue management and scheduling
- Terminal mode control
- Transaction id and document control number
- Statistics and log to collecting packages
- Terminalstatus function
- Cancel, suspend, preemption.
1) Command/procedure initiation and termination.
Upon entry of a command code the Function Manager
checks the entered command code against an
internally held command table. If the command
coe is found a transaction id is assigned and
control is transferred to the Dialogue Manager.
When the Dialogue Manager has finished a command/procedure
control is transferred back to the Function
Manager together with an instruction list informig
the Function Manager either what to do with
generated information (e.g. a prepared message)
or to request some information from the CAMPS
system (e.g. a retrieve request).
In the first case the generated information
is queued for the approprite CAMPS system in
the latter case a command is queued.
The Function Manager now await entry of the
next user command.
If the Dialogue Manager during performance
of its task needs access to a message, command
or alike this access is requestd through the
Function Manager with an indication, that control
is wanted again after access to the information
has been granted.
2) Delivery queue management and scheduling.
The Function Manager monitors the queues associated
with the termial position. There is one queue
for each precedence level and one queue for
reception of requested information.
The Function Manager scans the queues in order
of precedence and associates a transaction
id with the fetched information. Then control
is transferred to the Print/Display Manaer
for print or display of the information.
3) Terminal mode control
The Function Manager monitors the terminal
mode, and performs its task in accordance with
the current mode.
When operating in interactive mode the only
delivery queue sanned is the Flash queue.
If a queue element arrives in this queue the
Function Manager checks if preemption of the
Dialogue Manager is required, this will be
the case if the task of the Dialogue Manager
is of lower precedence than Flash. If preeption
is required the Dialogue Manager is preempted
and the terminal forced into receive mode.
When operating in receive mode the only events
from the operator the Function Manager serves
are the depressing of either of the two function
keys Cacel or Suspend.
The printing action in cause will be stopped
(if not of Flash precedence), the information
under print staying in its delivery queue and
the terminal forced into interactive mode.
4) Transaction-id and document control number
Transaction-ids and document control numbers
are fetched and assigned by the Function Manager.
5) Statistics and log submission to collecting
packages.
When the Function Manager initiates a command/procedure
a record for statistics collction and for log
collection are created.
For the created statistics record the contents
may be supplied by the Function Manager alone
or by the Function Manager and the Dialogue
Manager depending on the characteristics of
the transaction in prgress.…86…1 …02… …02…
…02… …02…
For the created log record the contents may
be supplied by the Function Manager alone,
by the Function Manager and the Dialogue Manager,
or by the Function Manager, the DialogueManager,
and the Terminal Monitoring and Control Software
(SS&C subsystem) depending on the characteristics
of the transaction in progress.
The Statistics information is communicated
to the Statistics package via the CAMPS System
Functions by te Function Manager upon completion
of a transaction.
Log information is communicated to the Log
and Accountability package via the CAMPS System
Functions by the Function Manager upon initiation
and/or completion of a transaction as required
forthe transaction type.
6) Terminal Status Function
The Function Manager is responsible for monitoring
the terminal control information and the display
of it at the top of the VDU.
7) Cancel, Suspend, Preemption
Cancel, suspend and preeption commands are
executed under the control of the Function
Manager.
A Cancel request may be issued by the operator.
The interpretation of the Cancel command depends
on the activity in progress.
The effect of depressing the Cancel key whre
a printing action is in progress is as described
above in 3).
The effect of a cancel request when an interactive
action is in progress will cause the action
to be terminated. Other effects will depend
on the type of the cancelled transactio.
A suspend function may be issued by the operator.
The interpretation of the suspend command
depends on the action in progress.
If an interactive function is in progress,
the suspend function will either have the same
effect as the cancel function or cause information
entered so far to be kept by the sysem for
later manipulation. The actual effects depend
on the transaction type in progress.
Pre-emption is carried out by the Function
Manager upon detection of the presence of an
element in the Flash precedence queue.
If the terminal is in nteractive mode, the
pre-emption will take place as described above
in 3), the pre-emption of the Dialogue Manager
having the same effect as the suspend function.
If the terminal is in receive mode, the printing
action will be stopped (analogue tocancel),
and the Print/Display Manager ordered to Print/Display
the information of Flash precedence.
5.13.1.2.13 D̲i̲a̲l̲o̲g̲u̲e̲ ̲M̲a̲n̲a̲g̲e̲r̲ ̲-̲ ̲U̲s̲e̲r̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲s̲
The Dialogue Manager monitors the dialogue with the
user, i.e. guides the user in entering paramters etc.
in the correct sequence.
The Dialogue Manager makes syntactic and semantic checks
on entered information. These checks may require look-up
in system tables by the Table Managemment Package.
The Dialogue Manager collects parts of statstics and
log information required.
5.13.1.2.14 P̲r̲i̲n̲t̲ ̲M̲a̲n̲a̲g̲e̲r̲ ̲-̲ ̲U̲s̲e̲r̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲s̲
The Print/Display Manager controls print on printer
and display on VDU of messages, comments and various
control information. Print/Display is performed under
diretion of a Format Descriptor for the presentation
format under execution. The format description describes
the fields to be output, the sequence of output and
the text strings to be output together with the fields.
5.13.1.2.15 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.2.16 S̲p̲e̲c̲i̲a̲l̲ ̲D̲e̲v̲i̲c̲e̲s̲
TBD.
5.13.1. 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̲
TBD.
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̲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/ICD/001…02…MDCO Procedures
ref. doc. no. CPS/ICD/002
Message Service Procedures ref. doc. no.
CPS/ICD/002
Supervisor Commands and Procedures ref. doc. no.
CPS/ICD/002
5.13.2.2 P̲a̲c̲k̲a̲g̲e̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲s̲
In the following subsections, all the interfaces of
the Terminal package to otherpackages are described.
Each interface is described for one terminal position
having either access to the Supervisor Function, Message
Distribution Control Function, Message Service Function
or User Functions. It should however be understood
tha for each active terminal position accessing CAMPS,
an interface of the described type exists, i.e. if
two MDCOs are signed-in, two instances of MDCO interfaces
exist, one for each MDCO terminal position. Further,
if a terminal position has accessto 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̲
The Traffic Handling Package perfrms analysis of incoming
and outgoing messages, as well as routing of outgoing
messages.
5.13.2.2.1.1 S̲u̲p̲e̲r̲v̲i̲s̲o̲r̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲
Service Messages prepared by the Supervisor are queued
by the Terminal Package in the Traffic Handling package
queue for utgoing service messages.
Outgoing Messages retrieved for rerun by the Supervisor
are queued by the Terminal Package in the Traffic Handling
Package queue for outgoing messages.
Incoming Service Messageswhich shall be presented to
the Supervisor are queued by the Traffic Handling package
in the Terminal Package queue for service messages.
Security reports, warning reports and channel reports
are placed in the Terminal Package queue for reports
b the Traffic Handling Package.…86…1 …02… …02… …02… …02…
Q1: Queue for Outgoing Service messages
Q2: Queue for Rerun of Outgoing messages
Q3: Queue for Supervisor reports
Q4: Queue for ServiceMessages
Q5: Request queue
Fig. 5.13.2.2.1-1
5.13.2.2.1.2 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.
5.13.2.2.1.3 M̲e̲s̲s̲a̲g̲e̲ ̲S̲e̲r̲v̲i̲c̲e̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲
Messages that are not automatically accepted by Trffic
Handling are queued for Message Service.
The Terminal Package places the message in the Traffic
Handling packages queue for messages having been to
Message Service after completion of message service.
5.13.2.2.1.4 U̲s̲e̲r̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲s̲
When th Release Officer releases a message, the Terminal
Package places the message in the Released message
queue of the Traffic Handling Package.
The Traffic Handling Package returns a Station Serial
Number, SSN to the Terminal Package.
5.13.2.3.2 D̲s̲t̲r̲i̲b̲u̲t̲i̲o̲n̲
The Distribution Package is responsible for internal
distribution of information.
5.13.2.3.2.1 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 b the Terminal Package in the Distribution Packages
queue assigned to this purpose.
Fig. 5.13.2.2.1-2
Fig. 5.13.2.2.1-3
Fig. 5.13.2.2.2-1
5.13.2.2.2.2 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 for
the Terminal Package in the queue assigned to his purpose.
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 Dstribution system, which if the ordered distribution
can be executed, i.e. listed terminal positions active,
returns a confirmation signal to the terminal position.
The MDCO may retrieve messages for distribution. Such
messages are by the Terminl Package queued for the
Distribution Package in the appropriate queue.
5.13.2.2.2.3 M̲e̲s̲s̲a̲g̲e̲ ̲S̲e̲r̲v̲i̲c̲e̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲
TBD.
5.13.2.2.2.3 U̲s̲e̲r̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲s̲
The Terminal package queues messages for coordination,
messages for release, comments, and relese notifications
to be distributed to the Distribution Package.
The Distribution package queues information addressed
to a user position in the FLASH, IMMEDIATE, PRIORITY
or ROUTINE queue of the Terminal Package in accordance
with the precedence f the delivered information.
Fig. 5.13.2.2.2-2
Fig. 5.13.2.2.2-3
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 (SAR) Package handles the
storage/retrieval of all items of information, which
are stored on long term storage.
5.13.2.2.3.1 S̲u̲p̲e̲r̲v̲i̲s̲o̲r̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲
When the SAR Package detects the need for getting an
offline disc mounted or for dumping to offline discs,
a request for the required activity is inserted by
the SAR Package in the Terminal Package Supervisor
reprt queue.
When the Supervisor has mounted the wanted disc or
acknowledged the dump activity to take place, the Terminal
Package communicates this to SAR.
Supervisor retrieve requests are by the Terminal Package
inserted in the SAR package retrive request queue.
When the SAR Package has processed the request, the
result is placed in the Terminal Package supervisor
queue for delivery.
Reports generated by SAR are inserted in the Terminal
Package supervisor report queue.
5.13.2.2.3.2 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, the Terminal
Package inserts the retrieve request in the SAR Packages
retrieve request queue. The SAR Package inserts the
result of the processing of the request in he Terminal
Packages MDCO delivery queue.
5.13.2.2.3.3 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.
Fig. 5.13.2.2.3-2
Fig. 5.13.2.2.3-3
5.13.2.2.3.4 U̲s̲e̲r̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲s̲
When a user issues a retrieval or message merge request,
the Terminal package inserts the request in the SAR
package retrieval request queue.
When te SAR Package has processed the request, it inserts
the result of it in the Terminal Package delivery queue.
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̲
The Log and Accountability Package collects log records
reported from various package and stres them on disk.
Upon request from the Supervisor trace of log is performed
by the Log and Accountability Package.
The Log and Accountability delivers periodically a
report to the terminal position containing log records
for each transaction wich have been executed at that
terminal in the given period.
5.13.2.2.4.1 S̲u̲p̲e̲r̲v̲i̲s̲o̲r̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲
Log records of Supervisor activities (command utilization
records) are communicated to the Log and Accountability
package through CAMPS System Functins.
The Log and Accountability Package queues log records
to the Terminal Package (Q1) for print-out at the supervisor's
terminal as they arrive, if this has been requested
by the supervisor.
The supervisor may request various traces of log recrds.
The Terminal Package queues such requests in the command
function queue of the Log and Accountability Package.
When the Log and Accountability Package has traced
the requested log records, they are placed in the Terminal
Package queue for taced 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 Lo and Accountability
Package.…86…1 …02… …02… …02… …02…
Fig. 15.13.2.2.4-1
5.13.2.2.4.2 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 Systeme
Functions.
5.13..2.4.3 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.
5.13.2.2.4.4 U̲s̲e̲r̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲s̲
Log records of user activities are communicated by
the Terminal ackage to the Log and Accountability Package
through CAMPS System Functions.
TEP will periodically with a periodicity specified
by the supervisor or as a result of a user request
ask the Log and Accountability Package to extract the
log records cnstituting a specified Status Report.
The Log and Accountability Package will place the
requested information in the Terminal Package queue
for requested information assigned to the requesting
user.
The request may be for one of the following sttus types:
- Transaction Status Report
- Message Status
- Release Status
5.13.2.2.5 S̲t̲a̲t̲i̲s̲t̲i̲c̲s̲
The Statistics package collects statistical information
from many packages and makes statistics based on the
collected information. The statist
