top - download
⟦1bc14947a⟧ Wang Wps File
Length: 16570 (0x40ba)
Types: Wang Wps File
Notes: Supervisor ICD
Names: »0315A «
Derivation
└─⟦303071de8⟧ Bits:30006071 8" Wang WCS floppy, CR 0027A
└─ ⟦this⟧ »0315A «
WangText
…02…CPS/MMO/005
…02…801117…02…#
COMMENTS TO SUPERVISOR ICD
…02……02…CAMPS
C̲O̲M̲M̲E̲N̲T̲S̲ ̲T̲O̲ ̲S̲U̲P̲E̲R̲V̲I̲S̲O̲R̲ ̲I̲C̲D̲
D̲N̲ ̲1̲ ICD will be replaced by Interface Control Document
(ICD).
D̲N̲ ̲2̲ F̲i̲r̲s̲t̲ ̲p̲a̲r̲a̲g̲r̲a̲p̲h̲
A figure number will be inserted. CR considers the
current diagram explanation to be sufficient, but below
mentioned updates will be carried out.
S̲e̲c̲o̲n̲d̲ ̲p̲a̲r̲a̲g̲r̲a̲p̲h̲
CR will include a reference to SRS section 3.2.4.1.1.1
b.
T̲h̲i̲r̲d̲ ̲p̲a̲r̲a̲g̲r̲a̲p̲h̲
CR will include a reference to SRS section 3.2.4.1.1.2
b.
F̲o̲u̲r̲t̲h̲ ̲p̲a̲r̲a̲g̲r̲a̲p̲h̲
CR will include a reference to SRS section 3.2.4.1.1.1
d.
D̲N̲ ̲3̲ The words syntax and semantic are explained in the
following paragraph. No updates by CR.
D̲N̲ ̲4̲ Refer to DN2. No diagram updates by CR.
D̲N̲ ̲5̲ The title will not be changed. A lead-in explanation
will be inserted as follows.
The diagrams, which describe the supervisory commands
and procedures contain three fields:
- Computer display
- Operator entry
- Remarks, which are defined below.
D̲N̲ ̲6̲ The "var" explanation will be reworded:
Denotes a variable displayed by the computer; the
variable is defined in the remarks field or the section
1.3.
The remarks field is explained at the last line on
page 8. No CR update.
D̲N̲ ̲7̲ The operator entry paragraph will be reworded as follows.
The operator entry is always a response to a prompt.
If a number of responses are possible to a prompt,
the different possibilities are listed separated by
a comma,
e.g. YES, NO.
If the responses are a number series, the first two
entries and the last entry are listed separated by
3 points e.g. 2,4....16.
A specific function key "CR" is used to specify:
- that a response is optional
- that the table field referred to is to be left
unchanged.
Except for "CR", operator responses use capital letters.
"VAR": Denotes a variable entered by the operator,
the variable is defined in the remarks field or in
section 1.3.
E̲x̲p̲l̲a̲i̲n̲ ̲"̲v̲a̲r̲"̲,̲ ̲"̲V̲A̲R̲"̲ ̲d̲i̲f̲f̲e̲r̲e̲n̲c̲e̲:
Refer to answers to DN 6 and 7.
D̲N̲ ̲8̲ In case of a non-existing entry, only insertion of
entry items will be allowed. CR will update.
D̲N̲ ̲9̲ Refer to answer to DN7.
D̲N̲ ̲1̲0̲ A reference will be inserted to a table containing
all possible "PROCs".
OPP: Operator profile table update
TEP: Terminal profile table update
AIG: AIG table update
PCA: PCA table update
ORI: Outgoing RI table update
CHA: Channel table update
IRI: Incoming RI table update
SDL: SDL table update
SCD: SCD table update
MDC: MDCO sic table update
SEC: Security table update
URE: Release table update
DEQ: Deletion of Released Message
DEL: Deletion
SMP: Service message preparation
SME: Service message editing
ROM: Retransmission of outgoing message
RTR: Retrieval to own position
LRE: Local redistribution
MSQ: Message service
MDQ: Correction of Message for distribution
RDI: Retrieve for specified local distribution
D̲N̲ ̲1̲1̲ No choices will be displayed, but a possibility to
display or print complete tables will be given.
D̲N̲ ̲1̲2̲ A description will be included in the REMARKS field
as follows:
An interactive dialogue relating to the specified table
entry is started. The computer displays a prompt whereto
the operator shall reply. The reply is a variable
as demonstrated in the OPERATOR ENTRY file.
D̲N̲ ̲1̲3̲ Quotation symbols indicate a variable. No CR update.
D̲N̲ ̲1̲4̲ All variables given in the COMPUTER DISPLAY column
will be displayed. No CR update.
D̲N̲ ̲1̲5̲ The syntax and semantic will be updated as recommended.
D̲N̲ ̲1̲6̲ CR does not understand, please clarify.
D̲N̲ ̲1̲7̲ CR agrees, syntax should allow for 2 DIGITS.
D̲N̲ ̲1̲8̲ Description text will be updated as follows:
Number of print-out copies of a message.
Requirement for 3 shall be deleted.
D̲N̲ ̲1̲9̲ Expiration will as specified in SRS 3.2.3.1.e.4 be
expressed in days. CR will update.
D̲N̲ ̲2̲0̲ ORIGID refers to Headquarters of a CAMPS site as reflected
in Format Line 6 of ACP127 ("FROM"). Limit shall be
changed to 8 (PLA's). Change syntax to: "1,2.....60
chars.".
D̲N̲ ̲2̲1̲ Refer to answer to DN2, second paragraph. No CR update.
D̲N̲ ̲2̲2̲ PLAID will be withhold.
D̲N̲ ̲2̲3̲ CR agrees.
D̲N̲ ̲2̲4̲ Semantic possibilities will be included as follows:
ZZ, OO, PP, RR.
D̲N̲ ̲2̲5̲ Not applicable anymore: There is only one release
series for outgoing messages of any CAMPS site.
D̲N̲ ̲2̲6̲ If a supervisor command is defined to be restrictive,
the associated restrictive text is displayed to the
supervisor after entry of the command to indicate that
special attention is necessary.
D̲N̲ ̲2̲7̲ CR agrees, there is only one "originating" RI per incoming
message (there might be 8 HQ's = 8 different PLA's
in Fl6 of ACP127, however).
D̲N̲ ̲2̲8̲ There is no other difference between SHORT CMD and
CMD than the length: Refer to SRS, section 3.2.4.1.1.2.
The limit of 10 short commands is in accordance with
above reference. No CR update.
D̲N̲ ̲2̲9̲ 26x26x26 different sics are possible, but max. 3000
exist. No CR update.
D̲N̲ ̲3̲0̲ Please refer to CPS/230/ICD/0003, section 3.5.2. Does
SHAPE still want this option?
D̲N̲ ̲3̲1̲ No CR update.
D̲N̲ ̲3̲2̲ According to SRS section 3.4.1.4.1.e, the number of
utilization records is maximum 100. CR will consider
this as a fixed figure and update accordingly. The
utilization records actually present redundant information
as the log contains identical information.
D̲N̲ ̲3̲3̲ The explanation of the functioning of the diagram is
expanded as defined in DN2, 5, 6, 7, 8. No CR update.
D̲N̲ ̲3̲4̲ The assignment of a terminal as supervisor terminal
is valid after a sign off. CR will update in REMARKS
field.
The BLOCK/UNBLOCK commands will be removed to a separate
page.
D̲N̲ ̲3̲5̲ It is possible to assign a ROP to print in- and out-messages
as specified in the operator profile: EQ TYPE. No
CR update.
D̲N̲ ̲3̲6̲ The drafter shall insert SIC's, amongst those also
exercise SIC's. If exercise SIC's are specified, the
correponding exercise indication and name is automatically
inserted. CR agrees: INSEXIND, but also DETEXIND
shall be deleted.
D̲N̲ ̲3̲7̲
A̲C̲T̲I̲O̲N̲ ̲T̲O̲ Please refer to CPS/230/ICD/0003, section 3.2.2.
S̲H̲A̲P̲E̲ Should we delete this requirement?
D̲N̲ ̲3̲8̲
A̲C̲T̲I̲O̲N̲ ̲T̲O̲ Please refer to CPS/230/ICD/0003, section 3.2.2
Does
S̲H̲A̲P̲E̲ SHAPE want to keep this option?
D̲N̲ ̲3̲9̲
A̲C̲T̲I̲O̲N̲ ̲T̲O̲ Please refer to CPS/230/ICD/0003, section 3.5.2.
S̲H̲A̲P̲E̲ Does SHAPE want to keep this option?
D̲N̲ ̲4̲0̲ Misunderstanding! The "REMARKS" should be: "Specify
for FL7 and FL8 if RI's are inserted or not". This
option has now been dropped, however! Please refer
to CPS/230/ICD/0003, section 3.7.2.
D̲N̲ ̲4̲1̲ Requirements have been changed! Please refer to SRS
p 52: "Message Handling Instr.".
D̲N̲ ̲4̲2̲ This function reflects requirement in SRS, page 144,
item 9). However, the option n̲o̲t̲ to effect routing
to MDCO in these cases has been forgotten. CR will
amend.
D̲N̲ ̲4̲3̲ CR will update the REMARKS column as follows: Assigns
the name entered in the VOLNAME parameter to the initialized
disk pack on the off-line disk.
D̲N̲ ̲4̲4̲ Please refer to CPS/210/SYS/0001, section 3.2.4.1.1.14
(which reflect the IFB). CR is willing to delete this
function on SHAPE request.
D̲N̲ ̲4̲5̲ CR will insert a display of the result of the system
integrity check.
D̲N̲ ̲4̲6̲ SCD's are associated to terminals via SCD table of
section 14.
Number of possible OPID's will be updated to 15.
Release TD shall be moved to operator profile.
A̲C̲T̲I̲O̲N̲ ̲T̲O̲
S̲H̲A̲P̲E̲ SHCAT=special handling categories (SRS has replaced
the word c̲a̲t̲e̲g̲o̲r̲y̲ with d̲e̲s̲i̲g̲n̲a̲t̲o̲r̲): CR requests S̲H̲A̲P̲E̲
̲t̲o̲ ̲c̲l̲a̲r̲i̲f̲y whether the SECURITY INTERROGATION at terminals
shall be based on SPECIAL CAT. WARNINGS (Subset of
special handling designators) or SPECIAL HANDLING DESIGNATORS
in general.
The terminal profile shall list 3 SHCAT according to
SRS, section 3.2.3.1.d., these are supposed to be different
(but do not have to be) from the special category warnings.
CR considers ATOMAL, EXCLUSIVE, CRYPTOSEC, and NAT.
EYES ONLY as belonging to the S̲p̲e̲c̲i̲a̲l̲ ̲C̲a̲t̲e̲g̲o̲r̲y̲ ̲W̲a̲r̲n̲i̲n̲g̲s̲
D̲N̲ ̲4̲7̲ Refer to DN19.
D̲N̲ ̲4̲8̲ The supervisor will be capable of performing PREP,
RECE, RELE, MDCO,SERV, SUPV as described in SRS section
3.2.4.
Section 13 in the ICD will be updated accordingly.
D̲N̲ ̲4̲9̲ The ability to comment a message send for coordination
is included in the CAP=PREP.
A comment to a coordination request can only suggest
modifications. No CR updates.
D̲N̲ ̲5̲0̲ The FUNCTION prompt relates to a specific tab entry
and not to a table entry item as mentioned in section
1.2.1, with the following extensions:
if I: only subsequent INSERT table entry item prompts
as depicted in the actual table procedures will
be issued.
if C: table entry item prompts will be issued as depicted
in the actual table procedures.
if D: as specified.
CR will update section 1.2.1.
D̲N̲ ̲5̲1̲ Refer to DN 46.
D̲N̲ ̲5̲2̲ Refer to DN 50.
D̲N̲ ̲5̲3̲ SRS Requirements have been changed to 200 AIG's. CR
will change to display and entry of PLAID.
D̲N̲ ̲5̲4̲ ZEN-MODE is a result of IFB, 3.8.3.2 as reflected in
SRS page 74, item b2.
There is a second use of ZEN which is reflected in
IFB, 3.8.4.2 and SRS page 78, item h and i.
Channels, n̲o̲t̲ RI's are classified. This will be changed.
PLA limit now changed to 3000.
D̲N̲ ̲5̲5̲ As suggested by SHAPE: There will be one table for
PLA's and associated RI's and one with channel parameters
such as associated RI's and classification
D̲N̲ ̲5̲6̲ Limit is 3000 RI's.
D̲N̲ ̲5̲7̲ Low speed teletype channels are TRC's; the number
(6 in total to NICS TARE and TRC's) is wrong however!
The MAX RI for channels: Refer to page 60. Should
be deleted since always 200.
D̲N̲ ̲5̲8̲ Agreed. RI-tables should be deleted: System should
have separate tables for RI's and SIC's.
D̲N̲ ̲5̲9̲ MDCO SIC table has been deleted. A list or algoritm
of Special Handling SIC's should be introduced, however.
D̲N̲ ̲6̲0̲ Agreed (200).
D̲N̲ ̲6̲1̲ CR agrees.
D̲N̲ ̲6̲2̲ CR agrees. Both PLAID and PLAREF should be displayed
and allowed as input.
D̲N̲ ̲6̲3̲ Refer to the answer in DN 50.
D̲N̲ ̲6̲4̲ By specifying a PLAID or PLAREF, the nearby PLA's should
be displayed as well. PLA's will be ordered according
to PLAREF.
D̲N̲ ̲6̲5̲ Refer to DN 64. PLANO should be deleted (as well as
AIGNO, page 54).
D̲N̲ ̲6̲6̲ Agreed (3000 PLA's).
D̲N̲ ̲6̲7̲ Correct, should be PLANO. Refer to DN 65.
D̲N̲ ̲6̲8̲ Refer to DN 54.
D̲N̲ ̲6̲9̲ Refer to the answer in DN50.
D̲N̲ ̲7̲0̲ The current dialogue is teletype oriented, thus the
information displayed after PLANO specification cannot
be modified.
The TEXT prompt requests the operator to update the
PLAID.
No CR update.
D̲N̲ ̲7̲1̲ Classifications are no more specified in this table,
but in channel table. 4 RI's may be inserted or less.
D̲N̲ ̲7̲2̲ Having only one channel associated to each RI, this
information may be included in the PLA table.
D̲N̲ ̲7̲3̲ Agreed.
D̲N̲ ̲7̲4̲ R̲S̲E̲R̲V̲: Second possibility stated by SHAPE is the right
one. According to IFB 3.14.2, the service
message in question refers to serial no. of
last transmitted message issued by the same
station which is transmitting the service message.
CR assumes it to be the first message in a
new RADAY series. According to the IFB, it
may arrive shortly before 2400.
D̲N̲ ̲7̲5̲ According to SRS, the limit is now always 200! If
more RI's involved, several messages may be transmitted
automatically.
D̲N̲ ̲7̲6̲ Agreed. This should be a SIC-table not an RI table.
There will be several changes to this table.
CR agrees to have o̲n̲e̲ SDL causing both action and info.
D̲N̲ ̲7̲7̲ Refer to DN 76.
D̲N̲ ̲7̲8̲ Refer to DN 59.
D̲N̲ ̲7̲9̲ WARTXT will be changed to SECWRNTXT. CR will update.
D̲N̲ ̲8̲0̲ The SRS states the possibility to update the security
table items.
Until these are changed no CR updates will take place.
D̲N̲ ̲8̲1̲ The concept of release and originator is now changed
somewhat. Originator is identical to HQ. For each
HQ is defined one or more r̲e̲l̲e̲a̲s̲e̲ T̲e̲r̲m̲i̲n̲a̲l̲s̲.
To each u̲s̲e̲r̲ is associated a r̲e̲l̲e̲a̲s̲e̲ t̲e̲r̲m̲i̲n̲a̲l̲ (SRS
page 103, IFB 3.7.2) and a̲s̲s̲o̲c̲i̲a̲t̲e̲d̲ ̲f̲u̲n̲c̲t̲i̲o̲n̲s̲ (including
the release function). This is as outlined by SHAPE.
Table will be changed.
D̲N̲ ̲8̲2̲ Refer to DN 25.
D̲N̲ ̲8̲3̲ Refer to DN 41.
D̲N̲ ̲8̲4̲ Deletion shall in general be defined as follows:
Cancellation of all not yet initiated transactions
concerning this message except for retrieval of initial
prepared version and released version.
Refer to answers to DN 85 and DN 86 for further comments.
D̲N̲ ̲8̲5̲ A deletion request from an operator to a message, which
is:
- sent for release, or
- has been released
is queued to the supervisor.
The procedure is an ICD/0001 format P section 24.3.4
and 24.3.5 requirement. CR will insert a reference
to
ICD/0001.
D̲N̲ ̲8̲6̲ This procedure does not refer to automatic deletion
of SPECAT messages, but fulfils the SRS section 3.2.4.1.1.15
requirements. CR will insert a reference to ICD/0001.
CR is willing to delete this requirement, however.
D̲N̲ ̲8̲7̲ According to SRS, page 62, the supervisor shall specify
PLA's or AIG's. However, since, at least on receiving
CAMP sites, the message always shall be routed to the
ACTION supervisor, he might as well specify the RI. Does
SHAPE
TO SHAPE want this option? should the option for PLA's and
AIG's be deleted?
D̲N̲ ̲8̲8̲ Conversion refers to conversion to ACP 127 format either
abbreviated or not. Release/coordination is not applicable
to service message preparation.
D̲N̲ ̲8̲9̲ The service message display procedure is invoked during
initial service message preparation and in service
message editing if YES is answered to the CLEAN COPY?
prompt.
CR will update.
D̲N̲ ̲9̲0̲ The message is not transmitted before final RI-assignment,
the message is transferred to message service (p. 87).
D̲N̲ ̲9̲1̲ The message is automatically transmitted after YES
ACTION response. Please clarify operating signal.
TO SHAPE
D̲N̲ ̲9̲2̲ CR will join the two functions.
Transaction Reference in format H3S shall be dropped
(not relevant).
Optionally, the MDCO or the supervisor may distribute
to a new set of SCD's or the original set plus/minus
the specified new SCD's.
D̲N̲ ̲9̲3̲ CR will insert in the REMARKS column: specify if distribution
(automatic) is to be executed.
D̲N̲9̲4̲ CR will replace "for which" by "for which automatic".
D̲N̲ ̲9̲5̲ A call of the correction procedure is executed from
the message service position and is not to some other
supervisory position. CR will update.
D̲N̲ ̲9̲6̲ Refer to DN 97. In case of garbled SIC's the message
is queued to the MDCO, n̲o̲t̲ message service.
D̲N̲ ̲9̲7̲ The function of specifying local distribution at a
message service position was thought as a means of
distributing strongly garbled messages which may not
be re-issued to automatic distribution (security information
must be available however).
D̲N̲ ̲9̲8̲ New processing means that the message will (automatically)
be sent to complete renewed analysis of ACP 127 format.
CR will clarify.
D̲N̲ ̲9̲9̲ Answer to NEW PROCESSING:
YES: refer to DN98.
NO: the updated message is returned in the tail of
the message service queue as the oldest message
and may later be handled by the MSQ procedure.
D̲N̲ ̲1̲0̲0̲ CR will replace
"to which no RI exists" by
"for which no RI is contained in RI table".
D̲N̲ ̲1̲0̲1̲ CR will update to allow for rejection without renewed
queuing or automatic processing.
D̲N̲ ̲1̲0̲2̲ The current MDQ procedure follows the requirements
in SRS section 3.2.4.3.1. No CR updates. CR is willing
to delete requirement for change of precedence, classification,
or SICs, however.
D̲N̲ ̲1̲0̲3̲ CR agrees.
