top - download
⟦570525135⟧ Wang Wps File
Length: 4362 (0x110a)
Types: Wang Wps File
Notes: Spelunked
Names: »~ORPHAN69.08«
Derivation
└─⟦bf0247e75⟧ Bits:30006089 8" Wang WCS floppy, CR 0141A
└─ ⟦this⟧ »~ORPHAN69.08«
WangText
C…08…C…0a…C…0d…C…0e…/
/ .…08….…0c….…0e……1f……0a……1f……0f……1f……05……1e……0a……1e……0f……1e… …1d……09……1d……0c……1d……01……1d……07……1c……0c……1c……01……1c… …1c……05……1b……09……1b……0c……1b……0d……1b……01……1b……02……1b…
…1b……05……1a……0a……1a……0e……1a… …19……08……19……0c……19……0d……19……0e……19…
…18……08……18……0c……18……00……18……86…1
…02…
…02…
…02…
…02…CPS/SDS/029
…02…820514…02……02…
SYSTEM
STATUS
AND
CONTROL
DETAILED
DESIGN
SPECIFICATION…02……02…CAMPS
4.2.9 C̲F̲H̲ ̲S̲u̲b̲p̲a̲c̲k̲a̲g̲e̲
4.2.9.1 C̲F̲H̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲S̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
The functions derived for the CFH subpackage are defined
in figure 4.2.9.1-1.
The CFH functions relate to the two iput sources:
- execution of online operator commands
- handling of FMS, TMS and WDP errorreports and the
functions derived from functional responsibilities:
- own errorhandling
- security handling
- start-up, which includes execution of te operator
start-up command.…86…1 …02… …02… …02… …02…
Fig. 4.2.9.1-1…01…CFH FUNCTIONS…86…1 …02… …02… …02… …02…
4.2.9.1.1 …02…C̲O̲P̲S̲Y̲ ̲s̲t̲a̲r̲t̲-̲u̲p̲ ̲f̲u̲n̲c̲t̲i̲o̲n̲s̲
The COPSY start-up responsibilities relate to the actions
taken subsequent to a DAMOS bootload sequence and until
online operation (refer to fg. 4.2.9.1.1-1 overleaf).
The
- initialize COPSY
- execute start cmd
- initialize mirrored disk
- operator only actions
- supervisor only actions
are described in section 2.2.2.1 and are not further
detailed.…86…1 …02… …02… …02… …02…
4.2.9.1.3 (l/3)…86…1 …02… …02… …02… …02…
Fig. 4.2.9.1.1 (2/3)…86…1 …02… …02… …02… …02…
Fig. 4.2.9.1.1 (3/3)…86…1 …02… …02… …02… …02…
The following sections expand the
- create, load and start processes
- create peripherals
functions.
The description is divided into
- general start-up principles
- hadling of objects and subjects
- start of processes…86…1 …02… …02… …02… …02…
4.2.9.1.2 G̲e̲n̲e̲r̲a̲l̲ ̲S̲t̲a̲r̲t̲-̲u̲p̲ ̲p̲r̲i̲n̲c̲i̲p̲l̲e̲s̲
A CAMPS software configuration is defined by
- configuration parameters per t̲y̲p̲e̲ of peripheral
device connected to the CAMPS system e.g.
VDU, ROP, TRC-PTOP etc.
- a set of load files per t̲y̲p̲e̲ of process
- a set of constants defining the maximum CAMPS site
(corresponding to the maximum wired capacity) named
"Maximum Configuration". The constants are preceded
by MAX-; e.g. MAX ̲VDU. The constants defines the
maximum number of lines within a peripheral type.
- a set of constants defining a specific CAMPS site
named "Site Configuration".
The constants are preceded by NO ̲OF; e.g.
NO ̲OF ̲VDUS.
The configuration parameter per type are contained
in a file CONFIG, which defines data for
- process
- subprocess
- mirrored disks
- CAMPS queues
creation.
The file is loaded into COPSY data space in a specific
segment named CONFIG during the start-up phase.
Give the above configuration data COPSY creates:
- processes
- subprocesses
- queues
- COPSY coroutines
Processes, subprocesses and COPSY Coroutines are created
according to the site configuration.…86…1 …02… …02…
…02… …02…
CAMPS queues are created according to the maximum configuration.
Hereby the logical terminal, device, channel numbers
can be used in queue referencing in group capabilities.
Sit dependant disk tables are created according to
the maximum configuration.
For terminal device and channel tables the supervisor
ensures that only entries corresponding to the site
configuration are used.
Thereby logical terminal device and chanel numbers
can be used in table referencing.
The disk table creation is not a SSC responsibility.
4.2.9.1.2.1 O̲t̲h̲e̲r̲ ̲c̲o̲n̲s̲t̲r̲a̲i̲n̲t̲s̲
a) M̲e̲m̲o̲r̲y̲ ̲S̲i̲z̲e̲
All process data and program space are memory resident.
b) P̲r̲o̲c̲e̲s̲s̲ ̲s̲e̲g̲m̲e̲n̲t̲s̲
A process onl contains one user level application
- program segment
- data segment
As data segments have to be mapped into TMP data space
during TMP data transfers a limit is set on the data
segment size. This again limits the number of subprocesses
in aprocess.
The COMON segment is actually also a user level program
segment.
