top - download
⟦abdd8d9f6⟧ Wang Wps File
Length: 18595 (0x48a3)
Types: Wang Wps File
Notes: FIX/1000/PSP/038
Names: »5207A «
Derivation
└─⟦c5670ecfe⟧ Bits:30006140 8" Wang WCS floppy, CR 0516A
└─ ⟦this⟧ »5207A «
WangText
…16……00……00……00……00…!…0a……00……00…!…0b…!…00…!…05… …86…1 …02… …02… …02…
…0e……0e… 5207A/aml…02…FIX/1000/PSP/0038
…02…OK/850529…02……02…
FIKS SYSTEM SPECIFICATION
…02……02…FK 7809…0f…
4.1.6 S̲u̲p̲e̲r̲v̲i̲s̲o̲r̲y̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲s̲ ̲S̲u̲b̲s̲y̲s̲t̲e̲m̲
4.1.6.1 F̲u̲n̲c̲t̲i̲o̲n̲s̲
The Supervisory Function Subsystem implements dedicated
functions for the NODE/MEDE supervisors whereas the
supervisor's message entry functions are covered in
the Message Entry Subsystem (MES). Also the SFS provides
an interface to the SCC and support statistics (collection
and printing) and print of log information.
The following functions are recognized:
o R̲e̲g̲i̲s̲t̲r̲a̲t̲i̲o̲n̲ ̲o̲f̲ ̲u̲n̲d̲e̲l̲i̲v̲e̲r̲a̲b̲l̲e̲ ̲m̲e̲s̲s̲a̲g̲e̲s̲
Undeliverable messages are received and registered
on hard copy.
o D̲i̲s̲t̲r̲i̲b̲u̲t̲i̲o̲n̲
Supports the distribution of undeliverable messages
to local terminals.
o M̲e̲s̲s̲a̲g̲e̲ ̲E̲n̲t̲r̲y̲
Supports the reentry of undeliverable messages
into the network.
o S̲u̲p̲e̲r̲v̲i̲s̲i̲o̲n̲
Supports
- display of other terminals' status
- display of alarms
- print of the message journal
- print of the message log
- print of the 24 hour statistics
o C̲o̲n̲t̲r̲o̲l̲
Supports
- blocking/unblocking of terminal
- initiation of security interrogation
- terminal queue reorganization relocation, rerouting,
and reestablishment
- NPDN connection/disconnection
- open/close trunks
o O̲n̲-̲l̲i̲n̲e̲ ̲T̲a̲b̲l̲e̲ ̲H̲a̲n̲d̲l̲i̲n̲g̲
Supports the update and display of
- ANO tables
- User security profiles in USP
- Data user tables
- Routing tables
o M̲E̲D̲E̲ ̲t̲o̲ ̲S̲C̲C̲ ̲I̲/̲F̲
Supports the collection of MEDE statistics, reception
of reports, and sending of control messages to
the SCC.
o S̲C̲C̲ ̲t̲o̲ ̲M̲E̲D̲E̲ ̲I̲/̲F̲
Supports update of local routing tables and supervisor
security profiles and requests on-line diagnostics
test results.
4.1.6.2 S̲u̲b̲s̲y̲s̲t̲e̲m̲ ̲B̲l̲o̲c̲k̲ ̲D̲i̲a̲g̲r̲a̲m̲
Figure 4.1.6 illustrated the flow of data and control
for each of the functions supported by the SFS.
R̲e̲g̲i̲s̲t̲r̲a̲t̲i̲o̲n̲ ̲o̲f̲ ̲u̲n̲d̲e̲l̲i̲v̲e̲r̲a̲b̲l̲e̲ ̲m̲e̲s̲s̲a̲g̲e̲s̲
Messages which for some reason cannot be delivered
to their correct destination (local terminals or other
N/M's) will be delivered to the SFS system. (The SFS
subsystem supports facilities for manually distribution
of these messages (ref. distribution and reentry).
When a message is received in the DT-queue of the SFS,
a DT-number is allocated to it. (This number is used
by the operator when he/she specifies a message to
be redistributed).
The registration of the message is performed by printing
the following information on a ROP which is allocated
for these messages:
1) The reason why the message could not be distributed
to the destination it was meant for.
2) The allocated DT-number.
3) The message header and the two first text lines.
4) The message classification.
The printing is performed by reading the message in
question from disk, formatting the text to be printed,
writing the formatted text to a PDB-file, telling the
PIP process (via QACCESS) to print the contents of
the PDB-file.
L̲o̲c̲a̲l̲ ̲d̲i̲s̲t̲r̲i̲b̲u̲t̲i̲o̲n̲ ̲o̲f̲ ̲u̲n̲d̲e̲l̲i̲v̲e̲r̲a̲b̲l̲e̲ ̲m̲e̲s̲s̲a̲g̲e̲s̲
Local distribution of messages are performed on request
from the supervisory operator.
The operator specifies the DT-number of the message
he/she wants to redistribute and the terminal ID's
of the terminals, which shall receive a copy of the
message. The number of copies to each terminal can
optionally be specified by the operator.
The MDS subsystem is asked to distribute the message
to the specified terminals (via pseudo MTCB's and QACCESS).
If the operator does not want to redistribute the
specified message he/she can either delete it or leave
it as it is for later use.
M̲e̲s̲s̲a̲g̲e̲ ̲r̲e̲e̲n̲t̲r̲y̲
Reentry of undeliverable messages into the FIKS network
is performed on request from the supervisory operator.
The operator specifies the DT-number of the message
he/she wants to reenter into the network. The message
is retrieved and a routing mask is defined. (The routing
mask will contain the destination (N/M's and/or SCC's)
to which the message was meant for but never delivered
to.
The message is sent to the NSS which will send the
messages to the destination specified in the routing
mask.
If the operator does not want to reenter the specified
message into the network he/she can either delete it
or leave it as it is, and then process it later on.
D̲i̲s̲p̲l̲a̲y̲ ̲A̲l̲a̲r̲m̲
The supervisor may request a display of the cause of
an alarm, which is performed by reading the oldest
element in the AL-queue. The reason code of the alarm
is decoded and converted to a readable text string
which is displayed on the VDU.
D̲i̲s̲p̲l̲a̲y̲ ̲S̲t̲a̲t̲u̲s̲
A supervisor's request of the queue status of the terminals
containing the queue length for print, display, report,
and distribution queues is performed by means of an
ITM procedure.
P̲r̲i̲n̲t̲ ̲M̲e̲s̲s̲a̲g̲e̲ ̲J̲o̲u̲r̲n̲a̲l̲,̲ ̲M̲e̲s̲s̲a̲g̲e̲ ̲L̲o̲g̲ ̲o̲r̲ ̲N̲/̲M̲ ̲S̲t̲a̲t̲i̲s̲t̲i̲c̲s̲
If the supervisor requests a printout of the message
journal, the request is transferred to the JOURNAL
process which will define the contents to be printed
out, and then ask the PIP process to perform the printing.
If a Message Log is requested the request is transferred
to the SRR process. SRR will generate a file containing
the log and ask the PIP process to print it.
If a N/M statistics is requested the PIP process is
requested to print the statistics file.
Control of Terminals (Block, Unblocking,
S̲e̲c̲u̲r̲i̲t̲y̲ ̲I̲n̲t̲e̲r̲r̲o̲g̲a̲t̲i̲o̲n̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
A supervisor's request for blocking, unblocking, security
interrogating terminal is performed by sending an AMOS
message to the ITM, which stops the processing at the
terminal to be blocked.
In "blocking" the ITM logs off the terminal and no
further log on is allowed.
In "unblocking" the ITM allows a blocked terminal to
log on.
In security interrogation the ITM initiates a password
authentication of an operator at a specified terminal.
Control of Queues (Relocate, Reorganize, Reroute, R̲e̲e̲s̲t̲a̲b̲l̲i̲s̲h̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
The control is executed by invoking the QACCESS procedure
and by updating the ANO and ALT tables in core.
U̲P̲D̲A̲T̲E̲ ̲a̲n̲d̲ ̲D̲I̲S̲P̲L̲A̲Y̲ ̲o̲f̲ ̲A̲N̲O̲ ̲a̲n̲d̲ ̲A̲I̲G̲ ̲t̲a̲b̲l̲e̲s̲
The supervisor may display the ANO table or an AIG
and correct entries by means of the procedures FORMAT-ANO-INDEX
and SET-ANO-TERM. Requests for updates may also be
received as control messages from a SCC.
U̲P̲D̲A̲T̲E̲ ̲U̲S̲P̲
The supervisor may display, correct, delete, and insert
user security profiles in the USP by means of the procedures
FORMAT-USP-INDEX and USP-TABLE-UPDATE. Requests for
updates may also be received as control messages from
a SCC.
L̲O̲A̲D̲ ̲D̲A̲T̲A̲ ̲U̲S̲E̲R̲ ̲T̲a̲b̲l̲e̲
The supervisor may load a new DATA USER table by creating
a control message (defining the table to be loaded)
and enqueueing it to the NSS.
U̲P̲D̲A̲T̲E̲ ̲R̲O̲U̲T̲I̲N̲G̲ ̲T̲a̲b̲l̲e̲
The supervisor may display, correct, insert, and delete
entries in the NODAL ROUTING table in the NDF. The
updated table is entered into a control message, which
is enqueued to the NSS.
N̲P̲D̲N̲ ̲C̲o̲n̲n̲e̲c̲t̲i̲o̲n̲
The Block diagram indicates that a control message
containing a NPDN Assignment or close down request
is sent to the NSS.
S̲t̲a̲t̲i̲s̲t̲i̲c̲s̲
Various statistic items are collected automatically
every hour on the hour and sent as a control message
to the SCC's.
Every midnight a statistic report is received from
the SCC. The statistic message is put into a supervisory
queue for printout (on request from the supervisory
operator).
R̲e̲p̲o̲r̲t̲i̲n̲g̲ ̲o̲f̲ ̲e̲v̲e̲n̲t̲s̲ ̲t̲o̲ ̲S̲C̲C̲
Some events, which have occured on the local N/M are
reported/generated by the SFS. These events are transferred
to the SCC's in a control message.
Events in question are: change of disk status, availability
of standby branch, status of trunk lines etc.
O̲n̲l̲i̲n̲e̲ ̲d̲i̲a̲g̲n̲o̲s̲t̲i̲c̲s̲ ̲t̲e̲s̲t̲s̲
Tests of the RAM memory area and the CPU module are
continuously performed. These tests are run at the
lowest priority, which means that they are mainly active
in idle situations. At regular time intervals the
diagnostics results are reported to the ESP process.
D̲e̲l̲i̲v̲e̲r̲y̲ ̲o̲f̲ ̲d̲i̲a̲g̲n̲o̲s̲t̲i̲c̲s̲ ̲r̲e̲s̲u̲l̲t̲s̲
On request from the SCC, diagnostics results, disk
status, and standby branch status are collected and
put into a control message, which is returned to the
SCC.
Figure 4.1.6-1…01…SFS Block Diagram
Figure 4.1.6-2…01…SFS Block Diagram
Figure 4.1.6-3…01…SFS Block Diagram
4.1.6.3 D̲E̲S̲I̲G̲N̲ ̲O̲V̲E̲R̲V̲I̲E̲W̲
The functions covered by the supervisory functions
subsystems are performed by four separate processes/modules:
S̲F̲S̲ ̲m̲o̲d̲u̲l̲e̲
The SFS module is a module within the terminal process.
The modules in the terminal process are:
ITM: Interactive terminal module, (handles communication
between terminal and process).
MES: Message entry functions (handles all functions
concerning narrative messages).
SFS: Supervisory functions module. This module
handles the interactive functions, which are
only available (legal) for the supervisory
terminal operators.
The most simple functions are executed by the
SFS module itself, while more time consuming
or complicated functions are performed by either
the SAF process or the DTS process (ref. descriptions
below). These processes execute the commands
on request from SFS, and they deliver the results
of the execution to SFS when they are performed.
SFS takes care of communicating the results
of the executed functions to the supvervisory
operator (either on screen or on hard copy).
The commands supported by SFS are in short:
D̲i̲s̲t̲r̲i̲b̲u̲t̲i̲o̲n̲ ̲c̲o̲m̲m̲a̲n̲d̲s̲:̲
DDT Local distribution of DT-messages
REE Reenter DT-messages to network
S̲u̲p̲e̲r̲v̲i̲s̲i̲o̲n̲ ̲c̲o̲m̲m̲a̲n̲d̲s̲:
DAL Display alarm
DQS Display queue status
PMJ Print message journal
PML Print message log
PST Print 24 hour statistics
C̲o̲n̲t̲r̲o̲l̲ ̲c̲o̲m̲m̲a̲n̲d̲s̲:
BLT Block terminal
UBT Unblock terminal
INT Interrogate terminal
ROQ Reorganize a terminal queue
REQ Relocate queue elements at a terminal
RRT Reroute terminal traffic
RET Reestablish terminal traffic
NPD NPDN dial-up
NPC NPDN close-down
OPT Open trunk
CLT Close trunk
O̲n̲-̲l̲i̲n̲e̲ ̲t̲a̲b̲l̲e̲ ̲h̲a̲n̲d̲l̲i̲n̲g̲ ̲c̲o̲m̲m̲a̲n̲d̲s̲:
DOI Display ANO table
DOT Update ANO table
DUR Data user reconfiguration
DRT Routing table update
ESM Security interrogation
S̲A̲F̲ ̲p̲r̲o̲c̲e̲s̲s̲
The SAF process exists in one incarnation on each N/M.
The process is always active and it contains the interface
(concerning control functions) to the SCC's. Furthermore
it has interfaces to the SFS module in each terminal
process and to the NSS process.
The functions in the SAF are:
- independent of each other
- their execution time are uncritical
- they are seldom invoked
The functions in the SAF process can be divided in
four categories:
a. S̲u̲p̲p̲o̲r̲t̲ ̲t̲o̲ ̲t̲e̲r̲m̲i̲n̲a̲l̲ ̲p̲r̲o̲c̲e̲s̲s̲e̲s̲
Some of the supervisory commands supported by the
terminal process which require complicated processing
are partly executed by the SAF. These functions
mainly concerns handling of tables and queues.
b. P̲r̲o̲c̲e̲s̲s̲i̲n̲g̲ ̲o̲f̲ ̲c̲o̲m̲m̲a̲n̲d̲s̲ ̲i̲s̲s̲u̲e̲d̲ ̲b̲y̲ ̲t̲e̲r̲m̲i̲n̲a̲l̲ ̲p̲r̲o̲c̲e̲s̲s̲e̲s̲
On request from terminal processes, the SAF executes
commands entered by a supervisory operator, which
require an interface to the NSS or SCC's. The
types of commands are open/close of trunks and
dial-up lines, reporting of events to the SCC's
etc.
c. A̲u̲t̲o̲m̲a̲t̲i̲c̲ ̲f̲u̲n̲c̲t̲i̲o̲n̲s̲
On an hourly basis, the SAF collects statitic items
and transfer them to the SCC's. Every midnight
the statistic items are read. Furthermore the
SAF collects statistics concerning queues and transfers
it to SCC's.
d. P̲r̲o̲c̲e̲s̲s̲i̲n̲g̲ ̲o̲f̲ ̲c̲o̲m̲m̲a̲n̲d̲s̲ ̲i̲s̲s̲u̲e̲d̲ ̲f̲r̲o̲m̲ ̲t̲h̲e̲ ̲S̲C̲C̲
The SAF receives and executes commands initiated
by a SCC operator. These commands concern updates
of RDF-tables and user security profiles on the
local N/M.
Every midnight the SAF receives a statistic report
message from the SCC. This message is entered
into a supervisory terminal queue for printout
or request.
D̲T̲S̲ ̲p̲r̲o̲c̲e̲s̲s̲
The DTS process exists in one incarnation on each N/M.
Its functions are:
- Reception of undeliverable messages. The messages
are received in the DT-queue and a DT-number is
allocated to each message. When a message is received
the reason why the message could not be delivered
correctly is printed on a ROP together with DT-number,
message header and two text lines.
- On request from a SFS module, a specified DT-message
is either retrieved and delivered to the SFS module
or reentered into the network. Furthermore the
SFS module can request DTS to delete a specified
DT-message.
O̲L̲D̲ ̲p̲r̲o̲c̲e̲s̲s̲
The OLD process exists in two incarnations on each
N/M, one in the active branch and one in the standby
branch. The process runs with the lowest priority
and it continuously performs RAM test and CPU test.
The test results are at regular time intervals delivered
(on request) to the ESP process. The test report tells
the ESP whether the branch is alive or not. Changes
in status are by ESP reported to the SAF process.
4.1.6.3.1 I̲n̲t̲e̲r̲f̲a̲c̲e̲s̲
S̲A̲F̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲ ̲t̲o̲ ̲t̲h̲e̲ ̲S̲C̲C̲
The SAF interface to the SCC - dealing with reports
and statistics - is provided through the nodal switch
subsystem (NSS) by means of control messages enqueued
by the standard FIKS intersubsystem methods.
S̲C̲C̲ ̲t̲o̲ ̲S̲A̲F̲ ̲i̲n̲t̲e̲r̲f̲a̲c̲e̲
The SCC to SAF interface - dealing with RDF and USP
tables and requests to the SAF - is provided through
control messages. A control message is recognized
by the NSS, which flags and directs it to the MDS,
which again directs it to a SAF input queue (SF).
A̲p̲p̲l̲i̲c̲a̲t̲i̲o̲n̲ ̲s̲u̲b̲s̲y̲s̲t̲e̲m̲s̲ ̲i̲n̲t̲e̲r̲f̲a̲c̲e̲ ̲t̲o̲ ̲t̲h̲e̲ ̲S̲F̲S̲ ̲m̲o̲d̲u̲l̲e̲
Application subsystems interface to the SFS in the
following cases:
o R̲e̲p̲o̲r̲t̲s̲ ̲t̲o̲ ̲b̲e̲ ̲s̲e̲n̲t̲ ̲t̲o̲ ̲t̲h̲e̲ ̲S̲C̲C̲
An entry is made in the SF queue
o R̲e̲p̲o̲r̲t̲s̲ ̲t̲o̲ ̲t̲h̲e̲ ̲s̲u̲p̲e̲r̲v̲i̲s̲o̲r̲y̲ ̲o̲p̲e̲r̲a̲t̲o̲r̲s̲
An entry is made in the report queue AL.
S̲F̲S̲ ̲m̲o̲d̲u̲l̲e̲ ̲t̲o̲ ̲S̲A̲F̲ ̲i̲n̲t̲e̲r̲f̲a̲c̲e̲
The SFS module invokes the SAF (e.g. table update)
by placing an entry in the SF queue.
The SF queue is a precedence queue allowing terminal
functions to be executed with high priority.
S̲A̲F̲ ̲t̲o̲ ̲S̲F̲S̲ ̲m̲o̲d̲u̲l̲e̲ ̲i̲n̲t̲e̲r̲f̲a̲c̲e̲
The SAF acknowledges request from the SFS module by
enqueueing a pseudo MTCB in the RD queue at the terminal
process.
O̲n̲-̲L̲i̲n̲e̲ ̲d̲i̲a̲g̲n̲o̲s̲t̲i̲c̲s̲ ̲i̲n̲t̲e̲r̲f̲a̲c̲e̲
The OLD sends test results to the ESP via an AMOS system
message.
The SAF requests and gets test results via AMOS system
messages.
C̲l̲o̲c̲k̲ ̲p̲r̲o̲c̲e̲s̲s̲ ̲i̲n̲t̲e̲r̲f̲a̲c̲e̲s̲
The Clock process invokes periodically the SAF and
OLD process by means of an AMOS system message.
S̲F̲S̲ ̲m̲o̲d̲u̲l̲e̲ ̲t̲o̲ ̲P̲I̲P̲ ̲i̲n̲t̲e̲r̲f̲a̲c̲e̲s̲
o The SFS module enqueues a pseudo MTCB in a PIP
queue when the statistic message is to be printed.
S̲F̲S̲ ̲m̲o̲d̲u̲l̲e̲ ̲t̲o̲ ̲M̲D̲S̲ ̲i̲n̲t̲e̲r̲f̲a̲c̲e̲s̲
o The SFS module enqueues a pseudo MTCB in the MDS
input queue when an undeliverable message is to
be distributed.
S̲F̲S̲ ̲m̲o̲d̲u̲l̲e̲ ̲t̲o̲ ̲S̲R̲R̲ ̲p̲r̲o̲c̲e̲s̲s̲
o The SFS module enqueues a pseudo MTCB in the SRR
input queue when a message log report has been
requested.
S̲F̲S̲ ̲m̲o̲d̲u̲l̲e̲ ̲t̲o̲ ̲J̲O̲U̲R̲N̲A̲L̲ ̲p̲r̲o̲c̲e̲s̲s̲
o The SFS module enqueues a pseudo MTCB in the JOURNAL
process when a mesage journal report has been requested.
S̲F̲S̲ ̲m̲o̲d̲u̲l̲e̲ ̲t̲o̲ ̲D̲T̲S̲ ̲i̲n̲t̲e̲r̲f̲a̲c̲e̲
o Requests concerning retrieval, reentry or deletion
of specified DT-messages are sent in AMOS system
messages.
D̲T̲S̲ ̲t̲o̲ ̲S̲F̲S̲ ̲m̲o̲d̲u̲l̲e̲ ̲i̲n̲t̲e̲r̲f̲a̲c̲e̲s̲
o Responses on requests received from the SFS module
are delivered in AMOS system messages and in PDB-messages.
S̲u̲b̲s̲y̲s̲t̲e̲m̲s̲ ̲t̲o̲ ̲D̲T̲S̲ ̲i̲n̲t̲e̲r̲f̲a̲c̲e̲s̲
o Undeliverable messages are by the subsystems delivered
in the DT-queue.
4.1.6.3.2 S̲u̲p̲e̲r̲v̲i̲s̲o̲r̲y̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲s̲ ̲S̲u̲b̲s̲y̲s̲t̲e̲m̲ ̲Q̲u̲e̲u̲e̲s̲
The following input queues are recognized (see Figure
4.1.6.3-1):
o A̲L̲ ̲q̲u̲e̲u̲e̲
Contains reports from application subsystems.
It is common to all supervisory operators and it
is served by the SFS module of the terminal process.
o D̲T̲ ̲q̲u̲e̲u̲e̲
Contains messages which cannot be delivered. The
queue is common to all supervisory terminals and
is served by the DTS process.
o S̲F̲ ̲q̲u̲e̲u̲e̲
Contains control messages from the SCC, commands
from the SFS module or reports from the application
subsystems.
The queue is common to all supervisory operators
and is served by the supervisory automatic function
process (SAF).
o R̲D̲ ̲q̲u̲e̲u̲e̲
Contains pseudo-MTCB's describing an answer from
the SAF to a STF request.
There exists one RD queue per active terminal and
it contains only one element. The RD queue is
served by the SFS module.
o A̲X̲ ̲q̲u̲e̲u̲e̲
Contains control messages originating from the
SCC defining 24 hours N/M statistics.
Figure 4.1.6.3-1…01…SFS Queue Overview
4.1.6.4 V̲i̲s̲u̲a̲l̲ ̲T̲a̲b̲l̲e̲ ̲o̲f̲ ̲C̲o̲n̲t̲e̲n̲t̲s̲
Figure 4.1.6-4 provides a visual table of contents
of the three functional categories which comprise the
SFS.
Figure 4.1.6-4 (1 of 4)…01…Supervisory Functions Subsystem…01…Visual Table of Contents
Figure 4.1.6-4 (2 of 4)…01…Supervisory Functions Subsystem…01…Visual Table of Contents
Figure 4.1.6-4 (3 of 4)…01…Supervisory Functions Subsystem…01…Visual Table of Contents
Figure 4.1.6-4 (4 of 4)…01…Supervisory Functions Subsystem…01…Visual Table of Contents
