top - download
⟦e70017e5d⟧ Wang Wps File
Length: 45494 (0xb1b6)
Types: Wang Wps File
Notes: CPS/210/SYS/0001
Names: »0235A «
Derivation
└─⟦4c54cd805⟧ Bits:30006066 8" Wang WCS floppy, CR 0020A
└─ ⟦this⟧ »0235A «
WangText
1…0b…1…01…1…06…1…07…0…08…0…0f…0 /…0a…/…0f…/ .…86…H
…02…
…02…
…02…
CPS/210/SYS/0001
…02…801124
CAMPS
SYSTEM
REQUIREMENTS
ISSUE
1.2 CAMPS
T̲A̲B̲L̲E̲ ̲O̲F̲ ̲C̲O̲N̲T̲E̲N̲T̲S̲
S̲e̲c̲t̲i̲o̲n̲ ̲3̲.̲2̲.̲4̲
…02……02……02…3.2.4 Supervisory Functions ................ 143
…02……02……02……02…3.2.4.1 Supervisor Functions.............. 146
…02……02……02……02……02…3.2.4.1.1 Supervisor Commands........... 148
…02……02……02……02……02……02…3.2.4.1.1.1 Common Requirements For
Commands .................
148
…02……02……02……02……02……02…3.2.4.1.1.2 Command Processing Control 149
…02……02……02……02……02……02…3.2.4.1.1.3 Message Processing Control 150
…02……02……02……02……02……02…3.2.4.1.1.4 Terminal Position Control. 153
…02……02……02……02……02……02…3.2.4.1.1.5 Operator Control.......... 155
…02……02……02……02……02……02…3.2.4.1.1.6 External Connection
Control ..................
156
…02……02……02……02……02……02…3.2.4.1.1.7 OCR, PTR/PTP, and Stand
Alone Teleprinter Control
157
…02……02……02……02……02……02…3.2.4.1.1.8 Report Control............ 158
…02……02……02……02……02……02…3.2.4.1.1.9 Statistic Control ........ 159
…02……02……02……02……02……02…3.2.4.1.1.10 Log Control.............. 159
…02……02……02……02……02……02…3.2.4.1.1.11 Offline Storage Control.. 159
…02……02……02……02……02……02…3.2.4.1.1.12 Security Warning Control. 161
…02……02……02……02……02……02…3.2.4.1.1.13 Supervisor Engineering
Commands ................
161
…02……02……02……02……02……02…3.2.4.1.1.14 Queue Control at Restart. 161
…02……02……02……02……02……02…3.2.4.1.1.15 Message Deletion ........ 162
…02……02……02……02……02…3.2.4.1.2 Service Message Handling ..... 162
…02……02……02……02……02……02…3.2.4.1.2.1 Reception of Service
Messages .................
162
…02……02……02……02……02……02…3.2.4.1.2.2 Preparation of Service
Messages .................
162
…02……02……02……02……02…3.2.4.1.3 Message Handling ............. 163
…02……02……02……02……02……02…3.2.4.1.3.1 Message Rerun ............ 163
…02……02……02……02……02……02…3.2.4.1.3.2 Retrieval ................ 163
…02……02……02……02……02……02…3.2.4.1.3.3 Redistribution ........... 164
…02……02……02……02……02…3.2.4.1.4 Statistics Print ............. 164
…02……02……02……02……02…3.2.4.1.5 Report Print ................. 164
…02……02……02……02……02…3.2.4.1.6 Log Print .................... 164
…02……02……02……02…3.2.4.2 Message Service .................. 164
…02……02……02……02……02…3.2.4.2.1 Incoming Message Assistance .. 168
…02……02……02……02……02…3.2.4.2.2 Routing Indicator Assignment . 168
…02……02……02……02……02…3.2.4.2.3 Handling of Outgoing Messages
with Encrypted Text ..........
169
…02……02……02……02…3.2.4.3 Message Distribution
Control ..........................
169
…02……02……02……02……02…3.2.4.3.1 Distribution ................. 171
…02……02……02……02……02…3.2.4.3.2 Retrieve for Distribution .... 172
…02……02……02……02…3.2.4.4 Reports .......................... 172
…02……02……02……02……02…3.2.4.4.1 General ...................... 172
…02……02……02……02……02…3.2.4.4.2 Security Reports ............. 173
…02……02……02……02……02…3.2.4.4.3 Warning Reports .............. 174
…02……02……02……02……02…3.2.4.4.4 Command Completion Reports ... 174
…02……02……02……02……02…3.2.4.4.5 Traffic Reports .............. 175
…02……02……02……02……02…3.2.4.4.6 Channel Reports .............. 176
…02……02……02……02……02…3.2.4.4.7 Deletion Request Report ...... 176
…02……02……02……02…3.2.4.5 Engineering Functions ............ 176
3.2.4.5.1 Engineering Function Imple-
mentation ....................
176
3.2.4.5.2 Engineering Functions
Detailed Definition ..........
177
3.2.4.5.3 H/W Configuration Status Dis-
play .........................
177
3.2.4.5.4 Software Development .........
178
3.2.4…02…S̲u̲p̲e̲r̲v̲i̲s̲o̲r̲y̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲s̲
The supervisory functions are functions to control
a CAMPS site as specified in this section.
The supervisory functions may be divided into
…02…- Supervisor functions (supervisor position)
…02…- Message service functions (service position)
…02…- Message distribution control (distribution position)
…02…- Engineering functions (engineering position)
The supervisory functions may be allocated to terminal
positions with equipment configurations as specified
below:
a) The supervisor position has always assigned a VDU
and one or more (up to 4) medium speed teleprinters.
There is only one supervisor position at a time.
b) A message service position has always assigned
a VDU and a medium speed printer. There may be
up to 4 message service positions.
c) A message distribution position has always assigned
a VDU and a medium speed teleprinter. There may
be up to 4 message distribution positions.
d) The engineering position has equipment required
to control hardware and software such as lineprinter,
console, floppy disk or similar.
The CAMPS supervisory functions are shown in fig. 3.2.4-1.
Figure 3.2.4-1
Figure 3.2.4-2
Terminal positions may be assigned the supervisory
functions in parallel as marked in matrix fig. 3.2.4-2
Where more than one of the functions shown in fig.
3.2.4-2 is assigned to a supervisory terminal, the
operator selects whether he will perform supervisory
functions, i.e. supervisor, MDCO, and Message Servicing,
or any other function. Having selected supervisory
functions these will be simultaneously available to
him with functions interleaving on a transactional
basis.
Supervisor position, messages service positions and
message distribution positions shall have use of standard
terminal procedures and functions as described below.
a) Sign-in, and sign-out are identical to those at
non supervisory terminal positions.
b) Cancel has the effect that any transaction not
yet accepted by the central processor is disregarded
(e.g. a command prepared but not given confirmation
is disregarded).
c) Suspend does not apply to supervisory terminal
positions.
d) Preemption does not apply to supervisory terminal
positions.
e) Delete character and enter new character (VDU input).
f) Delete entry of last variable data field and make
new entry.
3.2.4.1…02…S̲u̲p̲e̲r̲v̲i̲s̲o̲r̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲s̲
At system generation time 2 terminal positions are
designated as supervisor position.
The 2 terminal positions should be so connected to
the central processor that availability requirements
are met.
One of the 2 terminal positions is the active supervisor
position.
A special assign command is used to determine which
of the 2 terminal positions is the active supervisor
position.
Issue of the special command from one of the 2 terminal
positions shall have the effect that the issuing terminal
position becomes the active supervisor position.
The effect on the presently active supervisor position
of issuing the special command from the inactive supervisor
position shall be similar to cancel.
The supervisor functions are subdivided into:
1) Supervisor command functions
2) Service message handling
3) Message Handling
4) Statistics print
5) Report print
6) Log print
The supervisor assigns print functions to the printers
associated with his position. The functions are:
1) Supervisor print
2) Report print
3) Log print
4) Statistics print.
Any combination of above printer functions may be assigned
to the same printer (if less than 4 medium speed teleprinters
are assigned).
If more than one printout function is assigned to one
printer, printout is per priority as defined below:
1) Supervisor printout
2) Report print
3) Statistics print
4) Log print
3.2.4.1.1 S̲u̲p̲e̲r̲v̲i̲s̲o̲r̲ ̲C̲o̲m̲m̲a̲n̲d̲s̲
3.2.4.1.1.1 C̲o̲m̲m̲o̲n̲ ̲R̲e̲q̲u̲i̲r̲e̲m̲e̲n̲t̲s̲ ̲f̲o̲r̲ ̲C̲o̲m̲m̲a̲n̲d̲s̲
a) The command format shall consist of a brief mnemonic
code related to the "command function" from six
to eight characters in length, including space
followed by one or more variable data fields as
appropriate to the command function.
The entry of a supervisor command shall be subject
to the data entry time-out.
The action resulting from a command shall only
commence after the operator has entered a confirmation
signal as defined below.
Until confirmation signal is sent the operator
shall be able to cancel the command.
b) Supervisor commands are protected or unprotected
as specified by the supervisor.
Protected commands shall be accepted by the system
only if accompanied by the permissive entry code
(PEC).
The PEC shall consist of six alphanumeric characters.
A command shall exist for modifying the PEC.
c) All commands shall be displayed on the VDU for
confirmation.
Commands shall be issued to the system upon operator
entry of a confirmation code.
The confirmation code shall either be a short alphanumeric
character string (3 characters) or a function key.
Commands shall be disregarded by the system if
the operator instead of confirmation code gives
a cancel.
Upon command completion a completion report shall
be issued.
The system response to unacceptable commands shall
be explicitly stated to allow the operator to identify
the reason for rejection:
- invalid data entry.
- command function not allowable from that terminal.
- not preceded by the permissive entry code (PEC).
- ineffective (e.g., ascribing functions to non-existent
terminals).
Update of a parameter by a command shall - unless
otherwise specified - have effect for future access
to the parameter.
3.2.4.1.1.2…02…C̲o̲m̲m̲a̲n̲d̲ ̲P̲r̲o̲c̲e̲s̲s̲i̲n̲g̲ ̲C̲o̲n̲t̲r̲o̲l̲
a) A command shall exist to specify whether a given
command is protected or not.
b) Ten short command codes shall exist.
Each short command code consists of one or two
alphanumeric characters.
A command shall exist to specify the assignment
of commands to short command codes.
Entry of a short command code shall cause display
of the normal mnemonic.
c) Use of commands shall if specified cause storage
of a command utilization record.
A command utilization record shall consist of:
- command code
- time of command confirmation
- terminal position used.
A command shall exist causing printout of command
utilization records recorded in specified time
interval.
The printout shall be on the supervisor printer.
d) A list of commands with restrictive effect on the
system operation or configuration shall exist.
A command shall exist for display and update of
above list.
When appropriate the restriction(s) shall be displayed
to the operator during execution of these commands
or on request.
3.2.4.1.1.3 M̲e̲s̲s̲a̲g̲e̲ ̲P̲r̲o̲c̲e̲s̲s̲i̲n̲g̲ ̲C̲o̲n̲t̲r̲o̲l̲
Message processing is controlled through update of
parameters in the automatic processing as specified
below.
a) Addressing tables:
Commands shall exist to display and modify tables/table-entries
as specified below.
The term "table" is a logical relationship without
implying restrictions on the physical layout when
implemented.
1) P̲L̲A̲ ̲T̲a̲b̲l̲e̲
- PLA text
- Reference number
- Associated routing indicators
- Indication ZEN to be used with PLA
- Indication for insertion of accounting
information (FL10)
2) A̲I̲G̲ ̲T̲a̲b̲l̲e̲
- PLA's as ACTION
- PLA's as INFO
3) T̲a̲b̲l̲e̲ ̲o̲f̲ ̲R̲I̲'̲s̲ ̲r̲e̲c̲o̲g̲n̲i̲z̲e̲d̲ ̲b̲y̲ ̲C̲A̲M̲P̲S̲
- Per RI the associated channel designator
of the channel to be used when routing
outgoing messages.
- In common for all RIs whether outgoing
messages shall be routed automatically
or be output to papertape punch.
4) T̲a̲b̲l̲e̲ ̲o̲f̲ ̲R̲I̲s̲ ̲f̲o̲r̲ ̲t̲h̲i̲s̲ ̲C̲A̲M̲P̲S̲ ̲S̲i̲t̲e̲
This table contains all RIs for Headquarters
served by this CAMPS.
5) T̲a̲b̲l̲e̲ ̲o̲f̲ ̲H̲e̲a̲d̲q̲u̲a̲r̲t̲e̲r̲s̲ ̲f̲o̲r̲ ̲t̲h̲i̲s̲ ̲C̲A̲M̲P̲S̲ ̲S̲i̲t̲e̲
This table contains the two PLAs for each of
the Headquarters served by this CAMPS.
6) S̲I̲C̲ ̲T̲a̲b̲l̲e̲s̲
One SIC table is defined per Headquarters.
In each SIC-table the distribution within the
Headquarters based on SICs.
One SIC defined by all three letters may identify
an SDL (see below) or a group of SICs identified
by the first letter or by the first two letters
may identify an SDL. Further an originator
may identify an SDL.
7) S̲D̲L̲ ̲t̲a̲b̲l̲e̲
- Associated SCD's for normal traffic.
- Associated SCD's for exercise traffic.
8) S̲C̲D̲ ̲t̲a̲b̲l̲e̲
- Terminal designator associated to the staff
cell.
- Number of printed copies to each staff
cell.
9) S̲u̲p̲e̲r̲v̲i̲s̲o̲r̲ ̲A̲s̲s̲i̲s̲t̲e̲d̲ ̲D̲i̲s̲t̲r̲i̲b̲u̲t̲i̲o̲n̲
Specify routing of incoming messages for message
distribution control as one of the following:
- All incoming messages
- All incoming messages of specified classification
- All incoming messages except messages of
specified classifications.
10) The supervisor shall be able to modify the
disc fill rate threshold.
11) O̲t̲h̲e̲r̲
Specify terminal (line identification for distribution
of encrypted incoming messages and outgoing
messages where no channel of proper authorization
can be found.
Specify staff cell for printout of messages
containing ZEN associated with one or more
PLAs.
b) ACP127 parameters.
Select detection of exercise indicator.
Specify for outgoing messages (ACP127) that 18
spaces are used instead of 5 spaces in Format Line
1.
Specify for outgoing messages that in FL 2 precedence
warning shall be used for all precedence levels
and not only Flash.
Specify for outgoing messages whether both R and
U series RI's are used in FL 2 or whether FL 2a
shall contain R series only and FL 2b shall contain
U series only.
Specify for outgoing messages that in FL5 2 figures
indicating year shall be inserted after month or
alternatively no provision for year.
Maintain the year for use if year is specified
to be included.
Select for outgoing messages which zone-time letter
to be used.
Specify in common for FL7 and FL8 if RI's shall
be included.
c) Counters.
Reset to 0001 of the system print control number
of printed output common to all hardcopy reception
terminals.
Reset to 0001 of the special handling control number
of printed output common to all hardcopy reception
terminals.
Reset/set value of each release series.
3.2.4.1.1.4 T̲e̲r̲m̲i̲n̲a̲l̲ ̲P̲o̲s̲i̲t̲i̲o̲n̲ ̲C̲o̲n̲t̲r̲o̲l̲
A command shall exist for display and update of capabilities
and parameters of terminal positions as specified below.
The supervisor command capability cannot be reassigned
by this command:
a) Indicate that a terminal position has reception
capability.
b) Indicate that a terminal position has preparation
capability.
c) Indicate that a terminal position has distribution
capability (MDCO).
d) Specify for preparation position the associated
release position.
e) Indicate that a terminal position has Message service
capability.
f) Indicate that a terminal position has release capability.
g) Not used.
h) Specify for release positions the message originator
designator to be inserted in FL6 (Routing Indicator).
i) Specify for release positions if acknowledge required
on Flash messages.
j) Specify terminal position designator.
k) Specify terminal position classification.
l) Specify special handling categories that may be
handled at terminal position.
m) Specify security classification leading to security
interrogation for all terminals within a CAMPS
site before display/print of classified information.
n) Specify special handling categories leading to
security warning for all terminals within a CAMPS
site before display/print of classified information.
o) Specify if classification above SECRET shall lead
to the special security warning for all terminals
within a CAMPS site before display/print of classified
information.
p) Specify identification of operators who may sign
in at terminal position.
q) Specify VDU identification of configured VDU or
blank if no VDU.
r) Specify Medium Speed Teleprinter identification
of configured Medium Speed Teleprinter or empty
if none.
s) Specify Low Speed Teleprinter identification of
configured low speed teleprinter or empty if none.
t) VDU or teleprinter reconfiguration may only be
performed if the terminal position is unmanned
and the equipment is not allocated any other terminal
position.
u) Specify per equipment type number of lines used
in printout when paging is applied.
v) Specify per equipment type number of blank lines
between pages.
w) A command shall exist to block and unblock terminal
position.
x) A command shall exist to display total queue length
per terminal for all messages awaiting delivery
at reception positions.
y) Specify on a per site basis frequency of summary
report automatically printed at terminal positions
with hardcopy device.
z) Select per terminal type the allowed delay that
does not require preemption to 5, 10.....30 seconds.
3.2.4.1.1.5…02…O̲p̲e̲r̲a̲t̲o̲r̲ ̲C̲o̲n̲t̲r̲o̲l̲
a) Indicate that operator may act as operator of distribution
position.
b) Indicate that operator may act as operator of service
position.
c) Indicate that operator may act as operator of release
position.
d) Indicate that operator may act as operator of preparation
position.
e) Indicate that operator may act as operator of reception
position.
f) Indicate whether operator has access to exercise
traffic only or to all traffic types.
g) Indicate that operator may act as supervisor operator.
h) Classification of operator.
i) Password of operator.
j) Indicate that time limit shall apply for operator
password.
k) Set password time limit in increments of days with
max. 5 days.
l) A command shall exist to initiate print of all
operator identifications and passwords. This command
shall be protected by default.
3.2.4.1.1.6…02…E̲x̲t̲e̲r̲n̲a̲l̲ ̲C̲o̲n̲n̲e̲c̲t̲i̲o̲n̲ ̲C̲o̲n̲t̲r̲o̲l̲
a) The supervisor shall by means of command(s) be
able to control external connections
…02……02……02……02…-NICS TARE
…02……02……02……02…-SCARS II
…02……02……02……02…-ACE CCIS
…02……02……02……02…-TRC
-POINT-TO-POINT CONNECTIONS
to the extent described below.
b) The control shall be performed through commands
capable of displaying and updating parameters in
the control of external connections.
c) Specify for each channel the 3 letter channel designator.
d) Select sequence type to 001 through 999 or 0001
through 9999 per channel.
e) Select reset schedule to either daily reset to
001/0001 at 2400 hours or reset only by wrap around
(i.e. 001 after 999 and 0001 after 9999).
f) Reset of sequence for each sequence.
g) Specify max. classification of messages transmitted
over the channel.
h) Specify that a service message shall be received
daily in the interval 2345 to 0015.
i) Selection of periodicity of receiving self-addressed
channel check messages as either 30 minutes, 60
minutes, or none on incoming channels from TRCs
(TARE class "X").
j) Selection of periodicity for automatic transmission
of channel continuity messages as either 5 minutes
or none on channels to NICS TARE (TARE class "A").
k) Selection of periodicity of channel check messages
and channel continuity messages as 5 minutes to
30 minutes in increments of 5 minutes or none on
channels to other connected external stations.
l) Specify whether service messages shall be automatically
generated if more than 50 identical consecutive
characters have been received.
m) Selection of allowed delay without requiring preemption
as 5 to 30 secs. in increments of 5 secs.
n) Select time limit in common for all channels for
arrival of receipt report for Flash messages to
2,4,6....20 minutes.
3.2.4.1.1.7…02…O̲C̲R̲,̲ ̲P̲T̲R̲/̲P̲T̲P̲ ̲a̲n̲d̲ ̲S̲t̲a̲n̲d̲ ̲A̲l̲o̲n̲e̲ ̲T̲e̲l̲e̲p̲r̲i̲n̲t̲e̲r̲ ̲C̲o̲n̲t̲r̲o̲l̲
a) The OCR, PTR/PTP and Stand Alone teleprinter equipment
may be controlled to the extent specified below.
The OCR and PTR/PTP are used for entry of complete
messages as described in 3.2.1.4.
b) The OCR and PTR/PTP are used for entry of complete
messages as described in 3.2.1.4.
c) The control shall be in form of commands capable
of displaying and updating status as outlined below.
d) Specify to CAMPS to
- Accept input of messages from the OCR
- Not accept input of messages from the OCR…02…(logically
disconnected)
e) Specify to CAMPS to
- Accept input of messages from PTR
- Accept no input from PTR
(logically disconnected)
f) Specify to CAMPS to
- Output messages awaiting punch to the PTP
- Output no messages on the PTP
g) Specify to the CAMPS central equipment for each
lowspeed teleprinter line to
- Either output messages awaiting output
- or allow input of complete messages
- or accept no input or output (logically disconnected)
h) Specify for each medium speed teleprinter
- Either output messages awaiting output
- or allow no output (logically disconnected)
i) Specify for each stand alone teleprinter
- Terminal ID
- Classification
3.2.4.1.1.8…02…R̲e̲p̲o̲r̲t̲ ̲C̲o̲n̲t̲r̲o̲l̲
a) Commands shall exist to control reports as specified
below.
b) Select for each report type whether to be printed
in near real time or to be stored on the outstanding
report file.
c) Reassign Report print. The supervisor shall be
able to select any of the receive-only teleprinters
associated with his terminal position as report
printer. The output already issued for the printer
that was assigned shall be printed. The printout
on the assigned printer shall start with the first
not printed report.
d) Initiate printout of all outstanding reports either
on Report printer or on Log printer.
3.2.4.1.1.9 S̲t̲a̲t̲i̲s̲t̲i̲c̲ ̲C̲o̲n̲t̲r̲o̲l̲
Commands shall exist to control statistics print as
specified below.
Reassign statistics print. The supervisor shall be
able to select any of the receive-only teleprinters
associated with his terminal position as Statistics
printer. The output already issued for the printer,
that was assigned shall be printed. The printout on
the assigned Statistics printer shall start with the
first not printed statistics.
3.2.4.1.1.10…02…L̲o̲g̲ ̲C̲o̲n̲t̲r̲o̲l̲
Commands shall exist to control Log printout as specified
below.
Reassign Log print. The supervisor shall be able to
assign any of the receive-only teleprinters associated
with his terminal position as Log printer. The output
already issued for the printer that was assigned shall
be printed. The printout on the assigned Log printer
shall start with the first not printed Log entry.
3.2.4.1.1.11…02…O̲f̲f̲l̲i̲n̲e̲ ̲S̲t̲o̲r̲a̲g̲e̲ ̲C̲o̲n̲t̲r̲o̲l̲
a) Commands shall exist to control the offline storage
for archiving/retrieval as specified below.
b) If drive/interface is shared between active central
processor and standby central processor then the
commands specified below using the drive/interface
shall fail if drive/interface is not allocated
to active central processor.
The drive to be used for mounting offline storage
media may be unavailable if:
l) One of the operational drives has failed so
the drive is used as spare
2) The standby processor uses the drive for software
maintenance (at the specified site).
c) Commands shall exist to control the storage to
the long term storage and to mount/dismount media
involved.
d) A command shall exist to give name to storage media
units not initialized.
e) A command shall exist to delete previously stored
information.
f) The deletion of previous stored information shall
be by overwriting the media with a data pattern.
g) When retrieving from back ground storage then the
following (or similar) sequence shall apply to
get the offline media online.
1) Ensure drive allocated and available
2) Perform physical mount of volume
3) Perform logical mount of volume by giving the
identification of the volume.
h) The mount procedure shall be implemented as a command
giving normal command completion report upon termination
of execution. The command completion report shall
identify the mounted volume.
3.2.4.1.1.12 S̲e̲c̲u̲r̲i̲t̲y̲ ̲W̲a̲r̲n̲i̲n̲g̲ ̲C̲o̲n̲t̲r̲o̲l̲
The security warning displayed at reception positions
before special handling and (level specified by supervisor)
classified messages are received shall be maintained
as described below.
A command shall exist to display and update the warning
text.
A command shall exist to display and update the five
letter code for warning
3.2.4.1.1.13 S̲u̲p̲e̲r̲v̲i̲s̲o̲r̲ ̲E̲n̲g̲i̲n̲e̲e̲r̲i̲n̲g̲ ̲C̲o̲m̲m̲a̲n̲d̲s̲
The supervisor engineering commands are those engineering
functions implemented to work from the supervisor command
position.
The commands described below are a minimum, the actual
commands shall be derived from hardware and software
design and requirement for engineering functions.
A command shall exist to initiate system integrity
check (ref. 3.2.8).
3.2.4.1.1.14 Q̲u̲e̲u̲e̲ ̲C̲o̲n̲t̲r̲o̲l̲ ̲a̲t̲ ̲R̲e̲s̲t̲a̲r̲t̲
…02…a) During restart commands shall exist to cancel messages
and transactions as specified below.
1) For each outgoing channel cancel all messages
of specified precedence.
2) For each reception position cancel all output
of specified precedence.
3) For each release position cancel all messages
of specified precedence awaiting release.
4) For each preparation position cancel all suspended
transactions.
5) Cancel all messages of specified precedence
awaiting MDCO processing.
6) Cancel all messages of specified precedence
awaiting message service.
b) Messages, for which queue elements has been cancelled
as specified above will still be available for
retrieval to the extent specified in section 3.2.7.
3.2.4.1.1.15 M̲e̲s̲s̲a̲g̲e̲ ̲D̲e̲l̲e̲t̲i̲o̲n̲
A command shall exist for the supervisor to delete
messages as specified below.
Delete messages that have been released. Parameters
shall be
- DTG
- Release Series identification
- Serial number
The deletion shall have effect for transactions not
yet initiated for the released message (e.g. printout
at terminal position, transmission over external channel).
3.2.4.1.2 S̲e̲r̲v̲i̲c̲e̲ ̲M̲e̲s̲s̲a̲g̲e̲ ̲H̲a̲n̲d̲l̲i̲n̲g̲
3.2.4.1.2.1 R̲e̲c̲e̲p̲t̲i̲o̲n̲ ̲o̲f̲ ̲S̲e̲r̲v̲i̲c̲e̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲
a) The supervisor shall have capability to receive
service messages.
b) Service messages shall be queued to the supervisor
printer on a FIFO basis by precedence.
3.2.4.1.2.2 P̲r̲e̲p̲a̲r̲a̲t̲i̲o̲n̲ ̲o̲f̲ ̲S̲e̲r̲v̲i̲c̲e̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲
a) The supervisor shall be able to prepare service
messages and abbreviated service messages by means
of format AS. (Ref. CPS/230/ICD/0002).
b) The supervisor shall be able to edit service messages
prepared using format C1S. (Ref. CPS/230/ICD/0002).
c) Whenever the supervisor completes the service message
preparation it shall automatically be processed
until transmission.
d) Upon final completion a service message is no longer
available for the supervisor except by retrieval
as specified in section 3.2.7.
3.2.4.1.3 M̲e̲s̲s̲a̲g̲e̲ ̲H̲a̲n̲d̲l̲i̲n̲g̲
3.2.4.1.3.1 M̲e̲s̲s̲a̲g̲e̲ ̲R̲e̲r̲u̲n̲
a) The supervisor shall be capable of rerunning (retransmitting)
any of the outgoing messages retained in the Historical
database.
b) The procedure is described in CPS/230/ICD/0002
and includes
1) Identification of message to be rerun
2) Generation of Pilot (i.e. format lines A, B
and C in ACP127)
3) Dispatch for transmission
c) The retrieval implicit in message rerun is processed
similar to and with the same restrictions as normal
retrieval.
d) The dispatch for transmission means queue for routing
determination.
3.2.4.1.3.2 R̲e̲t̲r̲i̲e̲v̲a̲l̲
The supervisor shall be able to retrieve messages and
other transactions as described in 3.2.7.
3.2.4.1.3.3 R̲e̲d̲i̲s̲t̲r̲i̲b̲u̲t̲i̲o̲n̲
The supervisor shall be able to redistribute locally
messages as described below:
- Incoming Messages
- Released Messages
The retrieval implicit in the redistribution shall
be similar to and with same restrictions as normal
retrieval.
3.2.4.1.4 S̲t̲a̲t̲i̲s̲t̲i̲c̲s̲ ̲P̲r̲i̲n̲t̲
Statistics shall be printed at one of the printers
assigned to the supervisor position as specified by
the supervisor.
Statistics shall be queued on a FIFO basis.
3.2.4.1.5 R̲e̲p̲o̲r̲t̲ ̲P̲r̲i̲n̲t̲
Reports shall be printed at one of the printers assigned
to the supervisor position as specified by the supervisor.
Reports shall be queued on a FIFO basis.
3.2.4.1.6 L̲o̲g̲ ̲P̲r̲i̲n̲t̲
Log print shall be performed at one of the printers
assigned to the supervisor position, as specified by
the supervisor.
Log entries shall be queued on a FIFO basis.
3.2.4.2 M̲e̲s̲s̲a̲g̲e̲ ̲S̲e̲r̲v̲i̲c̲e̲
a) The messages service function supports:
…02… 1) correction of garbled incoming messages
…02… 2) routing indicator assignment for outgoing messages
(including T instructions inserted in FL4 of ACP127
messages as applicable)
…02… 3) verification and correction of accounting informtaion
on outgoing messages.
4) validation and correction of operating signals
b) Messages shall be queued for message service per
precedence.
c) The queuing and terminal position allocation is
shown in fig. 3.2.4.2-1.
Figure 3.2.4.2-1
d) Messages without recognizable precedence level
shall be queued with immediate precedence.
e) The message service queue shall be accessed by
terminal positions with message service function
allocated as described below.
f) The terminal operator issues a 3 letter TBD sequence
to request a message from the message service queue.
g) The requesting terminal position gets the oldest
of the messages with highest precedence (i.e. prioritized
FIFO queue).
h) When a queue element has been obtained from the
service queue it is logically deleted from the
queue so that 2 simultaneous requests will not
get the same message for service.
i) Any discontinue of processing for a queue element
(e.g. cancel) returns the element as the oldest
element for the appropriate precedence level.
j) In case of discontinue of processing the message
shall be as if it was not processed by the service
operator.
k) The message for service is displayed at the service
position together with a short notification why
the message has been sent for message service.
l) The notification shall be displayed before the
message itself.
m) The notification shall indicate which of the following
message service functions is expected
…02……02…1) garble correction
…02……02…2) group count assignment
…02……02…3) RI assignment
n) The display of a message to the message service
position is in the actual format for incoming messages
and in the ACP127 converted form for outgoing messages.
o) Incoming messages returned for further processing
as described below will be subject to complete
renewed analysis of ACP127 format.
p) Outgoing messages returned for further processing
are only analysed for RI's and precedence in FL2
or B to determine external channels and precedence.
3.2.4.2.1. I̲n̲c̲o̲m̲i̲n̲g̲ ̲M̲e̲s̲s̲a̲g̲e̲ ̲A̲s̲s̲i̲s̲t̲a̲n̲c̲e̲
The message service operator shall be capable of processing
incoming messages as described below.
a) He shall be capable of modifying/correcting any
part of the message.
b) He shall be capable of queing the message for printout
at terminal positions allocated to specified staff
cells.
c) He shall be capable of generating a one line annotation
to be printed with the message at all terminal
positions as derived above from specification of
staff cells.
d) He shall be capable of printing the message at
his own printer.
e) The printout shall be in the format as received
and corrected by the servicer with the annotation
described above in front.
f) He shall be capable of returning the message to
the queue for processing-of-incoming-messages for
renewed processing.
3.2.4.2.2 R̲o̲u̲t̲i̲n̲g̲ ̲I̲n̲d̲i̲c̲a̲t̲o̲r̲ ̲A̲s̲s̲i̲g̲n̲m̲e̲n̲t̲
a) Messages with PLAs which require manual addition
of routing indicator shall be queued for message
service for routing indicator assignment.
b) The message shall be displayed in ACP127 headed
by a list of those PLAs entered with "X" in the
initial preparation.
c) The message servicer shall be capable of modifying
the message in order to include the corresponding
RIs.
d) The message servicer shall after assignment of
missing RIs queue the message for routing determination.
3.2.4.2.3 H̲a̲n̲d̲l̲i̲n̲g̲ ̲o̲f̲ ̲O̲u̲t̲g̲o̲i̲n̲g̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲ ̲w̲i̲t̲h̲ ̲E̲n̲c̲r̲y̲p̲t̲e̲d̲ ̲T̲e̲x̲t̲
a) Messages with encrypted text shall be queued for
message service for verification and possible modification
of group count.
b) The message shall be displayed in ACP127 headed
by indication "Group Count Verification".
c) The message servicer shall be able to modify the
message in order to correct the group count.
d) The message servicer shall after verification and
possibly modification of the group count queue
the message for routing determination.
3.2.4.3 M̲e̲s̲s̲a̲g̲e̲ ̲D̲i̲s̲t̲r̲i̲b̲u̲t̲i̲o̲n̲ ̲C̲o̲n̲t̲r̲o̲l̲
a) The message distribution function supports
1) Specification of distribution instructions
replacing or completing automatically determined
distribution (Distribution).
2) Retrieval of messages from Historical database
for distribution as specified (Retrieve for
distribution)
b) Messages shall be queued for message distribution
per precedence.
c) The queuing and terminal position allocation is
shown in fig 3.2.4.3-1.
Figure 3.2.4.3-1
3.2.4.3.1 D̲i̲s̲t̲r̲i̲b̲u̲t̲i̲o̲n̲
a) The message distribution queue shall be accessed
by terminal positions with message distribution
function allocated as described below.
b) The terminal operator issues a 3 letter TBD sequence
to request a message from the message distribution
queue.
c) The requesting terminal position gets the oldest
of the messages with highest precedence (i.e. prioritized
FIFO queue).
d) When a queue element has been obtained from the
distribution queue it is logically deleted from
the queue so that simultaneous requests will not
get the same message for distribution.
e) Any discontinue of processing for a queue element
(e.g. cancel) returns the element as the oldest
element for the appropriate precedence level.
f) Messages are displayed to the operator of a distribution
position in ACP127 format.
g) The operator shall by means of procedure TBD described
in CPS/230/ICD/0002 be able to
1) Confirm/select precedence of messages
2) Confirm/select security classification of messages
3) Select whether to combine staff cells obtained
automatically with his selection or his selection
only shall apply
4) Specify staff-cells for distribution and select
whether they are ACTION or INFO addresses.
5) Specify distribution to PTP
h) A hard copy of the distribution instruction shall
be printed at the distribution position printer
if desired.
i) The distribution position operator shall be able
to review and modify the distribution instructions
before sending the message for further processing.
j) The distribution position operator shall receive
an acknowledgement that distribution instructions
have been entered.
k) In case distribution instructions are not acceptable
the messages shall be queued again for the message
distribution control function.
3.2.4.3.2 R̲e̲t̲r̲i̲e̲v̲e̲ ̲f̲o̲r̲ ̲d̲i̲s̲t̲r̲i̲b̲u̲t̲i̲o̲n̲
a) The message distribution operator shall by means
of procedure TBD (CPS/230/ICD/0002) be able to
1) retrieve messages for distribution
2) specify staff cells to which a retrieved message
shall be distributed.
b) The processing of the retrieval implicit in retrieve
and distribute is similar to and with the same
restrictions as normal retrievals.
3.2.4.4 R̲e̲p̲o̲r̲t̲s̲
3.2.4.4.l G̲e̲n̲e̲r̲a̲l̲
a) Reports shall be produced by the system to draw
the attention of the supervisory staff to specific
events as specified below.
b) Each report shall as specified be printed out and/or
stored in the outstanding report file.
c) Reports for which printout is specified shall be
queued for printout at report teleprinter.
d) Printout of reports above shall be preceded by
a "BELL".
e) Reports for which storage have been specified are
written to the outstanding report file.
f) Whenever the outstanding report file gets full
oldest entries are deleted to allow for writing
new entries.
g) Printout of all outstanding reports shall be performed
when specified by supervisor.
h) Printout of outstanding reports shall be on either
the report teleprinter or the log teleprinter.
i) Outstanding reports shall be queued for print in
groups of max. 30 reports.
j) Each report shall contain the following information
which shall be printed out on the same print line:
1) report identification, i.e. type and serial
number
2) time of occurrence of the reported event
3) a short description in English, and possible
recommended action to the reported event
4) data applicable to the report.
5) identity of related report which the new report
either supersedes or supplements
3.2.4.4.2 S̲e̲c̲u̲r̲i̲t̲y̲ ̲R̲e̲p̲o̲r̲t̲s̲
Security reports are those reports specified below.
a) Unsuccessful system integrity check.
b) Unsuccessful sign-in attempt (format K1).
c) Unsuccessful security interrogation and whether
it was due to time-out or faulty password.
d) Unsuccessful change of password.
e) Security warning timed out or invalid entry code.
f) Unsuccessful password entry by release officer
during release procedure.
g) Attempt by the equipment to transmit messages of
classification/special handling category not permitted
on channel.
3.2.4.4.3 W̲a̲r̲n̲i̲n̲g̲ ̲R̲e̲p̲o̲r̲t̲s̲
Warning reports are those reports specified below.
a) Table, queue, or file capacity exceeds a preset
threshold which may result in loss of information
for
1) message storage file
2) log
3) outstanding report file
4) channel queues
b) Preemption on external channels, which requires
supervisory action for retransmission of preempted
messages from external channel.
c) Report when 100 characters have been received on
channel after EOM but without VZCZC detected.
d) Halted messages when transmission to CAMPS of a
message is interrupted for more than 5/30 seconds
on highspeed/lowspeed channels.
e) More than 50 identical consecutive characters received
over a channel except for data messages identified
by format line 4.
f) Report that a service message has been sent indicating
50 identical characters.
g) Report that no receipt message has been received
within required time (Flash acknowledge).
h) No channel found available for transmission.
i) Report that mounting of off-line storage media
is required for retrieval.
3.2.4.4.4…02…C̲o̲m̲m̲a̲n̲d̲ ̲C̲o̲m̲p̲l̲e̲t̲i̲o̲n̲ ̲R̲e̲p̲o̲r̲t̲
a) Command completion reports are those reports specified
below.
1) Termination of processing of supervisor command.
3.2.4.4.5…02…T̲r̲a̲f̲f̲i̲c̲ ̲R̲e̲p̲o̲r̲t̲s̲
Traffic reports are those reports specified below.
a) For each incoming channel traffic reports shall
be generated each hour for the last hour:
1) Total number of messages received
2) Average length of messages
3) Per precedence level number of messages received
4) Per security classification category number
of messages received
5) Per special handling category number of messages
received
b) For each incoming channel traffic reports shall
be generated each day for the previous day separately
for the same message categories as for hourly report.
c) The daily report shall cover Oh-23h59.
d) For each incoming channel traffic reports shall
be generated each week for the previous week separately
for the same message categories as for hourly reports.
e) The weekly report shall cover Monday through Sunday.
f) For each outgoing channel and with the same intervals
for the same periods and message categories as
for incoming messages traffic reports shall be
generated.
g) For each incoming channel traffic reports shall
be generated with the same interval for the same
periods specifying number of messages rejected
for message service.
h) A Queue Status Report shall be generated on supervisor
request. The report shall contain the following
information:
- for each internal delivery channel (incl. release
position and supervisor and supervisor assistant
positions): Total queue length of incoming
messages/transactions.
- for each external outgoing channel: Total queue
length for outgoing messages
3.2.4.4.6…02…C̲h̲a̲n̲n̲e̲l̲ ̲R̲e̲p̲o̲r̲t̲s̲
Channel reports are those reports specified below.
a) Discontinuity of incoming message traffic as detected
from the improper serial number sequence.
b) Missing transmission serial number of incoming
traffic from external stations.
c) No service messages received within the period
starting at 23,45 and ending 00,15 hours on channels
as specified by the supervisor.
d) A message has been prematurely terminated. This
report is generated for messages, where the supervisor
is responsible for requesting retransmission.
e) On incoming channels a report when incoming messages
exceed a length of 12000 characters, i.e. before
a valid EOTF sequence is detected.
3.2.4.4.7 D̲e̲l̲e̲t̲i̲o̲n̲ ̲R̲e̲q̲u̲e̲s̲t̲ ̲R̲e̲p̲o̲r̲t̲
Report that a preparation position has made attempt
to delete a message already released.
3.2.4.5…02…E̲n̲g̲i̲n̲e̲e̲r̲i̲n̲g̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲s̲
Engineering functions are hardware and software control
functions.
3.2.4.5.1 E̲n̲g̲i̲n̲e̲e̲r̲i̲n̲g̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲s̲ ̲I̲m̲p̲l̲e̲m̲e̲n̲t̲a̲t̲i̲o̲n̲
a) Engineering functions are executed at 3 levels:
1) Direct hardware control (e.g. switch, patch).
2) System console control.
3) Supervisor engineering command control.
b) The level of executing an engineering function
depends on actual hardware and software.
3.2.4.5.2 E̲n̲g̲i̲n̲e̲e̲r̲i̲n̲g̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲s̲ ̲D̲e̲t̲a̲i̲l̲e̲d̲ ̲D̲e̲f̲i̲n̲i̲t̲i̲o̲n̲
a) The detailed definition of single engineering functions
depends on actual hardware and software, however,
main functions as described below shall be covered
and guidelines be followed.
b) Supervisor engineering command control may only
be used for control of on-line equipment.(Refer
3.2.4.1.1.13).
c) Engineering functions shall exist to switch between
hardware units whenever dualization is used to
obtain required availability.
d) Engineering functions shall exist to control external
lines as required by line interface equipment.
Examples are line speed, code, start/stop bits
control.
e) Engineering function shall exist to conduct online
and offline tests by software or other means as
needed to meet availability requirement.
f) Engineering function shall exist to control load
of software from online and offline media to facilitate
fast restart in failure cases and load of new software
transported to site as required for initialization
and restart (see 3.2.8).
3.2.4.5.3 H̲/̲W̲ ̲C̲o̲n̲f̲i̲g̲u̲r̲a̲t̲i̲o̲n̲ ̲S̲t̲a̲t̲u̲s̲ ̲D̲i̲s̲p̲l̲a̲y̲
As a basis for execution of engineering functions the
following status information shall be displayed at
VDUs and/or display-panels:
- switching status of redundant equipment on crate-level
(refer to 3.2.4.5.2.c)
- status of line interface equipment with regard
to parameters controllable via engineering functions
(refer to 3.2.4.5.2.d)
A full description is given in CPS/ICD/002.
3.2.4.5.4 S̲o̲f̲t̲w̲a̲r̲e̲ ̲D̲e̲v̲e̲l̲o̲p̲m̲e̲n̲t̲
a) One of the sites shall be nominated as software
maintenance centre.
b) Line printer shall exist at the software maintenance
centre.
c) Software package with compilers and other support
software as required shall exist at the software
maintenance centre.
d) Software development is performed on the standby
central processor at the software maintenance centre.
e) When the standby central processor is to be used
for software development at the software maintenance
centre it shall be taken offline (i.e. not available
for CAMPS operations).
f) The central processor performing software development
at the software maintenance centre shall have access
to background storage media for loading compilers,
source code etc.
g) The central processor performing software development
at the software maintenance centre shall have access
to such media for output of system generation that
the generated systems can be transported to other
sites and loaded (e.g. floppy disk).
h) It is acceptable that the media above are loaded/interfaced
on the same drives/via the same units as used for
mounting offline storage for retrieval and as used
for software input at initialization.
