top - download
⟦894d36546⟧ Wang Wps File
Length: 49267 (0xc073)
Types: Wang Wps File
Notes: CPS/ECP/016
Names: »1397A «
Derivation
└─⟦3d850f1a5⟧ Bits:30006054 8" Wang WCS floppy, CR 0085A
└─ ⟦this⟧ »1397A «
WangText
1…08……86…1
…02…
…02… …02…
…02…CPS/ECP/016
…02…TDJ/811221…02……02…#
CHANGES TO THE REQUIREMENT BASELINE
…02…Issue 1…02…CAMPS
T̲A̲B̲L̲E̲ ̲O̲F̲ ̲C̲O̲N̲T̲E̲N̲T̲
1 COST IMPACT ...................................
3
2 SCHEDULE IMPACT ...............................
3
3 PROPOSED CHANGES ..............................
3
A INCONSISTENCIES ............................
4
B EDITORIALS .................................
11
C DNs FROM PDR ...............................
13
D ACTION ITEMS ...............................
17
E CLARIFICATIONS .............................
20
1̲ ̲ ̲C̲O̲S̲T̲ ̲I̲M̲P̲A̲C̲T̲
None, regarding these changes.
2̲ ̲ ̲S̲C̲H̲E̲D̲U̲L̲E̲ ̲I̲M̲P̲A̲C̲T̲
None, regarding these changes.
3̲ ̲ ̲P̲R̲O̲P̲O̲S̲E̲D̲ ̲C̲H̲A̲N̲G̲E̲S̲
This ECP contains a collection of changes to the requirement
baselines, mainly the CPS/210/SYS/0001, but also the
ICDs No. 1, 2, 3, and 5.
The changes are in the first place caused by the Preliminary
Design Review, i.e. Discrepancy Notes and Action Items.
But also during our package design and test procedure
description many inconsistencies and clarifications
were found.
The changes are sectioned in 5 groups:
- Inconsistencies
- Editorials
- DNs from PDR
- Action Items
- Clarifications
A INCONSISTENCIES
******************
1) I̲N̲C̲O̲N̲S̲I̲S̲T̲E̲N̲C̲I̲E̲S̲ ̲B̲E̲T̲W̲E̲E̲N̲ ̲S̲E̲C̲.̲ ̲3̲.̲1̲ ̲A̲N̲D̲ ̲3̲.̲2̲ ̲I̲N̲ ̲T̲H̲E̲ ̲S̲R̲S̲
Inconsistencies between section 3.1.1.2 f) and section
3.2.2.3.1 a) 3).
a) Section 3.1.1.2 f) will be changed:
was:
If the SIC identifies an exercise message then
the distribution will be based on a special exercise
standard distribution list.
should be:
For an exercise message (as identified by "EXER"
prosign in format line 12 c) the distribution will
be based on a special exercise standard distribution
list.
b) Figure 3.1 - 3A will be updated. "Channel" will
be changed to "Circuit" in "PLA/CHANNEL/CLASSIFICATION
TABLE".
c) Page 35 and 36 will be updated with the names of
transactions as used in section 3.2.3.3.
Message Merge will be changed to Message Append,
and Message Edit will be changed to Continue Preparation
of Message, etc.
2) A̲S̲S̲O̲C̲I̲A̲T̲E̲D̲ ̲R̲E̲L̲E̲A̲S̲E̲ ̲P̲O̲S̲I̲T̲I̲O̲N̲
It is the user, who is associated with a release position.
This give rise to the following updates in CPS/210/SYS/0001:
a) section 3.1.2.1 h)
was:
(Each staff cell designator has one associated release
position ...........)
should be:
(Each User has one associated release position .............)
b) section 3.2.1.2.3 a)
was:
........ which the drafter's terminal position
is associated.
should be:
........ which the drafter is associated.
3) S̲U̲P̲E̲R̲V̲I̲S̲O̲R̲ ̲S̲U̲S̲P̲E̲N̲D̲/̲P̲R̲E̲-̲E̲M̲P̲T̲
Section 3.2.1.3.1.2 e) 2) of CPS/210/SYS/0001 shall
be deleted. It is in conflict with:
- There is no pre-emption on VDUs (refer to 3.2.3.4
h) 1) a))
- Suspend does not apply to supervisory terminal
positions (refer 3.2.4 d)).
4) I̲T̲E̲M̲ ̲R̲E̲F̲.̲ ̲I̲D̲ ̲I̲N̲S̲T̲E̲A̲D̲ ̲O̲F̲ ̲T̲D̲ ̲+̲ ̲S̲E̲R̲.̲ ̲N̲O̲.̲
A service message as well as a normal message is identified
during the preparation phase by the Item Reference
Identity and not be means of the terminal designator
and serial number. Section 3.2.1.3.1.2 d) of the SRS
needs to be updated accordingly.
5) I̲N̲C̲O̲N̲S̲I̲S̲T̲E̲N̲C̲I̲E̲S̲ ̲W̲I̲T̲H̲ ̲D̲E̲S̲I̲G̲N̲
The following changes are caused by inconsistencies
between the requirement and the reviewed design.
a) In section 3.2.4.1.1.14 a) 1) of the SRS:
Change "channel" to read "circuit"
b) On page 208 of the SRS in row 3 named "Locally
dist. of Message" and column 4 named "originator":
Change "SCD" to read "PLA ref."
6) C̲O̲N̲V̲E̲R̲S̲I̲O̲N̲ ̲O̲F̲ ̲C̲O̲M̲P̲L̲E̲T̲E̲ ̲M̲E̲S̲S̲A̲G̲E̲S̲
Inconsistency between section 3.2.1.4 and 3.2.1.5.3
in the SRS.
Section 3.2.1.4 defines messages from OCR as complete
messages.
Section 3.2.1.5.3 specifies the processing of complete
messages. And this processing does not apply for OCR
entered messages.
a) Updates to section 3.2.1.5.3:
was:
Messages entered under the provision of section
3.2.1.4 as complete, shall be processed as follows:
should be:
Messages entered under the provision of section
3.2.1.4 as complete, except messages from the OCR
which except for release are treated as VDU prepared
messages, shall be processed as follows:
7) I̲N̲S̲E̲R̲T̲I̲O̲N̲ ̲O̲F̲ ̲F̲R̲O̲M̲ ̲P̲L̲A̲
The FROM PLA is inserted in format A by the drafter
and not by the system. Refer CPS/230/ICD/0001 section
3.4.1.10.
This give rise to the following updates in CPS/210/SYS/0001:
a) Section 3.1.1.2 d)
was:
The addressing logic is shown in figure 3.1 - 3A
and B and is in short that the drafter or originator
of a message inserts ACTION and INFO address information
in the message in form of PLAs and SICs. The system
itself inserts the originator PLA. The drafter
may insert the PLAs either as:
should be:
The addressing logic is shown in figure 3.1 - 3A
and B and is in short that the drafter or originator
of a message inserts FROM, ACTION, and INFO address
information in the message in form of PLAs and
SICs. The drafter may insert the PLAs either as.
b) Section 3.2.4.1.1.4 g)
Delete this section and re-number the following
sections.
c) Section 3.2.1.2.1.1.1 b)
Insert additional item after item 8):
9) O̲r̲i̲g̲i̲n̲a̲t̲i̲n̲g̲ ̲H̲e̲a̲d̲q̲u̲a̲r̲t̲e̲r̲s̲
Parameter is mandatory. The "FROM" PLA shall
be entered.
Renumbering required from item 9).
8) F̲L̲A̲S̲H̲ ̲R̲E̲C̲E̲I̲P̲T̲
Whether the supervisor specification of FLASH receipt
acknowledgement is required or not, should be on a
site basis and not on basis of each release series.
a) This give rise to the following updates in CPS/210/SYS/0001:
section 3.2.1.6.4 b)
was:
....... flagging for each release series whether
ZGC to be inserted or not.
should be:
....... flagging whether ZGC to be inserted or
not.
b) section 3.2.4.1.1.4 h)
was:
Specify for release positions if acknowledge required
on FLASH messages.
should be:
Specify if acknowledge is required on FLASH messages.
9) T̲E̲R̲M̲I̲N̲A̲L̲ ̲R̲E̲Q̲U̲I̲R̲E̲M̲E̲N̲T̲S̲ ̲F̲R̲O̲M̲ ̲T̲H̲E̲ ̲T̲E̲R̲M̲I̲N̲A̲L̲ ̲P̲O̲S̲I̲T̲I̲O̲N̲
To make the Terminal Position Control section in the
SRS consistent with the Terminal - and Operator Profiles
in the CPS/230/ICD/0002 the following section shall
be moved.
a) section 3.2.4.1.1.4 d) shall be moved and inserted
as section 3.2.4.1.1.5 n)
b) section 3.2.4.1.1.4 h) shall be moved to be part
of section 3.2.4.1.1.3 b)
c) section 3.2.4.1.1.4 u) shall be moved and inserted
as section 3.2.4.1.1.5 a) 13).
10) M̲A̲X̲.̲ ̲2̲0̲0̲ ̲R̲I̲s̲ ̲P̲E̲R̲ ̲M̲E̲S̲S̲A̲G̲E̲
To make section 3.2.1.6.1 c) in the SRS consistent
with 3.4 the following update is recommended:
a) section 3.2.1.6.1 c)
was:
The maximum amount of routing indicators per channel
shall be as specified by the supervisor to max.
200.
should be:
The maximum amount of routing indicators per message
shall be max. 200.
11) P̲R̲O̲C̲E̲D̲U̲R̲E̲S̲ ̲R̲E̲L̲A̲T̲E̲D̲ ̲T̲O̲ ̲F̲L̲A̲S̲H̲ ̲R̲E̲C̲E̲I̲P̲T̲
Inconsistency between section 3.2.1.6.4 c) and 3.2.1.6.4
d) in the SRS.
The period to expect a FLASH receipt message is not
10 minutes, but can vary in time from 2 minutes to
20 minutes.
a) Section 3.2.1.6.4 c) should be changed to read:
"If a receipt message is requested and it is not
received within a specified time period from the
end of an outgoing transmission of the precedence
FLASH message, a warning report shall be generated."
12) S̲P̲E̲C̲I̲A̲L̲ ̲H̲A̲N̲D̲L̲I̲N̲G̲ ̲D̲E̲S̲I̲G̲N̲A̲T̲O̲R̲
To make section 3.4.5.6 in the SRS consistent with
CPS/230/ICD/0003 section 3.4.1 b) the following updates
are recommended:
was:
Special Category Warnings:
N̲a̲m̲e̲ D̲e̲s̲i̲g̲n̲a̲t̲o̲r̲
ATOMAL L
CTS B
EXCLUSIVE P
CRYPTO SECURITY Y
DATE MESSAGE DESIGNATOR D
should be:
S̲p̲e̲c̲i̲a̲l̲ ̲C̲a̲t̲e̲g̲o̲r̲y̲ ̲W̲a̲r̲n̲i̲n̲g̲s̲ D̲e̲s̲i̲g̲n̲a̲t̲o̲r̲
ATOMAL L
EXCLUSIVE P
CRYPTO SECURITY Y
DATA MESSAGE D
13) I̲T̲E̲M̲ ̲R̲E̲F̲E̲R̲E̲N̲C̲E̲ ̲I̲D̲E̲N̲T̲I̲T̲Y̲
The Item Ref. Id. is a 5 digit number in the range
from 00000 to 65535. Please refer to CPS/230/ICD/0001
app. A.
Section 3.2.7.2.1 f) in the SRS need to be updated
to reflect this.
14) S̲T̲A̲T̲U̲S̲ ̲I̲N̲F̲O̲R̲M̲A̲T̲I̲O̲N̲
Transaction Status is named Delivery status in the
CPS/230/ICD/0001. CR recommend to change "Transaction"
to read "Delivery" in section 3.2.4.5 d) 3) of the
SRS.
B EDITORIALS
*************
The following editorials should be updated in CPS/210/SYS/0001
1) p 73 was: DEF. This
should be: DEF, this
2) p 74a was: .... special handling designator
and/or special category warnings
should be: .... special category warnings
...
3) p 78 was: .... addressee(s). in .....
should be: .... addressee(s) in .....
4) p 85 replace: "PLAs" with "RNs" and "RNs"
with "PLAs"
replace: "channel" with "circuit"
5) p 89 replace: "segments" with "sections"
6) p 91a was: Messages with classificaion
CLEAR ....
should be: Messages with CLEAR designation
....
7) p 91a was: Messages of type CLEAR ....
should be: Messages with CLEAR designation
....
8) p 91 a was: .... of Instruction ....
should be: .... of T Instruction ....
9) p 197 was: 3.2.7.1.2.1
3.2.7.1.2.2
3.2.7.1.3
should be: 3.2.7.2.2
3.2.7.2.3
3.2.7.3
10) p 199a was: ... encrypted ATOMAL
should be: ... ATOMAL and encrypted messages
11) p 202 was: 3.2.7.1.2.1
figure 3.2.7.1.2.1
3.2.7.1.2.2
figure 3.2.7.1.2.2
should be: 3.2.7.2.2
figure 3.2.7.2.2-1
3.2.7.2.3
figure 3.2.7.2.3-1
12) p 206 was: 3.2.7.1.3
should be: 3.2.7.3
13) p 207 was: System Catalogue is for the
USER
should be: SYSTEM Catalogue is as for the
USER
14) p 245 was: .... a FSK modem according to
CPS/ICD/004
should be: .... a 600/1200 baud FSK modem.
C DNs FROM PDR
***************
1) S̲P̲E̲C̲I̲A̲L̲ ̲H̲A̲N̲D̲L̲I̲N̲G̲ ̲D̲E̲S̲I̲G̲N̲A̲T̲O̲R̲S̲
Ref: DN STP/65 and Action Item STP/1 from the PDR on
Statistical Package.
a) In accordance with ref., section 3.4.1.1.1 q) will
be updated to read:
The number of special handling designators, which
the system shall recognize, is max. 20.
b) The number of special handling designators, which
can be entered during message preparation, will
be changed from 1 to 2. The 2 entry fields are
each 2 characters long. It will be possible for
the drafter of a message to enter 2 special handling
designators, except for the designator "NAT. EYES
ONLY". In the case, where "NAT. EYES ONLY" shall
be entered, the first entry field shall contain
"EE" and the second field contains a 2 letter acronym
for the nationality.
The change to 2 entry fields for special handling
designators will reflect updates to CPS/230/ICD/0001
and CPS/230/ICD/0002.
2) D̲E̲D̲I̲C̲A̲T̲E̲D̲ ̲P̲T̲P̲
Ref: DN THP/35 and THP/36 from PDR on Traffic Handling
Package.
The MSO shall have the capability to route messages
to the dedicated PTP.
This give rise to the following related updates in
the SRS:
a) Section 3.2.1.6.1 e)
was:
If no RI fulfils classification requirements the
message shall be routed to the dedicated PTP.
should be:
If no RI fulfils classification requirements the
message shall be routed to the MSO, who may then
choose to route it to the dedicated PTP or insert
CLEAR before entering the message for routing.
b) Section 3.2.4.1.1.3 a) 12)
was:
Specify terminal (line identification) for distribution
of encrypted incoming messages and outgoing messages
where no channel of proper authorization can be
found.
should be:
Specify identification for dedicated PTP.
c) The following text will replace section 3.2.4.2.3:
3̲.̲2̲.̲4̲.̲2̲.̲3̲ ̲R̲o̲u̲t̲i̲n̲g̲ ̲t̲o̲ ̲P̲T̲P̲
The MSO shall have the capability to queue messages
being subject to routing indicator assignment to
the dedicated PTP.
d) The following sentence will be inserted as section
3.2.4.2 a) 1):
- Route to Punch
3) G̲R̲O̲U̲P̲ ̲C̲O̲U̲N̲T̲ ̲A̲S̲S̲I̲G̲N̲M̲E̲N̲T̲
Ref: DN 35/THP and 30/THP from the PDR on Traffic Handling
Package.
The MSOs capability for group count assignment shall
be removed.
The following sections shall be deleted:
a) Section 3.2.1.5.3 d) shall be deleted.
b) Section 3.2.4.2 m) 2) shall be deleted.
c) Section 3.2.4.2.3 shall be deleted.
4) H̲A̲N̲D̲L̲I̲N̲G̲ ̲O̲F̲ ̲C̲R̲Y̲P̲T̲O̲ ̲S̲E̲C̲U̲R̲I̲T̲Y̲
Ref. DN THP/36 from PDR on Traffic Handling Package.
a) The following section will be inserted as section
3.2.1.6.5 in the SRS:
H̲a̲n̲d̲l̲i̲n̲g̲ ̲o̲f̲ ̲C̲R̲Y̲P̲T̲O̲ ̲S̲E̲C̲U̲R̲I̲T̲Y̲
Messages of special handling type CRYPTO SECURITY
shall except when entered as complete message from
PTR be queued to the dedicated PTP for encryption
and shall not be subject for local distribution.
5) P̲U̲N̲C̲H̲E̲D̲ ̲P̲A̲P̲E̲R̲ ̲T̲A̲P̲E̲
Ref: DN THP/31 from the PDR on Traffic Handling Package.
a) According to ref.:
section 3.4.5.2.2 in the SRS:
was: .... succeeded by 20 cms blank tape ....
should be: .... succeeded by 30 cms blank
tape ....
6) E̲R̲R̲O̲R̲ ̲H̲A̲N̲D̲L̲I̲N̲G̲ ̲P̲T̲R̲
Ref: DN THP/21 from the PDR on Traffic Handling Package
a) According to ref. the following section will be
inserted as section 3.2.1.4 c) in the SRS.
If a message entered via a PTR has not been properly
terminated with EOTF, a warning report shall be
forwarded to the supervisor and the message discarded.
D ACTION ITEMS
***************
1) M̲A̲X̲I̲M̲U̲M̲ ̲S̲C̲D̲s̲ ̲I̲N̲ ̲S̲D̲L̲s̲
Maximum two action and ten info SCDs in one SDL.
a) Section 3.4.1.5 u) will be updated to read:
One SDL above includes composition of max. two
action and max. ten info SCDs.
2) S̲P̲E̲C̲I̲A̲L̲ ̲H̲A̲N̲D̲L̲I̲N̲G̲ ̲D̲E̲S̲I̲G̲N̲A̲T̲O̲R̲ ̲O̲N̲ ̲E̲X̲T̲E̲R̲N̲A̲L̲ ̲C̲H̲A̲N̲N̲E̲L̲S̲
Ref: DN THP/6 and action item THP/4 from PDR on Traffic
Handling Package, dated 24th June 1981.
Special Handling Designator does not apply to external
channels.
a) Special handling (warning) category will be removed
from the sections 3.2.1.6.1 f) and k).
3) L̲I̲N̲E̲ ̲P̲R̲I̲N̲T̲E̲R̲
Line printer shall be removed and replaced by medium
speed printer on the following pages in the SRS:
page 25 figure 3.1-1
page 143 line 22
page 144 figure 3.2.4-1
page 177 line 4
page 220 line 5 deleted
page 236 line 24
page 244 section 3.4.1.10.5 deleted
page 262a line 15
page 291 line 24
4) S̲O̲F̲T̲W̲A̲R̲E̲ ̲D̲O̲C̲U̲M̲E̲N̲T̲A̲T̲I̲O̲N̲
Ref: MOM no 8, dated 24-28 August 1981 para. 2.
It was agreed between CR and SHAPE that the As-built
SW documentation should be provided at two levels:
- The System Design Documentation
- The Detailed Design Documentation
This requirement is an update of CPS/210/SYS/0001,
sections 3.6.9.2 - 3.6.9.5, as follows:
a) Section 3.6.9.2:
Software shall be documented in two levels:
- System Design Specification
Sys. Eng. CDRL No. 07
- Detailed Design Specification,
Software Development CDRL No. 05.
b) Section 3.6.9.4 shall be included in section 3.6.9.3
(a).
c) Section 3.6.9.5 shall be re-numbered to 3.6.9.4
and the section title shall be changed to "Detailed
Design Specification".
5) E̲X̲E̲R̲C̲I̲S̲E̲ ̲S̲I̲C̲ ̲R̲A̲N̲G̲E̲
Ref: Action item MDP/1 from the PDR on Message Distribution
Package.
In accordance with action item the following line will
be deleted from section 3.12.3.2 2) in the CPS/230/ICD/0003:
"BE(X) - BZ(X) neglect these SICs"
6) I̲N̲S̲I̲G̲N̲I̲F̲I̲C̲A̲N̲T̲ ̲C̲H̲A̲R̲A̲C̲T̲E̲R̲S̲
Ref: Action item IOC/4 from the PDR on the I/O Control
Package.
The action was.
Update SRS to reflect the following:
The ITA No. 2 characters LS and FS as well as the ITA
No. 5 characters, SI and SO are not significant for
CAMPS internal message handling and can, therefore,
be deleted before analysis of all incoming messages.
a) The above text will be inserted as section 3.2.2.2
m) in the SRS. Section 3.2.2.2 m) will be renumbered
to 3.2.2.2 n).
7) E̲D̲I̲T̲O̲R̲I̲A̲L̲S̲ ̲T̲O̲ ̲T̲E̲M̲P̲E̲S̲T̲ ̲A̲C̲C̲E̲P̲T̲A̲N̲C̲E̲
Ref: a) CAMPS Log No. 302, dated 14th August 81
b) CAMPS Log No. 279, dated 13th July 81
In accordance with ref a) and b) the following editorials
will be updated:
a) section 3.4.5.1 b 2) second line:
was: certificate
should be: certification
b) section 3.4.5.1 b) 2) 7th line:
was: .... that the
should be: .... that the EMI
E CLARIFICATIONS
*****************
1) R̲E̲T̲R̲I̲E̲V̲A̲L̲
Ref a) Action item SAR/3, from the PDR on Storage
and Retrieval Package
b) Telex CPS/101/tlx/0328a
CR recommend to change the retrieval criteria for the
cases when to get a single item display and when to
get a catalogue display.
The criteria was:
If a TOC (or DTG) was specified in the retrieve key
then a single item was displayed and it was the first
item found which fit the key.
If a TOC window was specified then a catalogue was
displayed.
The new criteria should be:
If several items fit the specified retrieve key, then
a catalogue display is returned. The catalogue display
is limited to only contain items from one volume.
If only one item fits the retrieve key, then a single
item is returned.
This change give rise to the following updates in CPS/210/SYS/0001:
a) Section 3.2.7.2 g) will be changed to read.
The execution of a retrieval request may result
in a presentation of either catalogue information
or the retrieved item depending on whether several
or just one item meet the search request. The calatogue
display will only contain information from one
volume.
b) Section 3.2.7.2 j) will be deleted.
c) Section 3.2.7.1.2.2 1) will be deleted. It is correct
but redundant information.
d) The figures 3.2.7.1.2.1-1 and 3.2.7.1.2.2-1 will
be updated accordingly. The field "result" will
be updated to reflect the 3 cases:
- catalogue display
- item display
- not found try again
depending on whether several, one or no items meet
the retrieval key.
The change give rise to the following updates in
CPS/230/ICD/0001:
e) Section 3.11.1.2
was:
In the case where a specific Time of Occurrence
(TOC) is specified, then the first item which fits
the reference will be retrieved and presented.
If the reference cannot be found then error message
27 will be displayed in the response line.
In the case where a TOC window is specified, then
the items which satisfy the references are presented
on the form of a catalogue.
should be:
In the case where several items fit the specified
retrieve key, then a catalogue display is returned.
In the case where one item fits the retrieve key,
then a single item display is returned.
In the case where no item fits the retrieve key,
then error message 27 will be displayed in the
response line.
f) Section 3.11.7
was:
If a time window is specified then a catalogue
of these items within the time window will be presented.
should be:
If a time window is specified and several items
meet the retrieval key, then a catalogue of these
items within the time window will be presented.
2) S̲T̲A̲T̲I̲S̲T̲I̲C̲S̲
The statistical requirements listed in the SRS section
3.2.6 need to be clarified. CR recommend the following
updates:
a) Section 3.1.1.3.5 b) will be changed to read:
A special statistic is complied for messages rejected
for manual editing including the total number of
rejected messages.
b) Section 3.1.1.3.5 c)
the last sentence was:
.... Further for distributed messages the average
and maximum number of terminals included in the
distribution is recorded as well as the number
of messages which required supervisory assistance.
should be:
.... Further for distributed messages the average
and maximum number of terminals included in the
distribution is recorded.
c) Section 3.1.1.3.5 d)
was:
.... daily and month's basis
should be:
.... daily, weekly, and monthly basis
d) Section 3.1.1.3.5 e)
was:
.... day and current week
should be.
.... day and week
e) Section 3.2.6.1.1
was:
- current day for each complete hour from 0001
hours
- previous day for each hour from 0001 hours
to 2400
- each week with a predefined starting day of
last 4 complete weeks.
should be:
- current day for each complete hour from 0001
hours to 2400 hours
- previous days, upto 7, from a predefined starting
day.
- previous weeks, upto 4, with starting day defined
as above.
- previous month, with starting day as defined
above. A month is 4 complete weeks.
f) Section 3.2.6.2 will be updated to read as follows:
The system shall record hourly the storage occupancy
with respect to messages being processed. The occupancy
shall be defined as a percentage of used sectors
out of total number for use.
The occupancy is maintained as specified in 3.2.6.1.1.
The areas in question are:
- short term storage
- intermediate storage
Storage occupancy shal be recorded periodically
and shall be printed on request. The print-out
shall be at the supervisor printer assigned statistics
print.
g) Section 3.2.6.3 will be updated to read as follows:
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.
The availability shall be recorded and maintained
as specified in section 3.2.6.1.1.
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.
h) A new section will be inserted as section 3.2.6.6
with the following text:
S̲t̲a̲t̲i̲s̲t̲i̲c̲s̲ ̲P̲r̲i̲n̲t̲o̲u̲t̲
The statistics queued each day at 24.00 hour for
printout at the supervisor's printer assigned "statistics
print" consist of 1 out of 3 components:
- daily statistics
- weekly statistics
- monthly statistics
During the week, daily statistics are queued for
print, at the end of a 7 day period the weekly
statistics are queued and at the end of a 4 week
period the monthly statistics are queued.
i) A new section will be inserted as section 3.2.6.6.1
with the following text:
D̲a̲i̲l̲y̲ ̲S̲t̲a̲t̲i̲s̲t̲i̲c̲s̲ ̲C̲o̲n̲t̲e̲n̲t̲s̲
Contents of daily statistics are:
- 24 one hour statistics
- 1 daily statistics
- 1 previous daily statistics
j) A new section will be inserted as section 3.2.6.6.2
with the following text:
W̲e̲e̲k̲l̲y̲ ̲S̲t̲a̲t̲i̲s̲t̲i̲c̲s̲ ̲C̲o̲n̲t̲e̲n̲t̲s̲
Plus the daily statistics as listed above, the
following information is included:
- 7 one day statistics
- 1 weekly statistics
- 1 previous weekly statistics
k) A new section will be inserted as section 3.2.6.6.3
with the following text:
M̲o̲n̲t̲h̲l̲y̲ ̲S̲t̲a̲t̲i̲s̲t̲i̲c̲s̲ ̲C̲o̲n̲t̲e̲n̲t̲s̲
Plus the daily and weekly statistics as listed
above, the following information is included:
- 4 one weekly statistics
- 1 monthly statistics
- 1 previous monthly statistics
3) N̲O̲ ̲T̲E̲L̲E̲P̲R̲I̲N̲T̲E̲R̲ ̲A̲S̲ ̲P̲T̲P̲
Ref a) Telex from CR to SHAPE
CPS/101/TLX/0332, dated 22nd September 1981
b) Telex CAMPS LOG No. 342, dated 20th September
1981.
As agreed CAMPS shall not support low speed teleprinters
operating as Paper Tape Punch for production of ACP127
message tapes.
This give rise to the following updates in CPS/210/SYS/0001:
a) Section 2.3
A new section will be inserted as h)
PTP - Paper Tape Punch means dedicated Paper Tape
Punch.
b) Section 3.2.1.6.1 j)
This section will be deleted.
Note: The MSO has the possibility of routing
outgoing messages presented for him for
routing assignment to the dedicated PTP.
c) Section 3.2.4.1.1.3 a) 3) third subparagraph will
be deleted.
d) Section 3.2.3.1 b) 3)
PTP will be removed.
e) Section 3.2.3.1 f) 2) will be changed to read:
One Device type may be specified. Possible device
types shall be: Medium Speed Teleprinters (ROP),
Low Speed Teleprinters (ROP), Low speed Teleprinter
used as PTR and OCR.
f) Section 3.2.4.1.1.7 b)
The section will be replaced with:
The OCR, PTR/PTP, and low speed teleprinters operating
as PTR are used as described in 3.2.1.4.
g) Section 3.2.4.1.1.7 e)
PTP will be removed.
h) Section 3.2.4.1.1.7 m)
The section will be replaced with:
Specify to the CAMPS central equipment for each
low speed teleprinter used as PTR to
- Either allow input of complete messages
- or accept no input (logically disconnected)
4) D̲A̲T̲A̲ ̲M̲E̲S̲S̲A̲G̲E̲S̲
As a consequence of previous updates (ref. MOM no.
5 App. B para. 1, dated 9-13 February 1981). Data messages
are entered as normal messages.
a) Updates to Figure 3.2.1.1-2 in the SRS:
The row named Data Message shall be updated:
was:
ENTRY AS COMPLETE
should be:
ENTRY AS NORMAL MESSAGE
was:
No
should be:
1. YES
2. NO
b) Updates to section 3.2.1.5
was:
Figure 3.2.1.5-1 provides in a short form the details
of conversion for all types. Operational messages
with encrypted text and data messages are entered
as complete messages and shall except for certain
checks and replacements not be subject to conversion
processing. Refer to section 3.2.1.5.3 for details.
should be:
Figure 3.2.1.5-1 provides in a short form the details
of conversion for all types. Operational messages
with encrypted text are entered as complete messages
and shall except for certain checks and replacements
not be subject to conversion processing. Refer
to section 3.2.1.5.3 for details.
5) C̲O̲N̲V̲E̲R̲S̲I̲O̲N̲ ̲O̲F̲ ̲M̲E̲S̲S̲A̲G̲E̲S̲
The check that the exercise indication is in accordance
with the entered SICs is performed, when the drafter
prepare his message and not at conversion of the message
to ACP127.
a) CR recommend to move the requirement section 3.2.1.5.1
a) 4) in the SRS to be part of the CPS/230/ICD/0001
section 3.4.1.14.
b) Section 3.2.1.5.1 a) 6) will be changed:
was:
All special handling designators of FL4 shall be
matched to the information in FL12a for consistency.
should be:
All special handling designators in FL4 shall be
inserted as special category warnings in FL12a.
6) Withdrawn.
7) E̲N̲D̲-̲O̲F̲-̲T̲R̲A̲N̲S̲M̲I̲S̲S̲I̲O̲N̲ ̲F̲U̲N̲C̲T̲I̲O̲N̲
End-of-transmision function cannot both be Non-standard
and detected.
a) Therefore, change of section 3.2.2.2 e) 2) is recommended:
was:
Non-standard end-of-transmission sequence
should be:
Missing end-of-transmission sequence.
8) Q̲U̲E̲U̲E̲D̲ ̲F̲O̲R̲ ̲M̲E̲S̲S̲A̲G̲E̲ ̲D̲I̲S̲T̲R̲I̲B̲U̲T̲I̲O̲N̲
a) For clarity, change subsection in section 3.2.2.3
j) 2) in the SRS:
was:
- special handling designators and/or special
category warnings except cases f) and g) above,
but including messages with more than one of
these.
should be:
- special handling designators of type P and
Y, the special category warning National Eyes
Only and messages including more than one special
handling designator/special category warning.
b) For clarity, change section 3.2.1.2.4 j) in the
SRS:
was:
.... messages with special handling designators
and/or special category warnings .....
should be.
.... messages with special category warnings ....
9) A̲S̲S̲O̲C̲I̲A̲T̲E̲D̲ ̲S̲C̲D̲s̲ ̲F̲O̲R̲ ̲C̲R̲I̲S̲I̲S̲ ̲T̲R̲A̲F̲F̲I̲C̲
Refer to E 32 in this ECP.
10) M̲S̲O̲ ̲R̲E̲-̲R̲O̲U̲T̲E̲ ̲O̲F̲ ̲M̲E̲S̲S̲A̲G̲E̲S̲
For completeness of the MSO function the following
feature will be available for the MSO:
Direct an incoming garbled message for outgoing
message processing.
a) The following requirement will be inserted
in the SRS as section 3.2.4.2.1 e).
"If the message contains external RIs in format
line 2 when it is returned from the MSO then
the system will transmit the message to the
external RIs like outgoing messages entered
as complete".
b) Section 3.2.2.3 d)
Contents in brackets will be deleted.
11) O̲P̲E̲R̲A̲T̲I̲N̲G̲ ̲S̲I̲G̲N̲A̲L̲
Ref: MOM 13, dated 1-2 Oct. 1981.
To ensure correct ACP 127 conversion of the entered
message handling instructions during message preparation
CR will recommend the following proposal:
An entry field of 50 characters will be available in
the message preparation formats for entry of message
handling instructions. The drafter may enter as many
MHIs (3 character code + parameter) as wanted in free
format within the 50 character field. No check will
be performed during entry. During ACP 127 conversion
the MHI string will be used as is to build format line
5. Automatic inserted operating signals (e.g. ZGZ)
will go into format line 4.
a) Section 3.2.1.2.1.1.1 b) 13) will be changed to
read:
Message handling instructions consisting of a 3
letter group plus a parameter can be entered in
free format. The message handling instruction entry
string is limited to 50 characters to allow conversion
into format line 5 of ACP 127. No validation is
performed.
b) Section 3.2.1.5.1 6) will be updated to read.
Operating signals entered as message handling instructions
shall be inserted in format line 5.
c) These changes will also be reflected in CPS/230/ICD/0001
and CPS/230/ICD/0002.
12) I̲N̲C̲O̲M̲I̲N̲G̲ ̲M̲E̲S̲S̲A̲G̲E̲S̲ ̲F̲R̲O̲M̲ ̲P̲T̲R̲
Ref: ECP No. 10, CN No. 5
The update of section 3.2.1.4.2 b) in the SRS related
to ECP no. 10, CN no. 5 is wrong.
As stated in the ECP entry from Non-dedicated PTR is
outgoing messages only. Therefore, section 3.2.1.4.2
b) shall be deleted.
Note: It is correct that incoming messages shall
be entered in full ACP 127 format as it is
stated in section 3.2.1.4.3.
13) P̲R̲E̲E̲M̲P̲T̲I̲O̲N̲ ̲O̲N̲ ̲E̲X̲T̲E̲R̲N̲A̲L̲ ̲C̲H̲A̲N̲N̲E̲L̲S̲
Ref a) Subsystem specification of the telegraph automatic
relay equipment Vol. II of IV CAMPS Log. no
81, page 10-42, section 10.3.1.10.2 c)
b) Record of technical details discussed at TARE/CAMPS
Interface meeting held at SHAPE on 28th August
1980. Doc. no. 31, issue 1, date 4th December
1980, page 9; question no. 20.
As stated in ref. a) and b) NICS TARE does not pre-empt
transmission on medium speed channels, i.e. CAMPS NICS
TARE channels. The same rules must apply to CAMPS.
In that respect it is of low value to pre-empt transmission
of messages on CCIS/SCARS channels with high transmision
speed.
In accordance with the above arguments CR recommend
to insert a new section in the SRS as section 3.2.1.6.2
d) with the following wording:
"Premature termination of a transmission will only
be performed by CAMPS at TRC/Point-to-Point, SCARS
and ACCIS.
14) M̲A̲X̲I̲M̲U̲M̲ ̲L̲E̲N̲G̲T̲H̲ ̲O̲F̲ ̲P̲L̲A̲
The maximum length for an PLA should be 54 characters
(instead of 60) so the following case can be handled
correct.
Generation of FL8 in ACP 127 conversion
INFO(sp) RI/ PLA
char: 4 + 1 + 9 + 1 + 54 = 69 char.
The max. length for an RI is 9 char.
This give rise to the following updates:
Change SRS section 3.4.1.5 d), Change CPS/230/ICD/0001
p. 141 and all formats containing PLA fields. Change
CPS/230/ICD/0002 app. A and all formats containing
PLA fields.
15) S̲E̲C̲T̲I̲O̲N̲I̲N̲G̲ ̲O̲F̲ ̲M̲E̲S̲S̲A̲G̲E̲
Ref: Telex CPS/101/TLX/0333
The suggested update in ref. to section 3.2.1.5.1.
d) 6) second subparagraph in the SRS did not reflect
a correct update.
The section will be updated to read.
Each section shall include as first part of the section,
the full header plus format lines 12a, 12b, 12c (if
applicable) followed by the section number as a new
physical line and followed by format line 12d (if applicable)
and 12e, all in plain language.
16) M̲D̲C̲O̲ ̲D̲I̲S̲P̲L̲A̲Y̲ ̲O̲F̲ ̲D̲A̲T̲A̲ ̲M̲E̲S̲S̲A̲G̲E̲S̲
Ref: Action Item IOC/2 from the PDR on I/O Control
Package.
CR cannot see any reason for only displaying the header
part of a data message, now when all data messages
can be displayed. (Non-printable characters will be
removed by dummy characters, see ref.)
a) The following sentence will be deleted from section
3.2.2.3.4 in the SRS:
"When data messages are presented to the MDCO,
only the header part shall be displayed"
b) As in accordance with ref. the following sentences
will be inserted in the SRS section 3.2.2.3.4:
Data messages will be treated as garbled if they
contain non-printable characters.
* The non-printable characters will be displayed
as the sign (monkey tail) when the garbled message
is presented for the MSO.
The system will add (CR) and (LF) to separate lines
of 69 (or 80) characters during processing of incoming
data messages. In addition the message will be
sent to MSO for garble correction. This apply to
all internal and external incoming data messages
(though outgoing messages are not sent to MSO).
17) V̲Z̲C̲Z̲C̲ ̲I̲N̲ ̲I̲N̲P̲U̲T̲ ̲F̲R̲O̲M̲ ̲P̲T̲R̲
Ref a) Telex CPS/101/TLX/0328a dated 17. September
1981.
b) Telex CAMPS Log No. 333 dated 22. September
1981.
As stated in ref a) and b) "VZCZC (CR)(CR)(LF)" shall
always be present as a dummy line before FL2 of an
outgoing message entered via a PTR.
The following changes to the SRS reflect the new requirement:
a) Section 3.2.1.4.2 a) 1)
was:
Format line 1 is missing and shall be inserted
by CAMPS of transmission.
should be:
Format line 1 is missing (i.e. consist of VZCZC
(CR)(CR)(LF)) and shall be inserted by CAMPS before
transmission.
b) Section 3.2.1.4.3
was:
These messages will not contain format line 1.
should be.
These messages will not contain format line 1,
however, the sequence "VZCZC(CR)(CR)(LF)" will
be present as a dummy line before FL2.
18) X̲ ̲C̲H̲A̲R̲A̲C̲T̲E̲R̲S̲ ̲A̲F̲T̲E̲R̲ ̲B̲T̲
Ref a) Telex CPS/101/TLX/0213, dated 11th March 1981
b) Answer from SHAPE to that telex CAMPS Traffic
Handling Clarifications dated 30th March 1981.
The update of CPS/230/ICD/0003 related to point 2)
c) of ref. a) and b) was incorrect.
The up to 5 characters followed BT and before (EOLF)
can only be LF or FS.
a) Section 3.11.3 will be changed to read.
This format is mandatory in cases where the message
contains the format line 5. In such cases, when
it is not present, the message shall be rejected
to the message service position. The format line
shall be assumed to be present, if the sequence
"BT(X)(EOLF)" is detected where X represents either
(LS) or (FS). The sequence "X", if present, shall
not be transmitted to receiving terminals.
19) P̲L̲A̲s̲ ̲A̲S̲S̲O̲C̲I̲A̲T̲E̲D̲ ̲T̲O̲ ̲R̲I̲ ̲I̲N̲ ̲F̲L̲2̲
RIs are only associated to CAMPS and not associated
to Headquarters. Therefore, CR recommend to change
section 3.2.2.3 e) of the SRS:
was:
In case of relevant routing indicators in format line
2 the PLAs associated to these routing indicators in
format lines 7 and 8 (plus PLAs in AIGs, any single
addressee PLA and ZEN PLAs) shall be compared to PLAs
of the associated headquarters.
should be.
In case of relevant routing indicators in format line
2 the PLAs in format lines 7 and 8 (plus PLAs in AIGs,
any single addressee PLA and ZEN PLAs) shall be compared
to PLAs of the associated headquarters.
20) U̲S̲E̲ ̲O̲F̲ ̲Z̲E̲N̲
Ref a) Telex CPS/101/TLX/0336, dated 24th September
1981.
b) Telex CAMPS Log no. 340 dated 29th September
1981.
In accordance with ref. a) and b) the following changes
to the SRS apply:
a) Section 3.2.1.5.1 b) 2) the following will be added:
"- PLAs preceded by "ZEN" (refer to section 3.2.1.6.3)
shall not be considered in the RI selection
procedure"
b) Section 3.2.1.6.3 the following will be inserted:
The ZEN prosign can be inserted in front of a PLA
in one of the following cases:
a) during preparation the user can enter ZEN in
front of a PLA.
b) during RI assigment the MSO can enter ZEN in
front of a PLA.
c) when a local PLA is specified in format A the
system will insert a ZEN in front of that before
transmisison.
c) Section 3.2.1.2.4 d) the following will be added.
"ZEN PLAs as specified in 3.2.1.6.3 will be displayed
with ZEN in front of the PLA"
d) Figure 3.2.1.5-3 will be updated.
Supervisor specified ZEN PLAs do not exist anymore
(Refer to ECP no. 10 CN 13)
e) Section 3.2.2.3 e) the following sentence will
be added:
Incoming messages containing a local PLA preceded
by a ZEN shall be distributed normally.
21) S̲P̲E̲C̲I̲A̲L̲ ̲S̲I̲C̲s̲
CR recommend to add a description of special SICs and
exercise SICs in format line 12b.
The following text will be added to CPS/230/ICD/0003,
section 3.12.1.2 b):
If the special handling designator SIC AAA or one of
the SICs ABA, ACA, and ADA is specified this SIC shall
be placed in position 1 of the possible 3 SIC.
If an exercise SIC is specified this SIC shall be placed
in position 1 or 2. If in position 2 the preceding
SIC shall be of type AAA, ABA, ACA, or ADA.
The exercise SIC must be followed by at least one SIC.
Exercise SICs are in the range AE(X) to AZ(X).
22) S̲U̲P̲E̲R̲V̲I̲S̲O̲R̲ ̲V̲D̲U̲ ̲S̲W̲I̲T̲C̲H̲-̲O̲V̲E̲R̲
The effect on the active supervisor position of issuing
the special addressing command from the inactive supervisor
position shall be similar to sign-off and not similar
to cancel as stated in section 3.2.4.1.
This is caused by the fact that it is not possible
to have 2 supervisor processes.
Section 3.2.4.1 in the SRS will be updated accordingly.
23) P̲R̲I̲N̲T̲/̲S̲T̲O̲R̲E̲ ̲O̲F̲ ̲R̲E̲P̲O̲R̲T̲S̲
Ref: Telex CAMPS Log no. 356, dated 12. October 1981
Reports can either be printed or stored, not both.
A warning will be given to the supervisor when the
outstanding report file reaches a preset threshold.
This give rise to the following updates in the SRS:
a) Section 3.2.4.4.1 b) will be changed to read:
Each report shall as specified be printed out or
stored in the outstanding report file.
b) Section 3.2.4.4.1 f) will be expanded with:
(Refer to section 3.2.4.4.3 a)).
24) A̲B̲B̲R̲E̲V̲I̲A̲T̲E̲D̲ ̲P̲L̲A̲I̲N̲D̲R̲E̲S̲S̲ ̲M̲E̲S̲S̲A̲G̲E̲
Incoming abbreviated plaindress message will be routed
to the MDCO for distribution determination. That is
because the message does not include PLAs and due to
the fact that there is no one to one correspondence
between RIs and PLAs.
When abbreviated plaindress messages are displayed
for the user the TO and FROM RIs will be shown (RIs
from format line 2 and 3).
To reflect this, the following updates to the SRS will
be made:
a) Section 3.2.2.3 j) 2) the following sentence will
be added:
- incoming abbreviated plaindress messsages for
distribution assignment.
b) Section 3.2.2.3.1 b) 6) will be inserted as a new
section with the following text:
6) The TO and FROM RIs (RIs from format line 2
and 3) will be displayed instead of the missing
PLAs for messages of type abbreviated plaindress.
25) L̲O̲W̲ ̲G̲A̲R̲B̲L̲E̲D̲ ̲M̲E̲S̲S̲A̲G̲E̲S̲
The requirement in SRS section 3.2.2.3 h) stating:
"A message of precedence FLASH or IMMEDIATE, which
is sufficiently free for garble to allow conversion
into format E1 for distribution, shall be distributed
automatically."
is non-programmable. The requirement is to weak and
allow many interpretations. CR will go for; either
is a message garbled or it is not garbled, i.e. a graduation
of how much a message is garbled shall not lead to
different actions.
a) Therefore, CR recommend to delete the requirement
in SRS section 3.2.2.3 h).
26) R̲E̲L̲E̲A̲S̲E̲ ̲O̲F̲ ̲E̲N̲C̲R̲Y̲P̲T̲E̲D̲ ̲M̲E̲S̲S̲A̲G̲E̲S̲
Encrypted outgoing messages shall not be automatically
released. This had been done before it was punched
for off-line decryption.
a) Section 3.2.1.4.2 a) 2) in the SRS will be changed
to read:
Release serial number and time of release shall
be present, but will be replaced at conversion,
except for encrypted messages. (For details on
conversion refer to section 3.2.1.5).
27) G̲R̲O̲U̲P̲ ̲C̲O̲U̲N̲T̲ ̲I̲N̲ ̲F̲L̲1̲4̲
CAMPS will always place the group count in format line
14 for outgoing messages and messages punched for off-line
decryption.
a) The following sentence will be added to section
3.2.1.4.3 in the SRS:
Outgoing messages and messages punched for off-line
decryption will always contain the group count
in format line 14.
28) S̲I̲N̲G̲L̲E̲ ̲A̲D̲D̲R̲E̲S̲S̲E̲D̲ ̲M̲E̲S̲S̲A̲G̲E̲
Ref.: ECP No. 10, CN 3 b)
At conversion of an outgoing single addressed message
the PLA in FL7 or FL8 shall not be preceded with a
RI.
a) The following text will be inserted in the SRS
as section 3.2.1.5.1 a) 7).
The PLA in format line 7 or 8 shall not be preceded
with a RI for outgoing single addressed messages.
29) P̲A̲G̲I̲N̲G̲/̲S̲E̲C̲T̲I̲O̲N̲I̲N̲G̲
Paging/sectioning shall not lead to a page/section
only containing the format lines 13, 14, and 15.
a) Section 3.2.1.5.1 d) 8) will be inserted as a new
section in the SRS with the following text:
If paging/sectioning of a message, following the
paging/sectioning rules, will lead to a page/section
only containing format lines 13, 14, and 15, then
the paging/sectioning shall not be done and FL13,
14, and 15 shall be part of the previous page/section.
30) R̲E̲A̲D̲D̲R̲E̲S̲S̲A̲L̲ ̲O̲F̲ ̲A̲B̲B̲.̲ ̲P̲L̲A̲I̲N̲D̲R̲E̲S̲S̲ ̲M̲E̲S̲S̲A̲G̲E̲
It is not possible to readdress messages which do not
contain Plain Language Addresses.
a) This clarification reflects update to section 3.2.4.1.3.4
in the SRS. This section will be changed to read:
The supervisor shall be able to readdress messages
after retrieval. Readdressal pertains only to messages
with PLA. Refer to CPS/230/ICD/0002.
b) Furthermore, an update to CPS/230/ICD/0003 section
3.5.3 f) 3) a):
was:
The corresponding action is queueing to supervisor.
should be:
The corresponding action is queueing to supervisor
if SIC = SVC, otherwise queuing to the MDCO.
31) T̲-̲I̲N̲S̲T̲R̲U̲C̲T̲I̲O̲N̲S̲
Ref: a) CAMPS Log No. 362, dated 15. Oct. 1981
b) CPS/101/tlx/363
According to ref. a) and b) the following changes to
the requirements will be done:
CPS/230/ICD/0003, secton 3.4.1 d):
The section will be changed to read:
Some messages may include transmission instructions
in this format line. These instructions shall commence
at the start of a new printing line and shall be of
the form "RI 0(sp)T(sp)RI 1(sp)RI 2(sp)....(sp)RIN",
where N can be from 1 to 5. The RI 0 shall also appear
in format line 2, if CAMPS shall do the relaying. Maximum
three such T-instruction lines may exist. The instruction
signifies that CAMPS related to RI 0 shall pass the
message on to the stations indicated by RI 1 through
RI N. If RI 0 is repeated after the sequence (sp)T(sp),
this indicates internal distribution a̲n̲d̲ onward relaying
according to RI 2 through RI N. In case of instruction
"T" alone (no routing indicators) the message shall
be queued for message servicing (before relaying).
CPS/210/SYS/0001, section 3.2.4.2.2:
A new section will be inserted with the following text:
The message servicer shall be capable of entering/changing
upto 3 lines with T-instructions each line with max.
5 RIs after the "T".
32) S̲I̲C̲s̲ ̲A̲N̲D̲ ̲S̲C̲D̲s̲
Ref MOM 13, dated 1-2. October 1981
a) Section 3.4.1.5 updates:
s) Store and recognize max 3900 SICs of each 3
or 2 characters.
t) Storage of a total max. of 800 Standard Distribution
Lists serving 8 HQs. Included shall be SDLs
for normal, exercise and crisis traffic.
w) For each SCD above store an identification
of 3 characters (Refer 3.2.3.1 d) 2) and f)
3))
b) Section 3.2.3.1 f), the following sentence will
be deleted:
- Staff Cell Designators (only applicable for
ROP, when messages are sent directly)
c) Section 3.2.3.1 f) 3) will be deleted.
d) Figure 3.2.2.3-2 update
Reflects the output to Stand Alone Printer.
e) Section 3.2.4.1.1.3 a) 6) update:
One SIC defined by all three letter may identify
a SDL. A group of SICs defined by the first two
letters may also reference a SDL. A two letter
SIC may co-exist with any derived 3 letter version.
f) Section 3.2.2.3.1 a) update:
Insert after 3)
4) If a 3 letter SIC exists in the SIC table with
a non blank SDL-number, which matches one of
the SICs in the message, then this SDL will
be used for distribution. When no 3 letter
SICs as specified above exist, then a 2 letter
SIC will be searched and used if available.
g) Change section 3.2.2.3.1 a) 3)
There will be a separate set of pointers to the
SDLs for Normal, Exercise, and Crisis. For Exercise
and Crisis the SICs may be the same as for normal
distribution. The criteria for selection of Exercise
is FL12c. The SIC denoting the exercise nature
shall be ignored. Crisis distribution replaces
normal distribution by means of a switch.
h) 3.2.4.1.1.3 a) 7) should be changed to read:
S̲D̲L̲ ̲T̲a̲b̲l̲e̲
Set of SCDs (each set called a SDL) referenced
by the SIC tables. Ordering of the table in SDL-types
is the responsibility of the supervisor.
i) A new section will be inserted as section 3.4.1.5
ZC):
Each terminal position can be assigned up to 5
SCDs. The rest of the 400 SCDs can be allocated
without restrictions to Stand Alone Printers.
j) Section 3.2.4.1.1.3 a) 8) first para will be changed
to read:
- Terminal designator associated to the staff
cell or Device designator associated to stand
alone printers.
33) L̲O̲C̲A̲L̲ ̲R̲I̲s̲
Ref: MOM 13, dated 1-2. October 1981
a) Section 3.2.2.3 update:
Insert additionally after d):
e) The detection of a T-instruction in format
line 4 shall lead to automatic relay if associated
to local RI except for RIs for SCARS II and
CCIS .
b) Renumbering required
c) Section 3.4.1.5 update:
r) Store and recognize 50 PLAs for headquarters
served by one CAMPS site; only the first 20
characters of the PLAs shall be stored.
s) The number of RIs to be recognized locally
at message reception shall be 15 including
RIs for SCARS II for CCIS relaying.
d) Figure 3.2.2.3-2 update:
Update to reflect relay to SCARS II and CCIS.
e) Section 3.2.4.1.1.3 a) 3)
was:
- Per RI the associated channel designator of
the channel to be used when routing outgoing
messages.
should be:
- Per RI the associated circuit id to be used
when routing outgoing messages.
f) Section 3.2.4.1.1.3 a) 4)
was:
This table contains all RI's for Headquarters served
by this CAMPS.
should be:
This table contains all RI's for Headquarters served
by this CAMPS (max. 15 RI's). Each RI will be marked
with a network indicator: C for CAMPS, S for SCARS
and A for ACCIS.
34) F̲L̲1̲4̲ ̲W̲I̲T̲H̲ ̲C̲O̲R̲R̲E̲C̲T̲I̲O̲N̲S̲
If an incoming message contains corrections directives
in format line 14, then the message will be queued
for the message service position. The MSO can then
make the corrections to the message and remove the
correction directives from format line 14.
The following section will be added as 3.2.2.2 e) 6)
in the SRS:
If a message contains a FL14 with corrections.
35) G̲A̲R̲B̲L̲E̲ ̲C̲H̲A̲R̲A̲C̲T̲E̲R̲S̲ ̲B̲E̲T̲W̲E̲E̲N̲ ̲F̲O̲R̲M̲A̲T̲ ̲L̲I̲N̲E̲S̲
To make the understanding of section 3.2.2.2 e) 5)
in the SRS more clear CR recommend to change the section:
was:
If a garble is found between the end of a line and
the recognisable beginning of a subsequent, but not
necessarily consecutive line.
should be:
If a garble is found between the end of a recognisable
line and the beginning of a subsequent mandatory line.
