top - download
⟦838ef88c3⟧ Wang Wps File
Length: 109984 (0x1ada0)
Types: Wang Wps File
Notes: CPS/ICD/002
Names: »1243A «
Derivation
└─⟦48a409da8⟧ Bits:30006053 8" Wang WCS floppy, CR 0082A
└─ ⟦this⟧ »1243A «
WangText
_…00……00……00……00…@…0a……00……00…@…0b…@…0f…@…01…?…0b…?…05…>…00…=…0a…=
<…0d…<…07…;…0f…:…0a…: 9…0f…8…09…8…02…7…0d…7…07…6…0c…6…06…5…0c…5…02…5…07…4…0c…4…00…4…05…3…0b……18……01……18……06……18……07……17……08……17……09……17……0b……17……0f……17…
…16……08……16……0c……16……00……16……06……15……0a……15……00……15……06……15……07……14……0c……14……0d……14……0e……14……02……14……06……14……07……13……08……86…1 …02… …02… …02…
…02…CPS/230/ICD/0002
…02…820719…02……02…
SUPERVISOR COMMANDS AND PROCEDURES
…02…ISSUE 4.1…02…CAMPS
Change no. 1
Telex from
SHAPE,dated
820216,CAMPS
Log no. 527
DN1 42 Editorial
DN2 52 Editorial
53 Editorial
DN3 54 CC
55 CC
56 CC
DN4 66 Editorial
DN6 77 Editorial
DN7 80 Editorial
DN8 123 Editorial
DN10 124 Editorial
DN11 137 Editorial
DN12 160 Editorial
DN13 181 Editorial
DN14 184 Operating Signal Table Print
185 Operating Signal Table Print
186 Operating Signal Table Print
DN15 211 Editorial
DN16 228 Editorial
DN17 229 Editorial
DN18 230 Editorial
DN19 231 Editorial
DN20 233 Editorial
DN21 235 Editorial
DN22 236 Editorial
DN23 237 Editorial
DN24 243 Editorial
DN25 244 Editorial
DN26 277 Editorial
DN27 303 Editorial
DN28 303 Editorial
DN29 a. 304 Editorial
DN30 307 Editorial
MOM4(1,15) 3.2.3.4g)
MOM4(8) 3.2.3.4g2)
MOM4(14) 3.2.3.4h)
MOA(MMI) 3.2.3.5
MOM4(2)
MOM4(2) 3.2.3.5b)
MOM4(2) 3.2.3.5c)
MOA(MMI) TABLES:
3.2.3.5-1
3.2.3.5-2
3.2.3.5-3
MOA(MMI), 3.2.3.5 Definition of Transitions
MOM4(2)
MOM4(5) 3.2.3.6
MOM4(1.2) 3.2.3.7
MOA(MMI) 3.2.3.7.1
MOA(MMI) 3.2.3.7.2
MOA(MMI) 3.2.3.7.3
MOM4(1.2) 3.2.3.7.4
3.2.4 Table of Contents
T̲A̲B̲L̲E̲ ̲O̲F̲ ̲C̲O̲N̲T̲E̲N̲T̲S̲
1 SCOPE ............................................
20
1.1 REFERENCE DOCUMENTS ............................
20
1.2 DOCUMENT STRUCTURE .............................
21
2 VDU CHARACTERISTICS ..............................
22
2.1 VDU FACILITIES .................................
22
2.2 VDU SCREEN LAYOUT ..............................
22
2.2.1 VDU Header Area ............................
23
2.2.1.1 Terminal Function ......................
23
2.2.1.2 Classification .........................
23
2.2.1.3 Time ...................................
24
2.2.1.4 Queue Information ......................
24
2.2.1.4.1 Supervisor .........................
24
2.2.1.4.2 Message Distribution Control
Operator (MDCO) ....................
25
2.2.1.4.3 Message Service Operator (MSO) .....
25
2.2.1.5 Command Line ...........................
25
2.2.1.6 Response Line ..........................
26
2.2.1.7 System Line ............................
26
2.2.2 Format Area ................................
26
2.2.2.1 Margin Area ............................
27
2.2.2.2 Line Descriptor ........................
27
2.2.2.3 Field Descriptor .......................
27
2.2.2.4 Field Protection .......................
27
2.2.3 Menus ......................................
32
2.2.3.1 Screen-Layout ..........................
32
2.2.3.2 Menu Selection .........................
32
2.2.3.3 Commands ...............................
32
2.3 COMMANDS .......................................
32
2.3.1 General Commands ...........................
33
2.3.1.1 Command Validation .....................
33
2.3.2 Format Edit ................................
34
2.3.2.1 Insert (n) Lines .......................
34
2.3.2.2 Delete (n) Lines .......................
34
2.3.3 Field Edit .................................
35
2.3.3.1 Character Overwrite ....................
35
2.3.3.2 Next Field .............................
35
2.3.3.3 Previous Field .........................
35
2.3.4 Screen Manipulation ........................
35
2.3.4.1 Command ................................
35
2.3.4.2 Return .................................
35
2.3.4.3 Page On ................................
36
2.3.4.4 Page Back ..............................
36
2.3.4.5 Scroll On ..............................
36
2.3.4.6 Scroll Down ............................
36
2.3.4.7 System .................................
36
2.3.5 Transaction Processing .....................
36
2.3.5.1 Enter ..................................
37
2.3.5.2 Cancel .................................
37
2.3.5.3 Delete and present Next Message ........
37
2.3.5.4 Keep and Present Next Message ..........
37
2.3.5.5 Display Error Message ..................
37
2.3.5.6 Print ..................................
38
2.3.5.7 Return to Current Menu .................
38
2.3.6 Specific Commands ..........................
38
2.4 CURSOR CONTROL .................................
38
3 SUPERVISORY FUNCTIONS ............................
39
3.1 INTRODUCTION ...................................
39
3.1.1 Format .....................................
39
3.1.2 Menu .......................................
39
3.1.3 Direct Execution ...........................
39
3.1.4 Validation .................................
39
3.1.5 Error Notification .........................
40
3.1.6 Transaction Identity .......................
40
3.1.7 Item Reference Identity ....................
40
3.2 SIGN ON (SION) .................................
42
3.2.1 Data Entry .................................
42
3.2.1.1 Identification Code and Password .......
42
3.2.2 Validation .................................
42
3.3 HIGH LEVEL MENU ................................
45
3.3.1 User/Terminal ..............................
45
3.3.1.1 Supervisor Capability ..................
45
3.3.1.2 MDCO Capability ........................
45
3.3.1.3 MSO Capability .........................
45
3.3.1.4 User Capability ........................
45
3.3.1.5 Supervisor/MDCO/MSO/User Capabilities
.. 46
3.3.1.6 Supervisor Terminal ....................
46
3.3.1.7 Warning Message ........................
46
3.4 SUPERVISOR MENU (SUPV) .........................
49
3.4.1 Command Entries ............................
49
3.4.2 Validation .................................
49
4 SYSTEM CONTROL ...................................
52
4.1 SYSTEM CONTROL FUNCTIONS (SYSC) ................
52
4.1.1 Sequence ...................................
54
4.1.1.1 Sequence A - Parameter Examine/Update
.. 54
4.1.1.2 Sequence B - Table Entry Examine/Update
54
4.2 DEVICE CONTROL FUNCTIONS (DEVC) ................
58
4.2.1 Terminal Position Control (TEPC "TD") ......
60
4.2.1.1 Command Entry ..........................
60
4.2.1.2 Data Entry .............................
60
4.2.1.2.1 Terminal Designator ................
60
4.2.1.2.2 Blocked ............................
60
4.2.1.2.3 Maximum Classification .............
61
4.2.1.2.4 Special Handling Category ..........
61
4.2.1.2.5 Supervisor .........................
61
4.2.1.2.6 MSO ................................
62
4.2.1.2.7 MDCO ...............................
62
4.2.1.2.8 Preparation ........................
62
4.2.1.2.9 Reception ..........................
62
4.2.1.2.10 Release ..........................
62
4.2.1.2.11 User ID ..........................
63
4.2.1.2.12 SCDs .............................
63
4.2.1.2.13 VDU Port .........................
63
4.2.1.2.14 Shared Printer Device Designator
. 64
4.2.1.2.15 Delete This Terminal Profile .....
64
4.2.1.2.16 Next Terminal Profile ............
64
4.2.1.2.17 Next Terminal Designator .........
64
4.2.1.3 Validation .............................
64
4.2.2 PT/OCR/SATP Control (POSC "DD", "DEVICE
TYPE") .....................................
67
4.2.2.1 Command Entry ..........................
67
4.2.2.2 Data Entry .............................
67
4.2.2.2.1 Device Designator ..................
67
4.2.2.2.2 Connected ..........................
67
4.2.2.2.3 Device Type ........................
68
4.2.2.2.4 Maximum Classification .............
68
4.2.2.2.5 Printer/Papertape Reader ...........
68
4.2.2.2.6 Number of Plys .....................
68
4.2.2.2.7 Device Port ........................
69
4.2.2.2.8 Delete This Device Profile .........
69
4.2.2.2.9 Next Device Profile ...............
69
4.2.2.2.10 Next Device Designator ...........
69
4.2.2.3 Validation .............................
69
4.2.3 Channel Control (CHAC "CD") ................
71
4.2.3.1 Command Entry ..........................
71
4.2.3.2 Data Entry .............................
71
4.2.3.2.1 Incoming Channel Designator ........
71
4.2.3.2.2 Outgoing Channel Designator ........
71
4.2.3.2.3 Connect Channel ....................
72
4.2.3.2.4 Channel Type .......................
72
4.2.3.2.5 Maximum Classification .............
72
4.2.3.2.6 To RI ..............................
72
4.2.3.2.7 Open Channel for Incoming Traffic
.. 73
4.2.3.2.8 Channel Open for Outgoing Traffic
.. 73
4.2.3.2.9 Circuit ............................
73
4.2.3.2.10 Channel Port .....................
73
4.2.3.2.11 Delete This Channel Profile ......
74
4.2.3.2.12 Next Channel Profile .............
74
4.2.3.2.13 Next Channel Designator ..........
74
4.2.3.3 Validation .............................
74
4.3 ADDRESSING SCHEME CONTROL FUNCTIONS (ADSC)......
77
4.3.1 SIC-Table Update (SICT "SIC") ..............
79
4.3.1.1 Command Entry ..........................
79
4.3.1.2 Data Entry .............................
79
4.3.1.2.1 SIC ................................
79
4.3.1.2.2 Normal SDL .........................
79
4.3.1.2.3 Exercise SDL .......................
79
4.3.1.2.4 Crisis SDL .........................
80
4.3.1.2.5 Delete This SIC Table Entry ........
80
4.3.1.2.6 Next SIC-Table Entry ...............
80
4.3.1.2.7 Next SIC ...........................
80
4.3.1.3 Validation .............................
80
4.3.2 SDL-Table Update (SDLT "SDL") ..............
82
4.3.2.1 Command Entry ..........................
82
4.3.2.2 Data Entry .............................
82
4.3.2.2.1 SDL ................................
82
4.3.2.2.2 Action SCDs ........................
82
4.3.2.2.3 Info SCDs ..........................
83
4.3.2.2.4 Delete This SDL-Table Entry ........
83
4.3.2.2.5 Remove All References to this SDL
from SIC-Table .....................
83
4.3.2.2.6 Next SDL-Table Entry ...............
83
4.3.2.2.7 Next SDL ...........................
83
4.3.2.3 Validation .............................
83
4.3.3 SCD-Table Update (SCDT "SCD") ..............
85
4.3.3.1 Command Entry ..........................
85
4.3.3.2 Date Entry .............................
85
4.3.3.2.1 SCD ................................
85
4.3.3.2.2 Device/Terminal Type ...............
85
4.3.3.2.3 Designator .........................
86
4.3.3.2.4 No. of Copies ......................
86
4.3.3.2.5 Delete This SCD-Table Entry ........
86
4.3.3.2.6 Remove All References to this SCD
from SDL-Tables ....................
86
4.3.3.2.7 Next SDL-Table Entry ...............
86
4.3.3.2.8 Next SCD ...........................
86
4.3.3.3 Validation .............................
86
4.3.4 AIG-Table Update (AIGT "AIG") ..............
89
4.3.4.1 Command Entry ..........................
89
4.3.4.2 Data Entry .............................
89
4.3.4.2.1 AIG ................................
89
4.3.4.2.2 AG .................................
89
4.3.4.2.3 PLAREF & PLA .......................
89
4.3.4.2.4 Continuation .......................
90
4.3.4.2.5 Delete This AIG ....................
90
4.3.4.2.6 Next AIG-Table Entry ...............
90
4.3.4.2.7 Next AIG ...........................
90
4.3.4.3 Validation .............................
90
4.3.5 Global PLA-Table Update (GPLT "PLAREF") ....
92
4.3.5.1 Command Entry ..........................
92
4.3.5.2 Data Entry .............................
92
4.3.5.2.1 PLAREF .............................
92
4.3.5.2.2 PLA ................................
92
4.3.5.2.3 RIs ................................
92
4.3.5.2.4 Circuits ...........................
93
4.3.5.2.5 Classification .....................
93
4.3.5.2.6 Delete This PLAREF .................
93
4.3.5.2.7 Remove All References to This
PLAREF From AIG Table ..............
93
4.3.5.2.8 Next Global PLA-Table Entry ........
93
4.3.5.2.9 Next PLAREF ........................
94
4.3.5.3 Validation .............................
94
4.3.6 RI-Table Update (RITA "RI") ................
96
4.3.6.1 Command Entry ..........................
96
4.3.6.2 Data Entry .............................
96
4.3.6.2.1 RI .................................
96
4.3.6.2.2 Circuit ............................
96
4.3.6.2.3 Classification .....................
97
4.3.6.2.4 Delete This RI-Table Entry .........
97
4.3.6.2.5 Remove All References to This RI
from the PLA Table .................
97
4.3.6.2.6 Next RI-Table Entry ................
97
4.3.6.2.7 Next RI ............................
97
4.3.6.3 Validation .............................
97
4.3.7 CIRCUIT-Table Update (CIRT "CIRCUIT NO")
... 99
4.3.7.1 Command Entry ..........................
99
4.3.7.2 Data Entry .............................
99
4.3.7.2.1 Circuit ............................
99
4.3.7.2.2 Circuit Type .......................
99
4.3.7.2.3 Network ............................
100
4.3.7.2.4 Number of Connected Channels .......
100
4.3.7.2.5 Classification .....................
100
4.3.7.2.6 Next Circuit-Table Entry ...........
100
4.3.7.2.7 Next Circuit No. ...................
100
4.3.7.3 Validation .............................
101
4.3.8 SCARS/ACCIS Display-Table Update
(SCCT "DISPLAY ID") ........................
103
4.3.8.1 Command Entry ..........................
103
4.3.8.2 Data Entry .............................
103
4.3.8.2.1 Display Id .........................
103
4.3.8.2.2 Next Display .......................
103
4.3.8.2.3 Next Display ID ....................
103
4.3.8.3 Validation .............................
104
4.3.9 Operating Signal Table (OPST "MHI") ........
106
4.3.9.1 Command Entry ..........................
106
4.3.9.2 Data Entry .............................
106
4.3.9.2.1 MHI ................................
106
4.3.9.2.2 Message Handling Instruction .......
106
4.3.9.2.3 Delete This Operating Signal Table
Entry ..............................
106
4.3.9.2.4 Next Operating Signal Table Entry
.. 106
4.3.9.2.5 Next MHI ...........................
107
4.3.9.3 Validation .............................
107
4.3.10 Local PLA-Table Update (LPLT "PLAREF")
... 109
4.3.10.1 Command Entry ........................
109
4.3.10.2 Data Entry ...........................
109
4.3.10.2.1 PLAREF ...........................
109
4.3.10.2.2 Local PLA ........................
109
4.3.10.2.3 HQ ...............................
109
4.3.10.2.4 Delete This Local PLA-Table Entry
110
4.3.10.2.5 Next Local PLA-Table Entry .......
110
4.3.10.2.6 Next PLAREF ......................
110
4.3.10.3 Validation ...........................
110
4.3.11 Local RI-Table Update (LORI) .............
112
4.3.11.1 Data Entry ...........................
112
4.3.11.1.1 System Code C/S/A ................
112
4.3.11.1.2 Local CAMPS RIs ..................
112
4.3.11.1.3 CAMPS De RIs .....................
112
4.3.11.2 Validation ...........................
112
4.3.12 Reorganize All Tables (REOR) .............
114
4.3.13 Abandon Reorganization (ABRO) ............
114
4.4 USER PROFILE UPDATE (UPUP "USER ID") ...........
115
4.4.1 Command Entry ..............................
115
4.4.2 Data Entry .................................
115
4.4.2.1 User ID ................................
115
4.4.2.2 Maximum Classification .................
115
4.4.2.3 Special Handling Category ..............
115
4.4.2.4 Capabilities ...........................
116
4.4.2.5 Exercise Messages Only .................
116
4.4.2.6 Associated Release Terminal ............
116
4.4.2.7 Password ...............................
116
4.4.2.8 Last Ammended ..........................
116
4.4.2.9 Expires ................................
116
4.4.2.10 Delete This Profile ..................
117
4.4.2.11 Next User Profile ....................
117
4.4.2.12 Next User ID .........................
117
4.4.3 Validation .................................
117
4.5 QUEUE CONTROL FUNCTIONS (QUEC) .................
120
4.5.1 Block Circuit Queue (BLCQ "CIRCUIT NO") ....
122
4.5.2 Unblock Circuit Queue (UBCQ "CIRCUIT NO")
.. 122
4.5.3 Block Terminal Queue (BLTQ "TD") ...........
122
4.5.4 Unblock Terminal Queue (UBTQ "TD") .........
122
4.5.5 Block Device Queue (BLDQ "DD") .............
122
4.5.6 Unblock Device Queue (UBDQ "DD") ...........
122
4.5.7 Cancel Circuit Queue (CACQ "CIRCUIT NO")
... 123
4.5.7.1 Command Entry ..........................
123
4.5.7.2 Data Entry .............................
123
4.5.7.2.1 Message Precedence .................
123
4.5.7.2.2 Next Circuit-Table Entry ...........
123
4.5.7.2.3 Next Circuit .......................
123
4.5.7.3 Validation .............................
124
4.5.8 Cancel Terminal Queue (CATQ "TD") ..........
126
4.5.8.1 Command Entry ..........................
126
4.5.8.2 Data Entry .............................
126
4.5.8.2.1 Receive Queue ......................
126
4.5.8.2.2 Release-Queue ......................
126
4.5.8.2.3 Preparation ........................
126
4.5.8.2.4 Response ...........................
126
4.5.8.2.5 Next Terminal-Table Entry ..........
127
4.5.8.2.6 Next Terminal Designator ...........
127
4.5.8.3 Validation .............................
127
4.5.9 Cancel Device Queue (CADQ "DD") ............
129
4.5.9.1 Command Entry ..........................
129
4.5.9.2 Data Entry .............................
129
4.5.9.2.1 Message Precedence .................
129
4.5.9.2.2 Next Device-Table Entry ............
129
4.5.9.2.3 Next Device Designator .............
129
4.5.9.3 Validation .............................
129
4.5.10 Deleted ..................................
4.5.11 Deleted ..................................
4.5.12 Deleted ..................................
4.5.13 Deleted ..................................
4.6 SUPERVISOR PRINT CONTROL (SUPC) ................
134
4.6.1 Data Entry .................................
134
4.6.1.1 Device Designator ......................
134
4.6.2 Validation .................................
134
4.7 DISC CONTROL FUNCTIONS (DISC) ..................
137
4.7.1 Off Load Data (OFLD "TIME STAMP, VOL-ID")
.. 139
4.7.2 Abandon Off Load (ABOL) ....................
139
4.7.3 Copy System Parameter File (COPY) ..........
139
4.7.4 Off Line Retrieval Off (OROF) ..............
139
4.7.5 Off Line Retrieval On (ORON) ...............
139
4.7.6 Off Line Retrieval Suspend (ORSU) ..........
139
4.7.7 Currently Used Volume List (VOLI) ..........
140
4.7.8 Refuse Mount (REMO "VOL-ID") ...............
140
4.7.9 Volume Mount (VOMO "VOL-ID") ...............
140
4.7.10 System Volume Mount (VSMO "VOL-ID") ......
140
4.7.11 Volume Dismount (VODM "VOL-ID") ..........
140
4.7.12 Volume Name (VONM "VOL-ID") ..............
141
4.7.12.1 Data Entry ...........................
141
4.7.12.1.1 Dump of System Parameters Allowed
141
4.7.12.1.2 Offline Storage Allowed ..........
141
4.7.12.2 Validation ...........................
141
4.7.13 Volume Delete (VODL "VOL-ID") ............
143
4.7.13.1 Data Entry ...........................
143
4.7.13.1.1 Dump of System Parameter Allowed
. 143
4.7.13.1.2 Time of Last Dump ................
143
4.7.13.1.3 Offline Storage Allowed ..........
143
4.7.13.1.4 Time of Last Offload .............
143
4.7.13.1.5 Delete ...........................
143
4.7.13.2 Validation ...........................
143
4.8 COMMAND CONTROL (CMDC "CMC") ...................
145
4.8.1 Command entry ..............................
145
4.8.2 Data Entry .................................
145
4.8.2.1 Permissive Entry Code ..................
145
4.8.2.2 Restrictive Warning Text ...............
145
4.8.2.3 Next Command ...........................
145
4.8.2.4 Next Command Code ......................
145
4.8.3 Validation .................................
146
4.9 SECURITY CONTROL (SECC) ........................
148
4.9.1 Data Entry .................................
148
4.9.1.1 Security Interrogation to be Caused by
Classification .........................
148
4.9.1.2 Security Warning to be Caused by
Classification .........................
148
4.9.1.3 Special Handling Categories ............
148
4.9.1.4 Security Warning Text ..................
149
4.9.1.5 Security Warning Code ..................
149
4.9.2 Validation .................................
149
4.10 GLOBAL NO. SERIES CONTROL FUNCTIONS (GNSC)
... 152
4.10.1 System No. Series Control (NOSC) .........
154
4.10.1.1 Data Entry ...........................
154
4.10.1.1.1 Reset System Release Series to
0001 .............................
154
4.10.1.1.2 Reset System Print Control No.
Series to 0001 ...................
154
4.10.1.1.3 Reset Special Handling Print
Control Series to 0001 ...........
154
4.10.1.1.4 Special Handling Categories to
Cause Increment of Special
Handling Print Control Number ....
154
4.10.2 Channel No. Series Control (NOCC "CD")
... 156
4.10.2.1 Command Entry ........................
156
4.10.2.2 Data Entry ...........................
156
4.10.2.2.1 Reset Channel Serial No. .........
156
4.10.2.2.2 Reset Daily ......................
156
4.10.2.2.3 Sequence Type 3 Digits ...........
156
4.10.2.2.4 Next Channel .....................
156
4.10.2.2.5 Next Channel Designator ..........
157
4.10.2.3 Validation ...........................
157
4.10.3 Transaction No. Series reset (NOTR
"TD/DD") .................................
159
4.11 SYSTEM PARAMETER CONTROL FUNCTIONS (SYPC).....
161
4.11.1 Print/Punch Parameter Control (PPPC)......
163
4.11.1.1 Data Entry ...........................
163
4.11.1.1.1 Lines Per Page ...................
163
4.11.1.1.2 Lines Between Pages ..............
163
4.11.1.1.3 Max Flash-Preemption Delay .......
163
4.11.2 Channel Parameter Control (CHPC) .........
165
4.11.2.1 Data Entry ...........................
165
4.11.2.1.1 Send Self-Addressed Channel Check
To TRC ...........................
165
4.11.2.1.2 Send Channel Continuity Message
to NICS-TARE .....................
165
4.11.2.1.3 Expect Channel Continuity Message
From NICS-TARE ...................
165
4.11.2.1.4 Service Message To Be Generated
For More Than 140 Consecutive
Identical Characters Are Received
From TRC .........................
165
4.11.2.1.5 Expect Flash-Message Receipt .....
165
4.11.2.1.6 Send Channel-Check Message to
SCARS/CCIS .......................
165
4.11.2.1.7 Expect Transaction On
Acknowledgement From SCARS/CCIS
.. 165
4.11.2.1.8 Number Of Retransmissions To
SCARS/CCIS .......................
165
4.11.2.1.9 Select Permissible Delay For
Preemption .......................
165
4.11.3 ACP127 Parameter Control (ACPC) ..........
167
4.11.3.1 Data Entry ...........................
167
4.11.3.1.1 Five Spaces ......................
167
4.11.3.1.2 Separate R and U RIs .............
167
4.11.3.1.3 ZGC Insert .......................
167
4.11.3.1.4 Year .............................
167
4.11.3.1.5 Time Zone ........................
167
4.11.4 Message Distribution Parameter Control
(MDPC) ...................................
169
4.11.4.1 Data Entry ...........................
169
4.11.4.1.1 All Incoming Messages ............
169
4.11.4.1.2 All Of Classification ............
169
4.11.5 Special Distribution Parameter Control
(SDPC) ...................................
171
4.11.5.1 Date Entry ...........................
171
4.11.5.1.1 Device Designator for Papertape
Reader ...........................
171
4.11.5.1.2 Device Designator for Papertape
Punch ............................
171
4.11.5.1.3 Device Designator ................
171
4.11.5.2 Validation ...........................
172
4.11.6 Crisis Indicator On (CION) ...............
174
4.11.7 Crisis Indicator Off (CIOF) ..............
174
4.11.8 Set Quiet Hours (SQHT "TD") ..............
174
4.11.9 Stop Quiet Hours (SQHO) ..................
174
4.11.10 Flash Queue Time Out (FLQT "NN") .........
174
4.11.11 Close Log CIF (LGCL) .....................
174
4.12 SYSTEM INFORMATION EXTRACT FUNCTIONS (SYIE)...
176
4.12.1 Log Trace (LGTR) .........................
178
4.12.1.1 Data Entry ...........................
178
4.12.1.1.1 Trace From - To ..................
178
4.12.1.1.2 All Log Records ..................
178
4.12.1.1.3 For Channel Designator ...........
178
4.12.1.1.4 Incoming Messages ................
178
4.12.1.1.5 Outgoing Messages ................
178
4.12.1.1.6 Channel Discontinuity ............
179
4.12.1.1.7 For Terminal Designator ..........
179
4.12.1.1.8 Terminal Procedures ..............
179
4.12.1.1.9 MDCO .............................
179
4.12.1.1.10 Message Service ..................
179
4.12.1.1.11 Supervisor Commands ..............
179
4.12.1.1.12 Security Procedures ..............
179
4.12.1.1.13 For Device Designator ............
179
4.12.1.2 Validation ...........................
180
4.12.2 Password List (PWLT) .....................
182
4.12.3 Queue State Print (QSPT) .................
182
4.12.4 User Profile Print (UPPT "USER-ID") ......
182
4.12.5 Terminal profile Print (TPPT "TD") .......
182
4.12.6 Device Profile Print (DPPT "DD") .........
182
4.12.7 Channel Profile print (CPPT "CD") ........
182
4.12.8 Command Print (CMPT) .....................
183
4.12.9 System Parameter Print (SPAP) ............
183
4.12.10 Storage Occupancy Request (STOC) .........
183
4.13 TABLE PRINT FUNCTIONS (TAPR)....................
185
5 MESSAGE HANDLING .................................
195
5.1 MESSAGE HANDLING FUNCTIONS (MSGH) ..............
195
5.1.1 Commands ...................................
195
5.1.2 Validation .................................
195
5.2 SERVICE MESSAGE PREPARATION (SMPR) .............
198
5.2.1 new Plaindress Format Preparation (PRPF)
... 201
5.2.1.1 Data Entry of ACP127 Information
(Fig. 5.2.1-2) .........................
201
5.2.1.1.1 Item Reference Identity ............
201
5.2.1.1.2 Classification .....................
201
5.2.1.1.3 Special Handling ...................
202
5.2.1.1.4 Precedence Action ..................
202
5.2.1.1.5 Precedence Info. ...................
202
5.2.1.1.6 Message Handling Instructions ......
202
5.2.1.1.7 From ...............................
202
5.2.1.1.8 To Action ..........................
203
5.2.1.1.9 To Info. ...........................
203
5.2.1.1.10 Exempt ...........................
203
5.2.1.2 Validation .............................
203
5.2.1.3 Text ...................................
204
5.2.1.4 Entry of Message Processing Action
(Fig. 5.2.1-4) .........................
204
5.2.2 New Abbreviated Plaindress Format
Preparation (PRAP) .........................
209
5.2.2.1 Data Entry of ACP127 Format Line 2, 3
and 4 (Fig. 5.2.2.2-2) .................
209
5.2.2.1.1 Item Reference Identity ............
209
5.2.2.1.2 Precedence .........................
209
5.2.2.1.3 Routing Indicators .................
209
5.2.2.1.4 DE Routing Indicator ...............
210
5.2.2.1.5 Classification .....................
210
5.2.2.1.6 Special Handling ...................
210
5.2.2.1.7 Message Handling Instruction .......
210
5.2.2.2 Validation .............................
211
5.2.2.3 Entry of Text (Format line 12) .........
211
5.2.2.4 Entry of Message Processing Action
(Fig. 5.2.1-4) .........................
211
5.2.3 New Abbreviated Service Message Format
Preparation (PRAS) .........................
215
5.2.4 Continue Plaindress Preparation (CPFP) .....
217
5.2.4.1 Data Entry .............................
217
5.2.4.2 Validation .............................
217
5.2.5 Continue Abbreviated Plaindress Preparation
(CAPP) .....................................
219
5.2.6 Continue Abbreviated Service Message
Preparation (CASP) .........................
219
5.2.7 Service Message Deletion (DESM) ............
221
5.2.7.1 Data Entry .............................
221
5.2.7.2 Validation .............................
221
5.2.8 Status of Outgoing Service Messages (OSMS)
. 224
5.2.8.1 Data Presentation ......................
224
5.2.8.1.1 Messages Sent for Transmission .....
224
5.2.8.1.2 Deferred Messages ..................
224
5.2.8.1.3 Messages Deleted Since Previous
Status .............................
224
5.2.8.1.4 Number of Messages Prepared Since
Previous Status ....................
224
5.2.8.2 Validation .............................
224
5.3 RETRIEVAL FOR LOCAL USE (RELU) .................
227
5.3.1 Key Type Entry .............................
227
5.3.2 Retrieval Key A ............................
229
5.3.2.1 Data Entry .............................
229
5.2.3.1.1 Time of Occurrence (TOC) or TOC
Window .............................
229
5.3.2.1.2 Channel Designator .................
229
5.3.2.1.3 Channel Serial Number ..............
229
5.3.3 Retrieval Key B ............................
231
5.3.3.1 Data Entry .............................
231
5.3.3.1.1 Time of Occurrence (TOC) or TOC
Window .............................
231
5.3.3.1.2 Station ID .........................
231
5.3.3.1.3 Station Serial Number ..............
231
5.3.3.1.4 File Time ..........................
231
5.3.4 Retrieval Key C ............................
233
5.3.4.1 Data Entry .............................
233
5.3.4.1.1 Time of Occurrence (TOC) or TOC
Window .............................
233
5.3.4.1.2 DTG ................................
233
5.3.4.1.3 Headquarters ID ....................
233
5.3.4.1.4 SIC ................................
233
5.3.5 Retrieval key D ............................
235
5.3.5.1 Data Entry .............................
235
5.3.5.1.1 Time of Occurrence (TOC) or TOC
Window .............................
235
5.3.5.1.2 Item Reference Identity ............
235
5.3.6 Retrieval Key E ............................
237
5.3.6.1 Data Entry .............................
237
5.3.6.1.1 DTG ................................
237
5.3.6.1.2 Headquarter ID .....................
237
5.3.7 Validation .................................
239
5.4 RETRIEVAL FOR READDRESSAL (READ) ...............
243
5.4.1 Key Type Entry .............................
243
5.4.2 Validation of Retrieval Data ...............
243
5.4.3 Readdressal ................................
243
5.4.4 Data Entry .................................
245
5.4.4.1 From ...................................
245
5.4.4.2 To .....................................
245
5.4.4.3 To Action ..............................
245
5.4.4.4 To Info ................................
245
5.4.4.5 Exempt .................................
245
5.4.4.6 Local Print ............................
246
5.4.5 Validation .................................
246
5.4.6 Transmission ...............................
246
5.5 RETRIEVAL FOR RERUN (RERN) .....................
249
5.5.1 Validation Of Retrieval Data ...............
249
5.5.2 Rerun ......................................
249
5.6 RETRIEVAL FOR REDISTRIBUTION (REDS) ............
251
5.6.1 Validation Of Retrieval Data ...............
251
5.6.2 Redistribution .............................
251
5.6.3 Data Entry .................................
251
5.6.3.1 To SCDs ................................
251
5.6.3.2 Local Print ............................
252
5.6.4 Validation .................................
252
5.6.5 Distribution ...............................
252
5.7 RETRIEVAL FOR DELETION (REDE) ..................
255
5.7.1 Validation Of Retrieval Data ...............
255
5.7.2 Deletion ...................................
255
5.8 RESPONSE MESSAGE DISPLAY (RESP) ................
258
6 SUPERVISOR ENGINEERING ...........................
260a
6.1 SUPERVISOR ENGINEERING FUNCTIONS................
260a
6.2 NORMAL MODE (SENF) .............................
260a
6.2.1 SICH COMMAND ...............................
260a
6.2.2 PMAN COMMAND ...............................
260c
6.3 RESTART MODE ...................................
260c
6.3.1 CANCEL SYSTEM QUEUE (CASQ) .................
260e
6.3.1.1 DATA ENTRY .............................
260e
6.3.1.1.1 MDCO QUEUE (OPTIONAL) ..............
260e
6.3.1.1.2 MESSAGE SERVICE INCOMING QUEUE
(OPTIONAL) .........................
260e
6.3.1.1.3 MESSAGE SERVICE OUTGOING QUEUE
(OPTIONAL) .........................
260e
6.3.1.2 VALIDATION .............................
260e
6.3.2 CANCEL ALL CIRCUIT QUEUES (CAAC) ...........
260f
6.3.3 CANCEL ALL TERMINAL QUEUES (CAAT) ..........
260f
6.3.4 CANCEL ALL DEVICE QUEUES (CAAD) ............
260f
6.3.5 CACQ CMD ...................................
260f
6.3.6 CATQ CMD ...................................
260f
6.3.7 CADQ CMD ...................................
260f
6.3.8 CAGO COMMAND ...............................
260f
6.3.9 QSPT COMMAND ...............................
260f
6.3.10 STOC COMMAND ..............................
260f
7 MESSAGE DISTRIBUTION CONTROL .....................
262
7.1 MDCO FUNCTIONS (MDCO) ..........................
262
7.1.1 Command ....................................
262
7.1.2 Validtion ..................................
262
7.2 SERVICE MESSAGE PREPARATION (SMPR) .............
264
7.3 RETRIEVAL FOR REDISTRIBUTION (REDS) ............
264
7.4 MESSAGE DISTRIBUTION ASSISTANCE (MDAS) .........
266
7.4.1 Incoming Message Assistance ................
268
7.4.1.1 Data Entry .............................
268
7.4.1.1.1 SCD List ...........................
268
7.4.1.1.2 Local Print ........................
269
7.4.1.2 Sequence ...............................
269
7.4.1.2.1 PAGE-ON ............................
269
7.4.1.2.2 PAGE BACK ..........................
269
7.4.1.2.3 PRINT ..............................
269
7.4.1.2.4 ENTER ..............................
269
7.4.1.3 Validation .............................
270
7.4.2 Alternative Distribution Assistance ........
273
7.4.2.1 Data Entry .............................
273
7.4.2.1.1 SCD List ...........................
273
7.4.2.1.2 Local Print ........................
274
7.4.2.2 Sequence ...............................
274
7.4.2.2.1 PAGE ON ............................
274
7.4.2.2.2 PAGE BACK ..........................
274
7.4.2.2.3 PRINT ..............................
274
7.4.2.2.4 ENTER ..............................
274
7.4.2.3 Validation .............................
274
7.4.3 Objects Queued To The MDCO .................
277
7.4.3.1 Data Entry .............................
277
7.4.3.2 Sequence ...............................
277
7.4.3.2.1 PRINT ..............................
277
7.4.3.2.2 Send Comment .......................
277
7.4.3.3 Validation .............................
278
7.5 RESPONSE MESSAGE DISPLAY (RESP) ................
280
8 MESSAGE SERVICE CONTROL ..........................
282
8.1 MSO FUNCTIONS (MSOC) ...........................
282
8.1.1 Commands ...................................
282
8.1.2 Validation .................................
282
8.2 SERVICE MESSAGE PREPARATION (SMPR) .............
284
8.3 RETRIEVAL FOR READDRESSAL (READ) ...............
284
8.4 RETRIEVAL FOR RERUN (RERN) .....................
284
8.5 OUTGOING MESSAGE SERVICE ASSISTANCE (OMAS) .....
285
8.5.1 Outgoing RI Assignment .....................
287
8.5.1.1 Data Entry .............................
287
8.5.1.1.1 RI Assignment ......................
287
8.5.1.1.2 Punch ..............................
288
8.5.1.1.3 Clear ..............................
288
8.5.1.1.4 External Assigned T Instructions
... 288
8.5.1.1.5 Internal Assigned T Instructions
... 288
8.5.1.1.6 Local Print ........................
289
8.5.1.2 Sequence ...............................
289
8.5.1.2.1 PAGE ON ............................
289
8.5.1.2.2 PAGE BACK ..........................
289
8.5.1.2.3 PRINT ..............................
289
8.5.1.2.4 ENTER ..............................
289
8.5.1.3 Validation .............................
290
8.6 INCOMING MESSAGE SERVICE ASSISTANCE (IMAS) .....
293
8.6.1 Garble Correction ..........................
295
8.6.1.1 Data Entry .............................
295
8.6.1.1.1 Edit ...............................
295
8.6.1.1.2 Annotation .........................
296
8.6.1.2 Sequence ...............................
296
8.6.1.2.1 PRINT ..............................
296
8.6.1.2.2 ENTER ..............................
296
8.6.1.2.3 DELETE AND PRESENT NEXT ............
296
8.6.1.3 Validation .............................
296
8.6.2 Message Inspection .........................
298
8.6.2.1 Data Entry .............................
298
8.6.2.2 Sequence ...............................
298
8.6.2.2.1 PRINT ..............................
298
8.6.2.2.2 ENTER ..............................
298
8.6.2.2.3 DELETE AND PRESENT NEXT ............
298
8.6.2.3 Validation .............................
299
8.7 RESPONSE MESSAGE DISPLAY (RESP) ................
301
APPENDIX A: FIELD/ELEMENT DICTIONARY ...............
302
APPENDIX B: SYSTEM REPLY MESSAGES ..................
309
APPENDIX C: LIST OF COMMANDS .......................
310
1̲ ̲ ̲S̲C̲O̲P̲E̲
This ICD (Interface Control Document) includes the
description of procedures, commands and associated
formats defining the operator/computer interface related
to the following CAMPS functions:
- Supervisor
- Message Service
- Message Distribution Control
- Engineering
In relation to these functions the facilities to perform
the following are described:
- System parameter and table updates
- Service Messages
- Incoming Message Correction
- Routing Assistance
- Distribution Assistance
The parameters used in commands and procedures are
defined in Appendix A.
The specific command and procedure format is subject
to change during the system and subsystem design phase,
while the data items operated on will remain unchanged.
The table structures depicted are logical and do not
imply specific requirements to the implementation.
1.1 R̲E̲F̲E̲R̲E̲N̲C̲E̲ ̲D̲O̲C̲U̲M̲E̲N̲T̲S̲
The following documents are listed for reference purposes
only. The listing does not constitute the contents
of the documents as System Requirements but is intended
to serve the Contractor in providing supplementary
information in cases of interpretation of the requirements
specifically stated in this document:
ACP131B, Jul. 74
ACP117J, Sept. 1977, ACP117 Supp. 1G Dec. 79
ACP121 Supp. 1 A, Jan. 1970, 121E Jul. 70
ACP127 NATO Supp. 3, May 1973, 127(E) Oct. 74
APP-3, Jan. 1978
ADat-P3, Jan. 1975
The above documents are only applicable to the extent
that they are referenced in this ICD by name and specific
sections.
1.2 D̲O̲C̲U̲M̲E̲N̲T̲ ̲S̲T̲R̲U̲C̲T̲U̲R̲E̲
1) The description of the Supervisor Procedures is
in terms of TRANSACTIONS.
A transaction consists of a dialogue which a supervisor
is able to perform to achieve the aim of the selected
function. The transaction identifies FORMATS, describes
the dialogues associated with those formats, and
describes a possible sequence of formats. The overall
sequence of formats is shown 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, or which are required to give the
user direction, are also listed.
2̲ ̲ ̲V̲D̲U̲ ̲C̲H̲A̲R̲A̲C̲T̲E̲R̲I̲S̲T̲I̲C̲S̲
2.1 V̲D̲U̲ ̲F̲A̲C̲I̲L̲I̲T̲I̲E̲S̲
The full set of features of the CAMPS VDU are described
in the System Requirements Specification para. 3.4.1.10.1.
The basic characteristics assumed for this specification
are as specified below. The characteristics do not
imply additional requirements to CPS/210/SYS/0001.
- 5 lines VDU header
- Min 22 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 have the following attributes-Mandatory,
optional, alpha, numeric, alphanumeric, length
- VDU attributes - inverse video, dual intensity,
bell, paging, scrolling over VDU memory contents
- Delete/insert character
- Press to repeat for specified keys
- Lockable
2.2 V̲D̲U̲ ̲S̲C̲R̲E̲E̲N̲ ̲L̲A̲Y̲O̲U̲T̲
The VDU screen is divided into two areas; a five line
VDU header and a 22 line format area. The header contains
terminal status information and the format area is
used by the system to display formats and by the user
to enter data. (Fig. 2.2-1).
2.2.1 V̲D̲U̲ ̲H̲e̲a̲d̲e̲r̲ ̲A̲r̲e̲a̲
The fields used in the header are the following:
- Terminal Function
- Classification of current screen contents
- Time
- Queue status
- Command line
- Response Line
- System Line
2.2.1.1 T̲e̲r̲m̲i̲n̲a̲l̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲
This describes the transaction in course. It is a 25
alpha-numeric field.
The defined terminal functions are shown in the format
descriptions in section 3, through 8.
This field is updated on a per-format basis.
2.2.1.2 C̲l̲a̲s̲s̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
This relates to the classification of the information
on the screen. It is a 20 character alpha field.
Displayed items with the classification identified
will be updated before the presentation of the format.
For items where the classification will first be recognized
during validation this field will be updated when the
subsequent format is displayed.
The terminal and the operator have a preset highest
classification in their profile. The default classification
appearing on the screen is the lower of these two.
2.2.1.3 T̲i̲m̲e̲
This is the Time in DATE TIME GROUP format. It is a
14 alpha-numeric field containing the Day, Hour, Minute,
Zone, Month, Year.
This is updated every minute.
2.2.1.4 Q̲u̲e̲u̲e̲ ̲I̲n̲f̲o̲r̲m̲a̲t̲i̲o̲n̲
Queue Information is described separately for each
supervisory function in the following subsections:
Queue Information is updated every minute. FLASH update
occurs when explicitly stated in the text.
2.2.1.4.1 S̲u̲p̲e̲r̲v̲i̲s̲o̲r̲
Four Queues, one for each print function, are displayed,
each showing the totals of all messages in the respective
Queue, awaiting print-out.
The four Printer Queues are placed in order of priority
and have the following functions:
REPR: Report Print
SUPR: Supervisor Print
STAT: Statistics Print
LOGP: Log Print
A Response Queue is displayed showing all items queued
for Supervisor attention.
A User Queue is displayed, where the Supervisor can
see the total of items queued for the Supervisor's
user Capacity. (See Fig. 2.2-1).
2.2.1.4.2 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̲ ̲O̲p̲e̲r̲a̲t̲o̲r̲ ̲(̲M̲D̲C̲O̲)̲
Four Queues, one for each precedence level, are displayed,
giving the totals of all messages awaiting distribution
assistance for each precedence level.
A Distribution Queue is shown, with a total of all
messages awaiting distribution assistance.
When FLASH messages are queued, immediate update of
the above referenced queues takes place and a short
audio alarm is given.
A Response Queue is shown where all retrieved messages
are queued.
A User Queue is shown, where the MDCO can see the total
of items queued for the User Capacity. (See Fig. 2.2-2).
2.2.1.4.3 M̲e̲s̲s̲a̲g̲e̲ ̲S̲e̲r̲v̲i̲c̲e̲ ̲O̲p̲e̲r̲a̲t̲o̲r̲ ̲(̲M̲S̲O̲)̲
Four Queues, one for each precedence level, are shown,
giving the totals of all messages in the Incoming or
Outgoing Message Queue respectively, for each precedence
level.
Two Queues with totals of the Incoming and Outgoing
Messages, respectively, queued for service, are displayed.
When FLASH messages are queued immediate update of
the above referenced queues takes place and a short
audio alarm is given.
As for Supervisor and MDCO, the MSO has a Response
Queue and a User Queue. (See Fig. 2.2-3).
2.2.1.5 C̲o̲m̲m̲a̲n̲d̲ ̲L̲i̲n̲e̲
The command line will be used for the insertion of
commands and entry of parameters as listed in Appendix
C.
Commands will be entered by pressing a "Command" function
key which will cause the cursor to jump to the Command
Line in the header. The supervisor will then enter
the command on this line. On pressing the Return Key,
the command will be executed, the command line cleared,
and the cursor repositioned back within the main format
area. A command will consist of a command code, composed
of four alpha characters, possibly followed by one
or more parameters. Commas will be used as separators
between parameters.
2.2.1.6 R̲e̲s̲p̲o̲n̲s̲e̲ ̲L̲i̲n̲e̲
System response messages and replies to commands where
appropriate will be displayed on the response line.
It has a maximum length of 70 alpha numeric characters.
2.2.1.7 S̲y̲s̲t̲e̲m̲ ̲L̲i̲n̲e̲
All data exchanged between the user and the System
in connection with the formats Sign-On and Sign-Off
are performed via this System Line. Also the selection
of the CAMPS functions Supervisor, MDCO, MSO and User
is performed via this line. Commands will be entered
by pressing the "System" function key which will cause
the cursor to jump to the System Line in the VDU-header.
Security warning and security interrogation is also
performed via this line. Password or Security Code
is entered here.
2.2.2 F̲o̲r̲m̲a̲t̲ ̲A̲r̲e̲a̲
The symbols used in the VDU Layout forms is shown in
fig. 2.2-4.
Where specified the format area may be divided into
the margin area and the user area.
2.2.2.1 M̲a̲r̲g̲i̲n̲ ̲A̲r̲e̲a̲
The ten character margins used by the system to indicate
the following:
1 2 3 4 5 6 7 8 9
0
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
ERROR CODE SPACE SPACE NOT USED
LINE
DESCRIPTOR
The user area consists of the remaining 70 characters.
2.2.2.2 L̲i̲n̲e̲ ̲D̲e̲s̲c̲r̲i̲p̲t̲o̲r̲
A line descriptor will be given in the VDU margin to
indicate to the user if a line is repeatable or not.
2.2.2.3 F̲i̲e̲l̲d̲ ̲D̲e̲s̲c̲r̲i̲p̲t̲o̲r̲
Each data entry field has a descriptor, specifying
whether the user should input alpha, numeric or alphanumeric
data, and whether the entry is optional or mandatory.
This descriptor may, where specified in the format
description, be visible to the user in the form of
a symbol preceding each field, as a reminder of the
type of data required.
2.2.2.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.
Figure 2.2-1…01…SCREEN LAYOUT
Fig. 2.2-2
Fig. 2.2-3
= inverse video field
= Unprotected data-entry
field
= Protected data-field
L̲i̲n̲e̲ ̲d̲e̲s̲c̲r̲i̲p̲t̲o̲r̲
R = Repeating
F̲i̲e̲l̲d̲ ̲D̲e̲s̲c̲r̲i̲p̲t̲o̲r̲s̲
N = Mandatory numeric
n = Optional numeric
A = Mandatory alpha
a = Optional alpha
D = Mandatory/alphanumeric
d = Optional alphanumeric
Fig. 2.2-4…01……01…S̲Y̲M̲B̲O̲L̲S̲ ̲U̲S̲E̲D̲ ̲O̲N̲ ̲V̲D̲U̲ ̲L̲A̲Y̲O̲U̲T̲ ̲F̲O̲R̲M̲S̲
2.2.3 M̲e̲n̲u̲s̲
Menus will consist of a list of the functions and associated
commands available to the user, and will have no data-entry
fields.
2.2.3.1 S̲c̲r̲e̲e̲n̲-̲L̲a̲y̲o̲u̲t̲
Menus may occupy the entire margin and user area of
the VDU Screen (see 2.2.2 above).
2.2.3.2 M̲e̲n̲u̲ ̲S̲e̲l̲e̲c̲t̲i̲o̲n̲
The user selects an item from a menu by inputting a
command. The cursor will be pre-positioned on the command
line or system line awaiting his input. The menu will
provide an "aide-memoire" for the command relevant
to the options presented.
2.2.3.3 C̲o̲m̲m̲a̲n̲d̲s̲
The user is not limited to the commands shown on the
menu; any valid command for the selected CAMPS function
may be input.
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 command codes
2.3.1 G̲e̲n̲e̲r̲a̲l̲ ̲C̲o̲m̲m̲a̲n̲d̲s̲
The set of general commands available to the user is:
- Format Edit INSERT N LINES
DELETE N LINES
- Field Edit CHARACTER OVERWRITE
NEXT FIELD
PREVIOUS FIELD
- Screen Manipulations COMMAND
RETURN
PAGE-ON
PAGE-BACK
SCROLL-ON
SCROLL-BACK
SYSTEM
- Transaction Processing ENTER
CANCEL
DELETE AND PRESENT NEXT
MESSAGE
KEEP AND PRESENT NEXT MESSAGE
DISPLAY ERROR MESSAGE
PRINT
RETURN TO CURRENT MENU
2.3.1.1 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.
2.3.2 F̲o̲r̲m̲a̲t̲ ̲E̲d̲i̲t̲
The following commands are available in format edit.
Scrolling is not allowed.
2.3.2.1 I̲n̲s̲e̲r̲t̲ ̲(̲n̲)̲ ̲L̲i̲n̲e̲s̲
An "Insert" command is used to provide additional space
in a format.
The lines below the insert are pushed down to accomodate
the inserted lines.
If there is not enough free space on the current page
for the required number of lines then the displayed
lines will appear on a subsequent page.
The inserted lines are positioned with respect to the
cursor position, at the moment the command key was
depressed.
This command is only applicable to repeatable lines.
2.3.2.2 D̲e̲l̲e̲t̲e̲ ̲(̲n̲)̲ ̲L̲i̲n̲e̲s̲
A "delete" command is used to remove lines from a format.
The lines below the deletion are pushed up to remove
the deleted lines.
The deleted lines are positioned with respect to the
cursor position at the moment the command key was activated.
This command can only be used to delete repeatable
lines.
2.3.3 F̲i̲e̲l̲d̲ ̲E̲d̲i̲t̲
Editing is allowed on the contents of unprotected fields.
Only on ENTER will the changed fields be available
to the host for validation.
2.3.3.1 C̲h̲a̲r̲a̲c̲t̲e̲r̲ ̲O̲v̲e̲r̲w̲r̲i̲t̲e̲
The character to be overwritten is defined by the cursor
position. The character typed in will overwrite the
current one.
2.3.3.2 N̲e̲x̲t̲ ̲F̲i̲e̲l̲d̲
This command causes the cursor to jump to the next
field.
2.3.3.3 P̲r̲e̲v̲i̲o̲u̲s̲ ̲F̲i̲e̲l̲d̲
This command causes the cursor to return to the beginning
of the previous field.
2.3.4 S̲c̲r̲e̲e̲n̲ ̲M̲a̲n̲i̲p̲u̲l̲a̲t̲i̲o̲n̲
2.3.4.1 C̲o̲m̲m̲a̲n̲d̲
This causes the cursor to move to the command line.
2.3.4.2 R̲e̲t̲u̲r̲n̲
This causes the contents of the command line and system
line to be sent to the host.
2.3.4.3 P̲a̲g̲e̲ ̲O̲n̲
This causes the next page of information to be displayed.
If the presently displayed page is the last page of
a format this key shall have no effect.
2.3.4.4 P̲a̲g̲e̲ ̲B̲a̲c̲k̲
This causes the previous page of information to be
displayed. If the presently displayed page is the first
page of a format this key shall have no effect.
2.3.4.5 S̲c̲r̲o̲l̲l̲ ̲O̲n̲
This allows the user to move the display up one line
at a time until the bottom of the "display" is reached.
Scrolling is allowed within the limitation of the pages
currently stored in the VDU.
2.3.4.6 S̲c̲r̲o̲l̲l̲ ̲D̲o̲w̲n̲
This allows the user to move the display down one line
at a time until the top of the "display" is reached.
Scrolling is allowed within the limitation of the pages
currently stored in the VDU.
2.3.4.7 S̲y̲s̲t̲e̲m̲
This causes the cursor to move to the system line.
2.3.5 T̲r̲a̲n̲s̲a̲c̲t̲i̲o̲n̲ ̲P̲r̲o̲c̲e̲s̲s̲i̲n̲g̲
2.3.5.1 E̲n̲t̲e̲r̲
This causes the current pages stored in the VDU to
be transmitted to the host.
2.3.5.2 C̲a̲n̲c̲e̲l̲
This causes the current transaction not yet accepted
by the System to be disregarded and the item to remain
unchanged.
For MSO/MDCO, the command cancel causes the message
worked upon to be returned to the originating place
in the appropriate queue.
2.3.5.3 D̲e̲l̲e̲t̲e̲ ̲a̲n̲d̲ ̲P̲r̲e̲s̲e̲n̲t̲ ̲N̲e̲x̲t̲ ̲M̲e̲s̲s̲a̲g̲e̲
This causes the item currently on the screen to be
removed from the queue and the next item in the queue
to be displayed.
This command is only valid in receive/response mode,
and for manipulation of the Distribution Queue and
for the two Message Service Queues.
If there are no items in the queue, the system gives
response message "QUEUE IS EMPTY".
2.3.5.4 K̲e̲e̲p̲ ̲a̲n̲d̲ ̲P̲r̲e̲s̲e̲n̲t̲ ̲N̲e̲x̲t̲ ̲M̲e̲s̲s̲a̲g̲e̲
This causes the item currently on the screen to stay
in the queue and the next item from the queue to be
displayed. This command is only valid in receive/response
mode, and for manipulation of the Distribution Queue
and the Message Service Queues.
2.3.5.5 D̲i̲s̲p̲l̲a̲y̲ ̲E̲r̲r̲o̲r̲ ̲M̲e̲s̲s̲a̲g̲e̲
This command will cause the system to display the error
message, specified by the Command Parameter, in the
response line.
Valid command parameters are the error codes defined.
(ref. app. B).
2.3.5.6 P̲r̲i̲n̲t̲
This causes the entire received message/comment, part
of which is currently on the VDU screen, to be printed.
See individual Formats for availability of PRINT facilities
of formats.
2.3.5.7 R̲e̲t̲u̲r̲n̲ ̲t̲o̲ ̲C̲u̲r̲r̲e̲n̲t̲ ̲M̲e̲n̲u̲
This causes the system to send to the VDU the menu
which led to the present format, or in case of ambiguity,
to the main menu.
2.3.6 S̲p̲e̲c̲i̲f̲i̲c̲ ̲C̲o̲m̲m̲a̲n̲d̲s̲
The commands which are specific to a format are described
with that format (see also appendix C). The commands
are always in the form of four letter mnemonic.
2.4 C̲U̲R̲S̲O̲R̲ ̲C̲O̲N̲T̲R̲O̲L̲
A cursor is available to help the user entering data
on the VDU in the unprotected fields. The cursor can
be moved to any position of the screen by the use of
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.
3̲ ̲ ̲S̲U̲P̲E̲R̲V̲I̲S̲O̲R̲Y̲ ̲F̲U̲N̲C̲T̲I̲O̲N̲S̲
3.1 I̲N̲T̲R̲O̲D̲U̲C̲T̲I̲O̲N̲
The supervisor transaction is described using an overall
dialogue diagram, a dialogue description and a set
of VDU layout forms. The validation checks on the supervisor
entered data and the subsequent error correction loops
are also described.
3.1.1 F̲o̲r̲m̲a̲t̲
Formats will enable the supervisor to perform the function
related to that format by either completing fields
within the format or entering required data in blank
fields or fields requiring up-date.
3.1.2 M̲e̲n̲u̲
In the case of a further sub-division of a function
selected, the supervisor will be presented with another
menu to allow him to select the required sub-function.
3.1.3 D̲i̲r̲e̲c̲t̲ ̲E̲x̲e̲c̲u̲t̲i̲o̲n̲
If the supervisor enters a command plus parameters
and PEC, if appropriate, the system will execute the
command without display of menus.
3.1.4 V̲a̲l̲i̲d̲a̲t̲i̲o̲n̲
Full semantic validation (as specified in each Format)
takes place only after data-entry is complete. 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.5 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) After semantic validation by the Host, the message
is re-presented at the supervisory VDU, with one
error number (denoting the first error in the line)
in the left-hand margin. The fields in error will
be highlighted. If the supervisor wants an explanation
of the error-number, he can issue the command which
results in an explicit error message being displayed
clear of the main format, in the "Response" line
at the top of the screen.
c) In some cases specific supervisor direction will
be given related to the semantic validation. This
will be displayed in full.
3.1.6 T̲r̲a̲n̲s̲a̲c̲t̲i̲o̲n̲ ̲I̲d̲e̲n̲t̲i̲t̲y̲
This field is common to all Commands and Transactions
except for Menus. It is output by the system to identify
the transaction as logged.
It states the Terminal identity, Serial number of the
transaction and Time stamp of the transaction.
The full description is given in the field/element
dictionary. (Ref. app. A.)
3.1.7 I̲t̲e̲m̲ ̲R̲e̲f̲e̲r̲e̲n̲c̲e̲ ̲I̲d̲e̲n̲t̲i̲t̲y̲
This field is common to retrievable items.
A full description is given in the field/element dictionary.
(Ref. app. A.)
Figure 3.2-1
3.2 S̲I̲G̲N̲ ̲O̲N̲ ̲(̲S̲I̲O̲N̲)̲
When a VDU is activated by turning the locking key
to ON, the system puts out a standard layout (fig.
3.2-2) on the VDU. If a sign-on is wanted, the user
enters the command SION in the system line (see sign-on
sequence fig. 3.2-1).
3.2.1 D̲a̲t̲a̲ ̲E̲n̲t̲r̲y̲
3.2.1.1 I̲d̲e̲n̲t̲i̲f̲i̲c̲a̲t̲i̲o̲n̲ ̲C̲o̲d̲e̲ ̲a̲n̲d̲ ̲P̲a̲s̲s̲w̲o̲r̲d̲
The system prompts the user for the identification
code and the password. The entry shall be in the system
line. On entry, the characters in the ID code and password
are not displayed.
3.2.2 V̲a̲l̲i̲d̲a̲t̲i̲o̲n̲
The system checks each for validity. If either one
or both are invalid, the system will respond by returning
an error message in the system line.
If the user fails to enter correct sign-on parameters
three times, the terminal shall be blocked, i.e. sign-on
shall not be possible.
For the two supervisor terminal positions blocking
shall, however, never take place.
For a description of the System reaction after successful
sign-on refer to section 3.3.
Figure 3.2-2
Figure 3.3-1
3.3 H̲I̲G̲H̲ ̲L̲E̲V̲E̲L̲ ̲M̲E̲N̲U̲
3.3.1 U̲s̲e̲r̲/̲T̲e̲r̲m̲i̲n̲a̲l̲
Upon completion of the Sign-On as described in section
3.2, the system will present a menu that reflects the
user's capabilities at the terminal. The System selects
the menu to be presented to the user according to fig.
3.3-1.
3.3.1.1 S̲u̲p̲e̲r̲v̲i̲s̲o̲r̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲y̲
If the user signed-on has Supervisor Capability alone,
the Supervisor Menu is displayed. However, if a Supervisor
is already assigned, the High Level Menu (Fig. 3.3-2)
is presented, allowing the user to assign as Supervisor,
signing the other Supervisor off.
3.3.1.2 M̲D̲C̲O̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲y̲
If the user signed-on has MDCO capability alone, the
MDCO Menu is presented. (Section 7).
3.3.1.3 M̲S̲O̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲y̲
If the user has MSO capability alone, then MSO Menu
is presented. (Section 8).
3.3.1.4 U̲s̲e̲r̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲y̲
If only User capability is allowed, then the User Main
Menu is displayed. (See ICD/0001).
3.3.1.5 S̲u̲p̲e̲r̲v̲i̲s̲o̲r̲/̲M̲D̲C̲O̲/̲M̲S̲O̲/̲U̲s̲e̲r̲ ̲C̲a̲p̲a̲b̲i̲l̲t̲i̲e̲s̲
The user signed-on can have any combination of the
capabilities above and the System gives the High Level
Menu with the common capabilities of the Terminal and
User Profile filled in.
3.3.1.6 S̲u̲p̲e̲r̲v̲i̲s̲o̲r̲ ̲T̲e̲r̲m̲i̲n̲a̲l̲
One and only one terminal can be enabled as the supervisor
terminal at any one time, although an alternate terminal
is assigned that capability. In order to change the
supervisor terminal, the supervisor issues the command
ASSG (Assign Command) in the system line from the alternate
terminal. It is now enabled with supervisor capability
while the other is automatically cancelled. A system
reply message is issued.
3.3.1.7 W̲a̲r̲n̲i̲n̲g̲ ̲M̲e̲s̲s̲a̲g̲e̲
If the user has none of the possible capabilities at
this terminal, the System will display an error message
for an appropriate period of time, after which the
terminal is returned to unattended mode.
Figure ???
Fig. 3.4-1
3.4 S̲U̲P̲E̲R̲V̲I̲S̲O̲R̲ ̲M̲E̲N̲U̲ ̲(̲S̲U̲P̲V̲)̲
The following three functions are available for the
Supervisor:
- System Control.
- Message Handling.
- Supervisor Engineering.
3.4.1 C̲o̲m̲m̲a̲n̲d̲ ̲E̲n̲t̲r̲i̲e̲s̲
Function is selected by entering a command from the
Supervisor Menu. (Fig. 3.4-2).
3.4.2 V̲a̲l̲i̲d̲a̲t̲i̲o̲n̲
On valid entry, the appropriate format for selected
function is displayed. If entry is invalid, then Supervisor
Menu is displayed with an error message in the system
response line.
Fig. 3.4-2
Fig. 4.1-1
4̲.̲ ̲ ̲S̲Y̲S̲T̲E̲M̲ ̲C̲O̲N̲T̲R̲O̲L̲
This section describes the System Control Functions
which are used by the Supervisor.
4.1 S̲Y̲S̲T̲E̲M̲ ̲C̲O̲N̲T̲R̲O̲L̲ ̲F̲U̲N̲C̲T̲I̲O̲N̲S̲ ̲(̲S̲Y̲S̲C̲)̲
These functions are selected from the System Control
Menu (Fig. 4.1-2) which contains the following 12 functions:
- Device Control.
- Addressing Scheme Control.
- User Profile Update.
- Queue Control.
- Supervisor Print Control.
- Disk Control.
- Command Control.
- Security Control.
- Global No. Series Control.
- System Parameter Control.
- System Information Extract.
- Table Print.
Fig. 4.1-2
4.1.1 S̲e̲q̲u̲e̲n̲c̲e̲
The sequence which is followed as a result of the selection
of a specific funtion from the System Control menu
is basically of two kinds.
As shown in fig. 4.1-3 and fig. 4.1-4 a command is
issued which causes the associated format to be displayed.
Data fields are entered/altered and the format is
entered which causes the update to be validated. On
successful validation the supervisor is prompted for
the confirmation code. This is to reassure that the
Supervisor intends the updating to be performed.
4.1.1.1 S̲e̲q̲u̲e̲n̲c̲e̲ ̲A̲ ̲-̲ ̲P̲a̲r̲a̲m̲e̲t̲e̲r̲ ̲E̲x̲a̲m̲i̲n̲e̲/̲U̲p̲d̲a̲t̲e̲
Formats requiring the examination and entry or change
of parameters will follow sequence A to accomplish
update of these formats. This is described in figure
4.1-3.
4.1.1.2 S̲e̲q̲u̲e̲n̲c̲e̲ ̲B̲ ̲-̲ ̲T̲a̲b̲l̲e̲ ̲E̲n̲t̲r̲y̲ ̲E̲x̲a̲m̲i̲n̲e̲/̲U̲p̲d̲a̲t̲e̲
Formats requiring the examination and entry or change
of data in tables will follow sequence B to accomplish
update of those formats. This sequence is described
in figure 4.1-4.
Fig. 4.1-3
Fig. 4.1-4
Fig. 4.2-1
4.2 D̲E̲V̲I̲C̲E̲ ̲C̲O̲N̲T̲R̲O̲L̲ ̲F̲U̲N̲C̲T̲I̲O̲N̲S̲ ̲(̲D̲E̲V̲C̲)̲
These functions are available from the Device Control
Menu (fig. 4.2-2) and consist of the following:
- Terminal Position Control.
- PT/OCR/SATP Control.
- Channel Control.
Fig. 4.2-2
4.2.1 T̲e̲r̲m̲i̲n̲a̲l̲ ̲P̲o̲s̲i̲t̲i̲o̲n̲ ̲C̲o̲n̲t̲r̲o̲l̲ ̲(̲T̲E̲P̲C̲ ̲"̲T̲D̲"̲)̲
This command makes available the Terminal Position
Control Format (fig. 4.2.1-1).
4.2.1.1 C̲o̲m̲m̲a̲n̲d̲ ̲E̲n̲t̲r̲y̲
If the Terminal Designator (TD) specified is known
to the system, the TEPC-format will contain the data
of the Terminal Profile. If the TD is unknown, a new
profile will be created and the TEPC-format will be
empty apart from the specified TD. If the maximum no.
of profiles is exceeded, the command will be rejected.
4.2.1.2 D̲a̲t̲a̲ ̲E̲n̲t̲r̲y̲
4.2.1.2.1 T̲e̲r̲m̲i̲n̲a̲l̲ ̲D̲e̲s̲i̲g̲n̲a̲t̲o̲r̲ ̲(̲M̲a̲n̲d̲a̲t̲o̲r̲y̲)̲
If this field is changed, the system checks that the
entered TD is unique among the Terminal and Device
designators. The change will be carried out for all
user profiles referencing this and for the (max. 5)
entries in the SCD-table.
4.2.1.2.2 B̲l̲o̲c̲k̲e̲d̲ ̲(̲M̲a̲n̲d̲a̲t̲o̲r̲y̲)̲
For terminal profiles without supervisor capability
this is the only field that can be changed while the
terminal is unblocked. All other changes require that
the terminal is blocked.
Changes will have immediate effect on operation of
the VDU. This is equivalent to automatic blocking in
case of security violation attempts.
If this field is changed to y, the system shall check
all data entry fields for validity and if no validity
check fails, unblock the terminal.
For terminal profiles with supervisor capability, the
system shall not accept blocking of the terminal.
The Supervisor shall be able to change the profile
of the terminal position at which he has currently
signed-on. Where the system shall not accept changes
to a field content, this is explicitly stated in the
field description.
4.2.1.2.3 M̲a̲x̲i̲m̲u̲m̲ ̲C̲l̲a̲s̲s̲i̲f̲i̲c̲a̲t̲i̲o̲n̲ ̲(̲M̲a̲n̲d̲a̲t̲o̲r̲y̲)̲
The system shall not allow this field to be changed
unless the release queue, delivery queue, and response
queue are empty and blocked and no messages are under
preparation at the terminal.
If any of the capabilities Supervisor, MSO or MDCO
are specified, this field must be Cosmic Top Secret.
If not an error message will be displayed.
4.2.1.2.4 S̲p̲e̲c̲i̲a̲l̲ ̲H̲a̲n̲d̲l̲i̲n̲g̲ ̲C̲a̲t̲e̲g̲o̲r̲y̲ ̲(̲O̲p̲t̲i̲o̲n̲a̲l̲)̲
The system shall not allow this field to be changed
unless the release queue, delivery queue, and response
queue are empty and blocked and no messages are under
preparation at the terminal.
In addition if any of the capabilities Supervisor,
MSO or MDCO are specified, the system will ignore the
Special Handling Category specified as all categories
must be allowed.
4.2.1.2.5 S̲u̲p̲e̲r̲v̲i̲s̲o̲r̲
This field contains Y, if the terminal has supervisor
capability else N.
4.2.1.2.6 M̲S̲O̲ ̲(̲O̲p̲t̲i̲o̲n̲a̲l̲)̲
The system shall check that at least one and maximum
four terminal profiles has MSO capability specified.
The system shall thus: reject removal of the MSO
capability, if this is the last profile for which it
is specified, reject the insertion of MSO capability
if four profiles with it already exist.
4.2.1.2.7 M̲D̲C̲O̲ ̲(̲O̲p̲t̲i̲o̲n̲a̲l̲)̲
As for MSO.
4.2.1.2.8 P̲r̲e̲p̲a̲r̲a̲t̲i̲o̲n̲ ̲(̲O̲p̲t̲i̲o̲n̲a̲l̲)̲
The system shall not allow this field to be changed
unless the release queue, delivery queue, and response
queue are empty and blocked and no messages are under
preparation at the terminal.
4.2.1.2.9 R̲e̲c̲e̲p̲t̲i̲o̲n̲ ̲(̲O̲p̲t̲i̲o̲n̲a̲l̲)̲
Same as section 4.2.1.2.8 above.
4.2.1.2.10 R̲e̲l̲e̲a̲s̲e̲ ̲(̲O̲p̲t̲i̲o̲n̲a̲l̲)̲
Same conditions as in 4.2.1.2.8 above are checked,
Furthermore, if this capability is removed, the system
will check that no User Profile contains reference
to this TD as associated release position. The removal
of release capability will only be accepted if no such
reference is found.
4.2.1.2.11 U̲s̲e̲r̲ ̲I̲D̲ ̲(̲O̲p̲t̲i̲o̲n̲a̲l̲)̲
The system shall check: that a user profile exists
for the entered User ID, that no other Terminal profile
contains this User ID, that a User ID for which the
corresponding user profile contains supervisor capability
is not specified in a terminal profile without supervisor
capability.
4.2.1.2.12 S̲C̲D̲s̲ ̲(̲O̲p̲t̲i̲o̲n̲a̲l̲)̲
SCDs entered here will only be syntax checked as it
shall be possible to enter SCDs for the terminal before
entry in the SCD table.
(When SCDs are entered in the SCD-table, the system
will check against the Terminal Profile).
If one or more of the capabilities Preparation, Reception
or Release are set, entry of at least one SCD is mandatory.
If a SCD is changed (or removed), the system shall
check that the original SCD is not contained in the
SCD-table.
4.2.1.2.13 V̲D̲U̲ ̲P̲o̲r̲t̲ ̲(̲O̲p̲t̲i̲o̲n̲a̲l̲)̲
This field is optional but as it is required that all
Terminal Profiles are connected to a VDU, this field
must be entered before the terminal can be unblocked.
If the VDU PORT is changed, the system will check that
no other Terminal Profile is connected to the PORT
ID specified. The system also checks that the PORT
ID is of correct type (VDU).
For a terminal profile with supervisor capability,
the system shall not accept any change to this field.
It shall be checked by the system that the entered
DD does not identify any of the printers defined in
the Supervisor Print Control format.
4.2.1.2.14 S̲h̲a̲r̲e̲d̲ ̲P̲r̲i̲n̲t̲e̲r̲ ̲D̲e̲v̲i̲c̲e̲ ̲D̲e̲s̲i̲g̲n̲a̲t̲o̲r̲ ̲(̲O̲p̲t̲i̲o̲n̲a̲l̲)̲
The system checks that the designator specified is
of correct type (printer). There are no requirements
to the state of the printer when this change is performed.
If any of the capabilities MDCO, MSO, Preparation,
Reception or release are specified, the system shall
check that a shared printer is defined.
4.2.1.2.15 D̲e̲l̲e̲t̲e̲ ̲T̲h̲i̲s̲ ̲T̲e̲r̲m̲i̲n̲a̲l̲ ̲P̲r̲o̲f̲i̲l̲e̲ ̲(̲O̲p̲t̲i̲o̲n̲a̲l̲)̲
The effect of this is that the Terminal Profile is
removed from the system and thus the implications will
be a combination of the effects specified in this section.
Deletion will be rejected: if the TD is referenced
in the SCD-Table or in a User Profile, or supervisor
capability is defined.
4.2.1.2.16 N̲e̲x̲t̲ ̲T̲e̲r̲m̲i̲n̲a̲l̲ ̲P̲r̲o̲f̲i̲l̲e̲ ̲(̲O̲p̲t̲i̲o̲n̲a̲l̲)̲
This will give the "next" Terminal Profile (next by
design).
4.2.1.2.17 N̲e̲x̲t̲ ̲T̲e̲r̲m̲i̲n̲a̲l̲ ̲D̲e̲s̲i̲g̲n̲a̲t̲o̲r̲ ̲(̲O̲p̲t̲i̲o̲n̲a̲l̲)̲
If a TD is entered in this data-entry field, the system
shall react as if the command TEPC "TD" has been entered.
4.2.1.3 V̲a̲l̲i̲d̲a̲t̲i̲o̲n̲
The Supervisor depresses the ENTER key. The System
shall validate all data entries, except Next Terminal
Designator as described above and generate error codes
for invalid entries.
The entry Next Terminal Designator shall not be validated
until after the supervisor has been prompted for and
has entered the confirmation code. Validation for
this field shall be as described in section 4.2.1.1.
Fig. 4.2.1-1
4.2.2 P̲T̲/̲O̲C̲R̲/̲S̲A̲T̲P̲ ̲C̲o̲n̲t̲r̲o̲l̲ ̲(̲P̲O̲S̲C̲ ̲"̲D̲D̲"̲,̲ ̲"̲D̲E̲V̲I̲C̲E̲ ̲T̲Y̲P̲E̲"̲)̲
This command makes available the PT/OCR/SATP Control
Format (fig. 4.2.2-1).
4.2.2.1 C̲o̲m̲m̲a̲n̲d̲ ̲E̲n̲t̲r̲y̲
If the Device Designator (DD) specified is known to
the system, the POSC-format will contain the data of
the Device Profile. If the DD is unknown, a new profile
will be created and the POSC-format will be empty apart
from the specified DD, and the connected field which
is preset to N.
The device type shall be entered as a command parameter,
i.e. POSC "DD", "device type".
The system shall then check that the maximum number
of device profiles for the specified device type is
not exceeded (command rejected).
4.2.2.2 D̲a̲t̲a̲ ̲E̲n̲t̲r̲y̲
4.2.2.2.1 D̲e̲v̲i̲c̲e̲ ̲D̲e̲s̲i̲g̲n̲a̲t̲o̲r̲ ̲(̲M̲a̲n̲d̲a̲t̲o̲r̲y̲)̲
The system shall check that the entered DD is unique
among the Device and Terminal Designators and carry
out the change where appropriate in the SCD-Table,
the Terminal Profiles, special Distribution Parameters
and Supervisor Print Control.
4.2.2.2.2 C̲o̲n̲n̲e̲c̲t̲e̲d̲ ̲(̲M̲a̲n̲d̲a̲t̲o̲r̲y̲)̲
Changes will have immediate effect on the operation
of the device.
This is the only field that can be changed while the
device is connected.
If the connect field is changed to Y, the system shall
check all data-entry fields for validity and if no
validity check fails connect the device.
4.2.2.2.3 D̲e̲v̲i̲c̲e̲ ̲T̲y̲p̲e̲
This field contains the type of the device and can
be one of the following:
1. MSP
2. LSP
3. PTR
4. PTP
5. OCR
This field shall be derived by the system from the
Device Port data entry field.
4.2.2.2.4 M̲a̲x̲i̲m̲u̲m̲ ̲C̲l̲a̲s̲s̲i̲f̲i̲c̲a̲t̲i̲o̲n̲ ̲(̲M̲a̲n̲d̲a̲t̲o̲r̲y̲)̲
The system shall not allow this field to be changed
unless the device queue is empty and blocked.
The system shall not accept changes to this field for
devices referenced in Special Distribution Parameters.
4.2.2.2.5 P̲r̲i̲n̲t̲e̲r̲/̲P̲a̲p̲e̲r̲t̲a̲p̲e̲ ̲R̲e̲a̲d̲e̲r̲ ̲(̲O̲p̲t̲i̲o̲n̲a̲l̲)̲
This field is only applicable if device type is LSP.
The system shall only accept a change from Printer
to PTR, if the printer queue is empty and blocked.
4.2.2.2.6 N̲u̲m̲b̲e̲r̲ ̲o̲f̲ ̲P̲l̲y̲s̲ ̲(̲M̲a̲n̲d̲a̲t̲o̲r̲y̲)̲
In this field, the number of paper plys applicable
to the printer is entered.
4.2.2.2.7 D̲e̲v̲i̲c̲e̲ ̲P̲o̲r̲t̲ ̲(̲O̲p̲t̲i̲o̲n̲a̲l̲)̲
This field is optional but as it is required that all
Device Profiles are connected to a Device, this field
must be entered before the Device can be connected.
If the Device Port is changed, the system will check
that no other Device Profile is connected to the PORT
ID specified. The system also checks that the PORT
ID is of correct type i.e. refers to a device of identical
type.
4.2.2.2.8 D̲e̲l̲e̲t̲e̲ ̲T̲h̲i̲s̲ ̲D̲e̲v̲i̲c̲e̲ ̲P̲r̲o̲f̲i̲l̲e̲ ̲(̲O̲p̲t̲i̲o̲n̲a̲l̲)̲
The effect of this is that the Device Profile is removed
from the system and thus the implications are a combination
of the effects specified in this section. Deletion
will be rejected if the DD is referenced in the SCD-table,
Terminal Profiles, Special Distribution Parameters
and Supervisor Print Control.
4.2.2.2.9 N̲e̲x̲t̲ ̲D̲e̲v̲i̲c̲e̲ ̲P̲r̲o̲f̲i̲l̲e̲ ̲(̲O̲p̲t̲i̲o̲n̲a̲l̲)̲
This will give the "next" Device Profile (next by design).
4.2.2.2.10 N̲e̲x̲t̲ ̲D̲e̲v̲i̲c̲e̲ ̲D̲e̲s̲i̲g̲n̲a̲t̲o̲r̲ ̲(̲O̲p̲t̲i̲o̲n̲a̲l̲)̲
If a DD is entered in this data-entry field, the System
shall react as if the command POSC "DD" has been entered.
4.2.2.3 V̲a̲l̲i̲d̲a̲t̲i̲o̲n̲
The supervisor depresses the ENTER key. The System
shall validate all data entries, except Next Device
Designator, as described above and generate error codes
for invalid entries.
The entry Next Device Designator shall not be validated
until after the Supervisor has been prompted for and
has entered the confirmation code. Validation for
this field shall be as described in section 4.2.2.1.
Fig. 4.2.2-1
4.2.3 C̲h̲a̲n̲n̲e̲l̲ ̲C̲o̲n̲t̲r̲o̲l̲ ̲(̲C̲H̲A̲C̲ ̲"̲C̲D̲"̲)̲
This command makes available the Channel Control Format
(fig. 4.2.3-1).
4.2.3.1 C̲o̲m̲m̲a̲n̲d̲ ̲E̲n̲t̲r̲y̲
Both an Incoming and Outgoing Channel Designator (CD)
identify a Channel Profile and only one, the Incoming
Channel Designator, needs to be specified in order
to obtain the Channel Profile.
If the Incoming Channel Designator specified is known
to the system, the CHAC-format will contain the data
of the Channel Profile.
If the Incoming Channel Designator is unknown to the
System, a new Channel Profile will be created and the
CHAC-format will be empty apart from the specified
CD, which shall be inserted as the Incoming Channel
designator, the Connect Channel data-entry field which
shall be preset to N, and the Open Channel data entry
field which shall be preset to N.
If the maximum number of profiles is exceeded, the
command will be rejected.
4.2.3.2 D̲a̲t̲a̲ ̲E̲n̲t̲r̲y̲
4.2.3.2.1 I̲n̲c̲o̲m̲i̲n̲g̲ ̲C̲h̲a̲n̲n̲e̲l̲ ̲D̲e̲s̲i̲g̲n̲a̲t̲o̲r̲ ̲(̲M̲a̲n̲d̲a̲t̲o̲r̲y̲)̲
If this field is changed, the system shall check that
the designator is unique among the Incoming Channel
Designators.
4.2.3.2.2 O̲u̲t̲g̲o̲i̲n̲g̲ ̲C̲h̲a̲n̲n̲e̲l̲ ̲D̲e̲s̲i̲g̲n̲a̲t̲o̲r̲ ̲(̲M̲a̲n̲d̲a̲t̲o̲r̲y̲)̲
If this field is changed, the system shall check that
the designator is unique among the outgoing Channel
Designators.
4.2.3.2.3 C̲o̲n̲n̲e̲c̲t̲ ̲C̲h̲a̲n̲n̲e̲l̲ ̲(̲M̲a̲n̲d̲a̲t̲o̲r̲y̲)̲
If the Connect Channel field contains Y, the system
shall not accept any changes in the data-entry fields
except for: Connect Channel field, Open Channel for
Incoming Traffic field.
If the Connect Channel field is changed to N, the system
shall: attempt to send a Close-Channel Abbreviated
Service Message if the channel is open, i.e. close
down the channel.
If the Connect Channel field is changed to Y, the system
shall check all data-entry fields for validity, and
if no validity check fails, make the channel ready
for traffic.
4.2.3.2.4 C̲h̲a̲n̲n̲e̲l̲ ̲T̲y̲p̲e̲
This field corresponds to the circuit type and is filled
in by the system. For a new profile, this field is
empty.
The possible channel types are as follows:
- NICS/TARE
- TRC/PTOP
- SCARS
- ACCIS
4.2.3.2.5 M̲a̲x̲i̲m̲u̲m̲ ̲C̲l̲a̲s̲s̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
In this field the system enters the classification
of the channel in accordance with the associated circuit.
4.2.3.2.6 T̲o̲ ̲R̲I̲ ̲(̲M̲a̲n̲d̲a̲t̲o̲r̲y̲)̲
To RI for use in automatically generated Abbreviated
Service Messages. The system shall check that the
RI is contained in the External RI table.
4.2.3.2.7 O̲p̲e̲n̲ ̲C̲h̲a̲n̲n̲e̲l̲ ̲f̲o̲r̲ ̲I̲n̲c̲o̲m̲i̲n̲g̲ ̲T̲r̲a̲f̲f̲i̲c̲ ̲(̲M̲a̲n̲d̲a̲t̲o̲r̲y̲)̲
If "yes" is specified, this initiates the "Incoming
Channel Open Procedure" (Ref. CPS/ICD/004)
If "no" is specified, this initiates the "Incoming
Channel Close Procedure" (Ref. CPS/ICD/004).
This field is not applicable for SCARS/CCIS channels
and will be ignored if entered.
4.2.3.2.8 C̲h̲a̲n̲n̲e̲l̲ ̲O̲p̲e̲n̲ ̲f̲o̲r̲ ̲O̲u̲t̲g̲o̲i̲n̲g̲ ̲T̲r̲a̲f̲f̲i̲c̲
"Yes" in this field informs the Supervisor that the
"Outgoing Channel" is open (as a result of a request
from "the other end").
"No" in this field informs the Supervisor that the
"Outgoing Channel" is closed (as a result of a request
from "the other end").
This field will be empty for SCARS/ACCIS channels.
4.2.3.2.9 C̲i̲r̲c̲u̲i̲t̲ ̲(̲M̲a̲n̲d̲a̲t̲o̲r̲y̲)̲
This specifies the circuit to which the channel "belongs".
It cannot be changed for an existing Channel Profile.
The Circuit Type defines the Channel Type.
4.2.3.2.10 C̲h̲a̲n̲n̲e̲l̲ ̲P̲o̲r̲t̲ ̲(̲O̲p̲t̲i̲o̲n̲a̲l̲)̲
This field is optional but as all Channel Profiles
must be connected to a Port, the field must be entered
before the channel can be connected.
If the Channel Port is changed, the system will check
that no other Channel Profile is connected to the PORT
ID specified. The System also checks that the PORT
ID is of correct type (corresponds to the CHANNEL TYPE).
4.2.3.2.11 D̲e̲l̲e̲t̲e̲ ̲T̲h̲i̲s̲ ̲C̲h̲a̲n̲n̲e̲l̲ ̲P̲r̲o̲f̲i̲l̲e̲ ̲(̲O̲p̲t̲i̲o̲n̲a̲l̲)̲
The effect of this is to remove the profile from the
system.
4.2.3.2.12 N̲e̲x̲t̲ ̲C̲h̲a̲n̲n̲e̲l̲ ̲P̲r̲o̲f̲i̲l̲e̲ ̲(̲O̲p̲t̲i̲o̲n̲a̲l̲)̲
This will give the "next" Channel Profile (next by
design).
4.2.3.2.13 N̲e̲x̲t̲ ̲C̲h̲a̲n̲n̲e̲l̲ ̲D̲e̲s̲i̲g̲n̲a̲t̲o̲r̲ ̲(̲O̲p̲t̲i̲o̲n̲a̲l̲)̲
If a CD is entered in this data-entry field, the system
shall react as if the command CHAC "CD" has been entered.
4.2.3.3 V̲a̲l̲i̲d̲a̲t̲i̲o̲n̲
The supervisor depresses the ENTER key. The System
shall validate all data entries, except Next Channel
Designator, as described above and generate error codes
for invalid entries.
The entry Next Channel Designator shall not be validated
until after the supervisor has been prompted for and
has entered the confirmation code. Validation for
this field shall be as described in section 4.2.3.1.
Fig. 4.2.3-1
Fig. 4.3-1
4.3 A̲D̲D̲R̲E̲S̲S̲I̲N̲G̲ ̲S̲C̲H̲E̲M̲E̲ ̲C̲O̲N̲T̲R̲O̲L̲ ̲F̲U̲N̲C̲T̲I̲O̲N̲S̲
This command gives the Supervisor on-line control over
the Addressing Scheme for incoming and outgoing traffic.
The functions are selected from the Addressing Scheme
Menu (Fig. 4.3-2) and are as follows:
- SIC-Table Update
- SDL-Table Update
- SCD-Table Update
- AIG-Table Update
- Global PLA-Table Update
- RI-Table Update
- Circuit-Table Update
- Display Table Update
- Operating Signal Table Update
- Local PLA-Table Update
- Local RI-Table Update
- Reorganize All Tables
- Abandon Reorganisation.
Fig. 4.3-2
4.3.1 S̲I̲C̲-̲T̲a̲b̲l̲e̲ ̲U̲p̲d̲a̲t̲e̲ ̲(̲S̲I̲C̲T̲ ̲"̲S̲I̲C̲"̲)̲
This command makes available the SIC-Table Update Format
(fig. 4.3.1-1).
4.3.1.1 C̲o̲m̲m̲a̲n̲d̲ ̲E̲n̲t̲r̲y̲
If the SIC specified is known to the system, the SICT-format
will contain data of the table entry. If the SIC is
unknown to the system, a new entry in the table will
be created, provided that the table is not full. The
format displayed will be empty, apart from the specified
SIC.
4.3.1.2 D̲a̲t̲a̲ ̲E̲n̲t̲r̲y̲
4.3.1.2.1 S̲I̲C̲ ̲(̲M̲a̲n̲d̲a̲t̲o̲r̲y̲)̲
The system shall check that the entered SIC is unique.
Data in the field shall be left aligned.
The System shall furthermore check that at least one
SDL is defined for the entry.
4.3.1.2.2 N̲o̲r̲m̲a̲l̲ ̲S̲D̲L̲ ̲(̲O̲p̲t̲i̲o̲n̲a̲l̲)̲
The system shall check that the entered SDL identifies
a SDL-Table entry which is non-empty.
4.3.1.2.3 E̲x̲e̲r̲c̲i̲s̲e̲ ̲S̲D̲L̲ ̲(̲O̲p̲t̲i̲o̲n̲a̲l̲)̲
The system shall check that the entered SDL identifies
a SDL-Table entry which is non-empty.
4.3.1.2.4 C̲r̲i̲s̲i̲s̲ ̲S̲D̲L̲ ̲(̲O̲p̲t̲i̲o̲n̲a̲l̲)̲
The system shall check that the entered SDL identifies
a non-empty SDL-Table entry.
4.3.1.2.5 D̲e̲l̲e̲t̲e̲ ̲T̲h̲i̲s̲ ̲S̲I̲C̲ ̲T̲a̲b̲l̲e̲ ̲E̲n̲t̲r̲y̲ ̲(̲O̲p̲t̲i̲o̲n̲a̲l̲)̲
This removes the entry from the table.
4.3.1.2.6 N̲e̲x̲t̲ ̲S̲I̲C̲-̲T̲a̲b̲l̲e̲ ̲E̲n̲t̲r̲y̲ ̲(̲O̲p̲t̲i̲o̲n̲a̲l̲)̲
This gives the "next" SIC-Table Entry (next by design).
4.3.1.2.7 N̲e̲x̲t̲ ̲S̲I̲C̲ ̲(̲O̲p̲t̲i̲o̲n̲a̲l̲)̲
If a SIC is entered in this data-entry field, the system
shall react as if the command SICT "SIC" has been entered.
4.3.1.3 V̲a̲l̲i̲d̲a̲t̲i̲o̲n̲
The supervisor depresses the ENTER key. The System
shall validate all data entries, except Next SIC, as
described above and generate error code for invalid
entries.
The entry Next SIC shall not be validated until after
the Supervisor has been prompted for and has entered
the confirmation code. Validation for this field shall
be as described in section 4.3.1.1.
Fig. 4.3.1-1
4.3.2 S̲D̲L̲-̲T̲a̲b̲l̲e̲ ̲U̲p̲d̲a̲t̲e̲ ̲(̲S̲D̲L̲T̲ ̲"̲S̲D̲L̲"̲)̲
This command makes available the SDL-Table Update Format
(fig. 4.3.2-1).
4.3.2.1 C̲o̲m̲m̲a̲n̲d̲ ̲E̲n̲t̲r̲y̲
The system shall check that the specified SDL is within
the range 1-800, in which case the data of the table
entry shall be displayed.
4.3.2.2 D̲a̲t̲a̲ ̲E̲n̲t̲r̲y̲
4.3.2.2.1 S̲D̲L̲
This field contains a number in the range 1 - 800 of
the entry in the SDL table. The field cannot be changed.
4.3.2.2.2 A̲c̲t̲i̲o̲n̲ ̲S̲C̲D̲s̲ ̲(̲O̲p̲t̲i̲o̲n̲a̲l̲)̲
The system shall check that SCDs entered are contained
in the SCD-Table.
4.3.2.2.3 I̲n̲f̲o̲ ̲S̲C̲D̲s̲ ̲(̲O̲p̲t̲i̲o̲n̲a̲l̲)̲
The system shall check that the SCDs entered are contained
in the SCD Table.
4.3.2.2.4 D̲e̲l̲e̲t̲e̲ ̲T̲h̲i̲s̲ ̲S̲D̲L̲-̲T̲a̲b̲l̲e̲ ̲E̲n̲t̲r̲y̲ ̲(̲O̲p̲t̲i̲o̲n̲a̲l̲)̲
This removes the entry from the table.
4.3.2.2.5 R̲e̲m̲o̲v̲e̲ ̲A̲l̲l̲ ̲R̲e̲f̲e̲r̲e̲n̲c̲e̲s̲ ̲t̲o̲ ̲t̲h̲i̲s̲ ̲S̲D̲L̲ ̲f̲r̲o̲m̲ ̲S̲I̲C̲-̲T̲a̲b̲l̲e̲
̲(̲O̲p̲t̲i̲o̲n̲a̲l̲)̲
The system scans the entire SIC-Table and removes all
references to the SDL.
4.3.2.2.6 N̲e̲x̲t̲ ̲S̲D̲L̲-̲T̲a̲b̲l̲e̲ ̲E̲n̲t̲r̲y̲ ̲(̲O̲p̲t̲i̲o̲n̲a̲l̲)̲
This gives "next" SDL-Table Entry (next by design).
4.3.2.2.7 N̲e̲x̲t̲ ̲S̲D̲L̲ ̲(̲O̲p̲t̲i̲o̲n̲a̲l̲)̲
If a SDL is entered in this data-entry field, the system
shall react as if the command SDCT "SDL" has been entered.
4.3.2.3 V̲a̲l̲i̲d̲a̲t̲i̲o̲n̲
The Supervisor depresses the ENTER key. The System
shall validate all data entries, except Next SDL, as
described above and generate error code for invalid
entries.
The entry Next SDL shall not be validated until after
the supervisor has been prompted for and has entered
the confirmation code. Validation for this field shall
be as described in section 4.3.2.1.
Fig. 4.3.2-1
4.3.3 S̲C̲D̲-̲T̲a̲b̲l̲e̲ ̲U̲p̲d̲a̲t̲e̲ ̲(̲S̲C̲D̲T̲ ̲"̲S̲C̲D̲"̲)̲
This command makes available the SCD-Table Update Format
(fig. 4.3.3-1).
4.3.3.1 C̲o̲m̲m̲a̲n̲d̲ ̲E̲n̲t̲r̲y̲
If the specified SCD is known to the system, the SCDT-format
will contain data of the table entry. If the SCD is
unknown to the system, a new table entry will be created,
provided the table is not full. The format displayed
will be empty apart from the specified SCD.
4.3.3.2 D̲a̲t̲a̲ ̲E̲n̲t̲r̲y̲
4.3.3.2.1 S̲C̲D̲ ̲(̲M̲a̲n̲d̲a̲t̲o̲r̲y̲)̲
The system shall check that the entered SCD is unique,
and if the type is VDU, check that the SCD is contained
in the Terminal Profile.
If the SCD is changed, the system shall:
- check that the SCD is unique.
- if the type is VDU and the designator is unchanged,
check that the terminal is blocked. If not, the
change shall be rejected, otherwise the system
shall carry out the change in the Terminal Profile.
- if the change is accepted, carry out the change
in the SDL-Table.
4.3.3.2.2 D̲e̲v̲i̲c̲e̲/̲T̲e̲r̲m̲i̲n̲a̲l̲ ̲T̲y̲p̲e̲ ̲(̲M̲a̲n̲d̲a̲t̲o̲r̲y̲)̲
The system shall check that the type entered is either
VDU, MSP or LSP.
4.3.3.2.3 D̲e̲s̲i̲g̲n̲a̲t̲o̲r̲ ̲(̲M̲a̲n̲d̲a̲t̲o̲r̲y̲)̲
The system shall check that the entered designator
refers to a profile of correct type (i.e. VDU, MSP,
LSP) and if VDU that the profile contains the specified
SCD.
4.3.3.2.4 N̲o̲.̲ ̲o̲f̲ ̲C̲o̲p̲i̲e̲s̲ ̲(̲M̲a̲n̲d̲a̲t̲o̲r̲y̲)̲
The system checks that the field contents are in the
range 1 - 99.
4.3.3.2.5 D̲e̲l̲e̲t̲e̲ ̲T̲h̲i̲s̲ ̲S̲C̲D̲-̲T̲a̲b̲l̲e̲ ̲E̲n̲t̲r̲y̲ ̲(̲O̲p̲t̲i̲o̲n̲a̲l̲)̲
This removes the entry from the table.
4.3.3.2.6 R̲e̲m̲o̲v̲e̲ ̲A̲l̲l̲ ̲R̲e̲f̲e̲r̲e̲n̲c̲e̲s̲ ̲t̲o̲ ̲t̲h̲i̲s̲ ̲S̲C̲D̲ ̲f̲r̲o̲m̲ ̲S̲D̲L̲-̲T̲a̲b̲l̲e̲s̲
̲(̲O̲p̲t̲i̲o̲n̲a̲l̲)̲
The system scans the SDL-TABLE and removes all references
to this SCD.
4.3.3.2.7 N̲e̲x̲t̲ ̲S̲D̲L̲-̲T̲a̲b̲l̲e̲ ̲E̲n̲t̲r̲y̲ ̲(̲O̲p̲t̲i̲o̲n̲a̲l̲)̲
This gives the "next" SCD-Table entry (next by design).
4.3.3.2.8 N̲e̲x̲t̲ ̲S̲C̲D̲ ̲(̲O̲p̲t̲i̲o̲n̲a̲l̲)̲
If a SCD is entered in this data-entry field, the system
shall react as if the command SCDT "SCD" has been entered.
4.3.3.3 V̲a̲l̲i̲d̲a̲t̲i̲o̲n̲
The supervisor depresses the ENTER key. The system
shall validate all data entries, except Next SCD, as
described above and generate error codes for invalid
entries.
The entry Next SCD shall not be validated until after
the supervisor has been prompted for and has entered
the confirmation code. Validation for this field shall
be as described in section 4.3.3.1.
Fig. 4.3.3-1
4.3.4 A̲I̲G̲-̲T̲a̲b̲l̲e̲ ̲U̲p̲d̲a̲t̲e̲ ̲(̲A̲I̲G̲T̲ ̲"̲A̲I̲G̲"̲)̲
This command makes available the AIG-Table Update Format
(fig. 4.3.4-1).
4.3.4.1 C̲o̲m̲m̲a̲n̲d̲ ̲E̲n̲t̲r̲y̲
If the specified AIG is known to the system, the AIGT-format
will contain data of the table entry. If the AIG is
unknown to the system, a new table entry will be created,
provided that the table is not full. The format displayed
will be empty apart from the specified AIG.
4.3.4.2 D̲a̲t̲a̲ ̲E̲n̲t̲r̲y̲
4.3.4.2.1 A̲I̲G̲ ̲(̲M̲a̲n̲d̲a̲t̲o̲r̲y̲)̲
If this field is changed the system will check that
the AIG does not already exist in the table.
4.3.4.2.2 A̲G̲ ̲(̲O̲p̲t̲i̲o̲n̲a̲l̲)̲
If this field is entered or changed, the system will
check that the AG does not already exist.
4.3.4.2.3 P̲L̲A̲R̲E̲F̲ ̲&̲ ̲P̲L̲A̲ ̲(̲O̲p̲t̲i̲o̲n̲a̲l̲)̲
The system displays up to 15 lines for an existing
AIG. For a new AIG, one empty line is displayed. In
both cases, the insert line function key can be used
to get empty lines for entry of PLAREF. PLAREFs entered
are checked against the PLA-Tables. It is also checked
that the maximum number of 200 PLAs per AIG is not
exceeded. The system will sort PLAREFs in ascending
order per AIG in the table. PLAREFs can be removed
by being blanked out.
The system shall check that at least one PLAREF is
entered for a new AIG.
4.3.4.2.4 C̲o̲n̲t̲i̲n̲u̲a̲t̲i̲o̲n̲ ̲(̲O̲p̲t̲i̲o̲n̲a̲l̲)̲
This gives the next max. 15 PLAREF/PLA lines for this
AIG.
4.3.4.2.5 D̲e̲l̲e̲t̲e̲ ̲T̲h̲i̲s̲ ̲A̲I̲G̲ ̲(̲O̲p̲t̲i̲o̲n̲a̲l̲)̲
This removes the entry from the table.
4.3.4.2.6 N̲e̲x̲t̲ ̲A̲I̲G̲-̲T̲a̲b̲l̲e̲ ̲E̲n̲t̲r̲y̲ ̲(̲O̲p̲t̲i̲o̲n̲a̲l̲)̲
This gives the next AIG-Table Entry (next by design).
4.3.4.2.7 N̲e̲x̲t̲ ̲A̲I̲G̲ ̲(̲O̲p̲t̲i̲o̲n̲a̲l̲)̲
If an AIG is entered in this data-entry field, the
system shall react as if the command AIGT "AIG" has
been entered.
4.3.4.3 V̲a̲l̲i̲d̲a̲t̲i̲o̲n̲
The supervisor depresses the ENTER key. The System
shall validate all data entries, except Next AIG as
described above and generate error codes for invalid
entries.
The entry Next AIG shall not be validated until after
the supervisor has been prompted for and has entered
the confirmation code. Validation for this field shall
be as described in section 4.3.4.1.
Fig. 4.3.4-1
4.3.5 G̲l̲o̲b̲a̲l̲ ̲P̲L̲A̲-̲T̲a̲b̲l̲e̲ ̲U̲p̲d̲a̲t̲e̲ ̲(̲G̲P̲L̲T̲ ̲"̲P̲L̲A̲R̲E̲F̲"̲)̲
This command makes available the GLOBAL PLA-Table Update
Format (fig. 4.3.5-1).
4.3.5.1 C̲o̲m̲m̲a̲n̲d̲ ̲E̲n̲t̲r̲y̲
If the PLAREF specified is known to the system, the
GPLT-format will contain data of the table entry. If
the PLAREF is unknown, a new entry will be created,
provided that the table is not full. The format displayed
will be empty apart from the specified "PLAREF".
4.3.5.2 D̲a̲t̲a̲ ̲E̲n̲t̲r̲y̲
4.3.5.2.1 P̲L̲A̲R̲E̲F̲ ̲(̲M̲a̲n̲d̲a̲t̲o̲r̲y̲)̲
If this field is changed, the system will check that
the PLAREF does not already exist in neither of the
PLA tables. The system will scan the entire AIG table
carrying out the change.
4.3.5.2.2 P̲L̲A̲ ̲(̲M̲a̲n̲d̲a̲t̲o̲r̲y̲)̲
If this field is changed, the system will check that
the PLA does not already exist in neither of the PLA-tables.
4.3.5.2.3 R̲I̲s̲ ̲(̲O̲p̲t̲i̲o̲n̲a̲l̲)̲
The system shall check that at least one RI is entered,
that the RIs specified are contained in the RI-table.
Furthermore, the system shall check:
- that the first RI identifies a circuit of type
NICS/TARE, SCARS or ACCIS.
- that only one RI is entered if the type is SCARS
or ACCIS.
- that the subsequent RIs entered identify circuits
of type P-TO-P/TRC.
4.3.5.2.4 C̲i̲r̲c̲u̲i̲t̲s̲
These fields cannot be changed as they correspond to
the RIs in the RI-Table. For an existing PLAREF, the
fields contain circuit nos. For a new PLAREF, the system
obtains them from the RI-Table and enters them into
the GLOBAL PLA-Table.
4.3.5.2.5 C̲l̲a̲s̲s̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
These fields cannot be changed as they correspond to
the classifications in the RI-table. For an existing
PLAREF, the fields contain classification. For a new
PLAREF, the system obtains them from the RI-table and
enters then into the GLOBAL PLA-Table.
4.3.5.2.6 D̲e̲l̲e̲t̲e̲ ̲T̲h̲i̲s̲ ̲P̲L̲A̲R̲E̲F̲ ̲(̲O̲p̲t̲i̲o̲n̲a̲l̲)̲
This removes the entry from the table.
4.3.5.2.7 R̲e̲m̲o̲v̲e̲ ̲A̲l̲l̲ ̲R̲e̲f̲e̲r̲e̲n̲c̲e̲s̲ ̲t̲o̲ ̲T̲h̲i̲s̲ ̲P̲L̲A̲R̲E̲F̲ ̲f̲r̲o̲m̲ ̲A̲I̲G̲ ̲T̲a̲b̲l̲e̲
̲(̲O̲p̲t̲i̲o̲n̲a̲l̲)̲
The system scans the AIG-Table and removes all references
to the PLAREF.
4.3.5.2.8 N̲e̲x̲t̲ ̲G̲l̲o̲b̲a̲l̲ ̲P̲L̲A̲-̲T̲a̲b̲l̲e̲ ̲E̲n̲t̲r̲y̲ ̲(̲O̲p̲t̲i̲o̲n̲a̲l̲)̲
This gives the "next" Global PLA-Table Entry (next
by design).
4.3.5.2.9 N̲e̲x̲t̲ ̲P̲L̲A̲R̲E̲F̲ ̲(̲O̲p̲t̲i̲o̲n̲a̲l̲)̲
If a PLAREF is entered in this data-entry field, the
system shall react as if the command GPLT "PLAREF"
has been entered.
4.3.5.3 V̲a̲l̲i̲d̲a̲t̲i̲o̲n̲
The supervisor depresses the ENTER key. The system
shall validate all data entries, except Next PLAREF
as described above and generate error codes for invalid
entries.
The entry NEXT PLAREF shall not be validated until
after the supervisor has been prompted for and has
entered the confirmation code. Validation for this
field shall be as described in section 4.3.5.1.
Fig. 4.3.5-1
4.3.6 R̲I̲-̲T̲a̲b̲l̲e̲ ̲U̲p̲d̲a̲t̲e̲ ̲(̲R̲I̲T̲A̲ ̲"̲R̲I̲"̲)̲
This command makes available the RI-Table Update Format
(fig. 4.3.6-1).
4.3.6.1 C̲o̲m̲m̲a̲n̲d̲ ̲E̲n̲t̲r̲y̲
If the specified RI is known to the system, the RITA-format
will contain data of the table entry. If the RI is
unknown to the system, a new table entry will be created,
provided the table is not full, where the format displayed
will be empty apart from the specified RI.
4.3.6.2 D̲a̲t̲a̲ ̲E̲n̲t̲r̲y̲
4.3.6.2.1 R̲I̲ ̲(̲M̲a̲n̲d̲a̲t̲o̲r̲y̲)̲
If this field is changed, the system will check that
the RI does not already exist in the table. The system
will scan the Global PLA-Table and the Local RI-Table
carrying out the change.
4.3.6.2.2 C̲i̲r̲c̲u̲i̲t̲ ̲(̲M̲a̲n̲d̲a̲t̲o̲r̲y̲)̲
The system shall:
- scan the Local RI-table and change System Codes
accordingly (if appropriate), if this field is
changed from SCARS to CCIS or vice versa.
- remove the RI from the Local RI-Table (if appropriate),
if this field is changed from SCARS or ACCIS to
P-to-P/TRC or NICS/TARE.
For all changes, the system shall scan the Global PLA-Table
carrying out the change.
4.3.6.2.3 C̲l̲a̲s̲s̲i̲f̲i̲c̲a̲t̲i̲o̲n̲ ̲(̲M̲a̲n̲d̲a̲t̲o̲r̲y̲)̲
If the classification of the RI is changed, the system
shall scan the Global PLA-Table carrying out the change.
4.3.6.2.4 D̲e̲l̲e̲t̲e̲ ̲T̲h̲i̲s̲ ̲R̲I̲-̲T̲a̲b̲l̲e̲ ̲E̲n̲t̲r̲y̲ ̲(̲O̲p̲t̲i̲o̲n̲a̲l̲)̲
This removes the entry from the table.
If the RI refers to SCARS or ACCIS and is contained
in the Local RI-Table, the system shall remove it from
the Local RI-table.
4.3.6.2.5 R̲e̲m̲o̲v̲e̲ ̲A̲l̲l̲ ̲R̲e̲f̲e̲r̲e̲n̲c̲e̲s̲ ̲t̲o̲ ̲T̲h̲i̲s̲ ̲R̲I̲ ̲f̲r̲o̲m̲ ̲t̲h̲e̲ ̲P̲L̲A̲ ̲T̲a̲b̲l̲e̲
̲(̲O̲p̲t̲i̲o̲n̲a̲l̲)̲
The system scans the Global PLA-Table and removes all
references to the RI/CIRCUIT.
4.3.6.2.6 N̲e̲x̲t̲ ̲R̲I̲-̲T̲a̲b̲l̲e̲ ̲E̲n̲t̲r̲y̲ ̲(̲O̲p̲t̲i̲o̲n̲a̲l̲)̲
This gives the "next" RI-Table Entry (next by design).
4.3.6.2.7 N̲e̲x̲t̲ ̲R̲I̲ ̲(̲O̲p̲t̲i̲o̲n̲a̲l̲)̲
If a RI is entered in this data-entry field, the system
shall react as if the command RITA "RI" has been entered.
4.3.6.3 V̲a̲l̲i̲d̲a̲t̲i̲o̲n̲
The supervisor depresses the ENTER key. The system
shall validate all data entries, except Next RI (4.3.6.2.7),
as described above and generate error codes for invalid
entries.
The entry Next RI shall not be validated until after
the supervisor has been prompted for and has entered
the confirmation code. Validation for this field shall
be as described in section 4.3.6.1.
Fig. 4.3.6-1
4.3.7 C̲I̲R̲C̲U̲I̲T̲-̲T̲a̲b̲l̲e̲ ̲U̲p̲d̲a̲t̲e̲ ̲(̲C̲I̲R̲T̲ ̲"̲C̲I̲R̲C̲U̲I̲T̲ ̲N̲O̲"̲)̲
This command makes available the CIRCUIT-Table Update
Format (fig. 4.3.7-1).
4.3.7.1 C̲o̲m̲m̲a̲n̲d̲ ̲E̲n̲t̲r̲y̲
If the specified CIRCUIT NO is known to the system,
the CIRT-format will contain data of the table entry.
If the CIRCUIT NO is unknown to the system an error
message will be displayed.
4.3.7.2 D̲a̲t̲a̲ ̲E̲n̲t̲r̲y̲
4.3.7.2.1 C̲i̲r̲c̲u̲i̲t̲
This field contains the circuit number and cannot be
changed.
4.3.7.2.2 C̲i̲r̲c̲u̲i̲t̲ ̲T̲y̲p̲e̲
This field contains the type of circuit and can be
one of the following:
- NICS/TARE
- OTHER (P-TO-P/TRC)
- SCARS
- ACCIS
This field cannot be changed.
4.3.7.2.3 N̲e̲t̲w̲o̲r̲k̲ ̲(̲M̲a̲n̲d̲a̲t̲o̲r̲y̲)̲
In this field the Network numbers shall be entered.
The system shall check that the following correspondance
between Circuit Type and Network exists:
N̲e̲t̲w̲o̲r̲k̲ C̲i̲r̲c̲u̲i̲t̲ ̲T̲y̲p̲e̲
1 NICS/TARE
2,3 or 4 OTHER
5 SCARS
6 ACCISS
4.3.7.2.4 N̲u̲m̲b̲e̲r̲ ̲o̲f̲ ̲C̲o̲n̲n̲e̲c̲t̲e̲d̲ ̲C̲h̲a̲n̲n̲e̲l̲s̲
This field shall contain the number of connected channels
for this circuit.
4.3.7.2.5 C̲l̲a̲s̲s̲i̲f̲i̲c̲a̲t̲i̲o̲n̲ ̲(̲M̲a̲n̲d̲a̲t̲o̲r̲y̲)̲
In this field, the classification of the circuit shall
be entered. Changes to this field shall only be accepted
if the number of connected channels equals zero.
4.3.7.2.6 N̲e̲x̲t̲ ̲C̲i̲r̲c̲u̲i̲t̲-̲T̲a̲b̲l̲e̲ ̲E̲n̲t̲r̲y̲ ̲(̲O̲p̲t̲i̲o̲n̲a̲l̲)̲
This gives "next" circuit-table entry (next by design).
4.3.7.2.7 N̲e̲x̲t̲ ̲C̲i̲r̲c̲u̲i̲t̲ ̲N̲o̲.̲ ̲(̲O̲p̲t̲i̲o̲n̲a̲l̲)̲
If a CIRCUIT NO. is entered in this data-entry field,
the system shall react as if the command CIRT "CIRCUIT
NO" has been entered.
4.3.7.3 V̲a̲l̲i̲d̲a̲t̲i̲o̲n̲
The supervisor depresses the ENTER key. The system
shall validate all data entries, except Next Circuit
Number, as described above and generate error codes
for invalid entries.
The entry Next Circuit Number shall not be validated
until after the supervisor has been prompted for and
has entered the confirmation code. Validation for
this field shall be as described in section 4.3.7.1.
Fig. 4.3.7-1
4.3.8 S̲C̲A̲R̲S̲/̲A̲C̲C̲I̲S̲ ̲D̲i̲s̲p̲l̲a̲y̲-̲T̲a̲b̲l̲e̲ ̲U̲p̲d̲a̲t̲e̲ ̲(̲S̲C̲C̲T̲ ̲"̲D̲I̲S̲P̲L̲A̲Y̲ ̲I̲D̲"̲)̲
This command makes available the Display-Table Update
Format (fig. 4.3.8-1).
4.3.8.1 C̲o̲m̲m̲a̲n̲d̲ ̲E̲n̲t̲r̲y̲
If the specified DISPLAY-ID is known to the system,
the SCCT-format will contain data of the table entry.
If the DISPLAY ID is unknown to the system, the format
displayed will contain the DISPLAY-ID and the classification
must be filled in. If the maximum number of DISPLAY
IDs (300) is exceeded, an error message will be displayed.
4.3.8.2 D̲a̲t̲a̲ ̲E̲n̲t̲r̲y̲
4.3.8.2.1 D̲i̲s̲p̲l̲a̲y̲ ̲I̲d̲ ̲(̲M̲a̲n̲d̲a̲t̲o̲r̲y̲)̲
If this field is changed, the system will check that
it does not already exist in the table (in which case
an error message will be displayed).
4.3.8.2.2 N̲e̲x̲t̲ ̲D̲i̲s̲p̲l̲a̲y̲ ̲(̲O̲p̲t̲i̲o̲n̲a̲l̲)̲
This gives the "next" entry in the Display-Table (next
by design).
4.3.8.2.3 N̲e̲x̲t̲ ̲D̲i̲s̲p̲l̲a̲y̲ ̲I̲D̲ ̲(̲O̲p̲t̲i̲o̲n̲a̲l̲)̲
If a DISPLAY ID is entered in this data-entry field,
the system shall react as if the command SCCT "DISPLAY
ID" has been entered.
4.3.8.3 V̲a̲l̲i̲d̲a̲t̲i̲o̲n̲
The supervisor depresses the ENTER key. The system
shall validate all data entries, except Next Display
Id, as described above and generate error codes for
invalid entries.
The entry Next Display Id shall not be validated until
after the supervisor has been prompted for and has
entered the confirmation code. Validation for this
field shall be as described in section 4.3.8.1.
Fig. 4.3.8-1
4.3.9 O̲p̲e̲r̲a̲t̲i̲n̲g̲ ̲S̲i̲g̲n̲a̲l̲ ̲T̲a̲b̲l̲e̲ ̲(̲O̲P̲S̲T̲ ̲"̲M̲H̲I̲"̲)̲
This command makes the Operating Signal format available
(Fig. 4.3.9-1).
4.3.9.1 C̲o̲m̲m̲a̲n̲d̲ ̲E̲n̲t̲r̲y̲
If the specified MHI is known to the system, the OPST-format
will contain data of the table entry. If the MHI is
unknown to the system, a new table entry will be created,
provided the table is not full, where the format displayed
will be empty apart from the specified MHI.
4.3.9.2 D̲a̲t̲a̲ ̲E̲n̲t̲r̲y̲
4.3.9.2.1 M̲H̲I̲ ̲(̲M̲a̲n̲d̲a̲t̲o̲r̲y̲)̲
The Supervisor enters the 3-letter Message Handling
Instruction code where the first letter shall be Z
or Q.
4.3.9.2.2 M̲e̲s̲s̲a̲g̲e̲ ̲H̲a̲n̲d̲l̲i̲n̲g̲ ̲I̲n̲s̲t̲r̲u̲c̲t̲i̲o̲n̲ ̲(̲O̲p̲t̲i̲o̲n̲a̲l̲)̲
In this field is entered an explanatory text to the
3-letter MHI.
4.3.9.2.3 D̲e̲l̲e̲t̲e̲ ̲T̲h̲i̲s̲ ̲O̲p̲e̲r̲a̲t̲i̲n̲g̲ ̲S̲i̲g̲n̲a̲l̲ ̲T̲a̲b̲l̲e̲ ̲E̲n̲t̲r̲y̲ ̲(̲O̲p̲t̲i̲o̲n̲a̲l̲)̲
This removes the entry from the table.
4.3.9.2.4 N̲e̲x̲t̲ ̲O̲p̲e̲r̲a̲t̲i̲n̲g̲ ̲S̲i̲g̲n̲a̲l̲ ̲T̲a̲b̲l̲e̲ ̲E̲n̲t̲r̲y̲ ̲(̲O̲p̲t̲i̲o̲n̲a̲l̲)̲
This gives the "next" Operating Signal Table Entry
(next by design).
4.3.9.2.5 N̲e̲x̲t̲ ̲M̲H̲I̲ ̲(̲O̲p̲t̲i̲o̲n̲a̲l̲)̲
If a MHI is entered in this data-entry field, the system
shall react as if the command OPST "MHI" has been entered.
4.3.9.3 V̲a̲l̲i̲d̲a̲t̲i̲o̲n̲
The supervisor depresses the ENTER key. The system
shall validate all data entries, except Next MHI (4.3.9.2.5),
as described above and generate error codes for invalid
entries.
The entry Next MHI shall not be validated until after
the supervisor has been prompted for and has entered
the confirmation code. Validation for this field shall
be as described in section 4.3.9.1.
Fig. 4.3.9-1
4.3.10 L̲o̲c̲a̲l̲ ̲P̲L̲A̲-̲T̲a̲b̲l̲e̲ ̲U̲p̲d̲a̲t̲e̲ ̲(̲L̲P̲L̲T̲ ̲"̲P̲L̲A̲R̲E̲F̲"̲)̲
This Command makes available the Local PLA-Table Update
Format (fig. 4.3.10-1).
4.3.10.1 C̲o̲m̲m̲a̲n̲d̲ ̲E̲n̲t̲r̲y̲
If the Specified local PLAREF is known to the system,
the LPLT format shall contain data of the table entry.
If the PLAREF specified is unknown (i.e. not already
contained in any of the PLA-Tables) to the system,
a new table entry shall be created, provided the table
is not full, when the format displayed will be empty
apart from the specified PLAREF.
4.3.10.2 D̲a̲t̲a̲ ̲E̲n̲t̲r̲y̲
4.3.10.2.1 P̲L̲A̲R̲E̲F̲ ̲(̲M̲a̲n̲d̲a̲t̲o̲r̲y̲)̲
If this field is changed, the system shall check that
the entered PLAREF is unique, i.e. is not already contained
in any of the PLA-Tables. If a PLAREF has been inserted,
the system shall check that the data entry fields PLA
and HQ are filled in.
4.3.10.2.2 L̲o̲c̲a̲l̲ ̲P̲L̲A̲ ̲(̲O̲p̲t̲i̲o̲n̲a̲l̲)̲
The system shall check that the entered PLA is unique
within the Local PLA-table.
4.3.10.2.3 H̲Q̲ ̲(̲O̲p̲t̲i̲o̲n̲a̲l̲)̲
The system shall check that the entered number is within
the range 1-8.
4.3.10.2.4 D̲e̲l̲e̲t̲e̲ ̲T̲h̲i̲s̲ ̲L̲o̲c̲a̲l̲ ̲P̲L̲A̲-̲T̲a̲b̲l̲e̲ ̲E̲n̲t̲r̲y̲ ̲(̲O̲p̲t̲i̲o̲n̲a̲l̲)̲
This removes the entry from the table.
4.3.10.2.5 N̲e̲x̲t̲ ̲L̲o̲c̲a̲l̲ ̲P̲L̲A̲-̲T̲a̲b̲l̲e̲ ̲E̲n̲t̲r̲y̲ ̲(̲O̲p̲t̲i̲o̲n̲a̲l̲)̲
This gives the "next" Local PLA-Table Entry (next by
design).
4.3.10.2.6 N̲e̲x̲t̲ ̲P̲L̲A̲R̲E̲F̲ ̲(̲O̲p̲t̲i̲o̲n̲a̲l̲)̲
If a PLAREF is entered in this data-entry field, the
system shall react as if the command LPLT "PLAREF"
has been entered.
4.3.10.3 V̲a̲l̲i̲d̲a̲t̲i̲o̲n̲
The supervisor depresses the ENTER key. The system
shall validate all data entries, except Next PLAREF
(4.3.10.2.5) as described above and generate error
codes for invalid entries.
The entry Next PLAREF shall not be validated until
after the supervisor has been prompted for and has
entered the confirmation code. Validation for this
field shall be as described in section 4.3.10.1.
Fig. 4.3.10-1
4.3.11 L̲o̲c̲a̲l̲ ̲R̲I̲-̲T̲a̲b̲l̲e̲ ̲U̲p̲d̲a̲t̲e̲ ̲(̲L̲O̲R̲I̲)̲
This command makes available the Local RI-Table Update
Format.
4.3.11.1 D̲a̲t̲a̲ ̲E̲n̲t̲r̲y̲
4.3.11.1.1 S̲y̲s̲t̲e̲m̲ ̲C̲o̲d̲e̲ ̲C̲/̲S̲/̲A̲
Local RIs are preceeded by a system code.
C = CAMPS
S = SCARS
A = ACCIS
4.3.11.1.2 L̲o̲c̲a̲l̲ ̲C̲A̲M̲P̲S̲ ̲R̲I̲s̲ ̲(̲O̲p̲t̲i̲o̲n̲a̲l̲)̲
The RIs entered here shall by the system be used as
local RIs for this CAMPS.
The system shall check that entered SCARS/ACCIS RIs
are contained in the RI-table.
4.3.11.1.3 C̲A̲M̲P̲S̲ ̲D̲e̲ ̲R̲I̲s̲ ̲(̲M̲a̲n̲d̲a̲t̲o̲r̲y̲)̲
The 6 De RIs entered shall be used by the system for
the FL3 ACP127 conversion.
4.3.11.2 V̲a̲l̲i̲d̲a̲t̲i̲o̲n̲
The system shall validate entries as described above.
fig. 4.3.11-1
4.3.12 R̲e̲o̲r̲g̲a̲n̲i̲z̲e̲ ̲A̲l̲l̲ ̲T̲a̲b̲l̲e̲s̲ ̲(̲R̲E̲O̲R̲)̲
Table updating is implemented with an overflow mechanism
to avoid reorganization of the tables for every updating.
By use of the Table status facility, it is possible
to get the number of table entries in overflow areas
and if a large number exists (with performance degradation
as a result) reorganization should be requested.
The actual reorganization process prevents table updating
while in progress and degrades the performance of the
system. Therefore it should be avoided during busy
hours.
4.3.13 A̲b̲a̲n̲d̲o̲n̲ ̲R̲e̲o̲r̲g̲a̲n̲i̲z̲a̲t̲i̲o̲n̲ ̲(̲A̲B̲R̲O̲)̲
This function stops the current reorganization process.
The tables will be in the state prior to issue of reorganization
request and thus a subsequent reorganization will start
from the beginning.
