top - download
⟦3e1c3ffab⟧ Wang Wps File
Length: 46715 (0xb67b)
Types: Wang Wps File
Notes: CPS/210/SYS/0001
Names: »0595A «
Derivation
└─⟦ecb9329a3⟧ Bits:30006006 8" Wang WCS floppy, CR 0041A
└─ ⟦this⟧ »0595A «
WangText
8…08…8…0e…8 7…09…7…0a…7…00…7…05…6…0a…6…0b…6…02…5…08…5…86…1
…02…
…02…
…02…
…02…CPS/210/SYS/0001
…02…820509…02……02…
CAMPS
SYSTEM
REQUIREMENTS
…02…ISSUE
3.13…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 .....................
110
3.2.3.1 Equipment and Functions
Allocatable to a Terminal Position
111
3.2.3.2 Terminal Access Control .........
116
3.2.3.2.1 Physical Access ............
116
3.2.3.2.2 Logical Access .............
117
3.2.3.2.2.1 VDUs .....................
117
3.2.3.2.2.2 Stand Alone Devices ......
119
3.2.3.3 Functional Capabilities of
Terminal Procedures .............
120
3.2.3.4 Precedence and Queuing .........
126
3.2.3.5 Terminal Modes .................
129
3.2.3.6 Status Information Available from
Terminal Positions .............
135
3.2.3.7 Presentation of Information at
Terminal Positions .............
137
3.2.3.7.1 Use of Visual Display Units ..
137
3.2.3.7.2 Requirement to Printed Output
138
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, possible stand alone devices,
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 terminals 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̲
The equipment configuration allocated to a terminal
position shall be one of the two listed below.
…02… 1) VDU with keyboard and one to four medium speed
teleprinters (ROP).
2) VDU with keyboard and medium/low speed teleprinter
(ROP).
The first type is the supervisor position, whereas
the last one is for supervisor assistants and users.
The medium/low speed teleprinter mentioned above in
a2) shall be one of the printers listed in b1) or b2)
below. It shall be possible for several VDUs to share
one printer.
b) S̲t̲a̲n̲d̲ ̲A̲l̲o̲n̲e̲ ̲E̲q̲u̲i̲p̲m̲e̲n̲t̲ ̲(̲T̲e̲r̲m̲i̲n̲a̲l̲s̲)̲
The following equipment types may be physical stand
alone devices and shall be controlled via the Supervisor
VDU, i.e. Supervisor has responsibility with respect
to security.
1) Medium speed teleprinters (ROP)
2) Low speed teleprinters (ROP)
3) Low speed teleprinters used as PTR.
4) PTP
5) PTR
6) OCR
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̲
The following CAMPS functions may be accessed from
a terminal position (VDU).
…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 the supervisor and his assistants,
whereas the last three constitutes the functions
available to all user terminals.
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…- Shared printer identification
The terminals with functional capability for Supervisor,
Message Service, Message Distribution shall always
have the highest possible classification (default
CTS) and all Special Handling categories assigned.
…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.
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.
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.
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 four 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 for user terminals
include one or more of the following functions:
- Message Preparation
- Message Reception
- Message Release
For supervisor assistance terminals may the
list include one or more of the following functions.
- Message Distribution Control
- Message Service
The list shall for the supervisor terminals
contain the following functions:
- Supervisor/Engineering Control
- Message Distribution Control
- Message Service Control
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) S̲h̲a̲r̲e̲d̲ ̲P̲r̲i̲n̲t̲e̲r̲ ̲I̲d̲e̲n̲t̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
Identification of the shared printer associated
with the terminal position (VDU).
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
- associated release terminal
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 (day) 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 (day) when 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 four 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.
9) 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.
f) D̲e̲v̲i̲c̲e̲ ̲P̲r̲o̲f̲i̲l̲e̲s̲
The CAMPS System shall to each stand alone device
associate a Device Profile. The Device Profile
shall contain the information listed below.
- Device designator
- Device type
- Classification
- Multiply paper
PTP (dedicated) shall always be assigned highest
possible classification.
1) D̲e̲v̲i̲c̲e̲ ̲D̲e̲s̲i̲g̲n̲a̲t̲o̲r̲
A three letter code identifying the device
2) D̲e̲v̲i̲c̲e̲ ̲t̲y̲p̲e̲
One Device type may be specified. Possible
device types shall be: Medium Speed Teleprinters
(ROP), Low Speed Teleprinters (ROP), Low Speed
Teleprinter used as PTR, and OCR.
3) M̲u̲l̲t̲i̲p̲l̲y̲ ̲P̲a̲p̲e̲r̲
Number of PLYs per device. Only applicable for
printers.
3) C̲l̲a̲s̲s̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
The highest Classification which may be input
from or output to the device.
g) Terminal position profiles, Operator Profiles,
and Device 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 shall be performed by the CAMPS system
for VDUs and stand alone devices as specified below.
For VDUs and medium speed teleprinters, which are fitted
with a locking mechanism the access control shall be
performed on both a physical and logical level.
For other devices the access control is performed on
a logical level only.
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 (VDUs, medium speed
teleprinters). 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 output 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̲
3.2.3.2.2.1 V̲D̲U̲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-on procedure, the sign-off procedure and the
security interrogation procedure.
c) The logical access control level is entered through
the sign-on procedure during which the operator
is requested to enter his operator-id and his password.
d) During sign-on 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
e) A terminal position shall be blocked, i.e. no functions
can be performed via the terminal position,when
the following events occur during sign-on.
- three consecutive unsuccessful attempts to
enter an operator ID.
- three consecutive unsuccessful attempts to
enter a password.
- the absence of operator input for three minutes.
A warning shall be sent to the supervisor, who
may unblock the terminal when appropriate.
f) When an operator signs on he accepts the responsibility
with respect to security for that terminal position
i.e VDU. The terminal position is said to have
attended operation.
When the operator wishes to relinguish the responsibility
for that terminal position i.e. VDU with respect
to security, he signs off, activating the sign-off
procedure. The terminal is said to have unattended
operation.
The requirements to be met for attended and unattended
operation of terminal positions are as described
below.
g) 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.
Before allowing an operator to manipulate any information
to which he requests access, he shall be security
interrogated, if the information is classified
higher than NATO RESTRICTED (or as specified by
the supervisor) or is of a special handling category.
The absence of a reply within 3 minutes or three
invalid replies during a security interrogation
shall result in a blocked terminal. 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.
h) 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, the text "UNATTENDED MODE OF OPERATION
FROM time". Shall be displayed on the VDU screen.
Time shall be the time at which the VDU entered
the unattended mode of operation.
For a more detailed description of the sign-on,
sign-off, security interrogation and security warning
procedures refer to CPS/230/ICD/0001.
3.2.3.2.2.2 S̲t̲a̲n̲d̲ ̲A̲l̲o̲n̲e̲ ̲D̲e̲v̲i̲c̲e̲s̲
a) Stand alone devices, to which printers associated
with specific VDUs belong, are controlled by the
Supervisor with respect to access control refer
to section 3.2.4.1.1.7.
b) The following rules for input/output on such devices
shall apply.
1) When a device has been closed by the supervisor
no information shall be output on that device
nor shall any input be accepted by the System.
2) When a device has been opened by the supervisor
the system shall immediately before each output
action on that device perform a security check
as follows: The classification of the information
to be output is checked against the classification
contained in the device profile. If the former
is less than or equals that of the latter the
information shall be output else the information
shall be queued to the message distribution
control (MDCO) operator.
3) A medium speed teleprinter shall only be considered
opened, when both the locking mechanism of
the device is in the ON state and the device
has been opened by the supervisor.
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 user 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) 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̲)
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.
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) 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̲ ̲(̲f̲o̲r̲m̲a̲t̲ ̲C̲1̲)̲
Messages, for which a first draft has been
created, may be edited or sent to coordination
or release by invocation of the Continue Message
Preparation Procedure.
4) 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 is requested,
are displayed at the release officer's 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
Staff Cell (Notification of release (format
F)).
5) 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.
6) 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.
7) 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.
8) N̲e̲w̲ ̲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̲)̲
During preparation of the first draft of a
comment the comment header and comment text
is entered. 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.
9) 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.
10) C̲o̲n̲t̲i̲n̲u̲e̲ ̲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̲3̲)̲
Comments which have been retained may be edited
and sent to addressed Staff Cells by invocation
of the continue comment preparation procedure.
Editing is performed by use of the correction
procedures.
11) R̲e̲t̲r̲i̲e̲v̲a̲l̲ ̲(̲f̲o̲r̲m̲a̲t̲ ̲H̲)̲
This format is employed to retrieve and display
both incoming and outgoing messages, as well
as comments.
12) 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̲)̲
This format is used by the system to request
the terminal operator to identify himself by
entering his personal password.
13) S̲e̲c̲u̲r̲i̲t̲y̲ ̲W̲a̲r̲n̲i̲n̲g̲ ̲(̲f̲o̲r̲m̲a̲t̲ ̲I̲)̲
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.
14) S̲i̲g̲n̲-̲o̲n̲ ̲(̲f̲o̲r̲m̲a̲t̲ ̲K̲1̲)̲
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.
15) S̲i̲g̲n̲-̲o̲f̲f̲ ̲(̲f̲o̲r̲m̲a̲t̲ ̲K̲2̲)̲
This procedure is invoked by an operator when
he relinquishes the responsibility for a user
terminal and the messages displayed and/or
printed out.
16) 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.
17) M̲e̲s̲s̲a̲g̲e̲ ̲S̲t̲a̲t̲u̲s̲ ̲(̲f̲o̲r̲m̲a̲t̲ ̲N̲)̲
By use of this command the operator may request
the message status report to be presented at
his terminal position.
18) A̲p̲p̲e̲n̲d̲ ̲M̲e̲s̲s̲a̲g̲e̲ ̲(̲f̲o̲r̲m̲a̲t̲ ̲O̲)̲
This procedure is used to compile an outgoing
message using sections of existing messages.
19) 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̲)̲
This command is used by an originator to request
the deletion of a message.
20) 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, which was requested deleted
by the supervisor, has been deleted.
21) M̲e̲s̲s̲a̲g̲e̲ ̲R̲e̲l̲e̲a̲s̲e̲ ̲S̲t̲a̲t̲u̲s̲ ̲(̲f̲o̲r̲m̲a̲t̲ ̲Q̲)̲
This command is used by the releasing officer
to obtain the status of messages submitted
to him for release since 00.00 hour.
22) D̲e̲l̲i̲v̲e̲r̲y̲ ̲S̲t̲a̲t̲u̲s̲ ̲(̲f̲o̲r̲m̲a̲t̲ ̲R̲)̲
This command is used by a terminal operator
to obtain a list of all transactions delivered
to his terminal since 00.00 hour.
23) 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.
24) 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.
25) C̲o̲r̲r̲e̲c̲t̲i̲o̲n̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲s̲
Correction procedures are used in message and
comment preparation (Formats A, C1, M, G1,
G3). The user may correct/change the display
on the VDU screen by means of the edit functions.
The edit functions are of two types, format
edit and field edit.
Format edit is used to insert/delete predefined
lines for data entry. This facility is only
available in Formats A, C1, M, G1, and G3.
Field edit is used to change data within a
field. The user selects the data entry field
to be edited by cursor control, then edits
by character overwrite within the field.
The user may command a printed copy of the
edited message.
b) T̲r̲a̲n̲s̲a̲c̲t̲i̲o̲n̲ ̲C̲o̲n̲t̲r̲o̲l̲
The functions listed below shall be available to
the user for transaction control:
Suspend/return to current menu function
Cancel function
Delete and present next function
Keep and present next function
Print function
The system shall respond to the control functions
as follows:
Whenever the system accepts input of the transaction
control functions, the activation of a function
shall cause the system to execute the function,
if applicable. If not applicable for the transaction
in progress, or for the current state of processing
the system shall respond by displaying a proper
error message to the user.
c) S̲u̲s̲p̲e̲n̲d̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲
1) Activation of the suspend function shall cause
the transaction in progress (if any) to be
suspended, and the menu which led to the present
transaction to be displayed. The terminal shall
be set into the interactive mode of operation
and be available for user initiation of a new
transaction.
2) Suspension shall be as specified below:
a) When one of the interactive procedures
listed below is in progress activation
of the suspend function shall cause the
procedure to be interrupted in such a way
that it later can be resumed from the point
at which it was interrupted.
- New Message Preparation (format
A)
- Continue Message Preparation (format
C1)
- Comment Preparation (format
G1)
- Continue Comment Preparation (format
G3)
- Message Append (format
O)
- Predefined Message preparation (format
M)
b) Resuming a suspended transaction of the
above listed types (in a) shall be achieved
through the commands continue preparation
(format C1, G3)
c) Message Append (format O) is incorporated
in New Message Preparation (format A) and
continue message Preparation (format C1).
Suspension shall not be possible from the
point in time where the append request
has been accepted by the system until the
point in time where the user again is allowed
to access the message.
d) When information queued for presentation
on the VDU is displayed on the screen activation
of the suspend key shall result in the
message staying in the queue. When later
accessed, presentation shall be commenced
as usual, i.e. with presentation of the
first page.
The queued information applicable is:
- Messages for coordination (format
B)
- Messages for Release (format
D)
- Incoming Messages (format
E1)
- Outgoing Messsages (format
E2)
- Notification of Release (format
F)
- Comments (format
G2)
- Notification of Deletion (format
P2)
e) For format D (Message Release) suspension
shall only be effective until the point
in time where the release decision has
been entered into and accepted by the system.
f) When one of the transactions listed below
is in progress activation of the suspend
functions shall cause a proper error message
to be displayed (i.e. "invalid entry"):
- Retrieval (format
H)
- Security procedures (format
I)
- Sign on (format
K1)
- Sign off (format
K2)
- Outgoing Message/Comment Status (format
N)
- Message Deletion Request (format
P1)
- Release Status (format
Q)
- Delivery Status (format
R)
3) Whenever the terminal is in Receive Mode and
the transaction in progress is of precedence
FLASH, the activation of the suspend function
shall have no effect.
d) C̲a̲n̲c̲e̲l̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲
1) The cancel function shall allow the user to
cancel the transactions which he has commenced
before normal termination, and cause the VDU
screen to be blanked.
2) Cancel shall be as specified below:
a) When one of the interactive procedures
listed below is in progress activation
of the cancel, functions shall cause the
current transaction to be annulled and
the resources associated with the partly
completed transaction to be released for
use of other transactions
- New Message Preparation (format
A)
- Continue Message Preparation (format
C1)
- New Comment Preparation (format
G1)
- Continue Comment Preparation (format
G3)
- Predefined Message Preparation (format
M)
b) The cancellation shall only apply to the
transaction itself, e.g. if the cancel
function is activated during Continue Message
Preparation the message retained by the
system shall be in the same state as it
was prior to the cancelled Continue Message
Preparation procedure was invoked.
c) When one of the transactions listed below
is in progress activation of the cancel
function shall have the following effect:
Until the point in time where the system
has accepted the request, the request shall
be ignored, after this point in time and
until the point in time where the request
has been performed activation of the cancel
function shall have no effect. When the
requested display is on the screen (not
applicable for format P1 and O) activation
of the cancel function shall cause the
screen to be blanked.
- Retrieval (format
H)
- Message Deletion Request (format
P1)
- Append Message (format
O)
- Outgoing Message/Comment Status (format
N)
- Release Status (format
Q)
- Delivery Status (format
R)
d) When information queued for presentation
on the VDU is displayed on the screen activation
of the cancel function shall cause the
message to be removed from the queue.
e) The queued information applicable is
- Messages for coordination (format
B)
- Incoming Messages (format
E1)
- Outgoing Messages (format
E2)
- Notification of Release (format
F)
- Comments (format
G2)
- Notification of Deletion (format
P2)
f) When one of the transactions listed below
is in progress activation of the cancel
key shall have no effect:
- Message Release (format
D)
- Security procedures (format
I)
- Sign-on (format
K1)
- Sign-off (format
K2)
g) In all cases not specified above activation
of the cancel function shall have no effect.
3) Activation of the cancel key shall cause the
terminal to change its mode of operation to
interactive mode.
e) D̲e̲l̲e̲t̲e̲ ̲a̲n̲d̲ ̲P̲r̲e̲s̲e̲n̲t̲ ̲N̲e̲x̲t̲ ̲M̲e̲s̲s̲a̲g̲e̲
1) The delete and Present Next message shall only
have effect when the terminal is operating
in response mode or receive mode.
2) The activation of the Delete and Present Next
Message key shall cause the item, of which
a part is currently displayed on the screen,
to be removed from the queue and the next item
in the queue to be displayed.
f) K̲e̲e̲p̲ ̲a̲n̲d̲ ̲P̲r̲e̲s̲e̲n̲t̲ ̲N̲e̲x̲t̲ ̲M̲e̲s̲s̲a̲g̲e̲
1) The Keep and Present Next Message function
shall only have effect when the terminal is
operating in either response mode, receive
mode or release mode.
2) The activation of the Keep and Present Next
Message funtion shall cause the item, of which
a part is currently displayed on the screen,
to stay in the queue and the next item in the
queue to be displayed.
3) When the terminal is operating in receive mode
and the transaction currently displayed is
of precedence FLASH, activation of the Keep
and Present Next Message function shall have
no effect.
g) P̲r̲i̲n̲t̲
1) Activation of the Print function shall cause
the item for which print is requested to be
queued for print-out at the printer logically
associated the VDU.
2) The item for which print is requested shall
be identified as the one, for which a part
is currently displayed on the screen.
3) When the terminal is in Release mode, the effect
of the activation of the print function shall
only be as specified in 1) and 2) above, and
further cause the item to remain in the queue
and still be displayed.
4) When the terminal is in either receive mode
or in response mode the activation of the print
function shall have the effect as specified
in 1) and 2) above, and further cause the item
to be removed from the queue and the next item
in the queue to be displayed.
5) When the terminal is in interactive mode the
effect of the Print funcion shall be as specified
below:
a) For the transactions listed below the activation
of the print functions shall only have
effect while the system allow the user
to enter his decisions for further treatment
of the transaction (i.e during presentation
of format A-3 for format A and C1 and during
presentation of format G1-3 for format
G1 and G3) in which case the effect shall
be as specified in 1) and 2) above and
further cause the item to remain on the
screen.
- New Message Preparation (format
A)
- Continue Message Preparation (format
C1)
- New Comment Preparation (format
G1)
- Continue Comment Preparation (format
G3)
- Predefined Message (format
M)
b) The activation of the Print function shall
have no effect for the transactions listed
below.
- Message Append (format
O)
- Security Procedures (format
I)
- Sign-on (format
K1)
- Sign-off (format
K2)
- Message Deletion Request (format
P1)
c) For the transactions listed below the activation
of the print function shall only have effect
during the presentation of the requested
information/retrieved item.
- Retrieval (on-line) (format
H)
- Status formats (format
N,Q,R)
The effect shall be as specified in 1) and
2) above.
d) For off-line retrieved items queued in
the response queue refer g4).
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 or a stand alone
device 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.
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, M)
- Message Editing (format C1)
- Message Coordination (format B)
- 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.
- Security procedures (format I, K1,
K2)
- Append Message (format O)
The transactions Append Message has been assigned
to the precedence level FLASH when it is 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:
None. …86…1 …02… …02… …02… …02…
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.
- Message Status (format N)
- Delivery Status (format R)
- Release Status (format Q)
- Message Deletion (format P1)
g) Q̲u̲e̲u̲i̲n̲g̲
1) When transactions addressed to a terminal are
distributed by the system they shall be queued
for that terminal in accordance with their
type as specified below:
- Response queue:
Deletion Notification (format P2)
Release Notification (format F)
Items retrieved from off-line database
- Release queue:
Messages for release (format D)
- Receive queue:
Messages for coordination (format
B)
Incoming messages (format
E1)
Outgoing messages (format
E2)
Comments (format
G2)
a) Two types of queuing shall exist:
- precedence queuing
- non-precedence queuing
b) The response queue shall be of the non-precedence
type.
c) The release queue and the receive queue
shall be of the precedence type.
2) For a queue for which precedence queuing is
specified, the queuing shall be in accordance
with a) and b) below:
a) A transaction shall be queued in accordance
with the assigned precedence level, i.e.
it shall be queued before all those transactions
of lower precedence and after all those
transactions of higher precedence which
are queued for that terminal position.
b) Queuing of transactions belonging to the
same precedence level shall be as follows:
- The order in which transactions shall
be
queued is that of their time of queuing
to
the terminal.
3) For a queue for which non-precedence queuing
is specified, the queuing shall be as specified
below:
The order in which transactions shall be queued
is that of their time of arrival to the queue.
h) P̲r̲e̲e̲m̲p̲t̲i̲o̲n̲ ̲f̲o̲r̲ ̲V̲D̲U̲/̲P̲r̲i̲n̲t̲e̲r̲
1) V̲D̲U̲
a) There is no preemption of VDU
transactions. However the user is made
aware of the arrival of a FLASH message
in
his queue by means of audio and visual
alarm.
b) When transactions of precedence level FLASH
has been queued for a VDU for time T it
shall be sent to the Message Distribution
Control operator (MDCO) by the system,
and cause an audible alarm at the MDCO
position. However, if the user is already
displaying information of precedence FLASH,
information of precedence FLASH shall stay
in the queue and the user shall be notified
of the arrival of additional FLASH information.
The value of T is settable by the supervisor
to 30 secs., 5 mins., 10 mins., 15 mins.
2) P̲r̲i̲n̲t̲e̲r̲
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 commenced. If the
transaction in progress is of FLASH precedence
then no preemption shall take place.
a) On completion of the FLASH transaction,
the interrupted transaction shall be recommenced
from the beginning.
b) Transactions of the precedence levels PRIORITY
and IMMEDIATE shall not break into or interrupt
those of lower precedence.
c) Preemption shall not take place during
the time period T1 as specified by the
supervisor.
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 (VDU) 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 cause the transitions, see figure 3.2.3.5-1.
A terminal position shall be considered to be in one
of the following modes of operation:
- Receive mode
- Response mode
- Release mode
- Interactive mode
a) R̲e̲c̲e̲i̲v̲e̲ ̲M̲o̲d̲e̲
In receive mode, the user shall be able to request
the display of transactions queued to the terminal
position in the receive queue.
b) R̲e̲s̲p̲o̲n̲s̲e̲ ̲M̲o̲d̲e̲
In response mode, the user shall be able to request
the display of transactions queued to the terminal
position in the response queue.
c) R̲e̲l̲e̲a̲s̲e̲ ̲M̲o̲d̲e̲
In release mode, the releaser shall be able to
request the display of transactions queued to the
terminal position in the release queue. For each
displayed transaction, the releaser shall have
the capability of entering his release decision.
d) I̲n̲t̲e̲r̲a̲c̲t̲i̲v̲e̲ ̲M̲o̲d̲e̲
In interactive mode, the user shall be able to
invoke any of the interactive transactions (formats:
A, C1, G1, G3, H, I, K2, M, N, O, P1, Q, R) as
available from the terminal position.
e) The formats applicable to each mode for the Message
preparation, the Message release and the Message
reception capability are tabulated in table 3.2.3.5-1
through 3.2.3.5-3, respectively.
Figure 3.2.3.5-1
side 114
figure 3.2.3.5-2
3.2.3.5-3
figure
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 status information
accessible from a terminal position are outlined (ref.
CPS/230/ICD/0001). The Status information delivered
on request will not be used during acceptant test of
busy hour performance, but only during functional test.
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.
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) D̲e̲l̲i̲v̲e̲r̲y̲ ̲S̲t̲a̲t̲u̲s̲
Delivery status shall upon request be delivered
to all terminal positions allocated one or more
of the functions:
Message Preparation
Message Release
The requested Delivery Status contains a listing
of all transactions delivered to the terminal position
since hour 00.00 that day.
c) M̲e̲s̲s̲a̲g̲e̲ ̲S̲t̲a̲t̲u̲s̲
Message Status shall upon request be delivered
terminal positions allocated the function:
Message Preparation.
The delivered received Message Status contains
the status for each message and comment originated
from the terminal position since hour 00.00 at
that day.
d) M̲e̲s̲s̲a̲g̲e̲ ̲R̲e̲l̲e̲a̲s̲e̲ ̲S̲t̲a̲t̲u̲s̲
Message Release Status shall upon request be delivered
at Message Release Positions, informing the Release
officer of:
- Number of Messages Submitted to
- Number of Messages Released at
- Number of Messages Deferred at
- Number of Messages Refused at
his position since hour 00.00 of that day.
e) Status reports requested by an operator will contain
the requested status of all transactions handled
since hour 00.00 of that day. For message status,
however, status of information held in abeyance,
i.e. not yet released or transmitted, shall be
retained by the system for at least two days, and
included in the Message Status.
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 contain the requirements for Visual
Display Units
Section 3.2.3.7.2 contains the requirements for printed
output.
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 attended operation) at
the five top lines of the screen. (For detailed
information refer CPS/230/ICD/0001 and CPS/230/ICD/0002).
Terminal control information is:
- transaction in progress or mode of operation
- information on amount of transactions awaiting
release, coordination, and display respectively
b) Transactions queued to the VDU for delivery, shall
be presented to the user in Page/Scroll Mode, and
the user shall be able to request the information
to be presented.
Page Mode: The information shall be presented one
page (screen) at a time and the next page shall
be presented only when the operator shall have
the facility for paging both forwards and backwards.
Scroll mode: All lines of the screen, except for
the part occupied by the VDU header, shall be rolled
one line up or down as requested by the operator.
Scrolling shall apply to the part of information
present in the VDU memory.
c) Interactive transactions shall be supported in
Page mode.
No line shall exceed 69 characters with regard
to transaction formats in this section.
3.2.3.7.2 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 printer transaction which processed
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 shall be as specified in the
SCD table 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.
