top - download
⟦cdae4c8e2⟧ Wang Wps File
Length: 31479 (0x7af7)
Types: Wang Wps File
Notes: CPS/TCN/046
Names: »2298A «
Derivation
└─⟦81108f261⟧ Bits:30006114 8" Wang WCS floppy, CR 0183A
└─ ⟦this⟧ »2298A «
WangText
J…0d…J
J…06…I…0a…I…0e…I…02…H…08…H…0d…H…86…1
…02…
…02… …02…
…02…CPS/TCN/046
…02…820611…02……02…#
DAMOS
MEMORY
SIZES
BASED
ON
CAMPS
RESOURCES…02……02…CAMPS
1 PURPOSE AND SCOPE ..............................
2 SOFTWARE COMPONENTS ............................
2.1 DAMOS Program Size .........................
2.2 DAMOS Data Size ............................
2.2.1 DAMOS Boot loader data .................
2.2.2 DAMOS Process Manager and Dispatcher
Data ..................................
2.2.3 DAMOS Error Processor data .............
2.2.4 DAMOS Directory function data ..........
2.2.5 DAMOS Page Manager data ................
2.2.6 DAMOS Process Communication data .......
2.2.7 DAMOS Idle process data ................
2.2.8 DAMOS Device Management Data ...........
2.2.9 DAMOS Floppy Disk Cache Data ...........
2.2.10 DAMOS FMS Data ......................
2.2.11 DAMOS TMS Data .......................
2.3 DAMOS PPS SIZE .............................
2.3.1 Level 8 parameters .....................
2.3.1.1 VDU user ...........................
2.3.1.2 MTP ̲ROP, LTP ̲ROP ...................
2.3.1.3 OCR, PTR, PTP, LTP ̲PTR .............
2.3.1.4 NICS TARE ..........................
2.3.1.5 SCARS, CCIS, TRC ̲PTOP ..............
2.3.1.6 CMI ................................
2.3.1.7 COPSY ..............................
2.3.2 Object descriptor table (ODT) ..........
2.3.2.1 Process objects ....................
2.3.2.2 Memory Segments ....................
2.3.2.2.1 Memory segments for COPSY childr
2.3.2.2.2 Memory segments for COPSY ......
2.3.3 Syncronization Elements ................
2.3.3.1 Syncronization elements for COPSY ch
2.3.3.2 Syncronization elements in COPSY ...
2.3.4 CPU objects ............................
2.3.5 CPU Pools ..............................
2.3.6 Device Objects .........................
2.3.7 Resource pool object ...................
3 RESOURCE SPECIFICATION ..........................
3.1 KERNEL RESOURCE SPECIFICATION ...............
3.1.1 No of CPUs ...............................
3.1.2 No of CPU Pools ..........................
3.1.3 No of Processes ..........................
3.1.3.1 Process Allocation ...................
3.1.4 No of Main Memory Pages ..................
3.1.5 No of Segments ...........................
3.1.6 Synchronization Elements .................
3.1.6.1 DAMOS Internal .......................
3.1.6.2 FMS/TMS related sync. elements .......
3.1.6.3 CAMPS service system sync. elements ..
3.1.7 INFO Elements ............................
3.1.8 NO of simultaneous I/O requests ..........
3.1.9 No. of cataloged objects .................
3.2 TMS RESOURCE SPECIFICATION ...................
3.2.1 No of Users ..............................
3.2.2 No of Devices ............................
3.2.3 No of Subdevices .........................
3.2.4 No of Connections ........................
3.2.5 No of Operations .........................
1̲ ̲ ̲P̲U̲R̲P̲O̲S̲E̲ ̲A̲N̲D̲ ̲S̲C̲O̲P̲E̲
The purpose of this document is to calculate the size
of the DAMOS program and Data, on basis of the resources
which are used in CAMPS.
2̲ ̲ ̲S̲O̲F̲T̲W̲A̲R̲E̲ ̲C̲O̲M̲P̲O̲N̲E̲N̲T̲S̲
On figure 2-1 is shown the summary of the DAMOS memory
consumption. The figure is described in details in
the following sections.
It shall be remarked that in the calculation on figure
2-1 the PPS size of the COPSY children is set to 2048
words per PPS. It is stated that DAMOS only uses 1537
words per PPS. Therefore there will be a space of 500
words in each PPS which can be used by the CAMPS system
software (CSF).
DAMOS PROGRAM SIZE
- GPS (Global Program Segments) : 11
- KPS (Kernel Program Segments) : 32
- IDLE (Idle Processes) : 1
- ROOT : 2
- FMS ̲MOVING + FMS ̲FIXED : 9
- TMS : 6
DAMOS DATA SIZE
̲ BOOT LOADER : 2
- PMD (Process Manager & Dispatcher : 4
- EP (Error Processor) : 4
- DF (Directory Functions) : 3
- PM (Page Manager) : 10
- PCF (Process Communication Facility) : 67
- IDLE Process data : 2
- DVM (Device Manager) : 22
- FLOPPY DISK CACHE : 4
- FMS ̲MOVING : 11
- FMS ̲FIXED : 11
- TMS : 34
- CAMPS PROCESS PPS's
- COPSY (5403) : 6144 (6K)
-̲ ̲C̲O̲P̲S̲Y̲ ̲C̲H̲I̲L̲D̲R̲E̲N̲ ̲5̲5̲ ̲x̲ ̲2̲0̲4̲8̲ ̲(̲1̲5̲3̲7̲)̲ ̲ ̲ ̲ ̲:̲ ̲1̲1̲2̲6̲4̲0̲ ̲(̲1̲1̲0̲K̲)̲
T̲O̲T̲A̲L̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲3̲5̲1̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲
Figure 2-1
Summary of the DAMOS memory
consumption (words)
2.1 D̲A̲M̲O̲S̲ ̲P̲r̲o̲g̲r̲a̲m̲ ̲S̲i̲z̲e̲
The program size of the DAMOS kernel and Handlers are
as follows:
Global Program Segment (- Stream I/O) 11K
Kernel Program Segment
This includes following Handlers 32K
- DISK Handler
Floppy Disk Handler
OC Handler
LP Handler
DMA Handler
LTU basic
LTU Low
LTU VDU
TDX Handler (except Highlevel protocols
which are TBD)
Idle process program 1K
Root program 2K
FMS program 9K
TMS program ̲6̲K̲ ̲
Total DAMOS Program SIZE 61K
====
2.2 D̲A̲M̲O̲S̲ ̲D̲a̲t̲a̲ ̲S̲i̲z̲e̲
2.2.1 D̲A̲M̲O̲S̲ ̲B̲o̲o̲t̲ ̲l̲o̲a̲d̲e̲r̲ ̲d̲a̲t̲a̲
The DAMOS Boot loader occupies two translation tables.
Physical page 0,1 is reserved which means that the
Boot Loader uses 2̲K̲ ̲w̲o̲r̲d̲s̲ of PU RAM. This size is fixed.
2.2.2 D̲A̲M̲O̲S̲ ̲P̲r̲o̲c̲e̲s̲s̲ ̲M̲a̲n̲a̲g̲e̲r̲ ̲a̲n̲d̲ ̲D̲i̲s̲p̲a̲t̲c̲h̲e̲r̲ ̲D̲a̲t̲a̲
The DAMOS Process Manager and Dispatcher uses data
as follows:
46 words x NO OF PROCESSES
+ 10 words x NO OF CPUS
+180 words x NO OF CPU POOLS
+ 2 words x NO OF TTCBs
For calculation of the kernel resources refer section
3.1.
(46 x 63) + (10 x 3) + (180 x 3) + (2 x 64) = 3596
words
4̲K̲ ̲w̲o̲r̲d̲s̲
2.2.3 D̲A̲M̲O̲S̲ ̲E̲r̲r̲o̲r̲ ̲P̲r̲o̲c̲e̲s̲s̲o̲r̲ ̲d̲a̲t̲a̲
The DAMOS Error Processor uses 4̲K̲ ̲w̲o̲r̲d̲s̲ debug data
to save the translation tables. This size is fixed.
2.2.4 D̲A̲M̲O̲S̲ ̲D̲i̲r̲e̲c̲t̲o̲r̲y̲ ̲f̲u̲n̲c̲t̲i̲o̲n̲ ̲d̲a̲t̲a̲
The Damos Directory function uses 1K words for data
and 2K words for the PPS. Total area 3̲K̲ ̲w̲o̲r̲d̲s̲.̲
A catalogued object was at least (in DF):
- 1 catalogue entry …1a… 16 words
- min. 2 ACLE …1a… 3 words
giving minimum 22 words.
CAMPS contains 59 catalogued objects (refer 3.1.9)
corresponding to 1298 words. So the DF will occupy
2K in the PPS.
2.2.5 D̲A̲M̲O̲S̲ ̲P̲a̲g̲e̲ ̲M̲a̲n̲a̲g̲e̲r̲ ̲d̲a̲t̲a̲
The DAMOS Page Manager uses data as follows:
8 x NO OF PROCESSES
+8 x NO OF SEGMENTS
+7 x NO OF MAINMEMORY PAGES
+3 x NO OF PAGE MANAGER LIST ELEMENTS
For calculation of the kernel resources refer section
3.1.
The number of list elements is calculated as follows:
1,1 x NO OF MAINMEMORY PAGES
+1,1 x NO OF SEGMENTS
+0,6 x NO OF VIRTUAL MEMORYPAGES
+ 6 x NO OF PROCESSES =
(1,1 x 640) + (1,1 x 189) + 0,6 x 0) + (6 x 63) = 1290
List elements
Total size of the Page Manager data =
(8 x 63) + (8 x 189) + (7 x 640) + (3 x 1290) = 10366
1̲0̲,̲0̲K̲ ̲w̲o̲r̲d̲s̲
2.2.6 D̲A̲M̲O̲S̲ ̲P̲r̲o̲c̲e̲s̲s̲ ̲C̲o̲m̲m̲u̲n̲i̲c̲a̲t̲i̲o̲n̲ ̲d̲a̲t̲a̲
The DAMOS Process Communication Facilities uses data
as follows:
6 x SYNC ̲ELEMENTS
+ 11 x PROCESS COMMUNICATION LIST ELEMENTS
+ 19 x INFORMATION ELEMENTS
For calculation of the kernel resources refer section
3.1. The number of List Elements is equal to the number
of Info Elements.
(6 x 240) + (11 x 2222) + (19 x 2222) = 68,1K = 6̲7̲K̲
̲w̲o̲r̲d̲s̲
2.2.7 D̲A̲M̲O̲S̲ ̲I̲d̲l̲e̲ ̲p̲r̲o̲c̲e̲s̲s̲ ̲d̲a̲t̲a̲
The DAMOS Idle processes uses 1̲K̲ ̲w̲o̲r̲d̲s̲ data, and 1K
words for the PPS. Total Area = 2̲K̲ ̲w̲o̲r̲d̲s̲.̲
The SIZE of this data area is fixed.
2.2.8 D̲A̲M̲O̲S̲ ̲D̲e̲v̲i̲c̲e̲ ̲M̲a̲n̲a̲g̲e̲m̲e̲n̲t̲ ̲D̲a̲t̲a̲
The DAMOS Device Management Data uses data as follows:
Kernel Common Segment 400
words
Resource Manager:
60 words x NO OF PROCESSES
+15 words x NO OF POOLS (equal 8 used by DAMOS)
= (60 x 63) + (15 x 8) = 3900
words
Interrupt Vector Table 1024
words
Logical Device Table
2 words (3 words + NO OF DEVICES) = 3+(2x7) = 20
words
LP Handler 265
words
OC Handler 226
words
FD Handler 1255
words
DISM Handler 1255
words
DMA Handler 1674
words
LTU Handler:
674 words x NO OF LTUs
+ 95 words x NO OF LINES (NICS ̲TARE,SCARS,CCIS)
= (674 x 6) + (95 x 8) = 4804
words
TDX Handler:
Fixed SIZE +
7 WORDS x NO OF BUFFERS
+ 73 WORDS x NO OF BUSSES
+ 53 WORDS x NO OF LTUXs
+ 88 WORDS x NO OF VDUs =
825 + (364 x 7) + (73 x 1) +
(53 x 20) + (88 x 32) = 7322
words
Total =22140
words
2̲2̲K̲
̲w̲o̲r̲d̲s̲
2.2.9 D̲A̲M̲O̲S̲ ̲F̲l̲o̲p̲p̲y̲ ̲D̲i̲s̲k̲ ̲C̲a̲c̲h̲e̲ ̲D̲a̲t̲a̲
The DAMOS Floppy Disk Cache uses 4̲K̲ ̲w̲o̲r̲d̲s̲ data. The
SIZE of this data area can be reduced to 1K words if
necessary.
2.2.10 D̲A̲M̲O̲S̲ ̲F̲M̲S̲ ̲D̲a̲t̲a̲ ̲
The DAMOS FMS uses data as follows:
- FMS DATA static (fixed) 1K words
- PPS SIZE for FMS 2K words
- FMS DATA variable…0e…*…0f… 8̲K̲ ̲w̲o̲r̲d̲s̲
- Total (FMS processes) 11K words x 2 =
2̲2̲K̲ ̲w̲o̲r̲d̲s̲
…0e…*…0f…The SIZE of the variable data part can be calculated
as for TMS but the algorithm has not been available
from SSD.
2.2.11 D̲A̲M̲O̲S̲ ̲T̲M̲S̲ ̲D̲a̲t̲a̲
The DAMOS TMS uses data as follows:
- TMS DATA static (fixed) 1K words
- PPS SIZE for TMS 2K words
- TMS DATA variable
22 words x NO OF USERS
+ 6 words x NO OF DEVICE
+ 29 words x NO OF SUBDEVICES
+ 11 words x NO OF CONNECTIONS
+ 34 words x NO OF OPERATIONS
+ 30 words x NO OF SELECTORS
+ 3 words x NO OF ACLES
For calculation of the Resoruce specification refer
section 3.2
(22 x 45) + (6 x 8) + (29 x 318) + 11 x 445) + (34
x 472) +
(30 x 0) + (3 x 0) = 31203 words
TOTAL TMS SIZE = 3̲4̲K̲
̲w̲o̲r̲d̲s̲
2.3 D̲A̲M̲O̲S̲ ̲P̲P̲S̲ ̲S̲I̲Z̲E̲
The DAMOS PPS is illustrated overleaf. It contains:
- IOS data : refer section
2.3.1
- XFER data (16 words)
- object descriptor table (ODT) : refer section
2.3.2
- clean up references (16 words)
- context frames (16 x 15 = 240 words)
- parameter stack (400)
- the PPP (323 words)
Figure 2.3-1 summarizes the sizes.
Figure 2.3-1
DAMOS PPS
COMPONENT COPSY COPSY CHILD
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
IOS 2760 478 (max)
XFER 16 16
ODT 412 x 4 16 x 4
CLEAN UP REFS 16 16
CONTEXT 16 x 15 16 x 15
PARAM STACK 400 400
PPP 323 323
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲
…8f…T̲O̲T̲A̲L̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲5̲4̲0̲3̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲1̲5̲3̲7̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲…0e…
Figure 2.3-2
DAMOS PPS Component Sizing (words)
2.3.1 L̲e̲v̲e̲l̲ ̲8̲ ̲p̲a̲r̲a̲m̲e̲t̲e̲r̲s̲
For processes using
- TMS or
- FMS ̲MOVING or
- FMS ̲FIXED
the following parameters have to be specified:
- IOCBs (IO control block)
Max pending I/O requests. A cancel upon a request
requires an IOCB. Also, MMON (MMS) requests require
an IOCB.
- FSCBs (File Descriptor Control Block)
No of open files/lines/VDU splits.
- TPE (Termination Parameter Element)
The TLE's are the elements in the transfer list
containing the physical address of the (user IOs)
buffers.
A TLE is required per IO request multiplied by
the number of chained BLEs, which define the buffer.
- TTCB (Translation Table Control Block)
The XFER module must be supplied with the logical
address of a translation table, holding the physical
page number for each data area.
No CAMPS processes use chained buffers.
In the figures overleaf the various resource consumptions
per process type is specified.
A cancel implies only one IOCB per process as no
INIT cancel exists.
For IOCB, FDCBs the consumption for
- the first subprocess in the process is given
- the remaining subprocesses in the process are given.
PROCESS IOCB, TPE, TLE FDCB FSCB
TTCB
TYPE FIRST OTHER CANCEL FIRST OTHER FMS FMS
TMS
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲M̲O̲V̲I̲N̲G̲ ̲F̲I̲X̲E̲D̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
VDU 5 5 1 5 4 1 1 1
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲MTP ̲ROP
LTP ̲ROP 3 3*3 1 2 2 1 1 1
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
NICS ̲
TARE 8 2 x 8 1 2 2 1 1
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
PTR,
LTP ̲PTR 2 3 x 2 1 1 3 x 1 1 1
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
PTP
OCR 2 1 1 0 1 1
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
SCARS
CCIS 4 1 x 4 1 1 1 1 1
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
TRC ̲
PTOP 4 3 x 4 1 1 3 x 1 1 1
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
TMP 2 15 1 1 1
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
LOG 1 1 1 1
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
UMAM 1 11 1 1
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
CMI 8 1 6 1 1 1
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
SAK 5 8 1 1
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
STP 1 1 1 1
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
CSF
OLD
SPIP 0 0 0 0
ALS
A̲N̲B̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲COPSY 106 1 326 1 1 1 1
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
Figure 2.3.1-1
Level 8 parameters per process type for IO ̲system.
IOCB(3 words) TOTAL
LEVEL8
PRO- TPE (6 words) IOCBs
SIZE
CESS TLE (7 words) ALL FDCB FSCB
TTCB NO OF WORDS
TYPE PROCES- (3 words) (2 words)
(64 words) PROCES-
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲S̲E̲S̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲S̲E̲S̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
VDU 11 (2)* 176 9 2 1
16
271
MTP ̲ROP 13 (4) 52 4 2 1
4
288
LTP ̲ROP 13 (4) 0 4 2 1 (6)
0
288
NICS
TARE 25 50 4 1 1
2
478
LTP ̲PTR 9 0 4 1 1 (6)
0
222
PTR 9 9 4 1 1
1
222
PTP 2 2 1 1 1
1
101
OCR 2 2 1 1 1
1
101
SCARS
CCIS 9 9 2 1 1
1
216
TRC
PTDP 17 102 4 1 1
6
318
TMP 2 (2) 2 15 2 1
1
145
LOG 1 (1) 1 1 1 1
1
85
UMAM 1 (1) 1 11 1 1
1
115
CMI 9 (1) 9 6 2 1
1
230
SAR 5 (5) 5 8 1 1
1
170
STP 1 (1) 1 1 1 1
1
85
CSF 0 0 0 0 0
1
0
OLD 0 0 0 0 0
1
0
SPIP 0 0 0 0 0
1
0
ALS 0 0 0 0 0 0
1
0
AAB 0 0 0 0 0 0
1
0
COPSY 107 (4) 107 326 3 1
1 2760
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
530
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
Figure 2.3.1-2
* The figures in parenthesis denotes the FMS
part.
It is assumed that only TRC ̲PTOP connection
exists
and that no LTPs exist.
2.3.1.1 V̲D̲U̲ ̲u̲s̲e̲r̲
The IOCBs originate from
- 1 format file
- 1 function key
- 1 upper screen
- 2 lower screen (2 x buffered)
the FDCBs originate from
- 2 splits a 2 connection
- 1 format file
2.3.1.2 M̲T̲P̲ ̲R̲O̲P̲,̲ ̲L̲T̲P̲ ̲R̲O̲P̲
The IOCBs originate from
- 1 format file
- 1 line run 2 x buffered
2.3.1.3 O̲C̲R̲,̲ ̲P̲T̲R̲,̲ ̲P̲T̲P̲,̲ ̲L̲T̲P̲ ̲P̲T̲R̲
The IOCBs originate from
- 1 line run 2 x buffered
2.3.1.4 N̲I̲C̲S̲ ̲T̲A̲R̲E̲
The IOCBs originate from
- 1 line separated into 2 subdevices run 2 buffered;
input and output is used simultaneously.
2.3.1.5 S̲C̲A̲R̲S̲,̲ ̲C̲C̲I̲S̲,̲ ̲T̲R̲C̲ ̲P̲T̲O̲P̲
The IOCBs originate from
- 1 line run 2 x buffered and using input/output
simultaneously.
2.3.1.6 C̲M̲I̲
The IOCBs originate from
- the WDP ̲VDU (4)
- the WDP ̲RSP (3)
- the format file (1)
The FDCBs originate from
- the WDP ̲VDU (4)
- the WDP ̲RSP (1)
- the format file (1)
2.3.1.7 C̲O̲P̲S̲Y̲
The IOCBs originate from
- 4 files (Garble, Format, MMS ̲STORAGE, OTHER)
- 32 VDUs x 3 (1 format file, 2 input from system
split)
- 1 WDP ̲VDU x 1 (System Configuration)
- 1 WDP x 2
- 1 WDP ̲ROP x 3
The FDCBs originate from
- 6 files
- 1 STI
- 1 TIA
- 20 LTUX
- 32 x (1 + 6) VDU
- 16 MTP ̲ROPS
- 24 TRC/PTOP
- 1 PTP
- 1 OCR
- 1 PTR
- 6 LTU
- 6 * (1 + 2) NICS TARE
- 2 SCARS CCIS
- 1 MAP
- 1 WDP
- 1 WDP ̲VDU
- 1 WDP ̲ROP
- 1 LOGICAL ̲WDP
2.3.2 O̲b̲j̲e̲c̲t̲ ̲d̲e̲s̲c̲r̲i̲p̲t̲o̲r̲ ̲t̲a̲b̲l̲e̲ ̲(̲O̲D̲T̲)̲
The objects in the ODT are
- process object
- segment object
- CPU object
- CPU pool object
- sync. el object
- device object
- resource pool object
The object consumption is summarized in figure 2.3.2-1
and detailed in the following sections.
OBJECT ROOT COPSY COPSY
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲C̲H̲I̲L̲D̲
PROCESS 7 55
0
MEMORY SEGMENTS TBS 168
3
SYNC.ELS TBS 183 12..13
CPUS 3 3
0
CPU POOLS 3 3
0
DEVICES 6 0
0
RESOURCE POOL 0 0
0
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲
TOTAL 412 15..16
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲
Figure 2.3.2-1
ODT sizing.
LEVEL BOUND PAGE SEGMENT
15
PPP 63
15
OBJECT DESCRIPTOR
TABLE
DAMOS
12,13,14
PPS
12 8,9,10,11 XFER DATA 0.016
PART
8
IOS DATA
7 7
STREAM DATA PPS
6
CSF LOCAL DATA 0.424
IOC LOCAL DATA
1K * (no of VDU + ROPS) CAMPS
PPS
6 TMP LOCAL DATA 0.0 PAGE
TMP SHARED DATA 2.0 TMP ̲SHARED
1 1,2,3,4,5 CSF SHARED DATA 28.0 CSF ̲SHARED
0 STP SHARED DATA 8.0
empty
0
DS 0 DS
Figure 2.3-1
CAMPS process data space layout
2.3.2.1 P̲r̲o̲c̲e̲s̲s̲ ̲o̲b̲j̲e̲c̲t̲s̲
ROOT has the children
- FMS ̲MOVING
- FMS ̲FILES
- TMS
- COPSY
- 3 DUMMY PROCESSES
giving 7 child processes
Copsy has
- 55 children
i.e. the copsy object descriptor table contains
- 55 object descriptors.
2.3.2.2 M̲e̲m̲o̲r̲y̲ ̲S̲e̲g̲m̲e̲n̲t̲s̲
2.3.2.2.1 M̲e̲m̲o̲r̲y̲ ̲s̲e̲g̲m̲e̲n̲t̲s̲ ̲f̲o̲r̲ ̲C̲O̲P̲S̲Y̲ ̲c̲h̲i̲l̲d̲r̲e̲n̲
Any COPSY child process contains:
- program segments
- GPS
- COMON
- OWN PS
- data segments
- PPS
- CSF SHARED
- TMP SHARED
- OWN DS
The
- COMON
- CSF ̲SHARED
- TMP ̲SHARED
segments are inherited
I.e every COPSY child process has 3̲
object descriptors to memory segments.
2.3.2.2.2 M̲e̲m̲o̲r̲y̲ ̲s̲e̲g̲m̲e̲n̲t̲s̲ ̲f̲o̲r̲ ̲C̲O̲P̲S̲Y̲
COPSY creates per child process
- child PS
- child DS
- child PPS
i.e 3 x 55 = 165 memory segments obj. descriptors
COPSY inherits from ROOT
- COMON
- TMP ̲SHARED
- CSF ̲SHARED
i.e. 3 memory segments
i.e. COPSY contains 168 memory segments obj. descriptors
2.3.3 S̲y̲n̲c̲r̲o̲n̲i̲z̲a̲t̲i̲o̲n̲ ̲E̲l̲e̲m̲e̲n̲t̲s̲
2.3.3.1 S̲y̲n̲c̲r̲o̲n̲i̲z̲a̲t̲i̲o̲n̲ ̲e̲l̲e̲m̲e̲n̲t̲s̲ ̲f̲o̲r̲ ̲C̲O̲P̲S̲Y̲ ̲c̲h̲i̲l̲d̲r̲e̲n̲
COPSY inherits to any child process:
-TMON ̲SE
-CSF ̲REPORT ̲SE
-CSE ̲SAVE ̲SE
-CSF ̲RTC ̲SE
-TMP ̲SEARCH ̲SE
-TMP ̲UPDATE ̲SE
-STP ̲RESERVATION ̲SE
-SYSE
-MMON ̲RSE
-QMON ̲RSE
-TMP ̲RSE
IOS in a child process, which uses FMS ̲MOVING, FMS
̲FIXED, TMS
- looks up 1 request sync. el per service system
- creates 1 reply sync. el used for all service systems.
2.3.3.2 S̲y̲n̲c̲r̲o̲n̲i̲z̲a̲t̲i̲o̲n̲ ̲e̲l̲e̲m̲e̲n̲t̲s̲ ̲i̲n̲ ̲C̲O̲P̲S̲Y̲
COPSY inherits
-12 sync. els from ROOT (refer previous page + CESE)
COPSY creates per child process
-MMON ̲RSE
-QMON ̲RSE
-TMP ̲RSE
i.e 55 x 3 = 165 sync. els
COPSY creates for all child processes:
-PSE
-DSSE
COPSY communicates to 3.file system giving
-4 sync. els
i.e. COPSY contains 183 sync. els
2.3.4 C̲P̲U̲ ̲o̲b̲j̲e̲c̲t̲s̲
COPSY inherits 3 CPU objects.
No COPSY child inherits a CPU object
2.3.5 C̲P̲U̲ ̲P̲o̲o̲l̲s̲
COPSY inherits 3 CPU pools.
No COPSY child inherits a CPU pool object.
2.3.6 D̲e̲v̲i̲c̲e̲ ̲O̲b̲j̲e̲c̲t̲s̲
Only ROOT contains device object obtained during creation
of device handlers.
2.3.7 R̲e̲s̲o̲u̲r̲c̲e̲ ̲p̲o̲o̲l̲ ̲o̲b̲j̲e̲c̲t̲s̲
No resource pools exists in CAMPS.
The natural pools requires no objects.…86…1 …02…
…02… …02… …02…
3̲ ̲ ̲R̲E̲S̲O̲U̲R̲C̲E̲ ̲S̲P̲E̲C̲I̲F̲I̲C̲A̲T̲I̲O̲N̲ ̲
3.1 K̲E̲R̲N̲E̲L̲ ̲R̲E̲S̲O̲U̲R̲C̲E̲ ̲S̲P̲E̲C̲I̲F̲I̲C̲A̲T̲I̲O̲N̲S̲
3.1.1 N̲o̲ ̲o̲f̲ ̲C̲P̲U̲s̲
CAMPS contains three CPUs
3.1.2 N̲o̲ ̲o̲f̲ ̲C̲P̲U̲ ̲P̲o̲o̲l̲s̲
CAMPS contains one Pool per CPU, giving three CPU pools.
3.1.3 N̲o̲ ̲o̲f̲ ̲P̲r̲o̲c̲e̲s̲s̲e̲s̲
Figure 3.1.3-1 shows the CAMPS process tree.
Root has 7 children.
Copsy has 49-55 children.
Total number of processes: 63.
3.1.3.1 P̲r̲o̲c̲e̲s̲s̲ ̲A̲l̲l̲o̲c̲a̲t̲i̲o̲n̲
A user process contains
- 2 user VDU subprocesses (one subprocess handles
one VDU).
A MSO-MDCO process contains
- 1 MSO subprocess
- 1 MDCO subprocess
A ROP process contains
- 4 ROP subprocesses (a ROP may be a MTP ̲ROP or LTP
̲ROP; one subprocess handles one ROP)
A PTR process contains
- 4 PTR subprocesses (a PTR may be a dedicated PTR
or a LTP ̲PTR; one subprocess handles one PTR).
A TRC ̲PTOP process contains
- 4 TRC ̲PTDP subprocesses (a TRC ̲PTOP subprocess
handles one TRC ̲PTOP line).
A NICS ̲TARE process contains
- 3 NICS ̲TARE subprocesses (a NICS ̲TARE subprocess
handles one NICS ̲TARE line).
A SCARS ̲CCIS process contains
- 1 SCARS
- 1 CCIS
subprocess. One subprocess handles one line.
ROOT
(1)
FMS FMS TMS COPSY DUMMY
MOVING FIXED
(1) (1) (1) (1)
(3)
NON LINE LINE
PROCESSES PROCESSES
(12) (37
-
43)
TMP CMI SUPV USER
(1) (1) (1) (16)
CSP OLD ROP OCR
(1) (1) (4-10)* (1)
LOG STP PTR PTR
(1) (1) (1-7)* (1)
SAR MDP NICS SCARS
̲
(1) (1) TARE CCIS
(2) (1)
UMAN SPIP MSO TRC
̲PTOP
(1) (1) MDCO (0-6)*
(4)
l LTP = 1 ROP
+ 1 PTR
NO ̲OF ̲LTPS
+ NO ̲OF ̲TRC
̲PTOPS = 24
ex1 = 4 ROP, 1 PTR, 6 TRC
̲PTOP
ex2 = 10 ROP, 7 PTR, 0 TRC
̲PTOP
ACS AAS
(1) (1)
FIG. 3.1.3-1…01…CAMPS PROCESS TREE
3.1.4 N̲o̲ ̲o̲f̲ ̲M̲a̲i̲n̲ ̲M̲e̲m̲o̲r̲y̲ ̲P̲a̲g̲e̲s̲
The number of Main Meory pages in CAMPS is estimated
to 640 given 640 k words memory.
3.1.5 N̲o̲ ̲o̲f̲ ̲S̲e̲g̲m̲e̲n̲t̲s̲
Any COPSY childprocess and COPSY contains
- program segments
- GPS (Global Program segment)
- COMON (coroutine Monitor Program shared segment)
- OWN PS (user program segment)
- data segments
- PPS (Process Parameter Segment)
- CSF SHARED (CAMPS CSF system software segment)
- TMP SHARED (CAMPS TMP system software segment)
- OWN DS (User data segment)
ROOT and ROOT children (except COPSY) contains
- program segments
- GPS
- own PS
- data segments
- PPS
- own DS
Total no of segments in ROOT(includes GPS): 4
Total no of segments for FMSS and TMS: 3 x 3
Total no of segments for Idle Process: 1 + 1
+ 3
Total no of segments for COPSY (in-
cludes CSF SHARED, TMP SHARED and COMON): 6
Total no of segments for COPSY children: 55 x
3
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
Total no of segments 189
========================================================
3.1.6 S̲y̲n̲c̲h̲r̲o̲n̲i̲z̲a̲t̲i̲o̲n̲ ̲E̲l̲e̲m̲e̲n̲t̲s̲
CAMPS contains
- 3 DAMOS internal sync. elements
- 60 FMS, TMS related sync. elements
- 177 CAMPS service system sync. elements
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
240 synchronization elements
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
The figures are detailed in the following sections.
3.1.6.1 D̲A̲M̲O̲S̲ ̲I̲n̲t̲e̲r̲n̲a̲l̲
For TMS, FMS- MOVING, FMS ̲FIXED to handler communication
is used:
- 1 sync. element
Central errors are sent to CESE giving
- 1 sync. element
ROOT has a PSE (parent sync. el) giving
- 1 sync. element
Total no of sync elements: 3
3.1.6.2 F̲M̲S̲/̲T̲M̲S̲ ̲r̲e̲l̲a̲t̲e̲d̲ ̲s̲y̲n̲c̲.̲ ̲e̲l̲e̲m̲e̲n̲t̲s̲
Each service system (FMS-MOVING, FMS-FIZED OR TMS requires
one reply sync. element giving
- 56 (No of COPSY and COPSY child processes) sync.
element.
Asynchroneous reports to any service system is sent
to one sync. element DSSE giving
- 1 sync. element.
Total no of sync. element: 60
3.1.6.3 C̲A̲M̲P̲S̲ ̲s̲e̲r̲v̲i̲c̲e̲ ̲s̲y̲s̲t̲e̲m̲ ̲s̲y̲n̲c̲.̲ ̲e̲l̲e̲m̲e̲n̲t̲s̲
The CAMPS sewrvice systems
- COPSY
- CSF
- TMP
- STP
requires the following request sync. elements
- TMON ̲SE
- CSF ̲REPORT ̲SE
- CSF ̲SAVE ̲SE
- CSF ̲RTC ̲SE
- TMP ̲SEARCH ̲SE
- TMP ̲UPDATE ̲SE
- STP ̲RESERVATION ̲SE
- SYSE
giving
- 8 request sync. elements
A process which uses the CAMPS service systems requires
the following reply synchronization elements:
- MMON ̲RSE
- QMON ̲RSE
- TMP ̲RSE
giving
- 56 (COPSY and No. of COPSY children) x 3 = 168
reply sync. elements.
COPSY creates a PSE (parent sync element) for child
process reporting giving:
- 1 sync. element
Total No. of sync. elements: 177
3.1.7 I̲N̲F̲O̲ ̲E̲l̲e̲m̲e̲n̲t̲s̲
INFO elements are used during process communication
and originals from
- IO requests
- Errorreporting
- Handler to FMS/TMS communication.
The number of simultaneous CAMPS I/O request is maximum:
654. An IO request requires 1.3 INFO elements giving
850 INFO elements. 100 INFO elements are to be used
for errorreporting.
To each I/O request is used
- a reply info element which is used during the complete
I/O operation (This gives 1 info element)
- a request info element to FMS, which is only used
for a short period (FMS sends the request to a
handler).
(This consumption is estimated to 0.3 info element).
The handler to TMS communication requires 4 INFO elements
per subdevice.
This gives
- 318 x 4 INFO elements = 1272 INFO elements
Total 2222 INFO elements
3.1.8 N̲O̲ ̲o̲f̲ ̲s̲i̲m̲u̲l̲t̲a̲n̲e̲o̲u̲s̲ ̲I̲/̲O̲ ̲r̲e̲q̲u̲e̲s̲t̲s̲
CAMPS I/O requests relates to
- IOS calls
- MMON calls
The IOS calls are specified in section 2.3.1. figure
2.3.1-2 and gives 530.
The MMON ID calls are specified overleaf and gives
124.
I.e. the number of simultaneous I/O requests amounts
to 654.
M̲M̲O̲N̲ ̲I̲O̲ ̲R̲E̲Q̲U̲E̲S̲T̲S̲
Processes using MMON requires IO-requests as specified
below
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
PROCESS SUSP TOTAL
TYPE REQUESTS FOR ALL
PROCESSES
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
VDU 1 32
MTP ̲ROP 1 16
OCR 1 1
LTP-ROP 1 0
NICS-TARE 2 12
PTR 1 1
PTP 1 1
LTP-PTR 1 0
SCARS CCIS 2 4
TRC PTOP 2 48
ANALYSIS 1
SPIP 1
CONVERSION 1
MDP 1 1
SAR 1
STP 1
LOG 1
COPSY 1
UMAM 1
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
124
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
3.1.9 N̲o̲.̲ ̲o̲f̲ ̲c̲a̲t̲a̲l̲o̲g̲e̲d̲ ̲o̲b̲j̲e̲c̲t̲s̲
The following DAMOS sync. elements are cataloged
- FMS ̲MOVING
- FMS ̲FIED
- TMS
The following CAMPS sync. element are cataloged
- 55 QMON ̲RSE
- 1 STP ̲RESERVATION ̲SE
giving 59 catalogued objects in DF (directory functions)
3.2 T̲M̲S̲ ̲R̲E̲S̲O̲U̲R̲C̲E̲ ̲S̲P̲E̲C̲I̲F̲I̲C̲A̲T̲I̲O̲N̲
3.2.1 N̲o̲ ̲o̲f̲ ̲U̲s̲e̲r̲s̲
The number of users is the number of processes which
uses TMS.
- COPSY 1
- CMI 1
- All Line Processes 43
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
giving 45 users
3.2.2 N̲o̲ ̲o̲f̲ ̲D̲e̲v̲i̲c̲e̲s̲
The number of Devices in CAMPS are as follows:
- 1 STI
- 6 LTUs
- 1 MAP giving a total of
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
8 Devices
3.2.3 N̲o̲ ̲o̲f̲ ̲S̲u̲b̲d̲e̲v̲i̲c̲e̲s̲
The number of subdevices in CAMPS is as follows:
- 1 TIA
- 20 LTUXs
- 32 (1 + 6) VDUS*
- 16 MTP ̲ROPs
- 24 LTP/TRC ̲PTOPs
- 1 PTR
- 1 OCR
- 1 PTP
- 6* (1+2) NICS-TARE **
- 1 SCARS
- 1 CCIS
- 1 WDP
- 1 x (1+6) WDP-VDU*
- 1 VDP-ROP
- 1 Logical WDP
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
318 Total
* Each VDU has a subdevice for the VDU itself and 2
subdevices per split (3 splits exist; one subdevice
is used for Data communication and one for function
key administration.
** Each NICS-TARE line has a subdevice for the line
itself and one for the accept of "Message received.).
3.2.4 N̲o̲ ̲o̲f̲ ̲C̲o̲n̲n̲e̲c̲t̲i̲o̲n̲s̲
For VDUs the number of connections is as follows:
(6 COPSY connections + 4 child connections (offered))x
33 VDUS
- 330 VDU connections
For MTP ROPs the number of connections are as follows:
(1 COPSY connection + 1 child connection (offered))
*
16 MTP ̲ROPs
- 32 MTP POP connections
For LTP/TRC-PTOP, PTP, OCR, PTR, SCARS,CCIS and VDP
ROP the number of connections is as follows:
(1 COPSY connection + 1 child connection (offered))
*
(24 + 1 + 1 + 1 + 1 + 1) = 58 connections.
For NICS-TARE the number of connections is as follows:
(2 COPSY connections + 2 child connections (offered))
*
6 NICS-TARE lines = 24 connections.
For the logical WDP one connection exist:
Total number of connections: 4̲4̲5̲ ̲
3.2.5 N̲o̲ ̲o̲f̲ ̲O̲p̲e̲r̲a̲t̲i̲o̲n̲s̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲
PROCESS TMS TOTAL
TYPE OPERATIONS
NO OF PROCS
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲
VDU 9 x 16 144
MTP ̲ROP 9 x 4 36
LTP ̲ROP 9 x 0
NICS-TARE 25 x 2 50
LTP ̲PTR 9 x 0
PTR 9 x 1 9
PTR 9 x 1 9
OCR 2 x 1 2
SCARS CCIS 9 x 1 9
TRC ̲PTOP 17 x 6 102
CMI 8 x 1 8
COPSY 103 x 1 103
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
TOTAL 472
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
FIG.3.2.5-1…01…SPECIFICATION OF TMS IO-OPERATIONS
