top - download
⟦a56178533⟧ Wang Wps File
Length: 44609 (0xae41)
Types: Wang Wps File
Notes: Spelunked
Names: »~ORPHAN48.00«
Derivation
└─⟦4c162cf87⟧ Bits:30006103 8" Wang WCS floppy, CR 0163A
└─ ⟦this⟧ »~ORPHAN48.00«
WangText
/…08…/…0d…/…02…/…07….…0d….
-…08…-…0d…-…00…-…01…-…05…-…06…-…07…,…08…,…0d…,…0e…,…00…,…01…,…05…,…06…+…0c…+…0d…+
+…06…+…07…*…0d…*
)…08…)…0d…)…86…1
…02…
…02… …02…
…02…CPS/SDS/035
…02…850601…02……02…
SUPERVISOR
VDU
DETAILED
DESIGN
SPECIFICATION…02…ISSUE
1…02…CAMPS
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̲
a) The Supervisor VDU Package Specification for the
CAMPS project/4040 is written to fulfil the following
objectives:
1) To provide a detaled definition of the Supervisor
VDU Package function and Software architecture.
2) To provide user operational and development
personnel with details of the ongoing analysis.
3) To define in detail the interfaces with other
packages and to dscribe their facilities.
b) The Supervisor VDU Package Specification defines
the functions and software architecture of the
package to a level sufficient for a programmer
to start coding with a minimum of design effort.
The Supervisor VDU Packge constitutes one of the
building blocks of the TEP package.
All Supervisor VDU Package internal data and interfaces
are defined within this document in detail. For
a detailed data description of data external to
the Supervisor VDU package and nterfaces to other
packages refer the Database Design document and
the relevant interface documents.
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̲
a) CAMPS System Requirement Specification
CPS/210/SYS/0001
b) Supervisor Commands and Procedures CPS/230/ICD/0002
c) CAMPS System Design Specification
CPS/SDS/001
d) Database Design Document
CPS/DBD/001
e) CAMPS Software Interface Control Document
CPS/ICD/009
1.2.2 R̲e̲f̲e̲r̲e̲n̲c̲e̲ ̲D̲o̲c̲u̲m̲e̲n̲t̲s̲
DOCUMENT NAME DOCUMENT NUMBER
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
f) CAMPS System Functions CPS/SDS/024
g) Message Management CPS/SDS/025
h) System Status and Control CPS/SDS/029
i) Table Managmnt CPS/SDS/026
j) Input/Output Control CPS/SDS/028
k) Storage and Retrieval CPS/SDS/030
l) Statistics CPS/SDS/031
m) Logging CPS/SDS/032
n) Traffic Handling CPS/SDS/033
o) Message Distribution CPS/SDS/034
p) Supervisor Printer CPS/SDS/036
q) MDCO VDU CPS/SDS/037
r) MSO VDU CPS/SDS/038
s) User VDU CPS/SDS/039
t) OCR CPS/SDS/040
u) Printer CPS/SDS/041…86…1
…02…
…02…
…02…
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̲
Supervisor A supervisor command
Control Command: for which a PEC
may be defined
and to which Confirmation
Code and command
completion eports
applies. (ref.
a) section 3.2.4.1.1,
ref. b) appendix
c).
Supervisor A supervisor command
Procedure Command: which implies message
manipulation, System
Information Print
or table print.
(ref. b) appendix
c).
Supervisor Trans- Common tem for
Supervisor
action Command: Control Commands
and Supervisor
Procedure Commands
(ref. b. appendix
c), i.e. a Supervisor
Command to which
a transaction identification
is associated and
which are logged.
CAMPS function: The CAMPS function
incudes:
- The CAMPS
Supervisor
Function
- The CAMPS
Message
Distribution
Control Function
- The CAMPS
Message Service
Control Function
- The CAMPS User
Function, i.e
Preparation,
Reception nd
Release.…86…1
…02…
…02…
…02…
Preparation - Common term
Database (PDB) for the messages
under preparation
for which access
is controlled
by UMAM (ref.s)
1.3.2 A̲b̲b̲r̲e̲v̲i̲a̲t̲i̲o̲n̲s̲
SFCO Supervisor Function Control Coroutine
SRETR Supervisor Retrieval Coroutine
SUP Supervisor VDU Package
SVCO Supervisor VDU Control Coroutine
SVDIA Supervisor VDU Dialogue Coroutine
SUP Supervisor VDU Process
SPRI Supervisor Print Process
VUS VDU User Subprocess
UMAM User Message Access Monitoring Process
COCO Confirmation Code
PEC Permissive Entry Code
CCMD Supervisor Control Command
TCMD Supervisor Transaction Commad
PCMD Supervisor Procedure Command
IOC I/O Control Software
CSF CAMPS System Functions
SSC System Status and Control
THP Traffic Handling Package
MDP Message Distribution Package
TMP Table Management Package
SAR Storage and Retrieva
STP Statistics Package
LOG Log and Accountability Package
TEP Terminal Package
UMAM User Message Access Monitoring Process
VUS VDU User Subprocess…86…1 …02… …02… …02… …02…
PRIP Printer Package
PRIS Printer Subprocess
TEMCO T̲erminal M̲onitoring and C̲ontrol
SCREP S̲upervisor C̲ompletion R̲e̲p̲ort Control
CREPQ C̲ompletion R̲e̲p̲orting Q̲ueue
PDB P̲reparatio D̲atab̲ase
C̲o̲m̲m̲a̲n̲d̲ ̲a̲b̲b̲r̲e̲v̲i̲a̲t̲i̲o̲n̲s̲: (refer CPS/230/ICD/0002)
SUPV Supervisor Control
MDCO Message Distribution Control
MSOC Message Service Control
USER User
SYSC System Control
MSGH Message Handling
SENF Supervisor Engineering
DEVC DeviceControl
ADSC Addressing Scheme Control
UPUP User Profile Update
QUEC Queue Control
REPC Report Control
SUPC Supervisor Print Control
DISC Disc Control
CMDC Command Control
SECC Security Control
GNSC Global No Series Control
SYPC System Paameter Control
SYIE System Information Extract
TAPR Table Print
TEPC Terminal Position Control
POSC PT/OCR/SATP Control
CHAC Channel Control
SICT SIC Table Update
SDLT SDL Table Update
(Normal/Crisis)
SCDT SCD Table Update
AIGT AIG Tabe Update
GPLT Global PLA Table Update
RITA RI Table Update
CIRT Circuit Table Update
SCCT Display Table Update
OPST Operating Signal Table Update
LPLT Local PLA-Table Update
REOR Reorganize All Tables
ABRO Abandon Reorganization
BLCQ BlockQueue For This Circuit
UBCQ Unblock Queue For This Circuit
BLTQ Block Queue For This Terminal
UBTQ Unblock Queue For This Terminal
BLDQ Block Queue For This device
LORI Local RI-Table Update
LPLP Local PLA-Table Print
LORP Local RI-Table Print
REDE Retrieval for Deltion
UPPT User Profile Print
TPPT Terminal Profile Print
DPPT Device Profile Print
CPPT Channel Profile Print
CMPT Command Print
SPAP System Parameter Print
STOC Storage Occupancy Request
SICP SIC Table print
SDLP SDL Table Print
SCDP SD Table Print
AIGP AIG Table Print
GPLP Global PLA Table Print
RITP RI Table Print
CIRP Circuit Table Print
TSTP Table Status Print
SCCP Display Table Print-Out
SMPR Service Message Preparation
RELU Retrieval For Local Use
READ Retrieval Fr Readdressal
RERN Retrieval For Rerun
REDS Retrieval For Redistribution
RESP Response Message
PRPF Prepare New Plaindress Message
PRAP Prepare New Abbreviated Plaindress Message
PRAS Prepare New Abbreviated Service Message
CPFP Continue Plandress Preparation
CAPP Continue Abbreviated Plaindress Preparation
CASP Continue Abbreviated Service Message Preparation
DESM Delete Service Message
OSMS Outgoing Service Message Status
MDAS Message Distribution Assistance
OMAS Outgoing Messge Service Assistance
IMAS Incoming Message Service Assistance
SION Sign-On
SIOF Sign-Off
ASSG Supervisor Assign Command
UBDQ Unblock Queue For This Device
CACQ Circuit Queue Cancellation
CATQ Terminal Queue Cancellation
CADQ Device Queue Cancellation
CASQ System Queue Cancellation
At Restar
CAAC Cancel All Circuit Queues At Restart
CAAT Cancel All Terminal Queues At Restart
CAAD Cancel All Device-Queues At Restart
OFLD Off-Load Until "Time"
ABOL Abandon Off-Load
COPY Copy System Parameter File
OROF Off-Line Retrieval Off
ORONOff-Line Retrieval On
ORSU Off-Line Retrieval Suspend
VOLI List Volumes Currently In Use
REMO Refuse Mount Of Volume
VOMO Mount Volume
VSMO Mount Volume For System Use
VODM Dismount Volume
VONM Name Volume
VODL Delete Volume
NOSC System NoSeries Control
NOCC Channel No Series Control
NOTR Transaction No Series Reset
PPPC Print Punch Parameter Control
CHPC Channel Parameter Control
ACPC ACP127 Parameter Control
MDPC Message Distribution Parameter Control
SDPC Special Distribuion Parameter Control
CION Set Crisis Indicator On
CIOF Set Crisis Indicator Off
SQHT Set Quiet Hour Terminal
SQHO Set Quiet Hours Off
FLQT Set Flash Queue Time Out
LGTR Log Trace
PWLT Password List
QSPT Queue State Print…86…1 …02… …02… …02… …02…
2̲ ̲ ̲S̲U̲M̲M̲A̲R̲Y̲ ̲O̲F̲ ̲R̲E̲Q̲U̲I̲R̲E̲M̲E̲N̲T̲S̲
2.1 P̲A̲C̲K̲A̲G̲E̲ ̲S̲P̲E̲C̲I̲F̲I̲C̲A̲T̲I̲O̲N̲
a) The S̲upervisor VDU P̲ackage (SUP) constitutes the
only means by which CAMPS supervisors may gain
access to the servicesof the CAMPS Supervisor function.
b) SUP implements all the services of the CAMPS Supervisor
Function except supervisor printer functions (ref.
p), which implies the following responsibilities:
1) Interface the supervisor to the CAMPS system,
.e. Man/Machine I/F support and monitoring.
2) Control logic for Supervisor C̲ontrol C̲om̲mand̲s
(CCMD).
3) Direct all supervisor requests/commands to
the relevant Package within CAMPS.
c) The CAMPS Supervisor Function consists of functions
whih may be grouped into two main categories:
- System C̲ontrol Functions (SYSC)
- S̲upervisor E̲ngineering F̲unctions (SENF)
refer fig. 2.1-1
d) The System Control Functions are the functions
for:
Device Control
Addressing Scheme Control
User Profile Update
Queue Control
Report Control
Supervisor Print Control
Disk Control
Command Control…86…1 …02… …02… …02… …02…
Security Control
Global No. Series Control
System Parameter Control
System Information Extract
Table Print
as defined in CPS/230/ICD/0002.
These functions allow the spervisor to control the
operational and functional aspects of the system.
e) The Supervisor Engineering Functions are the functions
for:
- Initiation of System Integrity Check
- Initiation of Message Flow Trace Analysis
- Setting of dik threshold warning constants
- RESTART Control.
Fig. 2.1-1 CAMPS Supervisor Functions…86…1 …02… …02… …02… …02…
f) The packages to which SUP interfaces are:
1) I/O Control Software
2) File Management System
3) Message Management
4) CAMPS System Functions
5) System Status and Contol Software
6) Traffic Handling
7) Table Management
8) Storage and Retrieval
9) Log and Accountability
10) Statistics
11) Terminal Package
In figure 2.1-2 an overview of the SUP interfaces
is depicted.
g) The SUP interface to the Trminal Package (TEP)
consists of the interfaces between the Supervisor
VDU Process (SVUP) of SUP and the following other
TEP processes:
1) S̲upervisor P̲rint Process (SPRI) (ref p)
2) P̲rinter S̲ubprocess (PRIS) (ref u)
3) U̲ser M̲essage A̲ccess M̲oitoring Process (UMAM)
(ref s)…86…1 …02… …02… …02… …02…
Fig. 2.1-2 SUP INTERFACE OVERVIEW…86…1 …02… …02… …02… …02…
The information flow between SVUP and the rest of the
CAMPS System packages/processes is depicted in fig.
2.1-3 through 2.1-5.…86…1 …02… …02… …02… …02…
Fig. 2.1-3…86…1 …02… …02… …02… …02…
Information Flow - System Control Functions
Legend (fig. 2.1-3):
1. Profile Changes
Block/Unblock Terminal
Connect/Disconnect Channel/Device
Mount/Dismount Volume
Atoml Printer Identification
2. Profile Update
Table Update
Reorganize/Abandon Reorganization
Copy System Parameter File
Command Control
Security Control
Global No Series Control
System Parameter Control
3. Queue Block/Unblock
QueueCancel
4. Storage Occupancy
5. Logtrace
Send Log Record
6. WRITE/READ Volume Name
7. Off Load Data/Abandon offload
Offline retrieval on/off/suspend
Get Volume List
Mounted/Dismounted Volume
Mount Refused
Offline Volume Deleted
Initialize Volume
8. Open/Close for Incoming Traffic
9. Delete All items under preparation at specified
terminal.
Number of items under preparation at specified
terminal.
10. Activate: Password List, Profile Print, Command
Print, Table Prit, System Parameter Print, Supervisor
Print Control, Queue State Print.…86…1 …02… …02…
…02… …02…
Fig. 2.1-4…86…1 …02… …02… …02… …02…
Information Flow - Supervisor Engineering Functions
Legend (fig. 2.1-4)
1. Perform Message Flow Trace Analysis
2. Send Log Record
3. Command Completion Report
4. Set dis threshold warning constants.
Set security parameters.…86…1 …02… …02… …02… …02…
Fig. 2.1-5…86…1 …02… …02… …02… …02…
Information Flow - Supervisor Engineering
Functions at Restart
Legend (Fig. 2.1-5):
1. CAMPS Go
2. Queue Cancellations
3. Storage Occupancy
4. Send Log Record
5. Delee all items under preparation at specified
terminal
6. Supervisor Print Control
Completion Report
Queue State Print
2.2 P̲a̲c̲k̲a̲g̲e̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲s̲
a) In this section, the functions to be performed
by SUP are outlined. As stated in section 2.1,
te main task of SUP is to implement the CAMPS Supervisor
Function.
b) As a short introduction to the description of the
SUP main functions and functional responsibilities,
an overview of the capabilities of the CAMPS Supervisor
Function is depicte in fig. 2.2-1 through 2.2-3
and the environment as it may be emphasized by
the supervisor is depicted in fig. 2.2-4.…86…1
…02… …02… …02… …02…
Fig. 2.2-1/6
2.2.1 M̲a̲i̲n̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲s̲ ̲(̲N̲o̲r̲m̲a̲l̲ ̲O̲p̲e̲r̲a̲t̲i̲o̲n̲)̲
The main functions implemented by SUP are:
1. Continuous display of queue status information
2. Continuous display of information concrning the
transaction in progress
3. The means for Menu Guidance
4. The means for display of queued information
5. The means for directing requests/Commands to CAMPS
and deliver responses.
2.2.1.1 Q̲u̲e̲u̲e̲ ̲S̲t̲a̲t̲u̲s̲ ̲D̲i̲s̲p̲l̲a̲y̲
The upper 5 lines o the VDU screen is named VDU Header
Area ref. fig. 2.2-5.
The second line of the VDU Header Area is used for
Queue Status Display and updated regularly (every minute).
The queues in question are:
1. Supervisor Print Queue: this contains the ttal
number of elements queued for Supervisor Print
to PRIP (Printer Package).
2. Report Print Queue: this contains the total number
of elements queued for Report Print (Reports and
Service Message) to PRIP.
3. Log Print Queue: this contains thetotal number
of elements queued for Log Print to PRIP.
4. Statistics Print Queue: this contains the total
number of elements queued for Statistics Print
to PRIP.
Together with update of the Queue Status Display the
date/time field on the first ine is updated.
fig. 2.2-5/6…86…1 …02… …02… …02… …02…
2.2.1.2 I̲n̲f̲o̲r̲m̲a̲t̲i̲o̲n̲ ̲C̲o̲n̲c̲e̲r̲n̲i̲n̲g̲ ̲t̲h̲e̲ ̲T̲r̲a̲n̲s̲a̲c̲t̲i̲o̲n̲ ̲i̲n̲ ̲P̲r̲o̲g̲r̲e̲s̲s̲
The first line of the VDU Header Area is used to identify
the Transaction in progress (i.e. the Supervisor Function
caled upon) and the classification of the information
currently accessed.
Whenever the classification is unknown or no transaction
is in progress the maximum classification to which
the supervisor may gain access through this VDU is
displayed.
2..1.3 M̲e̲n̲u̲ ̲G̲u̲i̲d̲a̲n̲c̲e̲
a) Supervisor Transactions which reflect identical
functional areas are logically grouped, each group
represented by a Menu listing all the related transactions.
Fig. 2.2-6 depicts this grouping and the Menu Tree.
b) Steppingfrom a leaf (Menu) towards the roots (Main
Menu) of the Menu tree may be accomplished by use
of the F/C Key Return to current Menu.
c) Display of the Main Menu is accomplished by use
of the F/C Key SYSTEM ̲BREAK.
d) All other Menus are displayedwhen the Menu-Name
is entered as a Command.
e) Transactions may be called either directly or via
the appropriate menus.
2.2.1.4 R̲e̲q̲u̲e̲s̲t̲s̲/̲C̲o̲m̲m̲a̲n̲d̲s̲ ̲t̲o̲ ̲C̲A̲M̲P̲S̲ ̲S̲y̲s̲t̲e̲m̲
2.2.1.4.1 S̲u̲p̲e̲r̲v̲i̲s̲o̲r̲ ̲C̲o̲n̲t̲r̲o̲l̲ ̲C̲o̲m̲m̲a̲n̲d̲s̲
a) It is the responsibility of SUP to heck if a Supervisor
Control Command is accompanied with a PEC (if required)
and to request input of the confirmation code (COCO)
before issuing the entered command to the system
or executing it.
b) Further SUP is responsible for collecting the system
replies to Supervisor Control Commands and generate
and queue corresponding Command Completion Reports
to the Report printe.
For transaction control of Control Commands refer
fig. 2.2-7.
2.2.1.4.2 S̲u̲p̲e̲r̲v̲i̲s̲o̲r̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲ ̲C̲o̲m̲m̲a̲n̲d̲s̲
It is the responsibility of SUP to direct a procedure
command to the relevant part of the CAMPS System.
For transaction control of proedure commands refer
fig. 2.2-7 (Supervisor Procedure Commands).…86…1
…02… …02… …02… …02…
Fig. 2.2-7…86…1 …02… …02… …02… …02…
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̲
a) SUP performs Initialization, Close Down and Restart
on command from SSC (TEMCO)
b) I̲n̲i̲t̲i̲a̲i̲z̲a̲t̲i̲o̲n̲
Initialization of the SVUP process making the controlling
units (coroutines) ready to run. This includes
initial call of the Coroutine Monitor of the CSF
Software and of the Format Handler of the IOC software.
A Command Completion Codeis returned to SSC (TEMCO)
when initialization tasks have been performed.
c) C̲l̲o̲s̲e̲ ̲D̲o̲w̲n̲
Termination of the current processing in an ordered
manner setting SVUP into a state ready for restart.
d) R̲e̲s̲t̲a̲r̲t̲
Restart consists of two parts SVUP estart and Supervisor
Restart.
d1) S̲V̲U̲P̲ ̲R̲e̲s̲t̲a̲r̲t̲
SVUP Restart shall always be performed after Close
Down, Switchover and Total System Failure and contains
the elements described for Initialization.
d2) S̲u̲p̲e̲r̲v̲i̲s̲o̲r̲ ̲R̲e̲s̲t̲a̲r̲t̲
Supervisor Restartshall cause SVUP to enter the
Restart Mode allowing the supervisor to issue the
SENF Restart commands from the Supervisor VDU.
Exit from Restart Mode shall occur when the Supervisor
enters the CAMPS GO (CAGO) command, which shall
cause SVUP to sen a Restart Mode exit command (CAGO)
to SSC. In fig. 2.2-3, the restart commands are
depicted.
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̲
Not applicable.
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̲
Errors detected by SUP shall be reported to SSC for
decision on what type of acion shall be taken. (e.g.
Ignore, Terminate, Process, etc.).
Where system overload is detected SSC shall inform
SUP. SUP is responsible for closing (logically) all
incoming channels.
2.2.2.4 I̲n̲t̲e̲g̲r̲i̲t̲y̲ ̲o̲f̲ ̲O̲p̲e̲r̲a̲t̲i̲o̲n̲
SUP shall contain credibiliy checks to contain the
effects of corrupt or inaccurate data to the extent
this does not introduce redundant processing which
will decrease the system throughput.
It shall be a design aim that wherever possible the
consequence of a single softwae fault incident will
not affect more than one transaction. The detection
of an inconsistency indicating a fault shall initiate
a report and the re-processing from a validated checkpoint
in an attempt to recover with a minimum of discontinuity.
Onl after further failures should major recovery or
operator intervention action be invoked.
2.2.2.5 D̲a̲t̲a̲ ̲C̲o̲l̲l̲e̲c̲t̲i̲o̲n̲ ̲(̲L̲O̲G̲,̲ ̲S̲T̲A̲T̲I̲S̲T̲I̲C̲S̲,̲ ̲a̲n̲d̲ ̲R̲e̲p̲o̲r̲t̲s̲)̲
1. L̲o̲g̲ ̲C̲o̲l̲l̲e̲c̲t̲i̲o̲n̲
Log information on Supervisor Transactions shall
be collected by SUP and repoted to the Log Package.
Log information shall be reported at the time
of completion of a transaction and have the contents
as specified below.
L̲o̲g̲ ̲r̲e̲c̲o̲r̲d̲ ̲d̲a̲t̲a̲:
Terminal Designator
Transaction Serial Number
Format Identification
Log time
Item Reference ID
Exit Code
Start Time of Transaction
Month and Day
2 S̲t̲a̲t̲i̲s̲t̲i̲c̲s̲
N/A.
3 R̲e̲p̲o̲r̲t̲s̲
The following reports shall be generated and queued
to the Supervisor Print Package:
a) Command Completion Reports
2.2.2.6 S̲e̲c̲u̲r̲i̲t̲y̲
SUP shall maintain a list of all Supervisor commands
together with ther (possibly) associated Permissive
Entry Code (PEC) and (possibly) Restrictive Warning
Text.
This list shall be used during validation of any Supervisor
command issued to the system from the Supervisor VDUs.
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 following requirements extracted from CPS/210/SYS/0001
shall be fulfilled by SUP.
S̲u̲p̲e̲r̲v̲i̲s̲o̲r̲y̲ ̲C̲o̲m̲m̲a̲n̲d̲ ̲R̲e̲s̲p̲o̲n̲s̲e̲ ̲(̲3̲.̲4̲.̲1̲.̲6̲.̲5̲)̲
Response time shall be measured as of 3.4.1.6.3 c.
The response time is time to acceptance of command
parameters (ie. request for new input).
Response time for commands entered via the command
line or via a format display shall be less than 5 seconds
for 99% of all commands.
The above time shall never exceed 10 second.
U̲s̲e̲r̲ ̲T̲e̲r̲m̲i̲n̲a̲l̲ ̲I̲n̲t̲e̲r̲a̲c̲t̲i̲o̲n̲ ̲(̲3̲.̲4̲.̲1̲.̲6̲.̲3̲)̲
c) During interactive transactions at VDUs the response
time shall be measured as the time delay from transmission
of the last character of the input to the system
and the start of display of response/nex format/menu.
- Response times for validation of information
(e.g. message, edited message) shall not exceed
10 seconds per VDU page in 90% of all cases.
2.3.2 T̲h̲r̲o̲u̲g̲h̲p̲u̲t̲
The following characteristics extracted from CPS/210/SYS/0001
apply t SUP:
None
2.3.3 F̲l̲e̲x̲i̲b̲i̲l̲i̲t̲y̲
The design shall ensure that changes to formats and
format tolerances can be implemented with ease to facilitate
improvement of the MMI useability.
2.3.4 A̲c̲c̲u̲r̲a̲c̲y̲
Time shall be accurate within +/- 500 ms.
ll other data be that input or output shall be exact.
3̲ ̲ ̲E̲N̲V̲I̲R̲O̲N̲M̲E̲N̲T̲
3.1 E̲Q̲U̲I̲P̲M̲E̲N̲T̲
The equipment environment of this package is the CR80D
Computer.
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̲
SVUP's system software environment cosists of the following
components:
- DAMOS
- CAMPS System Function
- Message Management System
- Storage and File Management
- I/O Control Software
- SSC Software
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̲
Development software is standard DAMO and TOS (Terminal
Operating System) resident in a single CR8OD configuration.
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̲
Ref. Supervisor Procedures (CPS/230/ICD/0002)
3.3.2 P̲a̲c̲k̲a̲g̲e̲-̲I̲n̲t̲e̲r̲f̲a̲c̲e̲s̲
3.3.2.1 S̲S̲C̲ ̲I̲/̲F̲
Profile Changes
Block/Unblock Terminal
Connect/Disconnect Channel/Device
Atomal Printer identification
Start-user
Stop-user
Initialize
Restart
CAMPS Go
Cose all incoming channels (system overload)
3.3.2.2 T̲M̲P̲ ̲I̲/̲F̲
PROFILE UPDATE
TABLE UPDATE
REORGANIZE/ABANDON REORGANIZATION
COPY SYSTEM PARAMETER FILE
COMMAND CONTROL
SECURITY CONTROL
GLOBAL NO SERIES CONTROL
SYSTEM PARAMETER CONTROL
VALDATION FUNCTIONS
INITIALIZE SYSTEM FILES
3.3.2.3 C̲S̲F̲ ̲I̲/̲F̲
QUEUE CANCEL
QUEUE BLOCK/UNBLOCK
3.3.2.4 M̲M̲S̲ ̲I̲/̲F̲
SET THRESHOLD VALUES
SET SECURITY PARAMETERS
3.3.2.5 L̲O̲G̲ ̲I̲/̲F̲
SEND LOG RECORD
LOGTRACE
CLOSE LOG CIF
3.3.2.6 S̲A̲R̲ ̲I̲/̲F̲
DISK CONTROL
VOLUME LIST
3.3.2.7 T̲H̲P̲ ̲I̲/̲F̲
OPEN/CLOSE INCOMING CHANNEL TRAFFIC
3.3.2.8 S̲T̲P̲ ̲I̲/̲F̲
STORAGE OCCUPANCY
PERFORM MESSAGE FLOW TREE ANALYSIS
33.2.9 S̲P̲R̲I̲ ̲I̲/̲F̲
ACTIVATE: PASSWORDLIST, PROFILE PRINT, COMMAND PRINT,
TABLE PRINT, SYSTEM PARAMETER PRINT, QUEUE STATE PRINT.
SUPERVISOR PRINT CONTROL
3.3.2.10 U̲M̲A̲M̲ ̲I̲/̲F̲
DELIVER NUMBER OF ITEMS UNDER PREPARATION OF SPECIFIED
TERMINAL
3.4 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̲
The following security related functions are performed
by TEMCO (SSC):
Sign-on Procedure
Select SUPV capability
Sign-off procedure
TEMCO is further responsible for implementation of
the Assign (ASSG) comand, identifying which of the
two possible supervisor VDUs is the active.
TEMCO is responsible for connecting SVUP to the active
supervisor VDU.…86…1 …02… …02… …02… …02…
4̲ ̲ ̲P̲A̲C̲K̲A̲G̲E̲ ̲D̲E̲S̲I̲G̲N̲
4.1 P̲A̲C̲K̲A̲G̲E̲ ̲O̲V̲E̲R̲V̲I̲E̲W̲
The functions of the Supervisor VDU Package (SUP) are
implemented in one process, the Supervisor VDU Process
(SVUP).
An overview of SUP is shown in figure 4.1-1. SUP consists
of 6 subpackages of which four are impelemented as
coroutines.
The coroutines are:
a) The Supervisor VDU Control (SVCO) Coroutine interprets
and is responsible for the execution of commands
issued by TECO. SVCO controls all the other coroutines
and maintaines the VDU Header Status Area.
b) The Supervisor Control (SFCO) Coroutine controls
the interface to the user. SFCO containes all the
functions for control of the Man Machine Interface
(MMI), or command execution and command interfaces
to other packages.
c) The VDU Dialoue (VDIA) Coroutine performes input/output
to/from the VDU Format Area on command from SFCO.
VDIA is common to all VDU packages.
d) The Supervisor Completion Report ontrol (SCREP)
coroutine processes the items in the Command Completion
Reporting Queue (CREPQ) by generating Command Completion
Reports, if appropriated and queueing these to
SPRI (ref. p)
The other two sub-packages are:
a) The Supervisor Initilization (SUPI) subpackage
initializes the Supervisor VDU process, i.e. data,
coroutines etc.
b) The Supervisor VDU Procedures (SUPR) subpackage
contains the VDU package dependent syntax, display
and semantic procedures. These procedures are invoed
by VDIA.
Communication with other packages (apart from CSF)
is done via queues. The SVUP has 4 input queues:
Command Queue: Commands from TEMCO and timer
events from Timer Monitor
Answer Queue: Answers to requests from other
packages.
VODL Queue: Mount/dismount results from SSC.
Supervisor Command
Completion Reporting
Queue: Completion reporting of supervisor
commands.
The analysis performed leading to the breakdown
of SVUP into the five subpackages described above
is based on the analysis performed for VUP (ref.
)) and thus not presented within this document.
Figure 4.1-1
Legend fig. 4.1-1
1. Commands from SSC (e.g. start, stop) and timer
events.
2. Timer initiated update of VDU header (queues, time)
3. Control information from SVCO to SFC
4. Commands/parameters and function keys
5. Transaction ID, classification, error messages
6. System update requests
7. Validated/unvalidated system information
8. Volume delete command
9. Answers to requests
10. Command Compleion Reporting of Supervisor Commands
11. Control Information from SFCO to SCREP and commands
12. Command Completion Reporting of commands executed
by SVUP
13. Mount/dismount answer from SSC
The SVUP Coroutines shall be assigned mutual priorties
as specified below:
highest priority SVCO
SFCO
SVDIA
SCREP
lowest priority VODL
4.1.1 F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲S̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
This section contains an analysis of the main functions
to be performed by SUP.
The analysis is carried outto a level where self-contained
sub-functions can be identified.
The first level break-down of the SUP-functions is
shown on figure 4.1.1-1. The following main functions
are identified and broken down in this section.
TEMCO CONTROL FUNCTIONS:
These implement the TEMCO Commands (Init, start, stop,
close-down, etc.).
QUEUE STATUS MAINTENANCE:
These maintain the VDU Header Status Area.
SUPERVISOR TRANSACTION CONTROL:
These are the bulk of the package functions controlling
the MMIand performing the Supervisor transactions.
SUPERVISOR COMPLETION REPORT CONTROL
These functions generate Command Completion Reports
and queue them for print-out to SPRI.
Figure 4.1.1-1
4.1.1.1 T̲E̲M̲C̲O̲ ̲C̲o̲n̲t̲r̲o̲l̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲s̲
Functional breakdown of these functions is shown in
figure 4.1.1.1-1.
INITIALIZATION is performed on command from TEMCO during
start of the CAMP System.
RESTART process is performed on command from TEMCO
during recovery from a system failure (switchover or
total system failure).
CLOSE-DOWN is performed on command from TEMCO during
Ordered System Close Down.
START USER is performed oncommand from TEMCO following
a successful SIGN-ON procedure.
STOP USER is performed on command from TEMCO following
a SIGN-OFF procedure.
ENTER RESTART MODE is performed on command from TEMCO
when the Operator has requested the supervisor proces
to be started in restart mode.
Figure 4.1.1.1-1
4.1.1.2 Q̲u̲e̲u̲e̲ ̲S̲t̲a̲t̲u̲s̲ ̲M̲a̲i̲n̲t̲e̲n̲a̲n̲c̲e̲
Functional breakdown of these functions is shown in
figure 4.1.1.2-1. The functions are all performed on
timer request (every minute).
UPDATE DG FIELD:
The date-time-group is updated to reflect current time.
UPDATE SUPERVISOR PRINT-QUEUE LENGTH FIELD:
This field contains the total number of elements queued
for the P̲r̲i̲nt Process (PRIS) controlling the Supervisor
Printer. It is update to reflect current state of the
Supervisor Print Queue.
UPDATE LOG PRINT - QUEUE LENGTH FIELD:
This field contains the total number of elements queued
for the PRIS controlling the Log Printer. It is updated
to reflect current state of the queu.
UPDATE REPORT PRINT - QUEUE LENGTH FIELD:
This field contains the total number of elements queued
for the PRIs controlling the Report Printer. It is
updated to reflect current state of the queue.
UPDATE STATISTICS PRINT-QUEUE LENGTH FIELD:
This field contains the total number of elements queued
for the PRIS controlling the Statistics Printer. It
is updated to reflect current state of the queue.
DISPLAY QUEUE STATUS INFORMATION:
This function performs the actual display of the VD
Header Queue Status Line.
Figure 4.1.1.2-1
4.1.1.3 T̲r̲a̲n̲s̲a̲c̲t̲i̲o̲n̲ ̲A̲c̲c̲o̲u̲n̲t̲i̲n̲g̲
Functional break-down of these functions is shown in
figure 4.1.1.3-1.
ASSIGN TRANSACTION DESIGNATOR:
This function assigns a Transaction Desigator to the
transaction started.
COLLECT LOG DATA:
This function collects initial and final log information.
FINAL LOG REPORTING:
This function sends log information to the LOG-package
upon completion of the current transaction.
figure 4.1.1.3-1
4.1.1.4 T̲r̲a̲n̲s̲a̲c̲t̲i̲o̲n̲ ̲I̲n̲t̲e̲r̲r̲u̲p̲t̲i̲o̲n̲
Functional breakdown of these functions is shown in
figure 4.1.1.4-1. The functions are performed when
an F/C Key Interrupt occurs.
FETCH FUNCION KEY:
This function analyses the F/C Key Interrupt to identify
the F/C Key.
CHECK RECEIVED F/C KEY ALLOWED:
This function checks that the F/C key is valid in the
current context (at this stage in the transaction).
DISPLAY ERROR MESSAGE:
This function performs display of the appropriate error
message in the case where the F/C key is invalid.
EXECUTE F/C KEY FUNCTIONS:
This function performs the function corresponding to
the F/C Key.
Figure 4.1.1.4-1
4.1.1.5 C̲o̲m̲m̲a̲n̲d̲e̲d̲ ̲T̲a̲s̲k̲
Functional breakdown of these functions is shown in
figure 4.1.1.5-1. The functions are performed when
a command is entered on the Command line of the VDUheader
or via the format latest displayed.
COMMAND CODE VALIDATION is performed to check that
the command is a valid Supervisor Command and acceptable
in the current context.
PERMISSIVE ENTRY CODE VALIDATION is performed if a
PEC is specified fr the command entered.
COMMAND PARAMETER VALIDATION is performed on parameters
entered with the command (if any).
DISPLAY ERROR MESSAGE is performed if CMD, parameter
or PEC is not acceptable.
Figure 4.1.1.5-1
4.1.1.6 C̲o̲m̲m̲a̲n̲d̲ ̲T̲a̲s̲k̲ ̲C̲o̲n̲t̲r̲o̲l̲
Functional breakdown for these functions is shown in
figure 4.1.1.6-1.
COMMAND TASK INITIATION sets up the necessary environment
for specification f a command.
DISPLAY RESTRICTIVE WARNING TEXT display the restrictive
warning text of the command if defined.
COMMAND CONFIRMATION request and validate the entired
Command Confirmation Code (COCO).
OUTPUT REQUESTED NO OF LINES is performed whn an INSERT
LINES CMD is entered.
DELETE REQUESTED NO OF LINES is performed when a DELETE
LINES CMD is entered.
RETURN CURSOR returns the cursor to the position where
it was when the CMD-key was activated (prior to INSERT/DELETE
LINES CMDs).
EFINE VALID F/C KEYS defines the f/c key valid in the
context of the current transaction.
Figure 4.1.1.6-1
4.1.1.7 C̲o̲m̲m̲a̲n̲d̲s̲ ̲t̲o̲ ̲C̲A̲M̲P̲S̲ ̲S̲y̲s̲t̲e̲m̲
Functional breakdown of these functions is shown in
fig. 4.1.1.7-1.
UPDATE TABLE ENTRY is performed, when a change to a
system table is commandd.
UPDATE SYSTEM PARAMETERS are performed when a change
to a system parameter is commanded.
COMPLETION REPORTING is performed when a command task
to be performed by SUP has been completed.
SEND COMMAND TO SUBPACKAGE is performed when a commaned
task shall be performed by another subpackage.
PERFORM COMMANDED TASK is performed when a command
task shall be executed by SUP itself (e.g queue cancellation).…86…1
…02… …02… …02… …02… …02…
Fig. 4.1.1.7-1…86…1 …02… …02… …02… …02… …02…
4.1.1.8 D̲i̲a̲l̲o̲g̲u̲e̲ ̲F̲o̲r̲m̲a̲t̲t̲i̲n̲g̲
Functional breakdown of these functions is shown in
figure 4.1.1.8-1. The functions are all calls on the
Monitor Procedures of the FORMAT HANDLER in te IOC
Package ref j). Via these procedures the actual communication
with the VDU Format Area is performed.
Figure 4.1.1.12-1
4.1.1.9 F̲o̲r̲m̲a̲t̲ ̲D̲a̲t̲a̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲s̲
Functional breakdown of these functions is shown in
figure 4.1.1.13-1.
DISPLAY ERROR CODE FORMAT is performed when errors
are found during validaton.
Display procedures are called when data shall be output
(internal representation to ASCII conversion).
Syntax procedures are called when data is input (ASCII
to internal representation conversion plus simple syntac
check).
Figure 4.1.1.9-1
4.1.1.10 S̲u̲p̲e̲r̲v̲i̲s̲o̲r̲ ̲C̲o̲m̲p̲l̲e̲t̲i̲o̲n̲ ̲R̲e̲p̲o̲r̲t̲ ̲C̲o̲n̲t̲r̲o̲l̲
Functional breakdown of these functions is shown on
figure 4.1.1.10-1.
ANALYZE COMPLETION REPORTING INPUT is performed on
Command ompletion answers from subpackage to decide
whether a Completion Report shall be generated and
in case - which data it shall contain.
FETCH REPORT DATA is performed when data to a Completion
Report is needed.
SEND REPORT is performed when all dta constituting
a Completion Report has been collected.
Fig. 4.1.1.10-1…86…1 …02… …02… …02… …02… …02…
4.1.2 S̲o̲f̲t̲w̲a̲r̲e̲ ̲S̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
This section describes the mapping of the functions
specified in section 4.1.1 onto software components.
Figure 4.1.2-1 shows the mapping of functins into subpackages
(coroutines).
SVUP contains the coroutines:
SVCO S̲upervisor V̲DU C̲o̲ntrol
SFCO S̲upervisor F̲unction C̲o̲ntrol
VDIA V̲DU D̲i̲a̲logue
SCREP S̲upervisor C̲ompletion R̲e̲p̲ort Control
VODL V̲o̲lume D̲el̲etion
The detailed analysis leading t the software structure
of SVUP is very similar to the one described for VUP
(Ref.s) with respect to the coroutines SVCO, SFCO,
and VDIA.
SCREP is assigned the task of generating and queueing
command Completion Reports to the supervisor print
proess (SPRI) ref.p. Further the execution of some
of the supervisor commands have been assigned to SCREP,
namely those commands for which the execution time
may be noticable,refer fig. 4.1.2-2. In the referenced
fig.these are the commands REOR, CACQ hrough CAAD and
COPY. For the sake of concistency execution of the
commands REOR through CAAD and COPY have thus been
assigned to SCREP.
VODL is assigned the task of volume deletion due to
the relatively lon execution time.
The rest of this secion describes the functions allocated
to the sub-packages (coroutines). The functions can
be divided into two types:
1) Functions mapped from functional breakdown
2) Functions related to communication between software
components (coroutines andprocesses).
As the former functions are described in section 4.1.1
only the latter functions will be described in this
section. (The functions mapped from functional breakdown
are presented in highlighted boxes in this section).
Figure 4.1.2-1
Fig. 4.1.2-2…86…1 …02… …02… …02… …02… …02…
Commands for which Completion Reports are required.
Legend
Command : The command code of a command for which
a Command Completion Report is required
R : R̲esponse time, an idication of the time
it takes to execute the command. The following
codes have been used:
I: I̲mmediate
F: F̲ast
S: S̲low
E : Executions, an indication of which Process
is responsible for the execution of the
command. The following cdes have been used:
S : S̲VUP
O : O̲ther, another process than SVUP
SO: Executed by SVUP and/or ano̲ther process.
X : Indicates a special I/F, i.e. not via queues…86…1
…02… …02… …02… …02… …02…
4.1.2.1 S̲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̲
The software structure of the Supervisor VDU control
coroutine (SVCO) is outlined in the structure charts
on fig. 4.1.2.1-1 through 4.1..1-4.…86…1 …02… …02…
…02… …02… …02…
Fig. 4.1.2.1-1/-4…86…1 …02… …02… …02… …02… …02…
4.1.2.2 S̲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 SVCO andcontrols VDIA via
commands and processes completion acknowledges from
VDIA corresponding to the commands.
It communicates with SVCO by sending completion reports
corresponding to commands received from SVCO.
The control of the MMI is exercised ia Function Key
Interrupts received from the VDU, via execution of
commands entered from the VDU and via input/output
commands sent to VDIA.
Figures 4.1.2.2-1 through 4.1.2.2-3 show the software
structure.
Figures 4.1.2.2-1 to 3
4.1.2.3 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 storing of
input.
It accepts commands fom SFCO and sends completion reports
corresponding to these commands.
It communicates with the VDU via the Format Handler
of the IOC Package.
Figure 4.1.2.3-1 shows the software structure.
Figure 4.1.2.3-1
4.1.2.4 V̲O̲D̲L̲ ̲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 is responsible for deletion of the off-line
volume on command from SFCO. It communicates with SSC
through the VODL queue answer to mount/ dismount).
VODL accepts close-down command from SVCO.
Figure 4.1.2.4-1
4.1.2.5 S̲C̲R̲E̲P̲ ̲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̲
The SCREP Coroutine has the CREPQ queue as input source.
SCREP is controlled by SFCO and thus receives commands
from SFCO and returns ommand completion acknowledges
to SFCO.
Fig. 4.1.2.5-1 outlines the Software Structure.
Fig. 4.1.2.5-1…86…1 …02… …02… …02… …02… …02…
4.1.2.6 S̲u̲b̲p̲a̲c̲k̲a̲g̲e̲ ̲I̲d̲e̲n̲t̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
Each of the coroutines in section 4.1.2.1 through 4.1.2.5
are identified as subpackages.
The task of initializing the SVUP process and upstartof
the SVUP coroutines is described in the SVUP initialization
subpackage (SUPI).
The task of defining display procedures, syntax procedures,
and semantic procedures related to supervisor formats
is described in the supervisor VDU procedure subpakage
(SUPR).
The following subpackages are thus described in section
4.2:
- SVCO subpackage
- SFCO Subpackage
- VDIA Subpackage
- VODL Subpackage
- SCREP Subpackage
- SVUP Initialization Subpackage
- SUPR Subpackage
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̲
In this section, the data flow between the SVUP coroutines
will be described together with the control logic used
to synchronize their execution
The data flow internal to SVUP is depicted in fig.
4.1.3-1.
In fig. 4.1.3-2 an overview of the SVUP coroutines
and the primitives (SVCO ̲SEM, SFCO ̲SEM, SVDIA ̲SEM,
SCREP ̲SEM, VODL ̲SEM) used for synchronization is depicted.
SVCO receives its inut from SVCO ̲SEM. SVCO is the coroutine
which controls the activities of all the others through
its control of SFCO. SVCO starts and stops SFCO by
executing a send operation on SFCO ̲SEM with the proper
command. When SFCO has executed a command set by SVCO,
SFCO notifies SVCO by performing a send operation on
SVCO ̲SEM with the relevant Command Completion code.
SFCO receives its input from SFCO ̲SEM. SFCO controls
the activities of SVDIA through SVDIA ̲SEM. The control
logic is analog to t2̲0̲6̲1̲A̲…00…CPS/SDS/035 …00…sdv
…00…MSN …00…fra 1
…00…2̲2̲…00…0̲4̲…00…8̲2̲…00…2̲0̲…00…0̲5̲…00… ̲ ̲ ̲6̲…00…0̲8̲…00… ̲1̲9̲2̲6̲2̲…00…2̲1̲…00…0̲6̲…00…8̲5̲…00…1̲5̲…00…2̲2̲…00… ̲ ̲ ̲ ̲…00…05…00… ̲ ̲ ̲1̲94…00…2̲4̲…00…0̲6̲…00…8̲5̲…00…1̲1̲…00…4̲1̲…00…24…00…06…00…85…00…11…00…43…00…0163A…00…
77…00… ̲ ̲1̲5̲…00…39…00… 588…00… ̲3̲3̲300…00……18……00……01…0…02…#…00……10……00……01……10……05…'…10……11……02……80…*̲J̲…15……05……00……00……00……00……00……00……01…B
`̲…00……86……00……00……00……00…"…0a……00……00…"…0b…"…00…"…05…!…0a…!…0f…!…05… …0b… …00… …05……1f……08……1f……09……1f……0d……1f……0e……1f……0f……1f……00……1f……05……1f……06……1e……08……1e……09……1e……0d……1e……0e……1e… …1e……05……1d……0b……1d……0e……1d……0f……1d……05……1c……0b……1c……00……1c……05……1b……86…1 …02…
…02… …02…
…02…CPS/SDS/035
…02…850601…02……02…
SUPERVISOR VDU
DETAILED DESIGN SPECIFICATION…02…ISSUE 1…02…CAMPS
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̲
a) The Supervisor VDU Package Specification for the
CAMPS project/4040 is written to fulfill the following
objectives:
1) To provide a detiled definition of the Supervisor
VDU Package function and Software architecture.
2) To provide user operational and development
personnel with details of the ongoing analysis.
3) To define in detail the interfaces with other
packages and to escribe their facilities.
b) The Supervisor VDU Package Specification defines
the functions and software architecture of the
package to a level sufficient for a programmer
to start coding with a minimum of design effort.
The Supervisor VDU Pacage constitutes one of the
building blocks of the TEP package.
All Supervisor VDU Package internal data and interfaces
are defined within this document in detail. For
a detailed data description of data external to
the Supervisor VDU package andinterfaces to other
packages refer the Database Design document and
the relevant interface documents.
