top - download
⟦d46a5d27e⟧ Wang Wps File
Length: 8557 (0x216d)
Types: Wang Wps File
Notes: comments to clari. notes
Names: »0916A «
Derivation
└─⟦d10d3ed68⟧ Bits:30006014 8" Wang WCS floppy, CR 0055A
└─ ⟦this⟧ »0916A «
WangText
…02…
…02…KNN/810430…02……02…#
COMMENTS TO CLARIFICATION NOTES
…02……02…CAMPS
C̲N̲ ̲N̲o̲.̲ ̲2̲:̲ ̲A̲C̲P̲ ̲1̲2̲7̲ ̲A̲n̲a̲l̲y̲s̲i̲s̲
Re a) Refer CN No. 2
Re b) SHAPE has not answered the following question:
"Is accounting information limited to one line?"
Re d) CR propose that messages containing a SIC different
from 3 letters shall be directed to the MSO.
Only if no distribution for a SIC exists the
message shall be directed to the MDCO.
Re f) CR propose a maximum of 2 RIs per CAMPS HQ.
C̲N̲ ̲N̲o̲.̲ ̲3̲:̲ ̲A̲C̲P̲ ̲1̲2̲7̲ ̲C̲o̲n̲v̲e̲r̲s̲i̲o̲n̲
Re a) Refer CN no. 17.
Re c) Refer CN no. 18.
Re d) As a consequence of SHAPE response. CR does
not see any purpose in marking PLAs associated
with AIGs as ACTION/INFO. Therefore, CR propose
to delete that requirement.
Re f) Refer CN. no. 17.
C̲N̲ ̲N̲o̲.̲ ̲4̲:̲ ̲S̲e̲r̲v̲i̲c̲e̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲
Re e) CAMPS will be able to process incoming service
message containing PLAs (FL7 and FL8).
CAMPS does, however, only support preparation
of normal service messages, which do not contain
FL7 and 8.
C̲N̲ ̲N̲o̲.̲ ̲5̲:̲ ̲E̲n̲c̲r̲y̲p̲t̲e̲d̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲
Re a) For clarification CR amplify the following
two rules for outgoing messages.
R̲u̲l̲e̲ ̲1̲:̲
Outgoing codress messages shall, when entered
via the dedicated PTR, not contain GR in FL10.
R̲u̲l̲e̲ ̲2̲:̲
Outgoing codress messages shall when entered
via the normal PTR always contain GR, FL10.
Incoming decrypted messages (PLAIN DRESS) for
local distribution can only occur via the dedicated
PTR. These shall always contain GR in FL10.
Normal PTRs will only accept outgoing messages.
What message types can be entered via a PTR?
(ASM, data message, etc.)
Re c) CR assume that both SHD and SIC = "AAA" are
required, therefore, the following rules:
I̲n̲c̲o̲m̲i̲n̲g̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲
FL4 and FL12b will be consistency checked.
If inconsistent the message is directed to
the MSO.
O̲u̲t̲g̲o̲i̲n̲g̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲
Both the Special Handling Designator (SHD)
and the appropriate SIC ("AAA") shall be entered
by the user. If not, the message being prepared
will not pass the vailidation procedures associated
with message preparation.
C̲N̲ ̲N̲o̲.̲ ̲6̲:̲ ̲S̲e̲r̲v̲i̲c̲e̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲
Re a) Refer attached screen lay out for RI assignment.
It is not possible to convert and internal
prepared message to ACP 127 before all RIs
are assigned. Therefore, it is inconisstent
to talk about RI-assignment after conversion.
The new layout facilitates RI-assignment to
a PLA covered in an AIG. (Unpacked PLAs). CR
cannot see how it should be possible to assign
an RI to an AIG? Will SHAPE please clarify!
Re b) CR understand that the classification of a
message shall not be changed when the CLEAR
procedure is used.
Does this also imply that incoming messages
shall be distributed within a CAMPS site regardless
to the classification of the messages?
CR does not understand ref to "See 003".
CR cannot see how the CLEAR procedures can
be designed for outgoing messages. The requirement
states that the MSO shall have this capability.
He will, however, never get a message due to
low classification because the message will
be sent for off-line encryption. Will SHAPE
please clarify.
Re c) There should be some limits such as exclusion
of encrypted message or a Data messages.
Re d) SHAPE's response implies update of the SRS
section 3.2.4.2.1 b) and c) and 3.2.4.3.
figure
C̲N̲ ̲N̲o̲.̲ ̲7̲:̲ ̲A̲C̲P̲ ̲1̲2̲7̲ ̲C̲o̲n̲v̲e̲r̲s̲i̲o̲n̲
CR have no definition of FL12f. Please clarify.
C̲N̲ ̲N̲o̲.̲ ̲8̲:̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲ ̲f̲o̲r̲ ̲R̲e̲l̲e̲a̲s̲e̲
CR confirm that each terminal with release capabilities
has a separate release queue.
The agreement of CR should be taken together with the
clarification notes which specify the use of the release
queue.
CN No. 20: Queuing at user terminals
CN No. 21: Function Keys
CN No. 22: Terminal modes of operation
Futhermore, it is clarified that messages for release
(format D) of precedence FLASH shall not cause preemption.
(This is a consequence of CN No. 8).
CR propose that the duty officers shall have release
capabilities and that messages during quiet hours only
shall be prepared at terminals/by users associated
the releasing duty officer.
C̲N̲ ̲N̲o̲.̲ ̲9̲:̲ ̲M̲e̲s̲s̲a̲g̲e̲ ̲f̲o̲r̲ ̲C̲o̲o̲r̲d̲i̲n̲a̲t̲i̲o̲n̲s̲
CR withdraw.
C̲N̲ ̲N̲o̲.̲ ̲1̲0̲:̲ ̲Q̲u̲i̲e̲t̲ ̲H̲o̲u̲r̲s̲
Re d) It shall be noted that the short/long form
of PLAs only applies to incoming messages,
i.e. up to 8 PLAs shall be recognized. (8 HQ
per CAMPS site) in short/long form.
C̲N̲ ̲N̲o̲.̲ ̲1̲1̲:̲ ̲I̲n̲h̲e̲r̲e̲n̲t̲ ̲F̲L̲A̲S̲H̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲s̲
CR clarification of inherent FLASH precedence.
Transactions of inherent FLASH precedence applies as
follows:
Security procedures: From start of transaction to
termination
Deletion (format P1): From system accept of input
parameters until termination
of format P1.
Append (format O): From System accept of input
parameters to end of append
if on-line, otherwise until
system answers off-line, you
may proceed with another transaction.
Retrieval (format H): From system accept of input
parameters until termination
of transaction if on-line retrieval,
otherwise until system answers
off-line retrieval.
Note, however, the system will treat the retrieval
requests from many VDUs in order of arrival, not in
order of precedence (which is unknown).
C̲N̲ ̲N̲o̲.̲ ̲1̲2̲:̲ ̲I̲n̲c̲o̲m̲i̲n̲g̲ ̲M̲e̲s̲s̲a̲g̲e̲ ̲D̲i̲s̲t̲r̲i̲b̲u̲t̲i̲o̲n̲
Re a) Refer CN no. 18.
CN implies some new requirements in relation
to FL12D. Cr would like to discuss these during
the meeting 5th - 6th May.
Furthermore, CR recommend that table 3 is expanded
to include all special handling SICs/exercise
SICs. Therby we establish a firm baseline which
all parties hopefully are looking for.
Re b) CR suggest that SHAPE reconcider CN No. 12b)
(i.e. security access for MSO, MDCO, and Supervisor
Terminal/Equipment) once more for the following
reasons:
1) Max. classification is the only way by
which it is ensured that the MDCO/MSO and
supervisor queues never are blocked (refer
SRS p. 170 c) and p. 166g).
2) Only three special handling categories
can be specified in each user profile (refer
SRS p. 114 b)), which means that queues
can be blocked (fifo queue, where the first
element cannot be accessed).
C̲N̲ ̲N̲o̲.̲ ̲1̲3̲:̲ ̲Z̲E̲N̲ ̲i̲n̲ ̲P̲L̲A̲ ̲T̲a̲b̲l̲e̲s̲
CR does not require a ZEN indicator in the PLA tables
in order to select local HQs (max. 8 per CAMPS site).
This function will be performed by other means. (Refer
CN. No. 16).
C̲N̲ ̲N̲o̲.̲ ̲1̲4̲:̲ ̲S̲C̲D̲ ̲p̲e̲r̲ ̲P̲r̲i̲n̲t̲e̲r̲
CR clarify: The number of SCDs which can be specified
for a printer is limited to 5. This is the same restriction
as for VDUs and assures that distribution of messages/comments
can be based on the same criterias as for VDUs.
However, a printer may regardless of the SCDs specified
in this profile act as associated printer for VDUs
therefore, the SCDs in the printer profile only indicates
which mesages shall be distributed directly to the
printer.
Therefore, CR confirm: Printer profiles can only contain
upto 5 SCDs. A shared printer may be shared between
more than 5 VDUs, the VDU profile contains the terminal
designator of the associated printer.
C̲N̲ ̲N̲o̲.̲ ̲1̲5̲:̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲ ̲E̲n̲t̲e̲r̲e̲d̲ ̲v̲i̲a̲ ̲P̲T̲R̲
In case of separate transmisions CAMPS will not insert
ZEN in FL7 and in FL8.
C̲N̲ ̲N̲o̲.̲ ̲1̲6̲:̲ ̲M̲e̲s̲s̲a̲g̲e̲ ̲D̲i̲s̲t̲r̲i̲b̲u̲t̲i̲o̲n̲ ̲t̲o̲ ̲L̲o̲c̲a̲l̲/̲C̲o̲l̲o̲c̲a̲t̲e̲d̲
̲H̲e̲a̲d̲q̲u̲a̲r̲t̲e̲r̲s̲
An outgoing message containing local PLAs will be recognized
by the system. Copies of the message will be directed
to the appropriate local HQ for distribution in Format
E1 and ZEN prosign inserted in the message transmitted
via external network(s).
