top - download
⟦9a63560d0⟧ Wang Wps File
Length: 37473 (0x9261)
Types: Wang Wps File
Notes: CPS/SYS/001 issue II
Names: »0177A «
Derivation
└─⟦cf42e5d4d⟧ Bits:30005818 8" Wang WCS floppy, CR 0016A
└─ ⟦this⟧ »0177A «
WangText
…00……00……00……00……00…9…02……00……00…9
8…0b…8…0f…8 7…0a…7…0e…7
6…08…6…0d…6…86…1 …02… …02… …02…
…02…CPS/210/SYS/0001
…02…800919…02……02…
CAMPS SYSTEM REQUIREMENTS
…02……02…CAMPS
T̲A̲B̲L̲E̲ ̲O̲F̲ ̲C̲O̲N̲T̲E̲N̲T̲S̲
S̲e̲c̲t̲i̲o̲n̲ ̲3̲.̲2̲.̲5̲
…02……02……02…3.2.5 Logging ..............................
…02……02……02……02…3.2.5.1 Categories of Transactions to be
Logged ...........................
…02……02……02……02…3.2.5.2 Logging Events ...................
…02……02……02……02…3.2.5.3 Storage of Log Records............
…02……02……02……02…3.2.5.4 Print of Log Records..............
…02……02……02……02…3.2.5.5 Tracing (Computer Analysis) of
Log Information ..................
…02……02……02……02…3.2.5.6 Definition of Specific Log Records
…02……02……02……02……02…3.2.5.6.1 Log Records Relating to In-
coming messages...............
3.2.5.6.1.1 Log Records Related to
incoming NICS-TARE/TRC/
Point to Point connec-
tion Messages ............
3.5.2.6.1.1.1 Valid Messages .......
3.4.2.6.1.1.2 Invalid Messages .....
3.5.2.6.1.1.3 Automatic Deleted
Messages .............
3.2.5.6.1.2 Log Records Relating to
Incoming ACE CCIS Messa-
ges ......................
3.2.5.6.1.3 Log Records Relating to
Incoming SCARS II Messa-
ges ......................
…02……02……02……02……02…3.2.5.6.2 Log Records Relating to outgo-
ing Messages .................
3.2.5.6.2.1 NICS-TARE/TRC/Point to
Point connection
Messages .................
3.2.5.6.2.2 Log Records Relating to
Outgoing ACE CCIS Messages
3.2.5.6.2.3 Log Records Relating to
outgoing SCARS II Messages
…02……02……02……02……02…3.2.5.6.3 Channel Discontinuity.........
3.2.5.6.3.1 NICS-TARE/TRC/Point to
Point connection Channel
Discontinuity.............
3.2.5.6.3.2 Log Records Relating to
ACE CCIS Channels
Discontinuity ............
3.2.5.6.3.3 Log Records Relating to
SCARS II Channel Discon-
tinuity ..................
…02……02……02……02……02…3.2.5.6.4 Terminal Procedures...........
…02……02……02……02……02…3.2.5.6.5 Message Distribution Control..
…02……02……02……02……02…3.2.5.6.6 Message Service...............
…02……02……02……02……02…3.2.5.6.7 Supervisory Commands..........
3.2.5…02…L̲o̲g̲g̲i̲n̲g̲
The system shall maintain a log for all transactions,
including those terminated before completion.
3.2.5.1…02…C̲a̲t̲e̲g̲o̲r̲i̲e̲s̲ ̲o̲f̲ ̲t̲r̲a̲n̲s̲a̲c̲t̲i̲o̲n̲s̲ ̲t̲o̲ ̲b̲e̲ ̲l̲o̲g̲g̲e̲d̲.̲
A log shall be maintained with respect to:
a) external transactions related to:
1) incoming messages
2) outgoing messages
3) channel discontinuity.
b) internal transactions related to:
1) terminal procedures (refer to section 3.2.3).
2) message distribution control
3) message servicing
4) dedicated supervisory commands.
3.2.5.2…02…L̲o̲g̲g̲i̲n̲g̲ ̲E̲v̲e̲n̲t̲s̲
The log shall consist of records generated at specific
events during a transaction i.e.
a) time of initiation and/or
b) time of termination, including premature completion
caused by:
1) cancel
2) suspend
3) time out
4) unsuccessful security interrogation.
The log records defined by the above events are in
the following referred to as initial respective final
log record.
3.2.5.3…02…S̲t̲o̲r̲a̲g̲e̲ ̲o̲f̲ ̲L̲o̲g̲ ̲R̲e̲c̲o̲r̲d̲s̲
…02…a) Log records shall be stored for 24 hours.
…02…b) Log records shall at least be stored, when 30 seconds
have elapsed or 5 records are collected, whichever
occurs first.
3.2.5.4…02…P̲r̲i̲n̲t̲ ̲o̲f̲ ̲L̲o̲g̲ ̲R̲e̲c̲o̲r̲d̲s̲
a) Log records.
…02…1) Log records shall be brief (max. one line) and
shall be queued for printing at a supervisory printer
at the time of occurrence of the event being logged.
…02…2) Log records shall be printed in a way facilitating
a visual separation of those entries referring
to internal transactions and those referring to
external transactions.
…02…b) Summary reports.
…02…1) A summary report of all transactions with a terminal
shall be printed at the operators associated printer.
…02…2) The printout is either executed periodically using
procedure Transaction Status (Format R1) every
60 minutes or every 12 hours as set by the systems
supervisor or upon request using procedure Transaction
status enquiry (Format R2). Refer to section 3.2.3.3.
…02…c) Log records retrieved during computer analysis of the
log storage (refer to section 3.2.5.5) shall be printed
at the supervisors printer.
3.2.5.5…02…T̲r̲a̲c̲i̲n̲g̲ ̲(̲C̲o̲m̲p̲u̲t̲e̲r̲ ̲A̲n̲a̲l̲y̲s̲i̲s̲)̲ ̲o̲f̲ ̲L̲o̲g̲ ̲I̲n̲f̲o̲r̲m̲a̲t̲i̲o̲n̲.̲
The log records stored may be retrieved by the supervisor
with respect to:
…02…a) a specific channel. The retrieval key is time interval
and a parameter defining:
1) incoming messages
2) outgoing messages
3) channel discontinuity
…02…b) a specific terminal.
…02… The retrieval key is time interval and a parameter
defining:
1) terminal procedures
2) message distribution control
3) message service
4) dedicated supervisory commands
5) security interrogations
…02…c) The retrieval is executed in such a way that no significant
performance reduction occurs.
3.2.5.6…02…D̲e̲f̲i̲n̲i̲t̲i̲o̲n̲ ̲o̲f̲ ̲S̲p̲e̲c̲i̲f̲i̲c̲ ̲L̲o̲g̲ ̲R̲e̲c̲o̲r̲d̲s̲
This section defines the logging events and the corresponding
log records contents.
3.2.5.6.1…02…L̲o̲g̲ ̲R̲e̲c̲o̲r̲d̲s̲ ̲r̲e̲l̲a̲t̲i̲n̲g̲ ̲t̲o̲ ̲I̲n̲c̲o̲m̲i̲n̲g̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲
3.2.5.6.1.1 L̲o̲g̲ ̲R̲e̲c̲o̲r̲d̲s̲ ̲r̲e̲l̲a̲t̲e̲d̲ ̲t̲o̲ ̲i̲n̲c̲o̲m̲i̲n̲g̲ ̲N̲I̲C̲S̲ ̲T̲A̲R̲E̲/̲T̲R̲C̲/̲P̲o̲i̲n̲t̲
t̲o̲ ̲P̲o̲i̲n̲t̲ ̲c̲o̲n̲n̲e̲c̲t̲i̲o̲n̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲
3.2.5.6.1.1.1 V̲a̲l̲i̲d̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲
A log record for each valid incoming NICS TARE/TRC/Point
to Point connection message is created when the message
is stored and analyzed.
…02…a) The log record contains:
…02… 1) ACP127 message format line 1-4 extract as defined
in a2 below
…02… 2) Time of reception of the end-of-message.
…02… 3) The SIC's determined by analysis of "line 12b"
of the message as defined in the ACP 127 format.
…02… 4) A code indicating that the record refers to a valid
incoming message.
…02…b) ACP 127 Message format line 1-4 extract used in logging.
An indicator for the following items is where applicable
extracted from an ACP 127 message and inserted in the
corresponding log record:
…02… 1) format line 1 extract, which constitutes a unique
reference number:
1.1) channel (station) designator
1.2) transmission serial No.
…02… 2) Format line 2 extract:
…02… 2.1) precedence of message
…02… 3) Format line 3 extract:
…02… 3.1) calling station (routing indicator)
…02… 3.2) release-ID of caller
…02… 3.2.1) release serial No.
…02… 3.2.2) DTG
…02…4) Format line 4 extract:
…02… 4.1) classification (security warning)
…02… 4.2) special handling category.
3.2.5.6.1.1.2 I̲n̲v̲a̲l̲i̲d̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲
A log record with respect to incoming NICS TARE/TRC/Point
to Point connection messages is defined at the time
it is sent for message service.
The log record contains:
a) ACP127 message format line 1 - 4 extract as defined
in a2 above.
b) Time of reception of end-of-message or time at
which the message is determined to have terminated..
c) If not available in the ACP127 messages (point
1 above)
1) Channel designator
2) (expected) transmission serial no.
d) The SIC's determined by analysis of "line l2b"
of the message as defined in the ACP127 format.
…02…e) A code indicating, that the record refers to an incoming
message.
…02…f) A code indicating the reason for requesting message
service.
g) When applicable, a code indicating that transmission
preemption procedures have been invoked.
3.2.5.6.1.1.3 A̲u̲t̲o̲m̲a̲t̲i̲c̲a̲l̲l̲y̲ ̲D̲e̲l̲e̲t̲e̲d̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲
For messages, which are automatically deleted i.e.
COSMIC TOP SECRET and COSMIC TOP SECRET ATOMAL the
following record is used per message deleted:
a) for outgoing messages: the release-id
for incoming messages: the channel-id
b) a code indicating that deletion has taken place
c) the time of deletion.
3.2.5.6.1.2 L̲o̲g̲ ̲R̲e̲c̲o̲r̲d̲s̲ ̲R̲e̲l̲a̲t̲i̲n̲g̲ ̲t̲o̲ ̲I̲n̲c̲o̲m̲i̲n̲g̲ ̲A̲C̲E̲ ̲C̲C̲I̲S̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲.̲
TBD
3.2.5.6.1.3 L̲o̲g̲ ̲R̲e̲c̲o̲r̲d̲s̲ ̲R̲e̲l̲a̲t̲i̲n̲g̲ ̲t̲o̲ ̲I̲n̲c̲o̲m̲i̲n̲g̲ ̲S̲C̲A̲R̲S̲ ̲I̲I̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲.̲
TBD
3.2.5.6.2 L̲o̲g̲ ̲R̲e̲c̲o̲r̲d̲s̲ ̲R̲e̲l̲a̲t̲i̲n̲g̲ ̲t̲o̲ ̲O̲u̲t̲g̲o̲i̲n̲g̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲.
3.2.5.6.2.1 N̲I̲C̲S̲ ̲T̲A̲R̲E̲/̲T̲R̲C̲/̲P̲o̲i̲n̲t̲ ̲t̲o̲ ̲P̲o̲i̲n̲t̲ ̲C̲o̲n̲n̲e̲c̲t̲i̲o̲n̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲
a) A log record with respect to each outgoing NICS
TARE/TRC/Point to Point connnection message is
defined, when the message transmission is terminated.
b) The above log record contains:
1) ACP127 message line 1-4 extract as defined
in 3.2.5.6.1.1.(a2)
2) Time of transmission of the first character
of the "start-of-transmission" indicator (ZCZC)
3) A code indicating that the record refers to
an outgoing message
…02……02…4) When applicable, a code indicating that the transmission
has been prematurely terminated.
c) A̲u̲t̲o̲m̲a̲t̲i̲c̲a̲l̲l̲y̲ ̲D̲e̲l̲e̲t̲e̲d̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲
Log records are generated by automatic deletion
of some outgoing NICS TARE/TRC message as described
in section 3.2.5.6.1.1. (c)
3.2.5.6.2.2 L̲o̲g̲ ̲R̲e̲c̲o̲r̲d̲s̲ ̲R̲e̲l̲a̲t̲i̲n̲g̲ ̲t̲o̲ ̲O̲u̲t̲g̲o̲i̲n̲g̲ ̲A̲C̲E̲ ̲C̲C̲I̲S̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲
TBD
3.2.5.6.2.3 L̲o̲g̲ ̲R̲e̲c̲o̲r̲d̲s̲ ̲R̲e̲l̲a̲t̲i̲n̲g̲ ̲t̲o̲ ̲O̲u̲t̲g̲o̲i̲n̲g̲ ̲S̲C̲A̲R̲S̲ ̲I̲I̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲
TBD
3.2.5.6.3 C̲h̲a̲n̲n̲e̲l̲ ̲D̲i̲s̲c̲o̲n̲t̲i̲n̲u̲i̲t̲y̲
3.2.5.6.3.1 N̲I̲C̲S̲ ̲T̲A̲R̲E̲/̲T̲R̲C̲/̲P̲o̲i̲n̲t̲ ̲t̲o̲ ̲P̲o̲i̲n̲t̲ ̲C̲o̲n̲n̲e̲c̲t̲i̲o̲n̲ ̲C̲h̲a̲n̲n̲e̲l̲
̲D̲i̲s̲c̲o̲n̲t̲i̲n̲u̲i̲t̲y̲
The external channel accounting with respect to NICS
TARE/TRC/Point to Point connection messages shall result
in a log record in case of the following events:
a) Discontinuity of incoming message traffic as detected
from improper serial number sequence.
The log record contains the following information.
1) expected channel serial number
2) Channel designator and channel serial no. (from
line 1 in ACP127 format)
3) Time of event
…02……02…4) A code indicating the type of the log record
…02…b) Missing transmission serial number of incoming traffic.
The log record contains the following information.
1) Expected serial number
2) Channel designator
3) Time of events
4) A code indicating the type of the log record
3.2.5.6.3.2 L̲o̲g̲ ̲R̲e̲c̲o̲r̲d̲s̲ ̲R̲e̲l̲a̲t̲i̲n̲g̲ ̲t̲o̲ ̲A̲C̲E̲ ̲C̲C̲I̲S̲ ̲C̲h̲a̲n̲n̲e̲l̲ ̲d̲i̲s̲c̲o̲n̲t̲i̲n̲u̲i̲t̲y̲
TBD
3.2.5.6.3.3 L̲o̲g̲ ̲R̲e̲c̲o̲r̲d̲s̲ ̲R̲e̲l̲e̲a̲t̲i̲n̲g̲ ̲t̲o̲ ̲S̲C̲A̲R̲S̲ ̲I̲I̲ ̲C̲h̲a̲n̲n̲e̲l̲ ̲D̲i̲s̲c̲o̲n̲t̲i̲n̲u̲i̲t̲y̲
TBD
3.2.5.6.4 T̲e̲r̲m̲i̲n̲a̲l̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲s̲
a) Associated with logging of transactions relating
to the terminal procedures in table 3.2.5.6.4-1
below are two types of log records, as defined
below:
Record Items type I type
F
initial final
…02……02… ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
1 Transaction ID* x
x
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
2 A code indicating the procedure
is being used x
x
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲
3 Time of completion of transaction
x
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲
4 If applicable a code indicating the
reason for premature termination
x
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲
5 If security interrogation: a code in-
dicating the operator identity
x
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲
* at the time of initiation of the transaction
Table 3.2.5.6.4-1
Procedure expl. type I
Type F
initial
final
log
log
record
record
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
A Initial message preparation x
x
B Message coordination
x
C1 Message editing x
x
C2 Clean copy of message not
logged
D Release of messages special*
E1 Incoming message presentation special*
E2 Outgoing message presentation special*
F Notification of release
x
G1 Initial comment preparation x
x
G2 Comment presentation
x
G3 Comment editing x
x
H Retrieval x
x
I1 Security interrogation
x
I2 Security Warning
x
J Time statement not
logged
K1 Signing-in
x
K2 Signing-out x
L Change of Password
x
M1-Mn Text formats not
logged
N1 Message status x
N2 Message status enquiry x
x
O Message merge x
x
P1 Message deletion request x
P2 Message deletion notification x
Q1 Message release status
x
Q2 Message release status enquiry
x
R1 Transaction status x
R2 Transaction Status Enquiry x
S Terminal Status not
logged
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
*Defined on following pages.
Table 3.2.5.6.4.-2 Log records associated to terminal
procedures.
b) R̲e̲l̲e̲a̲s̲e̲ ̲o̲f̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e A release procedure
results in a final log record with the following
information:
1) Transaction ID
2) A code indicating that the record refers to
message release
3) A code indicating whether the message release
was approved, rejected or deferred
4) If approved, the release-ID
5) If applicable, a code indicating why the transaction
was prematurely terminated
c) I̲n̲c̲o̲m̲i̲n̲g̲/̲O̲u̲t̲g̲o̲i̲n̲g̲ ̲M̲e̲s̲s̲a̲g̲e̲ ̲P̲r̲e̲s̲e̲n̲t̲a̲t̲i̲o̲n̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲s̲
̲(̲E̲1̲ ̲a̲n̲d̲ ̲E̲2̲)̲
The incoming/outgoing message presentation procedures
(when queueing the associated message for distribution)
results in a log record with the following information:
1) Transaction-ID
2) A code indicating the procedure involved
3) The channel-ID of the incoming message (E1)
or the release-ID allocated to the message
on release (E2)
4) If applicable, a code indicating why the transaction
was prematurely terminated.
5) A code indicating the operator identity if
a successful security interrogation took place
before presentation.
6) An indication of the total number of transmissions
required for the message and the number outstanding
3.2.5.6.5 M̲e̲s̲s̲a̲g̲e̲ ̲D̲i̲s̲t̲r̲i̲b̲u̲t̲i̲o̲n̲ ̲C̲o̲n̲t̲r̲o̲l̲
The supervisor's use of message distribution control
procedures shall result in an initial log record with
the following information:
a) Transaction-ID
b) A code defining the specific procedure
c) A message reference
1) For outgoing messages: Release-ID
2) For incoming messages: Channel-ID
d) A code indicating the reason for diversion.
3.2.5.6.6 M̲e̲s̲s̲a̲g̲e̲ ̲S̲e̲r̲v̲i̲c̲e̲
The supervisor's use of message service procedures
shall result in an initial log record with the information
defined in section 3.2.5.6.5.
3.2.5.6.7 S̲u̲p̲e̲r̲v̲i̲s̲o̲r̲y̲ ̲C̲o̲m̲m̲a̲n̲d̲s̲
The supervisor's use of dedicated commands shall result
in an initial log record with the following information:
a) Transaction-ID
b) A code indicating which procedure is being used.
T̲A̲B̲L̲E̲ ̲O̲F̲ ̲C̲O̲N̲T̲E̲N̲T̲S̲…01…S̲e̲c̲t̲i̲o̲n̲ ̲3̲.̲2̲.̲6̲
3.2.6.1 Statistical Data on Messages .....
3.2.6.1.1 Incoming Messages ............
3.2.6.1.2 Outgoing Messages ............
3.2.6.1.3 Rejected Messages ............
3.2.6.2 Storage Occupancy ................
3.2.6.3 Channel Availability and Occupancy
3.2.6.4 Message Distribution .............
3.2.6.5 Use of Message Formats ...........
3.2.6.5.1 Formats A, C1, G1, M, O ......
3.2.6.5.2 Formats B, D, F, G2, H, I, N1
N2, P1, P2, Q1, Q2, R1 and R2
3.2.6.1 S̲t̲a̲t̲i̲s̲t̲i̲c̲a̲l̲ ̲D̲a̲t̲a̲ ̲o̲n̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲
3.2.6.1.1 I̲n̲c̲o̲m̲i̲n̲g̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲
The information shall be recorded for each incoming
channel and a statistic maintained for the
- current day for each complete hour from 0001 hours
- previous day for each hour from 0001 hours to 2400
hours
- each week with a predefined starting day of last
4 complete weeks.
The following information shall be recorded:
a) Total number of messages received
b) Average length of messages in characters (from
start of transmission indicator to end of transmission
function).
c) Number of messages received by each precedence
level.
d) Number of messages received by each security classification
category.
e) Number of messages received for each special handling
category.
3.2.6.1.2 O̲u̲t̲g̲o̲i̲n̲g̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲
Statistics concerning transmitted messages shall be
compiled on the same channel and time basis as for
incoming messages and contain the same information
categories.
3.2.6.1.3 R̲e̲j̲e̲c̲t̲e̲d̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲
The system shall maintain the following statistics
concerning incoming messages which were rejected for
manual editing when input to the system for automatic
processing; they shall be compiled on the same channel
and time criteria as in 3.2.6.1.1. The statistic shall
be maintained for:
- Total number of rejected messages
3.2.6.2 S̲t̲o̲r̲a̲g̲e̲ ̲O̲c̲c̲u̲p̲a̲n̲c̲y̲
The system shall record hourly the "storage occupancy"
with respect to messages being processed. The occupancy
shall be defined as a percentage of the capacity allocated
to the storage of messages being processed and shall
be calculated for the current hour to time of request
and for the previous hour.
The messages in question are
- incoming messages for which delivery has not been
completed (taking into account all copies).
- outgoing messages which have been released but
not yet transmitted.
3.2.6.3 C̲h̲a̲n̲n̲e̲l̲ ̲A̲v̲a̲i̲l̲a̲b̲i̲l̲i̲t̲y̲ ̲a̲n̲d̲ ̲O̲c̲c̲u̲p̲a̲n̲c̲y̲
The system shall maintain a record of "channel status
(open/closed)" to calculate the actual availability.
Statistics shall be available indicating for each
channel:
- hourly availability for the current day (each complete
hour from 0001 hours)
- average daily availability to date as well as the
daily averages for the previous seven days.
The channel occupancy with traffic shall be calculated
as a percentage of the availability based on the traffic
information collected in 3.2.6.1.1 and 3.2.6.1.2 and
with the same time criteria as the availability.
3.2.6.4 M̲e̲s̲s̲a̲g̲e̲ ̲D̲i̲s̲t̲r̲i̲b̲u̲t̲i̲o̲n̲
The system shall maintain a record of message distribution
information for
incoming messages:
- total system
- each distribution terminal separately
and for information copies of outgoing messages:
- total system
- each distribution terminal separately
The record shall contain
a) Number of messages delivered
b) Average and maximum length of a message
c) Distribution by classification
d) Distribution by special handling category
e) Distribution by precedence and with respect to
the total values only
f) The average and maximum number of terminals included
in the distribution
g) The number of messages requiring assistance.
The statistic shall be based on the time criteria of
3.2.6.1.1.
3.2.6.5 U̲s̲e̲ ̲o̲f̲ ̲M̲e̲s̲s̲a̲g̲e̲ ̲F̲o̲r̲m̲a̲t̲s̲
The system shall record the information below based
on the time criteria of 3.2.6.1.1.
Formats assocaited with CAMPS/CCIS and CAMPS/SCARS
interface shall also be treated in the same manner.
3.2.6.5.1 F̲o̲r̲m̲a̲t̲s̲ ̲A̲,̲ ̲C̲1̲,̲ ̲G̲1̲,̲ ̲M̲,̲ ̲O̲
Statistics shall be compiled for each format for
- total system
- each terminal
as follows:
a) Number of times the format has been used
b) The average and maximum duration of use
c) Distribution by security classification category
d) Distribution by precedence level
e) Average and maximum amount of new information introduced
each time it is used, in terms of characters entered
or changed.
3.2.6.5.2 F̲o̲r̲m̲a̲t̲s̲ ̲B̲,̲ ̲D̲,̲ ̲F̲,̲ ̲G̲2̲,̲ ̲H̲,̲ ̲I̲,̲ ̲N̲1̲,̲ ̲N̲2̲,̲ ̲P̲1̲,̲ ̲P̲2̲,̲ ̲Q̲1̲,̲
̲Q̲2̲,̲ ̲R̲1̲ ̲a̲n̲d̲ ̲R̲2̲.̲
Statistics shall be compiled for each format for
- total system
- each terminal
of the number of times the format has been used.
T̲A̲B̲L̲E̲ ̲O̲F̲ ̲C̲O̲N̲T̲E̲N̲T̲S̲
S̲e̲c̲t̲i̲o̲n̲ ̲3̲.̲2̲.̲7̲ ̲
…02……02……02…3.2.7 Storage and Retrieval.................
…02……02……02……02…3.2.7.1 Message Storage and Retrieval.....
…02……02……02……02……02…3.2.7.1.1 Storage and Retrieval of
…02……02……02……02……02……02……02……02……02……02… the Result of Initial
…02……02……02……02……02……02……02……02……02……02… preparation...................
…02……02……02……02……02…3.2.7.1.2 Storage and Retrieval of
…02……02……02……02……02……02……02……02……02……02… Messages as Released..........
…02……02……02……02……02…3.2.7.1.3 Storage and Retrieval of
…02……02……02……02……02……02……02……02……02……02… Incoming Messages.............
…02……02……02……02…3.2.7.2 Storage and Retrieval of Non-
…02……02……02……02……02……02……02……02……02…Message Traffic..................
3.2.7…02…S̲t̲o̲r̲a̲g̲e̲ ̲a̲n̲d̲ ̲R̲e̲t̲r̲i̲e̲v̲a̲l̲
a) This section describes the storage and retrieval
as available to supervisory terminal positions
and preparation reception terminal position.
b) This section excludes a description of the temporary
storage of messages and other output from transactions
as required in order to support initial preparation,
suspend, edit, coordination and other transactions
related to a message prior to release authorization
is given.
c) Messages and transactions shall be stored as specified
below.
d) Messages and non-messages shall be retrievable
as specified below.
e) Storage may be on-line or off-line.
f) Online storage is characterized by the fact that
no mounting of physical media is required to retrieve
the message.
g) The timespan for online storage is in the order
of days (refer 3.4.1.3.1, 3.4.1.4.1).
h) Offline storage normally requires that a media
must be loaded prior to retrieval.
i) Timespan for offline storage in the order of weeks
(refer 3.4.1.3.2, 3.4.1.4.2).
j) It is acceptable that retrieval from offline storage
is temporarily impossible when the interface/drive
is occupied by other tasks.
3.2.7.1 M̲e̲s̲s̲a̲g̲e̲ ̲S̲t̲o̲r̲a̲g̲e̲ ̲a̲n̲d̲ ̲R̲e̲t̲r̲i̲e̲v̲a̲l̲
a) Operational messages and service messages are subject
to storage and retrieval as specified below except
messages of categories COSMIC TOP SECRET and COSMIC
TOP SECRET ATOMAL.
b) Data messages are subject to storage and retrievalfor
reruns only.
3.2.7.1.1 S̲t̲o̲r̲a̲g̲e̲ ̲a̲n̲d̲ ̲R̲e̲t̲r̲i̲e̲v̲a̲l̲ ̲o̲f̲ ̲t̲h̲e̲ ̲R̲e̲s̲u̲l̲t̲ ̲o̲f̲ ̲I̲n̲i̲t̲i̲a̲l̲
̲P̲r̲e̲p̲a̲r̲a̲t̲i̲o̲n̲
a) Upon termination of the use of initial preparation
(Format A) the prepared first draft shall be stored.
b) The first draft shall be retrievable using as keys
1) DTG, and
2) Terminal designator + transaction serial number.
c) First draft may be retrieved from
1) Terminal position with terminal designator
identical to the above retrieval key terminal
designator.
2) Supervisor position
3) Any message distribution position
3.2.7.1.2 S̲t̲o̲r̲a̲g̲e̲ ̲a̲n̲d̲ ̲R̲e̲t̲r̲i̲e̲v̲a̲l̲ ̲o̲f̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲ ̲a̲s̲ ̲R̲e̲l̲e̲a̲s̲e̲d̲
a) Upon release messages shall be stored.
b) The released copy shall be retrievable using as
keys
1) DTG, and
2) Release ID + release serial number.
c) Released copy may be retrieved by
1) Supervisor position
2) Any message distribution position
d) Upon distribution of INFO copies to local terminal
positions, either automatically or supported by
the MDCO, the released copy shall only be retrievable
from terminal positions receiving a copy.
e) The retrieval keys for the latter case are
1) DTG at time of reception and
2) Terminal designator and serial number
f) The latter retrieval may be performed from
1) Terminal positions with terminal designator
identical to the above retrieval key terminal
designator
2) Supervisor position
3) Any messages distribution position
3.2.7.1.3 S̲t̲o̲r̲a̲g̲e̲ ̲a̲n̲d̲ ̲R̲e̲t̲r̲i̲e̲v̲a̲l̲ ̲o̲f̲ ̲I̲n̲c̲o̲m̲i̲n̲g̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲
a) Incoming messages shall after being analyzed for
correctness according to ACP 127 and after possibly
being corrected by Message Service be stored in
an incoming copy.
b) Retrieval of incoming copy shall be possible using
as keys
1) DTG, and
2) Channel-designator + channel serial number.
c) Retrieval using keys above shall be possible by
1) Supervisor position
2) Any message distribution position
d) After being distributed either automatically by
means of SIC's or as selected by the MDCO, and
after being correctly received at a terminal position,
retrieval shall be possible using keys
e) DTG at time of reception and Terminal designator
+ transaction serial number.
f) The latter retrieval may be performed by
1) Terminal position with terminal designator
identical to the above retrieval key terminal
designator.
2) Supervisor position.
3) Any message distribution position.
3.2.7.2 S̲t̲o̲r̲a̲g̲e̲ ̲a̲n̲d̲ ̲R̲e̲t̲r̲i̲e̲v̲a̲l̲ ̲o̲f̲ ̲N̲o̲n̲-̲m̲e̲s̲s̲a̲g̲e̲ ̲T̲r̲a̲f̲f̲i̲c̲
a) Release notifications shall be stored.
b) Upon correct reception of release notification
at appropriate preparation position, retrieval
of release notifications shall be possible using
keys
1) DTG at time of reception and Terminal designator
+ transaction serial number.
c) The retrieval of release notifications shall be
possible by
1) Terminal positions with terminal designator
identical to the above retrieval key terminal
designator.
2) Supervisor position
3) Any message distribution terminal position.
T̲A̲B̲L̲E̲ ̲O̲F̲ ̲C̲O̲N̲T̲E̲N̲T̲S̲…01…S̲e̲c̲t̲i̲o̲n̲ ̲3̲.̲2̲.̲8̲
…02……02……02…3.2.8 Start up and Errorhandling ...........
…02……02……02……02…3.2.8.1 On-line and Off-line CAMPS site
Software Packages.................
…02……02……02……02…3.2.8.2 Initialization....................
…02……02……02……02…3.2.8.3 Error Handling....................
…02……02……02……02……02…3.2.8.3.1 Error Types...................
…02……02……02……02……02…3.2.8.3.2 Error Detection...............
…02……02……02……02……02……02…3.2.8.3.2.1 On-line Error Detection...
…02……02……02……02……02……02…3.2.8.3.2.2 Off-line Error Detection..
…02……02……02……02……02…3.2.8.3.3 Error Reports.................
…02……02……02……02……02…3.2.8.3.4 Error Reactions...............
…02……02……02……02……02…3.2.8.3.5 Audit reports.................
…02……02……02……02…3.2.8.4 Recovery Situations...............
…02……02……02……02……02…3.2.8.4.1 Recovery/Restart from
Total System Error............
…02……02……02……02……02…3.2.8.4.2 Recovery/Restart after
Switchover ...................
…02……02……02……02…3.2.8.5 Degraded Availability
Configuration.....................
3.2.8 S̲t̲a̲r̲t̲ ̲u̲p̲ ̲a̲n̲d̲ ̲E̲r̲r̲o̲r̲ ̲H̲a̲n̲d̲l̲i̲n̲g̲
This chapter describes:
- on-line and off-line software packages, which are
used during initialization and recovery.
- initialization
- error handling, defining error detection, error
reporting and errorre actions (includes recovery
actions)
- degraded availability configuration.
Definition of terms:
- start up:
includes all aspects of initialization, recovery
and restart.
- Initialization:
brings the system from cold start into operational
use.
- Recovery:
reestablishes continuity in memory and file contents.
- Restart:
Reestablishes the dynamic behaviour of the system
based upon recovered data.
3.2.8.1 O̲n̲-̲l̲i̲n̲e̲ ̲a̲n̲d̲ ̲O̲f̲f̲-̲l̲i̲n̲e̲ ̲C̲A̲M̲P̲S̲ ̲S̲i̲t̲e̲ ̲S̲o̲f̲t̲w̲a̲r̲e̲ ̲P̲a̲c̲k̲a̲g̲e̲s̲
a) CAMPS contains for each site an on-line and an
off-line software package.
b) The off-line CAMPS site software package shall
be selected from a common library of routines and
shall form the basis for generation of the on-line
software package.
c) The off-line CAMPS site software package shall
contain the following data:
1) initial system parameter file, which contains:
1.1) the planned hardware configuration.
1.2) the standard settings of all other system
parameters required to put the system
into operational use, including default
values for those parameters, which can
be set by the supervisor.
2) a back-up of the current on-line system parameter
file (refer to point f. below.)
3) system programs library.
4) application programs library
d) The initial system parameters (refer point c, 1)
for each CAMPS installation shall be provided by
the contractor using information supplied by the
purchaser.
e) The on-line CAMPS site software package shall contain
the following data:
1) current system parameter file, which contains
the initial system parameter file last loaded
into the system with all the parameter changes
entered by supervisory commands since the time
of loading.
2) system programs library, which contains an
extract of the off-line system programs library.
3) application programs library, which contains
an extract of the off-line application programs
library.
f) It shall be possible for the supervisor to back-up
the current on-line system parameter file, i.e.
to command the production of an offline copy of
the online file.
1) The back-up shall be made without interruption
to the normal operation of the system.
2) The back-up system parameter file may be used
as initial system parameter file at a succeeding
initialization.
3.2.8.2 I̲n̲i̲t̲i̲a̲l̲i̲z̲a̲t̲i̲o̲n̲
a) The initialization contains the steps to bring
the system from cold start into operational use.
b) The CAMPS site software package shall normally
be available on-line for the initialization procedures.
c) It shall be possible to generate the on-line CAMPS
site software package by loading the off-line CAMPS
site software package.
d) The maximum allowable period from start until completion
of the initialization from an off-line source shall
not exceed 15 minutes.
e) The system shall be initialized with an empty historical
data base.
3.2.8.3 E̲r̲r̲o̲r̲h̲a̲n̲d̲l̲i̲n̲g̲
a) Errorhandling shall fulfil the requirements for
1) equipment availability/reliability
2) the integrity of operation (refer to b below)
b) 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:
1) lost wholly or in part, or
2) misdirected, or
3) corrupted
as a result of an equipment error, shall be less
than 1 in 10…0e…7…0f….
3.2.8.3.1 E̲r̲r̲o̲r̲ ̲T̲y̲p̲e̲s̲
a) Transient errors, which can not be verified by
repetition, shall not imply that the associated
equipment or software is considered erroneous.
b) Transient errors shall be categorized in relation
to equipment configuration
3.2.8.3.2 E̲r̲r̲o̲r̲ ̲D̲e̲t̲e̲c̲t̲i̲o̲n̲
3.2.8.3.2.1 O̲n̲-̲l̲i̲n̲e̲ ̲E̲r̲r̲o̲r̲ ̲D̲e̲t̲e̲c̲t̲i̲o̲n̲
a) The system shall be provided with automatic on-line
facilities to detect hardware and software errors:
- on line test programs operating as low priority
tasks shall be available.
b) The use of these facilities shall not degrade the
normal message handling function.
c) Peripheral equipment shall be interfaced to the
central computer system, in such a way that their
error conditions can be evaluated.
3.2.8.3.2.2 O̲f̲f̲-̲l̲i̲n̲e̲ ̲E̲r̲r̲o̲r̲ ̲D̲e̲t̲e̲c̲t̲i̲o̲n̲
a) The engineering staff shall have the facilities
to run diagnostic programs.
b) These programs shall be stored in a rapid access
storage.
c) Refer to section 3.2.8.5 for a description of the
configurational requirements.
3.2.8.3.3 E̲r̲r̲o̲r̲ ̲R̲e̲p̲o̲r̲t̲s̲
a) An error report shall be printed at the supervisor
printer, when an error has been detected.
b) The error report shall specify the error type.
c) When manual intervention is specified, the error
condition detected shall be signalled clearly to
the supervisor together with a suggested corrective
procedure.
3.2.8.3.4 E̲r̲r̲o̲r̲ ̲r̲e̲a̲c̲t̲i̲o̲n̲s̲
a) Subsequent corrective actions to errors such as
reconfiguration of replaceable modules shall be
defined to fulfill the requirements in section
3.2.8.3 (a).
3.2.8.3.5 A̲u̲d̲i̲t̲ ̲R̲e̲p̲o̲r̲t̲s̲
a) Audit reports based upon error reporting and log
information shall be generated to fulfil the requirements
for system availability integnity and overall security.
3.2.8.4 R̲e̲c̲o̲v̲e̲r̲y̲ ̲s̲i̲t̲u̲a̲t̲i̲o̲n̲s̲
Section 3.2.8.4 handles detailed recovery requirements
in the following situations:
- total system error
- error requiring a switchover
3.2.8.4.1 R̲e̲c̲o̲v̲e̲r̲y̲/̲R̲e̲s̲t̲a̲r̲t̲ ̲f̲r̲o̲m̲ ̲T̲o̲t̲a̲l̲ ̲S̲y̲s̲t̲e̲m̲ ̲E̲r̲r̲o̲r̲
a) The system shall preserve essential data enabling
recovery in case of total system error.
b) A total system error may be caused by:
1) simultaneous error in redundant equipment
2) error in main power supply
3) detection of a program error, which cannot
be recovered internally.
c) No message must be lost within the network e.g.
1) messages, which were only partially transmitted
or for which FLASH acknowledgement have not
been received prior to the error, shall be
retransmitted.
2) continuity of the reporting system shall be
maintained to ensure, that messages are not
lost within the network as a consequence of
the loss of either a report or an automatically
generated service message.
d) Continuity shall be maintained to the time defined
by the last storage with respect to the following
data items:
1) log records
2) statistics
3) messages/comments in the HDB
4) current system parameter file
5) message accounting
e) The data (defined above) stored prior to the total
system error can be recalled by the use of normal
commands.
f) Integrity of memory shall be maintained to ensure
that the system will not fail as a consequence
of operating upon corrupted data generated by a
preceding error.
g) Restart subsequent to recovery shall be based upon
the system parameter file obtained in 3.2.8.1(e).
h) Certain errors may preclude total recovery. In
these cases the system is recovered so that the
chance of losing a message is minimized.
i) Recovery and restart subsequent to a total system/restart
error will be finalized within 15 minutes.
3.2.8.4.2 R̲e̲c̲o̲v̲e̲r̲y̲ ̲a̲f̲t̲e̲r̲ ̲S̲w̲i̲t̲c̲h̲-̲o̲v̲e̲r̲
a) Where redundant equipment is provided to meet the
availability/reliability requirements, the switch
over from an active configuration to a standby
configuration shall not result in loss of messages,
i.e
1) The communication protocols shall ensure retransmission
of messages being garbled or partly lost.
2) The accountability log shall ensure that the
accountability related to messages is not lost
b) Where a transaction at a terminal is in progress
the user shall be informed of the state to which
the transaction has been recovered after switch
over.
c) A switch over initiated by the detection of an
error, shall normally not require operator intervention.
3.2.8.5 D̲e̲g̲r̲a̲d̲e̲d̲ ̲A̲v̲a̲i̲l̲a̲b̲i̲l̲i̲t̲y̲ ̲C̲o̲n̲f̲i̲g̲u̲r̲a̲t̲i̲o̲n̲
a) It is acceptable, that redundant modules are withdrawn
from use in the operational configuration. The
hereby obtained configuration is named: degraded
availability configuration.
b) The degraded availability configuration may be
entered in order to perform any of the following
actions:
1) preventive maintenance
2) loading and checkout of new software
3) execution of diagnostics programs
4) on-job training
c) Any of the above mentioned action shall not result
in interruption in the normal message handling
function.
d) An error in the degraded availability configuration
shall be handled as a total system error (refer
to section 3.2.8.4.1).
e) It shall be possible to reintegrate withdrawn modules
into the operational configuration and return them
to service within 5 minutes.
f) For preventive maintenance actions requiring longer
than this time, sufficient units shall be provided
to maintain the overall availability of the equipment.
g) If switch over is required for maintenance purposes
this switch over shall proceed automatically once
it has been initiated by the supervisor.
h) The availability/reliability and integrity of operation
requirements applies to the normal dualized CAMPS
equipment configuration and not to the degraded
availability configuration.
