top - download
⟦bd90a88b3⟧ Wang Wps File
Length: 74607 (0x1236f)
Types: Wang Wps File
Notes: CPS/230/ICD/0001
Names: »0364A «
Derivation
└─⟦2a70d8cf1⟧ Bits:30006046 8" Wang WCS floppy, CR 0073A
└─ ⟦this⟧ »0364A «
WangText
]…00……00……00……00…5…0a……00……00…5…0b…5…00…5 4…09…4…0e…4…01…4…05…3…08…*…0a…*
)…0c…)…0e…)
(…09…(…0e…(
'…09…'…0f…'…05…'…06…&…08…&…0d…&…02…&…06…%…09…%…0d…%
%…06…$…0d…$ #…0b…#…00…#…01…#…07…"…08…"…09…"…0a…"…0e…"…0f…"…00…"…06…!…0d…!
…86…1 …02… …02… …02…
…02…CPS/230/ICD/0001
…02…831219…02……02…
USER PROCEDURES AND ASSOCIATED FORMATS
…02…ISSUE 3.9…02…CAMPS
Issue 3.2 810812 C̲h̲a̲n̲g̲e̲ ̲n̲o̲.̲ ̲3̲
ECP no. 010
dated 810611
CN 18 33,37 and 39 Message Handling Instruction
CN 20 5,10,19,28,30 Response Queue/Mode
104,105,106, (Notification of
121,146 Append)
CN 21 104 The function key CANCEL
CN 23 3,9-12,15, System line, sign-in
18,24-27, sign-out, security
100,102,103 procedures
CN 24 128,130 Entry of release decision
CN 28 44 Classification of appended
message
CN 29 11 Margin area layout
13,26 Queue status line
30,37,38 Queue status line
39,41,43 Queue status line
50,51,52 Queue status line
55,58,61 Queue status line
62,67,69 Queue status line
73,77,80 Queue status line
82,84,86 Queue status line
88,90,94 Queue status line
95,98,101 Queue status line
110,111,112 Queue status line
114,117,119 Queue status line
121,125,130 Queue status line
133 Queue status line
ISSUE 3.3 811118 C̲h̲a̲n̲g̲e̲ ̲N̲o̲.̲ ̲4̲
ECP No. 15
dated
811013
1 14 Editorial
2 19 Editorial
3 22 Editorial
4 37,50,62,73, Transaction ID 21
94,98,101,110 characters instead of
114,117,119, 20
121a,133
5 30 Layout re-arranged
6 31,42 Use of ENTER
7 32,37 Start value of msg. type
8 34,48,110, Max l0 locally distr.
144 copies
9 35,38 Action addressee optional
10 35 Error number changed
11 35 MDCO changed to MSO
12 35 ACTION/INFO Addressees
13 35 Format of EXEC-SIC
14 36 Editorial
15 36,145 Validation of EXEC-SICs
16 37,50 Originator ID alphanumeric
17 37,50 Removal of "R" for Repeat
18 38 EXER/OPER is optional
19 41 Text field is repeatable
20 42,145 Actions regarding unreachable
release terminals
21 43 Input types format A-3
22 43,44 Retrieval format to be used
23 44 Format A-4 deleted
24 44 Invalid reference handling
25 44 Append from off-line
26 44 Editorial
27 48 CCIS/SCARS distribution
postponed
28 48 Editorial
29 49 REPEAT not a command
30 54 Clarifications regarding
C1-1
31 54 Trailing space lines
32 57 Use of formt G1-1
33 70 Format P1-2 deleted
34 70,71,73 TOC required
35 71 Use of format P1
36 74,77,80,82, Descriptive names of
84,86,88,90, retrieval formats
37 76 Retrieval output changed
38 77,80,82,84, Transaction ID included
86,88,90 in screen layouts
39 77 Input field included in
retrieval menu
40 77 Retrieval menu format rearranged
41 79 Off-line retrieval
42 79 Deletion of lines regarding
final/draft field
43 80,82,84,86, H-2 replaced with H-R
88,90 and H-D
44 80,82,84,90, DTG to be 11 characters
98, 121c
45 80 ORIG. HQ included
46 81,82 TOC, DTG mandatory/ optional
47 82,84 60 characters for ORIG.
HQ.
48 (83,84) PLA to be used. No change.
49 87 ORIG. SCD to be mandatory
50 88 ITEM REF. ID included
51 89 Output by retrieval
52 89 Originator PLA/SCD
53 92,93,94,95 ITEM REF. ID of release
notification to be included
54 92,97 Periodic print outs
55 92 Change of headlines sec.
3.12.4
56 (92),93,95 Messages deferred
57 (92),93,95 Messages awaiting append
58 93 Inclusion of "Comments to
be deferred".
60 93 Clarification
61 93,95 Format N-2 enhanced
62 95 Editorial
63 97 Time Stamp discrepancy
64 107 Screen layout rearranged
65 107 New header of section 4.2
66 107,110,113 DATE TIME GROUP
114 inserted
67 110,114,117 Handling instruction field
length = 69 chars
68 110 Fig. 4.2-1 rearranged
69 113,114 Format lines 6 to 13
70 132 Enhancement of release status
71 132,133 Clarification on "Total
Number"
72 133 Item ref ID included in
format Q
73 141 Precedence long form
74 141 Editorial
75 142 Editorial
76 142 Space included in Transaction
ID
77 143 Editorial
78 113,114 Msg. Handling Instruction
inserted
79 107,108,109, Renumbering
113,115,116
80 145 Editorial
81 146 Precedence included
Ref. tlx
CAMPS Log
No. 457
a 20 Editorial
b 125 Editorial
c 141 Editorial
d 144 Editorial
e 146 Editorial
ISSUE 3.4 820111 C̲h̲a̲n̲g̲e̲ ̲N̲o̲.̲ ̲5̲
Based on
CPS/ECP/016,
dated 811221
C - 1 32,50,62 Two special handling designators
E - 1 76 Retrieval response in accordance
with several, one or more
item fits the retrieval
key
E - 11 33,37,39,142 Operating Signal, 50 characters
text string
E - 14 37,38, 80n), Length of PLA is 54
82,84,110,111 characters
141
ISSUE 3.5 820118 C̲h̲a̲n̲g̲e̲ ̲N̲o̲.̲ ̲6̲
Based on
CPS/ECP/019
dated 820111
B - 1 5,135,136 No teleprinter as PTP
B - 2 18 Scrolling limitations
B - 3 5,134,142 SCARS/ACCIS comments
145,146 and displays
B - 4 78,79,87 Time specification in retrieval
keys
B - 5 17 Function key "RETURN"
B - 6 145 Explanatory Error Msg
ISSUE 3.6 821125 C̲h̲a̲n̲g̲e̲ ̲N̲o̲.̲ ̲7̲
Based on
CPS/ECP/025 25,102, Blocked Terminal
103
ISSUE 3.7 830509 C̲h̲a̲n̲g̲e̲ ̲N̲o̲.̲ ̲8̲
Based on
CPS/ECP/031 22 Concurrent error
dated 830509 indications
19a,35,36 Echoe back of format after
validation
37,38,41 Improvement of the
43,51,52 use of screen formats
110,111,112
114,117,119
130,134d,134i
ISSUE 3.8 830928 C̲h̲a̲n̲g̲e̲ ̲N̲o̲.̲ ̲9̲
Based on
CPS/ECP/035
dated 830804 44a. 44b Validation
ISSUE 3.9 831219 C̲h̲a̲n̲g̲e̲ ̲N̲o̲.̲1̲0̲
Based on 10,11 Clarification
CPS/ECP/038 12 Margin Area
dated 840120 15,17a Commands
18,19a,19b
20 Command Validation
25 Validation
22,33,34,35 Error Codes/Response
36,40,42,46 Text
54,57,71,72
76,102,104b
134f,145a,
145b
44a Append Message
48 Local Distribution
53,56,60 Editorial
64,65 Repeatable Sets/Fields
134r SCARS/ACCIS
134t,134u SCARS/ACCIS Release
141 PLA
30,62 Screen Formats
67,80c,80d,
82a,82b,84a
84b,86a,86b,
88a,88b,98
125,134m,
134n(i)
134n(ii)
134q,134s(i)
134s(ii)
134r.134v
134w
1 SCOPE ........................................
6
1.1 REFERENCE DOCUMENTS ......................
6
1.2 DOCUMENT STRUCTURE .......................
7
2 VDU CHARACTERISTICS ..........................
7 to 20
2.1 VDU FACILITIES ...........................
7
2.2 VDU SCREEN LAYOUT ........................
8
2.2.1 VDU Header Area ......................
9
2.2.1.1 Terminal Function ................
9
2.2.1.2 Classification ...................
9
2.2.1.3 Time .............................
10
2.2.1.4 Queue Information ................
10
2.2.1.5 Command Line .....................
10
2.2.1.6 Response Line ....................
11
2.2.1.7 System Line ......................
11
2.2.2 Format Area ..........................
11
2.2.2.1 Margin Area ......................
11
2.2.2.2 Line Descriptor ..................
11
2.2.2.3 Field Descriptor .................
12
2.2.2.4 Field Protection .................
12
2.3 COMMANDS .................................
15
2.3.1 General Commands .....................
15
2.3.2 Format Edit ..........................
16
2.3.2.1 Insert (n) Lines .................
16
2.3.2.2 Delete (n) Lines .................
16
2.3.3 Field Edit ...........................
16
2.3.3.1 Character Overwrite ..............
16
2.3.3.2 Next Field .......................
17a
2.3.3.3 Previous Field ...................
17a
2.3.3.4 Clear Format .....................
17a
2.3.3.5 Clear to End of Format ...........
17a
2.3.3.6 Clear to End of Field ............
17a
2.3.3.7 Delete Char ......................
17a
2.3.4 Screen Manipulation ..................
17b
2.3.4.1 Command ..........................
17b
2.3.4.2 Return ...........................
17b
2.3.4.3 Page-Forward .....................
17b
2.3.4.4 Page-Back ........................
17b
2.3.4.5 Scroll Forward ...................
18
2.3.4.6 Scroll Back ......................
18
2.3.4.7 System ...........................
18
2.3.5 Transaction Processing ...............
18
2.3.5.1 Enter ............................
18
2.3.5.2 Cancel ...........................
18
2.3.5.3 Suspend ..........................
18
2.3.5.4 Delete and Present Message .......
19a
2.3.5.5 Keep and Present Message .........
19a
2.3.5.6 Display Error Message ............
19a
2.3.5.7 Print ............................
19a
2.3.5.8 Return to Current Menu ...........
19a
2.3.5.9 Display PLA Text .................
19b
2.3.6 Specific Commands ....................
19b
2.4 CURSOR CONTROL ...........................
20
2.5 COMMAND VALIDATION .......................
20
3 USER TRANSACTION USING VDU ...................
21 to 103
3.1 OVERVIEW .................................
21
3.1.1 Validation ...........................
21
3.1.2 Error Indications ....................
21
3.1.3 Transaction Identity .................
22
3.1.4 Item Reference Identity ..............
22
3.1.5 Data Entry ...........................
22
3.1.5.1 Fields ...........................
22
3.1.5.2 Data Entry Description ...........
23
3.1.6 Exit Conditions ......................
23
3.2 SIGN ON (FORMAT K1).......................
25
3.3 USER MENU (FORMAT X)......................
29
3.4 NEW MESSAGE PREPARATION (FORMAT A)........
32
3.5 APPEND MESSAGE (FORMAT O) ................
44a
3.6 NEW COMMENT (FORMAT G1) ..................
48
3.7 CONTINUE MESSAGE PREP (FORMAT C1) ........
54
3.8 CONTINUE COMMENT PREP (FORMAT G3) ........
57
3.9 PREPARE PREDEFINED MESSAGE (FORMAT M) ....
60
3.10 MESSAGE/COMMENT DELETION (FORMAT P1) .....
71
3.11 MESSAGE/COMMENT RETRIEVAL (FORMAT H) .....
74
3.12 OUTGOING MESSAGE STATUS (FORMAT N) .......
92
3.13 DELIVERY STATUS (FORMAT R) ...............
97
3.14 SIGN-OFF (FORMAT K2) .....................
100
3.15 SECURITY PROCEDURES (FORMAT I) ...........
102
4 DISPLAY FORMATS ..............................
104 to 121
4.1 GENERAL ..................................
104
4.2 COORDINATION (FORMAT B), OUTGOING MESSAGE
(FORMAT E2), RELEASE (FORMAT D) ..........
107
4.3 INCOMING MESSAGE (FORMAT E1) .............
113
4.4 COMMENT (FORMAT G2) ......................
115
4.5 NOTIFICATION OF RELEASE (FORMAT F) .......
118
4.6 NOTIFICATION OF DELETION (FORMAT P2) .....
120
4.7 NOTIFICATION OF APPEND ...................
121
5 RELEASER TRANSACTIONS USING VDU ..............
122 to 133
5.1 RELEASER MENU-1 ..........................
124
5.2 RELEASER MENU-2 ..........................
126
5.3 MESSAGE RELEASE (FORMAT D) ...............
128
5.4 MESSAGE RELEASE STATUS (FORMAT Q) ........
132
6 SCARS/ACCIS Comments and VDU Displays ........
134a
6.1 PREPARE TERMINAL-TO-TERMINAL COMMENT .....
134a
6.2 PREPARE VDU DISPLAYS .....................
134e
6.3 CONTINUE TERMINAL-TO-TERMINAL COMMENT PREP
134j
6.4 CONTINUE VDU DISPLAY PREP. ...............
134j
6.5 PRESENTATION OF COMMENTS AND DISPLAYS ....
134j
6.6 RETRIEVAL OF VDU DISPLAYS ................
134o
6.7 SCARS/ACCIS COORDINATION .................
134r
6.8 SCARS/ACCIS RELEASE ......................
134t
7 TRANSACTION USING A LOW SPEED TELEPRINTER ....
135 to 136
7.1 INTRODUCTION .............................
135
7.2 MESSAGE INPUT ............................
135
7.2.1 Validation ...........................
135
7.3 MESSAGE PRINT OUT ........................
136
7.4 ELECTRICAL INTERFACE .....................
136
7.5 CHARACTER CONVERSION .....................
136
8 TRANSACTIONS USING AN OCR ....................
137
8.1 TYPES OF TRANSACTION USING OCR ...........
137
8.2 FORMAT OF MESSAGE INPUT TO OCR ...........
137
8.3 EDITING AND CORRECTION ...................
137
9 TRANSACTION USING A HIGH SPEED PTR/PTP .......
138
9.1 OUTPUT TO PUNCH ..........................
138
9.2 INPUT FROM READER ........................
138
10 TRANSACTIONS USING A MEDIUM SPEED RECEIVE ONLY
PRINTER ......................................
139
APPENDIX A - FIELD/ELEMENT DICTIONARY ...........
140 to 144
APPENDIX B - USER PROCEDURES RESPONSE MESSAGES/
ERROR CODES ........................
145a
APPENDIX C - SPECIFIC COMMANDS ..................
146
APPENDIX D - FUNCTION KEY LAYOUT ................
147
1̲ ̲ ̲S̲C̲O̲P̲E̲
This ICD defines the formats and transactions which
are applicable to the CAMPS functions
- Message Preparation
- Message Release
- Message Reception
In relation to these functions the facilities to perform
the following are described.
- Editing
- Retrieval
- Deletion
- Comment Preparation
- Security Checking
- Coordination
- Command and Control Display Preparation
1.1 R̲E̲F̲E̲R̲E̲N̲C̲E̲ ̲D̲O̲C̲U̲M̲E̲N̲T̲S̲
The following documents are listed for reference purposes
only. The listing does not constitute the contents
of the documents as System Requirements but is intended
to serve the Contractor in providing supplementary
information in cases of interpretation of the requirements
specifically stated in this document:
ACP131B, Jul. 74
ACP117J, Sept. 1977, ACP117 Supp. 1G Dec. 79
ACP121 Supp. 1 A, Jan. 1970, 121E Jul. 70
ACP127 NATO Supp. 3, May 1973, 127(E) Oct. 74
APP-3, Jan. 1978
ADat-P3, Jan. 1975
The above documents are only applicable to the extent
that they are referenced in this ICD by name and specific
sections.
1.2 D̲O̲C̲U̲M̲E̲N̲T̲ ̲S̲T̲R̲U̲C̲T̲U̲R̲E̲
1) The description of the User Procedures is in terms
of TRANSACTIONS.
A transaction consists of a dialogue which a user
is able to perform to achieve the aim of Message
Preparation, Message Release and Message Reception.
The transaction identifies FORMATS, describes the
dialogues associated with those formats, and describes
a possible sequence of formats. The overall sequence
of formats is shown in a diagram and the VDU layouts
of the formats are given on a special form.
2) The fields within these formats are identified
and defined in terms of their elements, the possible
values of the elements, and the semantic checks
performed.
3) The System Response Messages, returned as a result
of validation, or, which are required to give the
user direction, are also listed.
2̲ ̲ ̲V̲D̲U̲ ̲C̲H̲A̲R̲A̲C̲T̲E̲R̲I̲S̲T̲I̲C̲S̲
2.1 V̲D̲U̲ ̲F̲A̲C̲I̲L̲I̲T̲I̲E̲S̲
The full set of features of the CAMPS VDU are described
in the System Requirements Specification para. 3.4.1.10.1.
The basic characteristics assumed for this specification
are as specified below. The characteristics do not
imply additional requirements to CPS/210/SYS/0001.
- 4 lines VDU header
- Min 22 useable lines of 80 characters each
- 12 programmable function keys
- Split screen capability as defined in section 2.2
- Protected and Unprotected fields
- Unprotected fields have the following attributes-Mandatory,
optional, alpha, numeric, alphanumeric, length
- VDU attributes - inverse video, dual intensity,
bell, paging, scrolling over VDU memory contents
- Delete/insert character
- Delete/insert line, if in accordance with dialogue
design
- Press to repeat for specified keys
- Lockable
As the VDU to be used in the CAMPS is not known at
the time of preparation of this document, minor changes
may take place during implementation as long as they
do not impair the features of the VDU as specified
in para. 3.4.1.10.1 of the CPS/210/SYS/0001.
2.2 V̲D̲U̲ ̲S̲C̲R̲E̲E̲N̲ ̲L̲A̲Y̲O̲U̲T̲
The VDU screen is divided into two areas; a four line
VDU header and a 22 line format area. The header contains
terminal status information and the format area is
used by the system to display formats and by the user
to enter data. (Fig. 2.2-1).
2.2.1 V̲D̲U̲ ̲H̲e̲a̲d̲e̲r̲ ̲A̲r̲e̲a̲
The fields used in the header are the following:
- Terminal Function
- Classification of current screen contents
- Time
- Queue status
- Command line
- Response line
- System line
2.2.1.1 T̲e̲r̲m̲i̲n̲a̲l̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲
This describes the transaction in course. It is a 25
alpha-numeric field.
The defined terminal functions are shown in the format
descriptions in section 3, 4, and 5.
It is updated on a per-format basis.
2.2.1.2 C̲l̲a̲s̲s̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
This relates to the classification of the information
on the screen. It is a 20 character alpha field.
Displayed items with the classification identified
will be updated before the presentation of the format.
For items where the classification will first be recognized
during validation it will be updated when the subsequent
format is displayed.
The terminal and the operator have a preset highest
classification in their profile. The default classification
appearing on the screen is the lower of these two.
2.2.1.3 T̲i̲m̲e̲
This is the Time in DATE TIME GROUP format. It is a
14 alpha-numeric field containing the Day, Hour, Minute,
Zone, Month, Year.
This is updated every minute.
2.2.1.4 Q̲u̲e̲u̲e̲ ̲I̲n̲f̲o̲r̲m̲a̲t̲i̲o̲n̲
The number of messages queued for the terminal by precedence
as well as those for coordination, release, display
or response on a terminal will be shown. Each category
is identified by an alpha descriptor with a two numeric
field for the number of items of this category in the
terminal queue.
Queue information is updated every minute except when
FLASH messages are queued which causes immediate update
and a short audio alarm.
In the category "coordination" is contained the number
of messages incoming for coordination.
In the category "release" is contained the number of
messages for release.
In the category "display" is contained the number of
incoming messages, comments and outgoing messages.
In the category "response" is contained the number
of answers to retrieval request (from off-line database),
append notifications (off-line append), delete notifications
and release notifications.
2.2.1.5 C̲o̲m̲m̲a̲n̲d̲ ̲L̲i̲n̲e̲
The command line will be used for the insertion of
commands as listed in Appendix C (except for SION and
SIOF) and entry of parameters.
Commands will be entered by pressing a "Command" function
key which will cause the cursor to jump to the Command
Line in the header. The user will then enter the command
on this line. On pressing the Return Key, the command
will be executed, the command line cleared, and the
cursor repositioned back within the main format area.
A command will consist of four alpha characters followed
by a parameter field, if required. Commas or space
sign will be used as separators.
2.2.1.6 R̲e̲s̲p̲o̲n̲s̲e̲ ̲L̲i̲n̲e̲
System response messages and replies to commands where
appropriate will be displayed on the response line.
It has a maximum length of 70 alpha numeric characters.
2.2.1.7 S̲y̲s̲t̲e̲m̲ ̲L̲i̲n̲e̲
All data entered to / output from the system in connection
with the security procedures format K1, K2, I1 and
I2 are performed via this system line.
The user can enter the sign-on / sign-off command by
first pressing the SYSTEM function key, which will
cause the cursor to jump to the system line, and then
enter the command.
The system will use this line to prompt the user for
input of security parameters.
2.2.2 F̲o̲r̲m̲a̲t̲ ̲A̲r̲e̲a̲
The symbols used in the VDU Layout forms is shown in
fig. 2.2-2.
Where specified the format area may be divided into
the margin area and the user area.
This does not apply to the Command and Control display,
which occupy the full screen width.
2.2.2.1 M̲a̲r̲g̲i̲n̲ ̲A̲r̲e̲a̲
The ten character margins used by the system to indicate
the following:
1 2 3 4 5 6 7 8 9
0
ERROR CODE SPACE LINE SPACE TEXT LINE
NUMBER
DESCRIPTOR
The user area consists of the remaining 70 characters.
'TEXT LINE NUMBER' FIELD is only used when queued information
is displayed. 'ERROR CODE' FIELD is only used during
transaction in which the system validates input from
the VDUs format area.
2.2.2.2 L̲i̲n̲e̲ ̲D̲e̲s̲c̲r̲i̲p̲t̲o̲r̲
A line desciptor will be given in the VDU margin to
indicate to the user if a line is repeatable or not.
2.2.2.3 F̲i̲e̲l̲d̲ ̲D̲e̲s̲c̲r̲i̲p̲t̲o̲r̲
Each data entry field has a descriptor, specifying
whether the user should input alpha, numeric or alphanumeric
data, and whether the entry is optional or mandatory.
This descriptor is visible to the user in the form
of a symbol preceding each field, as a reminder of
the type of data required. The descriptor will only
be given for the first field of a series of "identical"
fields.
2.2.2.4 F̲i̲e̲l̲d̲ ̲P̲r̲o̲t̲e̲c̲t̲i̲o̲n̲
Unprotected data-entry fields are the only part of
the screen where characters can be written.
If the user does not enter a mandatory field or enters
an incorrect type of character he will be warned.
Figure 2.2-1…01…SCREEN LAYOUT
= inverse video field
= Unprotected data-entry
field
L̲i̲n̲e̲ ̲d̲e̲s̲c̲r̲i̲p̲t̲o̲r̲
R = Repeating
S = Selecting
M = Mandatory
O = Optional
F̲i̲e̲l̲d̲ ̲D̲e̲s̲c̲r̲i̲p̲t̲o̲r̲s̲
N = Mandatory numeric
n = Optional numeric
A = Mandatory alpha
a = Optional alpha
D = Mandatory alphanumeric
d = Optional alphanumeric
Fig. 2.2-2…01……01…S̲Y̲M̲B̲O̲L̲S̲ ̲U̲S̲E̲D̲ ̲O̲N̲ ̲V̲D̲U̲ ̲L̲A̲Y̲O̲U̲T̲ ̲F̲O̲R̲M̲S̲
2.3 C̲O̲M̲M̲A̲N̲D̲S̲
The commands are divided into three categories:
- those entered by standard function Keys
- those entered by preprogrammed function keys
- those entered by four letter mnemonics
2.3.1 G̲e̲n̲e̲r̲a̲l̲ ̲C̲o̲m̲m̲a̲n̲d̲s̲
The set of general commands available to the user is:
- Format Edit INSERT N LINES
DELETE N LINES
- Field Edit CHARACTER OVERWRITE
NEXT FIELD
PREVIOUS FIELD
CLEAR FORMAT
CLEAR TO END OF FORMAT
CLEAR TO END OF FIELD
DELETE CHAR
- Screen Manipulations COMMAND
RETURN
PAGE-FORWARD
PAGE-BACK
SCROLL-FORWARD
SCROLL-BACK
SYSTEM
- Transaction Processing ENTER
CANCEL
SUSPEND
DELETE AND PRESENT MESSAGE
KEEP AND PRESENT MESSAGE
DISPLAY ERROR MESSAGE
PRINT
RETURN TO CURRENT MENU
2.3.2 F̲o̲r̲m̲a̲t̲ ̲E̲d̲i̲t̲
The following commands are available in format edit.
Scrolling is not allowed.
2.3.2.1 I̲n̲s̲e̲r̲t̲ ̲(̲n̲)̲ ̲L̲i̲n̲e̲s̲
An "Insert" command is used to provide additional space
in a format.
The lines below the insert are pushed down to accomodate
the inserted lines.
If there is not enough free space on the current page
for the required number of lines then the displayed
lines will appear on a subsequent page.
The inserted lines are positioned with respect to the
cursor position, at the moment the command key was
depressed.
This command is only applicable to repeatable lines.
2.3.2.2 D̲e̲l̲e̲t̲e̲ ̲(̲n̲)̲ ̲L̲i̲n̲e̲s̲
A "delete" command is used to remove lines from a format.
The lines below the deletion are pushed up to remove
the deleted lines.
The deleted lines are positioned with respect to the
cursor position at the moment the command key was activated.
This command can only be used to delete repeatable
lines.
2.3.3 F̲i̲e̲l̲d̲ ̲E̲d̲i̲t̲
Editing is allowed on the contents of unprotected fields.
Only on ENTER will the changed fields be available
to the host for validation.
2.3.3.1 C̲h̲a̲r̲a̲c̲t̲e̲r̲ ̲O̲v̲e̲r̲w̲r̲i̲t̲e̲
The character to be overwritten is defined by the cursor
position. The next character typed in will overwrite
the previous one.
2.3.3.2 N̲e̲x̲t̲ ̲F̲i̲e̲l̲d̲
This command causes the cursor to jump to the next
field.
2.3.3.3 P̲r̲e̲v̲i̲o̲u̲s̲ ̲F̲i̲e̲l̲d̲
This command causes the cursor to return to the beginning
of the previous field.
2.3.3.4 C̲l̲e̲a̲r̲ ̲F̲o̲r̲m̲a̲t̲
This function clears all unprotected data, replacing
it with spaces, and positions the cursor to the first
unprotected character position in the split.
2.3.3.5 C̲l̲e̲a̲r̲ ̲t̲o̲ ̲E̲n̲d̲ ̲o̲f̲ ̲F̲o̲r̲m̲a̲t̲
All unprotected data from the cursor position to the
end of the split is cleared and replaced with spaces.
2.3.3.6 C̲l̲e̲a̲r̲ ̲t̲o̲ ̲E̲n̲d̲ ̲o̲f̲ ̲F̲i̲e̲l̲d̲
This function clears all unprotected character positions
from the cursor to the end of the current field and
replaces them with spaces.
2.3.3.7 D̲e̲l̲e̲t̲e̲ ̲C̲h̲a̲r̲
This function deletes the character at the cursor position,
causing all data after the cursor up to the next end-of-line
code to move one position to the left.
2.3.4 S̲c̲r̲e̲e̲n̲ ̲M̲a̲n̲i̲p̲u̲l̲a̲t̲i̲o̲n̲
2.3.4.1 C̲o̲m̲m̲a̲n̲d̲
This causes the cursor to move to the command line.
2.3.4.2 R̲e̲t̲u̲r̲n̲
This causes the contents of the command line to be
sent to the host.
2.2.4.3 P̲a̲g̲e̲-̲F̲o̲r̲w̲a̲r̲d̲
This causes the next page of information to be displayed.
If the presently displayed page is the last page of
a format this key shall have no effect.
2.3.4.4 P̲a̲g̲e̲-̲B̲a̲c̲k̲
This causes the previous page of information to be
displayed. If the presently displayed page is the first
page of a format this key shall have no effect.
2.3.4.5 S̲c̲r̲o̲l̲l̲ ̲F̲o̲r̲w̲a̲r̲d̲
This allows the user to move the display up one line
at a time until the bottom of the "display" is reached.
Scrolling is allowed within the limitation of the pages
currently stored in the VDU.
2.3.4.6 S̲c̲r̲o̲l̲l̲ ̲B̲a̲c̲k̲
This allows the user to move the display down one line
at a time until the top of the "display" is reached.
Scrolling is allowed within the limitation of the
pages currently stored in the VDU.
2.3.4.7 S̲y̲s̲t̲e̲m̲
This causes the cursor to move to the system line.
2.3.5 T̲r̲a̲n̲s̲a̲c̲t̲i̲o̲n̲ ̲P̲r̲o̲c̲e̲s̲s̲i̲n̲g̲
2.3.5.1 E̲n̲t̲e̲r̲
This causes some of the current pages stored in the
VDU to be transmitted to the host.
2.3.5.2 C̲a̲n̲c̲e̲l̲
This causes the current transaction to be annulled
and the resources associated with the partly completed
transaction to be released for use by other transactions.
2.3.5.3 S̲u̲s̲p̲e̲n̲d̲
Functions as described in the SRS (Section 3.2.3.3.c)
2.3.5.4 D̲e̲l̲e̲t̲e̲ ̲a̲n̲d̲ ̲P̲r̲e̲s̲e̲n̲t̲ ̲M̲e̲s̲s̲a̲g̲e̲
This causes the currently displayed item on the screen
to be deleted and the next item in the queue to be
received on the VDU when in receive/response mode.
If there are no items in the queues, the system gives
response message no. 29.
2.3.5.5 K̲e̲e̲p̲ ̲a̲n̲d̲ ̲P̲r̲e̲s̲e̲n̲t̲ ̲M̲e̲s̲s̲a̲g̲e̲
This causes the item currently on the screen to be
kept in the queue and the next item from the queue
displayed. This command is only valid in receive/response
mode.
2.3.5.6 D̲i̲s̲p̲l̲a̲y̲ ̲E̲r̲r̲o̲r̲ ̲M̲e̲s̲s̲a̲g̲e̲
The error code (ref. app. B) entered as one parameter
for this command will cause the system to return the
selected error message in the response line.
Entry of error numbers not used will cause the system
to display response message no. 47.
If data entered are invalid response message no. 65
is returned. If data consist of more than one parameter
response message no. 38 is returned.
2.3.5.7 P̲r̲i̲n̲t̲
This causes the entire received item, part of which
is currently on the VDU screen, to be printed on the
logically associated printer.
2.3.5.8 R̲e̲t̲u̲r̲n̲ ̲t̲o̲ ̲C̲u̲r̲r̲e̲n̲t̲ ̲M̲e̲n̲u̲
This causes the system to send to the VDU the menu
which led to the present format i.e. one of the user
menus.
2.3.5.9 D̲i̲s̲p̲l̲a̲y̲ ̲P̲L̲A̲ ̲T̲e̲x̲t̲
The PLA reference number entered as a parameter for
this command will cause the system to return the selected
PLA text in the response line.
If data entered are not 4 digits response message no.
19 is displayed.
If more than one parameter is entered response message
no. 38 is displayed.
If the entered PLA reference no. is not recognized
the system response will be response message no. 27.
2.3.6 S̲p̲e̲c̲i̲f̲i̲c̲ ̲C̲o̲m̲m̲a̲n̲d̲s̲
The commands which are specific to a format are described
with that format (see also appendix C). The commands
are always in the form of four letter mnemonic.
2.4 C̲U̲R̲S̲O̲R̲ ̲C̲O̲N̲T̲R̲O̲L̲
A cursor is available to help the user entering data
on the VDU in the unprotected fields. The cursor can
be moved to any position of the screen by the use of
the up, down, left, and right keys.
The initial position of the cursor will be on the first
character of the first unprotected fields in the format
area.
2.5 C̲O̲M̲M̲A̲N̲D̲ ̲V̲A̲L̲I̲D̲A̲T̲I̲O̲N̲
Incorrect entry in the command line will cause the
system to return response message no. 1 or no. 39.
If no data are entered in command line the cursor is
repositioned at the start of the command line.
If the user has no capability for the transaction requested
response message no. 41 is returned.
If a command with no parameters attached is entered
and parameters are present response message 38 is returned.
If a command with maximum one parameter attached is
entered, and the parameter is incorrect, response message
39 is returned.
If a parameter is too long, i.e. two many characters,
response message no. 37 is returned.
If a command with parameter attached is entered and
the number of parameters are incorrect response message
no. 38 or no. 40 is returned. No. 38 is used if too
many parameters are entered, no. 40 if one parameter
is missing.
If more than one response message, concerning validation
of commands with more than one parameter attached (i.e.
RETV, DELM) is to be used, the system will, after validation
display the error code numbers in the response line
just below the incorrect parameter.
3̲ ̲ ̲U̲S̲E̲R̲ ̲T̲R̲A̲N̲S̲A̲C̲T̲I̲O̲N̲ ̲U̲S̲I̲N̲G̲ ̲V̲D̲U̲
3.1 O̲V̲E̲R̲V̲I̲E̲W̲
The user transaction is described using an overall
dialogue diagram, a dialogue description and a set
of VDU layout forms. The validation checks on the user
entered data and the subsequent error outputs are also
described.
3.1.1 V̲a̲l̲i̲d̲a̲t̲i̲o̲n̲
Full semantic validation as specified within each format
takes place only after data-entry is complete (or has
reached a convenient break-point such as the end of
the message-header). Semantic validation is
automatic. During actual data-entry, validation will
be restricted to simple syntax-checking such as can
be achieved without reference to system tables (e.g.
SIC, PLA lists) and within the VDU itself. This allows
the user to prepare a message very rapidly and yet
with full confidence that it will be thoroughly validated
later, before being sent for release.
After a format is validated, format compression will
occur, i.e. repeated unused lines are suppressed. Subsequent
retrieval for display of this completed format will
show the compressed version.
The user shall be allowed 5 attempts to enter the correct
information and pass validation. If he does not succeed
then he is presented with error 13 and the current
transaction is terminated.
3.1.2 E̲r̲r̲o̲r̲ ̲I̲n̲d̲i̲c̲a̲t̲i̲o̲n̲
a) During the syntax validation of the data-entry,
the errors are indicated by the terminal. No further
information is needed, since the validation will
be limited to checking mandatory/optional and alpha/numeric/alphanumeric
fields, and the error should be self-evident.
b) After semantic validation, the message is presented
at the user's VDU and the errors are indicated
by means of error numbers in the left-hand margin.
The fields in error will be highlighted. If the
user wants an explanation of the error-number,
he can issue the error display command.
c) In some cases specific user direction will be presented
on the response line.
d) If the limit (20) for the number of error indications
that can be displayed simultaneously is reached,
a special error code, i.e. (XXX) meaning "more
errors" is displayed. If two fields or more on
the same line are in error an appropriate error
code for the last field at the line is displayed
in the margin area. The user shall then correct
the errors indicated and press ENTER in order to
get the remaining errors displayed.
3.1.3 T̲r̲a̲n̲s̲a̲c̲t̲i̲o̲n̲ ̲I̲d̲e̲n̲t̲i̲t̲y̲
This field is common to all formats. It is output by
the system to identify the transaction for logging
and statistical purposes.
It states the Terminal identity, Serial number of the
transaction and Time stamp of the transaction.
The full description is given in Appendix A.
3.1.4 I̲t̲e̲m̲ ̲R̲e̲f̲e̲r̲e̲n̲c̲e̲ ̲I̲d̲e̲n̲t̲i̲t̲y̲
This field is common to the formats related to retrievable
items. It contains a serial number which together with
a time stamp will be a unique identification of an
item.
3.1.5 D̲a̲t̲a̲ ̲E̲n̲t̲r̲y̲
3.1.5.1 F̲i̲e̲l̲d̲s̲
Fields are fixed length parts of the VDU screen with
a maximum of one line.
The unprotected fields are reserved for the user so
he can enter his data.
The protected fields are reserved for the system.
3.1.5.2 D̲a̲t̲a̲ ̲E̲n̲t̲r̲y̲ ̲D̲e̲s̲c̲r̲i̲p̲t̲i̲o̲n̲
The data is entered at the cursor position within the
unprotected fields. These are indicated to the user
by underlining or inverse video. When a field is completed,
the beginning of the next field can be accessed by
using the "next field key".
To help fast editing this key will go in repetition
mode if held down.
Similarly the beginning of the previous field is accessed
by the previous field key.
If the user skips a mandatory field, he will be warned.
3.1.6 E̲x̲i̲t̲ ̲C̲o̲n̲d̲i̲t̲i̲o̲n̲s̲
During a transaction, the user may exit the transactions
by using cancel or suspend at any point. The operation
of cancel and suspend for each format is given in the
SRS (section 3.2.3.3).
At the end of a transaction the user may be prompted
to take action and be presented with the current menu
or, if no action is prompted, he will automatically
be presented with the current menu.
However, in the case of receive mode only explicit
use of the "return to menu" function will result in
a display of the current menu. Details of the exit
conditions for each format are given in section 3,
4, and 5.
FORMAT K1 SIGN - ON…01…FIGURE 3.2-1
3.2 S̲I̲G̲N̲ ̲O̲N̲
3.2.1 S̲t̲a̲n̲d̲a̲r̲d̲ ̲L̲a̲y̲o̲u̲t̲
When a VDU is activated by turning the locking key
to ON, the system puts out a standard layout (K1-1)
on the VDU. If a sign-on is wanted, the user shall
depress the SYSTEM key and enter the command SION.
3.2.2 I̲d̲e̲n̲t̲i̲f̲i̲c̲a̲t̲i̲o̲n̲ ̲C̲o̲d̲e̲ ̲a̲n̲d̲ ̲P̲a̲s̲s̲w̲o̲r̲d̲
The system prompts the user for the identification
code and the password. The user shall enter the ID
code and password in the system line.
On entry the characters in the identification code
and password are not displayed.
3.2.2.1 V̲a̲l̲i̲d̲a̲t̲i̲o̲n̲
The system checks each entry for validity. If either
one or both are invalid, the system will respond by
display error message 1 in the system line. The field
in error will not be high-lighted in this case.
The user can enter his ID code and password a second
time and the validation described above is repeated.
If still invalid the user has one more chance to enter
the correct ID code and password. If invalid a third
time, system responds by displaying "VDU BLOCKED" on
the system line. This ends the sign-on transaction
for this user and the terminal will be blocked. If
both ID code and password are valid, the main menu
will appear on the VDU screen.
FIGURE 3.2-2
FIGURE 3.2-3
FORMAT - USER MENU
FIGURE 3.3-1
3.3 U̲S̲E̲R̲ ̲M̲E̲N̲U̲
3.3.1 U̲s̲e̲
The user menu is presented after successful sign on
and represents the first level functions which the
user may perform.
The user selects one of the options from the menu by
means of entering a command.
For user convenience the commands to be entered are
displayed on the screen.
These commands may also be used at the end of a transaction
where the user wishes to proceed directly to another
transaction bypassing the user menu.
3.3.1.2 V̲a̲l̲i̲d̲a̲t̲i̲o̲n̲
If the entry is valid then the system replies by displaying
the appropriate format for the selected function.
If the entry is invalid, then the system replies by
representing the user menu format together with the
error message in the system response line.
An invalid command results in error 1.
FIGURE 3.3-1
NEW MESSAGE PREPARATION…01…FORMAT A
FIGURE 3.4-1
3.4 N̲E̲W̲ ̲M̲E̲S̲S̲A̲G̲E̲ ̲P̲R̲E̲P̲A̲R̲A̲T̲I̲O̲N̲ ̲(̲F̲O̲R̲M̲A̲T̲ ̲A̲)̲
3.4.1 E̲n̲t̲r̲y̲ ̲o̲f̲ ̲U̲s̲e̲r̲ ̲D̲a̲t̲a̲ ̲(̲A̲-̲1̲)̲
3.4.1.1 I̲t̲e̲m̲ ̲R̲e̲f̲e̲r̲e̲n̲c̲e̲ ̲I̲d̲e̲n̲t̲i̲t̲y̲
The system will output an identity which is the key
on which this message is retrievable by the user until
the message is released.
3.4.1.1.a M̲e̲s̲s̲a̲g̲e̲ ̲T̲y̲p̲e̲
The system will output message type equal to zero.
Refer to section 3.9.
3.4.1.2 C̲l̲a̲s̲s̲i̲f̲i̲c̲a̲t̲i̲o̲n̲ ̲(̲M̲a̲n̲d̲a̲t̲o̲r̲y̲)̲
The user will enter the classification of the message
he is preparing. The system will check to ensure that
this classification is within the security profile
of both the terminal and the user and will present
this classification in the VDU header of A-2 after
validation of A-1. If the entry is not one of the recognized
entries, then error 3 is returned.
If the classification selected is higher than the security
profile of the terminal and/or the user a system response
message 4 is presented. This validation is performed
at the end of the header information entry.
3.4.1.3 S̲p̲e̲c̲i̲a̲l̲ ̲H̲a̲n̲d̲l̲i̲n̲g̲ ̲(̲O̲p̲t̲i̲o̲n̲a̲l̲)̲
The user can enter upto two special handling categories,
if appropriate. If, however, NATIONAL EYES ONLY is
entered, the first field shall contain EE and the second
field contain a 2-letter acronym for the nationality.The
system will check the special category selected against
the security profile of both the terminal and the user.
The system will also check the selected special category
against the security
classification selected to ensure that the following
combination does not exist: NATO Unclassified and any
special category except "national" eyes only. This
validation is performed at the end of the header information
and if invalid error code 64 will be returned.
If operator is not allowed to use the entered special
handling, then the system returns error code 4.
3.4.1.4 M̲e̲s̲s̲a̲g̲e̲ ̲H̲a̲n̲d̲l̲i̲n̲g̲ ̲I̲n̲s̲t̲r̲u̲c̲t̲i̲o̲n̲s̲ ̲(̲O̲p̲t̲i̲o̲n̲a̲l̲)̲
The user may enter any message handling instructions
(operating signals) in the 50 character long field.
A message handling instruction consists of a 3-letter
code plus a parameter, if applicable. The field will
not be validated.
The user can request help for entry of a message handling
instruction by entering a "Y" (YES) in the field "DISPLAY-Enter
Y". This field is a directive to the system and not
part of the message. After entry of the header information
and validation of the data the system will if requested
display twenty message handling instructions and prompt
the user for an entry (format A1-3).
3.4.1.5 P̲r̲e̲c̲e̲d̲e̲n̲c̲e̲;̲ ̲A̲c̲t̲i̲o̲n̲ ̲(̲M̲a̲n̲d̲a̲t̲o̲r̲y̲)̲
The user should enter the precedence with which the
message will be transmitted to action addressees. Invalid
precedences will generate error 6 after validation.
3.4.1.6 P̲r̲e̲c̲e̲d̲e̲n̲c̲e̲;̲ ̲I̲n̲f̲o̲ ̲(̲M̲a̲n̲d̲a̲t̲o̲r̲y̲ ̲i̲f̲ ̲t̲h̲e̲r̲e̲ ̲a̲r̲e̲ ̲I̲n̲f̲o̲ ̲a̲d̲d̲r̲e̲s̲s̲e̲e̲s̲)̲
The user enters the precedence with which the message
will be transmitted to info addressees. Validation
is as discussed in 3.4.1.5 above. If the info precedence
is higher than the action then this invalid condition
is denoted by error 7. Invalid precedences will generate
error 6 after validation.
3.4.1.7 C̲o̲o̲r̲d̲i̲n̲a̲t̲i̲o̲n̲ ̲(̲O̲p̲t̲i̲o̲n̲a̲l̲)̲
The user may enter the staff cell designators (SCDs)
of the staff cell(s) with whom he will coordinate.
Up to ten, three letter staff cell designators may
be entered. Upon validation, the system will generate
error 8 for invalid SCDs.
Each SCD field is followed by a COORDINATION CHECK
MARK field. This field is used by the user to indicate
that the message has been coordinated with the specific
SCD. The mark can be any character.
The message will be sent for coordination to the SCDs
which are not marked.
3.4.1.8 O̲R̲I̲G̲I̲N̲A̲T̲O̲R̲ ̲S̲C̲D̲ ̲(̲M̲A̲N̲D̲A̲T̲O̲R̲Y̲)̲
The user will enter his SCD. Only one SCD is permitted.
The system will validate the SCD and return error 8
for invalid SCD.
3.4.1.8.1 O̲r̲i̲g̲i̲n̲a̲t̲o̲r̲ ̲I̲d̲e̲n̲t̲i̲f̲i̲c̲a̲t̲i̲o̲n̲ ̲(̲M̲a̲n̲d̲a̲t̲o̲r̲y̲)̲
The user enters the originators name, rank, etc. It
will consist of a 20 character field.
3.4.1.9 L̲o̲c̲a̲l̲ ̲D̲i̲s̲t̲r̲i̲b̲u̲t̲i̲o̲n̲ ̲(̲O̲p̲t̲i̲o̲n̲a̲l̲)̲
The user may enter the SCD(s) (max. 10) of local info
addressees. The system will validate the SCD(s) and
return error 8 for invalid SCDs. If Special Handling
Designators is DD or YY local distribution SCD's are
not allowed. Error code 61 is returned.
3.4.1.10 F̲r̲o̲m̲ ̲(̲M̲a̲n̲d̲a̲t̲o̲r̲y̲)̲
The user must enter the name of his headquarters using
plain language address (PLA), or PLA reference number.
Invalid entry returns error 9.
3.4.1.11 T̲o̲ ̲(̲M̲a̲n̲d̲a̲t̲o̲r̲y̲)̲
3.4.1.11.1 T̲o̲ ̲A̲c̲t̲i̲o̲n̲ ̲(̲O̲p̲t̲i̲o̲n̲a̲l̲)̲
The user may enter the address(es) of the intended
action addressees. The user should begin with Address
Indicator Groups (AIGs)/Address Groups (AGs), if any.
This should be followed with PLAs and/or PLA reference
numbers. For invalid AIGs the system will generate
error 10 after the validation process. If the PLA entered
is not in the current PLA table then error 9 is returned.
The user may mark the PLA with a preceding X/ which
will cause the message to be directed to the MSO.
The user can also mark the PLA with a preceding ZEN/
which will cause the PLA to be ignored, when the message
is sent.
If an AIG/AG is entered after a PLA error code no.
60 is returned.
There is one entry per line.
3.4.1.11.2 T̲o̲ ̲I̲n̲f̲o̲ ̲(̲O̲p̲t̲i̲o̲n̲a̲l̲)̲
The same procedure is used as described in 3.4.1.11.1.
Either one Action or Info addressee is mandatory.
3.4.1.12 E̲x̲e̲m̲p̲t̲ ̲(̲O̲p̲t̲i̲o̲n̲a̲l̲)̲
The user should enter the PLA's, and/or PLA reference
number of the addresses to be excluded from any AIG(s)
he has used in the TO line. If invalid then error 9
is returned.
If the entry is not part of one of the AIGs in the
TO line then error 30 is returned.
3.4.1.13 S̲u̲b̲j̲e̲c̲t̲ ̲I̲n̲d̲i̲c̲a̲t̲o̲r̲ ̲C̲o̲d̲e̲ ̲(̲S̲I̲C̲)̲ ̲(̲M̲a̲n̲d̲a̲t̲o̲r̲y̲)̲
The user must enter the three letter SIC(s) for this
message. Up to three SICs may be entered. The system
will generate reply error 8 for any invalid SIC(s)
after validation. The format of an exercise SIC is
3 alpha characters. The first is "A", the second is
in the range E to Z and the third is in the range A
to Z.
3.4.1.14 E̲X̲E̲R̲/̲O̲P̲E̲R̲ ̲(̲O̲p̲t̲i̲o̲n̲a̲l̲)̲
The user may enter an exercise/operation name which
must begin with the letters, "EXER/" or "OPER/". The
user entered variable shall override the specification
made by the supervisor, if any. Any invalid entry will
result in the generation of error 12 after validation.
For "EXER/" the variable must not exceed 77 characters
including "EXER/". For "OPER/" the variable must not
exceed 106 including "OPER/".
3.4.1.15 V̲a̲l̲i̲d̲a̲t̲i̲o̲n̲
The user shall depress the ENTER key. The system will
validate user entries as described above and generate
system response message(s) for any invalid entries.
The user will have to re-enter data for invalid entries
and having edited all the fields in error depress the
enter key. The validation process will be repeated
until all entries are valid. He cannot continue the
preparation until all errors have been removed.
The user shall be allowed 5 attempts to enter the information.
If he does not succeed then he is presented with error
13 and the transaction is terminated.
The format shall be compressed but not converted at
this stage. The blank repeatable lines inserted in
the format will be suppressed, but the conversion of
the short-form user entries into full text will not
be performed.
If "EXER/" is entered and no exercise SIC is entered,
then error 59 is displayed.
FIGURE 3.4-2
FIGURE 3.4-3
Figure 3.4-4
3.4.2 E̲n̲t̲r̲y̲ ̲o̲f̲ ̲U̲s̲e̲r̲ ̲D̲a̲t̲a̲ ̲(̲A̲-̲2̲)̲
3.4.2.1 I̲n̲t̲e̲r̲n̲a̲l̲ ̲H̲a̲n̲d̲l̲i̲n̲g̲ ̲I̲n̲s̲t̲r̲u̲c̲t̲i̲o̲n̲ ̲(̲O̲p̲t̲i̲o̲n̲a̲l̲)̲
The user may enter free text, to describe the internal
handling instruction.
3.4.2.2 S̲u̲b̲j̲e̲c̲t̲ ̲(̲M̲a̲n̲d̲a̲t̲o̲r̲y̲)̲
The user should enter the subject of the message in
free text.
If no subject is entered error code 14 is returned.
3.4.2.3 T̲e̲x̲t̲ ̲(̲M̲a̲n̲d̲a̲t̲o̲r̲y̲)̲
The user should compose his text in this field. At
the end of text entry the ENTER key is pressed. When
the host receives A-2 format compression takes place
prior to the output of A-3.
If no text is entered error code 14 is returned.
FIGURE 3.4-5
FIGURE 3.4-6
3.4.3 M̲e̲s̲s̲a̲g̲e̲ ̲P̲r̲o̲c̲e̲s̲s̲i̲n̲g̲ ̲(̲A̲-̲3̲)̲
The user may now make a decision as to the action he
will take. The choice is made by entering data in one
of the fields provided and press the ENTER key.
The possibilities are
a) dispatch the message for coordination
b) send for release to the release position
c) defer the message for later continuation of preparation
d) append a message section from another message
On completion of a, b, or c the system will return
to the user menu. The description of the use of the
append message function is given in 3.5.
On completion of a), if some of the specified coordination
SCDs cannot be reached, then the system will identify
these SCDs by a display in the response line.
If b) is unsuccessful, i.e. the release position cannot
be reached, then system response message 34 will be
returned in the response line.
FIGURE 3.4-7
3.5 A̲P̲P̲E̲N̲D̲ ̲M̲E̲S̲S̲A̲G̲E̲
3.5.1 A̲p̲p̲e̲n̲d̲ ̲M̲e̲s̲s̲a̲g̲e̲
This enables the user to add a section of another message
to a message in preparation to compose a new outgoing
message.
The system shall build a new message in the following
way:
To the message header and the text part of the current
message will be added the extracted section of the
text part of the other message.
The user inserts the item type, the time stamp, the
five digit item reference identification, the staff
cell, and the two line numbers defining the section
of the message. If no line numbers are specified, then
the entire text part of the message will be appended.
Line number 1 is the first line of the text.
After the "reference" input, the ENTER key is pressed.
A security interrogation will be performed, if appropriate.
If the reference is invalid then format A-3 is presented
for the user.
On completion of the append, format A2 of the message
in preparation will be represented on the screen with
the new text added.
If the referenced message is in the off-line data base,
then the main menu will be presented and a notification
will be placed in the System Response queue when the
append is completed. From the point in time where append
has been requested and until append has been completed
no editing of the original message is possible.
3.5.2 V̲a̲l̲i̲d̲a̲t̲i̲o̲n̲
Validation will be carried out as described in section
3.4.3.3.
This page Intentionally Left Blank.
This page intentionally left blank.
If the line numbers specified have no meaning (the
line number does not exist in the referenced message),
then the entire text part will be concatenated.
System information is displayed as for transaction
concerning Retrieval, refer section 3.11.
3.5.3 R̲e̲s̲p̲o̲n̲s̲e̲ ̲T̲e̲x̲t̲
If an offline append has been completed and the message
to which append was requested has been deleted by Supervisor
then response message no. 52 will be displayed when
continuation of preparation is started.
If an off-line append has been completed, but no item
was found under specified retrieval key, response message
no. 18 will be displayed when continuation of preparation
is started.
No append will be executed in these cases. Other system
information concerning append as for transaction concerning
Retrieval (see section 3.11).
FIGURE 3.6-1
3.6 N̲E̲W̲ ̲C̲O̲M̲M̲E̲N̲T̲ ̲P̲R̲E̲P̲ ̲-̲ ̲G̲1̲
3.6.1 U̲s̲e̲
This format is used to prepare comments to be sent
to local CAMPS Staff Cells. On presentation the format
contains the TRANSACTION ID and ITEM REFERENCE IDENTITY
as in format A.
3.6.1.1 C̲l̲a̲s̲s̲i̲f̲i̲c̲a̲t̲i̲o̲n̲,̲ ̲S̲p̲e̲c̲i̲a̲l̲ ̲H̲a̲n̲d̲l̲i̲n̲g̲,̲ ̲P̲r̲e̲c̲e̲d̲e̲n̲c̲e̲
As for Format A. There is no Precedence Info line.
3.6.1.2 O̲r̲i̲g̲i̲n̲a̲t̲o̲r̲ ̲S̲C̲D̲
As for Format A.
3.6.1.2.1 O̲r̲i̲g̲i̲n̲a̲t̲o̲r̲ ̲I̲d̲e̲n̲t̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
As for Format A.
3.6.1.3 L̲o̲c̲a̲l̲ ̲D̲i̲s̲t̲r̲i̲b̲u̲t̲i̲o̲n̲ ̲(̲M̲a̲n̲d̲a̲t̲o̲r̲y̲)̲
Validation as for format A. There are ten entry fields.
3.6.1.4 V̲a̲l̲i̲d̲a̲t̲i̲o̲n̲
At this point the user presses the ENTER KEY which
causes the validation to be carried out on the comment
header.
The error messages or validation are as for the relevant
lines of format A.
3.6.2 T̲e̲x̲t̲ ̲(̲M̲a̲n̲d̲a̲t̲o̲r̲y̲)̲ ̲G̲1̲-̲2̲
This is unstructured text. If more lines for text are
required than are presented, the user may use INSERT
to expand the format.
On completion of the text the user should press the
ENTER key. The compression of the comment format follows
this operation.
3.6.3 C̲o̲m̲m̲e̲n̲t̲ ̲P̲r̲o̲c̲e̲s̲s̲i̲n̲g̲ ̲G̲1̲-̲3̲
The user may send his comment to addressees or defer.
FIGURE 3.6-2
FIGURE 3.6-3
FIGURE 3.6-4
FIGURE 3.7-1
3.7 C̲O̲N̲T̲I̲N̲U̲E̲ ̲M̲E̲S̲S̲A̲G̲E̲ ̲P̲R̲E̲P̲A̲R̲A̲T̲I̲O̲N̲ ̲-̲ ̲C̲1̲
3.7.1.1 U̲s̲e̲
This format is used when it is required to continue
the preparation of a message which was suspended, deferred
or which has been sent for coordination and requires
editing as a result of the returned comments. The user
inserts the command in the command line and format
C1-1 will be presented. The user may also insert both
the command and the item reference identity and the
message will be presented.
The system then retrieves the message and presents
it in a short-form and compressed format A on the screen
(i.e. trailing space-lines will be removed). Format
A1-1 appears first.
The user may continue with the message preparation
function as described under the NEW MESSAGE PREPARATION
format.
Any change of the format or its contents require re-validation.
The user may only continue preparation of messages
originally prepared by a staff cell associated with
the terminal.
3.7.1.2 V̲a̲l̲i̲d̲a̲t̲i̲o̲n̲
If the reference was to a non-existent message then
error 2 is given.
If the referenced item was not prepared at this terminal
then error code 2 is given.
If a message is not available for further editing because
it has been sent for release then the system will return
error 17. If a message is not available for further
editing because it is awaiting append then the system
will return error 49. If it has been released then
it will return error 2. If the item referred to is
anything but a message then error 20 is returned.
FIGURE 3.7-2
FIGURE 3.8-1
3.8 C̲O̲N̲T̲I̲N̲U̲E̲ ̲C̲O̲M̲M̲E̲N̲T̲ ̲P̲R̲E̲P̲ ̲-̲ ̲G̲3̲
3.8.1.1 U̲s̲e̲
This format is used when it is required to continue
the preparation of a comment which has been partly
prepared but not yet transmitted. The user inserts
the command in the command line and format G3-1 will
be presented. The user may also insert both the command
and the item reference identity and the message will
be presented.
The system then retrieves the comment and presents
it in a short form compressed format G1.
The user can then page through the comment and use
the editing functions. He may also continue with the
comment preparation function as described under NEW
COMMENT PREPARATION.
Any change of the format or its contents will require
re-validation.
The user may only continue comment preparation of a
comment prepared by a staff cell associated with the
terminal.
3.8.1.2 V̲a̲l̲i̲d̲a̲t̲i̲o̲n̲
If the reference is to a non existent comment then
return error 2.
If the referenced item is not prepared at this terminal
then return error 2.
If it has been transmitted then return error 2.
If the item referred to is anything else but a comment
then return error 15.
FIGURE 3.8-2
PREPARE PREFORMATTED MESSAGE
FIGURE 3.9-1
3.9 P̲R̲E̲P̲A̲R̲E̲ ̲P̲R̲E̲D̲E̲F̲I̲N̲E̲D̲ ̲M̲E̲S̲S̲A̲G̲E̲ ̲-̲ ̲M̲(̲x̲)̲
Format layout M-1 (fig 3.9-2) asks for the reference
number (X001 to X200) of the predefined message. The
reference number can also be entered as a parameter
to the command PRPM. The number is validated to ensure
it corresponds to a stored format. Up to 200 formats
may be stored.
The message is presented in format A to the user.
3.9.1 E̲n̲t̲r̲y̲ ̲o̲f̲ ̲D̲a̲t̲a̲-̲P̲a̲r̲t̲ ̲1̲
The header of the predefined message may be presented
partly completed. The fields which require user data
entry are indicated. (See fig. 3.9-3). The rules for
entry of data are the same as for format A (see section
3.4.1.1 to 3.4.1.14).
3.9.1.1 V̲a̲l̲i̲d̲a̲t̲i̲o̲n̲
The validation procedure is the same as described for
format A section 3.4.1.15.
FIGURE 3.9-2
FIGURE 3.9-3
3.9.2 E̲n̲t̲r̲y̲ ̲o̲f̲ ̲D̲a̲t̲a̲-̲P̲a̲r̲t̲ ̲2̲
The text portion shall be designed to assist the user
in preparing the text part of the message. An example
of a text format is given in fig. 3.9-4.
The text portion consists of the following text elements:
- Segments
- Sets
- Fields
3.9.2.1 S̲e̲g̲m̲e̲n̲t̲s̲
Segments are a group of related sets. Each segment
is surrounded with BEGIN/END statements, which indicate
the segment and give it an explicit segment identity
- e.g.:
BEGIN SEGMENT 1
SET ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
SET ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
BEGIN SEGMENT 2
SET ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
SET ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
END SEGMENT 2
SET ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
BEGIN SEGMENT 3
SET ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
SET ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
END SEGMENT 3
END SEGMENT 1
3.9.2.1.1 R̲e̲p̲e̲a̲t̲a̲b̲l̲e̲ ̲S̲e̲g̲m̲e̲n̲t̲s̲
Current segment may be repeated by use of an Insert
command. (As denoted by the cursor which shall be placed
in the first field of the segment).
Segments can be repeated by pressing CONTROL 1, and
be deleted by pressing CONTROL 2.
3.9.2.2 S̲E̲T̲S̲
A set consists of a field or a group of fields. In
front of each set is displayed a set-descriptor which
specifies whether a set is mandatory or optional. The
first line of a Set contains the SET ID and the SET
NAME. The next line(s) contains the field(s).
M SET ID SET NAME
Field 1
Field 2
Field 3
Only optional set may be deleted.
Each Set shall be followed by an empty repeatable line,
where the user can enter free text preceded by a free
text set ID and a "/" and terminated by a "//".
3.9.2.2.1 R̲e̲p̲e̲a̲t̲a̲b̲l̲e̲ ̲S̲e̲t̲s̲
All sets are repeatable. Use of an Insert command will
cause the format of the current Set (as denoted by
the cursor which shall be placed in the first field
of the set) to be repeated immediately after the set.
Sets can be repeated by pressing CONTROL 1, and deleted
by pressing CONTROL 2.
3.9.2.2.2 S̲e̲l̲e̲c̲t̲a̲b̲l̲e̲ ̲S̲e̲t̲s̲
To give the capability of using alternative sets, the
text format shall be defined to include all the alternative
Sets. These Sets will be marked with the set descriptor
S (selection). It is the responsibility of the user
only to use one of the selectable sets.
3.9.2.3 F̲i̲e̲l̲d̲s̲
Each field is preceded by a field name or one or more
spaces. A field or a sub-field is always preceded by
a field descriptor giving the attributes of the fields.
The attributes state whether the field is mandatory
or optional and whether the field is alpha, numeric
or any-character. The number of characters in the field
is also indicated. - e.g.:
Field Name N ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
The system will not correlate the mandatory/optional
specification for a set with the mandatory/optional
specification for a Field. Mandatory fields in an optional
set must be filled in or the set must be deleted.
3.9.2.3.1 R̲e̲p̲e̲a̲t̲a̲b̲l̲e̲ ̲F̲i̲e̲l̲d̲s̲
Repeatable field or group of fields are placed as the
last field(s) of a Set. The first field in a set can
never be repeatable. Repeatable fields are preceded
by the line descriptor R, though for a group only the
first field of the group is marked. Placing the cursor
in the R-marked field and use of the Insert command
will cause the field or group of fields to be repeated.
Fields may be repeated and deleted in the same way
as lines.
3.9.2.3.2 M̲i̲x̲e̲d̲ ̲F̲i̲e̲l̲d̲s̲
Fields can be composed of sub-fields, i.e. character
groups of different types. This is indicated in the
text format by splitting the field into its component
parts each preceded by a field descriptor. There will
be no spaces between each part of the field - e.g.:
Field Name N ̲ ̲ ̲ ̲ ̲ ̲ ̲A ̲ ̲ ̲ ̲ ̲ ̲ ̲N
3.9.2.3.3 S̲e̲l̲e̲c̲t̲a̲b̲l̲e̲ ̲F̲i̲e̲l̲d̲s̲
If a set specifies alternative fields, then all the
fields will be displayed. The fields will be preceded
with the line descriptor S. It is the responsibility
of the user only to use one of the fields.
3.9.2.4 V̲a̲l̲i̲d̲a̲t̲i̲o̲n̲
Syntax validation will take place in accordance with
the descriptions for the lines and fields. If an entry
is invalid, then the user will be warned.
FIGURE 3.9-4
3.9.3 D̲i̲s̲p̲l̲a̲y̲ ̲F̲o̲r̲m̲a̲t̲s̲ ̲o̲f̲ ̲P̲r̲e̲d̲e̲f̲i̲n̲e̲d̲ ̲M̲e̲s̲s̲a̲g̲e̲
Before display of the predefined message in case of
coordination, release, or local distribution the formatted
text, if any, shall be transformed into a display layout.
This layout shall in a compressed form present the
data entered into the formatted text. Set names, field
names, descriptors, and lines included by way of explanation
(e.g. Begin Segment 1) shall be removed. Also not used
lines and sets are removed. Only the Set Identification
and the fields shall be displayed. Each field is separated
by a field separator (/). Each set is terminated by
a "end marker" (//). Each Set shall start on a new
line. A field must not be continued onto a second line.
The continuation of the set from the preceding line
must start with the field marker (/) of the next field.
If a set is repeated, both the set Id and the fields
shall be repeated. Columnar sets, which as the first
character of the set Id contains a number, shall be
displayed in a columnar presentation.
For the layout see fig. 3.9-5.
FIGURE 3.9-5
MESSAGE/COMMENT DELETION
FORMAT P1
FIGURE 3.10-1
3.10 M̲E̲S̲S̲A̲G̲E̲/̲C̲O̲M̲M̲E̲N̲T̲ ̲D̲E̲L̲E̲T̲I̲O̲N̲
This format shall be used to request the system to
delete a message/comment at all stages in the preparation
process. Message submitted for release or awaiting
append and messages which have been released shall
not be deleted automatically, but the request for deletion
shall be forwarded to the supervisor of the system.
The user inserts the command in the command line and
format P1 will be presented. The user may also insert
both the command and the parameters and the message
will be deleted.
The user may only delete items prepared at the terminal
requesting the deletion.
3.10.1 T̲i̲m̲e̲ ̲S̲t̲a̲m̲p̲ ̲(̲M̲a̲n̲d̲a̲t̲o̲r̲y̲)̲
3.10.2 I̲t̲e̲m̲ ̲R̲e̲f̲e̲r̲e̲n̲c̲e̲ ̲I̲D̲
Item reference ID of the message/comment to be deleted
is entered by the user.
3.10.3 S̲t̲a̲f̲f̲ ̲C̲e̲l̲l̲ ̲D̲e̲s̲i̲g̲n̲a̲t̲o̲r̲
The user enters the staff cell designator of the originator
of the message/comment to be deleted.
3.10.4 V̲a̲l̲i̲d̲a̲t̲i̲o̲n̲
After validation security interrogation shall take
place. After deletion has been performed the system
responds with response message 21.
If the reference is to a non-existing item then error
23 is given in the response line.
If the item referenced to is awaiting release the system
shall reply with error 22 and send a deletion request
to the supervisor.
If the item referenced to is awaiting append the system
shall reply with error 49.
If the referenced message has been released the system
shall reply with error 23 and send a deletion request
to the supervisor.
If the message referred to cannot be deleted by the
requestor due to security, then system displays response
message no. 31.
FIGURE 3.10-2
RETRIEVAL…01…FORMAT H
FIGURE 3.11-1
3.11 M̲E̲S̲S̲A̲G̲E̲/̲C̲O̲M̲M̲E̲N̲T̲ ̲R̲E̲T̲R̲I̲E̲V̲A̲L̲ ̲-̲ ̲ ̲H̲
3.11.1 R̲e̲t̲r̲i̲e̲v̲a̲l̲ ̲F̲a̲c̲i̲l̲i̲t̲i̲e̲s̲
3.11.1.1 T̲y̲p̲e̲ ̲o̲f̲ ̲I̲t̲e̲m̲ ̲R̲e̲t̲r̲i̲e̲v̲a̲l̲
The following items are available for retrieval.
a) An outgoing message which has been released and
prepared at the terminal, and the first draft of
a message not yet released.
b) A message prepared at another terminal in the users
CAMPS site, and which on release was locally distributed
to this terminal according to the local distribution
SCDs in the message.
c) A message incoming from another headquarters which
is capable of being delivered at the terminal.
d) A comment prepared at this terminal and transmitted
or a comment received at this terminal.
e) A release notification sent from or to this terminal.
On entering the appropriate command and pressing the
RETURN key the user is presented with a request for
the entry of data required to retrieve the particular
item.
3.11.1.2 U̲s̲e̲ ̲o̲f̲ ̲R̲e̲t̲r̲i̲e̲v̲a̲l̲
Retrieval is based on two reference types:
- Internal references consisting of an item type,
a time stamp, an item reference identity, and a
SCD - uses a command.
- External references consisting of information derivable
from message contents - uses a menu.
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 55 will be displayed in the response
line.
The user is then invited to enter the unique keys by
means of a command.
If more than 10 retrieval requests have turned out
to be off-line the response text no. 63 is displayed.
If Time window reaches beyond one volume response text
nr. 57 is displayed.
If Supervisor has demanded Offline Retrieval Off then
response text no. 58 is displayed.
If response text no. 28 has been displayed then it
might be followed by response text no. 62.
3.11.1.3 R̲e̲t̲r̲i̲e̲v̲e̲ ̲C̲o̲m̲m̲a̲n̲d̲s̲
The user should enter the following parameters in the
command line:
- item type
- time stamp
- item reference identity
- Staff Cell
This will result in a presentation of the unique item
referred to if allowed by security checks.
3.11.1.4 S̲e̲c̲u̲r̲i̲t̲y̲
The user enters a Staff Cell Designator with the retrieval
request. There is a check that:
a) The SCD is one of up to five SCDs associated with
the physical terminal on which the retrieve is
requested.
b) The SCD is one which either originated or is on
the distribution list for an item as specified
in CPS/210/SYS/0001 section 3.2.7..
FIGURE 3.11-2
3.11.2 R̲e̲l̲e̲a̲s̲e̲d̲ ̲O̲u̲t̲g̲o̲i̲n̲g̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲/̲F̲i̲r̲s̲t̲ ̲D̲r̲a̲f̲t̲ ̲o̲f̲ ̲M̲e̲s̲s̲a̲g̲e̲
This format can be used to retrieve outgoing messages
which have been released, and first drafts of messages
not yet released. On release, the first draft is deleted
automatically.
3.11.2.1 R̲e̲l̲e̲a̲s̲e̲d̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲
3.11.2.1.1 T̲i̲m̲e̲ ̲o̲f̲ ̲O̲c̲c̲u̲r̲r̲e̲n̲c̲e̲ ̲(̲T̲O̲C̲)̲ ̲o̲r̲ ̲T̲O̲C̲ ̲W̲i̲n̲d̲o̲w̲ ̲(̲M̲a̲n̲d̲a̲t̲o̲r̲y̲)̲
For a released message this is the TIME STAMP of the
catalogging of the message, as specified in CPS/210/SYS/0001
section 3.2.7.
3.11.2.1.2 D̲T̲G̲ ̲(̲O̲p̲t̲i̲o̲n̲a̲l̲)̲
For a released message this is the DAY TIME GROUP of
the message.
3.11.2.1.3 O̲r̲i̲g̲i̲n̲a̲t̲i̲n̲g̲ ̲H̲Q̲ ̲(̲o̲p̲t̲i̲o̲n̲a̲l̲)̲
The user should enter the PLA or PLA reference number
of the originating HQ.
3.11.2.1.4 O̲r̲i̲g̲i̲n̲a̲t̲i̲n̲g̲ ̲S̲t̲a̲f̲f̲ ̲C̲e̲l̲l̲ ̲(̲M̲a̲n̲d̲a̲t̲o̲r̲y̲)̲
The Staff Cell identity of the originator of the message
is entered.
3.11.2.2 F̲i̲r̲s̲t̲ ̲D̲r̲a̲f̲t̲ ̲o̲f̲ ̲M̲e̲s̲s̲a̲g̲e̲
3.11.2.2.1 T̲i̲m̲e̲ ̲o̲f̲ ̲O̲c̲c̲u̲r̲r̲e̲n̲c̲e̲ ̲(̲T̲O̲C̲)̲ ̲o̲r̲ ̲T̲O̲C̲ ̲W̲i̲n̲d̲o̲w̲ ̲(̲M̲a̲n̲d̲a̲t̲o̲r̲y̲)̲
For a draft this is the time stamp of the completion
of the first draft.
3.11.2.2.2 I̲t̲e̲m̲ ̲R̲e̲f̲e̲r̲e̲n̲c̲e̲ ̲I̲d̲e̲n̲t̲i̲t̲y̲ ̲(̲O̲p̲t̲i̲o̲n̲a̲l̲)̲
3.11.2.2.3 O̲r̲i̲g̲i̲n̲a̲t̲i̲n̲g̲ ̲S̲C̲D̲ ̲(̲M̲a̲n̲d̲a̲t̲o̲r̲y̲)̲
3.11.2.3 V̲a̲l̲i̲d̲a̲t̲i̲o̲n̲
If the DTG entered means a search outside the currently
stored data base then response message 25 is returned.
On completion of the off-line retrieval the retrieved
item or response message is placed in the system response
queue.
If the TOC window is too large then error code 26 is
returned.
If the Item reference identity leads to a search in
the currently stored data base, then response message
28 is returned to assure the user that retrieval is
in progress.
On retrieval completion the catalogue display or the
retrieved item will be delivered to the terminals at
FLASH precedence.
FIGURE 3.11-3
FIGURE 3.11-4
3.11.3 I̲n̲c̲o̲m̲i̲n̲g̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲ ̲f̲r̲o̲m̲ ̲a̲n̲o̲t̲h̲e̲r̲ ̲H̲e̲a̲d̲q̲u̲a̲r̲t̲e̲r̲s̲
This format is used to retrieve incoming messages from
other headquarters which are allowed to be distributed
to the defined Staff Cell. Either TOC or DTG is mandatory,
but both should be entered if known.
3.11.3.1 T̲i̲m̲e̲ ̲o̲f̲ ̲O̲c̲c̲u̲r̲r̲e̲n̲c̲e̲ ̲(̲T̲O̲C̲)̲/̲T̲O̲C̲ ̲W̲i̲n̲d̲o̲w̲ ̲(̲O̲p̲t̲i̲o̲n̲a̲l̲)̲
This is the TIME STAMP of the catalogging of the message.
3.11.3.2 D̲T̲G̲ ̲(̲O̲p̲t̲i̲o̲n̲a̲l̲)̲
This is the Time of Release of the message at the originating
HQ as derived from format line 5 of the incoming message.
3.11.3.3 O̲r̲i̲g̲i̲n̲a̲t̲i̲n̲g̲ ̲H̲Q̲ ̲(̲O̲p̲t̲i̲o̲n̲a̲l̲)̲
This is the PLA or PLA reference number of the originating
HQ.
3.11.3.4 M̲e̲s̲s̲a̲g̲e̲ ̲O̲r̲i̲g̲i̲n̲a̲l̲l̲y̲ ̲D̲i̲s̲t̲r̲i̲b̲u̲t̲e̲d̲ ̲t̲o̲ ̲(̲M̲a̲n̲d̲a̲t̲o̲r̲y̲)̲
The user enters the SCD of the original receiver of
the message.
FIGURE 3.11-5
3.11.4 L̲o̲c̲a̲l̲l̲y̲ ̲D̲i̲s̲t̲r̲i̲b̲u̲t̲e̲d̲ ̲O̲u̲t̲g̲o̲i̲n̲g̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲
3.11.4.1 T̲i̲m̲e̲ ̲o̲f̲ ̲O̲c̲c̲u̲r̲r̲e̲n̲c̲e̲ ̲o̲r̲ ̲T̲O̲C̲ ̲W̲i̲n̲d̲o̲w̲ ̲(̲M̲a̲n̲d̲a̲t̲o̲r̲y̲)̲
This is the Time Stamp of catalogging.
3.11.4.2 D̲T̲G̲ ̲(̲O̲p̲t̲i̲o̲n̲a̲l̲)̲
This is the DTG of the message.
3.11.4.3 O̲r̲i̲g̲i̲n̲a̲t̲i̲n̲g̲ ̲H̲e̲a̲d̲q̲u̲a̲r̲t̲e̲r̲s̲ ̲(̲O̲p̲t̲i̲o̲n̲a̲l̲)̲
This is the PLA or PLA reference number of the originating
HQ.
3.11.4.4 M̲e̲s̲s̲a̲g̲e̲ ̲O̲r̲i̲g̲i̲n̲a̲l̲l̲y̲ ̲D̲i̲s̲t̲r̲i̲b̲u̲t̲e̲d̲ ̲T̲o̲ ̲(̲M̲a̲n̲d̲a̲t̲o̲r̲y̲)̲
Enter SCD of original recipient of message.
3.11.4.5 V̲a̲l̲i̲d̲a̲t̲i̲o̲n̲
Validation results are as for the same fields in the
outgoing message format (section 3.11.2.3).
FIGURE 3.11-5
3.11.5 C̲o̲m̲m̲e̲n̲t̲s̲ ̲S̲E̲N̲T̲/̲R̲E̲C̲E̲I̲V̲E̲D̲ ̲a̲t̲ ̲t̲h̲i̲s̲ ̲T̲e̲r̲m̲i̲n̲a̲l̲
3.11.5.1 T̲i̲m̲e̲ ̲S̲t̲a̲m̲p̲/̲T̲i̲m̲e̲ ̲W̲i̲n̲d̲o̲w̲ ̲(̲M̲a̲n̲d̲a̲t̲o̲r̲y̲)̲
The time of the transmit transaction for comments.
3.11.5.2 I̲t̲e̲m̲ ̲R̲e̲f̲e̲r̲e̲n̲c̲e̲ ̲I̲d̲e̲n̲t̲i̲t̲y̲ ̲(̲O̲p̲t̲i̲o̲n̲a̲l̲)̲
The number associated with the comment as a reference
number.
3.11.5.3 O̲r̲i̲g̲i̲n̲a̲t̲i̲n̲g̲/̲R̲e̲c̲e̲i̲v̲i̲n̲g̲ ̲S̲C̲D̲ ̲(̲M̲a̲n̲d̲a̲t̲o̲r̲y̲)̲
Enter the SCD which originated or which received the
original comment.
3.11.5.4 V̲a̲l̲i̲d̲a̲t̲i̲o̲n̲
Validation results are as for the same fields in the
outgoing message format (section 3.11.2.3).
FIGURE 3.11-6
3.11.6 R̲e̲t̲r̲i̲e̲v̲e̲ ̲R̲e̲l̲e̲a̲s̲e̲ ̲N̲o̲t̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
Release notifications resulting from successful or
unsuccessful applications for release may be retrieved.
The releaser and the receiver of the release notifications
must be able to retrieve them.
3.11.6.1 T̲i̲m̲e̲ ̲o̲f̲ ̲O̲c̲c̲u̲r̲r̲e̲n̲c̲e̲ ̲(̲T̲O̲C̲)̲ ̲o̲r̲ ̲T̲O̲C̲ ̲W̲i̲n̲d̲o̲w̲ ̲(̲M̲a̲n̲d̲a̲t̲o̲r̲y̲)̲
This is the time of the transmission of the release
notification to the user.
3.11.6.2 I̲t̲e̲m̲ ̲R̲e̲f̲e̲r̲e̲n̲c̲e̲ ̲I̲D̲ ̲(̲O̲p̲t̲i̲o̲n̲a̲l̲)̲
3.11.6.3 O̲r̲i̲g̲i̲n̲a̲t̲i̲n̲g̲ ̲S̲t̲a̲f̲f̲ ̲C̲e̲l̲l̲ ̲(̲M̲a̲n̲d̲a̲t̲o̲r̲y̲)̲
The user enters the identity of the SCD which originated
the message and received the original Release Notification.
The releaser must enter his SCD.
3.11.6.4 V̲a̲l̲i̲d̲a̲t̲i̲o̲n̲
Validation results are as for the same fields in the
outgoing message format (section 3.11.2.3).
FIGURE 3.11-8
3.11.7 U̲s̲e̲r̲ ̲C̲a̲t̲a̲l̲o̲g̲u̲e̲ ̲D̲i̲s̲p̲l̲a̲y̲
If several items fit the retrieval keys then a catalogue
of these items within the time window will be presented.
Cataloque display is limited to the size of a message
i.e. 12.000 characters.
The fields in the user catalogue are:
3.11.7.1 I̲t̲e̲m̲ ̲T̲y̲p̲e̲
3.11.7.2 T̲i̲m̲e̲ ̲S̲t̲a̲m̲p̲
This is the time stamp defined for the item type.
3.11.7.3 I̲t̲e̲m̲ ̲R̲e̲f̲e̲r̲e̲n̲c̲e̲ ̲I̲d̲e̲n̲t̲i̲t̲y̲
3.11.7.4 O̲r̲i̲g̲i̲n̲a̲t̲o̲r̲
For incoming and released outgoing and locally distributed
outgoing messages, this is the PLA reference number
of the originating HQ. For items of type C, N, and
D it is the SCD of the originator.
3.11.7.5 D̲T̲G̲
This is the DTG of an incoming or outgoing message.
3.11.7.6 S̲I̲C̲
Three SICs are shown.
Fig. 3.11-9
Fig. 3.12-1
