top - download
⟦8d4f87e95⟧ Wang Wps File
Length: 17021 (0x427d)
Types: Wang Wps File
Notes: CAMSP SYS DES. SPEC
Names: »0509A «
Derivation
└─⟦7c0ec4e20⟧ Bits:30006001 8" Wang WCS floppy, CR 0036A
└─ ⟦this⟧ »0509A «
WangText
3…09…3…86…1
…02…
…02… …02…
…02…CPS/SDS/001
…02…RG/810115…02……02…
CAMPS
SYSTEM
DESIGN
SPECIFICATION
…02……02…CAMPS
4.1.2 S̲o̲f̲t̲w̲a̲r̲e̲ ̲C̲o̲n̲f̲i̲g̲u̲r̲a̲t̲i̲o̲n̲
(In this section the term software includes firmware).
The CAMPS software is split, in accordance with the
requirements specified in CPS/210/SYS/0001, into three
major subsystems. In turn, these subsystems are subdivided
into "packages". A package is a convenient grouping
of functions that are performed by software (and firmware).
During the detailed design stage, the software modules
that form the packages will be identified. For the
purposes of this SDS, however, the packages are informally
divided, where convenient, into functions.
4.1.2.1 S̲o̲f̲t̲w̲a̲r̲e̲ ̲S̲u̲b̲s̲y̲s̲t̲e̲m̲s̲
There are 3 subsystems:
a) S̲y̲s̲t̲e̲m̲ ̲S̲o̲f̲t̲w̲a̲r̲e̲. This subsystem contains packages
which provide support for, and control of the resources
of the system. The packages contain any software
that is permitted to operate in a "privileged-user"
state.
b) A̲p̲p̲l̲i̲c̲a̲t̲i̲o̲n̲s̲ ̲S̲o̲f̲t̲w̲a̲r̲e̲. This subsystem contains
packages that perform the functional capabilities
defined by the CAMPS requirement. The packages
operate in an environment provided by the system
software subsystem.
c) S̲u̲p̲p̲o̲r̲t̲ ̲S̲o̲f̲t̲w̲a̲r̲e̲. This subsystem consists of all
the software that is not part of the operational
system.
4.1.2.2 S̲o̲f̲t̲w̲a̲r̲e̲ ̲P̲a̲c̲k̲a̲g̲e̲s̲.
The following paragraphs provide brief descriptions
of the packages. Figure 4.1.2-1 lists the subsystems
and packages.
Fig. 4.1.2-1…01…S̲o̲f̲t̲w̲a̲r̲e̲ ̲S̲u̲b̲s̲y̲s̲t̲e̲m̲s̲ ̲&̲ ̲P̲a̲c̲k̲a̲g̲e̲s̲
4.1.2.3 S̲y̲s̲t̲e̲m̲ ̲S̲o̲f̲t̲w̲a̲r̲e̲ ̲S̲u̲b̲s̲y̲s̲t̲e̲m̲
a) Ke̲r̲n̲e̲l̲ ̲(̲K̲E̲R̲)̲.̲ This package contains DAMOS operating
system functions that provide the fundamental creation
and control of processes; allocation of memory
and synchronization elements; allocation and scheduling
of CPUs within a PU; servicing of interrupts;
mapping of memory; administration of virtual
memory; security access and control; handling
of certain types of hardware and software failure
conditions and storage violations; clearing of
data areas to satisfy security requirements.
b) I̲n̲p̲u̲t̲-̲O̲u̲t̲p̲u̲t̲ ̲C̲o̲n̲t̲r̲o̲l̲ ̲(̲I̲O̲C̲)̲. This package extends
the kernel facilities to provide a set of input/output
interfaces particularly suited to the CAMPS requirements.
Amongst the components of the IOC package are
the Standard Software items I/O System (IOS) and
the Terminal Handler System (THS). IOS handles
the I/O commands used by other software packages.
THS contains the device - specific handlers needed
by IOC (and must not be confused with the Terminal
Package, TEP, which provides CAMPS functional control
of user terminals). Except for the discs, all
access to and from devices (which includes TDX,
LTUs, LTUXs, external channels and the Watchdog)
is made via the IOC package. The facilities include:
1) Data Transfers
2) Buffer allocation and de-allocation
3) Device initialisation and close down procedures,
down-line loading of LTUs.
4) Protocol handling for NICS TARE, CCIS, SCARS
5) Asynchronous I/O for low speed telegraph lines
together with transformations between ITA 2
and ITA 5 alphabets.
6) Device and transfer error notification and
device interrupt servicing.
7) Handling of the link to the stand-by or on-line
PU.
c) C̲A̲M̲P̲S̲ ̲S̲y̲s̲t̲e̲m̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲s̲ ̲(̲C̲S̲F̲)̲. This package extends
the kernel facilities to provide a software environment
particularly suited to the CAMPS requirements in
the following general respects:
1) Communication between processes via queue/synchronization
elements.
2) Queue manipulation facilities (process, terminal,
and device queues).
3) Sharing of data areas.
4) Handling of temporary work areas and spool
files (if required).
5) Allocation and manipulation of item (message
and comment) data base areas including use
and movement between short-term, intermediate
and long term storage areas.
6) Administration of timer initiation of processes
and provision of date and time.
7) Auditing support (applications interfaces for
recording statistics, logs, reports).
8) Certain security and access checks.
9) Facilities for recovery precautions (for example,
checkpoints) and for actual recovery.
10) Diagnostic trace facilities.
d) S̲t̲o̲r̲a̲g̲e̲ ̲a̲n̲d̲ ̲F̲i̲l̲e̲ ̲M̲a̲n̲a̲g̲e̲m̲e̲n̲t̲ ̲(̲S̲F̲M̲)̲. This package
provides facilities for accessing and manipulating
all discs (hard and floppy) and data held there
(except for virtual storage). In particular it
performs the following functions:
1) Mount/Dismount, initialisation, purging, mirrored-disc
control.
2) File and file catalogue accessing and manipulation.
3) Simple data accessing.
4) Manipulation and control of item (message and
comment) data, and control of item identity
allocation.
5) Control of storage types (short term, intermediate,
and long term).
6) Administering disc checkpoint data and associated
recovery procedures.
7) Certain security and access controls.
e) S̲y̲s̲t̲e̲m̲ ̲S̲t̲a̲t̲u̲s̲ ̲a̲n̲d̲ ̲C̲o̲n̲t̲r̲o̲l̲ ̲(̲S̲S̲C̲)̲. This package
controls the operation of the whole system and
has the following facilities:
1) Loading and start-up of the system both initially
and upon recovery. This also involves the
allocation of resources such as processes,
devices, CPUs and memory and combines Kernel
facilities to form the CAMPS operating system
(COPSY):
2) Control of on-line, stand-by, and off-line
PUs, and Watchdog. Switching the status of
a PU from "on-line" to "standby" and vice versa.
Switching an "off-line" PU to "standby" and
vice versa. Communication between the on-line
and standby PUs (checkpoint transmission and
reception).
3) Control of processes as the parent of all processes;
security and access control; administering
of changes to security profiles. User sign-on,
sign-off, security interrogations.
4) Initiation and administration of base level
diagnostic routines (in both on-line and standby
processor units).
5) Monitoring status of hardware subsystems and
devices; control of engineer's display and
configuration table. Physical device allocation
and switch-over. Switching from operation
with mirrored discs to a single disc and vice
versa (if required).
6) Handling of various errors reported by packages;
output at watchdog printer.
7) Synchronisation of clocks in PUs; setting
of date and time.
8) Production of off-line copy of system parameter
file (if required).
9) Operation of the on-line PU without the watchdog
(if required).
10) Controlled close-down of the system.
f) T̲a̲b̲l̲e̲ ̲M̲a̲n̲a̲g̲e̲m̲e̲n̲t̲ ̲(̲T̲M̲P̲)̲. This package provides
access to and manipulation of system tables (for
example Routing and distribution information, circuit
and channel data, operator and terminal profiles),
system parameters and global number series. The
package takes care of the differing storage and
access requirements of these types of data, their
inter-relationships, under organisation, record
access, and locking.
4.1.2.4 A̲p̲p̲l̲i̲c̲a̲t̲i̲o̲n̲s̲ ̲S̲o̲f̲t̲w̲a̲r̲e̲ ̲S̲u̲b̲s̲y̲s̲t̲e̲m̲
a) T̲r̲a̲f̲f̲i̲c̲ ̲H̲a̲n̲d̲l̲i̲n̲g̲ ̲(̲T̲H̲P̲)̲. This package controls
the handling of ACP 127 message traffic across
the CAMPS telegraph interfaces and the control
of other traffic between CAMPS and CCIS/SCARS,
OCR. It therefore performs the following functions:
1) Receipt and control of incoming traffic from
NICS TARE and low speed telegraph lines.
2) Transmission and control of outgoing traffic
to NICS TARE and low speed telegraph lines.
3) ACP 127 analysis and control of manual correction
via MSO of incoming ACP 127 messages.
4) ACP 127 synthesis and the control of manual
routing assistance via MSO of outgoing messages.
5) Circuit and channel control and channel continuity
checks (including periodic automatic generation
and awaiting receipt of channel check messages).
6) Automatic FLASH receipt and acknowledgement
checks.
7) Handling of information received from and transmitted
to CCIS, SCARS, OCR.
b) D̲i̲s̲t̲r̲i̲b̲u̲t̲i̲o̲n̲ ̲(̲M̲D̲P̲)̲. This package handles the distribution
to users (via terminals, SCARS, CCIS) of incoming
and outgoing messages, messages for co-ordination,
and comments. The functions of the package are:
1) Creation of distribution list for an incoming
message.
2) Selection of appropriate delivery queued for
incoming and outgoing messages, messages for
co-ordination, and comments.
3) Involvement of MDCO in manual assignment of
the distribution of a message.
4) Involvement of MDCO in the event of non-delivery
of a message because of security classification
mis-match or inappropriate terminal status.
c) T̲e̲r̲m̲i̲n̲a̲l̲ ̲P̲a̲c̲k̲a̲g̲e̲ ̲(̲T̲E̲P̲)̲. This package controls
the man-machine interface of CAMPS (excluding the
engineer's console) and provides common facilities
for all users of the system and for functions that
communicate with users. It is therefore responsible
for the following functions:
1) Input and initial checking of all user commands.
2) User transaction control and control of common
functions (such as cancel, suspend/resume,
delete).
3) Facilities for syntax validation of transaction
data.
4) VDU formatting and editing facilities, page-mode
and roll-up mode facilities.
5) Printer formatting and control, allocation
of various number series.
6) Access to terminals via queues or via direct
responses. Control of queues (queue commands
for interactive VDUs, automatic output at receive
only printers, single user and shared queues,
pre-emption, time-outs).
7) Status reports on terminal activities.
8) Collection of information for statistics directly
related to facilities controlled by this package.
9) Functions on behalf of all user types (supervisor,
MSD, MDCO, common users).
d) S̲t̲o̲r̲a̲g̲e̲ ̲a̲n̲d̲ ̲R̲e̲t̲r̲i̲e̲v̲a̲l̲ ̲(̲S̲A̲R̲)̲. This package handles
the storing in intermediate and long term storage
of messages, comments, and log records, together
with the maintenance and manipulation of associated
indexes. The package makes extensive use of the
SFM package and provides the following facilities:
1) Receipt of new retrieval parameters for insertion
in appropriate indexes.
2) Movement from short term to intermediate storage
of messages and comments.
3) Storage of log records in intermediate storage.
4) Periodic dumping of records from intermediate
to long term storage, and associated maintenance
of indexes.
5) Finding items, via retrieval keys, on on-line
and off-line storage and arranging for the
transfer, if required, to short term storage.
6) Deletion of items (upon request and for security
purposes).
7) Purging of off-line storage indexes.
e) L̲o̲g̲ ̲(̲L̲O̲G̲)̲. The CAMPS requirement specifies the
production of a log of various transactions and
of certain events associated with these transactions
(for example start and completion). Information
to be logged is produced by the various packages
in the system and, via, the CSF package supplied
to the LOG package. This package has the following
functions:
1) Periodic collection of log items, allocation
of log identifier and storing of the items.
2) Handling retrieval requests for log records.
3) Print-out of log records.
4) Production of summary reports.
f) S̲t̲a̲t̲i̲s̲t̲i̲c̲s̲ ̲(̲S̲T̲A̲)̲. This package collects by various
means from other subsystems, information concerning
traffic handling, telegraph channels, distribution,
and the use of formats. From this information,
it periodically produces statistic reports. The
Subsystem thus provides the following facilities:
1) Maintenance and resetting of directly updated
statistic counts.
2) Files for the collection of records from which
statistics are subsequently derived.
3) Maintenance of cumulative totals, as appropriate,
to produce hourly, daily, and weekly statistics.
4) Formatting and periodic output of statistics.
4.1.2.5 S̲u̲p̲p̲o̲r̲t̲ ̲S̲o̲f̲t̲w̲a̲r̲e̲ ̲S̲u̲b̲s̲y̲s̲t̲e̲m̲
The support software consists of the following packages
(TBD):
a) S̲o̲f̲t̲w̲a̲r̲e̲ ̲C̲r̲e̲a̲t̲i̲o̲n̲. This consists of the appropriate
compilers, assemblers, linkers, and editor by which
software can be produced. This subsystem is only
used at the CSSI.
b) S̲o̲f̲t̲w̲a̲r̲e̲ ̲D̲e̲l̲i̲v̲e̲r̲y̲. This consists of library maintenance,
cross-reference, system generation, data conversion
and any other tool needed for the creation of full
or part software systems for development or for
delivery to CAMPS sites. This subsystem is only
used at the CSSI.
c) S̲o̲f̲t̲w̲a̲r̲e̲ ̲R̲e̲c̲e̲p̲t̲i̲o̲n̲. (TBD). This consists of all
the software required at a CAMPS site to load new
or updated software. (If loading is to be performed
on the operational system, this may be part of
the system status and control subsystem, TBD).
d) T̲e̲s̲t̲ ̲B̲e̲d̲.̲ This consists of a debugger to provide
facilities defined in CPS/210/SYS/0001 3.5.11.5.1(d)
and a test and interaction facility to facilitate
testing of a software module. This subsystem is
only used at the CSSI.
e) F̲a̲c̲t̲o̲r̲y̲-̲t̲e̲s̲t̲ ̲S̲i̲m̲u̲l̲a̲t̲o̲r̲. This generates a standard
test environment to drive a CAMPS system.
f) H̲a̲r̲d̲w̲a̲r̲e̲ ̲T̲e̲s̲t̲.̲ This subsystem contains all the
software required to test any of the hardware components.
g) D̲u̲m̲p̲ ̲A̲n̲a̲l̲y̲s̲i̲s̲. This software is used to assist
in the analysis of dumps produced by the operational
system.
h) D̲a̲t̲a̲ ̲T̲a̲k̲e̲-̲o̲n̲. This software provides assistance
in the off-line preparation, verification and loading
to disc of bulk data for the CAMPS tables at each
site (TBD).
4.1.3 M̲a̲p̲p̲i̲n̲g̲ ̲o̲f̲ ̲S̲o̲f̲t̲w̲a̲r̲e̲ ̲o̲n̲t̲o̲ ̲H̲a̲r̲d̲w̲a̲r̲e̲
From the point-of-view of software subsystems, CAMPS
consists of the following major hardware components
(figure 4.1.3-1):
a) On-line PU which performs most of the operational
processing.
b) Standby PU which handles checkpoint information
and runs self-diagnostic programs in readiness
to take over quickly in the event of a failure
of the on-line PU.
c) Off-Line PU. If one of the twin PUs of a CAMPS
installation is neither on-line nor standby, it
will be off-line for repair, for test, or for loading
and checking new software.
d) Watchdog which monitors the on-line and standby
PUs and various other devices and contains the
master time-clock for the system. It permits an
operator at the engineer's console to communicate
with either PU.
e) I/O crate which provides access by the PUs to:
1) Three discs via disc controllers. Two of the
discs will form a "mirrored pair".
2) Line printer and floppy disc via LTUs.
3) CCIS and SCARS via LTUs Special Software/Firmware
will be required.
4) Local and remote NICS TARE via LTUs. Special
Software/Firmware will be required.
Fig. 4.1.3-1…01…H̲a̲r̲d̲w̲a̲r̲e̲ ̲C̲o̲n̲f̲i̲g̲u̲r̲a̲t̲i̲o̲n̲ ̲u̲p̲o̲n̲ ̲w̲h̲i̲c̲h̲ ̲C̲A̲M̲P̲S̲ ̲S̲o̲f̲t̲w̲a̲r̲e̲ ̲i̲s̲ ̲M̲a̲p̲p̲e̲d̲
f) TDX/LTUX crates which provide access via LTUXs
to:
1) Local VDUs.
2) Local medium speed printers.
3) Low speed telegraph lines (TRCs, Teleprinters,
and low speed TAREs).
4) Remote terminals via a statistical multiplexer.
5) Optical character reader (OCR).
Though most of the functions performed by the packages
of the system and applications subsystems are performed
within a processor unit, some involve other hardware
subsystems. Figures 4.1.3-2 to 4.1.3-8 show the
packages associated with the various hardware subsystems.
Fig. 4.1.3-2…01…K̲E̲R̲N̲E̲L̲
Fig. 4.1.3-3…01…C̲A̲M̲P̲S̲ ̲S̲y̲s̲t̲e̲m̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲s̲
Fig. 4.1.3-4…01…I̲O̲-̲C̲o̲n̲t̲r̲o̲l̲
Fig. 4.1.3-5…01…S̲y̲s̲t̲e̲m̲ ̲S̲t̲a̲t̲u̲s̲ ̲a̲n̲d̲ ̲C̲o̲n̲t̲r̲o̲l̲
Fig. 4.1.3-6…01…S̲t̲o̲r̲a̲g̲e̲ ̲&̲ ̲F̲i̲l̲e̲ ̲M̲a̲n̲a̲g̲e̲m̲e̲n̲t̲
Fig. 4.1.3-7…01…T̲e̲r̲m̲i̲n̲a̲l̲ ̲P̲a̲c̲k̲a̲g̲e̲
Fig. 4.1.3-8…01…A̲l̲l̲ ̲O̲t̲h̲e̲r̲ ̲P̲a̲c̲k̲a̲g̲e̲s̲
