top - download
⟦b404fba2b⟧ Wang Wps File
Length: 6985 (0x1b49)
Types: Wang Wps File
Notes: Minutes of Meeting No. 4
Names: »0487A «
Derivation
└─⟦6f17b967f⟧ Bits:30006000 8" Wang WCS floppy, CR 0035A
└─ ⟦this⟧ »0487A «
WangText
…02…
…02… /810129…02……02…#
MINUTES OF MEETING NO. 4
…02…FE/810109…02…CAMPS
4
…02……02……02……02……02……02…81-01-09…02…rev.1…02…CR A/S
…02… Agreements during the week 81-01-05 - 81-01-09
between SHAPE and CHRISTIAN ROVSING A/S
SHAPE:
Major Santiago Vargas Gert
Jensen
Major Don. Rob Flemming
Enevoldsen K.
N.
Nielsen
Major Joe Gorecki M.
Str]m-Nielsen
M. Agusman H.
Kierkegaard
D.A. Gardiner T.D.
Jensen
Finn
Hass
Svend
Olsen
1 L̲O̲G̲I̲C̲A̲L̲L̲Y̲ ̲A̲S̲S̲O̲C̲I̲A̲T̲E̲D̲ ̲P̲R̲I̲N̲T̲E̲R̲S̲
It was agreed to replace the SRS Requirements
for the terminal position equipped with
one VDU and one printer with the following
requirements:.
1.1 Printers can be shared between VDUs.
1.2 Messages, comments etc. are always distributed
to the VDU.
1.3 If the user activates the PRINT-function,
the message is queue to the logically
associated printer.
1.4 There will always be a associated printer
1.5 A classification check is performed immediately
prior to printing.
1.6 If the classification check fails, the
message is queued for the MDCO.
1.7 If the printer is "signed-off" the message
is queued for the printer anyway.
1.8 If the printer is "signed-off" while
the queues are active, the messages stay
in the queue.
1.9 For 1.7 and 1.8 the FLASH and IMMEDIATE
messages are queued for the MDCO
Note: The supervisor can display terminal
queue status upon request.
1.10 The
old
terminal
position
with
one
VDU
and
one
printer
is
replaced
by
one
case
of
the
new
concept,
so
that
VDU
and
printer
can
operate
in
parallel.
2 R̲E̲C̲E̲I̲V̲E̲ ̲Q̲U̲E̲U̲E̲ ̲M̲A̲N̲I̲P̲U̲L̲A̲T̲I̲O̲N̲
When a VDU is in receive mode, the user
has capability of extracting a message
from the queue, look at the message and
remove it or make it stay in the queue.
The user also has the capability of selecting
a queue of specific precedence.
This capability will not be used during
acceptance test of busy hour performance,
but only during functional test.
3 N̲U̲M̲B̲E̲R̲ ̲O̲F̲ ̲C̲H̲A̲N̲G̲E̲D̲ ̲C̲H̲A̲R̲A̲C̲T̲E̲R̲S̲
The statistics showing the number of
changed characters are removed.
4 T̲R̲A̲F̲F̲I̲C̲ ̲R̲E̲P̲O̲R̲T̲ ̲P̲E̲R̲ ̲C̲H̲A̲N̲N̲E̲L̲
The report showing traffic of incoming
and outgoing messages per channel is
removed. The statics are kept.
5 S̲T̲A̲T̲U̲S̲ ̲I̲N̲F̲O̲R̲M̲A̲T̲I̲O̲N̲
The status information will be:
SUPERVISOR USER
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
Message Status Periodic
every On
Request
(N1/N2) 24
hours
Message Release Periodic
every On
Request
(Q1/Q2) 24
hours
Transaction Status Periodic
every N/A
(R1/R2) 24
hours
Incoming Status Log N/A On
Request
The Incoming status
log will show:
TYPES TRANSAC- TS ITEM
REF- FROM DTG
TION TYPE ERENCE
ID
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲
Incoming I TOC YES PLA/REF YES
Messages
Received C TOC YES SCD N/A
Comments
Messages for A TOC YES SCD N/A
Coordination
Outgoing L TOC YES SCD YES
Messages for
Local Dis-
tribution
The status information on request
will not be used during acceptance
test of busy hour performance,
but only during functional test.
6. A̲b̲b̲r̲e̲v̲i̲a̲t̲e̲d̲ ̲C̲o̲m̲m̲a̲n̲d̲
The requirements for abbreviated
command are removed.
7. C̲o̲m̲m̲a̲n̲d̲ ̲U̲t̲i̲l̲i̲z̲a̲t̲i̲o̲n̲ ̲R̲e̲c̲o̲r̲d̲
The Command utilization record
are removed.
8. E̲x̲t̲r̲a̲c̲t̲i̲n̲g̲ ̲Q̲u̲e̲u̲e̲s̲ ̲b̲y̲ ̲R̲e̲c̲o̲r̲d̲
̲T̲y̲p̲e̲
Incoming messages shall not
be delivered before all other
messages of the same precedence
level.
9. F̲i̲r̲s̲t̲ ̲D̲r̲a̲f̲t̲ ̲o̲f̲ ̲M̲e̲s̲s̲a̲g̲e̲
The first draft of a message
is not kept after the message
is released. After release,
only the released version shall
be retained.
10. D̲a̲t̲a̲ ̲m̲e̲s̲s̲a̲g̲e̲s̲
Data messages are not paged
by CAMPS. Maximum size is 12,000
characters. (Ref. SRS 3.2.1.1.2
c).
11. E̲n̲c̲r̲y̲p̲t̲i̲o̲n̲
After preparing a message for
encryption, it is converted
to ACP 127, i.e. segmented before
being punched. The punched
tape is manually put in for
encryption. The encrypted output
tape is afterwards read into
CAMPS.
12. D̲i̲f̲f̲e̲r̲e̲n̲t̲ ̲P̲r̲e̲c̲e̲d̲e̲n̲c̲e̲ ̲L̲e̲v̲e̲l̲ ̲f̲o̲r̲
̲A̲c̲t̲i̲o̲n̲ ̲a̲n̲d̲ ̲I̲n̲f̲o̲r̲m̲a̲t̲i̲o̲n̲
C̲h̲a̲n̲g̲e̲ ̲t̲o̲ ̲3̲.̲2̲.̲1̲.̲5̲.̲1̲,̲ ̲3̲)̲ ̲o̲f̲ ̲S̲R̲S̲
When precedence specified for
a̲c̲t̲i̲o̲n̲ addressee(s) is of type
FLASH or IMMEDIATE and the precedence
for i̲n̲f̲o̲
addressee(s) is lower, a separate
transmission shall be made for
the INFO addressee(s) in the
case where the INFO PLA's give
rise to selection of a separate
channel to a separate destination,
i.e. either TARE, TRC/Low Speed
TTY.
13. Q̲u̲e̲u̲i̲n̲g̲ ̲a̲t̲ ̲Q̲u̲i̲e̲t̲ ̲H̲o̲u̲r̲s̲
When a terminal is locked or
no user has signed on, messages
and comments are still queued
for the terminal. However,
FLASH and IMMEDIATE messages
and comments are sent to the
MDCO for routing assignment.
The supervisor can also specify
that FLASH and IMMEDIATE messages
and comments are automatically
distributed to one or more manned
terminal position during quiet
hours. For
IMMEDIATE messages a copy is
queued for the original receiver.
Messages for coordination are
not queued, but the originator
is notified, that the message
was not delivered.
14. M̲o̲r̲e̲ ̲t̲h̲a̲n̲ ̲o̲n̲e̲ ̲F̲L̲A̲S̲H̲ ̲i̲n̲ ̲a̲ ̲Q̲u̲e̲u̲e̲
When the terminal position is
attended and the user has signed
on, FLASH messages and comments
will be delivered to the terminal
and placed in the queue. If
a FLASH message or comment cannot
be delivered within 30 seconds,
it is sent to the MDCO for redistribution.
However, if the user is already
displaying a FLASH message or
comment the following messages
and comments stay in the queues
and no pre-emption takes place
but the user will be notified
of the arrival of an additional
FLASH.
15. T̲e̲r̲m̲i̲n̲a̲l̲ ̲P̲o̲s̲i̲t̲i̲o̲n̲ ̲w̲i̲t̲h̲ ̲R̲O̲P̲ ̲O̲n̲l̲y̲
Terminal positions for some
SCD consist of a ROP only.
For these positions the following
applies.
Messages and comments are queued
for the terminal position without
classification check, because
it is unlikely the classification
check will fail.
A classification check is performed
immediately prior to printing.
If the classification check
fails, the message or the comment
is sent to the MDCO.
If the printer is signed-off,
the message or the comment is
queued for the printer anyway,
except for FLASH and IMMEDIATE,
which is sent to the MDCO.
16. R̲e̲t̲r̲i̲e̲v̲a̲l̲
The following diagram summarizes
the retrieval keys.
In addition security checks
have been added.
The following description changes
the previous agreement (Progress
Minutes of Meeting no. 4 dated
20th November 1980) only to
the extend specified herein.
