top - download
⟦3dab79acd⟧ Wang Wps File
Length: 53932 (0xd2ac)
Types: Wang Wps File
Notes: Spelunked
Names: »~ORPHAN56.00«
Derivation
└─⟦1304ed705⟧ Bits:30006073 8" Wang WCS floppy, CR 0030A
└─ ⟦this⟧ »~ORPHAN56.00«
WangText
…00……00……00……00…8…02……00……00…8
7…0b…3…0c…0…05…/…0a…/…00…/…05….…0a….…01….…05…-…08…-…09…-…0b…-…0f…- ,…08…,…0c…'…09…'…0c…'
&…08…&…0d…&…0e…& &…05…&…06…&…07…%…0b…%…0c…%…0d…%
$…0a…$…00…$…06… …05… …06……86…1 …02… …02… …02…
…02…CPS/230/ICD/0001
…02…810525…02……02…
USER PROCEDURES AND ASSOCIATED FORMATS
…02…ISSUE 3.1…02…CAMPS
1 SCOPE ........................................
6
1.1 REFERENCE DOCUMENTS ......................
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 Headr 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.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 FormatEdit ..........................
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 ..............
6
2.3.3.2 Next Field .......................
17
2.3.3.3 Previous Field ...................
17
2.3.4 Screen Manipulation ..................
17
2.3.4.1 Command ..........................
17
2.3.4.2 Return ..........................
17
2.3.4.3 Page-On ..........................
17
2.3.4.4 Page-Back ........................
17
2.3.4.5 Scroll On ........................
18
2.3.4.6 Scroll Down ......................
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 .......
19
2.3.5.5 Keep and Present Message .........
19
2.3.5.6 Display Error Message ............
19
2.3.5.7 Print ............................
19
.3.5.8 Return to Current Menu ...........
19
2.3.6 Specific Commands ....................
19
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) ................
44
3.6 NE 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 (FORMA P1) .....
71
3.11 MESSAGE/COMMENT RETRIEVAL (FORMAT H) .....
75
3.12 OUTGOING MESSAGE STATUS (FORMAT N) .......
92
3.13 DELIVERY STATUS (FORMAT R) ...............
97
3.14 SIGN-OFF (FORMAT K2) .....................
100
3.15 SECURTY PROCEDURES (FORMAT I) ........... 102
4 DISPLAY FORMATS ..............................
104 to 121
4.1 GENERAL ..................................
104
4.2 COORDINATION (FORMAT B), OUTGOING MESSAGE
(FORMATE2), 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
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 ESSAGE RELEASE STATUS (FORMAT Q) ........ 132
6 PREPARATION OF COMMAND AND CONTROL DISPLAY ...
134
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 OUTPUT ...........................
135
7.4 MESSAGE PRINT OUT ........................
136
7.5 ELECTRICAL INTERFACE .....................
13
7.6 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 CORRETION ................... 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 ONL
PRINTER ......................................
139
APPENDIX A - FIELD/ELEMENT DICTIONARY ...........
140 to 144
APPENDIX B - USER PROCEDURES RESPONSE MESSAGES/
ERROR CODES ........................
145
APPENDIX C - SPECIFIC COMMADS .................. 146…86…1
…02… …02… …02… …02…
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 relatio 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 ollowing 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 interpretatio 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. 175
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 te 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 i 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 ystem 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 theSystem 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 useble 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-Manatory,
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 s 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
ued 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 lne
- Response 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-forat 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 classifiation
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..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, or display
on a terminal will be shown. Each category is identified
by an alpha descriptor with a two numeric field fo
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 umber
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, outgoing messages, and
results of retrieva.
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 and entry of parameters.
Commands will be entered by pressing a "Command" function
key which will cause the cursor to jump to the Commnd
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 for alpha characters followed
by a parameter field, if required. Commas 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 charaters.
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 ocupy 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
SPACE ERROR CODE SPACE TEXT LINE NUMBER
LINE DESCRIPTOR
The user area consists of the remaining 70 characters.
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 o 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̲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.…86…1
…02… …02… …02… …02…
Figure 2.2-1…01…SCREEN LAYOUT…86…1 …02… …02… …02… …02…
= 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̲…86…1 …02… …02… …02… …02…
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 fou 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 OVRWRITE
NEXT FIELD
PREVIOUS FIELD
- Screen Manipulations COMMAND
RETURN
PAGE-ON
PAGE-BACK
SCROLL-ON
SCROLL-BACK
- Transaction Processing ENTER
CANCEL
SUSPEND
DELETE AND PRESENT MESSAGE
KEEP ND 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 here 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 wasdepressed.
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 ae 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 ENTE 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 previousfield.
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̲-̲O̲n̲
This causes the next page of nformation 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 firs
page of a format this key shall have no effect.
2.3.4.5 S̲c̲r̲o̲l̲l̲ ̲O̲n̲
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 to
pages currently stored in the VDU.
2.3.4.6 S̲c̲r̲o̲l̲l̲ ̲D̲o̲w̲n̲
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 two
pages currently stored i the VDU.
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 ith 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 mde.
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 commandis only valid in receive 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 a parameter
for this command will cause the system to return the
selected error message in the response line.
2.3.5.7 P̲r̲i̲n̲t̲
This causes te 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, or in cas of ambiguity
to the user menu.
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
he 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̲
Any incorrect entry in the command line will cause
the system to eturn response message no. 1.
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 valiation 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 brek-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) ad 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.. 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
hen 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 validaion 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 b 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.
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 al 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 Appendx 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 indentification 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 feld 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 fild 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 gien 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 ase 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…86…1 …02… …02… …02… …02… …02… …02…
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, th user enters
the command SION and the system will display layout
K1-2.
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 password. The user enters ID code + password
in the command line and deprsses ENTER key.
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
returning K1-2 anddisplay error message 1 in the response
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 moe chance to enter
the correct ID code and password. If invalid a third
time, system response message no. 13 is displayed on
the response line. This ends the sign on transaction
for this user and the VDU keyboard will be locked out
and format K2 dislayed. 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…86…1 …02… …02… …02… …02… …02…
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 ptions 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
tansaction 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 men format together with the
error message in the system response line.
An invalid command results in error 1.
FIGURE 3.3-1…86…1 …02… …02… …02… …02… …02…
NEW MESSAGE PREPARATION…01…FIGURE 3.4-1…86…1 …02… …02… …02… …02… …02…
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 messge is retrievable by the user until
the message is released.
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 securty 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 higer 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 will enter the specialhandling category, if
appropriate. 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
seleted 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 5 will be returned.
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 the reference number of one of ten
predefined message handling instructions or may enter
his own message handlng instructions. If it is a predefined
number then it is converted into an operating signal.
If it is text then this will cause the message to be
sent to the message service position for handling.
A display of the predefined instructions is availabe.
If the user cannot remember the reference numbers of
the predefined message handling instructions he may
request a display by entering a "Y" (YES) in the field
"DISPLAY-Enter Y". This field is a directive to the
system and not part of the messge. After entry of the
header information and validation of the data the system
will if requested display the predefined message handling
instruction and prompt for a reference number (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 uer 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 pecedence 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 generae
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 designaors 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 speciic
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 an 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)(10 provided) of local
info addressees. The system will validate the SCD(s)
and return error 8 for invalid SCDs.
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 nuber.
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̲ ̲(̲M̲a̲n̲d̲a̲t̲o̲r̲y̲)̲
The user should enter the address(es) of the intended
action addressees. The user should begin with Address
Indicator roups (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 erro 2 is returned.
The user may mark the PLA with a preceding X which
will cause the message to be directed to the MDCO.
There is one entry per line.
There will be an echo back of the format after validation,
with the PLA reference numbers convertd to full PLA.
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.
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)
hehas 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.
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 spcification
made by the supervisor, if any. Any invalid entry will
result in the generation of error 12 after validation.
The "EXER/" the variable must not exceed 77 characters
including "EXER/". For "OPER/" the variable must not
exceed 106 includng "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 enties
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 o 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 suppresed, but the conversion of
the short-form user entries into full text will not
be performed, with the exception of PLA ref. to PLA.
FIGURE 3.4-2…86…1 …02… …02… …02… …02… …02…
FIGURE 3.4-3…86…1 …02… …02… …02… …02… …02…
Figure 3.4-4…86…1 …02… …02… …02… …02… …02…
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.
3.4.3.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 compresson takes place
prior to the output of A-3.
FIGURE 3.4-5…86…1 …02… …02… …02… …02… …02…
FIGURE 3.4-6…86…1 …02… …02… …02… …02… …02…
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.
The possibilites 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 systemwill return to
the user menu. The description of the use of the append
message function is given in 3.5.
FIGURE 3.4-7…86…1 …02… …02… …02… …02… …02…
3.5 A̲P̲P̲E̲N̲D̲ ̲M̲E̲S̲S̲A̲G̲E̲ ̲-̲ ̲A̲-̲4̲
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 sytem 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 time stamp, the five digit item
rference identifications 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" nput, the ENTER key is pressed.
A security interrogation will be performed, if appropriate.
On completion of the append, format A2 of the message
in preparation will be represented on the screen with
the new text added.
3.5.2 V̲a̲l̲i̲d̲a̲t̲i̲o̲n̲
If te message(s) have a classification or special handling
designator not allowed for the terminal/user then response
message 4 is returned.
If the reference is to non-existent message then error
2 is given.
If the referenced item was not prepared/isplayed at
this terminal, then error code 16 is given.
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.
If the messages are notin the on-line data base then
the user is made aware of this by output of message
25.…86…1 …02… …02… …02… …02… …02…
FIGURE 3.6-1…86…1 …02… …02… …02… …02… …02…
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, CCIS and SCARS Staff Cells. On presentation
the format contains the TRANACTION ID and ITEM REFERENCE
IDENTITY as in format A (Refer to section 6).
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̲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̲
As for format A. There are ten entry fields and this
number may be expanded by repeat/insert.
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 th validation to be carried out on the comment
header.
The error messages or validation are as for the relevant
lines of format A.
The Staff Cells for SCARS and CCIS need not be validated.
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 REPEAT/INSERT
to expand the format.
On completio 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…86…1 …02… …02… …02… …02… …02…
FIGURE 3.6-4…86…1 …02… …02… …02… …02… …02…
FIGURE 3.7-1…86…1 …02… …02… …02… …02… …02…
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 has already been
started and deferred r which has been sent for coordination
and requires editing as a result of the returned comments.
The user inserts the item reference identity only of
the message in the command line.
The system then retrieves the message and presents
it in a shot-form and compressed format A on the screen.
Format A1-1 appears first.
The user can page through the message and use the editing
functions. He may also continue with the message preparation
function as described under the NEW MESSAGE PREPARATIO
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-xistent message then
error 2 is given.
If the referenced item was not prepared at this terminal
then error code 16 is given.
If a message is not available for further editing because
it has been sent for release then the system will return
erro 17. If it has been released then it will return
error 18. If the item referred to is a comment then
error 15 is returned.
FIGURE 3.7-2…86…1 …02… …02… …02… …02… …02…
FIGURE 3.8-1…86…1 …02… …02… …02… …02… …02…
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 transmited. The item reference
identity is inserted in the command line.
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 cntinue 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 asociated 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 16.
If it has been transmitted then return error 19
If the item referred to is a message then return error
20.
FIGURE 3.8-2…86…1 …02… …02… …02… …02… …02…
PREPARE PREFORMATTED MESSAGE
FIGURE 3.9-1…86…1 …02… …02… …02… …02… …02…
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 (M001 to M200) of the predefined message. The
reference number can also be enterd 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 predefned 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 validaton procedure is the same as described for
format A section 3.4.1.15.
FIGURE 3.9-2…86…1 …02… …02… …02… …02… …02…
FIGURE 3.9-3…86…1 …02… …02… …02… …02… …02…
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.
he 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 exlicit 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̲
Segments may be repeated by use of an Insert command.
The entry of e.g.:
INSERT SEGMENT 2
will cause segment 2's sets to be inserted just aftersegment
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 line-descriptor which
specifies whether a line is mandatory or optional.
The first line of a Set contains the SET ID and the
SET NAME. he 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 IDand 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 theset.
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 te field 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 escriptor 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̲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 grup 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.
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 componnt
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 displaed. 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. f an entry
is invalid, then the user will be warned.
FIGURE 3.9-4…86…1 …02… …02… …02… …02… …02…
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 ransformed 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 nt 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 e 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
chracter of the set Id contains a number, shall be
displayed in a columnar presentation.
For the layout see fig. 3.9-5.…86…1 …02… …02… …02… …02…
…02…
FIGURE 3.9-5…86…1 …02… …02… …02… …02… …02…
MESSAGE/COMMENT DELETION
FIGURE 3.10-1…86…1 …02… …02… …02… …02… …02…
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 nd 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 may only delete items prepared at the terminal
requesting the deletion.
3.10.1 I̲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.2 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.2 V̲a̲l̲i̲d̲a̲t̲i̲o̲
If the Item reference ID refers to a message stored
in the system and available for deletion then a security
interrogation shall take place if appropriate. After
correct entry of password the system responds with
response message 21.
If the reerence is to a non-existing message/comment
then error 2 is given in the response line.
If the message referenced to is awaiting release the
system shall reply with error 22 and send a deletion
request to the supervisor.
If the referenced message has been released the system
shall reply with error 23 and send a deletion request
to the supervisor.
FIGURE 3.10-2…86…1 …02… …02… …02… …02… …02…
FIGURE 3.11-1…86…1 …02… …02… …02… …02… …02…
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 whch 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 th 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 elease 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 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 hen 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.
The user is then invited to enter the unique keys bymeans
of a command.
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
eferred 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 rerieve 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-3…86…1 …02… …02… …02… …02… …02…
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 rele
