top - download
⟦5edad2451⟧ Wang Wps File
Length: 45773 (0xb2cd)
Types: Wang Wps File
Notes: FIX/1162/PSP/0069
Names: »5100A «
Derivation
└─⟦1f5010eea⟧ Bits:30006143 8" Wang WCS floppy, CR 0473A
└─ ⟦this⟧ »5100A «
WangText
…00……00……00……00……00…:…02……00……00…:
:…05…:…07…9…00…9…05…9…07…8…0b…8…0d…8…01…8…07…7…08…7…0d…7…00…7…01…7…06…6…0a…6…0d…6…0f…6…00…6…01…6…02…6
5…0a…5…0f……86…1 …02… …02… …02…
…0f… 5100A/aml…02…FIX/1162/PSP/0069
…02…APE/840622…02… #
FIKS NETWORK STATISTIC SUBSYSTEM (NES)
PRODUCT SPECIFICATION…02……02…FK 7809…0e…
FIKS NETWORK STATISTIC SUBSYSTEM (NES)
PRODUCT SPECIFICATION
FIX/1162/PSP/0069
Allan Petersen
Ole Eskedal
AMC (6), APE, REV, BHE, LU, Conf. Mgr., File
…0e… ILS Manager 840622
S/W Manager 840622
1
840622
Conf. Mgr. 840622
…0f… 5100A/aml…02… FIX/1162/PSP/0069
…02… APE/840622…02……02… ii
FIKS NETWORK STATISTIC SUBSYSTEM (NES)
PRODUCT SPECIFICATION…02……02…FK 7809…0e…
1 840622 All First issue of document
5100A/aml…02…FIX/1162/PSP/0069
…02…APE/840622…02……02…iii
FIKS NETWORK STATISTIC SUBSYSTEM (NES)
PRODUCT SPECIFICATION…02……02…FK 7809
T̲A̲B̲L̲E̲ ̲O̲F̲ ̲C̲O̲N̲T̲E̲N̲T̲S̲
1 SCOPE .......................................
1
2 APPLICABLE DOCUMENTS ........................
2
2.1 ABBREVIATIONS ............................
3
3 NETWORK STATISTIC SUBSYSTEM (NES) Overview ..
4
3.1 FUNCTIONS ................................
4
3.2 SUBSYSTEM OVERVIEW BLOCK DIAGRAM .........
5
3.3 DESIGN OVERVIEW ..........................
7
3.3.3 Incoming Statistics for NES .......... 10
3.4 VISUAL TABLE OF CONTENTS ................. 14
3.5 SUBSYSTEM OVERVIEW HIPO DIAGRAM .......... 16
4 DETAILED SUBSYSTEM DESIGN ................... 18
4.1 INTRODUCTION ............................. 18
4.2 DATA COLLECTION MODULE (DCM) ............. 19
4.2.1 Introduction ......................... 19
4.2.2 Module Description ................... 19
4.2.3 HIPO Chart ........................... 22
4.2.4 Summary Description .................. 26
4.2.5 Data Description ..................... 28
4.2.6 I/F Description ...................... 29
4.3 STATISTIC GENERATION MODULE (SGM) ........ 30
4.3.1 Introduction ......................... 30
4.3.2 Module Description ................... 30
4.3.3 HIPO Chart ........................... 32
4.3.4 Summary Description .................. 36
4.3.5 Data Description ..................... 39
4.3.6 I/F Description ...................... 39
4.4 DUMP STATISTIC MODULE (DSM) .............. 40
4.4.1 Introduction ......................... 40
4.4.2 Module Description ................... 40
4.4.3 HIPO Chart ........................... 42
4.4.4 Summary Description .................. 45
4.4.5 Data Description ..................... 48
4.4.6 I/F Description ...................... 48
5100A/aml…02…FIX/1162/PSP/0069
…02…APE/840622…02……02… iv
FIKS NETWORK STATISTIC SUBSYSTEM (NES)
PRODUCT SPECIFICATION…02……02…FK 7809
T̲A̲B̲L̲E̲ ̲O̲F̲ ̲C̲O̲N̲T̲E̲N̲T̲S̲
5 STORAGE ALLOCATION ......................... 49
6 PERFORMANCE CHARACTERISTICS ................ 50
7 LIMITATIONS ................................ 51
8 ERROR LOCATIONS ............................ 52
9 LISTING REFERENCE .......................... 55
10 QUALITY ASSURANCE .......................... 56
11 PREPARATIONS FOR DELIVERY .................. 57
12 NOTES ...................................... 58
12.1 MODULE GENERATION ....................... 58
12.2 EXECUTION CONSIDERATIONS ................ 58
12.3 RECOVERY/CHECKPOINT - RESTART ........... 59
1 S̲C̲O̲P̲E̲
The aim of this document is to describe the Network
Statistic Subsystem.
The purpose of the NES is to collect and store statistical
data record on a statistical data file.
On request generate 24 hour MEDE statistic or dump
statistic data record to statistical data file on floppy
disc.
The NES is only implemented at the two SCC's and executing
under control of the NSC subsystem.
2 A̲P̲P̲L̲I̲C̲A̲B̲L̲E̲ ̲D̲O̲C̲U̲M̲E̲N̲T̲S̲
1) CR80 AMOS Kernel
Product Specification
CSS/302/PSP/0008
2) CR80 AMOS I/O System
Product Specification
CSS/006/PSP/0006
3) CR80 AMOS File Management System
System Product Specification
CSS/920/SPS/0001
4) FIKS System PSP
FIX/1000/PSP/0038
5) FIKS Data Interface Reference
FIX/0100/MAN/0004
6) MTCB Monitor,
FIX/1256/PSP/0066
7) QACCESS Procedure
FIX/1256/PSP/0078
8) SCCM Subsystem PSP
FIX/1266/PSP/0089
9) HSP Subsystem PSP
FIX/1161/PSP/0051
10) TEPINT Background I/F Submodule
FIX/1364/PSP/0101
11) FIKS ESP SYSTEM
FIX/1105/PSP/0046
12) EVA Subsystem PSP
FIX/1161/PSP/0047
13) FIKS FIle Generators PSP
FIX/1200/PSP/0042
2.1 A̲B̲B̲R̲E̲V̲I̲A̲T̲I̲O̲N̲S̲
Refer to FIKS Data Interface Reference
Special Abbreviations:
NES Network Statistic Subsystem
DCM Data Collection Module
SGM Statistic Generation Module
DSM Dump Statistic Module
SDF Statistic Data File (Base)
3 N̲E̲T̲W̲O̲R̲K̲ ̲S̲T̲A̲T̲I̲S̲T̲I̲C̲ ̲S̲U̲B̲S̲Y̲S̲T̲E̲M̲ ̲(̲N̲E̲S̲)̲ ̲O̲v̲e̲r̲v̲i̲e̲w̲
3.1 F̲U̲N̲C̲T̲I̲O̲N̲S̲
The Network Statistic Subsystem (NES) at the System
Control Center (SCC) provides the following functions:
1) S̲t̲a̲t̲i̲s̲t̲i̲c̲a̲l̲ ̲D̲a̲t̲a̲ ̲C̲o̲l̲l̲e̲c̲t̲i̲o̲n̲ ̲a̲n̲d̲ ̲S̲t̲o̲r̲a̲g̲e̲
It receives statistical reports hourly or event
statistical reports from the Node/MEDE's or from
the SCC internally. The statistical data are then
stored in the Statistical Data Base (SDF) on disc.
2) G̲e̲n̲e̲r̲a̲t̲i̲o̲n̲ ̲(̲o̲n̲ ̲r̲e̲q̲u̲e̲s̲t̲)̲ ̲o̲f̲ ̲t̲h̲e̲ ̲2̲4̲ ̲H̲o̲u̲r̲ ̲M̲E̲D̲E̲ ̲S̲t̲a̲t̲i̲s̲t̲i̲c̲
Upon request, the Statistic Generation Module is
activated to generate 24 hour MEDE statistic.
The statistic report is generated for the period
of 24 hours of preceding day, and the MEDE statistic
is distributed to the appropriate MEDE.
3) D̲u̲m̲p̲i̲n̲g̲ ̲S̲t̲a̲t̲i̲s̲t̲i̲c̲ ̲F̲i̲l̲e̲ ̲t̲o̲ ̲F̲l̲o̲p̲p̲y̲ ̲D̲i̲s̲c̲ ̲(̲o̲n̲ ̲r̲e̲q̲u̲e̲s̲t̲)̲
Upon the (on-line) request for dumping statistical
data file, statistical data are copied from the
SDF to the floppy disc.
3.2 S̲U̲B̲S̲Y̲S̲T̲E̲M̲ ̲O̲V̲E̲R̲V̲I̲E̲W̲ ̲B̲L̲O̲C̲K̲ ̲D̲I̲A̲G̲R̲A̲M̲
Figure 3.2-1 illustrated the flow of data and control
for each of the three functions supported by the NES.
All data enter the NES through the Network Supervision
and Control Subsystem (NSC) (1a). NSC places a MTCB
entry to NES.
Details described in Reference 6+7.
Statistic reports are extracted from the NS queue and
are stored in the SDF (ref. 5, sec. 11.10.5) according
to the type and the Day Time Group of the report (1b).
Data Collection & Storage Module then print the status
of the process on printer through log queue (1c).
The Statistic Generation Module (SGM) is activated
on operator's request (2a) to retrieve the MEDE statistic
information from the Statistical Data FIle (2b) and
to generate 24 hour MEDE statistic.
The MEDE statistics are then sent to the input queue
of NSC (2c) - the Control Message Queue (CM) for further
distribution. (Statistic Generation Module then print
the status of the process on printer through log queue
(2d)).
Statistic file is copied from the SDF to the floppy
disc (3a) upon the terminal operator's request (3b).
(Dump Statistic Module then prints the status of the
process on printer through queue (3c)).
Figure 3.2-1…01…Network Statistics Subsystem, Block Diagram
3.3 D̲E̲S̲I̲G̲N̲ ̲O̲V̲E̲R̲V̲I̲E̲W̲
The Network Statistic Subsystem (NES) collects statistical
data on an hourly basis. All statistical data are
stored on a disc file which in cyclic manner contains
statistical data records of up to the last 48 hours.
The NES provides the facility of generating a 24 hour
MEDE statistic. Further, it is possible to dump the
statistical file to a floppy disc file.
S̲t̲a̲t̲i̲s̲t̲i̲c̲a̲l̲ ̲D̲a̲t̲a̲ ̲C̲o̲l̲l̲e̲c̲t̲i̲o̲n̲ ̲a̲n̲d̲ ̲S̲t̲o̲r̲a̲g̲e̲
The Network Statistic Subsystem (NES) receives once
per hour statistical data records from NSC as illustrated
in Figure 3.3-2.
o C̲o̲n̲t̲r̲o̲l̲ ̲m̲e̲s̲s̲a̲g̲e̲s̲ containing statistical records,
the contents of which originate from Node/MEDE's
and are received indirectly from the Network Supervision
and Control (NSC). The control messages may originate
from:
- a Node
- a MEDE
- SIP (Narrative message statistics).
The recieved records are stored on a statistics
file which contains the latest 48 hours statistics
in a cyclic manner.
Each record contains the following information:
- Statistic type
- length of record
- Statistic data
- Day Time Group
2̲4̲ ̲H̲o̲u̲r̲ ̲M̲E̲D̲E̲ ̲S̲t̲a̲t̲i̲s̲t̲i̲c̲ ̲G̲e̲n̲e̲r̲a̲t̲i̲o̲n̲
The statistic is generated on-line when the supervisor
activates the procedure.
The statistic contains information about the released
and received messages for each Node/MEDE, and cover
the traffic for the preceeding day from 00.00 - 24.00
hour.
The statistic are after generation automatically distributed
to the appropriate Node/MEDE (CM queue).
D̲u̲m̲p̲ ̲o̲f̲ ̲S̲t̲a̲t̲i̲s̲t̲i̲c̲a̲l̲ ̲F̲i̲l̲e̲ ̲t̲o̲ ̲F̲l̲o̲p̲p̲y̲ ̲D̲i̲s̲c̲
The statistical files are dumped (on-line) to floppy
disc files when the supervisor activates the dump procedure.
This causes a copy of the statistical data record from
the preceeding day (00.00 - 24.00 hour) to be produced.
Figure 3.3-2…01…Network Statistics, Design Overview
o S̲D̲F̲ ̲F̲i̲l̲e̲s̲
Those files "Statistical Data Files" are used for
storage of statistical data. Statistical data,
i.e. hourly statistical reports or event statistic
reports, are stored in those files according to
their statistic type and day time group. Refer
to ref. (5), sec. 11.10.5 for detailed information.
3.3.3 I̲n̲c̲o̲m̲i̲n̲g̲ ̲S̲t̲a̲t̲i̲s̲t̲i̲c̲s̲ ̲f̲o̲r̲ ̲N̲E̲S̲
S̲I̲P̲ ̲S̲t̲a̲t̲i̲s̲t̲i̲c̲s̲
o N̲I̲C̲S̲-̲T̲A̲R̲E̲ ̲M̲e̲s̲s̲a̲g̲e̲ ̲F̲l̲o̲w̲
- Number of incoming messages (from NICS) per
precedence per hour.
- Number of outgoing messages (to NICS) per precedence
per hour.
o A̲C̲P̲ ̲F̲o̲r̲m̲a̲t̲ ̲C̲o̲n̲v̲e̲r̲s̲i̲o̲n̲s̲
- Number of messages converted from ACP to SMF.
- Average message delay to and from NICS-TARE,
i.e. DTG of oldest message in the NICS-TARE
and conversion queue.
- Number of messages converted from SMF to ACP.
- Number of messages in error on conversion per
precedence.
Refer to ref. (5), sec. 10.2.2.13
Table 3.3.3-1a,…01…Network Statistics Subsystem, Input Data List
M̲E̲D̲E̲ ̲S̲t̲a̲t̲i̲s̲t̲i̲c̲s̲
o M̲e̲s̲s̲a̲g̲e̲ ̲F̲l̲o̲w̲
- Messages released, i.e. class/precedence/No.
of messages/No. of ANO's/Total No. of characters.
- Messages received (from the trunk), i.e. class/precedence/No.
of messages/total No. of characters.
o S̲t̲o̲r̲a̲g̲e̲ ̲(̲H̲D̲B̲)̲ ̲S̲t̲a̲t̲i̲s̲t̲i̲c̲s̲
The DTG of the oldest message in the HDB per MEDE
(per hour) is collected.
o M̲e̲s̲s̲a̲g̲e̲ ̲F̲l̲o̲w̲ ̲S̲t̲a̲t̲i̲s̲t̲i̲c̲s̲
The NES collects statistical data for the following:
a) Print queue-length of the message queues in
the MEDE categorized by precedence per MEDE.
b) Number of mutilated messages per MEDE.
c) DTG of oldest message in print queue per precedence
per MEDE.
Refer to ref. (5), sec. 10.2.2.10 + sec. 10.2.2.11
Table 3.3.3-1b…01…Network Statistics Subsystem, Input Data List
N̲o̲d̲e̲ ̲S̲t̲a̲t̲u̲s̲/̲U̲S̲P̲ ̲P̲r̲o̲f̲i̲l̲e̲ ̲S̲t̲a̲t̲i̲s̲t̲i̲c̲s̲
o M̲a̲i̲n̲t̲e̲n̲a̲n̲c̲e̲ ̲S̲t̲a̲t̲i̲s̲t̲i̲c̲s̲
The following events are collected:
a) Trunk circuit outage (closed or failure)
b) Trunk circuit back in service (open)
c) Crypto failure (on/off)
Refer to ref. (5), sec. 10.2.2.4
o S̲e̲c̲u̲r̲i̲t̲y̲ ̲S̲t̲a̲t̲i̲s̲t̲i̲c̲s̲
- Security profiles up-dates (changes/added/deleted).
Refer to ref. (5), sec. 10.2.2.9
Table 3.3.3-1c…01…Network Statistics Subsystem, Input Data List
N̲o̲d̲e̲/̲T̲r̲u̲n̲k̲ ̲S̲t̲a̲t̲i̲s̲t̲i̲c̲s̲
o M̲e̲s̲s̲a̲g̲e̲ ̲F̲l̲o̲w̲
- Number of frames retransmitted per trunk per
hour.
- Trunk message load in characters per hour.
- Trunk queue length per precedence per hour.
- The DTG of the oldest message in trunk queue
per precedence per Node.
Refer to ref. (5), sec. 10.2.2.1
Table 3.3.3-1d…01…Network Statistics Subsystem, Input Data List
3.4 V̲I̲S̲U̲A̲L̲ ̲T̲A̲B̲L̲E̲ ̲O̲F̲ ̲C̲O̲N̲T̲E̲N̲T̲S̲
Figure 3.4-1 provides a visual table of contents of
the three functional categories that comprise the NES.
Figure 3.4-1…01…Network Statistics, Table of Contents
3.5 S̲U̲B̲S̲Y̲S̲T̲E̲M̲ ̲O̲V̲E̲R̲V̲I̲E̲W̲ ̲H̲I̲P̲O̲ ̲D̲I̲A̲G̲R̲A̲M̲
Figure 3.5-1 provides an overview of the functions
covered in the NES.
Figure 3.5-1…01…HIPO Diagrams for NES
4 D̲E̲T̲A̲I̲L̲E̲D̲ ̲S̲U̲B̲S̲Y̲S̲T̲E̲M̲ ̲D̲E̲S̲I̲G̲N̲
4.1 I̲N̲T̲R̲O̲D̲U̲C̲T̲I̲O̲N̲
The following describes each module enclosing the NES.
The modular breakdown of the main functions in the
NES has been given in Section 3, Network Statistics
Subsystem Overview.
The description of the modules gives the details of
the S/W structure of the modules reflecting the functional
requirements, it also describes the data and external
interfaces. The detials about the data and the interfaces
are described in ref. (5), ref. (6), ref. (7), and
ref. (8).
The three functions shown in Figure 3.4-1 are implemented
as three modules enclosed in three AMOS processes namely
the:
o Data Collection and Storage Process
(DCM-process)
o Generate Statistic Process
(SGM-process)
o Dump Statistic Process
(DSM-process)
D̲a̲t̲a̲ ̲C̲o̲l̲l̲e̲c̲t̲i̲o̲n̲ ̲&̲ ̲S̲t̲o̲r̲a̲g̲e̲ ̲P̲r̲o̲c̲e̲s̲s̲
This process encloses the Data Collection Module (DCM).
The process is queue driven, i.e. when the NSC enters
an element into the NES input queue, i.e. the NS queue,
the QACCESS invokes the DCM by means of a AMOS signal.
Once invoked, the DCM will serve the NS queue until
it is empty.
D̲u̲m̲p̲ ̲a̲n̲d̲ ̲G̲e̲n̲e̲r̲a̲t̲e̲ ̲S̲t̲a̲t̲i̲s̲t̲i̲c̲ ̲P̲r̲o̲c̲e̲s̲s̲e̲s̲
Those processes enclose the Dump Statistic Module (DSM)
and the Generate Statistic Module (GSM). The processes
are interactive processes executing under control of
the TEPINT Background I/F Submodule. Ref. (10). The
processes are invoked by a terminal operator entering
a command which is handles by the above mentioned modules.
4.2 D̲A̲T̲A̲ ̲C̲O̲L̲L̲E̲C̲T̲I̲O̲N̲ ̲M̲O̲D̲U̲L̲E̲ ̲(̲D̲C̲M̲)̲
4.2.1 I̲n̲t̲r̲o̲d̲u̲c̲t̲i̲o̲n̲
The purpose of this module is to collect statistical
reports either from the Node/MEDE's or form the SCC
internally.
The statistical reports are mainly received periodically,
i.e. once per hour, but also event statistical reports
are received, i.e. report sent on an event occuring
within the FIKS Network.
Further, the purpose of the DCM is to store the contents
of the statistical report on a Statistical Data Base
(SDF) in a way which makes it possible off-line to
genrate Network Statistics, based on these data records.
4.2.2 M̲o̲d̲u̲l̲e̲ ̲D̲e̲s̲c̲r̲i̲p̲t̲i̲o̲n̲
The NES will once per hour receive statistical reports
from all Node/MEDE's in the FIKS Network and from the
Active SIP at the collocated Node/MEDE.
The statistical reports are received as a queue elements
in the NS queue. The queue elements point to a MTCB
which again points to the control messages on the IMF
or the PDB file. The control messages, i.e. the statistical
reports contain:
o Sampled counters
o Snapshot of queues
o Statistical events
S̲a̲m̲p̲l̲e̲d̲ ̲C̲o̲u̲n̲t̲e̲r̲s̲
Statistical counters are received from the Node/MEDE
about:
o Message Flow
o Trunk Load
o Retransmission on Trunks.
and from SIP about:
o Converted Messages
o Converted Messages in Error
These counters will be reset if the Node/MeDE performs
a restart or a switchover and each midnight (0…0e…00…0f… hour).
S̲n̲a̲p̲s̲h̲o̲t̲ ̲o̲f̲ ̲Q̲u̲e̲u̲e̲s̲
Snapshot received from the Node/MEDE's and the SCC
about queues are absolute values. This includes snapshot
of:
o Print Queues
o Trunk Queues
S̲t̲a̲t̲i̲s̲t̲i̲c̲a̲l̲ ̲E̲v̲e̲n̲t̲s̲
Statistical event reports can be received any time
(when the event is occurring). This means one event
results in one report.
S̲t̲o̲r̲a̲g̲e̲ ̲o̲f̲ ̲S̲t̲a̲t̲i̲s̲t̲i̲c̲a̲l̲ ̲D̲a̲t̲a̲ ̲R̲e̲c̲o̲r̲d̲s̲
Statistical data records are mainly copies of those
control messages released to the SCC by the originator.
A record header is added to the control message.
This header contains information about the originator,
time of release, type and subtype of message. The
information is used later on when statistical reports
are generated and sent back to the originators. A
"file header" for each kind of record keeps track of
which record was last stored and when it was stored.
For detailed information refer to ref. (5), sec. 11.10.5.
The following is a list of those records that are received
by the DCM and in which files they are stored:
1) Node Statistical Records
- Hourly received. "Node Statistics" - ref.
(5), sec. 10.2.2.1.
Stored in file: a *MOVHEAD*SDF.D*NSF
2) MEDE Hourly Records
- Hourly received "MEDE Hourly Reprots" - ref.
(5), sec. 10.2.2.11.
Stored in file: a *MOVHEAD*SDF.D*MHF
3) MEDE Statistical Records
- Hourly recieved "MEDE Statistics" - ref. (5),
sec. 10.2.2.10.
Stored in file a *MOVHEAD*SDF.D*MSF
4) SIP Records
- Hourly received "ACP127 and N/T Statistics"
- ref. (5), sec. 10.2.2.13.
Stored in file: a *MOVHEAD*SDF.D*SIF
5) USP Records
- Event based received "USP Profile Corrected/Inserted/Deleted"
- ref. (5), sec. 10.2.2.9.
Stored in file: a *MOVHEAD*SDF.D*USF
6) LOF Records
- Event based received "Local Network Status"
- ref. (5), sec. 10.2.2.4.
Stored in file: a *MOVHEAD*SDF.D*LOF
S̲t̲o̲r̲a̲g̲e̲ ̲o̲f̲ ̲T̲y̲p̲e̲ ̲1̲ ̲t̲h̲r̲o̲u̲g̲h̲ ̲4̲
These records are stored in a file having a fixed number
of records - one entry per orginator per hour in a
48 hour period.
I.e. a full range of records covering the last 0…0e…00…0f…
- 24…0e…00…0f… hour period will always be available. The key
by storage of this type of records is the originators
release DTG (form the binary header in the control
message).
Key: = Remainder of ((DTG + 1/2 hour)/48)
If two records within one hour, by anomality, has been
received twice, the latest received will over write
the former. If no one is received within an hour,
this will be known indirectly via the DTG in the reocrd
header of the one stored 48 hours earlier.
S̲t̲o̲r̲a̲g̲e̲ ̲o̲f̲ ̲T̲y̲p̲e̲ ̲5̲ ̲+̲ ̲6̲
These types of records are stored in files having a
fixed number of records. (Current value is #400).
The records are stored in order of arrival. When end
of file is reached "WRAP-AROUND" is performed. This
means that the range of time for which these records
may be retrieved depends upon how often the initializing
events occur.
When the storage is executed, this event is logged
by enqueing the proper MTCB into the EVENT-queue.
Refer to ref. (5), sec. 6 + 7.1.2.2, ref. (9), ref.
(12).
4.2.3 H̲I̲P̲O̲ ̲C̲h̲a̲r̲t̲
HIPO chart that describes the statistical collection
module is shown below.
Data and file items that are references are described
in section 4.2.5.
Procedure referenced, not AMOS, is described in ref.
6 + 7.
Figure 4.2.3-1…01…HIPO Diagram for DCM
Figure 4.2.3-2
HIPO Diagram for DCM
Figure 4.2.3-3
HIPO Diagram for DCM
4.2.4 S̲u̲m̲m̲a̲r̲y̲ ̲D̲e̲s̲c̲r̲i̲p̲t̲i̲o̲n̲
Figure 4.2.4-1 illustrates the flow of data and control
for the function supported by the data collection module.
1) The NSC enqueues a control message containing a
statistical report to the NES-DCM.
2) If the queue is empty, the QACCESSS invokes the
NES-DCM with a signal.
3) The DCM dequeues the element.
4) The DCM reads the characteristica from the MTCB
and the binary header of the control message.
5) The DCM finds where to store the received report,
i.e. on the SDF.
6) The statistical report is stored according to time
or release.
Figure 4.2.4-1…01…NES-Data Collection Module, Block Diagram
4.2.5 D̲a̲t̲a̲ ̲D̲e̲s̲c̲r̲i̲p̲t̲i̲o̲n̲
External data structures used by the DCM.
1. AMOS system software data structures.
Ref. (1)+ (2) + (3).
2. FIKS Queues.
Ref. (5), sec. 6.
3. MTCB, FIKS message control blocks.
Ref. (5), sec. 7.1.
4. FIKS Control Message Layout.
Ref. (5), sec. 10.2.
5. SCCM Data Structures.
Ref. (10).
6. SDF-Data Base Layout.
Ref. (5), sec. 11.10.5.
Note: There exists a "SFD-Data-Base" - generator which
creates all the files in thge SDF-data-base. Refer
to ref. (13), sec. 3.2.2.
No exceptional internal data structures have been used
by the DCM.
4.2.6 I̲/̲F̲ ̲D̲e̲s̲c̲r̲i̲p̲t̲i̲o̲n̲
The external interfaces of the DCM can be divided into:
o NSC - NES interface
o NES - HSP interface
N̲S̲C̲ ̲-̲ ̲N̲E̲S̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲
The NES communicates with the NSC when the NSC delivers
statistical data records from the network or from the
SCC internally. The NES is invoked when the NSC, by
means of QACCESS, enters elements in the empty NES
input queue - the NS queue.
Through QACCESS and MTCB monitor calls, the NES can
locate statistic data record in the PDB file. The
statistic data received by NES are the same as the
data that NSC receives from the Node/MEDE's or the
SCC internally. The NES will serve its input queue
until it is empty.
N̲E̲S̲ ̲-̲ ̲H̲S̲P̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲
The NES interfaces to the HSP for the purpose of logging
on the logprinter.
This interface is executed by means of the log queue
and pseudo MTDB's. The interface is handled by the
QACCESS and the MTCB monitor.
Refer to ref. (6) + (7).
4.3 S̲T̲A̲T̲I̲S̲T̲I̲C̲ ̲G̲E̲N̲E̲R̲A̲T̲I̲O̲N̲ ̲M̲O̲D̲U̲L̲E̲ ̲(̲S̲G̲M̲)̲
4.3.1 I̲n̲t̲r̲o̲d̲u̲c̲t̲i̲o̲n̲
The purpose of this module is generation of a 24 hour
MEDE statistic report on request.
A generate statistic request is entered via an interactive
command. Upon completion of statistic generation,
the MEDE statistics are handed to the NSC subsystem
which then handles the distribution to the appropriate
MEDEs.
The SGM process is an interactive process running under
control of the TEPINT Background I/F Submodule.
4.3.2 M̲o̲d̲u̲l̲e̲ ̲D̲e̲s̲c̲r̲i̲p̲t̲i̲o̲n̲
The SGM module gains control when the appropriate interactive
command is entered from one of the three interactive
terminals at the SCC.
The result of the interactive commands is a 24 MEDE
statistic report for each of the MEDEs in the FIKS
network.
The statistic report is generated for the period from
00.00 to 24.00 hour of the preceding day on the basis
of the statistic reports received by the DCM module.
The terminal operator will in case were he enters
the command shortly after the period of the preceeding
day has completed, receive a warning ("LAST RECORD
MAY BE MISSING") that the statistical report may be
generated based on statistical data where by the last
record is missing. The last statistical data record
for a given period may arrive when a new period has
begun due to network delay.
The statistical reports, i.e. control messages contain
binary information. The statistical report will on
request be printed on the receiving MEDE. This means
that the formatting of the statistical report takes
place in the MEDE. The receiving subsystem at the
MEDE is the SFS.
The statistical report contains the following binary
information:
o M̲e̲s̲s̲a̲g̲e̲s̲ ̲R̲e̲l̲e̲a̲s̲e̲d̲
The number of messages released per class per precedence
together with total number of address numbers,
ANO (Action + INFO) and total number of characters
of released messages.
These items are found in the MSF-file, ref. (5),
sec. 10.2.2.10, item MESMO .
o M̲e̲s̲s̲a̲g̲e̲s̲ ̲R̲e̲c̲e̲i̲v̲e̲d̲
The number of messages received from the network
per class and precedence together with the total
number of characters received from the network.
These items are found in the NSF-file, ref. (5),
sec. 10.2.2.1, last item.
Layout for the 24 hour MEDE stat is described in ref.
(5), sec. 10.2.1.4.2.
The statistical report for a MEDE is generated as follows:
All records in the files (NSF/MSF) belonging to the
MEDE and concerning the previous day (hour 0-23/24-47)
are scanned starting with the latest hour and ending
with earliest. If the record is too old, i.e. if the
DTG in the record header is older than the oldest DTG
in the affected period (no record has been received),
then the record is ignored. If the previous record
was of "Reset type" (indicated by the subtype in the
record header) then all the single items are added
to those already updated (the items are summarized).
This scheme is used to ensure valid statistics even
if a Node/MEDE had been restarted or been out of the
network for a while.
If, as a result of the scanning, no useful (too old)
records are found, then no report is generated for
this particular Node/MEDE and the operator is informed
by a display on the console:
"NO STATISTIC FOR MEDE X".
When generated, the report will be written into a control
message placed on a PDB-file. This message is then
by use of the MTCB-, QACCESS- and SCCM-procedures (ref.
(6) + (7) + (8)) be enqueued to the NSC subsystem,
which will see to it that via the FIKS networks it
will be distributed to the proper Node/MEDE.
The event of generating a statistic report is logged
by queing the proper MTCB into the EVENT-queue. Ref.
(5), sec. 6 + 7.1.2.2, Ref. (9) + (12).
4.3.3 H̲I̲P̲O̲ ̲C̲h̲a̲r̲t̲
HIPO chart that describes the statistical generation
module is shown below.
Data and file items that are referenced are described
in section 4.3.5.
Procedures referenced, not AMOS procedures, are described
in ref. 6 + 7 + 8.
Figure 4.3.3-1
HIPO Diagram for SGM
Figure 4.3.3-2…01…HIPO Diagram for SGM
Figure 4.3.3-3…01…HIPO Diagram for SGM
4.3.4 S̲u̲m̲m̲a̲r̲y̲ ̲D̲e̲s̲c̲r̲i̲p̲t̲i̲o̲n̲
Figure 4.3.4-1 illustrates the flow of data and control
for the function supported by the statistical generation
module.
1) The generate MEDE statistic command is entered
via an interactive terminal.
2) From the time the file partioned is found.
3) The statistical data are extracted from disc and
the statistic are generated.
4) Via the MTCB monitor file space for the statistical
reports are allocated on the PDB file.
5) The statistics are written into a control message,
which is intermediate stored on the PDB file.
6) the 24 hour statistics file is delivered to the
NSC by entering the MTCB referenced into the CM
by means of QACCESS.
Figure 4.3.4-1…01…SGM - Statistical Generation Module, Block Diagram
Figure 4.3.4-2…01…Flow Chart for Statistic Generation Progress
4.3.5 D̲a̲t̲a̲ ̲D̲e̲s̲c̲r̲i̲p̲t̲i̲o̲n̲
The data structures used by the SGM-process is also
used by the DCM-process, therefore, refer to section
4.2.5.
Re. layout of 24 hour MEDE-statistic refer to ref.
(5), sec. 10.2.1.4.2.
4.3.6 I̲/̲F̲ ̲D̲e̲s̲c̲r̲i̲p̲t̲i̲o̲n̲
The external interfaces of the SGM can be divided into:
o NES - NSC interface
o TEPINT BG I/F - NES interface
N̲E̲S̲ ̲-̲ ̲N̲S̲C̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲
This interface is executed by means of QACCESS and
the MTCB monitor calls in the Control Message (CM)
queue. The NES is invoked when the request for 24
MEDE stat. is entered. This command results in outputing
24 hour MEDE statistic to the input queue of the NSC
- the CM queue.
T̲E̲P̲I̲N̲T̲ ̲B̲G̲ ̲I̲/̲F̲ ̲-̲ ̲N̲E̲S̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲
This interface is executed by means of call to the
SCCM-procedures VDUIO, GETCMD, ref. (8).
By receiving the GMS command, the TEPINT BG I/F will
dispatch control to the SGM module. The SGM will now
execute directly I/O on the VDU by means of the two
above-mentioned procedures. By completion, the SGM
will return to the TEPINT BG I/F.
4.4 D̲U̲M̲P̲ ̲S̲T̲A̲T̲I̲S̲T̲I̲C̲ ̲M̲O̲D̲U̲L̲E̲ ̲(̲D̲S̲M̲)̲
4.4.1 I̲n̲t̲r̲o̲d̲u̲c̲t̲i̲o̲n̲
The purpose of this module is to dump the SDF-files,
statistical data base, on the MMD disc to statistical
data files on the floppy discs.
The statistical data files dumped is hereby only the
part from the preceeding day, i.e. from 00.00 to 24.00
hour. A dump statistic file request is entered via
an interactive command and during the processing the
module will communicate with the operator about mount
and dismount of floppy disc.
The DSM process is an interactive process executing
under control of the TEPINT Background I/F Submodule.
4.4.2 M̲o̲d̲u̲l̲e̲ ̲D̲e̲s̲c̲r̲i̲p̲t̲i̲o̲n̲
The DSM module gains control when the appropriate interactive
command is entered from one of the three interactive
terminal at the SCC.
The result of the interactive command is a dump of
the SDF-records to floppy discs. Due to the size of
the SDF-files, the dump will be written to four floppy
discs with the following content:
1: NSF-file
2: MHF-file
3: MSF-file
4: SIF-, NSF-, LOF-file
The NSF-, MHF-, MSF- and SIF-files are copies of those
contained in the SDF data base, where only the records
belonging to the previous day is included. The USF-
and LOF-files are exact copies of those from the SDF
data base.
In case where the terminal operator initiates a dump
of the SDF data base close to midnight (shift in period),
he will receive a warning ("LAST RECORD MAY BE MISSING")
that the data dumped may not be complete, anyway.
A missing record will show up as and "too old" DTG
in the record header, ref. sec. 4.3.2.
The files are dumped to floppy discs in the following
way:
1) The operator is asked, by use of the SCCM-procedure
VDUIO, to mount the proper floppy discs with one
of the following display on the console:
'INSERT FLOPPY DISC FOR DUMP OF NSF-FILE'
'INSERT FLOPPY DISC FOR DUMP OF MHF-FILE'
'INSERT FLOPPY DISC FOR DUMP OF MSF-FILE'
'INSERT FLOPPY DISC FOR DUMP OF SIF, USF, LOF -
FILES'
2) The operator then inserts the floppy discs with
volume name: FLOPPY in the floppy drive and notifies
the system by keying in his "accept". If he does
not accept then the dumping is skipped. (Go to
point 6).
3) If the file already exists on the floppy discs,
it is deleted (REMOVED).
4) The file is created as CONTIGNOUS with optimal
SIZE (not bigger than needed).
5) The SDF-file (or part of it) is copied into the
newly created file.
6) If there is more files to be dumped then do so.
(Go to point 1).
This procedure is very sensible concerning operator
mistakes, therefore, special error handling has been
implemented. If an error in the processing occur,
(e.g. caused by an erroneous floppy disc) the DSM-process
may be restarted by use of the system operator commnad
'START DSM' - ref. (11), sec. 3.2. After being restarted
'LOCAL ̲FIX ̲UP' is performed so that the DSM-process
is ready to repeat the dumping procedure from the beginning.
When the dumping is finished this event is logged by
enqueueing the proper MTCB into the EVENT-queue. Refer
to ref. 5), sec. 6 + 7.1.2.2, ref. (9) + (12).
4.4.3 H̲I̲P̲O̲ ̲C̲h̲a̲r̲t̲
HIPO chart that describes the dump statistical file
module is shown below.
Data and file items that are referenced are described
in section 4.4.5.
Procedures referenced, not AMOS procedures, are described
in ref. 6 + 7 + 8.
Figure 4.4.3-1
HIPO Diagram for DSM
Figure 4.4.3-2
HIPO Diagram for DSM
4.4.4 S̲u̲m̲m̲a̲r̲y̲ ̲D̲e̲s̲c̲r̲i̲p̲t̲i̲o̲n̲
Figure 4.4.4-1 illustrates the flow of data and control
for the function supported by the dump statistic module.
1) The dump statistical file to floppy disc command
is entered via an interactive terminal.
2) The operator is requested to mount the floppy disc.
3) The NSF-file is removed/created on the floppy disc.
4) The current day is determined to calculate the
partition to be dumped and the file is opened.
5) The file on the FMS is copied to the floppy disc.
6) The file is closed.
7) The operator is requested to dismount the floppy
disc.
8) 2 to 7 is repeated for the MHF file.
9) 2 to 7 is repeated for the MSF file.
10) 2 to 7 is repeated for the SIF-, USF-, LOF-file.
Figure 4.4.4-1…01…DSM - Dump Statistical File Module, Block Diagram
Figure 4.4.4-2…01…Flow Chart for Dump Statistic Process
4.4.5 D̲a̲t̲a̲ ̲D̲e̲s̲c̲r̲i̲p̲t̲i̲o̲n̲
The data structures used by the DSM process is also
used by the DCM-process, therefore, refer to section
4.2.5.
Re. layout of SDF dump files (floppy files) refer to
ref. (5), sec. 11.10.5.
4.4.6 I̲/̲F̲ ̲D̲e̲s̲c̲r̲i̲p̲t̲i̲o̲n̲
The only external interface of the DSM is the
o TEPINT BG I/F - NES interface
T̲E̲P̲I̲N̲T̲ ̲B̲G̲ ̲I̲/̲F̲ ̲-̲ ̲N̲E̲S̲ ̲i̲n̲t̲e̲r̲f̲a̲c̲e̲
This interface is executed by means of the calls to
the SCCM-procedures VDUIO, GETCMD, ref. (8). The DSM
hereby prompt the terminal operator for input.
The prompt concern:
o Mount/Dismount floppy disc
o Error codes
By receiving the DSF command, the TEPINT BG I/F will
dispatch control to the DSM module. The DSM now execute
direct terminal I/O on the VDU as described above.
By completion. the DSM will return control to the TEPING
BG I/F.
5 S̲T̲O̲R̲A̲G̲E̲ ̲A̲L̲L̲O̲C̲A̲T̲I̲O̲N̲
The modules included in the NES-subsystem has the following
memory claims (approximately) in words
M̲o̲d̲u̲l̲e̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲^̲ ̲P̲r̲o̲g̲r̲a̲m̲ ̲ ̲ ̲ ̲^̲ ̲P̲r̲o̲c̲e̲s̲s̲ ̲ ̲
^ ^
DCM ^ 880 ^ 1370
SGM ^ 690 ^ 1880
DSM ^ 920 ^ 1980
^ ^
Program header is not included in program. process
header is included in process.
6 P̲E̲R̲F̲O̲R̲M̲A̲N̲C̲E̲ ̲C̲H̲A̲R̲A̲C̲T̲E̲R̲I̲S̲T̲I̲C̲S̲
The processes that make up the NES are all activated
by events; DCM at arrival of statistic reports and
DSM, SGM once each 24 hours when statistics are issued
or dumped. This, together with the fact that statistic
is of secondary importance, ensures that no essential
timing constrain exists.
7 L̲I̲M̲I̲T̲A̲T̲I̲O̲N̲S̲
No vital limitation exists.
8 E̲R̲R̲O̲R̲ ̲L̲O̲C̲A̲T̲I̲O̲N̲S̲
L̲a̲b̲e̲l̲ ̲ ̲ ̲ ̲ ̲ ̲R̲a̲i̲s̲e̲d̲ ̲b̲y̲ ̲(̲c̲a̲l̲l̲ ̲o̲f̲)̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲C̲o̲m̲m̲e̲n̲t̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
^ ^
D̲C̲M̲ ^ ^
^ ^
1 ^ MON (IO, MODIFYBYTES) ^ storage of record
2 ^ MON (IO, READBYTES) ^ of RECORD HEADER
3 ^ MON (CONVDTG) ^ of DTG to ASCII
4 ^ MON (IO, MODIFYBYTES) ^ at update of RECORD
HEADER
5 ^ MON (GETDTG) ^ at update of FILE
HEADER
6 ^ MON (IO, MODIFYBYTES) ^ at update of FILE
HEADER
7 ^ MON (IO, READBYTES) ^ of FILE HEADER
8 ^ MON (IO, GETROOT) ^ of MOVHEAD
9 ^ MON (IO, DESCENT) ^ to SDF.D
10 ^ MON (IO, LOOKUP) ^ of NSF-file
11 ^ MON (IO, LOOKUP) ^ of MHF-file
12 ^ MON (IO, LOOKUP) ^ of MSF-file
13 ^ MON (IO, LOOKUP) ^ of SIF-file
14 ^ MON (IO, LOOKUP) ^ of NSF-file
15 ^ MON (IO, LOOKUP) ^ of LOL-file
16 ^ MON (IO, DISMANTLE) ^ of SDF.D
17 ^ MTCBINIT ^ SCCM-procedure
18 ^ MON (QACCESS, READ ̲DEST)^ read input queue
19 ^ MON (MTCB, GETFILE) ^ of control message
20 ^ MON (IO, READBYTES) ^ of binary header
in
^ ^ control message
21 ^ illegal stat. kind ^ not expected
22 ^ MON (IO, READBYTES) ^ of control message
23 ^ MON (SCCM, GET ̲NM ̲IDB) ^
24 ^ INSERT ̲MTCB-use ^ at EVENT-logging
25 ^ INSERT ̲QE-use ^ at EVENT-logging
26 ^ MON (MTCB, RELEASE FILE)^ of control message
27 ^ MON (MTCB, RELEASE) ^ of control message
^ ^
L̲a̲b̲e̲l̲ ̲ ̲ ̲ ̲ ̲ ̲R̲a̲i̲s̲e̲d̲ ̲b̲y̲ ̲(̲c̲a̲l̲l̲ ̲o̲f̲)̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲C̲o̲m̲m̲e̲n̲t̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
^ ^
S̲G̲M̲ ^ ^
^ ^
1 ^ MON (IO, GETROOT) ^ of MOVHEAD
2 ^ MON (IO, DESCENT) ^ to SDF.D
3 ^ MON (IO, LOOKUP) ^ of NSF-/MSF-file
4 ^ MTCBINIT-use ^ SCCM-procedure
5 ^ MON (GETDTG) ^
6 ^ VDUIO-use ^ at WARNING
7 ^ MON (SCCM, GET ̲NM ̲IDA) ^
8 ^ MON (IO, READBYTES) ^ in NSF-/MSF-file
9 ^ VDUIO-use ^ at WARNING
10 ^ illegal NM ̲ID ^
11 ^ INSERT ̲MTCB-use ^ at generate stat.msg.
12 ^ MON (MTCB, CREATEFILE) ^ at generate stat.msg.
13 ^ MON (IO, MODIFYBYTES) ^ at generate stat.msg.
14 ^ INSERT ̲QE ̲RES-use ^ at generate stat.msg.
15 ^ MON (MTCB, RELEASEFILE) ^ at generate stat.msg.
16 ^ MON (MTCB, RELASE) ^ at generate stat.msg.
17 ^ INSERT ̲MTCB-use ^ at EVENT logging
18 ^ INSERT ̲QE ^ at EVENT logging
^ ^
L̲a̲b̲e̲l̲ ̲ ̲ ̲ ̲ ̲ ̲R̲a̲i̲s̲e̲d̲ ̲b̲y̲ ̲(̲c̲a̲l̲l̲ ̲o̲f̲)̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲C̲o̲m̲m̲e̲n̲t̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
^ ^
D̲S̲M̲ ^ ^
^ ^
1 ^ MON (IO, DISMANTLE) ^ of floppy-file
2 ^ MON (IO, MOUNT) ^ of FLOPPY-volume
3 ^ MON (IO, GETROOT) ^ of FLOPPY-volume
4 ^ MON (IO, DISMANTLE) ^ of a *MD*FLOPPY
5 ^ MON (IO, DISMOUNT) ^ of FLOPPY-volume
6 ^ MON (GETDTG) ^ at copy of file
7 ^ MON (IO, APPENDBYTES) ^ at copy of file
8 ^ MON (IO, READBYTES) ^ at copy of file
9 ^ MON (IO, APPENDBYTES) ^ at copy of file
10 ^ MON (IO, LOOKUP) ^ of file on FLOPPY
11 ^ MON (IO, REMOVE) ^ of file on FLOPPY
12 ^ MON (IO, DISMANTLE) ^ of file on FLOPPY
13 ^ MON (IO, CREATE) ^ of file on FLOPPY
14 ^ MON (IO, ENTERFILE) ^ of file on FLOPPY
15 ^ MON (IO, PROTECT) ^ of file on FLOPPY,
user 0
16 ^ MON (IO, PROTECT) ^ of file on FLOPPY,
user-1
17 ^ MON (IO, GETTROOT) ^ of MOVHEAD
18 ^ MON (IO, DESCENT) ^ to SDF.D
19 ^ MON (IO, LOOKUP) ^ of NSF-file
19 ^ MON (IO, LOOKUP) ^ of NSF-file
20 ^ MON (IO, LOOKUP) ^ of MHF-file
21 ^ MON (IO, LOOKUP) ^ of MSF-file
22 ^ MON (IO, LOOKUP) ^ of SIF-file
23 ^ MON (IO, LOOKUP) ^ of USF-file
24 ^ MON (IO, LOOKUP) ^ of LOF-file
25 ^ MON (IO, DISMANTLE) ^ of LSDF.D
26 ^ MON (GETDTG) ^
27 ^ MTCBINIT-use ^ SCCM-procedure
28 ^ VDUIO-use ^ at WARNING
29 ^ VDUIO-use ^ at WARNING
30 ^ INSERT ̲MTCB ^ at EVENT-logging
31 ^ INSERT ̲QE ^ at EVENT-logging
32 ^ VDUIO-use ^ operator guidance
33 ^ VDUIO-use ^ operator guidance
^ ^
9 L̲I̲S̲T̲I̲N̲G̲ ̲R̲E̲F̲E̲R̲E̲N̲C̲E̲
Source listings and linker list may be obtained from
FIXLIB. Ref. to SCCLDD.
10 Q̲U̲A̲L̲I̲T̲Y̲ ̲A̲S̲S̲U̲R̲A̲N̲C̲E̲
Qualifications Tests:
M̲o̲d̲u̲l̲e̲ ̲T̲e̲s̲t̲:̲ Refer to
NES Subsystem Test Report
FIX/1162/TRP/0062
S̲y̲s̲t̲e̲m̲ ̲I̲n̲t̲e̲g̲r̲a̲t̲i̲o̲n̲ ̲T̲e̲s̲t̲: Refer to
System Test Report for S060 -
SCC - N/M Statistics Handling
FIX/0000/TRP/0090
11 P̲R̲E̲P̲A̲R̲A̲T̲I̲O̲N̲S̲ ̲F̲O̲R̲ ̲D̲E̲L̲I̲V̲E̲R̲Y̲
Do as stated in file 'INFORMATION' in the last delivery
of the NES-directory to FIXLIB.
12 N̲O̲T̲E̲S̲
12.1 M̲O̲D̲U̲L̲E̲ ̲G̲E̲N̲E̲R̲A̲T̲I̲O̲N̲
The NES is compiled by means of the SWELL compiler
CSS/415 and linked by means of the AMOS Linker CSS/416,
Refer to:
SWELL 80, Reference Manual
CSS/415/RFM/0002
CR80 AMOS SWELL Compiler, Users Manual
CSS/415/USM/0047
CR80 AMOS, Linker, Reference Manual
CSS/416/RFM/0003
CR80 AMOS, Linker, Users Manual
CSS/416/USM/0048
By using the command files as stated in the INFORMATION-file
in the last FIXLIB-delivery of NES it is possible to
generate all or a single module in the NES Subsystem.
12.2 E̲X̲E̲C̲U̲T̲I̲O̲N̲ ̲C̲O̲N̲S̲I̲D̲E̲R̲A̲T̲I̲O̲N̲S̲
As already indicated in sec. 6 the NES-processing is
of low priority compared to the rest of the processing
in the SCC-installation. That makes the processes
candidates for being executed as background tasks ref.
(11), sec. 3.3.15. Furthermore the sizing limitations
for being runned as background task (ref. (11), sec.
3.4.3) is fulfilled for all the NES-processes.
Therefore, it is obvious that they shall be executed
as background tasks in the FIKS operational system
and that the maintainer of the NES must have this in
mind at future updates.
12.3 R̲E̲C̲O̲V̲E̲R̲Y̲/̲C̲H̲E̲C̲K̲P̲O̲I̲N̲T̲ ̲-̲ ̲R̲E̲S̲T̲A̲R̲T̲
The processing in the NES Subsystem is independent
of, the system is recovered or not, at restart. The
only data that determine the processing, is placed
in the SDF-data-base, and this has no need for checkpointing/recovery.
