top - download
⟦a042295ae⟧ Wang Wps File
Length: 45466 (0xb19a)
Types: Wang Wps File
Notes: CPS/SYS/001 issue II
Names: »0175A «
Derivation
└─⟦cf42e5d4d⟧ Bits:30005818 8" Wang WCS floppy, CR 0016A
└─ ⟦this⟧ »0175A «
WangText
&…09…&…00…&…06…%…0b…%…01…%…06…$…0c…$…02…#…09……86…1
…02…
…02… …02…
…02…CPS/210/SYS/0001
…02…800919…02……02…
CAMPS
SYSTEM
REQUIREMENTS
…02……02…CAMPS
T̲A̲B̲L̲E̲ ̲O̲F̲ ̲C̲O̲N̲T̲E̲N̲T̲S̲…01…S̲e̲c̲t̲i̲o̲n̲ ̲3̲.̲2̲.̲3̲
3.2.3. Terminal Functions and
Characteristics......................
3.2.3.1 Equipment and Functions
Allocatable to a Terminal Position
3.2.3.2 Terminal Access Control...........
3.2.3.2.1 Physical Access ..............
3.2.3.2.2. Logical Access ..............
3.2.3.3 Functional Capabilities of
Terminal Procedures...............
3.2.3.4 Precedence and Queuing ...........
3.2.3.5 Terminal Modes ...................
3.2.3.6 Status Information Available from
Terminal Positions ...............
3.2.3.7 Presentation of Information at
Terminal Positions ...............
3.2.3.7.1 Use of Visual Display Units ..
3.2.3.7.2 (Section deleted) ............
3.2.3.7.3 Requirement to Printed Output
3.2.3.7.4 Presentation of Information at
Terminal Positions with both
VDU and Teleprinter ..........
3.2.3…02…T̲e̲r̲m̲i̲n̲a̲l̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲s̲ ̲a̲n̲d̲ ̲C̲h̲a̲r̲a̲c̲t̲e̲r̲i̲s̲t̲i̲c̲s̲
A terminal position constitutes the means by which
an operator gets access to the CAMPS system.
The functions available to operators through CAMPS
are:
…02…- Supervisor/Engineering
…02…- Message Distribution Control
…02…- Message Service
…02…- Message Release
…02…- Message Reception
…02…- Message Preparation
This section describes the possible equipment configurations
of a terminal position and how access to the CAMPS
system is achieved. Further, the functional capabilities
of the functions Message Release, Message Reception
and Message Preparation are described, whereas the
functions Supervisor/Engineering, Message Distribution
Control and Message Service are described in section
3.2.4.
The section is organized as follows:
Section 3.2.3.1 describes the possible equipment configurations
of a Terminal position, the content and use of terminal
profiles and operator profiles.
Section 3.2.3.2 describes the terminal access control
imposed by the CAMPS system, and the associated procedures
necessary to access the CAMPS functions.
Section 3.2.3.3 contains a description of the functional
capabilities available to users of a terminal position.
Section 3.2.3.4 introduces precedence levels assigned
to terminal transactions and how transactions are queued
for terminal positions in accordance with their precedence
level.
Section 3.2.3.5 specifies the modes of operation in
which a terminal position may be, and for each mode
the terminal procedures applicable dependent on the
allocated function.
Section 3.2.3.6 specifies the subsets of the accounting
information which may be retrieved from a terminal
position.
Section 3.2.3.7 details how and where information shall
be displayed/printed at terminal positions.
3.2.3.1 E̲q̲u̲i̲p̲m̲e̲n̲t̲ ̲a̲n̲d̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲s̲ ̲A̲l̲l̲o̲c̲a̲t̲a̲b̲l̲e̲ ̲t̲o̲ ̲a̲ ̲T̲e̲r̲m̲i̲n̲a̲l̲ ̲P̲o̲s̲i̲t̲i̲o̲n̲
a) T̲e̲r̲m̲i̲n̲a̲l̲ ̲P̲o̲s̲i̲t̲i̲o̲n̲ ̲E̲q̲u̲i̲p̲m̲e̲n̲t̲
…02… The equipment configuration allocated to a terminal
position shall be one of the three listed below.
…02… 1) VDU with keyboard and one to four medium speed
teleprinters (ROP).
…02…2) VDU with keyboard.
…02…3) VDU with keyboard and medium speed teleprinter
(ROP).
The first type is the supervisor position, whereas
the last two are user terminal positions.
b) S̲t̲a̲n̲d̲ ̲A̲l̲o̲n̲e̲ ̲E̲q̲u̲i̲p̲m̲e̲n̲t̲
The following equipment types may be physical stand
alone devices but shall always be logically associated
with the supervisor VDU (refer section 3.2.3.2
Terminal Access Control).
1) Medium speed teleprinters (ROP).
2) Low speed teleprinters with input from paper-tape
only (full ACP 127 messages).
c) T̲e̲r̲m̲i̲n̲a̲l̲ ̲P̲o̲s̲i̲t̲i̲o̲n̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲
…02… The following CAMPS functions may be accessed from
a terminal position.
…02…1) Supervisor/Engineering.
…02…2) Message Distribution Control.
…02…3) Message Service.
…02…4) Message Release.
…02…5) Message Reception.
…02…6) Message Preparation.
The first is available to the supervisor only,
the next two to supervisor assistants, whereas
the last three constitutes the functions available
to users.
d) T̲e̲r̲m̲i̲n̲a̲l̲ ̲P̲r̲o̲f̲i̲l̲e̲
…02… The CAMPS system shall to each terminal position associate
a Terminal Profile. The Terminal Profile shall contain
the information listed below.
…02…- Terminal designator
…02…- Staff cell designator(s)
…02…- Classification
…02…- Special handling categories
…02…- Functions
…02…- List of allocated operators
…02…- Associated release terminal
…02…- Equipment configuration
…02…- Number of printed copies
…02… 1) T̲e̲r̲m̲i̲n̲a̲l̲ ̲D̲e̲s̲i̲g̲n̲a̲t̲o̲r̲
A three letter code identifying the terminal
position.
…02…2) S̲t̲a̲f̲f̲ ̲C̲e̲l̲l̲ ̲D̲e̲s̲i̲g̲n̲a̲t̲o̲r̲s̲
A list of maximum five staff cell designators.
A staff cell designator (SCD) is a three letter
code identifying one staff cell.
…02…3) C̲l̲a̲s̲s̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
The highest classification of the information,
which may be accessed/received at the terminal
position.
…02…4) S̲p̲e̲c̲i̲a̲l̲ ̲H̲a̲n̲d̲l̲i̲n̲g̲ ̲C̲a̲t̲e̲g̲o̲r̲i̲e̲s̲
A list of maximum three special handling categories.
The list defines the special handling categories
which may be accessed/received at the terminal
position.
…02…5) F̲u̲n̲c̲t̲i̲o̲n̲s̲
A list of functions assigned to the terminal
position. The list may include one or more
of the following functions: Message Preparation,
Message Reception, Message Release, Message
Distribution Control, Message Service, Supervisor/Engineering.
…02…6) L̲i̲s̲t̲ ̲o̲f̲ ̲A̲l̲l̲o̲c̲a̲t̲e̲d̲ ̲O̲p̲e̲r̲a̲t̲o̲r̲s̲
A list of maximum 15 operator identification
codes. The list identifies the operators with
access rights to CAMPS functions via this terminal
position.
7) A̲s̲s̲o̲c̲i̲a̲t̲e̲d̲ ̲R̲e̲l̲e̲a̲s̲e̲ ̲T̲e̲r̲m̲i̲n̲a̲l̲
The terminal designator of the associated release
terminal
8) E̲q̲u̲i̲p̲m̲e̲n̲t̲ ̲C̲o̲n̲f̲i̲g̲u̲r̲a̲t̲i̲o̲n̲
Identification of the equipment configuration
associated with the terminal position.
9) N̲u̲m̲b̲e̲r̲ ̲o̲f̲ ̲P̲r̲i̲n̲t̲e̲d̲ ̲C̲o̲p̲i̲e̲s̲
The number of copies requested of each document
per staff cell, for which printout on printer
is delivered.
e) O̲p̲e̲r̲a̲t̲o̲r̲ ̲P̲r̲o̲f̲i̲l̲e̲
The CAMPS system shall to each operator with access
right to the system associate an Operator Profile.
The Operator Profile shall contain the information
listed below.
- operator identification code
- password
- change of password (date)
- expiration of password (date)
- classification
- special handling categories
- functions
- exercise
1) O̲p̲e̲r̲a̲t̲o̲r̲ ̲I̲d̲e̲n̲t̲i̲f̲i̲c̲a̲t̲i̲o̲n̲ ̲C̲o̲d̲e̲
A three letter code identifying a specific
operator.
2) P̲a̲s̲s̲w̲o̲r̲d̲
Password of the operator. An eight letter code
unique for each user.
3) C̲h̲a̲n̲g̲e̲ ̲o̲f̲ ̲P̲a̲s̲s̲w̲o̲r̲d̲
The time (date) for the latest change of the
password.
4) E̲x̲p̲i̲r̲a̲t̲i̲o̲n̲ ̲o̲f̲ ̲P̲a̲s̲s̲w̲o̲r̲d̲
The time (date) where the password expires
i.e. becomes invalid.
5) C̲l̲a̲s̲s̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
The highest classification of the information,
which the operator may access or receive.
6) S̲p̲e̲c̲i̲a̲l̲ ̲H̲a̲n̲d̲l̲i̲n̲g̲ ̲C̲a̲t̲e̲g̲o̲r̲i̲e̲s̲
A list of maximum three special handling categories.
The list defines the special handling categories
which the operator may access or receive.
7) F̲u̲n̲c̲t̲i̲o̲n̲s̲
A list of functions identifying those accessible
by the operator. The list may include one or
more of the following functions: Message Preparation,
Message Reception, Message Release, Message
Distribution Control, Message Service Supervisor/Engineering.
8) E̲x̲e̲r̲c̲i̲s̲e̲
An indicator which specifies if the operator
has access to exercise information only.
f) Terminal Profiles and the Operator Profiles shall
be maintained by the supervisor.
3.2.3.2 T̲e̲r̲m̲i̲n̲a̲l̲ ̲A̲c̲c̲e̲s̲s̲ ̲C̲o̲n̲t̲r̲o̲l̲
Access control to the CAMPS via a terminal position
is performed on two levels, a physical and a logical.
3.2.3.2.1 P̲h̲y̲s̲i̲c̲a̲l̲ ̲A̲c̲c̲e̲s̲s̲
The physical access control is accomplished by a locking
mechanism fitted to the devices associated with the
terminal position. The locking mechanism may be in
one of the two states ON or OFF, which indicates whether
the device is manned or unmanned.
a) O̲n̲-̲s̲t̲a̲t̲e̲ ̲(̲m̲a̲n̲n̲e̲d̲)̲
Insertion of the key and turning to the "ON"
position shall cause a signal to be sent to
or sensed by the system indicating that the
device is manned. It shall not be possible
to remove the key when in the "ON" position.
b) O̲F̲F̲-̲s̲t̲a̲t̲e̲ ̲(̲u̲n̲m̲a̲n̲n̲e̲d̲)̲
Turning of the key to the "OFF" position shall
cause a signal to be sent to or sensed by the system
indicating that the device is unmanned. For VDU's
this action shall also cause the screen and local
device storage to be cleared. No operational traffic
shall be directed to a device whose working mechanism
is in the OFF-state.
3.2.3.2.2 L̲o̲g̲i̲c̲a̲l̲ ̲A̲c̲c̲e̲s̲s̲
a) To be able to enter the logical access control
level the locking mechanism must be in the ON-state.
b) The logical access control is accomplished by the
sign-in procedure, the sign-out procedure and the
security interrogation procedure.
c) For a terminal position with both VDU and medium
speed teleprinter the following logical access
rules apply:
1) VDU locking mechanism in OFF state,
printer locking mechanism in ON state:
The locking mechanism for the terminal position
as a whole is considered to be in the OFF-state.
(sign-in not possible).
2) VDU locking mechanism is in ON state,
printer locking mechanism is in OFF state:
The terminal position is considered to be equipped
with VDU only.
d) The sign-in procedure is activated by the command
SI. During the sign-in procedure the operator is
requested to enter his operator-id and his password.
e) During sign-in the system shall by means of the
terminal profile and the operator profile, check
- if the operator-id is contained in the terminal
positions operator list
- if the entered password is valid
If the two conditions above are fulfilled the access
rights of the operator shall be determined from
Terminal Profile and Operator Profile as follows:
- The lowest classification of the two profiles
shall apply
- only coinciding functions shall become available
f) A terminal position shall be blocked, i.e. no functions
can be performed via the terminal position,when
the following events occur during sign-in.
- three consecutive unsuccessful attempts to
enter an operator ID.
- three consecutive unsuccessful attempts to
enter a password.
A warning shall be sent to the supervisor, who
may unblock the terminal when appropriate.
g) When an operator signs in he accepts the responsibility
with respect to security for that terminal position.
The terminal position is said to have attended
operation.
When the operator wishes to relinguish the responsibility
for that terminal position with respect to security,
he signs out, activating the sign-out procedure
by the Command SO. The terminal is said to have
unattended operation.
The requirements to be met for attended and unattended
operations of terminal positions are as described
below.
h) A̲t̲t̲e̲n̲d̲e̲d̲ ̲O̲p̲e̲r̲a̲t̲i̲o̲n̲
Even when an operator accepts the responsibility
for a terminal position, messages shall not be
transmitted to that terminal position of classification
higher than NATO RESTRICTED (or as specified by
the supervisor) or of the special handling categories
without first interrogating the operator by means
of the security interrogating procedure.
The absence of a reply within 3 minutes or three
invalid replies during a security interrogation
shall result in the terminal returning to the unattended
mode of operation. The supervisor shall be informed
and will be responsible for further handling of
the message.
Before display of information of certain security
classification or above, or belonging to the special
handling category (as specified by the supervisor)
a security warning shall be displayed.
The operator is then required to enter a five letter
code (indicating that the physical environment
of the terminal position is suitable for display
of the highly sensitive information).
The display of the information shall then proceed.
The same five letter code shall be used at all
terminal positions in response to the security
warning.
i) U̲n̲a̲t̲t̲e̲n̲d̲e̲d̲ ̲O̲p̲e̲r̲a̲t̲i̲o̲n̲
When a terminal position is unattended, i.e. when
no operator has accepted responsibility for its
security, only messages of the classification NATO
UNCLASSIFIED and of routine precedence shall be
transmitted to that terminal position.
For a more detailed description of the sign-in,
sign-out, security interrogation and security warning
procedures refer to CPS/230/ICD/0001 with format
indices as indicated below:
Sign-in - format K1
Sign-out - format K2
Security interrogation - format I1
Security warning - format I2
For logical access/accept of responsibility with
respect to physical stand alone devices refer to
section 3.2.4.
3.2.3.3 F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲ ̲o̲f̲ ̲T̲e̲r̲m̲i̲n̲a̲l̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲s̲
The rules for exchange of information between user
and system is laid down in the interactive procedures
and associated formats specified in ref. CPS/230/ICD/0001.
This section contains a list of the transactions together
with a summary of the functional capabilities.
Furthermore the terminal control procedures available
are outlined.
a) T̲r̲a̲n̲s̲a̲c̲t̲i̲o̲n̲s̲
1) I̲n̲i̲t̲i̲a̲l̲ ̲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̲)
Commands: PMA
During preparation of the first draft of a
message the message header and the message
text is entered. A predefined header and/or
text format may be used. Correction procedures
for editing of header and text are available
and clean copies of the message may be requested
as long as initial preparation is not terminated.
Termination of the initial message preparation
occurs when the message is sent to coordination
or release or is just retained as specified
by the operator.
2) M̲e̲s̲s̲a̲g̲e̲ ̲C̲o̲o̲r̲d̲i̲n̲a̲t̲i̲o̲n̲ ̲(̲f̲o̲r̲m̲a̲t̲ ̲B̲)̲
Messages under preparation are displayed in
this format when submitted to user terminals
for coordination.
3) M̲e̲s̲s̲a̲g̲e̲ ̲E̲d̲i̲t̲i̲n̲g̲ ̲(̲f̲o̲r̲m̲a̲t̲ ̲C̲1̲)̲
Command: EM.
Messages, for which a first draft has been
created, may be edited or sent to coordination
or release, by invocation of the Message Editing
Procedure. Editing is performed by use of the
correction procedures and clean copies may
be requested.
4) C̲l̲e̲a̲n̲ ̲C̲o̲p̲y̲ ̲o̲f̲ ̲M̲e̲s̲s̲a̲g̲e̲ ̲(̲f̲o̲r̲m̲a̲t̲ ̲C̲2̲)̲
Whenever a clean copy of a message under preparation
is requested, it shall be displayed in this
format .
5) R̲e̲l̲e̲a̲s̲e̲ ̲o̲f̲ ̲M̲e̲s̲s̲a̲g̲e̲ ̲(̲f̲o̲r̲m̲a̲t̲ ̲D̲)̲
Outgoing messages, for which release are requested
are displayed at the release officers terminal
position, and he is prompted for an answer
to the request. The entered answer possibly
associated with a comment is sent to the requesting
terminal (Notification of release (format F)).
6) I̲n̲c̲o̲m̲i̲n̲g̲ ̲M̲e̲s̲s̲a̲g̲e̲ ̲P̲r̲e̲s̲e̲n̲t̲a̲t̲i̲o̲n̲ ̲(̲f̲o̲r̲m̲a̲t̲ ̲E̲1̲)̲
Incoming messages are presented at terminal
positions in this format.
7) O̲u̲t̲g̲o̲i̲n̲g̲ ̲M̲e̲s̲s̲a̲g̲e̲ ̲P̲r̲e̲s̲e̲n̲t̲a̲t̲i̲o̲n̲ ̲(̲f̲o̲r̲m̲a̲t̲ ̲E̲2̲)̲
Local copies of outgoing messages (after release)
shall be presented at terminal positions in
this format.
8) N̲o̲t̲i̲f̲i̲c̲a̲t̲i̲o̲n̲ ̲o̲f̲ ̲R̲e̲l̲e̲a̲s̲e̲ ̲(̲f̲o̲r̲m̲a̲t̲ ̲F̲)̲
The system employs this format to notify the
originator of a message of the decision of
the releasing officer concerning release of
the message.
9) I̲n̲i̲t̲i̲a̲l̲ ̲C̲o̲m̲m̲e̲n̲t̲ ̲P̲r̲e̲p̲a̲r̲a̲t̲i̲o̲n̲ ̲(̲f̲o̲r̲m̲a̲t̲ ̲G̲1̲)̲
Command: CM1.
During preparation of the first draft of a
comment the comment header and comment text
is entered. Correction procedures and a listing
of the corrected comment may be requested as
long as initial comment preparation is not
terminated. Termination of the initial comment
preparation occurs when the comment is sent
to the addressed terminal positions or when
the comment is retained as specified by the
operator.
10) C̲o̲m̲m̲e̲n̲t̲ ̲P̲r̲e̲s̲e̲n̲t̲a̲t̲i̲o̲n̲ ̲(̲f̲o̲r̲m̲a̲t̲ ̲G̲2̲)̲
Comments sent from one terminal to another
are displayed at the specified destination
user terminal(s) in this format.
11) C̲o̲m̲m̲e̲n̲t̲ ̲E̲d̲i̲t̲i̲n̲g̲ ̲(̲f̲o̲r̲m̲a̲t̲ ̲G̲3̲)̲
Command: EC.
Comments which have been retained may be edited
and sent to addressed terminals by invocation
of the comment editing procedure. Editing is
performed by use of the correction procedures.
A listing of the corrected comment and further
corrections may be requested as long as the
comment editing procedure is not terminated.
12) R̲e̲t̲r̲i̲e̲v̲a̲l̲ ̲(̲f̲o̲r̲m̲a̲t̲ ̲H̲)̲
Command: RM.
This format is employed to retrieve and display
both incoming and outgoing messages, as well
as comments.
13) S̲e̲c̲u̲r̲i̲t̲y̲ ̲I̲n̲t̲e̲r̲r̲o̲g̲a̲t̲i̲o̲n̲ ̲(̲f̲o̲r̲m̲a̲t̲ ̲I̲1̲)̲
This format is used by the system to request
the terminal operator to identify himself by
entering his personal password.
14) S̲e̲c̲u̲r̲i̲t̲y̲ ̲W̲a̲r̲n̲i̲n̲g̲ ̲(̲f̲o̲r̲m̲a̲t̲ ̲I̲2̲)̲
This procedure is invoked by the system, asking
the operator if the surroundings are secure.
The system will display the waiting transaction
after the operator has entered the required
five letter code.
15) T̲i̲m̲e̲ ̲S̲t̲a̲t̲e̲m̲e̲n̲t̲ ̲(̲f̲o̲r̲m̲a̲t̲ ̲J̲)̲
Command: PT.
In response to a time request, the date time
group with time-zone and month shall be displayed
by the system in this format.
16) S̲i̲g̲n̲-̲i̲n̲ ̲(̲f̲o̲r̲m̲a̲t̲ ̲K̲1̲)̲
Command: SI.
This procedure is invoked by an operator to
identify himself to the system and accept responsibility
for correct application of security procedures
with respect to this terminal.
17) S̲i̲g̲n̲-̲o̲u̲t̲ ̲(̲f̲o̲r̲m̲a̲t̲ ̲K̲2̲)̲
Command SO.
This procedure is invoked by an operator when
he relinquishes the responsibility for a user
terminal and the messages displayed and/or
printed out.
18) C̲h̲a̲n̲g̲e̲ ̲o̲f̲ ̲P̲a̲s̲s̲w̲o̲r̲d̲ ̲(̲f̲o̲r̲m̲a̲t̲ ̲L̲)̲
This user format has been deleted. Change of
password is accomplished by sending a comment
to the supervisor.
19) T̲e̲x̲t̲ ̲F̲o̲r̲m̲a̲t̲s̲ ̲(̲f̲o̲r̲m̲a̲t̲s̲ ̲M̲1̲ ̲-̲ ̲M̲n̲)̲
These procedures are used in the preparation
of recurrent pre-defined reports.
20) M̲e̲s̲s̲a̲g̲e̲ ̲S̲t̲a̲t̲u̲s̲ ̲(̲f̲o̲r̲m̲a̲t̲ ̲N̲1̲)̲
This format is periodically employed by the
system to present the operator with a statement
of the status of all messages prepared at the
terminal.
21) M̲e̲s̲s̲a̲g̲e̲ ̲S̲t̲a̲t̲u̲s̲ ̲E̲n̲q̲u̲i̲r̲y̲ ̲(̲f̲o̲r̲m̲a̲t̲ ̲N̲2̲)̲
Command: SM.
By use of this command the operator may request
the message status report to be presented at
his terminal position.
22) M̲e̲s̲s̲a̲g̲e̲ ̲M̲e̲r̲g̲i̲n̲g̲ ̲(̲f̲o̲r̲m̲a̲t̲ ̲O̲)̲
Command: MM.
This procedure is used to compile an outgoing
message using sections of existing messages.
23) M̲e̲s̲s̲a̲g̲e̲ ̲D̲e̲l̲e̲t̲i̲o̲n̲ ̲R̲e̲q̲u̲e̲s̲t̲ ̲(̲f̲o̲r̲m̲a̲t̲ ̲P̲1̲)̲
Command: DM.
This command is used by an originator to request
the deletion of a message.
24) M̲e̲s̲s̲a̲g̲e̲ ̲D̲e̲l̲e̲t̲i̲o̲n̲ ̲N̲o̲t̲i̲f̲i̲c̲a̲t̲i̲o̲n̲ ̲(̲f̲o̲r̲m̲a̲t̲ ̲P̲2̲)̲
This format is employed by the system to notify
the originator and nominated coordinators of
a message (if sent for coordination) that the
message has been deleted.
25) M̲e̲s̲s̲a̲g̲e̲ ̲R̲e̲l̲e̲a̲s̲e̲ ̲S̲t̲a̲t̲u̲s̲ ̲R̲e̲p̲o̲r̲t̲ ̲(̲f̲o̲r̲m̲a̲t̲ ̲Q̲1̲)̲
This format is periodically employed by the
system to present the releasing officer with
a statement of the status of messages submitted
to him for release within an elapsed period.
26) M̲e̲s̲s̲a̲g̲e̲ ̲R̲e̲l̲e̲a̲s̲e̲ ̲S̲t̲a̲t̲u̲s̲ ̲E̲n̲q̲u̲i̲r̲y̲.̲ ̲(̲f̲o̲r̲m̲a̲t̲ ̲Q̲2̲)̲
Command: RS.
This command is used by the releasing officer
to obtain the status of messages submitted
to him for release since the last status report.
27) T̲r̲a̲n̲s̲a̲c̲t̲i̲o̲n̲ ̲S̲t̲a̲t̲u̲s̲ ̲(̲f̲o̲r̲m̲a̲t̲ ̲R̲1̲)̲
This format is periodically employed by the
system to inform a terminal operator of all
transactions with his terminal during an elapsed
period.
28) T̲r̲a̲n̲s̲a̲c̲t̲i̲o̲n̲s̲ ̲S̲t̲a̲t̲u̲s̲ ̲E̲n̲q̲u̲i̲r̲y̲ ̲(̲f̲o̲r̲m̲a̲t̲ ̲R̲2̲)̲
Command: TA.
This command is used by a terminal operator
to obtain a list of all transactions associated
with his terminal since the last Transaction
Status.
29) F̲o̲r̲m̲a̲t̲s̲ ̲f̲o̲r̲ ̲C̲A̲M̲P̲S̲/̲A̲C̲E̲ ̲A̲C̲C̲I̲S̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲
Refer applicable ICD.
30) F̲o̲r̲m̲a̲t̲s̲ ̲f̲o̲r̲ ̲C̲A̲M̲P̲S̲/̲S̲C̲A̲R̲S̲ ̲I̲I̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲
Refer applicable ICD.
31) C̲o̲r̲r̲e̲c̲t̲i̲o̲n̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲s̲
Correction procedures may be called from interactive
procedures to which one of the following formats
is associated: A, C1, G1, G3.
When the operator indicates that he wishes
to enter the correction procedure the system
shall condition itself to respond to any of
the following correction instructions:
Print or display the designated line, L (X)
Delete the designated line, D (X)
Change the entry under the designated
line to a new value C (X)
Insert a new entry after the designated
line I (X)
Where X shall be in accordance with
1) or 2) below:
1) A single letter indicating a format
line.
2) m (sp) n, where m indicates a format
line
and n is a number specifying a line
within the format line.
b) T̲e̲r̲m̲i̲n̲a̲l̲ ̲C̲o̲n̲t̲r̲o̲l̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲s̲
It shall be possible via the terminal keyboard
of a VDU to:
- suspend a transaction in progress
- cancel a transaction in progress
c) T̲h̲e̲ ̲S̲u̲s̲p̲e̲n̲d̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲
Activation of the suspend function shall result
in a suspension of the transaction in progress,
and the terminal shall be available to the operator
for the initiation of a new transaction. The suspend
function shall be applicable as follows:
1) when procedures to which the formats B, D,
E1, E2, G2, N1, Q1, R1 are associated are interrupted
by the operator by use of the suspend function,
the transaction shall be subsequently recommenced
from the start once the terminal has returned
to REST mode (ref subsection 3.2.3.5); due
account being taken to new transactions queued
for that terminal.
2) when procedures, to which the formats F, H,
I1, I2, K1, K2, L, O, P1, P2 are associated,
are in progress the activation of the suspend
function by the operator shall be ignored by
the system.
3) when procedures, to which the formats J, N2,
Q2, R2, are associated, are interrupted by
the operator by use of the suspend function,
it shall have the same effect as if the cancel
function had been activated.
4) when procedures, to which the formats A, C1,
G1, G3 are associated, are interrupted by use
of the suspend function, the subsequent use
of the procedures with associated formats
C1 or G3 shall cause the transaction to be
resumed from the point at which it was interrupted.
Incomplete format lines (except for the text
format line) shall not be retained. Only one
suspension of this kind (format A, C1, G1,
G3) may be active at a given time, except if
preemption applies in which case there may
be two.
d) T̲h̲e̲ ̲C̲a̲n̲c̲e̲l̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲
The cancel function shall allow the operator to
cancel any transaction which he has commenced before
the normal termination. The cancellation shall
apply only to the transaction itself, e.g. if Message
Editing is cancelled the message retained by the
system will be in the same state as it was prior
to the cancelled Message Editing function was invoked.
The cancel function will be effective only if activated
when one of the following transactions are in progress;
the format associated used as index: A, C1, G1,
G3, N2, Q2, R2.
e) D̲e̲l̲e̲t̲e̲ ̲L̲i̲n̲e̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲
The delete line function shall be used only with
respect to interactive procedures as follows:
l) Header entry:
The use of the DELETE LINE function shall cause
the current format line to be deleted The system
shall transmit an end-of-line function to the
terminal followed by the fixed text associated
with the entry and then await a further entry
by the operator.
2) Format lines containing text lines:
The use of the DELETE LINE function shall cause
the current line of text to be deleted.The
system shall output an end-of-line function
to the terminal and await further entry in
accordance with the format being used. Repeated
use of this function shall cause successive
lines of text to be deleted in reverse order
of entry. When no lines of text exist or remain,
the character "?" shall be transmitted to the
terminal.
f) D̲e̲l̲e̲t̲e̲ ̲C̲h̲a̲r̲a̲c̲t̲e̲r̲ ̲F̲u̲n̲t̲i̲o̲n̲
The delete character function shall be initiated
by activating the delete key.
Use of the function shall cause the previously
entered character to be discarded by the system.
When this function is applied to an empty line
the character "?" shall be transmitted to the terminal.
3.2.3.4 P̲r̲e̲c̲e̲d̲e̲n̲c̲e̲ ̲a̲n̲d̲ ̲Q̲u̲e̲u̲e̲i̲n̲g̲
This section identifies the levels of precedence to
be distinguished by the system, and specifies the order
in which transactions, belonging to different precedence
levels, queued for a terminal position shall be handled.
The order in which transactions belonging to the same
precedence level are handled is described as well.
a) P̲r̲e̲c̲e̲d̲e̲n̲c̲e̲ ̲L̲e̲v̲e̲l̲s̲
Each transaction will have, associated with it,
a precedence level related to the urgency with
which the transaction shall be handled.
There are four levels of precedence which shall
be distinguished by the system. To accommodate
a possible increase in the number of precedence
levels used, allowance shall be made in the design
for two other levels as yet unspecified.
The four defined precedence levels are:
P̲r̲e̲c̲e̲d̲e̲n̲c̲e̲ ̲L̲e̲v̲e̲l̲s̲ N̲a̲m̲e̲
1 Flash
2 Immediate
3 Priority
4 Routine
b) D̲e̲t̲e̲r̲m̲i̲n̲a̲t̲i̲o̲n̲ ̲o̲f̲ ̲P̲r̲e̲c̲e̲d̲e̲n̲c̲e̲ ̲L̲e̲v̲e̲l̲s̲ ̲o̲f̲ ̲T̲r̲a̲n̲s̲a̲c̲t̲i̲o̲n̲s̲
̲A̲s̲s̲o̲c̲i̲a̲t̲e̲d̲ ̲w̲i̲t̲h̲ ̲T̲e̲r̲m̲i̲n̲a̲l̲ ̲P̲o̲s̲i̲t̲i̲o̲n̲
The precedence levels used in relation to messages
under preparation and to comments, shall be that
assigned by the drafter at the appropriate point
in the preparation procedure.
That precedence level shall apply in relation to
the handling of following transactions involving
messages and comments:
- Message Preparation (format A, C2,
O)
- Message Editing (format C1)
- Release of Message (format D)
- Incoming and outgoing message
- Presentation (format E1, E2)
- Comments (format G1, G2,
G3)
c) T̲r̲a̲n̲s̲a̲c̲t̲i̲o̲n̲s̲ ̲o̲f̲ ̲t̲h̲e̲ ̲P̲r̲e̲c̲e̲d̲e̲n̲c̲e̲ ̲L̲e̲v̲e̲l̲ ̲-̲ ̲F̲L̲A̲S̲H̲
When the transactions listed below are in progress,
and only then, they belong to the precedence level
FLASH.
- Retrieval (format H)
- Security procedures (formats I1, I2,
K1, K2, L,)
- Message Merge (format O)
- Message Deletion (format P1, P2)
- Notification of Release (Format F)
The transactions Message Merge, Message Deletion
and Retrieval have been assigned to the precedence
level FLASH when they are in progress due to data
integrity and security considerations.
d) T̲r̲a̲n̲s̲a̲c̲t̲i̲o̲n̲s̲ ̲o̲f̲ ̲t̲h̲e̲ ̲P̲r̲e̲c̲e̲d̲e̲n̲c̲e̲ ̲L̲e̲v̲e̲l̲ ̲-̲ ̲I̲M̲M̲E̲D̲I̲A̲T̲E̲
The transactions listed below are by default assigned
to the precedence level IMMEDIATE:
- Transaction Status Report (R1).
e) T̲r̲a̲n̲s̲a̲c̲t̲i̲o̲n̲s̲ ̲o̲f̲ ̲t̲h̲e̲ ̲P̲r̲e̲c̲e̲d̲e̲n̲c̲e̲ ̲L̲e̲v̲e̲l̲ ̲-̲ ̲P̲R̲I̲O̲R̲I̲T̲Y̲
The transactions listed below are by default assigned
to the precedence level PRIORITY.
None.
f) T̲r̲a̲n̲s̲a̲c̲t̲i̲o̲n̲s̲ ̲o̲f̲ ̲t̲h̲e̲ ̲P̲r̲e̲c̲e̲d̲e̲n̲c̲e̲ ̲L̲e̲v̲e̲l̲ ̲-̲ ̲R̲O̲U̲T̲I̲N̲E̲
…02… The transactions listed below are by default assigned
to the precedence level ROUTINE.
- Time Statement (format J)
- Message Status Enquiry (format N1,
N2)
- Transaction Status Enquiry (format R2)
- Release Status Report (format Q1,
Q2)
g) Q̲u̲e̲u̲e̲i̲n̲g̲
When transactions addressed to a terminal position,
at which a transaction allready is in progress,
are received by the system they shall be queued
for that terminal position in accordance with g1)
and g2) below:
1) A transaction shall be queued in accordance
with the precedence level to which it belongs,
i.e. it shall be handled before all those transactions
of lower precedence and after all those transactions
of higher precedence which are queued for that
terminal position.
2) Queueing of transactions belonging to the same
precedence level shall be as follows:
- Incoming messages (format E1) shall be
handled before all other transactions.
- The order in which transactions shall be
handled is that of their time of queing
to the terminal, due account being taken
of the provision above under g2.
h) P̲r̲e̲e̲m̲p̲t̲i̲o̲n̲
When a lower precedence transaction is using a
facility required for a FLASH transaction, the
lower precedence transaction shall be interrupted
and the FLASH transaction recommenced.
1) The interrupted lower precedence transaction
shall be handled the same way as transactions
suspended by the operator using the suspend
function associated with the terminal.
Preemption shall not take place:
- During the transmission of the identification
serial number and date and time group of
the transaction, i.e. the transaction id.
- If the remainder of the transaction would
take less than T seconds. The parameter
T shall be specified by the supervisor.
2) Transactions of the precedence levels PRIORITY
and IMMEDIATE shall not break into or interrupt
those of lower precedence.
3) When transactions of precedence level FLASH
has been queued for a terminal for 30 seconds
it shall be sent to the Message Distribution
Control operator (MDCO) by the system, and
cause an audible alarm at this position.
3.2.3.5 T̲e̲r̲m̲i̲n̲a̲l̲ ̲M̲o̲d̲e̲s̲
In this section the possible modes of operation for
a terminal position are identified and for each function
the transactions in each mode are specified.
The last part of the section describes the possible
transitions between the modes of operation and the
events that causes the transitions.
A terminal position shall be considered to be in one
of the three following modes:
- Interactive mode
- Receive mode
- Rest mode
a) I̲n̲t̲e̲r̲a̲c̲t̲i̲v̲e̲ ̲m̲o̲d̲e̲
A Terminal position is said to be in interactive
mode, when a transaction initiated by a user is
in progress.
b) R̲e̲c̲e̲i̲v̲e̲ ̲M̲o̲d̲e̲
A terminal position is said to be in receive mode
when transactions not initiated by the user is
in progress.
c) R̲e̲s̲t̲ ̲M̲o̲d̲e̲
A Terminal position is said to be in rest mode
when it is neither in the interactive mode nor
in the receive mode.
In table 3.2.3.5.-1, 3.2.3.5.-2 and 3.2.3.5-3 the formats
applicable to each mode for respective Message Preparation,
Message Release and Message Reception are tabulated.
Figure 3.2.3.5-1
side 114
figure 3.2.3.5-2
3.2.3.5-3
figure
D̲e̲f̲i̲n̲i̲n̲i̲t̲i̲o̲n̲ ̲o̲f̲ ̲T̲r̲a̲n̲s̲i̲t̲i̲o̲n̲s̲
re 1: When a terminal is in Rest mode the operator
may initiate any of the interactive procedures
associated with the function(s) available to
him.
This will cause the terminal to enter the Interactive
mode of operation.
re 2: The terminal will return to the Rest mode from
the Interactive mode, when one of the following
events occur.
a) Normal termination of the interactive procedure.
b) Termination of the interactive procedure
due to erroneus entries by the operator.
c) Time-out. If an operator has not responded
in accordance with the requirements of
the interactive procedure after 3 minutes
(except format D).
If after activation of the suspend function,
no transaction is initiated by the operator
after 3 minutes.
d) If the operator activates the cancel function.
re 3: A terminal in Rest mode will enter the Receive
mode, when the system initiates one of the
transactions allocated to the Receive mode.
re 4: The terminal will return to Rest mode,
a) when no more transactions allocated to
the Receive mode are queued for that terminal
position.
b) when erroneous entries are entered by the
operator during
1 Security interrogation (format I1)
2 Security warning (format I2)
re 5: The terminal will enter the interactive mode
from the receive mode when the operator activates
the suspend function.
re 6: The transition from the interactive mode to
the receive mode may be caused only by preemption.
3.2.3.6 S̲t̲a̲t̲u̲s̲ ̲I̲n̲f̲o̲r̲m̲a̲t̲i̲o̲n̲ ̲A̲v̲a̲i̲l̲a̲b̲l̲e̲ ̲f̲r̲o̲m̲ ̲T̲e̲r̲m̲i̲n̲a̲l̲ ̲P̲o̲s̲i̲t̲i̲o̲n̲
This section first describes how transactions shall
be identified. Furthermore the extracts of log information
accessible from a terminal position are outlined (ref.
section 3.2.5).
a) T̲r̲a̲n̲s̲a̲c̲t̲i̲o̲n̲ ̲I̲d̲e̲n̲t̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
The system shall allocate a unique identification
to each new transaction with a terminal. (Format
J, format C2, and format S,M1 - Mn excepted).
This shall consist of:
- a three letter group identifying the terminal
position with which the transaction takes place.
(terminal designator).
- a serial number ranging from 001 to 999 which
is augmented by one for each succesive transaction
with that terminal position.
- a 'date and time group' giving the month, the
day of month, hour and minute at which the
transaction was initiated. (Day + Hour + Min
+ Zone suffix + Month).
b) T̲r̲a̲n̲s̲a̲c̲t̲i̲o̲n̲ ̲S̲t̲a̲t̲u̲s̲
Transaction status are transmitted periodically
with a periodicity as specified per site, by the
system to all terminal positions allocated one
or more of the functions:
Message Preparation
Message Release
Message Reception
The periodically received Transaction Status contains
a listing of all transactions associated with the
terminal position since the latest reception of
the periodically transmitted status.
The Transaction Status (format R1) may be requested
from terminal positions allocated the functions:
- Message Preparation or
- Message Release or
- Message Reception
This is done by initiation of the Transaction Status
Enquiry (format R2).
c) M̲e̲s̲s̲a̲g̲e̲ ̲S̲t̲a̲t̲u̲s̲
Message Status (format N1) are transmitted periodically
(with a periodicity as specified per site) to terminal
position allocated the function:
Message Preparation.
The periodically received Message Status contains
the status for each message and comment originated
from the terminal position.
The Message Status may be requested from a Message
preparation position by means of a Message Status
Enquiry (format N2).
d) M̲e̲s̲s̲a̲g̲e̲ ̲R̲e̲l̲e̲a̲s̲e̲ ̲S̲t̲a̲t̲u̲s̲
Message Release Status (format Q1) is received
periodically (with a periodicity as specified per
site) at Message Release Positions, informing the
Release officer of:
- Messages Submitted to
- Messages Released at
- Messages Deferred at
- Messages Refused at
his position since the latest Message Release Status
was received.
Message Release Status may be requested by the
Release officer using Release Status Enquiry (format
Q2).
e) Status reports requested by an operator (formats
R2, N2, Q2) will contain the requested status of
all transactions handled since the latest periodically
received report.
3.2.3.7 P̲r̲e̲s̲e̲n̲t̲a̲t̲i̲o̲n̲ ̲o̲f̲ ̲I̲n̲f̲o̲r̲m̲a̲t̲i̲o̲n̲ ̲a̲t̲ ̲T̲e̲r̲m̲i̲n̲a̲l̲ ̲P̲o̲s̲i̲t̲i̲o̲n̲s̲
This section specifies the requirement for presentation
of information on respective VDU and printer.
Section 3.2.3.7.1 and 3.2.3.7.2 contains the requirements
for Visual Display Units and teleprinters (send/receive).
Section 3.2.3.7.3 contains the requirements for printed
output.
Whereas section 3.2.3.7.4 defines the destination of
information when both a VDU and a teleprinter are allocated
a terminal position.
3.2.3.7.1 U̲s̲e̲ ̲o̲f̲ ̲V̲i̲s̲u̲a̲l̲ ̲D̲i̲s̲p̲l̲a̲y̲ ̲U̲n̲i̲t̲s̲
a) Terminal Control Information shall be permanently
displayed at each VDU (in manned operation) at
the top line of the screen.
Terminal control information is:
- function's allocated to the terminal.
- transaction in progress or Rest mode.
- whether a transaction is suspended.
- information on queues of transactions awaiting
access per precedence.
- the current operator command.
b) For transactions initiated by the system, i.e those
associated with the formats listed below, the information
shall be presented one line at a time and the next
line shall be presented only when the operator
enters a signal requesting it. All lines of the
screen, except for the top lines, shall be used
and the contents rolled up from the bottom each
time a new line is requested and the new line entered
as the bottom line on the screen (Scroll-mode).
c) For interactive transactions the VDU shall support
the following facility.
- all lines of the screen, except for the top
lines, shall be used and the contents rolled
up from the bottom each time the bottom line
is filled and the new line entered as the bottom
line on the screen. (Roll-up mode).
d) L̲i̲s̲t̲ ̲o̲f̲ ̲F̲o̲r̲m̲a̲t̲s̲ ̲t̲o̲ ̲b̲e̲ ̲P̲r̲e̲s̲e̲n̲t̲e̲d̲ ̲i̲n̲ ̲S̲c̲r̲o̲l̲l̲ ̲M̲o̲d̲e̲
Message Coordination (format B)
Incomming Message Presentation (format E1)
Outgoing Message Presentation (format E2)
Notification of Release (format F)
Comment Presentation (format G2)
Time Statement (format J)
Message Status (format N1)
Message Deletion Notification (format P2)
Message Release Status (format Q1)
Transaction Status (format R1)
The scroll function used when the last line is
presented shall indicate that the operator has
received the information presented to him.
e) L̲i̲s̲t̲ ̲o̲f̲ ̲F̲o̲r̲m̲a̲t̲s̲ ̲t̲o̲ ̲b̲e̲ ̲P̲r̲e̲s̲e̲n̲t̲e̲d̲ ̲i̲n̲ ̲R̲o̲l̲l̲-̲u̲p̲ ̲M̲o̲d̲e̲
Security Interrogation (format I1)
Security Warning Message (format I2)
Signing-In (format K1)
Signing-out (format K2)
Change of Password (format L)
Message Status Enquiry (format N2)
Message Merge (format O)
Message Deletion Request (format P1)
Message Release Status Enquiry (format Q2)
Terminal Information (format S)
Transaction Status Enquiry (format R2)
f) L̲i̲s̲t̲ ̲o̲f̲ ̲F̲o̲r̲m̲a̲t̲s̲ ̲t̲o̲ ̲w̲h̲i̲c̲h̲ ̲b̲o̲t̲h̲ ̲R̲o̲l̲l̲-̲u̲p̲ ̲a̲n̲d̲ ̲S̲c̲r̲o̲l̲l̲
̲M̲o̲d̲e̲ ̲a̲p̲p̲l̲y̲
Initial Message Preparation (format A)
Message Editing (format C1, C2)
Message Release (format D)
Initial Comment Preparation (format G1)
Comment Editing (format G3)
Retrieval (format H)
1) For formats A, C1, C2, G1, G3 the following
rules shall apply:
- Roll-up mode apply during the interactive
part of the associated procedures.
- When clean copies are requested they shall
be presented in scroll mode.
- When scrolling is requested during presentation
of the last line the VDU shall return to
Roll-up-mode and prompt the next format
line as specified by the interactive procedure
associated with the format
2) For format D Message Release the following
rules shall apply
- The Message for which release is requested
shall be presented in scroll mode.
- When scrolling is requested during presentation
of the last line the VDU shall enter the
Roll-up-mode and prompt the next format
line as specified by the interactive procedure
associated with the format.
3) For format H the following rules shall apply
- Roll-up mode apply during the interactive
part of the associated procedure.
- The retrieved messages are presented in
scroll mode.
3.2.3.7.2 This section deleted.
3.2.3.7.3 R̲e̲q̲u̲i̲r̲e̲m̲e̲n̲t̲s̲ ̲t̲o̲ ̲P̲r̲i̲n̲t̲e̲d̲ ̲O̲u̲t̲p̲u̲t̲
Document accounting.
a) Any printed copy document produced at a terminal
position shall carry a document control number.
b) The document control number shall form part of
the heading of the document and shall be repeated
on each page together with the page number and
total number of pages in the output.
c) At the top and bottom of each page the classification
of the document shall be printed.
d) The document control number consists of five components:
- Transaction Number
- System Print Control Number
- Date and Time Group
- Special Handling Control Number
- Number of Copies.
1) T̲r̲a̲n̲s̲a̲c̲t̲i̲o̲n̲ ̲N̲u̲m̲b̲e̲r̲
The transaction number is the transaction identification
of the transaction which caused the print-out
of the document.
2) S̲y̲s̲t̲e̲m̲ ̲P̲r̲i̲n̲t̲ ̲C̲o̲n̲t̲r̲o̲l̲ ̲N̲u̲m̲b̲e̲r̲
The System Print Control number is a four digit
number, incremented by one for each new printing
initiated by the CAMPS system i.e a common
series for all printed output independent of
the printing station within a CAMPS system.
3) D̲a̲t̲e̲ ̲a̲n̲d̲ ̲T̲i̲m̲e̲ ̲G̲r̲o̲u̲p̲
The date and time group associated with the
printing action. (Day of Month + Hour + Min
+ Zone suffix + Month).
4) S̲p̲e̲c̲i̲a̲l̲ ̲H̲a̲n̲d̲l̲i̲n̲g̲ ̲C̲o̲n̲t̲r̲o̲l̲ ̲N̲u̲m̲b̲e̲r̲
The special handling control number is a four
digit number preceded by a single letter (to
be specified at initialization). The series
shall be common to all printed output belonging
to the special handling categories specified
by the supervisor. The number shall be incremented
by one for each new printed output of the special
handling categories.
5) T̲h̲e̲ ̲N̲u̲m̲b̲e̲r̲ ̲o̲f̲ ̲C̲o̲p̲i̲e̲s̲ of a document printed
out at a printer station may be specified by
the supervisor.
The Document Control number shall include the
number of copies specified for the printing
action.
e) D̲o̲c̲u̲m̲e̲n̲t̲ ̲l̲a̲y̲o̲u̲t̲
Print-out shall be paged as described below.
1) Each page shall contain N lines, where N can
be specified separately for each device type
by the supervisor.
2) Line 1 shall contain only a "-" at the left
hand margin
3) Line 2 shall be blank.
4) Line 3 shall be the next line of the relevant
format.
5) Line (N-3) shall be the last line on the page
from the relevant format.
6) Line N shall contain only a "-" at the left
hand margin.
P̲h̲y̲s̲i̲c̲a̲l̲ ̲L̲i̲n̲e̲.̲ ̲ C̲o̲m̲p̲o̲s̲i̲t̲i̲o̲n̲.̲ ̲
1 -
2
3 (first format * line of this page)
4 (second format * line of this page)
5 (third format * line of this page)
6 (fourth format * line of this page)
7 (fifth format * line of this page
N-4 (second to last format * line of this page)
N-3 (last format * line of this page)
N-2
N-1
N -
* Format lines, refer to the appropriate formats.
3.2.3.7.4 P̲r̲e̲s̲e̲n̲t̲a̲t̲i̲o̲n̲ ̲o̲f̲ ̲I̲n̲f̲o̲r̲m̲a̲t̲i̲o̲n̲ ̲a̲t̲ ̲U̲s̲e̲r̲ ̲T̲e̲r̲m̲i̲n̲a̲l̲ ̲P̲o̲s̲i̲t̲i̲o̲n̲s̲
̲w̲i̲t̲h̲ ̲b̲o̲t̲h̲ ̲V̲D̲U̲ ̲a̲n̲d̲ ̲T̲e̲l̲e̲p̲r̲i̲n̲t̲e̲r̲
Transactions queued to a terminal equipped with both
VDU and teleprinter will be presented on the VDU or
Printer in accordance with the following rules:
a) P̲r̲e̲s̲e̲n̲t̲a̲t̲i̲o̲n̲ ̲o̲n̲ ̲P̲r̲i̲n̲t̲e̲r̲
- Message Coordination (format
B)
- Clean Copy (format
C2)
- Incoming Message Presentation (format
E1)
- Outgoing Message Presentation (format
E2)
- Notification of Release (format
F)
- Comment Presentation (format
G2)
- Retrieval (format
H)
- Message Deletion Notification (format
P2)
Periodically received:
- Message Status (format
N1)
- Release Status (format
Q1)
- Transaction status (format
R1)
b) P̲r̲e̲s̲e̲n̲t̲a̲t̲i̲o̲n̲ ̲o̲n̲ ̲V̲D̲U̲
- Initial Message Preparation (format
A)
- Message Editing (format
C1)
- Release of Message (format
D)
- Initial Comment Preparation (format
G1)
- Comment Editing (format
G3)
- Security Interrogation (format
I1)
- Security Warning (format
I2)
- Time Statement (format
J)
- Sign-In (format
K1)
- Sign-Out (format
K2)
- Change of Password (format
L)
- Text Formats (format
M)
- Terminal Status (format
S)
- Message Merge (format
O)
- Message Deletion Request (format
P1)
- Message Status (format
N2)
- Release Status (format
Q2)
- Transaction Status (format
R1)
On operator request:
- Message Status (format
N1)
- Release Status (format
Q1)
- Transaction Status (format
R1)
