top - download
⟦fb777bdef⟧ Wang Wps File
Length: 79682 (0x13742)
Types: Wang Wps File
Notes: CPS/ICD/010
Names: »1237A «
Derivation
└─⟦65f171b10⟧ Bits:30006062 8" Wang WCS floppy, CR 0094A
└─ ⟦this⟧ »1237A «
WangText
…00……00……00……00……00…;…02……00……00…;
…18……0d……18……07……17……01……16……0b……16……05……15……0f……14……08……14……00……14… …13……0a……13……0f……13… …12……09……12……0e……12…
…12……07……11……0b……11……0c……11……0d……11……00……11… …10……08……10……0a……10……0f……10…
…0f……08……0f……0d……0f……02……0f……07……0e……0d……0e…
…0e… …0e……06……0d……0b……0d……0c……0d……01……0d……02……0d……05……0c……08……0c……86…1 …02… …02… …02…
…02…CPS/ICD/010
…02…850418…02……02…
OPERATOR COMMANDS & PROCEDURES
…02…ISSUE 3.1…02…CAMPS
T̲A̲B̲L̲E̲ ̲O̲F̲ ̲C̲O̲N̲T̲E̲N̲T̲S̲
1. SCOPE ........................................
1 001
1.1 REFERENCE DOCUMENTS ........................
1 001
1.2 DOCUMENT STRUCTURE .........................
1 001
1.3 TERMS & ABBREVIATIONS ......................
1 002
1.3.1 Terms ..................................
1 002
1.3.2 Abbreviations ..........................
1 007
2. VDU CHARACTERISTICS...........................
2 001
2.1 VDU Facilities .............................
2 001
2.2 VDU Screen Layout ..........................
2 001
2.2.1 VDU Splits .............................
2 002
2.2.1.1 Command Split ......................
2 002
2.2.1.1.1 Time ...........................
2 002
2.2.1.1.2 Command Line ...................
2 004
2.2.1.1.3 Response Line ..................
2 004
2.2.1.1.4 Status Line ....................
2 005
2.2.1.2 Configuration Display ..............
2 005
2.2.1.3 Format Split .......................
2 006
2.2.1.3.1 Format Area ....................
2 007
2.2.1.3.2 Margin Area ....................
2 007
2.2.1.3.3 Field Descriptor ...............
2 007
2.2.1.3.4 Field Protection ...............
2 007
2.3 Commands ...................................
2 008
2.3.1 Standard Function Keys .................
2 008
2.3.1.1 Enter ..............................
2 009
2.3.1.2 Next Field (TAB) ...................
2 009
2.3.1.3 Previous Field (BACK-TAB) ..........
2 009
2.3.2 Preprogrammed Function Keys ............
2 009
2.3.2.1 CANCEL (Function Key F8) ...........
2 009
2.3.2.2 Display Error Message (Function
Key F7) ............................
2 009
2.3.3 Specific Commands ......................
2 010
2.3.3.1 Menu Selection .....................
2 010
2.3.3.2 Dialog Format Selection ............
2 010
2.3.3.2.1 Editing ........................
2 011
2.3.3.2.2 Character Overwrite ............
2 011
2.3.3.2.3 Cursor Control .................
2 011
2.3.4 Command Validation .....................
2 011
3. OPERATOR FUNCTIONS ...........................
3 001
3.1 INTRODUCTION ...............................
3 001
3.1.1 Introduction to operator commands at the
SUPV ̲VDU ...............................
3 001
3.1.1.1 Validation .........................
3 002
3.1.1.2 Error Notification .................
3 002
3.1.1.3 Data Entry .........................
3 003
3.1.1.3.1 Fields .........................
3 003
3.1.1.3.2 Data Entry Description .........
3 003
3.1.1.4 Exit Conditions ....................
3 003
3.2 OPERATOR MENUS .............................
3 005
3.2.1 High Level Menu ........................
3 006
3.2.1.1 Command ............................
3 006
3.2.1.2 Presentation .......................
3 006
3.2.1.3 Command Entry ......................
3 006
3.2.1.4 Validation .........................
3 006
3.2.1.5 Exit Condition .....................
3 006
3.3 Processor Unit (PU) System Control .........
3 008
3.3.1 PU-System Menu .........................
3 008
3.3.1.1 Command ............................
3 008
3.3.1.2 Presentation .......................
3 008
3.3.1.3 Command Entry ......................
3 008
3.3.1.4 Validation .........................
3 008
3.3.1.5 Exit Condition .....................
3 008
3.3.2 Delete Specific CIF ....................
3 010
3.3.2.1 Command ............................
3 010
3.3.2.2 Presentation .......................
3 010
3.3.2.3 Data Entry Fields ..................
3 010
3.3.2.3.1 CIF Reference: Field 1 .........
3 010
3.3.2.4 Validation .........................
3 010
3.3.2.5 Exit Condition .....................
3.011
3.3.3 Terminate Operator Only Mode ...........
3 013
3.3.3.1 Command ............................
3 013
3.3.3.2 Presentation .......................
3 013
3.3.3.3 Data Entry Fields ..................
3 013
3.3.3.3.1 Terminate Operator Only
Type: Field 1 ..................
3 013
3.3.3.4 Validation .........................
3 013
3.3.3.5 Exit Condition .....................
3 014
3.3.4 Switchover .............................
3 016
3.3.4.1 Command ............................
3 016
3.3.4.2 Presentation .......................
3 016
3.3.4.3 Data Entry Fields ..................
3 016
3.3.4.3.1 Time Before Switchover:
Field 1 ........................
3 016
3.3.4.4 Validation .........................
3.017
3.3.4.5 Exit Condition .....................
3 018
3.3.5 Close Down .............................
3 020
3.3.5.1 Command ............................
3 020
3.3.5.2 Presentation .......................
3 020
3.3.5.3 Data Entry Fields ..................
3 020
3.3.5.3.1 Close-Down of: Field 1 .........
3 020
3.3.5.3.2 Time: Field 2 ..................
3 021
3.3.5.4 Validation .........................
3 021
3.3.5.5 Exit Condition .....................
3 021
3.4 CHANNEL UNIT (CU) SYSTEM CONTROL ...........
3 024
3.4.1 CU-System Menu .........................
3 024
3.4.1.1 Command ............................
3 024
3.4.1.2 Presentation .......................
3 024
3.4.1.3 Command Entry ......................
3 024
3.4.1.4 Validation .........................
3 024
3.4.1.5 Exit Condition .....................
3 024
3.4.2 LTU Line Control .......................
3 027
3.4.2.1 Command ............................
3 027
3.4.2.2 Presentation .......................
3 027
3.4.2.3 Data Entry Fields ..................
3 027
3.4.2.3.1 Type: Field 1 ..................
3 027
3.4.2.3.2 Speed: Field 2 .................
3 027
3.4.2.3.3 Status: Field 3 ................
3 028
3.4.2.4 Validation .........................
3 028
3.4.2.5 Exit Condition .....................
3 029
3.4.3 LTU Control ............................
3 031
3.4.3.1 Command ............................
3 031
3.4.3.2 Presentation .......................
3 031
3.4.3.3 Data Entry Fields ..................
3 031
3.4.3.3.1 Type: Field 1 ..................
3 032
3.4.3.3.2 Status: Field 2 ................
3 032
3.4.3.4 Validation .........................
3 032
3.4.3.5 Exit Condition .....................
3 033
3.4.4 Disk Drive Assignment ..................
3 035
3.4.4.1 Command ...........................
3 035
3.4.4.2 Presentation ......................
3 035
3.4.4.3 Data Entry Fields .................
3 035
3.4.4.3.1 Type: Field 1 ................
3 035
3.4.4.3.2 Status: Field 2 ..............
3 035
3.4.4.4 Validation .........................
3 036
3.4.4.5 Exit Condition .....................
3 036
3.4.5 Volume Handling ........................
3 038
3.4.5.1 Command ............................
3 038
3.4.5.2 Presentation .......................
3 038
3.4.5.3 Data Entry Fields ..................
3 038
3.4.5.3.1 Volume Name: Field 1 ...........
3 038
3.4.5.3.2 Action: Field 2 ...............
3 039
3.4.5.4 Validation .........................
3 039
3.4.5.5 Exit Condition .....................
3 039
3.5 TDX-System Control .........................
3 042
3.5.1 TDX-System Menu ........................
3 042
3.5.1.1 Command ............................
3 042
3.5.1.2 Presentation .......................
3 042
3.5.1.3 Command Entry ......................
3 042
3.5.1.4 Validation .........................
3 042
3.5.1.5 Exit Condition .....................
3 042
3.5.2 LTUX Line Control ......................
3 045
3.5.2.1 Command ............................
3 045
3.5.2.2 Presentation .......................
3 045
3.5.2.3 Data Entry Fields ..................
3 045
3.5.2.3.1 Type: Field 1 ..................
3 045
3.5.2.3.2 Alphabet: Field 2 ..............
3 046
3.5.2.3.3 Speed: Field 3 .................
3 046
3.5.2.3.4 Status: Field 4 ................
3 046
3.5.2.4 Validation .........................
3 046
3.5.2.5 Exit Condition .....................
3 048
3.5.3 LTUX Control ...........................
3 050
3.5.3.1 Command ............................
3 050
3.5.3.2 Presentation .......................
3 050
3.5.3.3 Data Entry Fields ..................
3 050
3.5.3.3.1 Type : Field 1 .................
3 050
3.5.3.3.2 Status Field 2 .................
3 051
3.5.3.4 Validation .........................
3 051
3.5.3.5 Exit Condition .....................
3 052
3.5.4 BSM-X Control ..........................
3 054
3.5.4.1 Command ............................
3 054
3.5.4.2 Presentation .......................
3 054
3.5.4.3 Data Entry Field ...................
3 054
3.5.4.3.1 Status : Field 1 ...............
3 054
3.5.4.4 Validation .........................
3 055
3.5.4.5 Exit Condition .....................
3 055
3.6 SOFTWARE CONTROL COMMANDS ..................
3 057
3.6.1 Menu for SOFT Commands .................
3 057
3.6.1.1 Command ............................
3 057
3.6.1.2 Presentation .......................
3 057
3.6.1.3 Command Entry ......................
3 057
3.6.1.4 Validation .........................
3 057
3.6.1.5 Exit Condition .....................
3 058
3.6.2 Adjust Time ............................
3 060
3.6.2.1 Command ............................
3 060
3.6.2.2 Presentation .......................
3 060
3.6.2.3 Data Entry Fields ..................
3 060
3.6.2.3.1 Time to be Adjusted: Field 1 ...
3 060
3.6.2.3.2 Number of Seconds: Field 2 .....
3 060
3.6.2.4 Validation .........................
3 061
3.6.2.5 Exit Condition .....................
3 061
3.6.3 Load Modified Software .................
3 063
3.6.3.1 Command ............................
3 063
3.6.3.2 Presentation .......................
3 063
3.6.3.3 Data Entry Field ...................
3 063
3.6.3.3.1 Copy Mode: Field 1 .............
3 063
3.6.3.3.2 Type of Software: Field 2 ......
3 064
3.6.3.3.3 Patchfiles: Field 3 ...........
3 064
3.6.3.4 Validation .........................
3 064
3.6.3.5 Exit Condition .....................
3 065
3.6.4 Set Trace Mask .........................
3 067
3.6.4.1 Command ............................
3 067
3.6.4.2 Presentation .......................
3 067
3.6.4.3 Data Entry Fields ..................
3 067
3.6.4.3.1 Define Process: Field 1 .......
3 067
3.6.4.3.2 Priority: Field 2 .............
3 067
3.6.4.4 Validation .........................
3 068
3.6.4.5 Exit Condition .....................
3 069
3.6.5 Print System Configuration .............
3 071
3.6.5.1 Command ............................
3 071
3.6.5.2 Presentation .......................
3 071
3.6.5.3 Data Entry Field ...................
3 071
3.6.5.3.1 Type: Field ....................
3 071
3.6.5.3.2 Print from/to: Field 2/3 .......
3 071
3.6.5.4 Validation .........................
3 072
3.6.5.5 Output .............................
3 072
3.6.5.6 Exit Condition .....................
3 072
3.6.6 Print Software Version .................
3 075
3.6.6.1 Command ............................
3 075
3.6.6.2 Presentation .......................
3 075
3.6.6.3 Data Entry Fields ..................
3 075
3.6.6.3.1 Specify Disk: Field 1 ..........
3 075
3.6.6.4 Validation .........................
3 075
3.6.6.5 Output .............................
3 076
3.6.6.6 Exit Condition .....................
3 076
3.6.7 Print Process Time .....................
3 079
3.6.7.1 Command ............................
3 079
3.6.7.2 Presentation .......................
3 079
3.6.7.3 Output .............................
3 079
3.6.7.4 Exit Condition .....................
3 079
3.7 WDP OPERATOR COMMANDS ......................
3 081
3.7.1 PU Aimed WD Commands ...................
3 081
3.7.2 Direct Watchdog Commands ...............
3 081
3.7.2.1 Menu for Direct Watchdog commands ..
3 083
3.7.2.1.1 Presentation ...................
3 083
3.7.2.1.2 Command Entry ..................
3 083
3.7.2.1.3 Validation .....................
3 083
3.7.2.1.4 Exit Condition .................
3 083
3.7.2.2 Communication to PU ................
3 085
3.7.2.2.1 Command ........................
3 085
3.7.2.2.2 Effect .........................
3 085
3.7.2.2.3 Validation .....................
3 085
3.7.2.2.4 Exit Condition .................
3 085
3.7.2.3 Communication to whom? .............
3 086
3.7.2.3.1 Command ........................
3 086
3.7.2.3.2 Effect .........................
3 086
3.7.2.3.3 Validation .....................
3 086
3.7.2.3.4 Exit Condition .................
3 086
3.7.2.4 Reset PU .......................... 3
087
3.7.2.4.1 Command ....................... 3
087
3.7.2.4.2 Effect ........................ 3
087
3.7.2.4.3 Validation .................... 3
087
3.7.2.4.4 Exit Condition ................ 3
087
3.7.2.5 Enable PU ......................... 3
088
3.7.2.5.1 Command ....................... 3
088
3.7.2.5.2 Effect ........................ 3
088
3.7.2.5.3 Validation .................... 3
088
3.7.2.5.4 Exit Condition ................ 3
088
3.7.2.6 Disable PU ........................ 3
090
3.7.2.6.1 Command ....................... 3
090
3.7.2.6.2 Effect ........................ 3
090
3.7.2.6.3 Validation .................... 3
090
3.7.2.6.4 Exit Condition ................ 3
090
3.7.2.7 Enable Take-Ownership ............. 3
091
3.7.2.7.1 Command ....................... 3
091
3.7.2.7.2 Effect ........................ 3
091
3.7.2.7.3 Validation .................... 3
091
3.7.2.7.4 Exit Condition ................ 3
091
3.7.2.8 Disable Take-ownership ............ 3
092
3.7.2.8.1 Command ....................... 3
092
3.7.2.8.2 Effect ........................ 3
092
3.7.2.8.3 Validation .................... 3
092
3.7.2.8.4 Exit Condition ................ 3
092
3.7.2.9 Master Clear PU ................... 3
093
3.7.2.9.1 Command ....................... 3
093
3.7.2.9.2 Effect ........................ 3
093
3.7.2.9.4 Exit Condition ................ 3
093
3.7.2.10 Maintenance Mode ................ 3
094
3.7.2.10.1 Command ..................... 3
094
3.7.2.10.2 Effect ...................... 3
094
3.7.2.10.3 Validation .................. 3
094
3.7.2.10.4 Exit Condition .............. 3
094
3.7.2.11 Normal Mode ..................... 3
095
3.7.2.11.1 Command ..................... 3
095
3.7.2.11.2 Effect ...................... 3
095
3.7.2.11.3 Validation .................. 3
095
3.7.2.11.4 Exit Condition .............. 3
095
3.7.2.12 Direct Switchover ............... 3
096
3.7.2.12.1 Command ..................... 3
096
3.7.2.12.2 Effect ...................... 3
096
3 7 2.12.3 Validation .................. 3
096
3.7.2.12.4 Exit Condition .............. 3
097
3.7.2.13 Attention (break) to PU ......... 3
098
3.7.2.13.1 Command ..................... 3
098
3.7.2.13.2 Effect ...................... 3
098
3.7.2.13.3 Validation .................. 3
098
3.7.2.13.4 Exit Condition .............. 3
098
3.8 BOOT SEQUENCE ............................... 3
099
3.9 START UP .................................... 3
100
3.9.1 Command ............................... 3
100
3.9.2 Presentation .......................... 3
100
3.9.3 Data Entry Fields ..................... 3
100
3.9.3.1 Start up Type ..................... 3
100
3.9.3.2 Software Type ..................... 3
100
3.9.3.3 CAMPS Mode ........................ 3
101
3.9.3.4 Operator Only Mode ................ 3
101
3.9.3.5 Supervisor Only Mode .............. 3
101
3.9.3.6 TRACE Directory ................... 3
101
3.9.4 Validation ............................ 3
102
3.9.5 Exit Condition ........................ 3
102
APPENDIX A
Commands from ENGI-position supervisor
and WDP position ................................
1
APPENDIX B
1 MESSAGES TO THE OPERATOR ROP ..................
2
1.1 LOG OF COMMAND ............................
3
1.2 ERROR REPORTS .............................
3
1.3 SYSTEM STATUS INFORMATION .................
3
2 WATCHDOG RESPONSES UPON WD VDU ................
22
2.1 COMMAND RESPONSE ..........................
22
2.2 ERROR RESPONSE ............................
24
APPENDIX C
1 OFFLINE PU ....................................
23
APPENDIX D
1 CMI OUTPUT ....................................
26
1.1 CMI LOG ...................................
26
1.2 CMI FORMAT AND COMMAND LINE REPLIES .......
26
1.3 CMI COMMAND OUTPUT ........................
29
APPENDIX E
1 PORT NO overview ..............................
31
APPENDIX F
1 REPORT FORMAT .................................
34
2 FIELD CONTENTS ................................
37
3 HEXADECIMAL DUMPS .............................
41
APPENDIX G
1 COPSY SW REPORTS ..............................
50
2 RETIRE REPORTS ................................
52
3 GARBLE REPORTS ................................
61
4 START UP PHASE ERROR MESSAGES .................
68
APPENDIX H
COPSY CONTROLLED SHUTDOWN .......................
72
APPENDIX I
ROOT ERROR MESSAGES .............................
77
1̲ ̲ ̲S̲C̲O̲P̲E̲
This document describes the formats and transactions
which are applicable to the CAMPS operator commands.
The document is an extension of the design of SS&C
and is considered a system design document, like CPS/SDS/004
System Status and Control and like CPS/ICD/009 Software
Interface Control Document. The document is not considered
a contractual requirement document, but has been kept
in the same format as the user and supervisor ICD for
ease of reference and manual preparation.
1.1 R̲E̲F̲E̲R̲E̲N̲C̲E̲ ̲D̲O̲C̲U̲M̲E̲N̲T̲S̲
CAMPS System Requirements:
CPS/230/SYS/0001.
Reference manual for 7260 T Video Display Terminal,
P/N 917M/400A020.
1.2 D̲O̲C̲U̲M̲E̲N̲T̲ ̲S̲T̲R̲U̲C̲T̲U̲R̲E̲
1) The description of the Operator Procedures is in
terms of TRANSACTIONS.
A transaction consists of a dialogue which an operator
performs to execute an operator command. The transaction
identifies FORMATS and describes the diaglogues
associated with those formats. The overall sequence
of formats is shown in a diagram and the VDU layouts
of the formats are given on a special form.
2) The fields within these formats are identified
and defined in terms of their elements, the possible
values of the elements, and the semantic checks
performed.
3) The System Response Messages, returned as a result
of validation, are also listed.
1.3 T̲E̲R̲M̲S̲ ̲A̲N̲D̲ ̲A̲B̲B̲R̲E̲V̲I̲A̲T̲I̲O̲N̲S̲
1.3.1 T̲e̲r̲m̲s̲
Channel designator Identification of an external
channel
Circuit CAMPS to node connection
for the appropriate Network.
A circuit may consist of
one or more channels.
Close-down Action taken to bring
(Ordered/Emergency) processing within the system
or a part thereof to a stop
- can be either an ordered
sequence of steps or an
abrupt termination.
Cold start-up Initialization from the
on-line disks.
Connection (DAMOS) A connection is a logical
TMS term) channel to a "terminal"
on a channel. A terminal
can be:
- an EXC
- a VDU or VDU split
- an SAD
- a PU
Dead Start-up Initialization from the
off-line disk.
Designator A designator is a logical
representation of a line.
The designator to line
connection is subject to
change during a reconfiguration.
Device Designator Identification of a stand-alon
device.
Device Profile To each device, a device
profile is associated.
External Channel A channel in a telegraph
circuit or non telegraph
circuit.
Initial Start up System Start up based on
initial data.
Initialization The definition in the CPS/SDS/001
and subsequent documents
are described as follows:
Brings the system from
dead start into operational
use. No recovery actions
are included.
The definitions replace
the one used in the CPS/210/SYS/0001:
Brings the system from
cold start into operational
use.
Line A line refers to a physical
V24 wire from an LTU or
LTUX.
Logical Line The software aggregate representing
a physical connection to
an external device, network,
or system.
Logical connected/ Only the supervisor can
disconnected connect/disconnect an LTUX-line
or LTU-line logical.
Low Speed Media Low speed teleprinter (PTP,
PTR, ROP), Point-to-Point
connection and TRC.
Monitoring and Control Monitoring refers to a status
inspection, whereas control
refers to a execution.
Supervision includes monitoring
and control.
Non Telegraph Circuit CCIS and SCARS.
Off-Line Disk The part of disk storage
residing on removable packs.
On-Line Disk The part of disk storage
which is permanently mounted.
Operating System A process making high level
decisions about dynamic
allocation of resources
to a set of descendant processes.
Operator a) Person with responsibility
for operating the central
equipment from the
maintenance position
and/or control panels
(i.e. the technicians
and RST).
b) Person with responsibility
for maintenance and repair.
The term operator is identical
with Engineering in CPS/210/SYS/0001
and replaces it in the CPS/SDS/001
and subsequent documents.
Port A port refers to a line,
a BSM-X, an LTUX, an LTU,
a disk, a TDX bus, an IOBUS,
or a PU.
For lines, a port may be
visualized as a physical
wire relating to a specific
slot again relating to a
specific crate. Refer Appendix
E for a definition of actual
port numbers.
Process Execution of a specific
program operating on a specific
set of data. The active
components of the system
to which security and process
control as well as resource
management is applied.
Restart Refers to a cold or warm
start-up from the on-line
disks.
Recovery Reestablishes continuity
in memory and file contents
Staff cell designator The SCD is the smallest
addressable unit in one
CAMPS site.
Stand alone device Medium speed teleprinter,
low speed teleprinter (PTP,
PTR, ROP) OCR, PTR, and
PTP.
Start up Includes all aspects of
initialization, recovery
and restart
Supervisor Person located at supervisor
terminals in CAMPS central
equipment room
Supervisor's Assistant Person with responsibility
for special Message Service.
In the CPS/210/SYS/0001
supervisor means both supervisor
and supervisor assistant.
Supervisor Function Denotes the total group
of commands/procedures which
may be performed from a
VDU with supervisor capability.
Switchover Relates to a dualized configuration
containing an active and
a stand-by part. Switchover
is the actions of bringing
the stand-by device into
active state and the other
active device off-line.
System Control Data Tables, system parameters
etc. used to implement and
control the operation of
CAMPS.
System Parameter A simple variable, holding
part of the system state,
and controlled by TMP.
Telegraph circuit NICS TARE, Point to point
and TRC.
Terminal VDU, Medium Speed Teleprinter,
Low Speed Teleprinter, Line
Printer, PTP/PTR and OCR.
Terminal Device VDU, Medium Speed Teleprinter
and Low Speed Teleprinter.
Terminal Designator A code identifying the terminal
position.
Terminal Position VDU and associated (shared)
ROP.
Terminal Profile The terminal profile contains
information about an VDU
and identifies a shared
ROP.
Time of Day A 14 alpha-numeric field
which contains DAY, HOUR,
MINUTE, ZONE, MONTH, and
YEAR.
User a) Person with
responsibility for
input and output of
messages.
b) Person located at the
user
terminals in the staff
cells.
The user is identical with
the term operator in the
CPS/210/SYS/0001 and replaces
it in CPS/SDS/001
Volume A named entity which can
either be a complete disk
pack or a specifically addressable
part of a disk pack.
Warm start-up Start-up from the online
disks. It includes recovery/restart
actions. Switchover is
a type of warm start-up.
1.3.2 A̲b̲b̲r̲e̲v̲i̲a̲t̲i̲o̲n̲s̲
AC Active
CCB Configuration Control Bus
CMD Command Dispatcher
CMI Command Interface
COPSY CAMPS Operating System
CRT CAMPS Remote Terminal
EXC External Channel
FCT Function
FW Firmware
HW Hardware
LTP Low Speed Teleprinter
M&C Monitoring and Control
MTP Medium Speed Teleprinter
OCR Optical Character Reader
OLD On-line diagnostics
PTOP Point to Point
PTP Paper Tape Punch
PU Processor Unit
ROP Receive Only Printer
SAD Stand Alone Device
SB Stand By
SSC System Status and Control
SUPV ̲DVU The VDU at the Supervisor position(s)
SW Software
TRC Tape Relay Center
VDU Visual Display Unit
WDP Watchdog Processor
WDP ̲VDU The VDU at the WDP posotion
2̲ ̲ ̲V̲D̲U̲ ̲C̲H̲A̲R̲A̲C̲T̲E̲R̲I̲S̲T̲I̲C̲S̲
2.1 V̲D̲U̲ ̲F̲a̲c̲i̲l̲i̲t̲i̲e̲s̲
The full set of features of the CAMPS VDU is described
in the System Requirements Specification section 3.4.1.10.1.
The basic VDU characteristics assumed for this specification
are as specified below. The characteristics do not
imply additional requirements to CPS/210/SYS/0001.
- 1 VDU status line.
- Min. 27 useable lines of 80 characters each.
- 12 programmable function keys.
- Split screen capability as defined in section 2.2.
- Protected and unprotected fields.
- Unprotected fields having the following attributes:
mandatory, optional, alpha, numberic, alphanumeric,
length.
- VDU attributes - inverse video, dual intensity,
bell, paging, scrolling over VDU memory contents.
- Delete/insert character.
- Lockable.
2.2 V̲D̲U̲ ̲S̲c̲r̲e̲e̲n̲ ̲L̲a̲y̲o̲u̲t̲
Fig. 2.2.1-1
Fig. 2.2.1-2
2.2.1 V̲D̲U̲ ̲S̲p̲l̲i̲t̲s̲
The VDU contains three splits:
- the command split
- the configuration display split
- the format split
as illustrated in fig. 2.2.1-1.
In fig. 2.2.2-2 the command and configuration display
splits are detailed.
2.2.1.1 C̲o̲m̲m̲a̲n̲d̲ ̲S̲p̲l̲i̲t̲
The command split contains the following:
- the time of day
- the command line
- the response line
- status line.
2.2.1.1.1 T̲i̲m̲e̲
This is the Time in DATE TIME GROUP format. It is a
14 alpha-numeric field containing the Day, Hour, Minute,
Zone, Month, Year.
This is updated every minute.
2.2.1.1.2 C̲o̲m̲m̲a̲n̲d̲ ̲L̲i̲n̲e̲
The command line contains two unprotected fields:
- command field
- identify field.
The operator uses the commandfield to specify a command
(ref. Appendix A). Some commands, i.e. boot commands
and peripheral reconfiguration commands, need a further
set of parameters, which are to be set in the identify
field (ID).
The commands are entered by depressing the ENTER key.
The cursor is moved to the first position of the command
field after completion of a transaction, or if the
operator depresses either the CANCEL or DISPLAY ERROR
key instead.
2.2.1.1.3 R̲e̲s̲p̲o̲n̲s̲e̲ ̲L̲i̲n̲e̲
The response line is used to inform the operator if
he has entered invalid parameters.
The response is given unsolicited in a case of an invalid
command or ID. If a parameter in the format is not
accepted, the operator can request an explanation of
the error-number and it will be given in the response
line.
2.2.1.1.4 S̲t̲a̲t̲u̲s̲ ̲L̲i̲n̲e̲
The VDU uses the top line of the display screen to
display the status indicators for the various modes
and conditions, that may exist in the terminal (ref.
P/N 917M400A020). Furthermore, the operator is notified
in this line if an empty mandatory field is sent.
2.2.1.2 C̲o̲n̲f̲i̲g̲u̲r̲a̲t̲i̲o̲n̲ ̲D̲i̲s̲p̲l̲a̲y̲
The configuration display provides:
- status information (marked in black boxes)
- no. of devices which are configurationally enabled
for various HW items.
The PU status can be:
- ACTIVE
- STANDBY
- OFFLINE
- ERROR.
The WDP-ROP status can be:
- ON
- OFF.
The DISK status can be:
- MOUNTED
- IN-SERVICE
- OUT-OF-SERVICE
- DSK ̲ERROR (disk controller or drive)
- VOL ̲ERROR (volume)
The TDX bus status can be:
- ACTIVE
- IN-SERVICE
- OUT-OF-SERVICE
- ERROR
Also the configuration display defines the last error
report printed out.
2.2.1.3 F̲o̲r̲m̲a̲t̲ ̲S̲p̲l̲i̲t̲
The format split is used during execution of operator
commands to an on-line PU, to display formats.
2.2.1.3.1 F̲o̲r̲m̲a̲t̲ ̲A̲r̲e̲a̲
The symbols used in the VDU Layout forms are shown
in fig. 2.2.1.3.1-1.
2.2.1.3.2 M̲a̲r̲g̲i̲n̲ ̲A̲r̲e̲a̲
The ten character margins are used by the system to
indicate the following:
1 2 3 4 5 6 7 8 9 10
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲
SPACE ERROR CODE SPACE
The user area consists of the remaining 70 characters.
2.2.1.3.3 F̲i̲e̲l̲d̲ ̲D̲e̲s̲c̲r̲i̲p̲t̲o̲r̲
Each data entry field has a descriptor, specifying
whether the user should input alpha, numeric or alphanumeric
data, and whether the entry is optional or mandatory.
This descriptor is visible to the user in the form
of a symbol preceding each field, as a reminder of
the type of data required.
2.2.1.3.4 F̲i̲e̲l̲d̲ ̲P̲r̲o̲t̲e̲c̲t̲i̲o̲n̲
Unprotected data-entry fields are the only part of
the screen where characters can be written.
If the user does not enter a mandatory field or enters
an incorrect type of character, he will be warned.
F̲i̲e̲l̲d̲ ̲D̲e̲s̲c̲r̲i̲p̲t̲o̲r̲
̲ ̲
̲ ̲ = inverse video field
̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ = unprotecte data-entry field
N = Mandatory numeric
n = Optional numeric
A = Mandatory alpha
a = Optional alpha
D = Mandatory alphanumeric
d = Optional alphanumeric
Fig. 2.2.1.3.1-1
S̲Y̲M̲B̲O̲L̲S̲ ̲U̲S̲E̲D̲ ̲O̲N̲ ̲V̲D̲U̲ ̲L̲A̲Y̲O̲U̲T̲ ̲F̲O̲R̲M̲S̲
2.3 C̲o̲m̲m̲a̲n̲d̲s̲
The commands are divided into three categories:
- those entered by standard function keys
- those entered by preprogrammed function keys
- those entered by four letter mnemonics.
2.3.1 S̲t̲a̲n̲d̲a̲r̲d̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲ ̲K̲e̲y̲s̲
Ref. P/N 917M/400A20 7260T video display terminal.
2.3.1.1 E̲n̲t̲e̲r̲
This causes the contents of the Command Line or the
unprotected fields of the split to be transmitted to
the system.
2.3.1.2 N̲e̲x̲t̲ ̲F̲i̲e̲l̲d̲ ̲(̲T̲A̲B̲)̲
This command causes the cursor to jump to the next
field.
2.3.1.3 P̲r̲e̲v̲i̲o̲u̲s̲ ̲F̲i̲e̲l̲d̲ ̲(̲B̲A̲C̲K̲-̲T̲A̲B̲)̲
This command causes the cursor to return to the beginning
of the previous field.
2.3.2 P̲r̲e̲-̲p̲r̲o̲g̲r̲a̲m̲m̲e̲d̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲ ̲K̲e̲y̲s̲
2.3.2.1 C̲a̲n̲c̲e̲l̲(̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲ ̲K̲e̲y̲ ̲F̲8̲)̲
The depressing of the CANCEL key instead of the ENTER
key causes the format display, the command line and
the response line to be cleared. The cursor is positioned
in the first position of the command line.
The key is to be used, if the operator has requested
a format, which he does not want to update. In off-line
communication mode, the CANCEL key causes the VDU to
return to on-line communication mode.
2.3.2.2 D̲i̲s̲p̲l̲a̲y̲ ̲E̲r̲r̲o̲r̲ ̲M̲e̲s̲s̲a̲g̲e̲ ̲(̲F̲u̲n̲c̲t̲i̲o̲n̲ ̲K̲e̲y̲ ̲F̲7̲)̲
This function key is used to return from the format
display to the command line, if the operator wants
an explanation of an error-number.
The operator is only allowed to request the explanation
by the error code in the command line; all other commands
are refused.
The explanation of an error code is given in the response
line and the cursor is returned to the format display.
2.3.3 S̲p̲e̲c̲i̲f̲i̲c̲ ̲C̲o̲m̲m̲a̲n̲d̲s̲
The commands which are specific to a format are described
with that format (see also appendix A). The commands
are always in the form of four letter mnemonic.
2.3.3.1 M̲e̲n̲u̲ ̲S̲e̲l̲e̲c̲t̲i̲o̲n̲
The operator selects an item from a menu by inputting
a command. The cursor will be pre-positioned on the
command line awaiting his input. The menu will provide
an "aide-memoire" for the command relevant to the options
presented.
The operator is not limited to the commands shown on
the menu; any valid command for the selected CAMPS
function may be input.
2.3.3.2 D̲i̲a̲l̲o̲g̲ ̲F̲o̲r̲m̲a̲t̲ ̲S̲e̲l̲e̲c̲t̲i̲o̲n̲
The operator selects a Dialog format from one of the
sub-menus and the cursor is positioned in the first
unprotected field.
The Dialog Format is used during execution of operator
commands to an on-line PU (e.g. insert or remove a
VDU line).
2.3.3.2.1 E̲d̲i̲t̲i̲n̲g̲
Editing is allowed on the contents of unprotected fields.
The changed fields will only be available to the system
on depressing the ENTER key.
2.3.3.2.2 C̲h̲a̲r̲a̲c̲t̲e̲r̲ ̲O̲v̲e̲r̲w̲r̲i̲t̲e̲
The character to be overwritten is defined by the cursor
position. The next character typed in will overwrite
the previous one.
2.3.3.2.3 C̲u̲r̲s̲o̲r̲ ̲C̲o̲n̲t̲r̲o̲l̲
A cursor is available to help the user entering data
on the VDU in the unprotected fields. The cursor can
be moved to any position of the screen by the use of
the up, down, left and right keys.
The initial position of the cursor will be on the first
character of the first unprotected fields in the format
area.
2.3.4 C̲o̲m̲m̲a̲n̲d̲ ̲V̲a̲l̲i̲d̲a̲t̲i̲o̲n̲
Unrecognisable commands, commands not valid under the
present circumstances, and commands with missing or
invalid parameters will result in an error-message
displayed in the response line (ref. Appendix D).
The legal commands are listed in Appendix A.
3̲ ̲ ̲O̲P̲E̲R̲A̲T̲O̲R̲ ̲F̲U̲N̲C̲T̲I̲O̲N̲S̲
3.1 I̲N̲T̲R̲O̲D̲U̲C̲T̲I̲O̲N̲
The operator functions are executed from two VDU positions
- the VDU at the supervisor position (SUPV ̲VDU)
- the VDU at the watchdog position (WDP ̲VDU)
The operator commands available at the SUPV ̲VDU position
are obtained, when the supervisor has signed on as
ENGI, and are described in the sections 3.1.1 to 3.6.
The operator commands at the WDP ̲VDU are divided into
2 parts
- operator boot and start-up commands, which are
handled in section 3.8 and 3.9 respectively
- direct commands to the watchdog, which are handled
in section 3.7.
The operator commands at the WDP ̲VDU are executed on
a VDU in TTY mode.
3.1.1 I̲n̲t̲r̲o̲d̲u̲c̲t̲i̲o̲n̲ ̲t̲o̲ ̲o̲p̲e̲r̲a̲t̲o̲r̲ ̲c̲o̲m̲m̲a̲n̲d̲s̲ ̲a̲t̲ ̲t̲h̲e̲ ̲S̲U̲P̲V̲ ̲V̲D̲U̲
The operator transaction is described using a dialog
description and a set of VDU layout forms. The validation
checks on the operator entered data and the subsequent
error correction loops are also described.
Fig. 3.1-1 gives an overview of the on-line operator
commands available from one of the supervisor positions,
when signed on as ENGI.
3.1.1.1 V̲a̲l̲i̲d̲a̲t̲i̲o̲n̲
Full semantic validation (as specified in each Format)
takes place only after the data-entry is completed.
During actual data-entry, validation will be restricted
to simple syntax-checking against alpha/alphanumeric
and mandatory/optional field descriptions. This allows
the operator to prepare an input very rapidly and yet
with full confidence that it will be thoroughly validated
later, before being issued to the system.
3.1.2 E̲r̲r̲o̲r̲ ̲N̲o̲t̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
a) During the syntax validation associated with data-entry,
error notification will be by the terminal "bell".
This needs no further explanation, since the validation
will be limited to checking mandatory/optional
and alpha/numeric/alphanumeric fields, and therefore
the error should be self-evident.
b) If a mandator field is a part of the transmission
to the system and that field is blank, the message
"ENTRY REQUIRED" is displayed on the status line,
and the transmission is aborted.
c) If an error is detected during semantic validation
by the system, the format is re-presented at the
operator's VDU, with one error number (denoting
the first error in the line) in the left-hand margin.
The error numbers are listed in Appendix D. If
the operator wants an explanation of the error
number,, he can issue the command (ref. 2.3.2.2)
which results in an explicit error message being
displayed on the "Response" line.
3.1.1.3 D̲a̲t̲a̲ ̲E̲n̲t̲r̲y̲
3.1.1.3.1 F̲i̲e̲l̲d̲s̲
The fields are fixed length parts of the VDU screen
with a maximum of one line.
The unprotected fields are reserved for the operator.
The protected fields are reserved for the system.
3.1.1.3.2 D̲a̲t̲a̲ ̲E̲n̲t̲r̲y̲ ̲D̲e̲s̲c̲r̲i̲p̲t̲i̲o̲n̲
The data is entered at the cursor position within the
unprotected fields. These are indicated to the operator
by underlining. When a field is completed, the beginning
of the next field can be accessed by using the "next
field key".
Similarly, the beginning of the previous field is accessed
by the previous field key.
If the user skips a mandatory field, he will be warned.
Ref. 3.1.2.b.
3.1.1.4 E̲x̲i̲t̲ ̲C̲o̲n̲d̲i̲t̲i̲o̲n̲s̲
The operator can regret his choice of format or the
updating of a format by depressing the CANCEL key.
This will cause the display of the current menu, the
command line and the response line will be cleared.
If the operator has entered a format by depressing
the ENTER key, the transaction cannot be cancelled.
At the end of a transaction, the current menu is displayed,
the command line and the response line are cleared.
A log of the transaction including the time of day
(DTG) is printed on the operator lineprinter. The logs
are listed in Appendix D.
Fig. 3.1-1
OVERVIEW OF ONLINE OPERATOR COMMANDS
FROM THE ENGI POSITION (SUPV ̲VDU)
3.2 E̲N̲G̲I̲ ̲M̲E̲N̲U̲S̲
When the engineer signs on as E̲N̲G̲I̲ on one of the two
supervisor positions, the High Level Menu shown in
figure 3.2.1-1 is displayed together with the configuration
display.
3.2.1 H̲i̲g̲h̲ ̲L̲e̲v̲e̲l̲ ̲M̲e̲n̲u̲
Format HIME.
3.2.1.1 C̲o̲m̲m̲a̲n̲d̲
The High Level Menu is obtained by the command:
- HIME or
- due to sign on as engi
3.2.1.2 P̲r̲e̲s̲e̲n̲t̲a̲t̲i̲o̲n̲
The Menu format lists the available sub-menus, plus
the commands required to obtain the menus - see fig.
3.2.1-1.
3.2.1.3 C̲o̲m̲m̲a̲n̲d̲ ̲E̲n̲t̲r̲y̲
The cursor is positioned on the command line, awaiting
input of a command.
The command specified by the operator is executed when
the ENTER key is depressed.
3.2.1.4 V̲a̲l̲i̲d̲a̲t̲i̲o̲n̲
The operator command is validated in accordance with
section 2.3.4.
3.2.1.5 E̲x̲i̲t̲ ̲C̲o̲n̲d̲i̲t̲i̲o̲n̲
If the command is accepted, the High Level Menu is
displayed and the cursor is returned to the first position
of the command field on command line. The operator
may now enter a new command.
If the CANCEL key is depressed, the command line and
the response line are cleared and the cursor is positioned
on the first position of the command field.
Fig. 3.2.1-1
3.3 P̲r̲o̲c̲e̲s̲s̲o̲r̲ ̲U̲n̲i̲t̲ ̲(̲P̲U̲)̲ ̲S̲y̲s̲t̲e̲m̲ ̲C̲o̲n̲t̲r̲o̲l̲
3.3.1 P̲U̲-̲S̲y̲s̲t̲e̲m̲ ̲M̲e̲n̲u̲
Format PUSY.
3.3.1.1 C̲o̲m̲m̲a̲n̲d̲
The PU System Menue is obtained by the command:
- PUSY.
3.3.1.2 P̲r̲e̲s̲e̲n̲t̲a̲t̲i̲o̲n̲
The Menu lists the available options, plus the commands
required to obtain the options. See fig. 3.3.1-1.
3.3.1.3 C̲o̲m̲m̲a̲n̲d̲ ̲E̲n̲t̲r̲y̲
The cursor is positioned on the Command Line, awaiting
input of a command.
The command specified by the operator is executed,
when the ENTER key is depressed.
3.3.1.4 V̲a̲l̲i̲d̲a̲t̲i̲o̲n̲
The operator command is validated in accordance with
section 2.3.4.
3.3.1.5 E̲x̲i̲t̲ ̲C̲o̲n̲d̲i̲t̲i̲o̲n̲s̲
If the command is accepted, the PU-System Menu is displayed
and the cursor is returned to the first position of
the command field on the command line. The operator
may now enter a new command.
If the CANCEL key is depressed, the command line and
the response line are cleared and the cursor is positioned
on the first position of the command field.
Fig. 3.5.1-1
3.3.2 D̲e̲l̲e̲t̲e̲ ̲S̲p̲e̲c̲i̲f̲i̲c̲ ̲C̲I̲F̲
Format DCIF.
3.3.2.1 C̲o̲m̲m̲a̲n̲d̲
The delete specific CIF format is obtained by the command:
- DCIF in the command field
3.3.2.2 P̲r̲e̲s̲e̲n̲t̲a̲t̲i̲o̲n̲
The format to be used is shown in Figure 3.3.2-1.
3.3.2.3 D̲a̲t̲a̲ ̲E̲n̲t̲r̲y̲ ̲F̲i̲e̲l̲d̲s̲
The cursor is position in the first field ready to
accept input.
3.3.2.3.1 C̲I̲F̲ ̲R̲e̲f̲e̲r̲e̲n̲c̲e̲:̲ ̲F̲i̲e̲l̲d̲ ̲1̲
The operator enters the CIF reference number 0-2…0e…32…0f…
(10 digits).
3.3.2.4 V̲a̲l̲i̲d̲a̲t̲i̲o̲n̲
It is checked that the CIF reference is legal and existing.
The following error codes are used:
- 001; INVALID ENTRY
- 215; NO CIF FOUND
3.3.2.5 E̲x̲i̲t̲ ̲C̲o̲n̲d̲i̲t̲i̲o̲n̲
When all data fields entered are accepted and the command
executed, the PUSY menu is displayed, the command line
and the response line are cleared. The cursor is returned
to the first position of the command field on the command
line, awaiting a new command to be entered.
The operator can cancel the current transaction by
depressing the CANCEL key (ref. section 3.1.4).
When a transaction is initiated, a log is printed on
the operator lineprinter and the configuration display
is updated.
When a transaction is completed, a log is printed on
the operator lineprinter. The log format is given in
Appendix D.
Figure 3.3.2-1
3.3.3 T̲e̲r̲m̲i̲n̲a̲t̲e̲ ̲O̲p̲e̲r̲a̲t̲o̲r̲ ̲O̲n̲l̲y̲ ̲M̲o̲d̲e̲
Format TOPM.
3.3.3.1 C̲o̲m̲m̲a̲n̲d̲
The terminate operator only mode format is obtained
by the command
- TOPM in command field.
3.3.3.2 P̲r̲e̲s̲e̲n̲t̲a̲t̲i̲o̲n̲
The format to be used is shown in Fig. 3.3.3-1.
3.3.3.3 D̲a̲t̲a̲ ̲E̲n̲t̲r̲y̲ ̲F̲i̲e̲l̲d̲s̲
The cursor is position in the first field ready to
accept input.
3.3.3.3.1 T̲e̲r̲m̲i̲n̲a̲t̲e̲ ̲O̲p̲e̲r̲a̲t̲o̲r̲ ̲O̲n̲l̲y̲ ̲T̲y̲p̲e̲:̲ ̲F̲i̲e̲l̲d̲ ̲1̲
The operator specifies whether the system is to be
- closed down
- continue start up.
3.3.3.4 V̲a̲l̲i̲d̲a̲t̲i̲o̲n̲
Only syntax check is performed error code used:
- 001; INVALID ENTRY
3.3.3.5 E̲x̲i̲t̲ ̲C̲o̲n̲d̲i̲t̲i̲o̲n̲
When all data fields entered are accepted and the command
executed, the format display, the command line, and
the response line are cleared. The cursor is returned
to the first position of the command field on the command
line, awaiting a new command to be entered.
The operator can cancel the current transaction by
depressing the CANCEL key (ref. section 3.1.4).
When a transaction is initiated, a log is printed on
the operator ROP.
When a transaction is completed, a log is printed on
the operator ROP. The log format is given in Appendix
D.
Figure 3.3.3-1
3.3.4 S̲w̲i̲t̲c̲h̲o̲v̲e̲r̲
Format SWCH.
3.3.4.1 C̲o̲m̲m̲a̲n̲d̲
The switchover format is obtained by the command:
- SWCH, in the command field.
The command is used to switchover from the ACTIVE PU
to STANDBY.
3.3.4.2 P̲r̲e̲s̲e̲n̲t̲a̲t̲i̲o̲n̲
The format used to execute a switchover is shown in
fig. 3.3.4-1.
The texts underneath the fields are used as an explanation
of the numbers to be inserted in the unprotected fields.
3.3.4.3 D̲a̲t̲a̲ ̲E̲n̲t̲r̲y̲ ̲F̲i̲e̲l̲d̲s̲
The cursor is positioned in the first field ready to
accept input.
3.3.4.3.1 T̲i̲m̲e̲ ̲B̲e̲f̲o̲r̲e̲ ̲S̲w̲i̲t̲c̲h̲o̲v̲e̲r̲ ̲:̲ ̲F̲i̲e̲l̲d̲ ̲1̲
The operator specifies the time to be used in a switchover
if set set:
- Zero, indicating an emergency switchover.
- Greater than zero, indicating an ordered switchover.
3.3.4.4 V̲a̲l̲i̲d̲a̲t̲i̲o̲n̲
A check is carried out whether a Standby PU exists.
If a standby PU does not exist, no switchover can take
place and therefore the active PU awaits a new command
by:
- Display of the current menu.
- The cursor is returned to the command field.
- A warning is displayed on the response line: "NO
STANDBY PU AVAILABLE".
The following error codes are used:
- 001; INVALID ENTRY
The error code is displayed in the left-hand margin.
The procedure used to obtain the explanation of the
error code is given in section 2.3.2.2.
If an invalid parameter is found, the operator has
to enter a new parameter.
3.3.4.5 E̲x̲i̲t̲ ̲C̲o̲n̲d̲i̲t̲i̲o̲n̲
When all data fields entered are accepted and the command
executed, the PUSY menu is displayed, the command line
and the response line are cleared. The cursor is returned
to the first position of the command field on the command
line, awaiting a new command to be entered.
The operator can cancel the current transaction by
depressing the CANCEL key (ref. section 3.1.4).
When a transaction is initiated, a log is printed on
the operator lineprinter and the configuration display
is updated.
When a transaction is completed, a log is printed on
the operator lineprinter. The log format is given in
Appendix D.
Fig. 3.3.4-1
3.3.5 C̲l̲o̲s̲e̲ ̲D̲o̲w̲n̲
Format CLOS.
3.3.5.1 C̲o̲m̲m̲a̲n̲d̲
The close-down format is obtained by the command:
- CLOS.
The command is used to close down one of the PUs.
3.3.5.2 P̲r̲e̲s̲e̲n̲t̲a̲t̲i̲o̲n̲
The format used to specify the close-down is shown
in fig. 3.3.5-1. The format contains two data Entry
fields, used by the operator to specify the close-down
mode:
- Status of PUs.
- Time to close-down.
Underneath each field an expounding of the parameters
to be inserted is given.
3.3.5.3 D̲a̲t̲a̲ ̲E̲n̲t̲r̲y̲ ̲F̲i̲e̲l̲d̲s̲
The cursor is positioned in the first field awaiting
input from the operator.
3.3.5.3.1 C̲l̲o̲s̲e̲-̲D̲o̲w̲n̲ ̲o̲f̲ ̲:̲ ̲F̲i̲e̲l̲d̲ ̲1̲
The operator specifes which PU is to be closed down.
3.3.5.3.2 T̲i̲m̲e̲ ̲:̲ ̲F̲i̲e̲l̲d̲ ̲2̲
If the operator wants an emergency close-down of the
Active, he sets time to zero. For all other settings
of the time, the close-down is to be regarded as an
ordered close-down. If a Standby PU is specified, the
close-down is always an emergency close-down.
3.3.5.4 V̲a̲l̲i̲d̲a̲t̲i̲o̲n̲
If the operator specifies a close-down of a Standby
PU, the time for close down is zero, all other settings
are regarded as zero. If the Standby PU already is
closed:
- The cursor is returned to the command field.
- The format display is cleared.
The error code to be used is:
- 001; INVALID ENTRY.
The error code is displayed in the left-hand margin.
The procedure for obtaining the explanation of the
number is given in section 2.3.2.2.
If an invalid number is found, the operator has to
enter a new one.
3.3.5.5 E̲x̲i̲t̲ ̲C̲o̲n̲d̲i̲t̲i̲o̲n̲
When all data fields entered are accepted and the command
executed, the PUSY menu is displayed, the command line
and the response line are cleared. The cursor is returned
to the first position of the command field on the command
line, awaiting a new command to be entered.
The operator can cancel the current transaction by
depressing the CANCEL key (ref. section 3.1.4).
When a transaction is initiated, a log is printed on
the operator ROP and the configuration display is updated.
When a transaction is completed, a log is printed on
the operator ROP. The log format is given in Appendix
D.
Fig. 3.3.5-1
3.4 C̲h̲a̲n̲n̲e̲l̲ ̲U̲n̲i̲t̲ ̲(̲C̲U̲)̲ ̲S̲y̲s̲t̲e̲m̲ ̲C̲o̲n̲t̲r̲o̲l̲
3.4.1 C̲U̲-̲S̲y̲s̲t̲e̲m̲ ̲M̲e̲n̲u̲
Format CUSY.
3.4.1.1 C̲o̲m̲m̲a̲n̲d̲
The CU-System Menu is obtained by the command:
- CUSY.
3.4.1.2 P̲r̲e̲s̲e̲n̲t̲a̲t̲i̲o̲n̲
The Menu Format lists the available options, plus the
commands required to obtain the options. See fig. 3.4.1-1.
3.4.1.3 C̲o̲m̲m̲a̲n̲d̲ ̲E̲n̲t̲r̲y̲
The cursor is positioned on the Command Line, awaiting
input of a command. The command specified by the operator
is executed when the ENTER key is depressed.
3.4.1.4 V̲a̲l̲i̲d̲a̲t̲i̲o̲n̲
The operator command is validated in accordance with
section 2.3.4.
3.4.1.5 E̲x̲i̲t̲ ̲C̲o̲n̲d̲i̲t̲i̲o̲n̲
If the command is accepted, the CU-System Menu is displayed
and the cursor is returned to the first position of
the command field on the command line. The operator
may now enter a new command.
If the CANCEL key is depressed, the command line and
the response line are cleared and the cursor is positioned
on the first position of the command field.
Fig. 3.4.1-1
3.4.2 L̲T̲U̲ ̲L̲i̲n̲e̲ ̲C̲o̲n̲t̲r̲o̲l̲
Format LTLN.
3.4.2.1 C̲o̲m̲m̲a̲n̲d̲
To obtain the format used to set up the LTU line characteristics,
the operator has to enter:
- LTLN, in the command field.
- ID (1 : 10), in the ID field.
ID is the number (Port-ID) used to give an explicit
specification of the LTU line.
3.4.2.2 P̲r̲e̲s̲e̲n̲t̲a̲t̲i̲o̲n̲
The format shown in fig. 3.4.2-1 contains the current
characteristics for the LTU line, which is specified
by the Port-ID. The possible numbers to be inserted
in the unprotected fields are explained underneath
each field.
3.4.2.3 D̲a̲t̲a̲ ̲E̲n̲t̲r̲y̲ ̲F̲i̲e̲l̲d̲s̲
The cursor is positioned in the first Data Entry Field,
ready for operator input.
3.4.2.3.1 T̲y̲p̲e̲ ̲:̲ ̲F̲i̲e̲l̲d̲ ̲1̲
The operator enters the type of line in this field.
The possible LTU lines are given in the next line of
the format.
3.4.2.3.2 S̲p̲e̲e̲d̲ ̲:̲ ̲F̲i̲e̲l̲d̲ ̲2̲
The operator enters a number associated with the speed
specified in the next format line.
The speed to be used for each type is given in Appendix
E.
3.4.2.3.3 S̲t̲a̲t̲u̲s̲ ̲:̲ ̲F̲i̲e̲l̲d̲ ̲3̲
The operator specifies whether the line is to be set
"in service" or "out of service".
Error cannot be set.
3.4.2.4 V̲a̲l̲i̲d̲a̲t̲i̲o̲n̲
Upon depression of the ENTER key, the parameters from
the Data Entry Fields are validated.
The LTU line parameters can only be changed:
- If the LTU line is logical disconnected
The type of line is valid if:
- The type of line is in accordance with the type
of LTU to which it is connected.
- For CCIS/SCARS max. 1 line per LTU.
- For TARE max. 2 lines per LTU.
- Or if status of LTU is "out of service".
The following error codes are used:
- 1; INVALID ENTRY
- 103; ILLEGAL SPEED
- 106; ILLEGAL TYPE
- 107; MAXIMUM CONFIGURATION EXCEEDED
- 6; ILLEGAL NUMBER
- 201; LINE CONNECTED IN PROFILE
- 203; NOT ALLOWED IN OPERATOR ONLY MODE
- 205; HW ̲ERROR
The error codes are displayed in the left-hand margin.
The procedure for obtaining the explanation of the
error code is given in section 2.3.2.2.
If an invalid parameter is found, the operator has
to insert another parameter.
3.4.2.5 E̲x̲i̲t̲ ̲C̲o̲n̲d̲i̲t̲i̲o̲n̲
When all data fields entered are accepted and the command
executed, the CUSY menu is displayed, the command line
and the response line are cleared. The cursor is returned
to the first position of the command field on the command
line, awaiting a new command to be entered.
The operator can cancel the current transaction by
depressing the CANCEL key (ref. section 3.1.4).
When a transaction is initiated, a log is printed on
the operator ROP and the configuration display is updated.
When a transaction is completed, a log is printed on
the operator ROP. The log format is given in Appendix
D.
Fig. 3.4.2-1
3.4.3 L̲T̲U̲ ̲C̲o̲n̲t̲r̲o̲l̲
Format LTUU.
3.4.3.1 C̲o̲m̲m̲a̲n̲d̲
The format used to set up the LTU parameters is obtained
by the command:
- LTUU in the command field
- ID (1:5), in the ID field
ID is the number which specifies the Port-ID of the
LTU to be updated.
3.4.3.2 P̲r̲e̲s̲e̲n̲t̲a̲t̲i̲o̲n̲
The LTU control format is shown in fig. 3.4.3-1
The Port-ID of the specified LTU is displayed in the
protected field.
Furthermore, the present state (type and status) is
displayed in the unprotected fields. The operator is
allowed to update these fields.
The possible number to be inserted, and an expounding
of these, are given underneath each unprotected field.
3.4.3.3 D̲a̲t̲a̲ ̲E̲n̲t̲r̲y̲ ̲F̲i̲e̲l̲d̲s̲
The cursor is positioned in the first Data Entry Field.
The operator can update this and/or jump to the next
field.
3.4.3.3.1 T̲y̲p̲e̲ ̲:̲ ̲F̲i̲e̲l̲d̲ ̲1̲
The operator enters the numbers associated with the
type of LTU specified in the next format line.
3.4.3.3.2 S̲t̲a̲t̲u̲s̲ ̲:̲ ̲F̲i̲e̲l̲d̲ ̲2̲
The operator specifies whether the LTU shall be set
Active (bus connection), Manual or "out of service".
Manual means that the operator sets the Bus Connection
Manual in the CU Crate
Error cannot be specified.
3.4.3.4 V̲a̲l̲i̲d̲a̲t̲i̲o̲n̲
Upon depression of the ENTER key, the parameters from
the Data Entry Fields are validated.
The LTU parameters can only be changed if:
- If the associated LTU-line(s) is logical disconnected
- If the current status is error
If an invalid parameter is found during validation,
an error code is displayed in the left-hand margin
of the line with the error.
The following error codes are used:
- 001; INVALID ENTRY
- 106; ILLEGAL TYPE
- 201; LINE CONNECTED IN PROFILE
- 205; NOT ALLOWED IN OPERATOR ONLY MODE
- 207; LTU ̲LOAD ̲ERROR
The procedure for obtaining the explanation of the
error code is given in section 2.3.2.2.
If an invalid parameter is found, the operator has
to insert another parameter.
3.4.3.5 E̲x̲i̲t̲ ̲C̲o̲n̲d̲i̲t̲i̲o̲n̲
When all data fields entered are accepted and the command
executed, the CUSY menu is displayed, the command line
and the response line are cleared. The cursor is returned
to the first position of the command field on the command
line, awaiting a new command to be entered.
The operator can cancel the current transaction by
depressing the CANCEL key (ref. section 3.1.4).
When a transaction is initiated, a log is printed on
the operator ROP.
When a transaction is completed, a log is printed on
the operator ROP. The log format is given in Appendix
D.
Fig. 3.4.3-1
3.4.4 D̲i̲s̲k̲ ̲D̲r̲i̲v̲e̲ ̲A̲s̲s̲i̲g̲n̲m̲e̲n̲t̲
Format DDRI.
3.4.4.1 C̲o̲m̲m̲a̲n̲d̲
The format used for assign/deassign a disk (for mirrored
disk mount/dismount(s) included) is obtained by entering:
- DDRI, in the command field.
3.4.4.2 P̲r̲e̲s̲e̲n̲t̲a̲t̲i̲o̲n̲
The disk drive assignment format is shown in fig. 3.4.4-1.
The text underneath each field explains the numbers
to be accepted in the field.
3.4.4.3 D̲a̲t̲a̲ ̲E̲n̲t̲r̲y̲ ̲F̲i̲e̲l̲d̲s̲
The cursor is positioned in the first unprotected field
ready for operator input.
3.4.4.3.1 T̲y̲p̲e̲ ̲:̲ ̲F̲i̲e̲l̲d̲ ̲1̲
The operator specifies which disk he wants to update.
3.4.4.3.2 S̲t̲a̲t̲u̲s̲ ̲:̲ ̲F̲i̲e̲l̲d̲ ̲2̲
The operator specifies whether the actual disk is to
be in-service or, offline (not know to CAMPS) if mirrored
disk mount/dismount is included in the command.
Error cannot be set.
3.4.4.4 V̲a̲l̲i̲d̲a̲t̲i̲o̲n̲
Upon depression of the ENTER key, the parameters are
validated.
If the operator specifies a mirrored disk:
- At least one disk has to be ON-LINE.
- The volume is expected to be physically mounted
prior to the assignment.
The following error codes are foreseen:
- 001; INVALID ENTRY
- 006; ILLEGAL TYPE
- 109; NO DISK AVAILABLE
- 205; HW ERROR
- 210; LAST MORRORED DISK
- 213; NON EXISTING VOLUME
- 214; VOLUME MOUNTED
- 221; COPY ERROR
The error numbers are displayed in the left-hand margin.
The procedure for obtaining an explanation of the number
is given in section 2.3.2.2.
If an invalid parameter has been found, the operator
has to insert another parameter.
3.4.4.5 E̲x̲i̲t̲ ̲C̲o̲n̲d̲i̲t̲i̲o̲n̲
When all data fields entered are accepted and the command
executed, the CUSY is displayed, the command line and
the response line are cleared. The cursor is returned
to the first position of the command field on the command
line, awaiting a new command to be entered.
The operator can cancel the current transaction by
depressing the CANCEL key (ref. section 3.1.4).
When a transaction is initiated, a log is printed on
the operator ROP and the configuration display is updated.
When a transaction is completed, a log is printed on
the operator ROP. The log format is given in Appendix
D.
Fig. 3.4.5-1
3.4.5 V̲o̲l̲u̲m̲e̲ ̲H̲a̲n̲d̲l̲i̲n̲g̲
Format VOLU.
3.4.5.1 C̲o̲m̲m̲a̲n̲d̲
The format used to specify mount/dismount of a volume
is obtained by the command:
- VOLU.
3.4.5.2 P̲r̲e̲s̲e̲n̲t̲a̲t̲i̲o̲n̲
The Volume Handling format is shown in fig. 3.4.5-1.
The format contains three Data Entry fields, to be
used by the operator, to specify the name of the volume
the action to be taken.
3.4.5.3 D̲a̲t̲a̲ ̲E̲n̲t̲r̲y̲ ̲F̲i̲e̲l̲d̲s̲
The cursor is positioned in the first Data Entry Field
ready for operator input.
3.4.5.3.1 V̲o̲l̲u̲m̲e̲ ̲N̲a̲m̲e̲ ̲:̲ ̲F̲i̲e̲l̲d̲ ̲1̲
The operator enters the name of the volume to be mounted/dismounted.
3.4.5.3.2 A̲c̲t̲i̲o̲n̲ ̲:̲ ̲F̲i̲e̲l̲d̲ ̲2̲
The operator specifies whether the volume has to be
mounted or dismounted.
3.4.5.4 V̲a̲l̲i̲d̲a̲t̲i̲o̲n̲
When the operator has depressed the ENTER key, the
input paramaters from the Data Entry Fields are validated.
A check is carried out as to whether:
- The specified volume exists.
- The specified disk is on-line.
The following error codes are used:
- 001 INVALID ENTRY
- 109 NO DISK AVAILABLE
- 205 HW ERROR
- 211 WRONG VOLUME NAME
- 212 VOLUME NAME IS USED
- 213 NON EXISTING VOLUME
- 214 VOLUME MOUNTED
The error numbers are displayed in the left-hand margin.
The procedure for obtaining an explanation of the error
code is given in section 2.3.2.2.
If an invalid parameter has been found, the operator
has to enter another parameter.
3.4.5.5 E̲x̲i̲t̲ ̲C̲o̲n̲d̲i̲t̲i̲o̲n̲
When all data fields entered are accepted and the command
executed, the CUSY menu is displayed, the command line
and the response line are cleared. The cursor is returned
to the first position of the command field on the command
line, awaiting a new command to be entered.
The operator can cancel the current transaction by
depressing the CANCEL key (ref. section 3.1.4).
When a transaction is initiated, a log is printed on
the operator ROP.
When a transaction is completed, a log is printed on
the operator. The log format is given in Appendix D.
Fig. 3.4.6-1
3.5 T̲D̲X̲-̲S̲y̲s̲t̲e̲m̲ ̲C̲o̲n̲t̲r̲o̲l̲
3.5.1 T̲D̲X̲-̲S̲y̲s̲t̲e̲m̲ ̲M̲e̲n̲u̲
Format TDXS.
3.5.1.1 C̲o̲m̲m̲a̲n̲d̲
The TDX-System Menu is obtained by the command "TDXS".
3.5.1.2 P̲r̲e̲s̲e̲n̲t̲a̲t̲i̲o̲n̲
The Menu lists the commands available to supervise
the TDX-System (refer fig. 3.5.1-1).
3.5.1.3 C̲o̲m̲m̲a̲n̲d̲ ̲E̲n̲t̲r̲y̲
The cursor is positioned on the Command Line, awaiting
input of a command. The command specified by the operator
is executed when the ENTER key is depressed.
3.5.1.4 V̲a̲l̲i̲d̲a̲t̲i̲o̲n̲
The operator command will be validated in accordance
with section 2.3.4.
3.5.1.5 E̲x̲i̲t̲ ̲C̲o̲n̲d̲i̲t̲i̲o̲n̲
If the command is accepted, the TDX-System Menu is
displayed and the cursor is returned to the first position
of the command field on command line. The operator
may now enter a new command.
If the CANCEL key is depressed, the command line and
the response line are cleared and the cursor is positioned
on the first position of the command field.
Fig. 3.5.1-1
3.5.2 L̲T̲U̲X̲ ̲L̲i̲n̲e̲ ̲C̲o̲n̲t̲r̲o̲l̲
Format LXLN.
3.5.2.1 C̲o̲m̲m̲a̲n̲d̲
To obtain the format used to control an LTUX line,
the operator has to enter:
- LXLN, in the command field.
- A number (1:120) in the ID field.
The ID is the number (Port-ID) used to give an explicit
specification of the LTUX line to be controlled.
3.5.2.2 P̲r̲e̲s̲e̲n̲t̲a̲t̲i̲o̲n̲
The format shown in fig. 3.5.2-1 contains the current
characteristic for the LTUX line, which is specified
by the Port-ID. The possible numbers to be inserted
in the unprotected fields are expounded below each
of the fields.
3.5.2.3 D̲a̲t̲a̲ ̲E̲n̲t̲r̲y̲ ̲F̲i̲e̲l̲d̲s̲
The cursor is positioned in the first Data Entry Field
ready for operator entry.
3.5.2.3.1 T̲y̲p̲e̲ ̲:̲ ̲F̲i̲e̲l̲d̲ ̲1̲
The operator specifies the type of device in this field.
The types of devices are specified on the next line
of the format.
3.5.2.3.2 A̲l̲p̲h̲a̲b̲e̲t̲ ̲:̲ ̲F̲i̲e̲l̲d̲ ̲2̲
If the operator wants to insert a PTP, PTR, LTP or
TRC/PTOP, he has to specify whether ITA 2 or ITA 5
is to be used.
3.5.2.3.3 S̲p̲e̲e̲d̲ ̲:̲ ̲F̲i̲e̲l̲d̲ ̲3̲
The operator enters the speed to be used for the line.
The possible speeds associated with a device are given
in the speed-table in Appendix E.
3.5.2.3.4 S̲t̲a̲t̲u̲s̲ ̲:̲ ̲F̲i̲e̲l̲d̲ ̲4̲
This field is used to specify whether the device is
to be set:
- "In service".
- "Out of service".
Error cannot be set.
3.5.2.4 V̲a̲l̲i̲d̲a̲t̲i̲o̲n̲
Upon depression of the ENTER key, the parameters from
the Data Entry Fields are validated.
The LTUX line parameters can only be changed:
- If the line is logical disconnected
The speed is valid if:
- Speed of the device is contained in the speed-table.
- Same speed on neighbour's lines (if present).
Note 1) A LTUX includes two sets of lines called
neighbour lines and they can be identified
by their Port-ID; 1 and 2, 3 and 4 ...
79 and 80 are neighbour lines.
- The sum of speeds on a group of lines is 9600
Baud
Note 2) A group of lines is connected to one LTUX;
a group can also be identified by the Port-ID
- 1, 2, 3, 4 is one group, 4, 5, 6, 7,
is another, and so on.
The type of device is accepted if:
- The LTUX to which the line is connected includes
the device type, or:
- The LTUX is "out of service".
The following error codes are used:
- 001; INVALID ENTRY
- 101; ILLEGAL PORT ID
- 102; ENTRY PORT ID
- 103; ILLEGAL SPEED
- 104; DESCREPANCY WITH THE NEIGHBOUR LINE
- 105; THE SUM OF SPEEDS EXCEEDS 19200 BAUD
- 106; ILLEGAL TYPE
- 107; MAX CONFIGURATION EXCEEDED
- 201; LINE CONNECTED IN PROFILE
- 203; NOT ALLOWED IN OPERATOR ONLY MODE
- 205; HW ERROR
The error codes are displayed in the left-hand margin
on the line in error. The procedure for obtaining the
explanation of the error code is given in section 2.3.2.2.
The explanation of the error code is given in the response
line and the cursor is returned to the field in error.
3.5.2.5 E̲x̲i̲t̲ ̲C̲o̲n̲d̲i̲t̲i̲o̲n̲
When all data fields entered are accepted and the command
executed, the TDX menu is displayed, the command line
and the response line are cleared. The cursor is returned
to the first position of the command field on the command
line, awaiting a new command to be entered.
The operator can cancel the current transaction by
depressing the CANCEL key (ref. section 3.1.4).
When a transaction is initiated, a log is printed on
the operator ROP.
When a transaction is completed, a log is printed on
the operator ROP. The log format is given in Appendix
D.
Fig. 3.5.2-1
3.5.3 L̲T̲U̲X̲ ̲C̲o̲n̲t̲r̲o̲l̲
Format LTUX.
3.5.3.1 C̲o̲m̲m̲a̲n̲d̲
To obtain the format used to control the LTUX, the
operator has to enter:
- LTUX, in the command field.
- A number (1 : 30), in the ID field.
The ID is the number (PORT-ID), used to give an explicit
specification of the LTUX to be controlled.
3.5.3.2 P̲r̲e̲s̲e̲n̲t̲a̲t̲i̲o̲n̲
The LTUX control format shown in fig. 3.5.3-1 contains
the current characteristics for the LTUX, specified
by the Port-ID. The possible numbers to be inserted
in the unprotected fields are expounded underneath
each field.
3.5.3.3 D̲a̲t̲a̲ ̲E̲n̲t̲r̲y̲ ̲F̲i̲e̲l̲d̲s̲
The cursor is positioned in the first Data Entry Field
and the operator may enter the new data.
3.5.3.3.1 T̲y̲p̲e̲ ̲:̲ ̲F̲i̲e̲l̲d̲ ̲1̲
The operator enters the number, associated with the
type of LTUX specified in the next format line.
The type specifies the lines (e.g. VDU, OCR) to be
accepted for this LTUX.
3.5.3.3.2 S̲t̲a̲t̲u̲s̲ ̲:̲ ̲F̲i̲e̲l̲d̲ ̲2̲
The operator specifies whether the LTUX shall be set:
- "In service" or:
- "Out of service".
Error cannot be specified.
3.5.3.4 V̲a̲l̲i̲d̲a̲t̲i̲o̲n̲
Upon depressing of the ENTER key, the parameters from
the Data Entry Fields are validated.
The LTUX parameter can only be changed:
- If the LTUX-lines associated to the LTUX are logical
disconnected
The LTUX type is accepted:
- If the lines "in service" fit, or:
- If the status is set "out of service".
If an invalid parameter is found during validation,
an error code is displayed in the left-hand margin
on the line with the error.
The following error codes are used:
- 001; INVALID ENTRY
- 101; ILLEGAL PORT ̲ID
- 102; ENTER PORT ̲ID
- 106; ILLEGAL TYPE
- 201; LINE CONNECTED IN PROFILE
- 203; NOT ALLOWED IN OPERATOR ONLY MODE
- 205; HW ERROR
3.5.3.5 E̲x̲i̲t̲ ̲C̲o̲n̲d̲i̲t̲i̲o̲n̲
If the data entry is accepted, the TDX menu is displayed,
the command line and the response line are cleared.
The cursor is returned to the first position of the
command field on the command line, awaiting a new command
to be entered.
If the operator does not want to update the format
displayed, he has to depress the CANCEL key. The exit
condition will be the same as above, but no transaction
takes place.
The transactions executed are logged on the operator
ROP.
The format of the log is shown in Appendix D.
Fig. 3.5.3-1
3.5.4 B̲S̲M̲-̲X̲ ̲C̲o̲n̲t̲r̲o̲l̲
Format BSMX.
3.5.4.1 C̲o̲m̲m̲a̲n̲d̲
To obtain the format used to specify to which TDX-Bux
a BSM-X is to be connected, the operator has to enter:
- BSMX, in the command field.
- A number (1 : 15), in the ID field.
The ID is the number (Port-ID) used to give an explicit
specification of the BSM-X module.
3.5.4.2 P̲r̲e̲s̲e̲n̲t̲a̲t̲i̲o̲n̲
The format shown in fig. 3.5.4-1 contains the current
characteristic for the BXM-X module.
The possible numbers to be inserted in the unprotected
field are explained underneath the field.
3.5.4.3 D̲a̲t̲a̲ ̲E̲n̲t̲r̲y̲ ̲F̲i̲e̲l̲d̲
The cursor is positioned in the Data Entry Field and
the operator may enter the new data.
3.5.4.3.1 S̲t̲a̲t̲u̲s̲ ̲:̲ ̲F̲i̲e̲l̲d̲ ̲1̲
The operator specifies whether the BSM-X module shall
be:
- Connected to the Active TDX bus.
- Connected to the non-active TDX bus.
- Taken "out of service".
Error cannot be set.
3.5.4.4 V̲a̲l̲i̲d̲a̲t̲i̲o̲n̲
Upon depressing the ENTER key, the parameter is validated.
If the operator specifies a BSM-X as connected to an
non active TDX-bus, a check is carried out as to whether
the LTUX-Lines associated to this BSM ̲X is logical
disconnected. The specification of an "out of service"
BSM-X means it is disconnected from both TDX-Buses.
The following error codes are foreseen:
- 001; INVALID ENTRY
- 101; ILLEGAL PORT ̲ID
- 102; ENTER PORT ̲ID
- 201; LINE CONNECTED IN PROFILE
- 203; NOT ALLOWED IN OPERATOR ONLY MODE
- 205; HW ERROR
- 206; WDP ̲CCB ̲FAILED
The error numbers are displayed in the left-hand margin.
The procedure to obtain an explanation of the number
is given in section 2.3.2.2.
If an invalid parameter has been found, the operator
has to insert another parameter.
3.5.4.5 E̲x̲i̲t̲ ̲C̲o̲n̲d̲i̲t̲i̲o̲n̲
When all data fields entered are accepted and the command
executed, the TDX menu is displayed, the command line
and the response line are cleared. The cursor is returned
to the first position of the command field on the command
line, awaiting a new command to be entered.
The operator can cancel the current transaction by
depressing the CANCEL key (ref. section 3.1.4).
When a transaction is initiated, a log is printed on
the operator lineprinter.
When a transaction is completed, a log is printed on
the operator lineprinter. The log format is given in
Appendix D.
Fig. 3.5.4-1
3.6 S̲o̲f̲t̲w̲a̲r̲e̲ ̲C̲o̲n̲t̲r̲o̲l̲ ̲C̲o̲m̲m̲a̲n̲d̲s̲
3.6.1 M̲e̲n̲u̲ ̲f̲o̲r̲ ̲S̲O̲F̲T̲ ̲C̲o̲m̲m̲a̲n̲d̲s̲
Format SOFT.
3.6.1.1 C̲o̲m̲m̲a̲n̲d̲
The SOFT command Menu is obtained by the command:
- SOFT.
3.6.1.2 P̲r̲e̲s̲e̲n̲t̲a̲t̲i̲o̲n̲
The Menu lists the available options, plus the commands
to be used to obtain these options.
The menu is shown in fig. 3.6.1-1.
3.6.1.3 C̲o̲m̲m̲a̲n̲d̲ ̲E̲n̲t̲r̲y̲
The cursor is positioned on the Command Line, awaiting
input of a command. The command specified by the operator
is executed, when the ENTER key is depressed.
3.6.1.4 V̲a̲l̲i̲d̲a̲t̲i̲o̲n̲
The operator command is validated in accordance with
section 2.3.4.
3.6.1.5 E̲x̲i̲t̲ ̲C̲o̲n̲d̲i̲t̲i̲o̲n̲
If the command is accepted, the Soft Command Menu is
displayed and the cursor is returned to the first position
of the command field on command line. The operator
may now enter a new command.
If the CANCEL key is depressed, the command line and
the response line are cleared and the cursor is positioned
on the first position of the command field.
Fig. 3.6.1-1
3.6.2 A̲d̲j̲u̲s̲t̲ ̲T̲i̲m̲e̲
Format ADTM.
3.6.2.1 C̲o̲m̲m̲a̲n̲d̲
The command used to obtain the time of day format is:
- ADTM.
3.6.2.2 P̲r̲e̲s̲e̲n̲t̲a̲t̲i̲o̲n̲
The format used to update the clock is shown in fig.
3.6.2-1. The format contains two Data Entry Fields
to be used to update the clock.
3.6.2.3 D̲a̲t̲a̲ ̲E̲n̲t̲r̲y̲ ̲F̲i̲e̲l̲d̲s̲
The cursor is positioned in the first field awaiting
input from the operator.
3.6.2.3.1 T̲i̲m̲e̲ ̲t̲o̲ ̲b̲e̲ ̲A̲d̲j̲u̲s̲t̲e̲d̲:̲ ̲ ̲F̲i̲e̲l̲d̲ ̲1̲
The operator specifies whether the clock is to be set
forward or backward.
3.6.2.3.2 N̲u̲m̲b̲e̲r̲ ̲o̲f̲ ̲S̲e̲c̲o̲n̲d̲s̲:̲ ̲F̲i̲e̲l̲d̲ ̲2̲
The operator enters the number of seconds to be adjusted
(max. 120 seconds).
3.6.2.4 V̲a̲l̲i̲d̲a̲t̲i̲o̲n̲
The following error codes are foreseen:
- 001; INVALID ENTRY
- 108; ADJUSTMENT GREATER THAN 120 SECONDS
- 203; NOT ALLOWED IN OPERATOR ONLY MODE
The error codes are displayed in the left-hand margin.
3.6.2.5 E̲x̲i̲t̲ ̲C̲o̲n̲d̲i̲t̲i̲o̲n̲
When all data fields entered are accepted and the command
executed, the SOFT menu is displayed, the command line
and the response line are cleared. The cursor is returned
to the first position of the command field on the command
line, awaiting a new command to be entered.
The operator can cancel the current transaction by
depressing the CANCEL key (ref. section 3.1.4).
When a transaction is initiated, a log is printed on
the operator ROP.
When a transaction is completed, a log is printed on
the operator ROP. The log format is given in Appendix
D.
Fig. 3.6.2-1
3.6.3 L̲o̲a̲d̲ ̲M̲o̲d̲i̲f̲i̲e̲d̲ ̲S̲o̲f̲t̲w̲a̲r̲e̲
Format LMOS.
3.6.3.1 C̲o̲m̲m̲a̲n̲d̲
The format to be used to load modified software is
obtained by the command:
- LMOS.
Prior to execution of this command, the operator has
to mount the floppy disk (Ref. section 3.4.5.) or request
the supervisor to mount the offline disk:
3.6.3.2 P̲r̲e̲s̲e̲n̲t̲a̲t̲i̲o̲n̲
The format used to load software is shown in fig. 3.6.3-1.
The Data Entry Fields are used to define:
- Copy Mode.
- Type of software.
Underneath each field, a description of the parameters
to be inserted is given.
3.6.3.3 D̲a̲t̲a̲ ̲E̲n̲t̲r̲y̲ ̲F̲i̲e̲l̲d̲s̲
The cursor is positioned in the first field ready to
receive the operator input.
3.6.3.3.1 C̲o̲p̲y̲ ̲M̲o̲d̲e̲ ̲:̲ ̲F̲i̲e̲l̲d̲ ̲1̲
The operator specifies the disk containing the new
software and the disk on which it is to be copied.
3.6.3.3.2 T̲y̲p̲e̲ ̲o̲f̲ ̲S̲o̲f̲t̲w̲a̲r̲e̲ ̲:̲ ̲F̲i̲e̲l̲d̲ ̲2̲
The operator specifies whether application, system
software or patchfiles are to be copied.
3.6.3.3.3 S̲p̲e̲c̲i̲f̲y̲ ̲S̲i̲n̲g̲l̲e̲ ̲F̲i̲l̲e̲:̲ ̲F̲i̲e̲l̲d̲ ̲3̲
Refer comments i figure 3.6.3-1.
3.6.3.4 V̲a̲l̲i̲d̲a̲t̲i̲o̲n̲
A check is carrried out as to whether the specified
disks are available and whether modified software has
loaded or is to be loaded.
The following error codes are foreseen:
- 001; INVALID ENTRY
- 205; HW ERROR
- 221; COPY ERROR
3.6.3.5 E̲x̲i̲t̲ ̲C̲o̲n̲d̲i̲t̲i̲o̲n̲
When all data fields entered are accepted and the command
executed, the SOFT menu is displayed, the command line
and the response line are cleared. The cursor is returned
to the first position of the command field on the command
line, awaiting a new command to be entered.
The operator can cancel the current transaction by
depressing the CANCEL key (ref. section 3.1.4).
When a transaction is initiated, a log is printed on
the operator ROP.
When a transaction is completed, a log is printed on
the operator ROP. The log format is given in Appendix
D.
Fig. 3.6.3-1
3.6.4 S̲e̲t̲ ̲T̲r̲a̲c̲e̲ ̲M̲a̲s̲k̲
FORMAT STRM
3.6.4.1 C̲o̲m̲m̲a̲n̲d̲
The format used to set a trace mask is obtained by
the command:
- STRM in the command field.
3.6.4.2 P̲r̲e̲s̲e̲n̲t̲a̲t̲i̲o̲n̲
The STRM format is shown in fig. 3.6.4-1.
The purpose of the Trace Function is to facilitate
monitoring of application modules by tracing their
system call. Because of the overhead in terms of memory
and CPU, the Trace Function is only to be used in test
and integration phase.
3.6.4.3 D̲a̲t̲a̲ ̲E̲n̲t̲r̲y̲ ̲F̲i̲e̲l̲d̲s̲
3.6.4.3.1 D̲e̲f̲i̲n̲e̲ ̲P̲r̲o̲c̲e̲s̲s̲:̲ ̲ ̲F̲i̲e̲l̲d̲ ̲1̲
The operator specifies the number of the process from
which trace records are to be generated. If zero specified,
the next field is used to specify the global priority.
If 999 specified the trace record generation is reset
for all processes.
3.6.4.3.2 P̲r̲i̲o̲r̲i̲t̲y̲:̲ ̲ ̲F̲i̲e̲l̲d̲ ̲2̲
The operator defines the priority of process specified
in Field 1. If field 1 is set to zero, the global
priority is specified.
The priority is used to define the amount of trace
records stored in the trace file attached to the process
in the following way:
- A trace record is only generated if the Global
Priority and the process priority of the calling
process are both smaller than or equal to the Function
Priority of the called function (A function is
a unique identification of the called system function,
the Priority for each function is set at the system
generation).
Each process has its own trace file.
3.6.4.4 V̲a̲l̲i̲d̲a̲t̲i̲o̲n̲
It is checked if the specified process number exists.
The following error codes are used:
- 001; INVALID ENTRY
- 203; NOT ALLOWED IN OPERATOR ONLY MODE
- 216; ILLEGAL PROCESS ̲NO
