top - download
⟦8141dcab9⟧ Wang Wps File
Length: 53565 (0xd13d)
Types: Wang Wps File
Notes: CPS/SDS/005
Names: »1083A «
Derivation
└─⟦b282628ca⟧ Bits:30006035 8" Wang WCS floppy, CR 0059A
└─ ⟦this⟧ »1083A «
WangText
…00……00……00……00……00…E…0a……00……00…E…0b…E D…0e…C…08…C…01…B…0b…B…00…B
B…05…B…06…A…0b…A…0f…A @…09…@…0b…@…0e…=…00…=…06…<…0c…<
<…06…<…07…;…08…;…09…;…0a……86…1 …02… …02… …02…
…02…CPS/SDS/005
…02…BMN/810801…02……02…
TABLE MANAGEMENT
…02……02…CAMPS
T̲A̲B̲L̲E̲ ̲O̲F̲ ̲C̲O̲N̲T̲E̲N̲T̲S̲
1 GENERAL ...........................................
8
1.1 PURPOSE AND SCOPE ...............................
8
1.2 APPLICABLE DOCUMENTS AND PROJECT REF. ...........
8
1.2.1 Applicable Documents ........................
8
1.2.2 Project References ..........................
8
1.3 TERMS AND ABBREVIATIONS .........................
9
1.3.1 Terms .......................................
9
1.3.2 Abbreviations ...............................
9
2 SUMMARY OF REQUIREMENTS ...........................
10
2.1 TMP DESCRIPTION .................................
10
2.2 TMP FUNCTIONS ...................................
12
2.2.1 TMP Normal Functions ........................
12
2.2.1.1 Search In Tables ........................
12
2.2.1.2 Update Of Tables ........................
12
2.2.1.3 Reorganization Of Tables ................
12
2.2.1.4 Back-up/Reload of TMP Data ..............
12
2.2.1.5 Global Number Series Management .........
13
2.2.1.6 System Parameters .......................
13
2.2.2 Functional Responsibilities .................
13
2.2.2.1 Initialization, Close Down, and Restart
. 13
2.2.2.1.1 Initialization ......................
13
2.2.2.1.2 Close Down ..........................
13
2.2.2.1.3 Restart .............................
13
2.2.2.2 Check Pointing And Recovery .............
14
2.2.2.3 Error Detection And Error Handling ......
14
2.2.2.4 Integrity Of Operation ..................
14
2.2.2.5 Data Collection .........................
14
2.2.2.6 Security ................................
15
2.3 CHARACTERISTICS .................................
15
2.3.1 Timing ......................................
15
2.3.2 Throughput ..................................
15
2.3.3 Flexibility .................................
16
2.3.4 Accuracy ....................................
16
3 ENVIRONMENTS ......................................
17
3.1 EQUIPMENT .......................................
17
3.2 SOFTWARE ........................................
17
3.2.1 System Software .............................
17
3.2.2 Development Support Software ................
17
3.3 Interfaces ......................................
17
3.3.1 External Interfaces .........................
17
3.3.2 Package Interfaces ..........................
18
3.4 FUNCTIONS MAINTAINED BY OTHER PACKAGES ..........
18
4 TMP DESIGN ........................................
19
4.1 TMP OVERVIEW ....................................
19
4.1.1 Functional Description ......................
19
4.1.1.1 Table Organization And Access Methods
... 19
4.1.1.1.1 Table Organization ..................
19
4.1.1.1.2 Record Structure ....................
20
4.1.1.1.3 Field Structure .....................
20
4.1.1.1.4 Search Key Structure ................
21
4.1.1.1.5 Table Description ...................
21
4.1.1.2 Table Search ............................
29
4.1.1.3 Table Update ............................
30
4.1.1.4 TMP Interface Functions .................
30
4.1.1.5 System Parameters And Global Number
Series ..................................
31
4.1.1.6 Back-up And Reload ......................
31
4.1.1.7 Reorganize ..............................
31
4.1.1.8 Functional Breakdown ....................
31
4.1.1.8.1 Table Search Functions ..............
33
4.1.1.8.1.1 Search Communication ...........
33
4.1.1.8.1.2 Sort Keys ......................
33
4.1.1.8.1.3 Memory Table Search ............
33
4.1.1.8.1.4 Disc Table Search ..............
34
4.1.1.8.2 Table Update Functions ..............
34
4.1.1.8.2.1 Search .........................
34
4.1.1.8.2.2 Update Record ..................
34
4.1.1.8.2.3 Update Disk ....................
34
4.1.1.8.2.4 Support ........................
35
4.1.1.8.2.5 Update Communication ...........
35
4.1.1.8.3 TMP Monitor .........................
35
4.1.1.8.3.1 Check Function .................
35
4.1.1.8.3.2 Process Interface ..............
35
4.1.1.8.3.3 Get System Parameter ...........
36
4.1.1.8.3.4 Get Global No. Series ..........
36
4.1.1.8.3.5 Set Global No. Series ..........
36
4.1.2 TMP Software Structure ......................
36
4.1.2.1 TMP Process .............................
76
4.1.2.2 TMP Monitor .............................
76
4.1.3 Data Flow And Control Logic .................
39
4.1.3.1 Data Flow ...............................
39
4.1.3.2 Control Logic ...........................
41
4.1.4 Common Data Elements ........................
47
4.1.4.1 Info Data ...............................
47
4.1.4.1.1 System Parameters ...................
47
4.1.4.1.2 Tables ..............................
49
4.1.4.2 Control Data ............................
50
4.1.5 External Data Elements ......................
52
4.1.5.1 TMP Variable ............................
52
4.1.5.2 TMP Communication Buffers ...............
52
4.1.6 TMP Interfaces ..............................
55
4.1.6.1 TMP Interface Functions .................
55
4.1.6.1.1 Search ..............................
56
4.1.6.1.2 Get System Parameters ...............
56
4.1.6.1.3 Get Global No. Series ...............
56
4.1.6.1.4 Get Table Attributes ................
57
4.1.6.1.5 Update ..............................
57
4.1.6.1.5.1 Remove Record ..................
57
4.1.6.1.5.2 Insert Record ..................
58
4.1.6.1.5.3 Change Specified Fields ........
58
4.1.6.1.5.4 Change All Fields With Value
... 59
4.1.6.1.6 Set Global Number Series ............
59
4.1.6.1.7 Set Table Attributes ................
60
4.1.6.1.8 Reorganize .........................
60
4.1.6.1.9 Back-up ............................
60
4.1.6.1.10 Reload .............................
60
4.1.6.2 Package Interface Overview ..............
61
4.1.6.2.1 Logical Tables .....................
61
4.1.6.2.2 Package Access Rights ..............
62
4.1.6.3 Subpackage Interface ....................
66
4.2 TMP SUBPACKAGE SPECIFICATION ....................
68
4.2.1 Table Search Functions ......................
68
4.2.1.1 Functional Specification ................
68
4.2.1.1.1 Communication .......................
71
4.2.1.1.1.1 Receive Request.................
71
4.2.1.1.1.2 Send Response ..................
71
4.2.1.1.1.3 Set Table Attributes ...........
71
4.2.1.1.1.4 Get Table Attributes............
71…86…1 …02… …02… …02… …02… …02… …02… …02… …02… …02… …02…
4.2.1.1.2 Sort Keys ...........................
72
4.2.1.1.2.1 Compare String .................
72
4.2.1.1.3 Memory Table Search .................
73
4.2.1.1.3.1 Binary Search ..................
75
4.2.1.1.3.2 Direct Search ..................
75
4.2.1.1.3.3 Sequential Search ..............
76
4.2.1.1.3.4 Mask Data ......................
77
4.2.1.1.4 Disk Table Search ...................
78
4.2.1.1.4.1 Index Block ....................
80
4.2.1.1.4.2 Direct Block ...................
80
4.2.1.1.4.3 Read Disk Block ................
81
4.2.1.2 Software Structure ......................
81
4.2.1.3 Data Flow And Control Logic .............
82
4.2.1.4 Subpackage Data .........................
88
4.2.1.5 Subpackage Interface ....................
88
4.2.2 Table Update ................................
90
4.2.2.1 Functional Specification ................
90
4.2.2.1.1 Search ..............................
92
4.2.2.1.1.1 Memory Search ..................
92
4.2.2.1.1.2 Disk Search ....................
92
4.2.2.1.2 Update Record .......................
92
4.2.2.1.2.1 Update Data ....................
92
4.2.2.1.2.2 Remove Record ..................
93
4.2.2.1.2.3 Insert Record ..................
94
4.2.2.1.3 Update Disk .........................
94
4.2.2.1.4 Support .............................
95
4.2.2.1.4.1 Reorganize .....................
95
4.2.2.1.4.2 Back-up ........................
96
4.2.2.1.4.3 Reload .........................
96
4.2.2.1.5 Communication .......................
96
4.2.2.1.5.1 Receive Request ................
96
4.2.2.1.5.2 Send Response ..................
96
4.2.2.2 Software Structure ....................
96
4.2.2.3 Data Flow And Control Logic ...........
97
4.2.2.4 Table Update Data .....................
101
4.2.2.5 Subpackage Interface ..................
101
4.2.3 TMP Monitor .................................
103
4.2.3.1 Functional Specification ................
103
4.2.3.1.1 Detect Function .....................
105
4.2.3.1.2 Process Interface ...................
105
4.2.3.1.2.1 Request Function ...............
105
4.2.3.1.2.2 Deliver Output .................
105
4.2.3.1.3 Get System Parameter ................
105
4.2.3.1.3.1 Find Parameter .................
106
4.2.3.1.3.2 Deliver Parameter ..............
106
4.2.3.1.4 Get Global Number Series ............
106
4.2.3.1.4.1 Find Global Number Series ......
107
4.2.3.1.4.2 Increase Global Number Series
.. 107
4.2.3.1.4.3 Deliver Global Number Series
... 108
4.2.3.1.5 Set Global Number Series ............
108
4.2.3.1.5.1 Find Global Number Series ......
109
4.2.3.1.5.2 Write Global Number Series .....
109
4.2.3.2 Software Structure ......................
109
4.2.3.2.1 Detect Function .....................
109
4.2.3.2.2 Process Interface ...................
110
4.2.3.2.2.1 Init ...........................
110
4.2.3.2.2.2 Answer Received ................
110
4.2.3.2.2.3 Complete .......................
110
4.2.3.2.2.4 Cancel .........................
110
4.2.3.2.3 Get System Parameters ...............
111
4.2.3.2.3.1 Init Get Parameters ............
111
4.2.3.2.3.2 Answer Received Get Parameter
.. 111
4.2.3.2.3.3 Complete Set Parameters ........
111
4.2.3.2.3.4 Cancel Get Parameters ..........
111
4.2.3.2.4 Global Number Series ................
112
4.2.3.3 Data Flow And Control Logic .............
112
4.2.3.4 Subpackage Data .........................
114
4.2.3.4.1 Global Number Series Data ...........
114
4.2.3.4.2 Interface Data ......................
114
4.2.3.5 Subpackage Interface ....................
116
4.3 MEMORY LAYOUT ...................................
118
4.3.1 Table Storage ...............................
118
4.3.2 Working Storage .............................
120
4.3.3 Code Storage ................................
120
1̲ ̲ ̲G̲E̲N̲E̲R̲A̲L̲
1.1 P̲U̲R̲P̲O̲S̲E̲ ̲A̲N̲D̲ ̲S̲C̲O̲P̲E̲
The purpose of Table Management Package (TMP) is to
provide search and update tools to the packages which
want to access the data base containing tables, system
parameters and global number series.
Furthermore, TMP will control that no package accesses
other data than it is allowed to access.
This document describes TMP down to a level where all
functions performed by TMP and all components to be
implemented inside TMP are defined.
This description is a further detailed description
of TMP functions than the one in CPS/SDS/001 and it
will be more detailed described in the detailed design
document.
In this specification is given a description of general
interfaces and general data structures.
For more detailed data and interface description refer
CPS/DBD/001 and CAMPS SW Interface Control Document.
1.2 A̲P̲P̲L̲I̲C̲A̲B̲L̲E̲ ̲D̲O̲C̲U̲M̲E̲N̲T̲S̲ ̲A̲N̲D̲ ̲P̲R̲O̲J̲E̲C̲T̲ ̲R̲E̲F̲E̲R̲E̲N̲C̲E̲S̲
1.2.1 A̲p̲p̲l̲i̲c̲a̲b̲l̲e̲ ̲D̲o̲c̲u̲m̲e̲n̲t̲s̲
- CPS/210/SYS/0001
- CPS/ICD/002
- CPS/SDS/001
- CPS/DBD/001
- CPS/SWICD
1.2.2 P̲r̲o̲j̲e̲c̲t̲ ̲R̲e̲f̲e̲r̲e̲n̲c̲e̲s̲
N/A.
1.3 T̲E̲R̲M̲S̲ ̲A̲N̲D̲ ̲A̲B̲B̲R̲E̲V̲I̲A̲T̲I̲O̲N̲S̲
1.3.1 T̲e̲r̲m̲s̲
S̲u̲b̲p̲r̲o̲c̲e̲s̲s̲
Group of modules having the same access rights.
K̲e̲y̲
Field value used to identify a record.
S̲e̲a̲r̲c̲h̲ ̲K̲e̲y̲
Consists of three parts:
- Key
- Record Type
- Table Body (start addr. of table part)
T̲a̲b̲l̲e̲
List of same type records.
1.3.2 A̲b̲b̲r̲e̲v̲i̲a̲t̲i̲o̲n̲s̲
CSF CAMPS System Functions
GNS Global Number Series
ID Identification
MDP Message Distribution Package
SFM Storage and File Management
SSC System Status and Control
SyncEl Synchronization Element
TEP Terminal Package
THP Traffic Handling Package
TMP Table Management Package
2̲ ̲ ̲S̲U̲M̲M̲A̲R̲Y̲ ̲O̲F̲ ̲R̲E̲Q̲U̲I̲R̲E̲M̲E̲N̲T̲S̲
2.1 T̲M̲P̲ ̲D̲E̲S̲C̲R̲I̲P̲T̲I̲O̲N̲
TMP receives function requests from application packages
and SSC and returns answers by means of system call
monitor in CSF package.
TMP reads from disk and writes to disk via SFM.
Ref. fig. 2.1-1.
Fig. 2.1-1…01…Package Interrelationship
2.2 T̲M̲P̲ ̲F̲U̲N̲C̲T̲I̲O̲N̲S̲
2.2.1 T̲M̲P̲ ̲N̲o̲r̲m̲a̲l̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲s̲
The normal TMP functions are:
- Search In Tables
- Update Of Tables
- Reorganization Of Tables
- Back-up/Reload Of TMP Data
- Global Number Series Management
- System Parameter Management
2.2.1.1 S̲e̲a̲r̲c̲h̲ ̲I̲n̲ ̲T̲a̲b̲l̲e̲s̲
One or more records from a table are identified after
a key value and delivered to caller. More than one
key to the same table may be specified at a time.
Only the record fields requested by caller are delivered.
2.2.1.2 U̲p̲d̲a̲t̲e̲ ̲O̲f̲ ̲T̲a̲b̲l̲e̲
One record is changed, inserted in a table or removed
from a table.
2.2.1.3 R̲e̲o̲r̲g̲a̲n̲i̲z̲a̲t̲i̲o̲n̲ ̲O̲f̲ ̲T̲a̲b̲l̲e̲s̲
A table is reorganized so unused records are removed
and records in overflow area are put in their appropriate
place.
2.2.1.4 B̲a̲c̲k̲-̲u̲p̲/̲R̲e̲l̲o̲a̲d̲ ̲O̲f̲ ̲T̲M̲P̲ ̲D̲a̲t̲a̲
Tables are backed up by copying them to an offline
volume, or they are reloaded by copying them back in
their appropriate position at the on-line volume.
2.2.1.5 G̲l̲o̲b̲a̲l̲ ̲N̲u̲m̲b̲e̲r̲ ̲S̲e̲r̲i̲e̲s̲ ̲M̲a̲n̲a̲g̲e̲m̲e̲n̲t̲
The GNS is maintained in a way, so that they may be
read or updated by other packages.
The read may cause the GNS being read to be increased
by one.
2.2.1.6 S̲y̲s̲t̲e̲m̲ ̲P̲a̲r̲a̲m̲e̲t̲e̲r̲ ̲M̲a̲n̲a̲g̲e̲m̲e̲n̲t̲
A system parameter may be read or set to a new value.
2.2.2 F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲R̲e̲s̲p̲o̲n̲s̲i̲b̲i̲l̲i̲t̲i̲e̲s̲
2.2.2.1 I̲n̲i̲t̲i̲a̲l̲i̲z̲a̲t̲i̲o̲n̲,̲ ̲C̲l̲o̲s̲e̲ ̲D̲o̲w̲n̲,̲ ̲a̲n̲d̲ ̲R̲e̲s̲t̲a̲r̲t̲
2.2.2.1.1 I̲n̲i̲t̲i̲a̲l̲i̲z̲a̲t̲i̲o̲n̲
In initialization TMP reloads all TMP data and copies
the memory resident data into memory. Then a completion
code is returned to SSC and TMP will then wait for
further requests.
2.2.2.1.2 C̲l̲o̲s̲e̲ ̲D̲o̲w̲n̲
TMP has no responsibility of its own by close down.
2.2.2.1.3 R̲e̲s̲t̲a̲r̲t̲
By restart TMP will read memory resident data into
memory.
Then a completion code is returned to SSC and TMP will
then wait for further requests.
2.2.2.2 C̲h̲e̲c̲k̲ ̲P̲o̲i̲n̲t̲i̲n̲g̲ ̲a̲n̲d̲ ̲R̲e̲c̲o̲v̲e̲r̲y̲
TMP performs no check pointing.
All data except global number series will be copied
to disk each time they are updated so they will always
be recoverable.
All requests to TMP where TMP has not yet returned
an answer are lost by system failure.
2.2.2.3 E̲r̲r̲o̲r̲ ̲D̲e̲t̲e̲c̲t̲i̲o̲n̲ ̲a̲n̲d̲ ̲E̲r̲r̲o̲r̲ ̲H̲a̲n̲d̲l̲i̲n̲g̲
If input data in a TMP request are syntactically illegal
or inconsistent, the requesting process is retired
by using a Kernel call.
2.2.2.4 I̲n̲t̲e̲g̲r̲i̲t̲y̲ ̲o̲f̲ ̲O̲p̲e̲r̲a̲t̲i̲o̲n̲
TMP ensures that all requests will return an answer
to the calling process and that no request may cause
damage in the TMP process.
Inconsistence in TMP data caused by update may result
in no more output to processes requesting search than
a completion code.
Inconsistence in TMP data may only be coursed by a
misused update function.
The updated part of a table is written in a safety
copy at disk before the original table is updated.
2.2.2.5 D̲a̲t̲a̲ ̲C̲o̲l̲l̲e̲c̲t̲i̲o̲n̲
N/A.
2.2.2.6 S̲e̲c̲u̲r̲i̲t̲y̲
TMP ensures that no subprocess reads or updates data
not defined at system generation time.
2.3 C̲H̲A̲R̲A̲C̲T̲E̲R̲I̲S̲T̲I̲C̲S̲
2.3.1 T̲i̲m̲i̲n̲g̲
The access times specified here are maximum time per
key.
When more than one key is given by one request, the
mean time per key will be less than access time by
one key.
The total access time is the sum of the time used by
SFM and the time used by TMP.
The access times are:
FMS
TMP
- Parameter read or GNS access 0 ms 0,5
ms
- Search in memory resident tables 0 ms
10 ms
- Update of memory tables 80 ms
20 ms
- Search in disk tables 40 ms
20 ms
- Search in disk tables via reference 80 ms
30 ms
- Update of disk tables 120 ms
30 ms
2.3.2 T̲h̲r̲o̲u̲g̲h̲p̲u̲t̲
The throughput may be increased by having the disk
search coroutine in two incarnations.
The throughput will increase about 50%.
2.3.3 F̲l̲e̲x̲i̲b̲i̲l̲i̲t̲y̲
The number of data groups or the number of entries
in one data group may increase without affecting the
TMP Software.
The only difference is that more storage is needed.
2.3.4 A̲c̲c̲u̲r̲a̲c̲y̲
Any deviation from defined parameters will result in
the calling process being retired.
3̲ ̲ ̲E̲N̲V̲I̲R̲O̲N̲M̲E̲N̲T̲
3.1 E̲Q̲U̲I̲P̲M̲E̲N̲T̲
TMP executes in one processing unit consisting of more
than one CPU.
3.2 S̲O̲F̲T̲W̲A̲R̲E̲
3.2.1 S̲y̲s̲t̲e̲m̲ ̲S̲o̲f̲t̲w̲a̲r̲e̲
TMP uses the KERNEL, SFM, and CSF system software packages.
TMP must be controlled by an operation system, for
instance COPSY within SSC, defining the control parameters
used by TMP.
3.2.2 D̲e̲v̲e̲l̲o̲p̲m̲e̲n̲t̲ ̲S̲u̲p̲p̲o̲r̲t̲ ̲S̲o̲f̲t̲w̲a̲r̲e̲
The software used for development of this package is
contained in Support Software Package.
3.3 I̲N̲T̲E̲R̲F̲A̲C̲E̲S̲
3.3.1 E̲x̲t̲e̲r̲n̲a̲l̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲s̲
N/A
3.3.2 P̲a̲c̲k̲a̲g̲e̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲s̲
SSC, TEP, THP, and MDP interfaces to TMP by requesting
search and update functions.
3.4 F̲U̲N̲C̲T̲I̲O̲N̲S̲ ̲M̲A̲I̲N̲T̲A̲I̲N̲E̲D̲ ̲B̲Y̲ ̲O̲T̲H̲E̲R̲ ̲P̲A̲C̲K̲A̲G̲E̲S̲
TMP is supported by Coroutine Monitor and System Call
Monitor in the CSF package.
4̲ ̲ ̲T̲M̲P̲ ̲D̲E̲S̲I̲G̲N̲
4.1 T̲M̲P̲ ̲O̲V̲E̲R̲V̲I̲E̲W̲
Table Management Package performs search and update
functions at tables, system parameters, and GNS.
The functions in TMP will be as general as possible
so it may be possible to add further tables to the
TMP data without the processing modules should be changed.
4.1.1 F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲D̲e̲s̲c̲r̲i̲p̲t̲i̲o̲n̲
TMP functional description starts with a description
of data organization and access methods used by TMP.
This is followed by a general description of the functions
performed by TMP.
Finally, the functions are split up in subpackages
and each subpackage is briefly described.
4.1.1.1 T̲a̲b̲l̲e̲ ̲O̲r̲g̲a̲n̲i̲z̲a̲t̲i̲o̲n̲ ̲a̲n̲d̲ ̲A̲c̲c̲e̲s̲s̲ ̲M̲e̲t̲h̲o̲d̲s̲
4.1.1.1.1 T̲a̲b̲l̲e̲ ̲O̲r̲g̲a̲n̲i̲z̲a̲t̲i̲o̲n̲
All tables consist of a list of similar type records.
Ref. fig. 4.1.1.1-1. A table may be organized direct
or sequential.
Direct organization means that the records are identified
alone by their position in the table.
Sequential organization means that the records are
sorted in accordance with a primary key which also
identifies the record. The primary key field in a
record must be unique in one table. The records may
also be searched by a secondary key, but a secondary
key may identify more than one record in one table.
Refer fig. 4.1.1.1-2. Sequential organization may
be expanded to index sequential organization which
means that the table is split into a number of same
length blocks which are referred in another sequential
table containing a reference to last primary key in
each block. Ref. fig. 4.1.1.1-3.
Sequential organization has also an incarnation called
Secondary Key Organization. This type may be used
if a table is often accessed using a unique secondary
key. The secondary keys are put in sorted order in
a reference table where each secondary key has a reference
to the physical position of the record (ref. figure
4.1.1.1-4).
4.1.1.1.2 R̲e̲c̲o̲r̲d̲ ̲S̲t̲r̲u̲c̲t̲u̲r̲e̲
Each record in a table consists of two or more fields.
The first field in all record types is reserved for
TMP control data. The second field will contain the
primary key if the record has any.
The rest of the fields may contain data of various
kind.
All records known by TMP have from two to sixteen fields
of various length and are defined by a record description.
(Ref. figure 4.1.1.-5).
4.1.1.1.3 F̲i̲e̲l̲d̲ ̲S̲t̲r̲u̲c̲t̲u̲r̲e̲
There exist two field types. Simple fields and repeated
fields.
The simple field consists of one information field.
The repeated field consists of a defined number of
identical subfields. The first byte in a repeated field
will tell how many of the subfields are used. (Ref.
figure 4.1.1.1-5).
4.1.1.1.4 S̲e̲a̲r̲c̲h̲ ̲K̲e̲y̲ ̲S̲t̲r̲u̲c̲t̲u̲r̲e̲
The key is only a part of the SEARCH KEY which is used
by TMP search functions.
A search key consists of three parts:
- Key
- Record Type
- Search Mask
Key is one field value which shall be compared with
one or more fields in a record.
Record Type is the type of the records held in the
actual table. The type refers to the record description
(refer section 4.1.1.1.3).
Search Mask is a one word bit mask specified as input
parameter, where each bit set specifies that associated
field in record shall be used as key. Only by searching
secondary keys, more than one bit may be set. No bit
set is used when a direct organized table is accessed.
If a repeated field is specified as Key all subfields
will be compared.
4.1.1.1.5 T̲a̲b̲l̲e̲ ̲D̲e̲s̲c̲r̲i̲p̲t̲i̲o̲n̲
For each logical table access method there exists one
table description. This means that if the same input
key may give two different outputs there exist two
different table descriptions referring the same physical
table.
An example is if the one table description specifies
that the contents of first table are output to caller
and the other table description specifies that the
contents of first table are input to an automatic search
in a second level table. (E.g. AIG to PLA#s and AIG
to RIs).
The table descriptions hold the information necessary
for a search such as organization type, start address
and access rights.
The description also holds table load status, a time
stamp telling when the table was updated last time,
and an information word where supervisor may write
information to himself. Time stamp, supervisor information,
table ID and table load status may be read by all packages.
A subprocess is a group of modules having the same
access rights to TMP data.
The subprocess access masks are used to check that
no module accesses other data than specified during
system generation. The access rights are checked before
the search or update is started. (Ref. figre 4.1.1.1-6).
Fig. 4.1.1.1-1…01…Functional Description
Fig. 4.1.1.1-2…01…Functional Description
Fig. 4.1.1.1-3…01…Functional Description
Fig. 4.1.1.1-4…01…Functional Description
Fig. 4.1.1.1-5…01…Functional Description
Fig. 4.1.1.1-6…01…Functional Description
4.1.1.2 T̲a̲b̲l̲e̲ ̲S̲e̲a̲r̲c̲h̲
When TMP performs a search, it gets its input from
a data structure in the data area of the requesting
application process.
The segments containing this structure and the area
where output shall be delivered are mapped into TMP
process during the search.
The data structure contains the following information.
- Table ID.
- Output Address
- Output Buffer Length
- Search Mask
- Read Mask
- Number of Keys
- List of Keys
Table ID. is a reference to the table description containing
information necessary for this search.
Output address is a reference to the area where output
shall be delivered.
Output buffer length tells how much the output data
may fill.
Search Mask specifies which fields to be searched at.
Read Mask specifies which fields shall be delivered
by output.
Number of keys specifies how many input key values
are specified in key list.
List of keys is a list of field values used by search.
Before search TMP checks the input keys for syntax
and inconsistency and sorts them in a single linked
list.
The output is delivered in the same order as input
Keys were sorted. Each Key has a pointer referencing
its associated output.
The output is structured precisely as the input keys
so the outupt may be used as a new input just as it
is.
An application process may by request specify if the
first level output shall be used as input for search
of a second level output.
The input parameters for a one level search and a two
level search differs in the way that two different
table IDs are used.
The table ID for a two level search will contain a
reference to the table where the second level information
is held.
4.1.1.3 T̲a̲b̲l̲e̲ ̲U̲p̲d̲a̲t̲e̲
Table update will update one record specified by a
primary key or it may update one or more fields of
the same value to one new value in a table.
The single record update may remove a record, insert
a record or change the data fields.
The data fields to be changed may be all, or some specified
fields of same type which shall be set to the same
value or it may be all fields of a special value set
to another value.
The data field update may update the specified fields
in all records in a table to a specified value, or
update only the specified fields having a special value
to a new value.
4.1.1.4 T̲M̲P̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲s̲
The interface functions receive requests from application
processes and pass them on to TMP process which performs
the real processing.
The interface functions will also ensure that the application
processes get the responses sent by TMP process each
time a request is completed.
The interface functions will ensure that no unknown
request is passed on to TMP process.
4.1.1.5 S̲y̲s̲t̲e̲m̲ ̲P̲a̲r̲a̲m̲e̲t̲e̲r̲s̲ ̲a̲n̲d̲ ̲G̲l̲o̲b̲a̲l̲ ̲N̲u̲m̲b̲e̲r̲ ̲S̲e̲r̲i̲e̲s̲
System parameters and GNS can be read and updated.
A GNS may be read in the special way that it is increased
by one just before read. If maximum value is exceeded
by the increase, the series is reset to one.
All accesses except parameter update are performed
by the application processes by using monitor procedure
calls.
Parameter update is performed by TMP process as a normal
table update.
4.1.1.6 B̲a̲c̲k̲-̲u̲p̲ ̲a̲n̲d̲ ̲R̲e̲l̲o̲a̲d̲
Back-up copies a TMP file from the on-line to an off-line
disk.
Reload copies a TMP file from an off-line to the on-line
volume.
After reload, the new copied file is read into memory,
if it normally resides here.
4.1.1.7 R̲e̲o̲r̲g̲a̲n̲i̲z̲e̲
Reorganize removes unused records from a table and
puts records from an overflow area in their appropriate
position. Reorganize may be stopped by a request from
the Supervisor.
4.1.1.8 F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲B̲r̲e̲a̲k̲d̲o̲w̲n̲
To break this package down in subpackages, the functions
described in this chapter are split into three main
groups.
Each group is a subpackage containing functions with
common characteristics. The functions mapped on each
subpackage is shown at fig. 4.1.4.7-1.
The three subpackages are at the second level.
Fig. 4.1.1.7-1…01…Functional Breakdown
4.1.1.8.1 T̲a̲b̲l̲e̲ ̲S̲e̲a̲r̲c̲h̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲s̲
This subpackage receives search requests from a SyncEl.,
sorts the input keys and generates the output which
contains the wanted information.
4.1.1.8.1.1 S̲e̲a̲r̲c̲h̲ ̲C̲o̲m̲m̲u̲n̲i̲c̲a̲t̲i̲o̲n̲
This function receives one request from a SyncEl, passes
it on to processing and after processing it returns
a response to another SyncEl. specified by input parameters.
The request may be so simple that it is performed by
the communication function itself e.g., "set table
attributes" or "get table attributes".
4.1.1.8.1.2 S̲o̲r̲t̲ ̲K̲e̲y̲s̲
First, the access rights of calling subprocess are
checked.
Then, this function maps the segments containing input
data into TMP process and sorts the input keys. When
sorting the keys each key is checked for syntax and
consistency.
4.1.1.8.1.3 M̲e̲m̲o̲r̲y̲ ̲T̲a̲b̲l̲e̲ ̲S̲e̲a̲r̲c̲h̲
A record in a table or table part residing in memory
is found and compressed to the information wanted on
output.
During the compression, the output is delivered in
the area specified by input parameters.
4.1.1.8.1.4 D̲i̲s̲k̲ ̲T̲a̲b̲l̲e̲ ̲S̲e̲a̲r̲c̲h̲
Identifies the block where a given record in a disk
resident table should be and reads the actual block
into memory.
4.1.1.8.2 T̲a̲b̲l̲e̲ ̲U̲p̲d̲a̲t̲e̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲s̲
The table update functions will receive an update request,
perform it and return a response when the requested
function is completed.
By update request is meant:
- Table update request
- Parameter update request
- Reorganize request
- Back-up/Reload request
4.1.1.8.2.1 S̲e̲a̲r̲c̲h̲
This function uses the table search functions in such
a way so that the output is not only the record value,
but also its own address.
For disk resident tables, the actual disk block will
be read into memory in the update functions working
area.
4.1.1.8.2.2 U̲p̲d̲a̲t̲e̲ ̲R̲e̲c̲o̲r̲d̲
A record identified by address is updated to specified
value.
If the update is a remove record or insert record current
table block may be reorganized.
4.1.1.8.2.3 U̲p̲d̲a̲t̲e̲ ̲D̲i̲s̲k̲
An updated table block in memory is copied to disk
in a way so the table will always be recoverable.
4.1.1.8.2.4 S̲u̲p̲p̲o̲r̲t̲
This function may perform one of three independent
subfunctions. The three functions are:
- Reorganize table
- Back-up file
- Reload file
4.1.1.8.2.5 U̲p̲d̲a̲t̲e̲ ̲C̲o̲m̲m̲u̲n̲i̲c̲a̲t̲i̲o̲n̲
This function receives an update request from a SyncEl
and passes it on to processing.
After the requested function is completed, a response
is sent to another SyncEl specified by input parameters.
4.1.1.8.3 T̲M̲P̲ ̲M̲o̲n̲i̲t̲o̲r̲
TMP monitor maintains communication between application
processes and the TMP process.
TMP monitor also performs simple accesses to TMP data
which do not require many resources.
4.1.1.8.3.1 C̲h̲e̲c̲k̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲
The requested function is checked. If the request
is to TMP process, it is passed on to the process interface
function (ref. 4.1.1.7.3.2) otherwise it is performed
by TMP monitor itself.
4.1.1.8.3.2 P̲r̲o̲c̲e̲s̲s̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲
The input parameters from a request is sent to TMP
process via a SyncEl.
When sent, the response from TMP process is awaited.
When the response arrives at the answer SyncEl, it
is passed on to the application process.
4.1.1.8.3.3 G̲e̲t̲ ̲S̲y̲s̲t̲e̲m̲ ̲P̲a̲r̲a̲m̲e̲t̲e̲r̲s̲
The specified system parameter is read and delivered
to calling application process.
4.1.1.8.3.4 G̲e̲t̲ ̲G̲l̲o̲b̲a̲l̲ ̲N̲u̲m̲b̲e̲r̲ ̲S̲e̲r̲i̲e̲s̲
The specified series value is read and delivered to
calling application process.
If it is specified, the series value is increased by
one before read.
4.1.1.8.3.5 S̲e̲t̲ ̲G̲l̲o̲b̲a̲l̲ ̲N̲u̲m̲b̲e̲r̲ ̲S̲e̲r̲i̲e̲s̲
The specified series are set to specified value.
4.1.2 T̲M̲P̲ ̲S̲o̲f̲t̲w̲a̲r̲e̲ ̲S̲t̲r̲u̲c̲t̲u̲r̲e̲
TMP Software consists of two parts.
First part is the TMP process performing the most TMP
processing such as sorting, searching, and updating.
All TMP disk accesses are made by this process.
Second part is the TMP Monitor which is a set of procedures
maintaining the interface between application processes
and TMP process.
These procedures also perform simple processing which
do not require many resources.
Fig. 4.1.2-1 shows the TMP software components and
environment.
4.1.2.1 T̲M̲P̲ ̲P̲r̲o̲c̲e̲s̲s̲
The TMP process consists of four coroutines.
The memory search coroutine handles the search requests
requiring no disk accesses and maintains read and update
of table attributes.
The disk search coroutine handles the search requests
requiring one or more disk accesses.
The update coroutine handles the update requests.
The support coroutine handles the reorganize and back
up/re-load requests.
The requests are received from two SyncEls and answers
are directed to SynchEls associated to the requesting
modules.
The search requests are received from the SyncEl via
a semaphore, which makes it possible for the support
coroutine to request searches without accessing SyncEls.
Ref. fig. 4.1.3.2-3.
The search coroutines have their own working area while
the update and support coroutines share one working
area. This means that support coroutine must go in
a waiting state when an update request is made. This
synchronization is managed by using semaphores.
4.1.2.2 T̲M̲P̲ ̲M̲o̲n̲i̲t̲o̲r̲
The TMP monitor is a set of procedures executed in
system mode by calling process.
Fig. 4.1.2-1…01…TMP Software Structure
4.1.3 D̲a̲t̲a̲ ̲F̲l̲o̲w̲ ̲a̲n̲d̲ ̲C̲o̲n̲t̲r̲o̲l̲ ̲L̲o̲g̲i̲c̲
4.1.3.1 D̲a̲t̲a̲ ̲F̲l̲o̲w̲
Fig. 4.1.3.1-1 shows the data flow for a table update
request. Data flow for the other requests is so simple
that they easily may be identified in the functional
description and the control logic.
HIPO Diagram…01…Fig. 4.1.3.1-1
4.1.3.2 C̲o̲n̲t̲r̲o̲l̲ ̲L̲o̲g̲i̲c̲
Fig. 4.1.3.2-1 shows how TMP monitor passes requests
on to TMP process by sending them to SyncEls.
After processing, an answer is sent to the requesting
process via its associated answer SyncEl.
The TMP monitor receives the answer from the SyncEl
and delivers it to the application process.
Fig. 4.1.3.2-2 shows how TMP monitor is connected to
the application process by system call monitor.
The process communication sends the requests to SyncEls
and receives the associated answers from the answer
SyncEl by means of system call monitor.
System parameter and GNS management perform the processing
themselves and return the answer directly through system
call monitor.
During manipulation, the manipulation routines can
be locked by means of hardware semaphores.
Figure 4.1.3.2-3 shows how the TMP process coroutines
receive their request.
The search requests are received from a SyncEl via
a semaphore by the memory search coroutine.
Receiving via a semaphore makes it possible for support
coroutine to request searches without accessing syncEls.
If the search requires disk access the request is passed
on to the operation semaphore where disk search coroutine
is waiting when it is inactive else the memory search
coroutine performs the search itself.
Answers at searches are sent to an answer SyuncEl or
to the support coroutine answer semaphore depending
on where the request came from.
If the update request is a reorganize or a back-up/re-
load request it is passed on to the support coroutine.
Answers at updates are sent to an answer SyncEl.
Update coroutine and support coroutine share their
working area so only one of them executes at a time.
This Synchronization is managed by a semaphore and
two flags.
The update coroutine will always have first priority
to the working area.
Fig. 4.1.3.2-1 Software Structure
Fig. 4.1.3.2-2 Software Structure
Fig. 4.1.3.2-3 Software Structure
Fig. 4.1.3.2-4
4.1.4 C̲o̲m̲m̲o̲n̲ ̲D̲a̲t̲a̲ ̲E̲l̲e̲m̲e̲n̲t̲s̲
The data common to TMP can be split into two groups:
the information data and the control data.
The information data are the data held in the system
parameters and tables. These data are mainly used to
deliver to calling application packages so they can
read the information contained therein.
The control data are the data used by TMP for searching
and updating the information data.
4.1.4.1 I̲n̲f̲o̲ ̲D̲a̲t̲a̲
There are two main groups of information data:
- System Parameters
- Tables.
Each group is characterized by the way its data are
organized and accessed.
4.1.4.1.1 S̲y̲s̲t̲e̲m̲ ̲P̲a̲r̲a̲m̲e̲t̲e̲r̲s̲
The system parameters are held in a set of variable
length records, each containing one parameter. The
parameters are only identified by a parameter number.
For each parameter record there exists a description
giving a pointer to the record and the record length.
Ref. fig. 4.1.4.1.1-1.
The record description is organized as a direct table,
addressed by parameter number. System parameters are
read by TMP Monitor and updated by Table Update Functions.
Fig. 4.1.4.1.1-1 Common Data
4.1.4.1.2 T̲a̲b̲l̲e̲s̲
The tables are organized as directly organized tables
or sequentially organized tables. The sequentially
organzied tables are supplied with index reference
and/or secondary search key reference as described.
To meet the requirements to table search and table
update TMP must maintain the following physical tables.
- AIG table with memory index and secondary search
key AG.
- PLA table with memory index and secondary search
key PLA#.
- Local PLA table
- RI table with memory index
- Local RI table
- Circuit table
- Exercise SIC table with memory index
- Normal SIC table with memory index
- Crisis SIC table with memory index
- Normal SDL table
- Crisis SDL table
- SCD table
- Port table
- Subprocess table
- Process table
- Software table
- PU table
- Disk table
- TDX Bus table
- Command table
- Operating Signal table
- Technical Error Report table
- User Profile table
- Terminal Profile table
- Device Profile table
- Channel Profile table
- SSC Parameter table
- Supervisor Parameter table
4.1.4.2 C̲o̲n̲t̲r̲o̲l̲ ̲D̲a̲t̲a̲
TMP control data are private TMP data used by accessing
the information data.
The control data are:
- Table Descriptions
- Index Tables
- Secondary Search Key Tables.
The table descriptions contain all information about
physical tables necessary for a search or an update.
Ref. fig. 4.1.4.2-1.
The index tables contain the last key at each block
in the associated table. There is one index table for
each index sequential table. Ref. fig. 4.1.1.1-3.
The secondary search key tables contain all secondary
search keys in sorted order. For each key there is
a reference to the associated record. The secondary
key value is unique to the table. Ref. fig. 4.1.1.1-4.
Fig. 4.1.4.1-1 Control Data
4.1.5 E̲x̲t̲e̲r̲n̲a̲l̲ ̲D̲a̲t̲a̲ ̲E̲l̲e̲m̲e̲n̲t̲s̲
There are two groups of data elements shared with other
packages:
- Table Attributes
- TMP Communication Buffers
The Table Attributes are the first three words in the
table description.
The communication buffers are the area mapped in from
the application processes where search input and output
parameters are written.
4.1.5.1 T̲a̲b̲l̲e̲ ̲A̲t̲t̲r̲i̲b̲u̲t̲e̲s̲
The first three words in the table description are
the table ID, the table load status, time stamp set
by TMP after previous update and one word set by TMP
after a special supervisor request. These three words
may be read by all packages. Ref. fig. 4.1.4.2-1.
4.1.5.2 T̲M̲P̲ ̲C̲o̲m̲m̲u̲n̲i̲c̲a̲t̲i̲o̲n̲ ̲B̲u̲f̲f̲e̲r̲s̲
TMP communication buffers are the segments mapped into
TMP process during a table search.
When these buffers contain input for search they contain
a head and a data area.
The head holds information describing the requested
search. Ref. fig. 4.1.5.2-1.
The data area contains a list of key values.
All keys are of the same type and they are all followed
by one free word reserved as output pointer. Ref. fig.
4.1.5.2-1.
The data area has also a free part reserved for output
data. Ref. fig. 4.1.5.2-1.
When the buffers contain input for update they contain
structures as described in the interface section. Refer
section 4.1.6.1.
Fig. 4.1.5.2-1 External Data Elements
4.1.6 T̲M̲P̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲s̲
Application packages interface to TMP by requesting
a function and later on receiving an answer.
4.1.6.1 T̲M̲P̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲s̲
The interface functions to TMP are as follows:
- Search
- Get System parameter
- Get GNS
- Get Table Attributes
- Update
- Set GNS
- Set Table Attributes
- Reorganize
- Backup
- Reload.
These interface functions are described in the paragraphs
4.1.6.1 to 12. For each interface function there exists
a function code used by call. This is not described
as part of input parameters.
A process may only access the data it has access rights
to and only by the functions it is allowed to use with
this special data.
All functions have a completion code as output. This
Completion code may have different values which is
not described in the single paragraphs. The completion
code values may be one of the following.
Not all values might be used for all functions.
Completion code values.
- COMPLETE
- Output buffer full
- No next entry
- Table already full
- One or more non-existing keys in input
- Function interrupted
4.1.6.1.1 S̲e̲a̲r̲c̲h̲
The output associated with the keys in the input list
in a communication buffer as described in 4.1.5.1,
is delivered in the output area in the same buffer.
The search mask has a bit set for each field that is
to be searched. Only one type of fields must be referred.
If the table contains records with repeated fields,
all subfields are compared by search, but only if associated
bit is set.
Input: Buffer Head
- Reference to the head of a communication
buffer containing input for search.
Output: CC.
4.1.6.1.2 G̲e̲t̲ ̲S̲y̲s̲t̲e̲m̲ ̲P̲a̲r̲a̲m̲e̲t̲e̲r̲s̲
The system parameter specified by parameter number
is delivered to caller. If the parameter length does
not exceed two words, it is delivered in two registers.
Otherwise it is delivered at an address specified by
caller.
Input: Parameter Number
Output Address.
Output: Parameter Value
CC.
4.1.6.1.3 G̲e̲t̲ ̲G̲l̲o̲b̲a̲l̲ ̲N̲u̲m̲b̲e̲r̲ ̲S̲e̲r̲i̲e̲s̲
The series value specified by series ID. is delivered
to caller. If it is specified, the value is increased
by one before read.
The value is delivered in two registers in ASCII representation.
A three digit serial number will always start with
the ASCII representation of a "space".
Input: GNS ID.
Increase
- Boolean telling whether the GNS shall be
increased.
Output: GNS Value
CC.
4.1.6.1.4 G̲e̲t̲ ̲T̲a̲b̲l̲e̲ ̲A̲t̲t̲r̲i̲b̲u̲t̲e̲s̲
The attributes for specified table description are
delivered in three registers. The attributes are Table
ID, Table Load Status, Time Stamp and Supervisor Information.
Input: Table ID.
Output: Table ID
Table Load Status
Time Stamp
Supervisor Information
CC.
4.1.6.1.5 U̲p̲d̲a̲t̲e̲
The specified record(s) are updated to specified value.
The update must be one of the following:
- Remove Record
- Insert Record
- Change Specified Fields
- Change All Fields With Value
The update parameters here defined are contained in
a communication buffer (Ref. 4.1.5.1).
4.1.6.1.5.1 R̲e̲m̲o̲v̲e̲ ̲R̲e̲c̲o̲r̲d̲
The desired records are removed from the specified
table.
If a primary key is specified, only one record is removed.
For a secondary key, all records with the key are removed.
Input: Table ID
Key
Search Mask.
Output: CC
4.1.6.1.5.2 I̲n̲s̲e̲r̲t̲ ̲R̲e̲c̲o̲r̲d̲
The specified record is inserted at the position where
it belongs.
Input: Table ID
Record.
Output: CC.
4.1.6.1.5.3 C̲h̲a̲n̲g̲e̲ ̲S̲p̲e̲c̲i̲f̲i̲e̲d̲ ̲F̲i̲e̲l̲d̲s̲
One or more specified fields in one record are changed
to a new value.
The fields are specified by their pattern. A specified
field has an associated bit in a search mask set.
The primary Key must not be one of the specified fields.
The new field values are specified as a list of fields.
The record is identified by primary Key.
Input: Table ID
Key
Field List
Search Mask.
Output: CC.
4.1.6.1.5.4 C̲h̲a̲n̲g̲e̲ ̲A̲l̲l̲ ̲F̲i̲e̲l̲d̲s̲ ̲w̲i̲t̲h̲ ̲V̲a̲l̲u̲e̲
All fields in a record or in a whole table are changed
to a new value if their old value is the specified
one.
All the fields must be of the same type as the one
specified.
A search mask may specify which fields shall be compared.
If the specified field is a repeated field the field
values must be subfield values.
The field must not be the primary key.
Input: Table ID
Key
- If used, only one record is changed.
Search Mask
Old Field Value
New Field Value.
Output: CC.
4.1.6.1.6 S̲e̲t̲ ̲G̲l̲o̲b̲a̲l̲ ̲S̲e̲r̲i̲a̲l̲ ̲N̲u̲m̲b̲e̲r̲
The specific GNS is set to specific values.
The indicator for three or four digits will also be
set to specified value. It is set to three digits if
first ASCII character in GNS value is a space.
Input: GNS ID
GNS Value
- ASCII Representation
Output: CC.
4.1.6.1.7 S̲e̲t̲ ̲T̲a̲b̲l̲e̲ ̲A̲t̲t̲r̲i̲b̲u̲t̲e̲s̲
The supervisor information word in specified table
description is set to specified value.
Input: Table ID
Information Word
- One word
Output: CC.
4.1.6.1.8 R̲e̲o̲r̲g̲a̲n̲i̲z̲e̲
The specified table is reorganized and the references
to it are updated.
Input: Table ID.
Output: CC.
4.1.6.1.9 B̲a̲c̲k̲u̲p̲
Specified file is copied from on-line to off-line volume
under the same file name.
Input: File Name.
Output: CC.
4.1.6.1.10 R̲e̲l̲o̲a̲d̲
Specified file is copied from off-line to on-line volume,
into the file of the same file name.
Input: File Name.
Output: CC.
4.1.6.2 P̲a̲c̲k̲a̲g̲e̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲ ̲O̲v̲e̲r̲v̲i̲e̲w̲
The application packages have capability to access
TMP data as described in this paragraph.
Each logical table has its own table description and
thus also its own access masks telling which subprocesses
having read and/or update access rights to associated
table.
4.1.6.2.1 L̲o̲g̲i̲c̲a̲l̲ ̲T̲a̲b̲l̲e̲s̲
Logical TMP knows the following tables:
Routing tables:
- AG table
- AIG table
- PLA table
- PLA# table
- Local PLA table
- Local RI table
- Circuit table
Distribution tables:
- Exercise SIC table
- Norm. SIC table
- Crises SIC table
- Normal SDL table
- Crisis SDL table
- SCD table
Configuration tables
- Port table
- Subprocess table
- Process table
- Software table
- PU table
- Disk table
- TDX Bus table
Other Tables
- Command table
- Operation Signal table
- Technical Error Report table
Profiles
- User Profile table
- Terminal Profile table
- Device Profile table
- Channel Profile table
System Parameters
- SSC Parameter table
- Supervisor Parameter table
GNS
- Global Number Series tables
4.1.6.2.2 P̲a̲c̲k̲a̲g̲e̲ ̲A̲c̲c̲e̲s̲s̲ ̲R̲i̲g̲h̲t̲s̲
A package may only access the data which it has access
rights to and only by using the functions allowed for
actual data type (e.g. tables or GNS).
The access rights are defined by system generation
time.
Figure 4.1.6.2-1 shows which functions each package
uses by interface to TMP.
Figure 4.1.6.2-2 shows which TMP data each package
has read access to.
Figure 4.1.6.2-3 shows which TMP data each package
has update access to.
Figure 4.1.6.2-1
TMP READ ACCESS
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
PACKAGES SSC TEP THP MDP
T̲A̲B̲L̲E̲S̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
Routing tables All All
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
Distribution All All
tables
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
Configuration All Port Table
tables
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
Other tables Technical Command Operating
Error rep. table ope- signal
table rating sig- table
nal table
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
Profiles All All Channel
Profile
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
System Parameters All All All All
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
GNS All All All All
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
FIGURE 4.1.6.2-2…01…PACKAGE INTERFACE OVERVIEW
TMP UPDATE ACCESS
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
PACKAGES SSC TEP THP MDP
T̲A̲B̲L̲E̲S̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
Routing tables All Circuit
table
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
Distribution All
tables
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
Configuration All Port Table Port table
tables
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
Other tables Technical Command
Error rep. table ope-
table rating sig-
nal table
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
Profiles All Channel
Profile
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
System Parameters SSC para- Supervisor
meters parameters
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
GNS All All All All
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
FIGURE 4.1.6.2-3…01…PACKAGE INTERFACE OVERVIEW
4.1.6.3 S̲u̲b̲p̲a̲c̲k̲a̲g̲e̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲
The TMP Monitor sends function requests to search and
update subpackages.
Search and update subpackages request TMP monitor to
return output to the calling process.
The update subpackage requests search functions from
the search subpackage and the search subpackage sends
the output back to update subpackage.
The update subpackage executes some of the search subpackages
procedures and will, after execution, have determined
the output itself.
Ref. fig. 4.1.6.3-1
FIGURE 4.1.6.3-1
