top - download
⟦a3278bce6⟧ Wang Wps File
Length: 58158 (0xe32e)
Types: Wang Wps File
Notes: FIX/1200/PSP/0042
Names: »5030A «
Derivation
└─⟦4d5d1ede7⟧ Bits:30006147 8" Wang WCS floppy, CR 0342A
└─ ⟦this⟧ »5030A «
WangText
9…00……00……00……00…H…0a……00……00…H…0b…H…0d…H…0f…G…08…G…01…F…0a…F
E…0c…E…05…D…0b…D…0e…D
D…05…C…0a…C…0e…C…02…C…05…B…08…B…0c…B…00…B A…08…A…0c…A…00…A …86…1 …02… …02… …02…
5030A/heh…02…FIX/1200/PSP/0042
…02……0f……0f…REV/840504 #
FIKS FILE GENERATORS PRODUCT SPECIFICATION
…02… …02…FK7809 …0e……0e…
FIKS FILE GENERATORS
PRODUCT SPECIFICATION
FIX/1200/PSP/0042
Flemming Revens
Ole Eskedal
AMC (6), APE, REV, LOL, LU, Conf.Mgr., File
…0e… S/W Manager 840504
1
840504
Conf. Mgmt 840504…0f…
5030A/heh…02… FIX/1200/PSP/0042
…02……0f……0f… REV/840504 ii
FIKS FILE GENERATORS PRODUCT SPECIFICATION
…02… …02… FK7809 …0e……0e…
1 840504 All First issue of document
5030A/heh…02…FIX/1200/PSP/0042
…02……0f……0f…REV/840504 iii
FIKS FILE GENERATORS PRODUCT SPECIFICATION
…02… …02… FK7809…0e……0e…
T̲A̲B̲L̲E̲ ̲O̲F̲ ̲C̲O̲N̲T̲E̲N̲T̲S̲
1 SCOPE .......................................
1
1.1 INTRODUCTION .............................
1
1.2 ABBREVIATIONS ............................
1
2 APPLICABLE DOCUMENTS ........................
2
3 FILE GENERATORS .............................
4
3.1 GENERATORS FOR CRITICAL REGION FILES .....
4
3.1.1 CONF .................................
5
3.1.1.1 Module Specification .............
5
3.1.1.2 Functional Capabilities ..........
5
3.1.1.3 Prerequisites ....................
5
3.1.1.4 Installation .....................
5
3.1.2 TCT ..................................
6
3.1.2.1 Module specification .............
6
3.1.2.2 Functional Capabilities .........
6
3.1.2.3 Prerequisites ....................
6
3.1.2.4 Installation .....................
6
3.1.3 CRT ..................................
7
3.1.3.1 Module Specification .............
7
3.1.3.2 Functional Capabilities ..........
7
3.1.3.3 Prerequisites ....................
7
3.1.3.4 Installation .....................
7
3.1.4 PTT ..................................
8
3.1.4.1 Module Specification .............
8
3.1.4.2 Functional Capabilities ..........
8
3.1.4.3 Installation .....................
8
3.1.5 SSLP .................................
9
3.1.5.1 Module Specification .............
9
3.1.5.2 Functional Capabilities ..........
9
3.1.5.3 Prerequisites ....................
9
3.1.5.4 Installation .....................
9
3.1.6 PDPTAB ............................... 10
3.1.6.1 Module Specification ............. 10
3.1.6.2 Functional Capabilities .......... 10
3.1.6.3 Prerequisites .................... 10
3.1.6.4 Installation ..................... 10
5030A/heh…02…FIX/1200/PSP/0042
…02……0f……0f…REV/840504 iv
FIKS FILE GENERATORS PRODUCT SPECIFICATION
…02… …02…FK7809 …0e……0e…
T̲A̲B̲L̲E̲ ̲O̲F̲ ̲C̲O̲N̲T̲E̲N̲T̲S̲
3.1.7 SYNR ................................. 11
3.1.7.1 Module Specification ............. 11
3.1.7.2 Functional Capabilities .......... 11
3.1.7.3 Prerequisites .................... 11
3.1.7.4 Installation ..................... 11
3.1.8 SYNT ................................. 12
3.1.8.1 Module Specification ............. 12
3.1.8.2 Functional capabilities .......... 12
3.1.8.3 Prerequisities ................... 12
3.1.8.4 Installation ..................... 12
3.1.9 CLS 1 ................................ 13
3.1.9.1 Module Specification ............. 13
3.1.9.2 Functional Capabilities .......... 13
3.1.9.3 Prerequisites .................... 13
3.1.9.4 Installation ..................... 13
3.1.10 CLS2 ............................... 14
3.1.10.1 Module Specification ........... 14
3.1.10.2 Functional Capabilities ........ 14
3.1.10.3 Prerequisites .................. 14
3.1.10.4 Installation ................... 14
3.1.11 SPEC ............................... 15
3.1.11.1 Module Specification ........... 15
3.1.11.2 Functional Capabilities ........ 15
3.1.11.3 Prerequisites .................. 15
3.1.11.4 Installation ................... 15
3.1.12 STEVTB ............................. 16
3.1.12.1 Module Specification ........... 16
3.1.12.2 Functional Capabilities ........ 16
3.1.12.3 Prerequisites .................. 16
3.1.12.4 Installation ................... 16
3.1.13 STAT ............................... 17
3.1.13.1 Module Specification ........... 17
3.1.13.2 Functional Capabilities ........ 17
3.1.13.3 Prerequisites .................. 17
3.1.13.4 Installation ................... 17
5030A/heh…02…FIX/1200/PSP/0042
…02……0f……0f…REV/840504 v
FIKS FILE GENERATORS PRODUCT SPECIFICATION
…02… …02…FK7809 …0e……0e…
T̲A̲B̲L̲E̲ ̲O̲F̲ ̲C̲O̲N̲T̲E̲N̲T̲S̲
3.1.14 TXTLNS ............................. 18
3.1.14.1 Module Specification ........... 18
3.1.14.2 Functional Capabilities ........ 18
3.1.14.3 Prerequisites .................. 18
3.1.14.4 Installation ................... 18
3.1.15 SMAILB ............................. 19
3.1.15.1 Module Specification ........... 19
3.1.15.2 Functional Capabilities ....... 19
3.1.15.3 Prerequisites .................. 19
3.1.15.4 Installation ................... 19
3.1.16 CMAILB ............................. 20
3.1.16.1 Module Specification ........... 20
3.1.16.2 Functional Capabilities ........ 20
3.1.16.3 Prerequisites .................. 20
3.1.16.4 Installation ................... 20
3.1.17 SCCCRT ............................. 21
3.1.17.1 Module Specification ........... 21
3.1.17.2 Functional Cpapibilities ....... 21
3.1.17.3 Prerequisites .................. 21
3.1.17.4 Installation ................... 21
3.1.18 SCCPTT ............................. 22
3.1.18.1 Module Specification ........... 22
3.1.18.2 Functional Capabilities ........ 22
3.1.18.3 Prerequisites .................. 22
3.1.18.4 Installation ................... 22
3.1.19 SCCSSLP ............................ 23
3.1.19.1 Module Specification ........... 23
3.1.19.2 Functional Capabilities ........ 23
3.1.19.3 Prerequisites .................. 23
3.1.19.4 Installation ................... 23
3.1.20 FNC ................................ 24
3.1.20.1 Module Specification ........... 24
3.1.20.2 Functional Capabilities ........ 24
3.1.20.3 Prerequisites .................. 24
3.1.20.4 Installation ................... 24
5030A/heh…02…FIX/1200/PSP/0042
…02……0f……0f…REV/840504 vi
FIKS FILE GENERATORS PRODUCT SPECIFICATION
…02… …02…FK7809 …0e……0e…
T̲A̲B̲L̲E̲ ̲O̲F̲ ̲C̲O̲N̲T̲E̲N̲T̲S̲
3.1.21 FST ................................ 25
3.1.21.1 Module Specification ........... 25
3.1.21.2 Functional Capabilities ........ 25
3.1.21.3 Prerequisites .................. 25
3.1.21.4 Installation ................... 25
3.1.22 FRD ................................ 26
3.1.22.1 Module Specification ........... 26
3.1.22.2 Functional Capabilities ........ 26
3.1.22.3 Prerequisites .................. 26
3.1.22.4 Installation ................... 26
3.1.23 FRT ................................ 27
3.1.23.1 Module Specification ........... 27
3.1.23.2 Functional Capabilities ........ 27
3.1.23.3 Prerequisites .................. 27
3.1.23.4 Installation ................... 27
3.1.24 CSMAILB ............................ 28
3.1.24.1 Module Specification ........... 28
3.1.24.2 Functional Capabilities ........ 28
3.1.24.3 Prerequisites .................. 28
3.1.24.4 Installation ................... 28
3.1.25 SSS ................................ 29
3.1.25.1 Module Specification ........... 29
3.1.25.2 Functional Capabilities ........ 29
3.1.25.3 Prerequisites .................. 29
3.1.25.4 Installation ................... 29
3.1.26 CLAS1 .............................. 30
3.1.26.1 Module Specification ........... 30
3.1.26.2 Functional Capabilities ........ 30
3.1.26.3 Prerequisites .................. 30
3.1.26.4 Installation ................... 30
3.1.27 CLAS2 .............................. 31
3.1.27.1 Module Specification ........... 31
3.1.27.2 Functional Capabilities ........ 31
3.1.27.3 Prerequisites .................. 31
3.1.27.4 Installation ................... 31
5030A/heh…02…FIX/1200/PSP/0042
…02……0f……0f…REV/840504 vii
FIKS FILE GENERATORS PRODUCT SPECIFICATION
…02… …02…FK7809 …0e……0e…
T̲A̲B̲L̲E̲ ̲O̲F̲ ̲C̲O̲N̲T̲E̲N̲T̲S̲
3.1.28 RITANO ............................. 32
3.1.28.1 Module Specification ........... 32
3.1.28.2 Functional Capabilities ........ 32
3.1.28.3 Prerequisites .................. 32
3.1.28.4 Installation ................... 32
3.1.29 SCCSYNR ............................ 33
3.1.29.1 Module Specification ........... 33
3.1.29.2 Functional Capabilities ........ 33
3.1.29.3 Prerequisites .................. 33
3.1.29.4 Installation ................... 33
3.1.30 SCCSYNT ............................ 34
3.1.30.1 Module Specification ........... 34
3.1.30.2 Functional Capabilities ........ 34
3.1.30.3 Prerequisites .................. 34
3.1.30.4 Installation ................... 34
3.1.31 TABUPD ............................. 35
3.1.31.1 Module Specification ........... 35
3.1.31.2 Functional Capabilities ........ 35
3.1.31.3 Prerequisites .................. 35
3.1.31.4 Installation ................... 35
3.2 GENERATION OF DISC RESIDENT FILES ........ 36
3.2.1 IMF .................................. 37
3.2.1.1 Module Specification ............. 37
3.2.1.2 Functional Capabilities .......... 37
3.2.1.3 Prerequisites .................... 37
3.2.1.4 Installation ..................... 37
3.2.2 MTF, MRF, DTGF ....................... 38
3.2.2.1 Module Specification ............. 38
3.2.2.2 Functional Capabilities .......... 38
3.2.2.3 Prerequisites .................... 38
3.2.3 SDF.D ................................ 39
3.2.3.1 Module Specification ............. 39
3.2.3.2 Functional Capabilities .......... 39
3.2.3.3 Prerequisites .................... 39
3.2.3.4 Installation ..................... 39
5030A/heh…02…FIX/1200/PSP/0042
…02……0f……0f…REV/840504 viii
FIKS FILE GENERATORS PRODUCT SPECIFICATION
…02… …02…FK7809 …0e……0e…
T̲A̲B̲L̲E̲ ̲O̲F̲ ̲C̲O̲N̲T̲E̲N̲T̲S̲
3.2.4 MJF ̲INIT ............................. 40
3.2.4.1 Module Specification ............. 40
3.2.4.2 Functional Capabilities .......... 40
3.2.3.3 Prerequisites .................... 40
3.2.4.4 Installation ..................... 40
3.2.5 SRS ̲CHECKP ........................... 41
3.2.5.1 Module Specification ............. 41
3.2.5.2 Functional Capabilities .......... 41
3.2.5.3 Prerequisites .................... 41
3.2.6 USP, SCCUSP .......................... 42
3.2.6.1 Module Specification ............. 42
3.2.6.2 Functional Capabilities .......... 42
3.2.6.3 Prerequisites .................... 42
3.2.6.4 Installation ..................... 42
3.2.7 NDF .................................. 43
3.2.7.1 Module Specification ............. 43
3.2.7.2 Functional Capabilities .......... 43
3.2.7.3 Prerequisites .................... 43
3.2.7.4 Installation ..................... 43
3.2.8 PDB .................................. 44
3.2.8.1 Module Specification ............. 44
3.2.8.2 Functional Capabilities ......... 44
3.1.8.3 Prerequisites .................... 44
3.2.9 CHECKP ̲FILE .......................... 45
3.2.9.1 Module Specification ............. 45
3.2.9.2 Functional Capabilities .......... 45
3.2.9.3 Prerequisites .................... 45
3.2.9.4 Installation ..................... 45
3.2.10 BGPS ̲FILE .......................... 46
3.2.10.1 Module Specification ........... 46
3.1.10.2 Functional Capabilities ........ 46
3.2.10.3 Prerequisites .................. 46
3.2.10.4 Installation ................... 46
5030A/heh…02…FIX/1200/PSP/0042
…02……0f……0f…REV/840504 ix
FIKS FILE GENERATORS PRODUCT SPECIFICATION
…02… …02…FK7809 …0e……0e…
T̲A̲B̲L̲E̲ ̲O̲F̲ ̲C̲O̲N̲T̲E̲N̲T̲S̲
3.2.11 RDF ................................ 47
3.2.11.1 Module Specification ........... 47
3.2.11.2 Functional Capabilities ........ 47
3.2.11.3 Prerequisites .................. 47
3.2.11.4 Installation ................... 47
3.2.12 TMF ................................ 48
3.2.12.1 Module Specification ........... 48
3.2.12.2 Functional Capabilities ........ 48
3.2.12.3 Prerequisites .................. 48
3.2.12.4 Installation ................... 48
3.3 PROCESSING ............................... 49
3.4 STORAGE ALLOCATION ....................... 50
3.5 PERFORMANCE CHARACTERISTICS .............. 51
3.6 LIMITATIONS .............................. 52
3.7 ERROR CODE/ERROR LOCATIONS ............... 53
3.8 PREPARATIONS FOR DELIVERY ................ 54
4 QUALITY ASSURANCE ........................... 55
4.1 QUALIFICATION TEST ....................... 55
5 NOTES ....................................... 56
1 S̲C̲O̲P̲E̲
The purpose of this document is to describe the generation
and installation of
- constant
- configuration and
- log
files in the FIKS-system.
1.1 I̲N̲T̲R̲O̲D̲U̲C̲T̲I̲O̲N̲
The main purpose of this document is to describe the
functionally capabilities of the filegenerators and
the principles in installing the files.
Only a brief description of the file contents and
their purpose in the FIKS-system is given herein.
For details please refer to the applicable documents
specified.
1.2 A̲B̲B̲R̲E̲V̲I̲A̲T̲I̲O̲N̲S̲
Please refer to ref. 1 chapter 1.2.
2 A̲P̲P̲L̲I̲C̲A̲B̲L̲E̲ ̲D̲O̲C̲U̲M̲E̲N̲T̲S̲
1: FIX/0100/MAN/0004 FIKS DATA I/F
REFERENCE MANUAL
2: FIX/1151/PSP/0099 TEP SUBSYSTEM
PRODUCT SPECIFICATION
3: FIX/1000/EWP/0080 FIKS S/W Conf. Ctrl.
LIBRARY DESCRIPTION (SCCLDD)
4: FIX/1164/PSP/0060 MES SUBSYSTEM
PRODUCT SPECIFICATION
5: FIX/1164/PSP/0100 TEPINT SUBSYSTEM
PRODUCT SPECIFICATION
6: FIX/1100/PSP/0086 RIA SUBSYSTEM
PRODUCT SPECIFICATION
7: FIX/1162/PSP/0069 NES SUBSYSTEM
PRODUCT SPECIFICATION
8: FIX/1200/PSP/0054 JOURNAL PROCEDURE
PRODUCT SPECIFICATION
9: FIX/1100/PSP/0041 CHECKPOINT SUBSYSTEM
PRODUCT SPECIFICATION
10: FIX/1105/PSP/0046 ESP SUBSYSTEM
PRODUCT SPECIFICATION
11: FIX/1155/PSP/0088 SAF SUBSYSTEM
PRODUCT SPECIFICATION
12: FIX/1161/PSP/0095 SPU SUBSYSTEM
PRODUCT SPECIFICATION
13: FIX/1152/PSP/0075 PIP SUBSYSTEM
PRODUCT SPECIFICATION
14: FIX/1160/PSP/0091 ISH SUBSYSTEM
PRODUCT SPECIFICATION
15: FIX/1200/PSP/0076 PSM SUBSYSTEM
PRODUCT SPECIFICATION
16: FIX/1169/PSP/0065 MSA SUBSYSTEM
PRODUCT SPECIFICATION
17: FIX/1161/PSP/0068 NED SUBSYSTEM
PRODUCT SPECIFICATION
18: FIX/1164/PSP/0059 MAS SUBSYSTEM
PRODUCT SPECIFICATION
19: FIX/1154/PSP/0107 NODAL SWITCH SUBSYSTEM(NSS)
PRODUCT SPECIFICATION
3 F̲I̲L̲E̲ ̲G̲E̲N̲E̲R̲A̲T̲O̲R̲S̲
3.1 G̲E̲N̲E̲R̲A̲T̲O̲R̲S̲ ̲F̲O̲R̲ ̲C̲R̲I̲T̲I̲C̲A̲L̲ ̲R̲E̲G̲I̲O̲N̲ ̲F̲I̲L̲E̲S̲
Most of the generators demands an existing file that
is filled with predefined data in the generators.
At FIKS-boot-time loads the ESP the files into the
associated critical regions.
The critical regions are mostly used as dictionaries
for the subsystems.
The filegenerators must run under TOS, as mentioned
by the term "FIKS-offline".
The filegenerators (executable code) are placed in:
a *MOVHEAD*MD*FIX ̲CONFIG.D*INIT.D.
The files (output from the filegenerators) are placed,
as mentioned by the term "current" directory, in:
a *MOVHEAD*MD
As permanent work files, these work files are copied
to:
a *MOVHEAD*MD*FIX ̲CONFIG.D
to new permanent files that have a version number as
suffix in the name.
The filename is constructed as shown below:
FILENAME. id. VERSION
id: N/M-id or SCC-id, if the file
is unique
VERSION 4 digits, starting with 0000,
and increased by 1 if a new
version has to be installed.
3.1.1 C̲O̲N̲F̲
3.1.1.1 M̲o̲d̲u̲l̲e̲ ̲S̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
The CONFIG ̲GEN file generator is used to create the
file CONF.x (x=Node/MEDE ident in ASCII). CONF.x is
used, when the FIKS system is initialized, to load
the critical region CONFIG with initial data. For detailed
information please refer to ref. 1.
3.1.1.2 F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The file CONF.x placed in "current" directory is reset.
The initial data is then written into the file.
3.1.1.3 P̲r̲e̲r̲e̲q̲u̲i̲s̲i̲t̲e̲s̲
The file CONF.x must exist in the "current" directory
with a proper protection.
3.1.1.4 I̲n̲s̲t̲a̲l̲l̲a̲t̲i̲o̲n̲
The generator is installed in the:
a *MOVHEAD*FIX ̲CONFIG.D*INIT.D.
The CONF.x is generated FIKS-offline. The source files
used to generate the CONFIG ̲GEN-file generator are
contained in a seperate delivery to FIXLIB.
Note: One version for each Node/MEDE - or SCC - instal-
lation.
3.1.2 T̲C̲T̲
3.1.2.1 M̲o̲d̲u̲l̲e̲ ̲s̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
THe TCT-Filegenerator is used to create the file TCT,
the TCT-file is used, when the FIKS system is initialized,
to load the critical region XTCBCR with initial data.
For details refer to ref. 1, 2, and 15.
3.1.2.2 F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The file TCT placed in "current" directory is reset.
The initial data is then written into the file.
3.1.2.3 P̲r̲e̲r̲e̲q̲u̲i̲s̲i̲t̲e̲s̲
The file TCT must exist in the "current" directory
with a proper protection.
3.1.2.4 I̲n̲s̲t̲a̲l̲l̲a̲t̲i̲o̲n̲
The TCT-Filegenerator is installed in the
a *MOVHEAD*FIX ̲CONFIG.D*INIT.D.
The TCT-file is generated offline.
Note: One version for each N/M - or SCC - installation.
By any change in the Terminal-configuration for a site,
the associated TCT-Filegenerator must be updated, and
an initialization of the TCT-file take place.
3.1.3 C̲R̲T̲
3.1.3.1 M̲o̲d̲u̲l̲e̲ ̲S̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
CRT is a FIKS-offline filegenerator for the CRT-file
on the N/M.
The file is used by the ESP at Boot-time to generate
the critical region CRT001.
The region containing the Command Reference Table is
used by the TEP Subsystem.
3.1.3.2 F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The CRT-file is reset and the file is filled with data
predefined in the CRT-filegenerator.
3.1.3.3 P̲r̲e̲r̲e̲q̲u̲i̲s̲i̲t̲e̲s̲
The CRT-file must be present in the "current" directory
on MOVHEAD as a random file of 1 sector, with a proper
protection.
3.1.3.4 I̲n̲s̲t̲a̲l̲l̲a̲t̲i̲o̲n̲
The CRT-filegenerator is installed in the
a *MOVHEAD*MD*FIX ̲CONFIG.D.*INIT.D.
3.1.4 P̲T̲T̲
3.1.4.1 M̲o̲d̲u̲l̲e̲ ̲S̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
PTT is an offline generator for the PTT-file on the
N/M.
The file is used by the ESP at Boot-time to generate
the critical region PTT001.
The region, which contains the Prompt Text Table, is
used by the TEP Subsystem.
For details refer to ref. 1 and 2.
3.1.4.2 F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The PTT-file is reset and the file is filled with data
predefined in the PTT-filegenerator.
3.1.4.3 I̲n̲s̲t̲a̲l̲l̲a̲t̲i̲o̲n̲
The PTT-generator is installed in the
a *MOVHEAD*MD*FIX ̲CONFIG.D*INIT.D.
3.1.5 S̲S̲L̲P̲
3.1.5.1 M̲o̲d̲u̲l̲e̲ ̲S̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
SSLP is a FIKS-offline filegenerator for SSLP-file
on the N/M.
The SSLP-file is used by the ESP at Boot-time to generate
the critical region SSLP01, which is equal to the file.
The region, which contains the Skeleton Status Line
Picture, is used by the PSM Subsystem.
For details please refer to ref. 15.
3.1.5.2 F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The SSLP-file, placed in the "current" directory, is
reset and the file is filled with data predefined in
the SSLP-filegenerator.
3.1.5.3 P̲r̲e̲r̲e̲q̲u̲i̲s̲i̲t̲e̲s̲
The SSLP-file must be present in the "current" directory
on MOVHEAD as a random file of 1 sector, with a proper
protection.
3.1.5.4 I̲n̲s̲t̲a̲l̲l̲a̲t̲i̲o̲n̲
The SSLP-filegenerator is installed in the
a *MOVHEAD*MD*FIX ̲CONFIG.D*INIT.D.
3.1.6 P̲D̲B̲T̲A̲B̲
3.1.6.1 M̲o̲d̲u̲l̲e̲ ̲S̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
PDBTAB is an offline generator for the PDBT file.
The file is used by the ESP at Boot-time to generate
the critical region PDBTAB. The file is equal to the
critical region.
The region is used during several message handling
procedures.
The region contains counters and pointers related to
the actual terminal.
For details please refer to ref. 1.
3.1.6.2 F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The PDBT file is reset and the file is filled with
nulls to fit the size necessary for the actual number
of terminals.
3.1.6.3 P̲r̲e̲r̲e̲q̲u̲i̲s̲i̲t̲e̲s̲
The PDBT file must be present in the main directory
as a random file of 1 sector.
Protection: public.
3.1.6.4 I̲n̲s̲t̲a̲l̲l̲a̲t̲i̲o̲n̲
The file is installed in
a *MOVHEAD*MD*FIX ̲CONFIG.D*INIT.D.
3.1.7 S̲Y̲N̲R̲
3.1.7.1 M̲o̲d̲u̲l̲e̲ ̲S̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
SYNR is a FIKS-offline filegenerator for the SYNR-file
on the N/M.
The SYNR-file is used by the ESP at Boot-time to generate
the critical region SYNREF. The file is equal to the
region.
The region, which contains the Syntax Reference table,
is used by the TEP Subsystem.
For details please refer to ref. 1 and 2.
3.1.7.2 F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The SYNR-file is reset and the file is filled with
data predefined in the SYNR-filegenerator.
3.1.7.3 P̲r̲e̲r̲e̲q̲u̲i̲s̲i̲t̲e̲s̲
The SYNR-file must be present in the "current" directory
on MOVHEAD as a random file of 2 sectors, with a proper
protection.
3.1.7.4 I̲n̲s̲t̲a̲l̲l̲a̲t̲i̲o̲n̲
The SYNR-filegenerator is installed in the
a *MOVHEAD*MD*FIX ̲CONFIG.D*INIT.D.
3.1.8 S̲Y̲N̲T̲
3.1.8.1 M̲o̲d̲u̲l̲e̲ ̲S̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
SYNT is a FIKS-offline filegenerator for the SYNT-file
on the N/M.
The SYNT-file is used by the ESP at Boot-time to generate
the critical region SYNTAB. The file is equal to the
region.
The region, which contains the SYntax Table, is used
by the TEP Subsystem.
For details please refer to ref. 1 and 2.
3.1.8.2 F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲c̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The SYNT-file is reset and the file is filled with
data predefined in the SYNT-filegenerator.
3.1.8.3 P̲r̲e̲r̲e̲q̲u̲i̲s̲i̲t̲i̲e̲s̲
The SYNT-file must be present in the "current" directory
on MOVHEAD as a random file of 4 sectors, with a proper
protection.
3.1.8.4 I̲n̲s̲t̲a̲l̲l̲a̲t̲i̲o̲n̲
The SYNT-filegenerator is installed in the
a *MOVHEAD*MD*FIX ̲CONFIG.D*INIT.D.
3.1.9 C̲L̲S̲1̲
3.1.9.1 M̲o̲d̲u̲l̲e̲ ̲S̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
CLS1 is a FIKS-offline filegenerator for the CLS1-file
on the N/M.
The file is used by the ESP at Boot-time to generate
the critical region CLASS1.
The region, which contains the Danish, English, and
NATO classifications in clear text, is used by the
PIP Subsystem.
For details please refer to ref. 1 and 13.
3.1.9.2 F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The CLS1-file is reset and the file is filled with
data predefined in the CLS1-filegenerator.
3.1.9.3 P̲r̲e̲r̲e̲q̲u̲i̲s̲i̲t̲e̲s̲
The CLS1-file must be present in the "current" directory
on MOVHEAD as a random file of 1 sector, with a proper
protection.
3.1.9.4 I̲n̲s̲t̲a̲l̲l̲a̲t̲i̲o̲n̲
The CLS1-filegenerator is installed in the
a *MOVHEAD*MD*FIX ̲CONFIG.D*INIT.D.
3.1.10 C̲L̲S̲2̲
3.1.10.1 M̲o̲d̲u̲l̲e̲ ̲S̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
CLS2 is a FIKS-offline filegenerator for the CLS2-file
on the N/M.
The file is used by the ESP at Boot-time to generate
the critical region CLASS2.
The region, which contains the Danish, English, and
NATO classifications as abbriviations, is used by the
TEP Subsystem.
For details please refer to ref. 1, 2, and 13.
3.1.10.2 F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The CLS2-file is reset and the file is filled with
data predefined in the CLS2-filegenerator.
3.1.10.3 P̲r̲e̲r̲e̲q̲u̲i̲s̲i̲t̲e̲s̲
The CLS2-file must be present in the "current" directory
on MOVHEAD as a random file of 1 sector, with a proper
protection.
3.1.10.4 I̲n̲s̲t̲a̲l̲l̲a̲t̲i̲o̲n̲
The CLS2-filegenerator is installed in the
a *MOVHEAD*MD*FIX ̲CONFIG.D*INIT.D.
3.1.11 S̲P̲E̲C̲
3.1.11.1 M̲o̲d̲u̲l̲e̲ ̲S̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
The SPEC is a FIKS-offline filegenerator for the SPEC-file
on the N/M.
The file is used by the ESP at Boot-time to generate
the critical region SPECTB. The file is equal to the
region.
The region, which contains the SPECAT (Special Categories)
in clear text and as abbreviations, are used by the
TEP Subsystem.
For details please refer to ref. 1, 2, and 13.
3.1.11.2 F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The SPEC-file is reset, and the file is filled with
data predefined in the SPEC-filegenerator.
3.1.11.3 P̲r̲e̲r̲e̲q̲u̲i̲s̲i̲t̲e̲s̲
The SPEC-file must be present in the "current" directory
on MOVHEAD as a random file of 1 sector, with a proper
protection.
3.1.11.4 I̲n̲s̲t̲a̲l̲l̲a̲t̲i̲o̲n̲
The SPEC-filegenerator is installed in the
a *MOVHEAD*MD*FIX ̲CONFIG.D*INIT.D.
3.1.12 S̲T̲E̲V̲T̲B̲
3.1.12.1 M̲o̲d̲u̲l̲e̲ ̲S̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
STEVTB is an off-line generator for the STEV file.
The file is used by the ESP at Boot-time. The file
is equal to the critical region STEVTB.
The region is used during message preparation to convert
prompt level number to a legal sequence No.
During short preparation only a subset of the prompts
used in long preparation are allowed. The prompts that
are only used during long preparation are marked with
a minus.
For details please refer to ref. 1.
The critical region is accessed by the procedure GET
̲STATE ̲EVNT ref. 4.
3.1.12.2 F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The STEV file is reset and data as described in ref.
1 are appended to the file.
3.1.12.3 P̲r̲e̲r̲e̲q̲u̲i̲s̲i̲t̲e̲s̲
The STEV file must be present in the "current" directory
as a random file of 1 sector.
Pretection: public.
3.1.12.4 I̲n̲s̲t̲a̲l̲l̲a̲t̲i̲o̲n̲
The file-generator is installed in
a *MOVHEAD*MD*FIX ̲CONFIG.D*INIT.D.
3.1.13 S̲T̲A̲T̲
3.1.13.1 M̲o̲d̲u̲l̲e̲ ̲S̲p̲e̲c̲e̲f̲i̲c̲a̲t̲i̲o̲n̲
STAT is a FIKS-offline filegenerator for the STAT-file
on the N/M.
The STAT-file is used by the ESP at Boot-time to generate
the critical region STATIC. The file is equal to the
critical region STATIC.
The region is used during several message handling
procedures for statistics.
For details refer to ref. 1, 2, and 13.
3.1.13.2 F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The STAT-file is reset and the file is filled with
nils to fit the size of STATIC.
3.1.13.3 P̲r̲e̲r̲e̲q̲u̲i̲s̲i̲t̲e̲s̲
The STAT-file must be present in the "current" directory
on MOVHEAD as a random file of 2 sectors with a proper
protection.
3.1.13.4 I̲n̲s̲t̲a̲l̲l̲a̲t̲i̲o̲n̲
The STAT-filegenerator is installed in the
a *MOVHEAD*MD*FIX ̲CONFIG.D*INIT.D.
3.1.14 T̲X̲T̲L̲N̲S̲
3.1.14.1 M̲o̲d̲u̲l̲e̲ ̲S̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
TXTLNS is an off-line generator for the TXLN file
The file is used by the ESP at Boot-time to generate
the critical region. The file is equal to the critical
region TXTLNS.
The region is used during display of different tables.
The region contains table headers and other information.
For details please refer to ref. 1.
The critical region is accessed by the procedures
DISP ̲HEADER
PDB ̲MSG ̲STATUS
DISP ̲HDB ̲MSG.
For procedures ref. 3 and 4
3.1.14.2 F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The TXLN file is reset and data as described in ref.
1 are appended to the file.
3.1.14.3 P̲r̲e̲r̲e̲q̲u̲i̲s̲i̲t̲e̲s̲
The TXLN file must be present in the "current" directory
as a random file of 1 sector.
Protection: public.
3.1.14.4 I̲n̲s̲t̲a̲l̲l̲a̲t̲i̲o̲n̲
The file-generator is installed in
a *MOVHEAD*MD*FIX ̲CONFIG.D*INIT.D.
3.1.15 S̲M̲A̲I̲L̲B̲
3.1.15.1 M̲o̲d̲u̲l̲e̲ ̲S̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
SMAILB is a FIKS-offline filegenerator for the SMAILB-file
on the N/M.
The SMAILB-file that contains nils is loaded by the
ESP at Boot-time into the critical region SMAILB, the
size of the region is 28 bytes.
The region is used by the SIP procedure.
For details please refer to ref. 15 and 19.
3.1.15.2 F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The SMAILB-file, placed in the "current" directory,
is reset and the file is filled with nils by the SMAILB-filegenerator.
3.1.15.3 P̲r̲e̲r̲e̲q̲u̲i̲s̲i̲t̲e̲s̲
The SMAILB-file must be present in the "current" directory
on MOVHEAD as a random file of 1 sector, with a proper
protection.
3.1.15.4 I̲n̲s̲t̲a̲l̲l̲a̲t̲i̲o̲n̲
The SMAILB-filegenerator is installed in the
a *MOVHEAD*MD*FIX ̲CONFIG.D*INIT.D.
3.1.16 C̲M̲A̲I̲L̲B̲
3.1.16.1 M̲o̲d̲u̲l̲e̲ ̲S̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
CMAILB is a FIKS-offline filegenerator for the SMAILB-file
on the N/M.
The CMAILB-file that contains nils, is loaded by the
ESP at Boot-time into the critical region SMAILB, the
size of the region is 52 bytes.
The region is used by the SWD- and SPM subsystems.
For details please refer to ref. 15 and 19.
3.1.16.2 F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The CMAILB-file, placed in the "current" directory,
is reset and the file is filled with nils by the CMAILB-filegenerator.
3.1.16.3 P̲r̲e̲r̲e̲q̲u̲i̲s̲i̲t̲e̲s̲
The CMAILB-file must be present in the "current" directory
on MOVHEAD as a random file of 1 sector, with a proper
protection.
3.1.16.4 I̲n̲s̲t̲a̲l̲l̲a̲t̲i̲o̲n̲
The CMAILB-filegenerator is installed in the
a *MOVHEAD*MD*FIX ̲CONFIG.D*INIT.D.
3.1.17 S̲C̲C̲C̲R̲T̲
3.1.17.1 M̲o̲d̲u̲l̲e̲ ̲S̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
SCCCRT is a FIKS-offline filegenerator for the SCCCRT-file
on the SCC.
The SCCCRT-file is used by the ESP at Boot-time to
generate the critical region CRT001.
The region that contains the SCC Command Reference
Table, is used by the TEPINT Subsystem. The file and
region is equal.
For details refer to ref. 1 and 5.
3.1.17.2 F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The SCCCRT-file is reset and the file is filled with
data predefined in the SCCCRT-filegenerator.
3.1.17.3 P̲r̲e̲r̲e̲q̲u̲i̲s̲i̲t̲e̲s̲
The SCCCRT-file must be present in the "current" directory
on MOVHEAD as a random file of 1 sector, with a proper
protection.
3.1.17.4 I̲n̲s̲t̲a̲l̲l̲a̲t̲i̲o̲n̲
The SCCCRT-filegenerator is installed in the
a *MOVHEAD*MD*FIX ̲CONFIG.D*INIT.D.
3.1.18 S̲C̲C̲P̲T̲T̲
3.1.18.1 M̲o̲d̲u̲l̲e̲ ̲S̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
SCCPTT is a FIKS-offline filegenerator for creation
of the PTT-file on the SCC.
The PTT-file is used by the ESP at Boot-time to generate
the critical region PTT001. The file is equal to the
region.
The region that contains the Prompt Text Table, is
used by the TEPINT Subsystem.
For details refer to ref. 1 and 5.
3.1.18.2 F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The PTT-file placed in the "current" directory is reset,
and the initial data is then written into the file.
3.1.18.3 P̲r̲e̲r̲e̲q̲u̲i̲s̲i̲t̲e̲s̲
The PTT-file must exist in the "current" directory
with a proper protection.
3.1.18.4 I̲n̲s̲t̲a̲l̲l̲a̲t̲i̲o̲n̲
The filegenerator is installed in the
a *MOVHEAD*MD*FIX ̲CONFIG.D*INIT.D.
3.1.19 S̲C̲C̲S̲S̲L̲P̲
3.1.19.1 M̲o̲d̲u̲l̲e̲ ̲S̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
SCCSSLP is a FIKS-offline filegenerator for the SCCSSLP-file
on the SCC.
The SCCSSLP-file is used by the ESP to generate the
critical region SSLP01 that is equal to the file.
The region that contains the Skeleton Status Line Picture
for the SCC, is used by PSM Subsystem.
For details please refer to ref. 15.
3.1.19.2 F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The SCCSSLP-file, placed in the "current" directory,
is reset and the file is filled with data predefined
in the SCCSSLP-filegenerator.
3.1.19.3 P̲r̲e̲r̲e̲q̲u̲i̲s̲i̲t̲e̲s̲
The SCCSSLP-file must be present in the "current" directory
on MOVHEAD as a random file of 1 sector, with a proper
protection.
3.1.19.4 I̲n̲s̲t̲a̲l̲l̲a̲t̲i̲o̲n̲
The SCCSSLP-filegenerator is installed in the
a *MOVHEAD*MD*FIX ̲CONFIG.D*INIT.D.
3.1.20 F̲N̲C̲
3.1.20.1 M̲o̲d̲u̲l̲e̲ ̲S̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
FNC is a FIKS-offline filegenerator for the FNC-file
on the SCC.
The FNC-file that contains the FIKS Network Configuration
table, is used by the NED Subsystem.
The FNC-file is used by the ESP at Boot-time to generate
the critical region FNC001. The file and the region
is equal.
For details refer to ref. 1, 17, and 19
3.1.20.2 F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The FNC-file, in the "current" directory, is reset
and the file is filled with data predefined in the
FNC-filegenerator.
3.1.20.3 P̲r̲e̲r̲e̲q̲u̲i̲s̲i̲t̲e̲s̲
The FNC-file must be present in the "current" directory
on MOVHEAD as a random file of 1 sector, with a proper
protection.
3.1.20.4 I̲n̲s̲t̲a̲l̲l̲a̲t̲i̲o̲n̲
The FNC-filegenerator is installed in the
a *MOVHEAD*MD*FIX ̲CONFIG.D*INIT.D.
3.1.21 F̲S̲T̲
3.1.21.1 M̲o̲d̲u̲l̲e̲ ̲S̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
FST is a FIKS-offline filegenerator for the FST-file
on the SCC.
The FST-file that contains the FIKS Status Table is
used by the NSS Subsystem.
The FNC-file is used by the ESP at Boot-time to generate
the critical region FST001. The file and the region
is equal.
For details refer to ref. 1 and 19.
3.1.21.2 F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The FST-file, in the "current" directory, is reset
and the file is filled with data predefined in the
FST-filegenerator.
3.1.21.3 P̲r̲e̲r̲e̲q̲u̲i̲s̲i̲t̲e̲s̲
The FST-file must be present in the "current" directory
on MOVHEAD as a random file of 5 sectors, with a proper
protection.
3.1.21.4 I̲n̲s̲t̲a̲l̲l̲a̲t̲i̲o̲n̲
The FST-filegenerator is installed in the
a *MOVHEAD*MD*FIX ̲CONFIG.D*INIT.D.
3.1.22 F̲R̲D̲
3.1.22.1 M̲o̲d̲u̲l̲e̲ ̲S̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
FRD is a FIKS-offline filegenerator for the FRD-file
on the SCC.
The FRD-file that contains the FIKS Routing Delay Table
is used by the NSS Subsystem.
The FRD-file is used by the ESP at Boot-time to generate
the critical region FRD001. The file and the region
is equal.
For details please refer to ref. 1 and 19.
3.1.22.2 F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The FRD-file, placed in the "current" directory, is
reset and the file is filled with data predefined in
the FRD-filegenerator.
3.1.22.3 P̲r̲e̲r̲e̲q̲u̲i̲s̲i̲t̲e̲s̲
The FRD-file must be present in the "current" directory
on MOVHEAD as a random file of 2 sectors, with a proper
protection.
3.1.2.24 I̲n̲s̲t̲a̲l̲l̲a̲t̲i̲o̲n̲
The FRD-filegenerator is installed in the
a *MOVHEAD*MD*FIX ̲CONFIG.D*INIT.D.
3.1.23 F̲R̲T̲
3.1.23.1 M̲o̲d̲u̲l̲e̲ ̲S̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
FRT is a FIKS-offline filegenerator for the FRT-file
on the SCC.
The FRT-file that contains the FIKS Routing Table is
used by the NSS Subsystem.
The FRT-file is used by the ESP at Boot-time to generate
the critical region FRT001. The file is equal to the
region.
For details please refer to ref. 1 and 19.
3.1.23.2 F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The FRT-file, placed in the "current" directory, is
reset and the file is filled with data predefined in
the FRT-filegenerator.
3.1.23.3 P̲r̲e̲r̲e̲q̲u̲i̲s̲i̲t̲e̲s̲
The FRT-file must be present in the "current" directory
on MOVHEAD as a random file of 2 sectors, with a proper
protection.
3.1.23.4 I̲n̲s̲t̲a̲l̲l̲a̲t̲i̲o̲n̲
The FRT-filegenerator is installed in the
a *MOVHEAD*MD*FIX ̲CONFIG.D*INIT.D.
3.1.24 C̲S̲M̲A̲I̲L̲B̲
3.1.24.1 M̲o̲d̲u̲l̲e̲ ̲S̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
CSMAILB is a FIKS-offline filegenerator for the CSMAILB-file
on the SCC.
The CSMAILB-file that contains nils is loaded at Boot-time
by the ESP into the critical region CSMAILB, the size
of the region is 48 bytes.
The region is used by the CWD- and CPM-subsystems.
For details please refer to ref. 19.
3.1.24.2 F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The CSMAILB-file, placed in the "current" directory,
is reset and the file is filled with nils by the CSMAILB-filegenerator.
3.1.24.3 P̲r̲e̲r̲e̲q̲u̲i̲s̲i̲t̲e̲s̲
The CSMAILB-file must be present in the "current" directory
on MOVHEAD as a random file of 1 sector, with a proper
protection.
3.1.24.4 I̲n̲s̲t̲a̲l̲l̲a̲t̲i̲o̲n̲
The CSMAILB-filegenerator is installed in the
a *MOVHEAD*MD*FIX ̲CONFIG.D*INIT.D.
3.1.25 S̲S̲S̲
3.1.25.1 M̲o̲d̲u̲l̲e̲ ̲S̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
SSS is a FIKS-offline filegenerator for the SSS-file
on the SCC.
The SSS-file is used by the ESP at Boot-time to create
the critical region SSS. The file is equal to the region.
The region is used by the MSA or MAS Subsystems.
For details please refer to ref. 16 and 18.
3.1.25.2 F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The SSS-file is reset and the file is filled with nils
to fit the size of the region (16 bytes).
3.1.25.3 P̲r̲e̲r̲e̲q̲u̲i̲s̲i̲t̲e̲s̲
The SSS-file must be present on the "current" directory
on MOVHEAD as a random file of 1 sector, with a proper
protection.
3.1.25.4 I̲n̲s̲t̲a̲l̲l̲a̲t̲i̲o̲n̲
The SSS-filegenerator is installed in the
a *MOVHEAD*MD*FIX ̲CONFIG.D*INIT.D.
3.1.26 C̲L̲A̲S̲1̲
3.1.26.1 M̲o̲d̲u̲l̲e̲ ̲S̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
The CLS1 is a FIKS-offline filegenerator for the CLS1-file
on the N/M. The CLAS1-file is a copy of the CLS1-file.
The CLAS1-file is used by the ESP at Boot-time to generate
the critical region CLASS1 that is equal to the file.
The region contains the Danish, English, and NATO classifications
in clear text.
For details please refer to ref. 1.
3.1.26.2 F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
Ref. to 3.1.9.2.
3.1.26.3 P̲r̲e̲r̲e̲q̲u̲i̲s̲i̲t̲e̲s̲
Ref. to 3.1.9.3.
3.1.26.4 I̲n̲s̲t̲a̲l̲l̲a̲t̲i̲o̲n̲
Ref. to 3.1.9.1 and 3.1.9.4.
The CLS1-file on the N/M is copied to a floppy-disk,
and written from the floppy-disk into
a *MOVHEAD*MD*FIX ̲CONFIG.D*CLAS1.XXXX on the SCC.
3.1.27 C̲L̲A̲S̲2̲
3.1.27.1 M̲o̲d̲u̲l̲e̲ ̲S̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
The CLS2 is a FIKS-offline filegenerator for the CLS2-file
on the N/M.
The CLAS2 being a copy of the CLS2-file is used at
Boot-time by the ESP to generate the critical region
CLASS2 that is equal to the CLAS2-file.
For more details refer to 3.1.10.1.
3.1.27.2 F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
Refer to 3.1.10.2.
3.1.27.3 P̲r̲e̲r̲e̲q̲u̲i̲s̲i̲t̲e̲s̲
Refer to 3.1.10.3.
3.1.27.4 I̲n̲s̲t̲a̲l̲l̲a̲t̲i̲o̲n̲
Refer to 3.1.10.1 and 3.1.10.4.
The CLS2-file on the N/M is copied to a floppy-disk,
and written from the floppy-disk into
a *MOVHEAD*MD*FIX ̲CONFIG.D*CLAS2.XXXX on the SCC.
3.1.28 R̲I̲T̲A̲N̲O̲
3.1.28.1 M̲o̲d̲u̲l̲e̲ ̲S̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
The RITANO ̲GEN filegenerator is used to create the
file RITANO ̲SAVE on the SCC.
The RITANO ̲SAVE is loaded into the critical region
RITANO at Boot-time, and the RITANO is accessed by
the monitor RITA.
For details refer to ref. 1 and 6.
3.1.28.2 F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The file RITANO ̲SAVE, placed in the directory
a *MOVHEAD*FIX ̲CONFIG.D.
is reset, and the initial data are then written into
the file.
3.1.28.3 P̲r̲e̲r̲e̲q̲u̲i̲s̲i̲t̲e̲s̲
The file a *MOVHEAD*FIX ̲CONFIG.D*RITANO ̲SAVE must exist
as a random file of 2 sectors, with a proper protection.
3.1.28.4 I̲n̲s̲t̲a̲l̲l̲a̲t̲i̲o̲n̲
The generator is installed in the
a *MOVHEAD*FIX ̲CONFIG.D*INIT.D.
The RITANO ̲SAVE is generated FIKS-offline.
The initial data used to generate the RITANO ̲SAVE is
placed in the variable RITANO ̲ARRAY, please check and
update this variable before use of the generator.
3.1.29 S̲C̲C̲S̲Y̲N̲R̲
3.1.29.1 M̲o̲d̲u̲l̲e̲ ̲S̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
The SCCSYNR is a FIKS-offline filegenerator for the
SCCSYNR-file on the SCC.
The SCCSYNR-file is used by the ESP at Boot-time to
generate the critical region SYNREF. The file is equal
to the region.
The region that contains the Syntax Reference table
is used by the TEPINT Subsystem.
For details please refer to ref. 1 and 5.
3.1.29.2 F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The SCCSYNR-file is reset and the file is filled with
data predefined in the SCCSYNR-filegenerator.
3.1.29.3 P̲r̲e̲r̲e̲q̲u̲i̲s̲i̲t̲e̲s̲
The SCCSYNR-file must be present in the "current" directory
on MOVHEAD as a random file of 1 sector, with a proper
protection.
3.1.29.4 I̲n̲s̲t̲a̲l̲l̲a̲t̲i̲o̲n̲
The SCCSYNR-filegenerator is installed in the
a *MOVHEAD*MD*FIX ̲CONFIG.D*INIT.D.
3.1.30 S̲C̲C̲S̲Y̲N̲T̲
3.1.30.1 M̲o̲d̲u̲l̲e̲ ̲S̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
The SCCSYNT is a FIKS-offline filegenerator for the
SCCSYNT-file on the SCC.
The SCCSYNT-file is used by the ESP at Boot-time to
generate the critical region SYNTAB. The file is equal
to region.
The region that contains the Syntax Table is used by
the TEPINT Subsystem.
For details please refer to ref. 1 and 5.
3.1.30.2 F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The SCCSYNT-file is reset and the file is filled with
data predefined in the SCCSYNT-filegenerator.
3.1.30.3 P̲r̲e̲r̲e̲q̲u̲i̲s̲i̲t̲e̲s̲
The SCCSYNT-file must be present in the "current" directory
on MOVHEAD as a random file of 2 sectors, with a proper
protection.
3.1.30.4 I̲n̲s̲t̲a̲l̲l̲a̲t̲i̲o̲n̲
The SCCSYNT-filegenerator is installed in the
a *MOVHEAD*MD*FIX ̲CONFIG.D*INIT.D.
3.1.31 T̲A̲B̲U̲P̲D̲
3.1.31.1 M̲o̲d̲u̲l̲e̲ ̲S̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
TABUPD is a FIKS-offline filegenerator for the TABUPD-file
on the SCC.
The file is used by the ESP at Boot-time to generate
the critical region TABUPD.
The region is used for communications between several
subsystems.
For details please refer to ref. 1.
3.1.31.2 F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The TABUPD-file is reset, and filled with 300 bytes
of nils.
3.1.31.3 P̲r̲e̲r̲e̲q̲u̲i̲s̲i̲t̲e̲s̲
The TABUPD-file must be present in the "current" directory
on MOVHEAD as a random file of 1 sector, with a proper
protection.
3.1.31.4 I̲n̲s̲t̲a̲l̲l̲a̲t̲i̲o̲n̲
The TABUPD-filegenerator is installed in the
a *MOVHEAD*MD*FIX ̲CONFIG.D*INIT.D.
3.2 G̲E̲N̲E̲R̲A̲T̲I̲O̲N̲ ̲O̲F̲ ̲D̲I̲S̲C̲ ̲R̲E̲S̲I̲D̲E̲N̲T̲ ̲F̲I̲L̲E̲S̲
The disc resident files are mostly files that demand
more storage space than it is possible to get in the
"current" configuration.
To compensate for this some files are placed on the
part of the disc named FIXHEAD.
Some of the disc resident files must be created FIKS-offline,
and some have the possibility for both FIKS-offline
and FIKS-online creation.
3.2.1 I̲M̲F̲
3.2.1.1 M̲o̲d̲u̲l̲e̲ ̲S̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
The intermediate Message File (IMF) is a permanent
file on the fix-head disc of a NODE/MEDE.
The IMF contains all inbound messages and all NSS generated
messages (for network as well as for the local MEDE).
The file is divided into message areas of 18 segments
big enough for a message of maximum length, incl. the
binary header.
3.2.1.2 F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
No IMF generator is needed.
3.2.1.3 P̲r̲e̲r̲e̲q̲u̲i̲s̲i̲t̲e̲s̲
Not applicable.
3.2.1.4 I̲n̲s̲t̲a̲l̲l̲a̲t̲i̲o̲n̲
The file is created at system generation time.
The file organization is contiguous.
The size is 112 x 18 = 2016 segments.
After being created the file is entirely filled with
pseudo data just to fix its size.
3.2.2 M̲T̲F̲,̲ ̲M̲R̲F̲,̲ ̲D̲T̲G̲F̲
3.2.2.1 M̲o̲d̲u̲l̲e̲ ̲S̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
The files MFT, MRF, DTGF are located in MOVHEAD * MD,
and used by the subsystem SRS. MFT is the HDB file,
while MRF and DTGF are catalogue files.
The SRS subsystem expects that the files at initialization
time are filled with dummy characters.
For this purpose the generator FILL ̲HDB is available.
In addition the generator includes the function of
the PRESET ̲HDB generator (ref. chapt. 3.2.5).
The generator is only activated once: at disc initialization
time.
3.2.2.2 F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The processsing in FILL ̲HDB is as follows:
o The files MTF, MRF, DTGF, and SRS ̲CHECKP are reset.
o The SRS ̲CHECKP file is filled as described in chapt.
3.2.5.
o The MRF file is filled with zeros (2801 sectors)
o The DTGF file is filled with zeros (172 sectors)
o The MTF file is filled with zeros (110170 sectors)
3.2.2.3 P̲r̲e̲r̲e̲q̲u̲i̲s̲i̲t̲e̲s̲
FILL ̲HDB expects that the following files are created:
FIXHEAD * SRS ̲CHECKP: 3 contiguous sectors
MOVHEAD * MFR : 2801 - -
MOVHEAD * DTGF : 172 - -
MOVHEAD * MFT : 110270 - -
All files must have PUBLIC protection.
3.2.3 S̲D̲F̲.̲D̲
3.2.3.1 M̲o̲d̲u̲l̲e̲ ̲S̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
The SDCR-generator creates the SDF.D-directory and
the files to be included in the directory. I.e. the
NSF-, MHF-, MDF-, SIF-, USF-, and LOF-files. Refer
to FIKS DATA INTERFACE, FIX/0100/MAN/004, sec. The
files are exclusively accessed by the NES Subsystem.
3.2.3.2 F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
If the SDF.D-directory does no exist, then it is created.
For each of the files to be contained in the directory
holds that if they exist, then they are removed. The
files are created with contiguous organization and
optimal size (i.e. not greater than necessary). Protection
is sat so that the files can be accessed by both system-
and ordinary users (userids -1, -1, an 0,0). The files
are filled with binary zero's.
3.2.3.3 P̲r̲e̲r̲e̲q̲u̲i̲s̲i̲t̲e̲s̲
None. (Ordinary FIKS FMS-system). The generator can
be started both at FIKS-offline and -online (Background
process).
3.2.3.4 I̲n̲s̲t̲a̲l̲l̲a̲t̲i̲o̲n̲
The generator (executable code) is installed in the
a *MOVHEAD*FIX ̲CONFIG.D*INIT.D.
on the SCC's. The SDFCR-generator is a part of the
NES subsystem and the source files for SDFCR is therefore
contained in the NES-deliveries to FIXLIB. Refer to
NES Subsystem PSP, FIX/1162/PSP/0069.
3.2.4 M̲J̲F̲ ̲I̲N̲I̲T̲
3.2.4.1 M̲o̲d̲u̲l̲e̲ ̲S̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
MJF ̲INIT is an offline generator for the MJF file.
The file is used by the JOURNAL procedure (FIX/1200/PSP/0054)
to store message log information.
The file is accessed by JOURNAL (read, write) and by
PIP (read).
3.2.4.2 F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The file is reset and then filled with dummy data.
A control record of 8 words is read to the file (words
8-16). The contents of the record are
Word 1 : FIRST ̲REC = 0
Word 2-3: BTG ̲FIRST ̲REC = 0
Word 4 : F ̲WRAP ̲AROUND = 0
Word 5 : F ̲EMPTY ̲FILE = 1
Word 6 : F ̲ESP ̲WARNING = 0
Word 7-8: Spare = 0
3.2.4.3 P̲r̲e̲r̲e̲q̲u̲i̲s̲i̲t̲e̲s̲
MJF must be present in the main directory as a contiguous
file of 513 sectors. Protection: public.
3.2.4.4 I̲n̲s̲t̲a̲l̲l̲a̲t̲i̲o̲n̲
The generator is intalled in the directory
a *MOVHEAD*FIX ̲CONFIG.D*INIT.D.
3.2.5 S̲R̲S̲ ̲C̲H̲E̲C̲K̲P̲
3.2.5.1 M̲o̲d̲u̲l̲e̲ ̲S̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
The file FIXHEAD * SRS ̲CHECKP is a contiguous file
of 3 sectors and is meant for storage of checkpoints
for the submodule SRS. The file is at all times an
image of the critical region SRS ̲CR.
Presetting of SRS ̲CHECKP is made by activating the
generator PRESET ̲HDB located in
a *MOVHEAD*MD*FIX ̲CONFIG.D*INIT.D.
When activated, all pointers to HDB contents are preset,
indicating an empty HDB.
3.2.5.2 F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
PRESET ̲HDB resets the file FIXHEAD*SRS ̲CHECKP and
all pointers except the below listed are set to zero:
OLDEST ̲DTG = 10
DTG ̲FIRST ̲IN ̲MEM = 10
DTG ̲LAST = 10
BASE ̲DTG = 5
DTG ̲IND = 1
REC ̲NO ̲OLDEST = 1
REC ̲NO ̲FIRST ̲IN ̲MEN = 1
SELT ̲NO ̲FIRST ̲SELT ̲OLDEST ̲M = 1
3.2.5.3 P̲r̲e̲r̲e̲q̲u̲i̲s̲i̲t̲e̲s̲
The file FIXHEAD*SRS ̲CHECKP must be created as a contiguous
file of 3 sectors and have PUBLIC protection.
3.2.6 U̲S̲P̲,̲ ̲S̲C̲C̲U̲S̲P̲
3.2.6.1 M̲o̲d̲u̲l̲e̲ ̲S̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
The USP-filegenerator is used to create the file USPx
(x = Node/Mede ident in ASCii). The USPx-file is handled
by the SAF-subsystem (ref. 11).
The SCCUSP-filegenerator is used to create the file
USP on the SCC. The USP-file is then handled by the
SPU-subsystem (ref. 12).
For details please refer to ref. 1, 11, and 12.
3.2.6.2 F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The file USPx or USP placed in the "current" directory
is reset, and the initial data (Security profiles for
supervisors) is written into the file.
3.2.6.3 P̲r̲e̲r̲e̲q̲u̲i̲s̲i̲t̲e̲s̲
The file USPx or USP must exist in the "current" directory
with a proper protection.
3.2.6.4 I̲n̲s̲t̲a̲l̲l̲a̲t̲i̲o̲n̲
The filegenerator USP or SCCUSP is installed in the
a *MOVHEAD*FIX ̲CONFIG.D*INIT.D.
The file USPx or USP is generated offline.
3.2.7 N̲D̲F̲
3.2.7.1 M̲o̲d̲u̲l̲e̲ ̲S̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
The Nodal Data File (NDF) is a permanent file on the
moving-head disc of a Node/Mede.
It contains information about the network and the node
configuration necessary for start and restart. During
operation it is maintained by the NSS, so it will be
updated ready for restart.
The NDF consists of 2 segments:
o segment #1 contains the virgin NDF, which
is input during a start condition
It is generated during system
generation time, and it is
never updated.
o segment #0 contains the NDF, which is
input during a restart condition.
It is updated currently, when
any of the Nodal Data is changed.
3.2.7.2 F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The NDF generator is the Assembler.
Input is a textfile containing the source for each
node and SCC.
Output is a binary file for segment #1 of the NDF:
3.2.7.3 P̲r̲e̲r̲e̲q̲u̲i̲s̲i̲t̲e̲s̲
Before running the Assembler, the name of the node
in question must be set in the source by the Editor.
3.2.7.4 I̲n̲s̲t̲a̲l̲l̲a̲t̲i̲o̲n̲
The NDF generated is copied into segment #1 as mentioned
above.
The contents of segment #0 is irrelevant during a start
condition.
3.2.8 P̲D̲B̲
3.2.8.1 M̲o̲d̲u̲l̲e̲ ̲S̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
An offline generator of the PDB files is available.
The generator is used at disc configuration time.
3.2.8.2 F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The generator is a command file: CR ̲FIX ̲PDBS with an
associated 2nd level command file CR ̲FIX ̲PDBS.CIN.
The command file generates 210 random files with the
names PDBOO1-PDB21O in the directory MOVHEAD * PDB.
3.1.8.3 P̲r̲e̲r̲e̲q̲u̲i̲s̲i̲t̲e̲s̲
The directory PDB must exist and have the protection
PUBLIC in MOVHEAD * MD.
In order to obtain the correct protection of the PDB-files
the command file must be activated by a user with same
rights as PUBLIC.
3.2.9 C̲H̲E̲C̲K̲P̲ ̲F̲I̲L̲E̲
3.2.9.1 M̲o̲d̲u̲l̲e̲ ̲S̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
The general checkpoint file used in the FIKS system
(CHECKP ̲FILE) is created of the CHPFIL-file generator.
Refer to FIKS DATA INTERFACE REFERENCE, FIX/0100/MAN/0004,
sec. 11.12.
The file is accessed by the checkpoint process and
the ESP process.
3.2.9.2 F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
If the file a *FIXHEAD*CHECKP ̲FILE exists, then it
is removed. The file is created with contiguous organization
and optimal size (i.e. not greater than necessay).
Protection is set in order that the file can be accessed
by both system- and ordinary FMS-users (userid -1,
-1, and 0,0). The file is filled with binary zero's.
3.2.9.3 P̲r̲e̲r̲e̲q̲u̲i̲s̲i̲t̲e̲s̲
None. (Ordinary FIKS FMS-system). The generator can
be started both at FIKS offline and online (Background
process).
3.2.9.4 I̲n̲s̲t̲a̲l̲l̲a̲t̲i̲o̲n̲
The generator (executable code) is installed in the
a *MOVHEAD*FIX ̲CONFIG.D*INIT.D.
The CHPFIL-generator is a part of the Checkpoint Subsystem
and source files for generating of the CHPFIL is therefore
included in the CHECKP-deliveries to FIXLIB. Refer
to Checkpoint Subsystem PSP, ref. 9.
Note: Different version of CHPFIL depends on whether
it is a Node/MEDE - or a SCC-installation.
3.2.10 B̲G̲P̲S̲ ̲F̲I̲L̲E̲
3.2.10.1 M̲o̲d̲u̲l̲e̲ ̲S̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
The BGPS ̲FILE used in the FIKS system to "roll in/out"
the background processes is created of the BPSFIL-filegenerator.
Refer to ESP System PSP, FIX/1105/PSP/0046. The file
is exclusively accessed by the BGMANG-process.
3.1.10.2 F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
If the file a *FIXHEAD*BGPS ̲FILE exists, then it is
removed. The file is created with contiguous organization
and optimal size. protection is set in order that the
file can be accessed by system- and ordinary FMS-users
(userid -1, -1, and 0,0). The file is filled with binary
zero's.
3.2.10.3 P̲r̲e̲r̲e̲q̲u̲i̲s̲i̲t̲e̲s̲
None. (Ordinary FIKS FMS system).
3.2.10.4 I̲n̲s̲t̲a̲l̲l̲a̲t̲i̲o̲n̲
The generator (executable code) is installed in the
a *MOVHEAD*FIX ̲CONFIG.D.*INIT.D.
The BPSFIL-filegenerator is a part of the ESP System
and source files for generating of the BPSFIL is therefore
included in the the ESP-deliveries to FIXLIB. Refer
to ESP System PSP, FIX/1105/PSP/0046.
Note: The version of BPSFIL to be used depends on
whether it is a Node/MEDE or a SCC-installation.
3.2.11 R̲D̲F̲
3.2.11.1 M̲o̲d̲u̲l̲e̲ ̲S̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
RDF-filegenerator is an offline generator for the RDF-file.
The Routing Directory File (RDF) contains information
to be used in routing and distribution of messages.
For details please refer to ref. 1.
3.2.11.2 F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The RDF-file is reset and the file is filled with data
predefined in the RDF-filegenerator.
3.2.11.3 P̲r̲e̲r̲e̲q̲u̲i̲s̲i̲t̲e̲s̲
The RDF-file must be present in the main directory
on FIXHEAD as a random file, with public protection.
3.2.11.4 I̲n̲s̲t̲a̲l̲l̲a̲t̲i̲o̲n̲
The RDF-Filegenerator (executable code) is installed
in the
a *MOVHEAD*MD*FIX ̲CONFIG.D*INIT.D.
3.2.12 T̲M̲F̲
3.2.12.1 M̲o̲d̲u̲l̲e̲ ̲S̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
The TMF-filegenerator is used FIKS-offline to create
the TMF-file on the N/M.
The TMF-file is used during preparation LONG, if the
keyoperator specifies a Text Mask number to the first
prompt
For details refer to ref. 1, and the description of
TMF ̲GEN written by AMC.
3.2.12.2 F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The TMF-file is reset and the file is filled with data
predefined in the TMF ̲filegenerator.
3.2.12.3 P̲r̲e̲r̲e̲q̲u̲i̲s̲i̲t̲e̲s̲
The TMF-file must be present in the "current" directory
on MOVHEAD as a contiguous file of 5 sectors, with
a proper protection.
3.2.12.4 I̲n̲s̲t̲a̲l̲l̲a̲t̲i̲o̲n̲
The TMF-filegenerator (executable code) is installed
in the
a *MOVHEAD*MD*FIX ̲CONFIG.D*INIT.D.
3.3 P̲R̲O̲C̲E̲S̲S̲I̲N̲G̲
This chapter is included in the chapters 3.1 and 3.2.
3.4 S̲T̲O̲R̲A̲G̲E̲ ̲A̲L̲L̲O̲C̲A̲T̲I̲O̲N̲
As most of the filegenerators must run FIKS-offline,
i.e. under TOS, no special provisions are applicable.
3.5 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̲
N/A.
3.6 L̲I̲M̲I̲T̲A̲T̲I̲O̲N̲S̲
Please be sure that the file created has a proper protection,
generally:
SYS -1, -1
FIKS 0, 0
3.7 E̲R̲R̲O̲R̲ ̲C̲O̲D̲E̲S̲/̲E̲R̲R̲O̲R̲ ̲L̲O̲C̲A̲T̲I̲O̲N̲S̲
Please refer to the source listings.
3.8 P̲R̲E̲P̲A̲R̲A̲T̲I̲O̲N̲S̲ ̲F̲O̲R̲ ̲D̲E̲L̲I̲V̲E̲R̲Y̲
Please refer to SCCLDD.
4 Q̲U̲A̲L̲I̲T̲Y̲ ̲A̲S̲S̲U̲R̲A̲N̲C̲E̲
4.1 Q̲U̲A̲L̲I̲F̲I̲C̲A̲T̲I̲O̲N̲ ̲T̲E̲S̲T̲
Please refer to testreports for System Tests, S010.
5 N̲O̲T̲E̲S̲
N/A.
