top - download
⟦5eb622c4c⟧ Wang Wps File
Length: 8663 (0x21d7)
Types: Wang Wps File
Notes: Spelunked
Names: »~ORPHAN75.00«
Derivation
└─⟦2c0571bd0⟧ Bits:30005816 8" Wang WCS floppy, CR 0005A
└─ ⟦this⟧ »~ORPHAN75.00«
WangText
4.6.2 C̲r̲e̲a̲t̲e̲
a) The
program
Create
shall
be
supported,
refer
to
doc.
no
CSS/932/USM/00036.
The
set
of
input
parameter
to
create
as
stated
in
the
above
referenced
document
shall
b
extended
to
include:
1) Date
and
time.
By
default
this
parameter
shall
be
set
by
Create
to
the
current
System
date
and
time.
2) Security
classification.
A
default
value
may
be
defined.
A
security
check
shall
be
performed
(user
classificationcontra
classification
of
file)
before
the
creation
is
actually
executed.
4.6.3 E̲n̲t̲e̲r̲
The
program
Enter,
refer
to
doc.
no.
CSS/932/USM/0036,
shall
be
supported.
4.6.4 L̲i̲s̲t̲
a) The
program
List,
refer
to
doc.
no
CSS/932/USM/0036
shall
be
suported.
Besides
NAME,
TYPE,
SIZE,
ALLOC,
AREA
as
stated
in
the
above
referenced
document
the
listing
shall
include:
1) Date
and
Time
for
the
creation
of
the
file
2) Security
classification
4.6.5 P̲r̲o̲t̲e̲c̲t̲
The
program
Protect,
refer
to
doc.
o
CSS/932/USM/0036,
shall
be
supported.
4.6.6 R̲e̲m̲o̲v̲e̲
a) The program Remove, refer to CSS/932/USM/0032,
shall be supported.
b) If the invokation of the program Remove causes
disk storage to be deallocated, all the dealocated
storage shall be purged, pattern to be overwritten
with see section 8.
4.6.7 R̲e̲n̲a̲m̲e̲
The program Rename, refer to CSS/932/USM/0036 shall
be supported.
4.6.8 D̲c̲o̲p̲y̲
The program Dcopy, refer to doc. no. CSS/111/USM/0050
shall be suppoted.
4.7 D̲I̲A̲G̲N̲O̲S̲T̲I̲C̲S̲ ̲P̲R̲O̲G̲R̲A̲M̲
a) DAMOS shall support
1) on-line self test diagnostics software programs
2) off-line diagnostics software testprograms
b) which detects
1) firmware, and
2) hardware errors
c) The test program may bebased on built-in selftest
program in the CR80D modules.
Error conditions in the peripheral equipment shall
be evaluated by the central computer system.
4.7.1 O̲n̲-̲l̲i̲n̲e̲ ̲D̲i̲a̲g̲n̲o̲s̲t̲i̲c̲s̲ ̲p̲r̲o̲g̲r̲a̲m̲
Generally the on-line diagnostics selftest programs
shall limit the effect of an error.
Specifically the DAMOS shall meet requirements derivedfrom
- integrity of operation
- availability requirements
4.7.1.1 I̲n̲t̲e̲g̲r̲i̲t̲y̲ ̲o̲f̲ ̲o̲p̲e̲r̲a̲t̲i̲o̲n̲
The probability that a message or internal transaction
is
- lost wholy or in part, or
- misdirected, or
- corrupted
as a result of an equipment eror, shall be less than
1 in 10…0e…7…0f….
E̲x̲a̲m̲p̲l̲e̲
A CPU contains an error which is seldom stimulated
and which results in a corrupt message. This error
will not be detected by software checks and it is the
responsibility of a CPU software selftest prgram to
detect the error.
4.7.1.2 A̲v̲a̲i̲l̲a̲b̲i̲l̲i̲t̲y̲
Detailed CAMPS availability requirements are described
in CPS/210/SYS/0001: CAMPS system requirements, section
3.4.4. DAMOS derived requirements are:
- error reports shall isolate an equipemnt eror to
a replaceable module, thereby minimizing the MTTR
- print/display of driver and the like statistics
shall be possible to support preventive maintenance
thereby maximizing the MTBF.
4.7.1.3 O̲n̲-̲l̲i̲n̲e̲ ̲t̲e̲s̲t̲ ̲p̲r̲o̲g̲r̲a̲m̲s̲
The test programs shall be designed to operate as low
priority tasks in timeshared multiprogramming mode
together with the application software. Errrs shall
be reported to an error fix up process. The testprograms
shall cover the hardware modules defined in section
4.7.2.1.
Specific test program to verify system integrity shall
be available.
4.7.1.4 S̲y̲n̲t̲a̲x̲ ̲I̲n̲t̲e̲g̲r̲i̲t̲y̲ ̲T̲e̲s̲t̲ ̲P̲r̲o̲g̲r̲a̲m̲s̲
A systm integrity test program, which
- on request and
- periodically
performs a checksumming of system software shall be
available.
4.7.2 O̲f̲f̲-̲l̲i̲n̲e̲ ̲D̲i̲a̲g̲n̲o̲s̲t̲i̲c̲s̲ ̲P̲r̲o̲g̲r̲a̲m̲s̲
The off-line diagnostics programs shall fulfil requirements
derived from th CAMPS availability requirements defined
in CPS/210/SYS/0001 section 3.4.4.
To fulfil these requirements:
- diagnostics programs shall isolate an equipment
error to a replaceable module, to meet the MTTR
requirements
- preventive maintenance rograms shall be designed
to maximize MTBF
Diagnostics programs shall be executed in the standby
branch in off-line mode without interuption in the
normal message handling function in the active branch.
4.7.2.1 O̲f̲f̲-̲l̲i̲n̲e̲ ̲t̲e̲s̲t̲p̲r̲o̲g̲r̲a̲m̲s̲
The off-line software package shall at least contain
programs for test of the following hardware modules:
- CPU/CACHE
- Memory MAP
- RAM
- PROM - CIA
- TDX I/F
- TDX BUS
- LTUX
- I/O BUS
- LTU
- Disk controller
- Disk line
- Disk pack
- card reader
- paper tape punch
- line printer
- terminal equipement
- floppy disk
- watchdog (SCC)
- power supply
4.8 M̲I̲S̲C̲E̲L̲L̲A̲N̲E̲O̲U̲S̲ ̲P̲R̲O̲G̲A̲M̲S̲
4.8.1 F̲o̲r̲m̲a̲t̲t̲i̲n̲g̲ ̲o̲f̲ ̲D̲i̲s̲k̲
A tool for initializing a virgin disk shall be supported
(disk and floppy)
4.8.2 F̲i̲l̲e̲ ̲C̲o̲n̲v̲e̲r̲s̲i̲o̲n̲
A tool for copying a file from disk to floppy disk
and viseverse shall be supported.
4.8.3 S̲y̲s̲t̲e̲m̲ ̲T̲i̲m̲e̲ ̲S̲e̲t̲t̲i̲n̲g̲
A tool for setting/resetting the system time and date
shall be supported.
4.8.4 T̲i̲m̲e̲
A program which as output delivers the current system
and timeshall be supported.
4.8.5 T̲e̲s̲t̲ ̲D̲r̲i̲v̲e̲ ̲P̲r̲o̲g̲r̲a̲m̲
In order to be able to support test drive programs
DAMOS shall allow read and write of process-relative
data areas, as well as read (and write) of sync-element
data areas and other common data areasby a separate
test drive process created by the application programmer.
Furthermore, it could be considered to make debugger
commands available as calls from a test drive program
in order to automatize tests. They should in this case
be expanded y an
"Await Process in Next Breakpoint"
5̲ ̲ ̲P̲E̲R̲F̲O̲R̲M̲A̲N̲C̲E̲
5.1 S̲I̲Z̲I̲N̲G̲
SIZE WORDS
I̲T̲E̲M̲ P̲R̲O̲G̲R̲A̲M̲ D̲A̲T̲A̲
DAMOS KERNEL 4 k
I/O system 4 k
FMS 5 k
CAMPS message handing
extension to I/O, FMS 1,5k
Process control and system 6 k
data for 60 processes
200 sync elements 2 k
Control area for 40 waiting
processe, and 400 non-delivered 3,5k
info each 5 word
Memory management, Clock, 3 k
idle processe, Root
Handlers and drivers (see 3.3) 10 k
FMS User Control Blocks, CAPs
File control blocks for
50 users, each 2 files and 3 messages 9 k*
totally 20 files and 120 messages
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
Totally excluding FMS data buffers
for trasfer 48 k**
*) As the data is located in the disk interface some
duplication of control blocks is possibly required.
**) The CAMPS offer of February 1980 estimates thi
value to 37k including Pascal, but excluding process
control, so this must be a maximum.
5.2 T̲I̲M̲I̲N̲G̲
Process scheduling and delay management:
In an environment with 60 application processes + DAMOS
with FMS, THS and drivers, handlers, hereof 20 applications
awaitingtime-out running on 3 CPU-CACHE with a 10ms
timeslice the scheduling, process shift caused by scheduling,
real time management and timeout control shall as an
1 second average never exceed 5% of the CPU processing
power available in a 3 CPU environent.
I/O + FMS + DISK handler:
Assuming a configuration with 1 CPU CACHE with 1 application
accessing one CDC disk via the IOS and FMS. All possible
combination of commands issued to the FMS from the
application yielding 25 physical sectoracesss per second
shall execute with a CPU consumption never exceeding
20% in peak second. This comsumption includes process
shifts provoked by the I/O but excludes normal scheduling.
The IOS + FMS + DISK handlers shall have a throughput
in a one CPU nvironment of at least 80 I/Os per second
with a response time not to exceed 40 ms + wait time
for disk + disk access time.
The IOS + FMS + disk handlers shall have a throughput
in a multi-CPU environment (3) of not less than 150
I/Os pr second wth responsetimes as above, assuming
30% CPU load from application.
I/O +THS + TDX driver:
Assuming a configuration with 1 CPU CACHE will one
application accessing a device connected via the TDX.
All possible combinations of I/Os on data and conrol
channels summing up to 100 I/Os per second shall execute
with a CPU consumption never exceeding 20% of the available
as average in a peak second. This consumption includes
process shifts provoked by the I/O but excludes normal
process schedulin
