top - download
⟦6ba0a9b10⟧ Wang Wps File
Length: 87229 (0x154bd)
Types: Wang Wps File
Notes: FIX/1164/PSP/0060
Names: »3300A «
Derivation
└─⟦714fc5a2b⟧ Bits:30006132 8" Wang WCS floppy, CR 0290A
└─ ⟦this⟧ »3300A «
WangText
3…00……00……00……00…J…02……00……00…J
J…05…;…00…;…07…:…0d……1d……06……1c……0d……1c… …1b……0a……1b……00……1b……06……1a……0c……1a…
…19……09……19……0f……19……05……18……0c……18…
…17……0b……17……00……17……02……17……06……16……0a……16……0f……16…
…15……08……15……09……15……0a……15……0c……15……0e……15……00……15……05……14……0a……14……0e……14……02……13……08……13……0a……13……0d……13……00……13… …13……06……12……09……12……0c……12……01……12… …12……06……12……07……11……08……11……0b……11……0d……11……0f……11……01……11……86…1 …02… …02… …02…
…02…FIX/1164/PSP/0060
…02…JJJ/890612…02… #
FIKS MES SUBSYTEM PSP
…02…MLA/830125…02… FIKS
FIKS MES SUBSYSTEM PSP
Product Specification
FIX/1164/PSP/0060
…0f…AK…0e…
FMK
AK (4)
FMK
(5)
FIKS Pgm.Mgr.
1.2
890612
REVISION RECORD
REVISION RECORD
REVISION RECORD
REVISION RECORD
REVISION RECORD
Wang/Disk:
3300A/290A
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲…06…1 …02… …02… …02…
ISSUE DATE PAGES BRIEF
DESCRIPTION
OF
CHANGE
ISSUE DATE PAGES BRIEF
DESCRIPTION
OF
CHANGE
ISSUE DATE PAGES BRIEF
DESCRIPTION
OF
CHANGE
ISSUE DATE PAGES BRIEF
DESCRIPTION
OF
CHANGE
ISSUE DATE PAGES BRIEF
DESCRIPTION
OF
CHANGE
AFFECTED
AFFECTED
AFFECTED
AFFECTED
AFFECTED
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ^ ^
^
1 ^830125 ^ All ^
Original
issue
of
document.
^ ^ ^
1.1 ^861204 ^ DCN1 ^
Changed
in
accordance
with
Order
No:
05/86.
^ ^ ^
1.2 ^890612 ^ DCN2 ^
Changed
in
accordance
with
Order
No:
^ ^ ^
05/88,
25/88
^ ^ ^
^ ^ ^
^ ^ ^
^ ^ ^
^ ^ ^
^ ^ ^
^ ^ ^
^ ^ ^
^ ^ ^
^ ^ ^
^ ^ ^
^ ^ ^
^ ^ ^
^ ^ ^
^ ^ ^
^ ^ ^
^ ^ ^
^ ^ ^
^ ^ ^
^ ^ ^
^ ^ ^
^ ^ ^
^ ^ ^
^ ^ ^
^ ^ ^
^ ^ ^
^ ^ ^
^ ^ ^
^ ^ ^
^ ^ ^
^ ^ ^
^ ^ ^
^ ^ ^
^ ^ ^
^ ^ ^
^ ^ ^
^ ^ ^
^ ^ ^
^ ^ ^
^ ^ ^
^ ^ ^
T̲A̲B̲L̲E̲ ̲O̲F̲ ̲C̲O̲N̲T̲E̲N̲T̲S̲
Page
1 SCOPE ......................................... 1
1.1 INTRODUCTION ............................... 1
1.2 ABBREVIATIONS .............................. 7
2 APPLICABLE DOCUMENTS .......................... 8
3 MODULE SPECIFICATION .......................... 10
3.1 Functional Capabilities .................... 10
3.1.1.1 Preparation Module ................. 11
3.1.1.2 GET ̲STATE ̲EVNT Procedure ........... 16
3.1.1.3 LOAD ̲TXT ̲MASK Procedure ............ 17
3.1.1.4 HEADER ̲INPUT Procedure ............. 18
3.1.1.5 READ ̲INPUT Procedure ............... 19
3.1.1.6 TP ̲MASK ̲TO Procedure ............... 21
3.1.2.1 Edit Module ........................ 22
3.1.2.2 GET ̲EDIT ̲CMD Procedure ............. 28
3.1.2.3 REPLACE ̲LINE Procedure ............. 29
3.1.2.4 ACCEPT ̲LINES Procedure ............. 30
3.1.2.5 INSERT ̲LINES Procedure ............. 31
3.1.2.6 DELETE ̲LINES Procedure ............. 32
3.1.2.7 ACC ̲NEW ̲LINE Procedure ............. 33
3.1.2.8 ACC ̲CUR ̲LINE Procedure ............. 34
3.1.2.9 GET ̲NEXT ̲LINE Procedure ............ 35
3.1.2.10 TERMINATE ̲EDIT Procedure ......... 36
3.1.2.11 DISP ̲CUR ̲LINE Procedure .......... 37
3.1.2.12 DEL ̲CUR ̲LINE Procedure ........... 38
3.1.2.13 BUILD ̲LINE Procedure ............. 39
3.1.3.1 COORDINATE MODULE .................. 40
3.1.3.2 ORIGINATOR COORDINATE Procedure .... 41
3.1.3.3 COORDINATOR COORDINATE Procedure ... 42
3.1.4.1 DISPLAY MODULE ..................... 43
3.1.4.2 QUEUE ̲INDEX Procedure .............. 44
3.1.4.3 PDB ̲MSG ̲STATUS Procedure ........... 46
3.1.4.4 SH ̲DELIVERY Procedure .............. 47
3.1.4.5 DISP ̲HDB ̲MSG Procedure ............. 48
3.1.4.6 LIST ̲PDB ̲MSG Procedure ............. 49
3.1.4.7 PRINT ̲ON ̲TP Procedure .............. 50
3.1.4.8 DISP ̲HEADER Procedure .............. 51
3.1.4.9 DISP ̲LINES Procedure ............... 52
3.1.4.10 SH ̲ALARM Procedure ............... 53
3.1.5.1 RELEASE Module ..................... 54
3.1.5.2 ORIGINATOR ̲RELEASE Procedure ....... 55
3.1.5.3 RELEASER ̲RELEASE Procedure ......... 56
3.1.5.4 RELEASE ̲TO ̲MDS Procedure ........... 57
3.1.5.5 UPDATE ̲STA Procedure ............... 58
3.1.6.1 DELETE Module ...................... 59
3.1.7.1 READDRESS Module ................... 60
3.1.8.1 RETRIEVE Module .................... 62
3.1.9.1 RETRIEVE ̲DISTRIBUTE Module ......... 63
3.1.9.2 ENQUEUE ̲TO ̲MDS Procedure ........... 64
3.1.10.1 KBD ̲DATA Procedure ............... 65
3.1.10.2 MES ̲ERROR Procedure .............. 66
3.1.10.3 CANCEL ̲FIX ̲UP Procedure .......... 67
3.1.10.4 CR ̲NEW ̲MESSAGE Procedure ......... 68
3.1.10.5 PRMT ̲MASK ̲ID Procedure ........... 69
3.1.10.6 PRMT ̲PREC ̲CODE Procedure ......... 70
3.1.10.7 PRMT ̲FM ̲ADR Procedure ............ 71
3.1.10.8 PRMT ̲TO ̲ADR Procedure ............ 72
3.1.10.9 PRMT ̲XMT ̲ADR Procedure ........... 73
3.1.10.10 PRMT ̲IWFO ̲ADR Procedure .......... 74
3.1.10.11 PRMT ̲INT ̲DIST Procedure .......... 75
3.1.10.12 PRMT ̲CLASS Procedure ............. 76
3.1.10.13 PRMT ̲SPECAT Procedure ............ 77
3.1.10.14 PRMT ̲SIC ̲Procedure ............... 78
3.1.10.15 PRMT ̲DTG ̲Procedure ............... 79
3.1.10.16 GET ̲PLAIN ̲ADDR Procedure ......... 80
3.1.10.17 UPDAT ̲FILE ̲TAB Procedure ......... 81
3.1.10.18 COMPLETE ̲PDB Procedure ........... 83
3.1.10.19 GET ̲BUFF ̲SPACE Procedure ......... 84
3.1.10.20 GET ̲ALST ̲SPACE Procedure ......... 85
3.1.10.21 STORE ̲ALIST Procedure ............ 86
3.1.10.22 PDB ̲MTCB ̲UPDAT Procedure ......... 87
3.1.10.23 CH ̲MSG ̲ID Procedure .............. 88
3.1.10.24 CH ̲MSG ̲CLASS Procedure ........... 89
3.1.10.25 SCAN ̲FILE ̲TABLE Procedure ........ 90
3.1.10.26 LOAD ̲MSG ̲BUFF Procedure .......... 91
3.1.10.27 UPDATE ̲PDB ̲LMH Procedure ......... 92
3.1.10.28 DISP ̲MESSAGE Procedure ........... 93
3.1.10.29 RETR ̲FM ̲HDB Procedure ............ 94
3.1.10.30 CH ̲SRS ̲FEEDB Procedure ........... 95
3.1.10.31 FILE ̲TO ̲FILE Procedure ........... 96
3.1.10.32 PURGE ̲BUFFER Procedure ........... 97
3.1.10.33 KEYBOARD ̲CTRL Procedure .......... 98
3.1.10.34 MES ̲CHECKP Procedure ............. 99
3.1.10.35 CHECK ̲CC Procedure ............... 100a
3.1.10.36 PRMT ̲ZPW ̲DTG Procedure ........... 100a
3.1.11 PAS Module ........................... 100b
3.1.12 RETRANSMISSION Module ................ 100c
3.1.12.1 RETRANSMIT Procedure ............. 100c
3.1.12.2 RELEASE ̲RTM Procedure ............ 100d
3.1.12.3 DECODE ̲AIG Procedure ............. 100d
3.1.12.4 TO ̲NEW ̲ALIST Procedure ........... 100d
3.2 Interface Description ...................... 101
3.2.1.1 Prepare Module ..................... 101
3.2.1.1.1 Internal Interface ............. 101
3.2.1.1.2 External Interface ............. 105
3.2.1.2 GET ̲STATE ̲EVNT Procedure ........... 106
3.2.1.2.1 Internal Interface ............. 106
3.2.1.2.2 External Interface ............. 107
3.2.1.3 LOAD ̲TXT ̲MASK Procedure ............ 108
3.2.1.3.1 Internal Interface ............. 108
3.2.1.3.2 External Interface ............. 109
3.2.1.4 HEADER ̲INPUT Procedure ............. 110
3.2.1.4.1 Internal Interface ............. 110
3.2.1.4.2 External Interface ............. 111
3.2.1.5 READ ̲INPUT ̲Procedure ............... 112
3.2.1.5.1 Internal Interface ............. 112
3.2.1.5.1 External Interface ............. 114
3.2.1.6 TP ̲MASK ̲IO Procedure ............... 115
3.2.1.6.1 Internal Interface ............. 115
3.2.1.6.2 External Interface ............. 117
3.2.2.1 EDIT Module ........................ 118
3.2.2.1.1 Internal Interface ............. 118
3.2.2.1.2 External Interface ............. 120
3.2.2.2 GET ̲EDIT ̲CMD Procedure ............. 121
3.2.2.2.1 Internal Interface ............. 121
3.2.2.2.2 External Interfaces ............ 122
3.2.2.3 REPLACE ̲LINE Procedure ............. 123
3.2.2.3.1 Internal Interface ............. 123
3.2.2.3.2 External Interface ............. 124
3.2.2.4 ACCEPT ̲LINES Procedure ............. 125
3.2.2.4.1 Internal Interface ............. 125
3.2.2.4.2 External Interfaces ............ 126
3.2.2.5 INSERT ̲LINES Procedure ............. 127
3.2.2.5.1 Internal Interfaces ............ 127
3.2.2.5.2 External Interfaces ............ 128
3.2.2.6 DELETE ̲LINES Procedures ............ 129
3.2.2.6.1 Internal Interface ............. 129
3.2.2.6.2 External Interfaces ............ 129
3.2.2.7 ACC ̲NEW ̲LINE Procedure ............. 130
3.2.2.7.1 Internal Interface ............. 130
3.2.2.7.2 External Interface ............. 133
3.2.2.8 ACC ̲CUR ̲LINE Procedure ............. 134
3.2.2.8.1 Internal Interface ............. 134
3.2.2.8.2 External Interface ............. 134
3.2.2.9 GET ̲NEXT ̲LINE Procedure ............ 136
3.2.2.9.1 Internal Interface ............. 136
3.2.2.9.2 External Interface ............. 136
3.2.2.10 TERMINATE ̲EDIT Procedure ........ 137
3.2.2.10.1 Internal Interface .......... 137
3.2.2.10.2 External Interface .......... 138
3.2.2.11 DISP ̲CUR ̲LINE Procedure ......... 139
3.2.2.11.1 Internal Interface .......... 139
3.2.2.11.2 External Interface .......... 139
3.2.2.12 DEL ̲CUR ̲LINE Procedure .......... 140
3.2.2.12.1 Internal Interface .......... 140
3.2.2.12.2 External Interface .......... 140
3.2.2.13 BUILD ̲LINE Procedure ............ 141
3.2.2.13.1 Internal Interface .......... 141
3.2.2.13.2 External Interfaces ......... 141
3.2.3.1 COORDINATE Module ................. 142
3.2.3.1.1 Internal Interface ............ 142
3.2.3.1.2 External Interface ............ 143
3.2.3.2 ORIGINATOR ̲TERM Procedure ......... 144
3.2.3.2.1 Internal Interface ............ 144
3.2.3.2.2 Externl Interface ............. 145
3.2.3.3 COORDINATOR ̲TERM Procedure ........ 146
3.2.3.3.1 Internal Interface ............ 146
3.2.3.3.2 External Interface ............ 147
3.2.4.1 DISPLAY Module .................... 149
3.2.4.1.1 Internal Interface ............ 149
3.2.4.1.2 External Interface ............ 150
3.2.4.2 QUEUE ̲INDEX Procedure ............. 151
3.2.4.2.1 Internal Interface ............ 151
3.2.4.2.2. External Interface .......... 152
3.2.4.3 PDB ̲MSG ̲STATUS Procedure .......... 153
3.2.4.3.1 Internal Interface ............ 153
3.2.4.3.2 External Interface ............ 154
3.2.4.4 SH ̲DELIVERY Procedure ............. 155
3.2.4.4.1 Internal Interface ............ 155
3.2.4.4.2 External Interface ............ 156
3.2.4.5 DISP ̲HDB ̲MSG Procedure ............ 157
3.2.4.5.1 Internal Interface ............ 157
3.2.4.5.2 External Interface ............ 158
3.2.4.6 LIST ̲PDB ̲MSG Procedure ............ 159
3.2.4.6.1 Internal Interface ............ 159
3.2.4.6.2 External Interface ............ 160
3.2.4.7 PRINT ̲ON ̲TP Procedure ............. 162
3.2.4.7.1 Internal Interface ............ 162
3.2.4.7.2 External Interface ............ 163
3.2.4.8 DISP ̲HEADER Procedure ............. 164
3.2.4.8.1 Internal Interface ............ 164
3.2.4.8.2 External Interface ............ 164
3.2.4.9 DISP ̲LINE Procedure ............... 165
3.2.4.9.1 Internal Interface ............ 165
3.2.4.9.2 External Interface ............ 166
3.2.4.10 SH ̲ALARM Procedure ................. 167
3.2.4.10.1 Internal Interface ........... 167
3.2.4.10.2 External Interface ........... 168
3.2.5.1 RELEASE Module ..................... 169
3.2.5.1.1 Internal Interface ............. 169
3.2.5.1.2 External Interface ............. 170
3.2.5.2 ORIGINATOR ̲RELEASE Procedure ....... 171
3.2.5.2.1 Internal Interface ............. 171
3.2.5.2.2 External Interface ............. 172
3.2.5.3 RELEASER ̲RELEASE Procedure ......... 173
3.2.5.3.1 Internal Interface ............. 173
3.2.5.3.2 External Interface ............. 175
3.2.5.4 RELEASE ̲TO ̲MDS Procedure ........... 177
3.2.5.4.1 Internal Interface ............. 177
3.2.5.4.2 External Inteface .............. 179
3.2.5.5 UPDATE ̲STATIC Procedure ............ 181
3.2.5.5.1 Internal Interface ............. 181
3.2.5.5.2 External Interface ............. 181
3.2.6.1 DELETE Module ...................... 183
3.2.6.1.1 Internal Interface ............. 183
3.2.6.1.2 External Interface ............. 185
3.2.7.1 READDRESS Module ................... 186
3.2.7.1.1 Internal Interface ............. 186
3.2.7.1.2 External Interface ............. 189
3.2.8.1 RETRIEVE Module .................... 191
3.2.8.1.1 Internal Interface ............. 191
3.2.8.1.2 External Interface ............. 192
3.2.9.1 RETRIEVE ̲DISTRIBUTE Module ......... 193
3.2.9.1.1 Internal Interface ............. 193
3.2.9.1.2 External Interface ............. 194
3.2.9.2 ENQUEUE ̲TO ̲MDS Procedure ........... 195
3.2.9.2.1 Internal Interface ............. 195
3.2.9.2.2 External Interface ............. 195
3.2.10.1 KBD DATA Procedure ............... 196
3.2.10.1.1 Internal Interface ........... 196
3.2.10.1.2 External Interface ........... 198
3.2.10.2 MES ̲ERROR Procedure .............. 199
3.2.10.2.1 Internal Inteface ............ 199
3.2.10.2.2 External Interface ........... 201
3.2.10.3 CANCEL ̲FIX ̲UP Procedure .......... 202
3.2.10.3.1 Internal Interface ........... 202
3.2.10.3.2 External Interface ........... 203
3.2.10.4 CR ̲NEW ̲MESSAGE Procedure ......... 205
3.2.10.4.1 Internal Interface ........... 205
3.2.10.4.2 External Interface ........... 207
3.2.10.5 PRMT ̲MASK ̲ID Procedure ........... 208
3.2.10.5.1 Internal Interface ........... 208
3.2.10.5.2 External Interface ........... 208
3.2.10.6 PRMT ̲PREC ̲CODE Procedure ......... 209
3.2.10.6.1 Internal Interface ........... 209
3.2.10.6.2 External Interface ........... 209
3.2.10.7 PRMT ̲FM ̲ADR Procedure ............ 210
3.2.10.7.1 Internal Interface ........... 210
3.2.10.7.2 External Interface ........... 210
3.2.10.8 PRMT ̲TO ̲ADR Procedure ............ 211
3.2.10.8.1 Internal Interface ........... 211
3.2.10.8.2 External Interface ........... 211
3.2.10.9 PRMT ̲XMT ̲ADR Procedure ........... 212
3.2.10.9.1 Internal Interface ........... 212
3.2.10.9.2 External Interface ........... 212
3.2.10.10 PRMT ̲INFO ̲ADR Procedure .......... 213
3.2.10.10.1 Internal Interface ........... 213
3.2.10.10.2 External Interface ........... 213
3.2.10.11 PRMT ̲INT ̲DIST Procedure .......... 214
3.2.10.11.1 Internal Interface ........... 214
3.2.10.11.2 External Interface ........... 214
3.2.10.12 PRMT ̲CLASS Procedure ............. 215
3.2.10.12.1 Internal Interface ........... 215
3.2.10.12.2 External Interface ........... 215
3.2.10.13 PRMT ̲SPECAT Procedure ............ 216
3.2.10.13.1 Internal Interface ........... 216
3.2.10.13.2 External Interface ........... 216
3.2.10.14 PRMT ̲SIC Procedure ............... 217
3.2.10.14.1 Internal Interface ........... 217
3.2.10.14.2 External Interface ........... 217
3.2.10.15 PRMT ̲DTG Procedure ............... 218
3.2.10.15.1 Internal Interface ........... 218
3.2.10.15.2 External Interface ........... 219
3.2.10.16 GET PLAIN ̲ADDR Procedure ......... 220
3.2.10.16.1 Internal Interface ........... 220
3.2.10.16.2 External Interface ........... 222
3.2.10.17 UPDAT ̲FILE ̲TAB Procedure ......... 223
3.2.10.17.1 Internal Interface ........... 223
3.2.10.17.2 External Interface ........... 223
3.2.10.18 COMPLETE ̲PDB Procedure ........... 226
3.2.10.18.1 Internal Interface ........... 226
3.2.10.18.2 External Interface ........... 228
3.2.10.19 GET ̲BUFF ̲SPACE Procedure ......... 229
3.2.10.19.1 Internal Interface ........... 229
3.2.10.19.2 External Interface ........... 230
3.2.10.20. GET ̲ALST ̲SPACE Procedure ....... 231
3.2.10.20.1 Internal Interface ........... 231
3.2.10.20.2 External Interface ........... 231
3.2.10.21 STORE ̲ALIST Procedure ............ 232
3.2.10.21.1 Internal Interface ........... 232
3.2.10.21.2 External Interface ........... 234
3.2.10.22 PDB ̲MTCB ̲UPDAT Procedure ......... 235
3.2.10.22.1 Internal Interface ........... 235
3.2.10.22.2 External Interface ........... 236
3.2.10.23 CH ̲MSG ̲ID Procedure .............. 237
3.2.10.23.1 Internal Interface ........... 237
3.2.10.23.2 External Inteface ............ 238
3.2.10.24 CH ̲MSG ̲CLASS Procedure ........... 239
3.2.10.24.1 Internal Interface ........... 239
3.2.10.24.2 External Interface ........... 239
3.2.10.25 SCAN ̲FILE ̲TAB Procedure .......... 240
3.2.10.25.1 Internal Interface ........... 240
3.2.10.25.2 External Interface ........... 240
3.2.10.26 LOAD ̲MSG ̲BUFF Procedure .......... 241
3.2.10.26.1 Internal Interface ........... 241
3.2.10.26.2 External Interface ........... 242
3.2.10.27 UPDATE ̲PDB ̲LMH Procedure ......... 243
3.2.10.27.1 Internal Interface ........... 243
3.2.10.27.2 External Interface ........... 244
3.2.10.28 DISP ̲MESSAGE Procedure ........... 244
3.2.10.28.1 Internal Interface ........... 244
3.2.10.28.2 External Interface ........... 245
3.2.10.29 PETR ̲FM ̲HDB Procedure ............ 246
3.2.10.29.1 Internal Interface ........... 246
3.2.10.29.2 External Interface ........... 247
3.2.10.30 CH ̲SRS ̲FEEDB Procedure ........... 248
3.2.10.30.1 Internal Interface ........... 248
3.2.10.30.2 External Interface ........... 248
3.2.10.31 FILE ̲TO ̲FILE Procedure ........... 249
3.2.10.31.1 Internal Interface ........... 249
3.2.10.31.2 External Interface ........... 250
3.2.10.32 PURGE ̲BUFFER Procedure ........... 251
3.2.10.32.1 Internal Interface ........... 251
3.2.10.32.2 External Interface ........... 251
3.2.10.33 KEYBOARD ̲CTRL Procedure .......... 252
3.2.10.33.1 Internal Interface ........... 252
3.2.10.33.1 External Interface ........... 252
3.2.10.34 MES ̲CHECKP Procedure ............. 253
3.2.10.34.1 Internal Interface ........... 253
3.2.10.34.2 External Interface ........... 253
3.2.10.35 CHECK ̲CC Procedure ............... 254
3.2.10.35.1 Internal Interface ........... 254
3.2.10.35.2 External Interface ........... 254
3.2.10.36 PRMT ̲ZPW ̲DTG Procedure ........... 255a
3.2.10.36.1 Internal Interface ........... 255a
3.2.10.36.2 External Interface ........... 255a
3.2.11 PAS Module .......................... 255b
3.2.11.1 Internal Interface .............. 255b
3.2.11.2 External Interface .............. 255d
3.3 Processing ................................. 256
PREPARE Module
3.3.1.1 PREPARE Main ...................... 257
3.3.1.2 GET ̲STATE ̲EVNT .................... 268
3.3.1.3 LOAD ̲TXT ̲MASK ..................... 269
3.3.1.4 HEADER ̲INPUT ...................... 270
3.3.1.5 READ ̲INPUT ........................ 271
3.3.1.6 TP ̲MASK ̲IO ........................ 274
EDIT Module
3.3.2.1 EDIT Main ......................... 280
3.3.2.2 GET ̲EDIT ̲CMD ...................... 282
3.3.2.3 REPLACE ̲LINE ...................... 283
3.3.2.4 ACCEPT ̲LINES ...................... 284
3.3.2.5 INSERT ̲LINES ...................... 287
3.3.2.6 DELETE ̲LINES ...................... 288
3.3.2.7 ACC ̲NEW ̲LINE ....................... 289
3.3.2.8 ACC ̲CUR ̲LINE........................ 302
3.3.2.9 GET ̲NEXT ̲LINE....................... 305
3.3.2.10 TERMINATE ̲EDIT.................... 309
3.3.2.11 DISP ̲CUR ̲LINE .................... 311
3.3.2.12 DEL ̲CUR ̲LINE ..................... 312
3.3.2.13 DEL ̲CUR ̲LINE ..................... 313
COORDINATE Module
3.3.3.1 COORDINATE Main .................... 314
3.3.3.2 ORIGINATOR ̲TERM .................... 315
3.3.3.3 CORRDINATOR ̲TERM ................... 317
DISPLAY Module
3.3.4.1 DISPLAY Main ...................... 320
3.3.4.2 QUEUE ̲INDEX ....................... 322
3.3.4.3 PDG ̲MSG ̲STATUS .................... 326
3.3.4.4 SH ̲DELIVERY ....................... 328
3.3.4.5 DISP ̲HDB MSG ...................... 331
3.3.4.6 LIST ̲PDB ̲MSG ...................... 334
3.3.4.7 PRINT ̲ON ̲TP ....................... 336
3.3.4.8 DISP ̲HEADER ....................... 337
3.3.4.9 DISP ̲LINES ........................ 338
3.3.4.10 SH ̲ALARM ........................ 339
RELEASE Module
3.3.5.1 RELEASE Main ...................... 341
3.3.5.2 ORIGINATOR ̲RELEASE ................ 342
3.3.5.3 RELEASER ̲RELEASE .................. 344
3.3.5.4 RELEASE ̲TO ̲MDS .................... 346
3.3.5.5 UPDATE ̲STATIC ..................... 348
DELETE Module
3.3.6.1 DELETE Main ....................... 349
READDRESS Module
3.3.7.1 READDRESS Main .................... 351
RETRIEVE Module
3.3.8.1 RETRIEVE Main ..................... 358
RETRIEVE/DISTRIBUTE Module
3.3.9.1 RETR ̲DISTRIB ...................... 360
3.3.9.2 ENQUEUE ̲TO ̲MDS .................... 361
UTILITIES
3.3.10.1 KBD ̲DATA ........................ 362
3.3.10.2 MES ̲ERROR ....................... 396
3.3.10.3 CANCEL ̲FIX ̲UP ................... 397
3.3.10.4 CR ̲NEW ̲MESSAGE .................. 413
3.3.10.5 PRMT ̲MASK ̲ID .................... 414
3.3.10.6 PRMT ̲PREC ̲CODE .................. 415
3.3.10.7 PRMT ̲FM ̲ADR ..................... 418
3.3.10.8 PRMT ̲TO ̲ADR ..................... 419
3.3.10.9 PRMT ̲XMT ̲ADR .................... 420
3.3.10.10 PRMT ̲INFO ̲ADR ................... 421
3.3.10.11 PRMT ̲INT ̲DIST ................... 422
3.3.10.12 PRMT ̲CLASS ...................... 423
3.3.10.13 PRMT ̲SPECAT ..................... 424
3.3.10.14 PRMT ̲SIC ........................ 425
3.3.10.15 PRMT ̲DTG ........................ 426
3.3.10.16 GET ̲PLAIN ̲ADDR .................. 427
3.3.10.17 UPDAT ̲FILE ̲TAB .................. 428
3.3.10.18 COMPLETE ̲PDB .................... 429
3.3.10.19 GET ̲BUFF ̲SPACE .................. 430
3.3.10.20 GET ̲ALIST ̲SPACE ................. 431
3.3.10.21 STORE ̲ALIST ..................... 432
3.3.10.22 PDB ̲MTCB ̲UPDAT .................. 433
3.3.10.23 CH ̲MSG ̲ID ....................... 434
3.3.10.24 CH ̲MSG ̲CLASS .................... 435
3.3.10.25 SCAN ̲FILE ̲TABLE ................. 436
3.3.10.26 LOAD ̲MSG ̲BUFF ................... 437
3.3.10.27 UPDATE ̲PDB ̲LMH .................. 438
3.3.10.28 DISP ̲MESSAGE .................... 439
3.3.10.29 RETR ̲FM ̲HDB ..................... 444
3.3.10.30 CH ̲STS ̲FEEDB .................... 445
3.3.10.31 FILE ̲TO ̲FILE .................... 446
3.3.10.32 PURGE ̲BUFFER .................... 447
3.3.10.33 KEYBOARD ̲CTRL ................... 448
3.3.10.34 MES ̲CHECKE ...................... 449
3.3.10.35 CHECK ̲CC ........................ 450
3.3.11 Processing .......................... 450A
3.3.11.1 PAS Main Module ................. 450A
3.3.11.2 CRE ̲HEADER (PAS) ................ 450D
3.4 Data Organization IO-buffers during
header preparation ........................ 451
3.5 Storage Allocation ........................ 454
3.6 Performance Characteristics ............... 455
3.7 Limitations ............................... 456
3.8 Error Codes/Error Locations .............. 457
3.9 Listing References ........................ 483
4 QUALITY ASSURANCE ............................. 484
4.1 Qualfication Tests ........................ 484
4.2 Other Quality Assurance Provisions ........ 484
5 PREPARATIONS FOR DELIVERY ..................... 485
6 NOTES ......................................... 486
7 APPENDICES .................................... 487
1 S̲C̲O̲P̲E̲
The document describes the function of the Message Entry Subsystem (MES).
The purpose of the MES, is to support the terminal interactive procedures required in message
handling.
The MES is active during several phases in a message transition through the FIKS system,
from message origination over message review to the final message distribution.
Interactive terminal procedures to support dedicated supervisor function (in the SFS), and
operations on the System Control Center SCC, are not described in here.
1.1 I̲N̲T̲R̲O̲D̲U̲C̲T̲I̲O̲N̲
The objective of the MES is to provide the interactive terminal user the service of common
message facilities.
Common MES functions are:
A: P̲R̲E̲P̲A̲R̲E̲
PEL preparation long - English
PRL preparation long - Danish
PES preparation short - English
PRS preparation short - Danish
The p̲r̲e̲p̲a̲r̲a̲t̲i̲o̲n̲ function supports the creation of a message and its storage on the Preparation
Data Base (PDB).
B: E̲D̲I̲T̲
EDI Edit message on PDB
The e̲d̲i̲t̲ function supports the modification of the header and text lines of a message
stored on the PDB.
C: C̲O̲O̲R̲D̲I̲N̲A̲T̲E̲
COO Originator coordinate request
DCO Coordinator request
The c̲o̲o̲r̲d̲i̲n̲a̲t̲i̲o̲n̲ function supports the (logical) transmission of a message between the
message preparer's terminal and a coordinator's terminal for comments.
D: D̲I̲S̲P̲L̲A̲Y̲
Status:
DQI Display queue index
STA Display message status
Messages:
SPH Special handling print out
DRR Display from retrieve queue
LST Print from preparation data base (PDB)
PRN Print from precedence queues (TP)
The d̲i̲s̲p̲l̲a̲y̲ function supports the presentation on a terminal of queue information and
message status and the presentation on a terminal of messages from the PDB, or the Historical
Data Base (HDB).
Delivery of special handling messages are also performed by this module.
E: R̲E̲L̲E̲A̲S̲E̲
REL Release message (originator)
DRL Release message (releaser)
The r̲e̲l̲e̲a̲s̲e̲ function supports the outbound and/or local distribution of a message upon
approval of an interactive releaseing authority.
F: D̲E̲L̲E̲T̲E̲
DEL Delete message from PDB
The d̲e̲l̲e̲t̲i̲o̲n̲ function provides the user a facility to delete messages that he prepared
but has not released.
G: R̲E̲A̲D̲D̲R̲E̲S̲S̲
RAD Readdress HDB message (Danish)
RAE Readdress HDB message (English)
The r̲e̲a̲d̲d̲r̲e̲s̲s̲a̲l̲ function supports the release of a message, stored on the Historical
Data Base. It allows the user to prepare a message containing one previously released
message.
H: R̲E̲T̲R̲I̲E̲V̲E̲
RTR Retrieve HDB message
The r̲e̲t̲r̲i̲e̲v̲e̲ function supports the retrieval from the Historical Data Base (HDB).
I: R̲E̲T̲R̲I̲E̲V̲E̲ ̲D̲I̲S̲T̲R̲I̲B̲U̲T̲E̲
RDT Retrieve HDB message and distribute to local terminals.
The r̲e̲t̲r̲i̲e̲v̲e̲/̲d̲i̲s̲t̲r̲i̲b̲u̲t̲e̲ function supports the retrieval from the HDB, and distribution
to terminals local to the MEDE.
J: R̲E̲T̲R̲A̲N̲S̲M̲I̲S̲S̲I̲O̲N̲
RTM Retransmit message
The retransmission function provides the user a facility to retrieve a message from the
HDB and release it to a subset of the original addressees.
K: R̲E̲T̲R̲A̲N̲S̲M̲I̲T̲ ̲T̲R̲A̲F̲F̲I̲C̲
RTT Retransmit traffic to NICS TARE
The retransmit traffic function provides the user a facility to retrieve messages in
a DTG-range and retransmit them to NICS TARE.
O̲V̲E̲R̲V̲I̲E̲W̲ ̲O̲F̲ ̲M̲E̲S̲S̲A̲G̲E̲ ̲A̲C̲C̲E̲S̲S̲
Fig. 1.
A message prepared and stored on the PDB is in Simplified Message Format (SMF).
As long as the message stays in the PDB (= until release) following functions can be performed:
o Edit the message header or text.
o Coordinate the message with another terminal operator by sending the message and
remarks to coordinator, and receive remarks from the coordinator.
o Release message to MDS, originator terminal release authority.
o Transfer message to release position, originator terminal no release authority.
o Release message to MDS, releasing terminal, or send message back to the originator
with a remark.
o List message on the printer.
o Delete message, which has n̲o̲t̲ been sent for coordination, print out or release.
When a message has been released and transferred to the HDB it can be accessed:
o Retrieve from the HDB for print or display.
o Retrieve from the HDB for readdressing purpose. The new message prepared becomes
part of the preparation pool.
o Retrieve from the HDB and distribute local.
A simplified transition diagram is shown on the next page.
Figure 1.
Simplified Message Transition
1.2 A̲B̲B̲R̲E̲V̲I̲A̲T̲I̲O̲N̲S̲
Please refer to FIKS DATA INTERFACE
FIX/0100/MAN/0004.
2 A̲P̲P̲L̲I̲C̲A̲B̲L̲E̲ ̲D̲O̲C̲U̲M̲E̲N̲T̲S̲
Fiks Data I/F Reference
FIX/0100/MAN/0004
Fiks S/W Configuration Control Lib.Descr. DOC.
FIX/0100/MAN/0004
CONV ̲DTG Monitor PSP
FIX/1256/PSP/0039
GET ̲DTG Monitor PSP
FIX/1256/PSP/0049
INTASC Monitor PSP
FIX/1256/PSP/0052
LOG ̲JOUR Monitor PSP
FIX/1256/PSP/0057
MTCB Monitor PSP FIX/1256/PSP/0066
QACCESS Monitor PSP
FIX/1256/PSP/0078
RDF Monitor PSP
FIX/1256/PSP/0081
SFS Submodule PSP
FIX/1155/PSP/0093
SRR Subsystem PSP
FIX/1153/PSP/0096
TEP Subsystem PSP
FIX/1151/PSP/0099
System Design Specification for the
Retransmission Procedure
FXA/SDS/004
3 M̲O̲D̲U̲L̲E̲ ̲S̲P̲E̲C̲I̲F̲I̲C̲A̲T̲I̲O̲N̲
3.1 F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The functional capabilities are divided into 10 sections according to the 9 MES-main-functions
and the common utilities.
Each section is divided into subsections. One subsection per procedure.
Example
3.1.4.2
module level procedure level
Indicates DISPLAY module and procedure
QUEUE ̲INDEX
3.1.1.1 P̲r̲e̲p̲a̲r̲a̲t̲i̲o̲n̲ ̲M̲o̲d̲u̲l̲e̲
F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The purpose of this module is to process the prepara-
tion of a message, and storage on the PDB. The message prepared is in simplified message
format, SMF, and consists of a message header and a part containing the message text.
The preparation is performed on a line by line mode where the operators response is analysed
by the S/W, except for the text part which is entered in free format.
Max. 10 messages can be in preparation per terminal and the max. size of one message is 9,000
bytes.
In case the legal size of the message is exhausted the prepared 9,000 bytes or up to max
PDB-pool size are stored.
The total size of the PDB pool per terminal is 10,000 bytes. A message entered at a terminal
is supplied with a "message id" which identifies the originating termi-
nal and a sequence number local to the position. A message entered into the PDB is considered
to be in one of the following states:
PRE in preparation
REL sent to releaser
OUT sent for printout by means of the procedure LST
COO sent for coordinate
The message will remain "in preparation" until final release or delete.
M̲e̲s̲s̲a̲g̲e̲ ̲P̲r̲e̲p̲a̲r̲a̲t̲i̲o̲n̲
Message preparation can be performed in four different modes:
M̲o̲d̲e̲ K̲e̲y̲ ̲w̲o̲r̲d̲s̲
short preparation danish PRS
short preparation english PES
long preparation danish PRL
long preparation english PEL
H̲e̲a̲d̲e̲r̲ ̲p̲r̲e̲p̲a̲r̲a̲t̲i̲o̲n̲
The header generation is supported by the S/W in prompting the terminal operator for input,
on a line by line basis, and the operator response is analyzed.
Errors and/or omissions are notified to the operator.
The message header contains the message precedence, and the address information of the originator
and the destination positions. The terminal holds a default address of the originator, (FROM
address).
The header also includes the text description, classifi-
cation, specat and subject indication. The contents of the message header is summarized below:
o action precedence (PREC ACT)
o info precedence (PREC INFO)
o date-time-group (DTG) (prompted after internal distribution)
o message id (computer generated)
o from address (FM)
o to address (TO, AIG)
o except address (XMT)
o info address (INFO)
o text delimiter (BT)
o message classification (CLASS)
o special category (SPECAT)
o subject indicator code (SIC)
T̲e̲x̲t̲ ̲P̲r̲e̲p̲a̲r̲a̲t̲i̲o̲n̲
The text part consists of:
o text part
o internal distribution (INT DIST)
The "real" text part entering is accepted in free format and is supported in different modes:
o page mode, on a VDU
o line mode, on a TP
o text mask input (page mode on VDU - line mode on TP)
o PTR input, on a VDU with PTR
P̲a̲g̲e̲ ̲m̲o̲d̲e̲ ̲o̲n̲ ̲a̲ ̲V̲D̲U̲
The S/W supports text input from the VDU in page mode, part page, i.e. transmission of data
is performed up to current cursor position, when the SEND PAGE key has been activated.
The VDU screen is cleared before text input is started and after end of text input. (After
EOM key has been activated).
If more than one page of text is required, the screen can be cleared by activating the key
NEXT.
L̲i̲n̲e̲ ̲m̲o̲d̲e̲ ̲o̲n̲ ̲a̲ ̲T̲P̲
The S/W supports input from the TP in a line at a time mode. The text input is terminated
by N (EOM).
P̲T̲R̲ ̲i̲n̲p̲u̲t̲
Paper tape input can be performed only from a VDU with a PTR fixed allocated.
Before text input, the operator is requested about tape input or not (TAPE ̲).
If tape input is wanted (Y as answer), the VDU screen will be cleared and the S/W will only
accept data-input from the paper tape reader.
Input can be switched back to VDU keyboard by pressing NEXT (function key). Input is then
as normal page mode input from VDU.
If no text input, except from tape, is required, the text part is terminated as during normal
VDU input by activating EOM-key.
T̲e̲x̲t̲ ̲m̲a̲s̲k̲ ̲i̲n̲p̲u̲t̲
The message text part input can be supported by using a specified text mask from a common
pool on the TMF.
Each mask occupies max. 300 bytes on the disk and formatted to max. 1 screen load. The common
pool has a size of max. 60,000 bytes.
As first prompt in a long preparation, the operator will be asked about text mask number.
CR only means no text mask is wanted. If a text mask is requested, the requested mask is
presented for "fill out" after the header preparation, and text characteristica has been
entered.
All the masks are accessible without restrictions from all terminals, but the difference
in the VDU and TP characteristica implies a different operational concept for the two cases:
T̲e̲x̲t̲ ̲m̲a̲s̲k̲ ̲o̲n̲ ̲V̲D̲U̲
The VDU screen is cleared before the mask is loaded, and the VDU is set into part page mode.
The operator can then fill out the unprotected fields on the screen.
The complete mask with given input is transferred to the PDB upon operator activation of
the SEND-PAGE.
T̲e̲x̲t̲ ̲m̲a̲s̲k̲ ̲o̲n̲ ̲T̲P̲
The requested mask is presented at the terminal on a line by line basis, interactively coordinated
with the operator input to specified "fields".
3.1.1.2 GET ̲STATE ̲EVNT Procedure
…0e……0e… ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲…0f……0f…
F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The procedure finds current prompt (sequence no.) from a state-event table (STEVNT) and checks
if the prompt is used in the actual procedure.
A return code is set according to the found prompt.
The procedure is used during header preparation in message preparation.
3.1.1.3 LOAD ̲TXT ̲MASK Procedure
…0e……0e… ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲…0f……0f…
F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The procedure loads a text mask from the text mask file (TMF) to one of the IO-buffers.
The text mask loaded is the mask which the operator has requested during header preparation.
In case the mask is not found an error notification is returned to the caller.
The max. size of a mask is 300 bytes.
The mask numbers are from 001 to 200.
3.1.1.4 HEADER ̲INPUT Procedure
…0e……0e… ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲…0f……0f…
F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The procedure supports header preparation by activation of the prompt utilities. It is called
in case of sequence no. is
o Mask ̲id
o Zpw
o Prec ̲act
o Prec ̲info
o Fm
o To
o Xmt
o Info
o Class
o Specat
o Sic
Before the prompting it is checked whether or not the internal storage capacity for the message
and the address-list is exhausted.
3.1.1.5 READ ̲INPUT Procedure
…0e……0e… ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲…0f……0f…
F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The READ ̲INPUT procedure supports the text input from VDU or TP during preparation or readdressing.
During preparation, the procedure also supports the tape-input if requested.
On VDU
Before text input the screen is cleared. The text is entered page by page.
When a page has been prepared, the page is sent to the computer by activating the SEND-PAGE
key. The cursor will then scan the screen from top to the position where the cursor was
located at SEND-time. The cursor will then go to home position. By activating the NEXT
key, the screen will be cleared and a new page can be prepared. The text-input is terminated
by th EOT key, which also cleares the screen.
On TP
The text is entered line by line.
The text input is terminated by pressing
N
The text input from the terminal is appended to the PDB-message file.
In case of resource error, the input procedure is terminated and an error notification
is issued to the operator after he has activated NEXT key or EOM key.
Resource error occurs when the current msg exhaust 9,000 character or when current msg
plus rest of PDB pool exhaust 10,000 chars. The text up to the limit is saved.
3.1.1.6 TP ̲MASK ̲IO Procedure
…0e……0e… ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲…0f……0f…
F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The purpose of this procedure is to split a text mask into parts which can be prompted line
by line. The prompts consist of the protected fields in the text mask, with one prompt pr.
line. The answer to the prompt can be up to rest of the line.
The procedure will append the prompt and the answer to the PDB-file.
The procedure will return to caller in case of CANCEL, EOM, resource error or if the whole
mask has been transmitted.
The procedure supports 2 types of masks
- field formatted
- line formatted
3.1.2.1 E̲d̲i̲t̲ ̲M̲o̲d̲u̲l̲e̲
F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The purpose of this module is to support the editing of a message stored on the PDB.
In the EDIT module last message handled means last message handled in the preparation pool.
The maximum size of a message is 9,000 bytes.
The editing sequence is controlled by the S/W, based upon the operator input and following
functions are supported:
o accept
- current line
- header part of message
- current line + specified number of lines,
optionally display of accepted lines.
o insert
- according to prompt level header/text lines can be inserted
o replace
- current line replaced by new line
o delete
- specified number of lines deleted
o finish/abort
- complete the editing sequence either by replacing "old" message with "new", or
keep the old.
Access can only be performed to messages in the PDB pool for the actual terminal, and with
a legal security class.
The editing is performed on a line by line basis, and with an operator - S/W interaction.
This means that for a given operator edit command the corresponding prompt is issued and
the operator response to this is analyzed for correct format and the appropriate action is
taken.
Only items which initially have (could have) been entered via the terminal can be modified,
e.g. n̲o̲t̲ the MSG ̲ID.
If message has been readdressed, only the "new" header and the "new" text can be modified.
Messages sent for coordination and release or message in printout cannot be edited.
The edit sequence starts always by displaying the first message line (precedence, dtg, msg-id).
Depending of the operator edit command this line is implicitly changed:
E̲d̲i̲t̲ ̲C̲o̲m̲m̲a̲n̲d̲
- accept
precedence act, info accepted
dtg accepted
the operator will not be prompted further for these data
- insert, delete
illegal commands
- replace
precedence act prompted
precedence info prompted
dtg prompted
E̲d̲i̲t̲i̲n̲g̲ ̲o̲n̲ ̲o̲t̲h̲e̲r̲ ̲l̲e̲v̲e̲l̲s̲
- accept
next msg line presented
- insert
prompt on level issued, until "end of
insertion", which is equal to the one
defined in preparation
next line presented
- delete
next msg line presented
- replace
prompt on level issued as in the
preparation procedure
next msg line presented
An overview of the edit commands and prompt actions is given below.
Relation between edit command and prompt response
and action for each level (continued)
Relation between edit command and prompt response
and action for each level (continued)
3.1.2.2 G̲E̲T̲ ̲E̲D̲I̲T̲ ̲C̲M̲D̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲
F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The procedure will output the prompt for edit command and read the operator response.
It is checked whether or not the entered cmd will be legal in this state of editing.
If the command is found legal one of the following functions will be activated:
o Replace line (sec 3.1.2.3)
o Accept lines (sec 3.1.2.4)
o Insert lines (sec 3.1.2.5)
o Delete lines (sec 3.1.2.6)
o Terminate edit (sec 3.1.2.10)
o Abort edit (CANCEL ̲FIX ̲UP) (sec 3.1.10.3)
3.1.2.3 R̲E̲P̲L̲A̲C̲E̲ ̲L̲I̲N̲E̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲
F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The procedure supports the replacement of one line with a new. The actual prompt is issued
and the response is read.
The "new" message is updated and the next line of the "old" message is found and displayed.
3.1.2.4 A̲C̲C̲E̲P̲T̲ ̲L̲I̲N̲E̲S̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲
F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The procedure supports the acceptance of one ore more lines of the "old" message. It can
also be specified that he whole message or the signal header shall be accepted.
After acceptance the next true of the "old" message will be displayed if there is a next
line.
3.1.2.5 I̲N̲S̲E̲R̲T̲ ̲L̲I̲N̲E̲S̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲
F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The procedure supports the acceptance of the current line i.e. the line just displayed and
the insertion of one or more lines. The insertion will be terminated if a "CR" is given only
input and the next line of the "old" message will be found and displayed.
3.1.2.6 D̲E̲L̲E̲T̲E̲ ̲L̲I̲N̲E̲S̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲
F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The procedure supports the deletion of one or more lines. For each line it is checked if
the line can be deleted.
When deletion is finish the next line of the "old" message is found and displayed.
3.1.2.7 A̲C̲C̲ ̲N̲E̲W̲ ̲L̲I̲N̲E̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲
F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
This procedure is used when a new line shall be entered i.e. during replace or insert. Prompt
will be issued according to message level and the line entered will be appended to the "new"
message. The procedure will examine the input to find out what the next message level will
be if the inserting has to continue.
If the input is"CR" only and the procedure is used in replacing of a line, it is checked,
if the line is mandatory.
3.1.2.8 A̲C̲C̲ ̲C̲U̲R̲ ̲L̲I̲N̲E̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲
F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The procedure supports the acceptance of the current line in the "old" message. It is checked
if it is legal to accept the line under the actual circumstances (e.g. accept of an XMT-line
when the AIG-line preceding is deleted).
3.1.2.9 G̲E̲T̲ ̲N̲E̲X̲T̲ ̲L̲I̲N̲E̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲
F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The procedure is used to point out the next line in the "old" message. It is done by searching
the I/O-buffer for next line start. If it is necessary the next part of the message is read.
If header editing the next alist element is found to, and the next part of the alist is read
onto the I/O-buffer if necessary.
The found line is examined to decide what the next message level must be.
3.1.2.10 T̲E̲R̲M̲I̲N̲A̲T̲E̲ ̲E̲D̲I̲T̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲
F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The procedure will terminate the edit function, e.g. completing the "new" message and the
PDB file table will be checkpointed.
The "old" file and the I/O-buffers will be purged in case of SH message.
3.1.2.11 D̲I̲S̲P̲ ̲C̲U̲R̲ ̲L̲I̲N̲E̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲
F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The procedure will display current line.
3.1.2.12 D̲E̲L̲ ̲C̲U̲R̲ ̲L̲I̲N̲E̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲
F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The procedure will check if it is legal to delete current line in the actual surroundings
(e.g. delete a FM line or delete a TO line if there is no other TO, XMT or INFO lines).
3.1.2.13 B̲U̲I̲L̲D̲ ̲L̲I̲N̲E̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲
F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The procedure will strip off or insert keywords on
o TO level
o INFO level
o INT DIST level
If line is the first on that level the keyword will be inserted else it will be stripped
off.
3.1.3.1 C̲O̲O̲R̲D̲I̲N̲A̲T̲E̲ ̲M̲O̲D̲U̲L̲E̲
F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The purpose of this module is to support transmission of a PDB message between terminal users,
the message originator and a coordinator, for comments.
3.1.3.2 O̲R̲I̲G̲I̲N̲A̲T̲O̲R̲ ̲C̲O̲O̲R̲D̲I̲N̲A̲T̲E̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲
F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The purpose of this module is to select a message from the PDB and send it to a specified
terminal position with comments.
The message can only be sent for coordination to terminals inside the MEDE area in question.
Coordination can be performed on messages created at the terminal and with a class actual
terminal class (user).
Coordination can be performed on specific messages or "last message handled at terminal",
and the message is logically transferred to the coordinator position, in the terminal CO
queue.
The destination terminal is specified with the TERM ID and an additional remark. (Rest of
line).
The originating terminal can send one line of remarks together with the message to the coordinator.
A message sent for coordination cannot be accessed further from the originating terminal
before it has been logically returned by the coordinator.
A message sent for release or in print out cannot be accessed for coordination.
3.1.3.3 C̲O̲O̲R̲D̲I̲N̲A̲T̲O̲R̲ ̲C̲O̲O̲R̲D̲I̲N̲A̲T̲E̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲
F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The purpose of this module is for a coordinator terminal to handle messages entered into
the CO queue of that terminal, for coordination.
The remarks sent from the originator together with the message is presented at the terminal,
and is the basis for coordinator validation. The coordinator may enter one line of remarks
to be returned to the originator together with the message. The remarks are queued in the
terminal LP queue. The message itself is "returned" logically to the terminal PDB pool.
The coordinator outqueues from the CO queue messages for coordination with a classification
actual terminal class (user class). In case of security breach the message and originator
remarks are queued back into the CO queue.
The coordinator may refuse to coordinate the message which implies that the message and the
originating remarks are queued back into the CO queue. The MTCB will then be flagged to avoid
more than one printout.
Prior to coordination the remarks and the message are presented at the terminal:
- display of MSG ID
- display of TERM ID + Comment
- print MSG ID
- print of TERM ID + Comment
- print of message
- print of remarks.
3.1.4.1 D̲I̲S̲P̲L̲A̲Y̲ ̲M̲O̲D̲U̲L̲E̲
F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The purpose of this procedure is to switch control to the procedure which handles the requested
display type.
The different display modes and the according keywords are:
- DQI (ref 3.1.4.2)
Displays enqueuing dtg for messages in specified queue
- STA (ref 3.1.4.3)
Displays status for messages in the PDB pool at the actual terminal
- SPH (ref 3.1.4.4)
Displays message from the SH-queue
- DRR (ref 3.1.4.5)
Displays HDB message from the RT-queue
- LST (ref 3.1.4.6)
Prints message from the PDB pool
- PRN (ref 3.1.4.7)
Prints a message from the precedence queues. Only used on TP's.
3.1.4.2 QUEUE ̲INDEX Procedure
…0e……0e… ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲…0f……0f…
F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The procedure supports the display of a dtg list for a specified queue.
For each entry waiting in the queue the enqueuing-time is presented.
The procedure will prompt the operator for QUEUE ID ̲
The terminal queues to be accessed are:
SH
Z
Y
O Precedence print queues
LP
P
M
R
AX
CO Display queues
RL
RT
DT
Supervisor queues
AL
The dtg list is formattes as follows:
1 line showing the requested queue id and page number if not first page
1 line as underline to header
18 lines where each line consists of up to 7 dtg-elements. Each dtg element is 6 digits
(day-hour-minute)
If there are more queue elements than one full screen can display the procedure acts according
to the terminal type.
VDU operation
The procedure waits for NEXT-key to be activated, whereupon next page is displayed in the
same way as the first page.
The dtg list is displayed page by page on request, until the complete queue information has
been displayed.
TP operation
The procedure will present the dtg list as on VDU, but without the "next screen" option.
This implies a continuously output of the list.
If no elements are present in the requested queue, the operator will get an error notification.
3.1.4.3 PDB ̲MSG ̲STATUS Procedure
…0e……0e… ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲…0f……0f…
F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The procedure supports the display of the status for messages in the PDB pool for the actual
terminal.
The message status is displayed per message with the following information:
o MSG ID
o DTG of msg
o STATUS of message
- PRE available for terminal
- REL sent for Release
- COO sent for Coordination
- OUT sent for print-out
o PRECEDENCE of message
The status list is formatted as follows:
1 line showing which kind of status information the list will give
1 line as underline to header
1-10 lines with message status
One line per message
A status line is represented with
MSG ID : 6 alphanumeric characters
DTG : 6 digits (day-hour-minute)
STATUS : 3 alpha characters
PRECEDENCE : 1 alpha character
3.1.4.4 SH ̲DELIVERY Procedure
…0e……0e… ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲…0f……0f…
F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲y̲
The function of the SH ̲DELIVERY procedure is to deliver a special handling message to an
operator. The message to be delivered is waiting in the SH-queue of the terminal. When entering
the procedure the operator will be prompted for his SH-password. When the operator responds
on this prompt, he has 3 attempts. If all 3 attempts fail, the terminal will be blocked,
the message will be inserted into the supervisor DT-queue and an alarm will be generated.
The operator can answer "N" to the prompt PASSWORD and then the message will be enqueued
to the supervisor for distribution.
When password is accepted the message will be printed at the terminal, and the operator will
be prompted for PASSWORD again. If correct SH-password is not entered in max. 3 attempts,
the terminal will be blocked, and an alarm will be generated.
3.1.4.5 DISP ̲HDB ̲MSG Procedure
…0e……0e… ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲…0f……0f…
F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The procedure is called when an operator wants to inspect an element in the RT-queue after
a retrieval. (The SRR subsystem inserts an element in the RT-queue in case of a retrieval
without hard copy or if the retrieval failed).
The RT-queue is inspected and it is determined whether the element indicates a message or
an error notification to be displayed/printed.
If it is a message, the user is checked for security (and if his security level is lower
than that of the message, an error notification is displayed and the queue element is appended
to the queue) and the message is displayed (or printed if the terminal is a teleprinter).
If the queue element indicates a failed retrieval the used retrieval parameters are set up
in an error notification and displayed/printed.
3.1.4.6 LIST ̲PDB ̲MSG Procedure
…0e……0e… ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲…0f……0f…
F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The procedure supports the printout of a message stored in the PDB pool.
Only messages related to th terminal, and not sent for Release or Coordinate or already sent
for printout, can be sent for printout at the terminal.
The messages are printed in the standard output format.
The message identification given, can be "last message handled at the terminal" or a specific
message, identi-
fied by the msg id. Access is only possible to messages with a legal security class.
When the message is sent for printout, the status will be OUT until the printout has finished.
The status will then change back to PRE.
On VDU, the message will be placed in the LP-queue, and the requested printout will wait
for messages with higher precedence to be printed.
On TP, the requested message will be first message printed, even if messages of higher precedence
are waiting.
3.1.4.7 PRINT ̲ON ̲TP Procedure
…0e……0e… ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲…0f……0f…
F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The procedure supports the request for printout from the terminal precedence queues on a
TP logged on in RX/TX mode.
The procedure (PRN) is only known on a TP.
Interactive communication via the terminal is suspended during the printout.
The "next" message to process is the one from the terminal precedence queues of highest priority,
and only messages with a legal class can be delivered to the terminal. In case the operator
requests printout of a message with higher classification than he is allowed to, he will
gen an error notification and the message is enqueued to the supervisor. (DT-queue).
The messages are printed according to the standard message format.
3.1.4.8 DISP ̲HEADER Procedure
…0e……0e… ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲…0f……0f…
F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The procedure is used to get a header line from the critical region and place it in the IO-buffer
as first line.
The procedure supports the following procedures with header line.
QUEUE ̲INDEX
PDB ̲MSG ̲STATUS
DISP ̲HDB ̲MSG
3.1.4.9 DISP ̲LINES Procedure
…0e……0e… ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲…0f……0f…
F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The procedure is used to output a number of bytes from the IO-buffer to the terminal. If
the terminal is VDU, the caller can request the screen cleared before the text is displayed.
3.1.4.10 SH ̲ALARM Procedure
…0e……0e… ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲…0f……0f…
F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The function of the SH ̲ALARM procedure is to take care of the security errors during the
delivery of a SH-message. Depending on the input, the procedure will
o Reroute the message to the supervisor's distributions queue
o Block the keyboard
o Generate an alarm
o
The rerouting will be checkpointed.
3.1.5.1 R̲E̲L̲E̲A̲S̲E̲ ̲M̲o̲d̲u̲l̲e̲
F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The purpose of this module is to release messages stored in the PDB for distribution by the
MDS. After release the message is stored on the HDB via the MDS except for SH-messages.
The statistic is updated for every combination
- class/precedence
and contains information about
- no of messages
- no of ANO's
- no of characters
Release to the MDS is performed from the originator terminal or a related release terminal.
3.1.5.2 O̲R̲I̲G̲I̲N̲A̲T̲O̲R̲ ̲R̲E̲L̲E̲A̲S̲E̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲
F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The purpose of this module is to process the release function on messages in the preparation
pool. The release is performed on messages related to the actual terminal.
Release can be performed from the terminal on messages with a classification actual user
class.
Release can be performed on specific messages or "last message handled at terminal", and
the message is logically removed from the preparation pool after release.
If the originating terminal has release authority the message is released immediately, if
not the message is sent to the release terminal, in the RL queue, defined for the originating
terminal.
A message sent for release from another terminal can not be accessed further by the originator,
before it is logically transferred back to this terminal.
A release notification is given to the originator terminal when the message has been released
to the MDS.
An entry is made in the message journal when a message has been released to the MDS.
Release cannot be performed on messages sent for coordination or in printout.
3.1.5.3 R̲E̲L̲E̲A̲S̲E̲R̲ ̲R̲E̲L̲E̲A̲S̲E̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲
F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The purpose of this procedure is to process the release function of a message sent for release
at the terminal with release authority.
The message to be released has been entered into the RL queue of the terminal, at the originator
attempt to release the message.
In case of security breach at the release terminal, the message shall be entered badk into
the RL queue.
At release refuseal the releaser can return the message (logically, with one line of remarks
to the originator). The remarks are entered into the terminal LP queue. At release time a
notification is sent to the originating terminal, in the LP queue.
Release can be performed on messages with a classification actual user class.
The message is displayed at the terminal before the release can be performed.
In case of SH-message the buffers are purged after release or release refuseal.
3.1.5.4 R̲E̲L̲E̲A̲S̲E̲ ̲T̲O̲ ̲M̲D̲S̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲
F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The function of this procedure is to release a PDB message to the MDS during a originator-
or releaser release. The message will be removed from the PDB file table and an entry in
log journal will be made.
3.1.5.5 U̲P̲D̲A̲T̲E̲ ̲S̲T̲A̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲
F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
This procedure will after release of a message update the critical region STATIC for every
combination of class and precedence with following informations:
o no of ANO's in message
o no of chars in message
and the message counter will be incremented.
3.1.6.1 D̲E̲L̲E̲T̲E̲ ̲M̲o̲d̲u̲l̲e̲
F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The purpose of this module is to process the deletion of a message in preparation.
Only messages related to the actual terminal and with a classification actual user class
can be deleted.
Deletion of messages sent for Coordination, Release or Printout is not possible.
Special Handling messages are purged when deleted.
Deletion can only be performed on specific messages (MSG ID), and not "last message handled".
3.1.7.1 R̲E̲A̲D̲D̲R̲E̲S̲S̲ ̲M̲o̲d̲u̲l̲e̲
F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The purpose of this module is to process a readdressal request on messages stored on the
HDB
Readdressing is performed on messages for which the operator at the terminal has retrieval
right:
- terminal is supervisor/assistant
- terminal is originator of the message (FM adr)
- terminal is represented as destination address
(TO, INFO) in the message
The following retrieve keys are used:
- MSG ID
- DTG (retrieval dtg)
Readdressing is in principle a preparation with the "old" message as text part of the "new".
The old message is appended to the text part of the new, and the complete new message is
considered as one message in "preparation state".
In case the retrieval from the HDB fails, the procedure is terminated with an error message
to the operator and the prepared message is lost.
The message size is checked against
- max message size of 9000 bytes
- max pool size of 10000 bytes
The size limit can be exhausted in different ways
1. Old message too big for readdressing
msg size 8830 bytes
2. New header + old message exhaust msg size or pool size
3. New header + new text + old message exhaust msg size or pool size
When the legal size of the message or PDB pool is exhausted, the procedure terminates with
an error message to the operator and
Ad 1 + 2: The new message is lost completely
Ad 3: The new header + old message is saved completely. The new text part is saved
up to the limit of the message or PDB pool.
3.1.8.1 R̲E̲T̲R̲I̲E̲V̲E̲ ̲M̲o̲d̲u̲l̲e̲
F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The procedures are called when an operator requests a retrieval of one or more messages from
HDB.
3 different retrieval keys can be used by the operator:
a. Message id + DTG
b. DTG range
c. DTG range + SIC
The operator can specify whether he wants the message printed or displayed on VDU.
When the retrieval information is obtained from the operator a MTCB is created, updated with
retrieval information and enqueued to SRS subsystem.
The event is logged by calling MON LOG ̲JOUR.
3.1.9.1 R̲E̲T̲R̲I̲E̲V̲E̲ ̲D̲I̲S̲T̲R̲I̲B̲U̲T̲E̲ ̲M̲o̲d̲u̲l̲e̲
F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The procedure is called when an operator wants to make a local distribution of a message
from HDB.
The operator is requested to input message id and retrieval time of the message.
A pseudo MTCB containing the retrieval request is sent to the SRR subsystem and the operator
is requested to input the terminal id's of those which are ment to receive the message.
If the retrieval has succeeded a number of Pseudo MTCB's are generated, updated with message
identification of the retrieved message and terminal numbers and then sent to MMS subsystem.
Each MTCB contains information on max. 5 recievers.
3.1.9.2 ENQUEUE ̲TO ̲MDS Procedure
…0e……0e… ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲…0f……0f…
F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The procedure is a part of the processing in the retrieve-distribute command.
At call all destination terminal numbers are delivered in the buffer BUFF1. (Each entry consists
of 1 word: lower byte = terminal number, upper byte = no. of copies to this terminal).
The MTCB index and all destination are delivered to MDS, which enqueues the MTCB to the terminal
queues.
The information is delivered in pseudo MTCB's containing the MTCB id of the message and up
to 5 destination terminals.
When all entries en BUFF1 are delivered to MDS the process is exited.
3.1.10.1 K̲B̲D̲ ̲D̲A̲T̲A̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲
F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The procedure is used to read keyboard input entered via a VDU or TP. The terminal I/F is
supported by the ITM.
The module decodes the line of entered control characters and checks for legal syntax.
According to defined actions processing is performed as response to the input.
The syntax analysis is controlled via syntax tables, see Data I/F document.
The procedure is invoked by a single call. The procedure returns when legal input has been
entered or a "CANCEL" has been detected.
In case of illegal input the procedure issues an error message and a new prompt.
3.1.10.2 MES ̲ERROR Procedure
…0e……0e… ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲…0f……0f…
F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The procedure performs the error notification to the operator.
3.1.10.3 C̲A̲N̲C̲E̲L̲ ̲F̲I̲X̲ ̲U̲P̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲
F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The procedure performs the necessary Fix up due to a requested "CANCEL", or if an error is
detected. In general the Fix up will be done, so the procedure currently cancelled is deactivated,
and the related data + files left as before entering the interrupted procedure.
3.1.10.4 CR ̲NEW ̲MESSAGE Procedure
…0e……0e… ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲…0f……0f…
F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The procedure is used to generate an MTCB for the address list, an MTCB for the message and
a PDB file for a new preparation.
It is checked whether the max allowed number of messages prepared at the terminal has been
reached. It is also checked whether the max allowed number of characters in the PDB pool
has been reached.
In case of resource error the procedure is terminated with an error notice.
A message id is allocated to the new message and displayed.
The procedure writes a dummy binary header on the message file and writes first line of message
in buffer - only msg id.
3.1.10.5 P̲R̲M̲T̲ ̲M̲A̲S̲K̲ ̲I̲D̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲
F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The procedure outputs the prompt for mask id (FORMATTED MSG) and reads file operator response.
3.1.10.6 P̲R̲M̲T̲ ̲P̲R̲E̲C̲ ̲C̲O̲D̲E̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲
F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The procedure outputs the prompts for precedence action (PREC ACT) and precedence info (PREC
INFO), and reads the operator response.
3.1.10.7 P̲R̲M̲T̲ ̲F̲M̲ ̲A̲D̲R̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲
F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The procedure outputs the prompt for the from addressee (FM), and reads the operator response.
The plain address is inserted in the I/O-buffer and displayed on the terminal if specified
in the operator input.
The nominal FM in the TCB is used if specified in the input.
3.1.10.8 P̲R̲M̲T̲ ̲T̲O̲ ̲A̲D̲R̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲
F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The procedure outputs the prompt for the to addressee (TO), and reads the operator response.
The plain address is inserted in the i/o buffer and output on the terminal if specified in
the operator input.
3.1.10.9 P̲R̲M̲T̲ ̲X̲M̲T̲ ̲A̲D̲R̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲
F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The procedure outputs the prompt for the exempt addressees related with a given AIG, and
reads the operator response.
The plain address is inserted in the I/O buffer.
3.1.10.10 P̲R̲M̲T̲ ̲I̲N̲F̲O̲ ̲A̲D̲R̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲
F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The procedure outputs the prompt for the info addressee (INFO), and reads the operator response.
The plain address is inserted in the i/o buffer and output on the terminal if specified in
the operator input.
3.1.10.11 P̲R̲M̲T̲ ̲I̲N̲T̲ ̲D̲I̲S̲T̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲
F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The procedure outputs the prompt for internal distribution (INT ̲DIST), and read the operator
response. The MTCB and PDB are updated.
3.1.10.12 P̲R̲M̲T̲ ̲C̲L̲A̲S̲S̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲
F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The procedure outputs the prompt for message classifi-
cation (CLASS), and reads the operator response. The entered class is validated against the
current terminal class.
The plain text is inserted in the I/O-buffer.
3.1.10.13 P̲R̲M̲T̲ ̲S̲P̲E̲C̲A̲T̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲
F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The procedure outputs the prompt for message special category (SPECAT), and reads the operator
response.
It is checked if an SH password exists in the current terminal profile.
The plain text is inserted in the I/O-buffer.
3.1.10.14 P̲R̲M̲T̲ ̲S̲I̲C̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲
F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The procedure outputs the prompt for message special indicator code (SIC), and reads the
operator response. The response is inserted in the I/O-buffer.
3.1.10.15 P̲R̲M̲T̲ ̲D̲T̲G̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲
F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The procedure outputs the prompt for date time group (DTG), and reads the operator response.
A DTG is generated by the system on request. The PDB is updated.
3.1.10.16 GET ̲PLAIN ̲ADDR Procedure
…0e……0e… ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲…0f……0f…
F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The procedure converts an ANO to a plain address, and displays it if requested.
3.1.10.17 UPDAT ̲FILE ̲TAB Procedure
…0e……0e… ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲…0f……0f…
F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The procedure is used during message preparation, editing and readdressing.
The procedure updates the PDB file table.
The following entries in the file table are updated
- PDB ̲SIZE: new size of PDB pool
- MSG ̲PREP: no of messages prepared from term
- MSG ̲PDB: no of messages in PDB pool
- LAST ̲MSG: msg no for last msg handled
- MTCBINDEX: mtcb index
- MSGNO: msg no
Table-update after header preparation:
MSG ̲PREP: incremented with one
MSG ̲PDB: incremented with one
LAST ̲MSG: equal to msg no
MTCBINDEX: mtcb index for address list
MSGNO: msg no dedicated to message
Table-update after text preparation
PDB ̲SIZE: updated with msg size
MTCBINDEX: mtcb index for address list is exchange
with mtcb index for message file
Table-update after editing
PDB ̲SIZE: updated according to new message
MTCBINDEX: mtcb index for old message is exchanged
with mtcb index for new message
Table-update after readdressing
All entries are updated as after a normal preparation (header + text).
3.1.10.18 COMPLETE ̲PDB Procedure
…0e……0e… ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲…0f……0f…
F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The procedure is used in preparation, edit and readdressing processing to complete the PDB
file by appending the address list to the message part, updating the binary header, the related
MTCB and the PDB file table entry. The address list MTCB, and perhaps file, are released.
3.1.10.19 GET ̲BUFF ̲SPACE Procedure
…0e……0e… ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲…0f……0f…
F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The procedure supports the preparation and edit processing.
The procedure checks if buffer space is exhausted. If space is exhausted the buffer data
is moved to PDB file.
3.1.10.20 GET ̲ALST ̲SPACE Procedure
…0e……0e… ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲…0f……0f…
F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The procedure supports the preparation and edit processing.
The procedure checks if buffer space for adress list is exhausted.
If space is exhausted the address list is stored on an address file (PDB-file).
3.1.10.21 STORE ̲ALIST Procedure
…0e……0e… ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲…0f……0f…
F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The procedure supports the preparation and edit processing.
The procedure temporarily stores the address list on file or in a pseudo MTCB.
3.1.10.22 PDB ̲MTCB ̲UPDAT Procedure
…0e……0e… ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲…0f……0f…
F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The procedure is used during the preparation and edit processing to update the binary header
and related MTCB, according to the processing level. Update is performed in a local area
until the header is complete, whereupon the real MTCB is updated.
3.1.10.23 C̲H̲ ̲M̲S̲G̲ ̲I̲D̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲
F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The procedure requests input of a message identification MSG ID, and validates the operator
entered data:
. check syntax
. check TERM ̲ID against TCB
. scan PDB file table to find the requested ID
. check if access right to message, class check
against terminal profile.
3.1.10.24 C̲H̲ ̲M̲S̲G̲ ̲C̲L̲A̲S̲S̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲
F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The procedure checks the classification of the referenced message against the current terminal
class (user).
A legal access is
msg class ̲ terminal class
Further it is read from the TCB if a current terminal user has an SH password.
The procedure also checks if a message is in a legal state for access (= " in preparation").
3.1.10.25 S̲C̲A̲N̲ ̲F̲I̲L̲E̲ ̲T̲A̲B̲L̲E̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲
F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The procedure scans the PDB file table for a terminal to find the MTCB index for the message,
related to the entered message identification (MSG ̲ID).
Optionally the refetence to "last message handled" can be given.
3.1.10.26 LOAD ̲MSG ̲BUFF Procedure
…0e……0e… ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲…0f……0f…
F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The LOAD ̲MSG ̲BUFF procedure loads a message, stored on a file, into a buffer.
3.1.10.27 U̲P̲D̲A̲T̲E̲ ̲P̲D̲B̲ ̲L̲M̲H̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲
F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The procedure will update the entry in the PDB file table called LAST ̲MSG ̲HANDLED with the
number of current message.
3.1.10.28 DISP ̲MESSAGE Procedure
…0e……0e… ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲…0f……0f…
F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The procedure is used to support the display of a message from a disk file, to a VDU terminal.
The message is displayed page by page.
During display, the keyboard is blocked.
The IO-buffers are purged after display.
The procedure supports message display in the following modes:
- Display header
- Display text
- Display header and text
- Display header and one line
The display of header and one line includes display of a reason lined signal header and one
text line.
3.1.10.29 RETR ̲FM ̲HDB Procedure
…0e……0e… ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲…0f……0f…
F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The procedure is called when a retrieval of a message on HDB is requested (either at Retrieve-distribute
or at Readdress).
The operator is requested to input message id and retrieval DTG of the message to be distributed/
readdressed. Retrieval information is inserted in a created pseudo MTCB which is enqueued
to SRR-subsystem.
The redistribution/readdress request is logged by call of MON LOG ̲JOURNAL.
3.1.10.30 CH ̲SRS ̲FEEDB Procedure
…0e……0e… ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲…0f……0f…
F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
As a result of a retrieval request initiated by either Readdress or Retrieve-distribute module
an element in the RD-queue is awaited.
The RD-queue is read and the MTCB is inspected. A pseudo MTCB indicates a failed retrieval,
and causes the procedure to exit in the error exit.
If the MTCB is real, the requested message has been found.
The MTCB of the message is reserved, the RD-queue element is deleted and the procedure is
exited.
3.1.10.31 FILE ̲TO ̲FILE Procedure
…0e……0e… ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲…0f……0f…
F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The procedure supports the preparation and readdress processing.
The procedure is used to move data from a PDB file or a HDB file, and append the data to
the message file (PDB).
3.1.10.32 PURGE ̲BUFFER Procedure
…0e……0e… ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲…0f……0f…
F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The procedure is used to purge IO-buffers - overwrite with nulls.
3.1.10.33 KEYBOARD ̲CTRL Procedure
…0e……0e… ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲…0f……0f…
F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The procedure is used to block or unblock the keyboard.
3.1.10.35 CHECK ̲CC ̲Procedure
…0e……0e… ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲…0f……0f…
F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The procedure examines a given error code to find out whether or not the error code is caused
by deficiency of sectors on disk.
3.1.10.36 PRMT ̲ZPW ̲DTG Procedure
…0e……0e… ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲…0f……0f…
F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲
The procedure outputs the prompt for ZPW operation signal, and reads the response.
The signal header will be updated with the response.
3.1.11 P̲A̲S̲ ̲M̲o̲d̲u̲l̲e̲
F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲i̲e̲s̲.̲
The purpose of this module is to easen the distribu-
tion in FIKS of ACP127 messages received on papertape from an ordinary teleprinter.
The PAS module automates the normal procedure for this distribution i.e. PAS equals the ordinary
preparation like this
N̲o̲r̲m̲a̲l̲ P̲A̲S̲
Proc ̲ PES Proc ̲ PAS
Precedence ̲ Y Insert msg (no answer
from operator
needed)
FM ̲ / (tape-input)
TO ̲ X003 Released DTG
TO ̲ Proc ̲
Class ̲ SECR
Tape ̲ Y
(tape input)
DTG ̲ /
Proc ̲ Rel
Msgid ̲
Released DTG
Proc ̲
only prompts to the operator and his answers are shown. Messages prepared and released with
PAS use in every way identical to ordinarily prepared and released messages.
