top - download
⟦567803af4⟧ Wang Wps File
Length: 9311 (0x245f)
Types: Wang Wps File
Notes: Spelunked
Names: »~ORPHAN76.00«
Derivation
└─⟦7f5d2b450⟧ Bits:30006107 8" Wang WCS floppy, CR 0170A
└─ ⟦this⟧ »~ORPHAN76.00«
WangText
…1f……00……00……00……00…L…02……00……00…L
L L…07…K…08…K…09…K…0f…K…05…8…0c…8…0d…8…01…8…02…8
8 8…07…7…08…7…0b…7…0c…7…0e…7…0f…-…00…-…01…-…07…,…08…,…0c…,…0d…,…00…,…01…+…08…+…09…+…0e…+…05…*…0b…*…01…*…07…)…0b…)…00…)…05…(…08…(…0b…(…0f…(…02…(…05…(…07…'…0a…'…0d…'
'…07…&…09…&…86…1 …02… …02… …02…
…02…CPS/SDS/039
…02…820505…02……02…
USER VDU
DETAILED DESIGN SPECIFICATION…02……02…CAMPS
Fig. 4.1.1.4-2
4.1.2 S̲o̲f̲t̲w̲a̲r̲e̲ ̲S̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
In this section the software structure of VUP will
be described. The allocation of functions onto processes
and coroutines will be explained, based o the analysis
performed in section 4.1.1.
Figure 4.1.2-1 shows the mapping of functions onto
processes and coroutines
4.1.2.1. V̲U̲S̲ ̲P̲r̲o̲c̲e̲s̲s̲
The VDU USER PROCESS controls the interaction with
the user VDU, under supervision of TEMCO (SSC softwre).
It thus has the following responsibilities:
- TEMCO command execution
- Control and execution of user transactions
- User transaction accounting
- Maintaining the VDU Header queue status
- Monitoring of FLASH queues.
Fig. 4.1.2-1
Fig. 4.1.2.1-1 VUS Structure
4.1.2.1.1 V̲U̲S̲ ̲C̲o̲r̲o̲u̲t̲i̲n̲e̲s̲
The VDU USER PROCESS consists of four coroutines:
- the VDU Control Coroutine
- the User Function Control Coroutine
- the VDU Dialogue Coroutine
- he Retrieve Coroutine.
In figure 4.1.2.1-1 an overview of VUS is depicted.
4.1.2.1.1.1 V̲D̲U̲ ̲C̲o̲n̲t̲r̲o̲l̲ ̲C̲o̲r̲o̲u̲t̲i̲n̲e̲
The VDU Control (VCO) Coroutine is the controlling
coroutine, controlling the start / stop of the processing
of all the other corouines.
VCO is responsible for the execution of commands received
from TEMCO, e.g initialize, close down, restart, start/stop,
for VDU Header queue status update and that no message
is kept longer in a Flash precedence queue than allowed
by the suprvisor.
During the analysis it was found that TEMCO Control
Functions and Queue Status Maintenance functions were
to be executed with higher priority than User Transaction
Control Functions. Thus these two functions have been
allocated their own oroutine named V̲DU C̲O̲NTROL COROUTINE
(VCO).
The VCO coroutine shall be asssigned the highest priority
among the coroutines of VUS, meaning that whenever
VCO and other VUS coroutines are ready to run, VCO
shall be allowed to run first.
4.1.2.1..2 U̲s̲e̲r̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲ ̲C̲o̲n̲t̲r̲o̲l̲ ̲C̲o̲r̲o̲u̲t̲i̲n̲e̲
The User Function Control (UFCO) Coroutine performs
the direct control of the VDU Dialogue Coroutine.…86…1
…02… …02… …02… …02…
UFCO performs the user transaction control, which consists
of:
- user transaction execution
- user requested transaction interruption
- user transaction accounting.
The fnctions of UFCO and VDIA have been assigned separate
coroutines to decrease the complexity of the software.
When a user transaction is in progress, UFCO software
shall only take care of transaction interruption while
all formatting and I/O transferinitiation / awaiting
is performed by VDIA. UFCO is assigned a higher priority
than VDIA.
4.1.2.1.1.3 V̲D̲U̲ ̲D̲i̲a̲l̲o̲g̲u̲e̲ ̲C̲o̲r̲o̲u̲t̲i̲n̲e̲
The VDU dialogue (VDIA) coroutine is responsible for
the VDU format transformation of input and output and
for validaton of user input.
4.1.2.1.1.4 R̲e̲t̲r̲i̲e̲v̲e̲ ̲C̲o̲r̲o̲u̲t̲i̲n̲e̲
The Retrieve (RETR) Coroutine is responsible for reception
and treatment of retrieval answers from SAR.
The functions of RETR have been assigned to a separate
coroutine, due to the fact that he function may be
performed even when the other coroutines have been
stopped after user sign-off. Furthermore, the function
of the RETR may be considered as low priority tasks,
having in mind that during on-line retrieval all the
other coroutines ssociated with user transaction processing
(UFCO, VDIA) will await input from RETR, thereby allowing
RETR to be processing. RETR is assigned the lowest
priority within VUS.
4.1.2.2 U̲M̲A̲M̲ ̲P̲r̲o̲c̲e̲s̲s̲
The UMAM process controls the access to the preparation
database and maintains the Outgoing Message Status,
the Release Status, the Delivery Status and the Srvice
Message Status for each VDU and printer.
In figure 4.1.2.1-2 an overview of the UMAM process
is shown.
The functions of UMAM have been allocated their own
process for the following reasons:
a) To keep security access control as simple ad tight
as possible.
b) To minimize the damage caused by system malfunction.
With reference to the analysis in 4.1.1.4.1 this
means that the solution where the releaser process
queues a request for removing or changing items
is not chosen. Note tat due to security, it is
our aim that a user process should not be trusted,
meaning that access rights possessed by an unassigned
user process (no user has signed on) shall be kept
at a minimum.
c) The close relationship between Preparation Dataase
Access Control and Message / Comment Status Maintenance
has caused both functions to be allocated to the
same process.
d) The allocation of one process to Status Maintenance
gives the designer the freedom to optimize disk-accesses
and to utilze the fact that identical entries in
different status types exist.
e) The centralization of status maintenance and PDB
access control for all VDU processes in one process,
increases the flexibility of the system.
4.1.2.3 S̲o̲f̲t̲w̲a̲r̲e̲ ̲S̲t̲r̲u̲c̲t̲u̲r̲e̲
n the preceding subsections of section 4.1.2, the processes
and coroutines of VUP have been isolated, and the functions
to be performed by these software components identified.
F̲I̲G̲U̲R̲E̲ ̲4̲.̲1̲.̲2̲.̲1̲-̲…86…1 …02… …02… …02… …02…
The software structure for each component (i.e. coroutine)
will be outlined in the following subsections. The
description of the software structure will mainly be
in the form of sftware structure charts.
In figure 4.1.2.3-1 an overview of the VUP processes
is shown.
4.1.2.3.1 V̲U̲S̲ ̲I̲N̲I̲T̲I̲A̲L̲I̲Z̲A̲T̲I̲O̲N̲ ̲S̲o̲f̲t̲w̲a̲r̲e̲ ̲S̲t̲r̲u̲c̲t̲u̲r̲e̲
This subpackage contains the software which initializes
the coroutines and semaphores of the VUS, MSOS and
DOS subprocesses.
The software structure is shown in figure 4.1.2.3-2.
4.1.2.3.2 V̲C̲O̲ ̲C̲o̲r̲o̲u̲t̲i̲n̲e̲ ̲S̲o̲f̲t̲w̲a̲r̲e̲ ̲S̲t̲r̲u̲c̲t̲u̲r̲e̲
This coroutine receives commands from TEMCO and starts/stops
UFCO accordingly.
Furthermore the periodic updating of the VDU-hader
is performed by VCO.
The software structure of the VDU Control Coroutine
(VCO) is outlined in the structure chart in fig. 4.1.2.3-3.
Fig. 4.1.2.3-1 Software Structure Process Overview.
Fig. 4.1.2.3-2 VUS INITIALIZATION - SOFTWARE STRUCTURE…86…1 …02… …02… …02… …02…
Fig. 4.1.2.3-3 VCO COROUTINE - SOFTWARE STRUCTURE
4.1.2.3.3 U̲F̲C̲O̲ ̲C̲o̲r̲o̲u̲t̲i̲n̲e̲ ̲S̲o̲f̲t̲w̲a̲r̲e̲ ̲S̲t̲r̲u̲c̲t̲u̲r̲e̲
This coroutine controls input / output to and from
the VDU and the communication with other packages.
It accepts commands from VCO ad control VDIA via commands
and process completion reports from VDIA corresponding
to the commands.
It communicates with VCO by sending completion report
corresponding to commands received by VCO.
The control of the MMI is exercised via functio key
interrupts received from the VDU, via execution of
commands entered from the VDU and via input / output
commands sent to VDIA.
Fig. 4.1.2.3-4 shows the software structure.
Fig. 4.1.2.3-4 UFCO COROUTINE - SOFTWARE STRUCTURE…86…1 …02… …02… …02… …02…
4.1.2.3.4 V̲D̲I̲A̲ ̲C̲o̲r̲o̲u̲t̲i̲n̲e̲ ̲S̲o̲f̲t̲w̲a̲r̲e̲ ̲S̲t̲r̲u̲c̲t̲u̲r̲e̲
This coroutine performs input / output to and from
the format area of the VDU and validation and storage
of input.
It accepts commads from UFCO and sends completion report
corresponding to these commands.
It communicates with the VDU via the Format Handler
of the IOC Package and accesses data in the I̲nternal
M̲essage F̲ormat (IMF) via the Message Monitor of the
CSF Package.
ig. 4.1.2.3-5 shows the software structure.
F̲I̲G̲U̲R̲E̲ ̲4̲.̲1̲.̲2̲.̲3̲-̲5̲ ̲V̲D̲I̲A̲ ̲C̲O̲R̲O̲U̲T̲I̲N̲E̲ ̲-̲ ̲S̲O̲F̲T̲W̲A̲R̲E̲ ̲S̲T̲R̲U̲C̲T̲U̲R̲E̲
4.1.2.3.5 RE̲T̲R̲ ̲C̲o̲r̲o̲u̲t̲i̲n̲e̲ ̲S̲o̲f̲t̲w̲a̲r̲e̲ ̲S̲t̲r̲u̲c̲t̲u̲r̲e̲
This coroutine receives input from SAR via the Retrieve
Queue and communicates with UFCO.
This communication is done either by RETR ending Online
Retrieval Results direct to UFCO or Off-line Retrieval
Results indirectly via the Response Queue.
Fig. 4.1.2.3-6 shows the software structure.
Fig. 4.1.2.3-6 RETR COROUTINE - SOFTWARE STRUCTURE
4.1.2.3.6 U̲M̲A̲M̲ ̲S̲o̲f̲t̲w̲a̲r̲e̲ ̲S̲t̲r̲u̲c̲t̲u̲r̲e̲
This processs receives input from other packages in
the Collect and Command Queues.
Figure 4.1.2.3-7 shows the software structure.
