top - download
⟦35134a0d1⟧ Wang Wps File
Length: 77399 (0x12e57)
Types: Wang Wps File
Notes: FIX/0100/MAN/0004
Names: »3927A «
Derivation
└─⟦aa66ef7f5⟧ Bits:30006148 8" Wang WCS floppy, CR 0341A
└─ ⟦this⟧ »3927A «
WangText
…00……00……00……00……00…>…02……00……00…>
>…05…=…0a…= <…0f…;…0b…;…06…:…0a…:…0e…:…02…:…06…9…0c…9…02…9…07…8…09…8…0e…8…0f…8 7…09…7…0e…7 6…09…6…0a…6…0e…6 5…0a…5…0c…5…01…5…06…4…0b…4…00…4…07…3…0c…3
3…05…2…0c…2…00…2…05…2…07…1…0c…1…0f…1…86…1 …02… …02… …02…
3927A
…02…FIX/0100/MAN/0004
…02…APE/880623…02……02…#
FIKS DATA I/F REFERENCE
…02… …02…FK 7809
FIKS DATA I/F REFERENCE
FIX/0100/MAN/0004
AK
FMK (5), AK (4)
FIKS Pgm.Mgr.
3.4
880906
Conf. Manager …86…1
…02…
…02… …02…
3927A…02…FIX/0100/MAN/0004
…02…JJJ/880906…02……02…ii
FIKS DATA I/F REFERENCE
…02…APE/880627…02…FK 8446
800228 All Issue 1 of Document
800530 All Issue 2 of Document
830815 All Issue 3 of Document
851115 DCN1 Updates in accordance
with
FIKS/FODCCIS Link imple-
mentation
860922 DCN2 Changed in accordance
with Order No. 01/86.
880627 DCN3 Changed in accordance
with Order No. 16/86
01/87, 05/87, 09/87,
04/88, 06/88, 07/88
880906 DCN4 Changed in accordance
with Order NO. 24/88
3927A…02…FIX/0100/MAN/0004
…02…APE/830815…02……02…iii
FIKS DATA I/F REFERENCE
…02……02…FK 7809
T̲A̲B̲L̲E̲ ̲O̲F̲ ̲C̲O̲N̲T̲E̲N̲T̲S̲
1 SCOPE ...........................................
1
1.2 Abbreviations ...............................
2
2 APPLICABLE DOCUMENTS ............................
8
3 INTRODUCTION ....................................
9
3.1 Definition and Conventions of Data Types ....
9
3.1.1 Standard Conventions for Words and
Bytes ...................................
9
3.1.2 Character Conventions ...................
10
3.1.3 Boolean Representation ..................
12
3.1.4 Integer Conventions .....................
12
3.1.5 Pascal Sets, Records and Arrays .........
13
3.1.6 Naming of Identifiers ...................
14
3.2 Pascal and Assembly Language Conventions ....
15
4 TYPES AND CONSTANTS .............................
17
4.1 Prefix ......................................
17
4.2 Error Codes .................................
17
4.2.1 Error Codes for Interactive Procedures ..
17
4.2.2 Error Codes from Application Programs ...
18
4.2.2.1 Format of Error Logging .............
18
4.2.2.2 Error Code Listings .................
21
5 CONFIGURATION PARAMETERS ........................
35
5.1 Configuration Table .........................
35
6 QUEUES ..........................................
37
7 CONTROL BLOCKS ..................................
41
7.1 MTGB General Layout and Content .............
41
7.1.1 Message Identification ..................
45
7.1.1.1 Message Transition at Node-MEDE .....
45
7.1.1.2 Message Transition at the SCC .......
69
7.1.2 Parameter Block .........................
90
7.1.2.1 Pseudo-MTCB Transistions at
Node-MEDE ...........................
90
7.1.2.2 Pseudo MTCB Transitions at the SCC ..
149
7.1.2.3.1 Input to MAC via MC-queue .......
222
7.1.2.3.2 Input to MPX via system messages
and answers .....................
226
7.1.2.3.3 Input to INTERCEPT (Terminal
Process) ........................
232
7.2 TCB General Layout and Content ..............
235
3927A…02…FIX/0100/MAN/0004
…02…APE/880627…02……02…iv
FIKS DATA I/F REFERENCE
…02…APE/830815…02…FK 7809
8 TABLES AND RECORDS ..............................
239
8.1 Checkpoints .................................
239
8.1.1 Introduction ............................
239
8.1.2 What is checkpointed ....................
240
8.1.3 How is checkpointing performed ..........
240
8.1.4 Use of the Checkpoint Process ...........
241
8.1.4.1 MTCB-checkpoints ....................
243
8.1.4.2 RDF-checkpoints .....................
245
8.1.4.3 TCB-checkpoints .....................
245
8.1.4.4 PDBTAB-checkpoints ..................
246
8.1.4.5 PAGE NUMBERS-checkpoints ............
247
8.1.4.6 SYSTEM-checkpoints ..................
247
8.1.4.7 Guidelines for doing checkpoints ....
247
8.2 NSC Critical Region Description .............
249
8.2.1 FIKS Network Configuration Table (FNC) ..
249
8.2.1.1 FNC Layout ..........................
249
8.2.1.2 FNC Description .....................
252
8.2.2 FIKS Status Table (FST) .................
254
8.2.2.1 FST Layout ..........................
254
8.2.2.2 FST Description .....................
263
8.2.3 FIKS Routing Delay Table (FRD) ..........
273
8.2.3.1 FRD Layout ..........................
273
8.2.3.2 FRD Description .....................
277
8.2.4 FIKS Routing Table (FRT) ................
277
8.2.4.1 FRT Layout ..........................
277
8.2.4.2 FRT Description .....................
280
8.3 SSS Critical Region Layout ..................
282a
8.4 RDF Core extract ............................
283
8.5 Syntax Tables for MES/SFS Terminal Input ....
291
8.6 References ..................................
298
8.7 Classification Tables .......................
305
8.8 Misc. Tables ................................
306
8.8.1 PDBTAB - PDB File Table .................
306
8.8.2 TXTLNS - Text Lines .....................
307
8.8.3 STEVTB State Event Table ................
309
8.9 SRS CR Critical Region Layout ...............
310
8.10 AMOS Messages .............................
311
8.10.1 Messages between ESP and SAF ..........
311
8.10.2 Messages between SRS and MDS ..........
311
8.11 Jack-Table ................................
312
3927A…02…FIX/0100/MAN/0004
…02…APE/830815…02……02…v
FIKS DATA I/F REFERENCE
…02……02…FK 7809
9 FIKS SYSTEM EVENTS AND COUNTERS .................
322
9.1 Statistics from Subsystems ..................
322
10 MESSAGE FORMATS ................................
324
10.1 Narrative Messages ........................
324
10.1.1 Binary Header .......................
327
10.1.2 Signal ..............................
331
10.1.3 Address List ........................
338
10.2 Control Messages ..........................
341
10.2.1 Control Messages to the MEDE ..........
347
10.2.1.1 On-Line Diagnostic Request ........
348
10.2.1.2 AIG Table Update/Insert/Delete ....
349
10.2.1.3 ANO Table Update/Insert/Delete ....
351
10.2.1.4 USP Table Update/Insert/Delete ....
353
10.2.1.4.1 SCC Mode Change ...............
355
10.2.1.4.2 24 Hour Statistic .............
355
10.2.1.5 Trunk Failure .....................
358
10.2.1.6 Node Failure On/Off ...............
360
10.2.1.7 NPDN Call-up ......................
362
10.2.1.8 NPDN Close-Down ...................
364
10.2.1.9 Trunk Opened/Closed ...............
366
10.2.2 Control Messages to the SCC ...........
368
10.2.2.1 Node Statistics ...................
370
10.2.2.2 Hourly Report .....................
373
10.2.2.4 Local Network Status ..............
375
10.2.2.5 N/M Switchover In/Out of
Operation .........................
377
10.2.2.6 N/M Stand-by Available/
Unavailable .......................
377
10.2.2.7 On-Line Diagnostic Result .........
378
10.2.2.8 Disc On/Off Notice ................
380
10.2.2.9 USP Profile Corrected/Inserted/
Deleted ...........................
382
10.2.2.10 MEDE Statistics ...................
384
10.2.2.11 MEDE Hourly Report ................
386
10.2.2.12 Keep Alive Message ................
388
10.2.2.13 ACP127 and N/T Statistics .........
388
10.2.3 Control Messages to the NSS ...........
390
10.2.3.1 Routing Table .....................
391
10.2.3.2 Open/Close Trunk ..................
393
10.2.3.4 Primary Path for Data User ........
395
10.2.3.5 Set Retransmission Threshold ......
397
10.2.3.6 Set Trunk Queue Threshold .........
399
10.2.3.7 Local Network Status Request ......
401
10.2.3.8 NPDN Call-up/Close-down ...........
402
10.2.3.9 Local Routing Table Update ........
404
10.2.3.10 Configuration .....................
406
10.2.3.11 Open/Close Trunk ..................
407
10.2.3.12 ACK/NACK ..........................
409
10.2.3.13 MICK/MACK .........................
410
3927A…02…FIX/0100/MAN/0004
…02…APE/830815…02……02…vi
FIKS DATA I/F REFERENCE
…02……02…FK 7809
11 FILES ..........................................
411
11.1 Temporary Files ...........................
411
11.1.1 Inbound Message File ..................
411
11.1.2 Temporary Message Files: PDS, TEF, ....
414
11.1.2.1 Preparation Data Base (PDB) .......
416
11.1.2.2 Temporary Edit File (TEF) .........
417
11.1.2.3 Temporary Storage File (TSF) ......
417
11.1.2.4 Temporary Remarks File (TRF) ......
417
11.1.2.5 Message Log File (MLF) ............
420
11.2 HDB Layout ................................
421
11.3 Routing Directory File RDF ................
427
11.4 Text mask file, TMF .......................
455
11.5 Terminal Handling File (THF) ..............
463
11.6 Nodal Data File ...........................
490
11.7 Classification File .......................
491
11.8 LTUX Configuration Files ..................
491
11.9 Reason and Alarm Text Files ...............
491
11.10 SCC Files .................................
500
11.10.1 TSF: ..................................
500
11.10.2 SMF: ..................................
500
11.10.3 AMF: ..................................
501
11.10.4 ADF: ..................................
502
11.10.5 SDF: ..................................
503
11.10.6 THF ...................................
513
11.10.7 RDF ...................................
513
11.11 Message Journal File ......................
513
11.12 Checkpoint File ...........................
515
12 OPERATOR I/O DATA ..............................
523
12.1 N/M Operator I/O Data .....................
523
12.1.1 N/M Error Codes from Interactive
Procedures ............................
523
12.1.2 N/M Alarm Texts .......................
526
12.1.3 Distribution Reason Texts .............
526
12.2 SCC Operator I/O Data .....................
527
12.2.1 SCC VDU/Printer Parameter Description .
527
12.2.2 Operator Command Formats ..............
546
12.2.3 Operator VDU Display Formats
(Lower Screen) ........................
557
12.2.4 Operator Display Format
Upper Screen) .........................
569
12.2.5 Operator ROP Print Formats ............
570
12.2.6 LOG ROP Formats .......................
573
12.2.7 REP ROP Formats .......................
581
12.2.8 Netowrk Status Displays Colours .......
585
1 S̲C̲O̲P̲E̲
The objective of this document is to provide a complete
description of the Common Data Elements and Files used
for Design and Coding of FIKS Application S/W. Data
elements defined by AMOS wil not be disucssed here.
Section 3 defines or references the conventions to
be used for data types.
Section 4 summarizes the common data types and constants.
Secton 5 specifies the Start-up and configuration parameters
for a Node/MEDE or SCC Configuration.
Section 6 defines the queue structure of FIKS.
Section 7 defined the control blocks; Message Transition
Control Block (MTCB) and Terminal Control Block (TCB).
Section 8 defines the common tables and records used
by FIKS Application S/W.
Section 9 defines the FIKS system events and statistics.
Section 10 defines the organisation, layout and size
of the files in FIKS.
1.2 A̲b̲b̲r̲e̲v̲i̲a̲t̲i̲o̲n̲s̲
ACK = acknowledgement
ACP = allied communications protocol
ADDR = address
ADP = automatic data processing
ACL = access control list
AIG = address indicator group
ALF = accountability log file
AMC = air material command
ANO = address number
ASCII = american standard code for information
interchange
ASM = abbreviated service message
ASR = automatic send receive
ATOM = atomal
BID = block identification
BID-1000 = cryptographic equipment
BG = background
CCIE = communication channel I/F equipment
CCITT = committ} consultatif international
telegraphique et telephonique
CHODDEN = chief of defense, denmark
CMD = cartridge module drive
COMCENTER = communication center
COMSEC = communications security
CONF = confidential
CPU = central processing unit
CR = carriage return
CR A/S = christian rovsing a/s
CRYPTO = cryptographic
CRYS = crypto security
CTS = cosmis top secret
CPEI = computer program end item
CHECKP = checkpoint
CIP = collocated interface process
CWD = CIP watchdog
CPM = CIP protocol machine
CQ = conversion queue
DCE = data circuit terminating equipment
DEE = data encrytion equipment
DEMUX = demultiplexer
DMA = direct memory addressing
DOLCE = digital online crypto equipment
DQM = delivery queuer module
DTE = data terminal equipment
DTG = date/time group
DTGF = date/time group file
EDC = error detection and correction
EOT = end of transmission
ESP = error switchover proces
EXCL = exclusive
FDX = full duplex
FIFO = first in - first out
FIKS = forsvarets integrerede kommunikationssystem
FMS = file management subsystem
FMP = file management processor
FSS = fiks software system
FTR = fortroligt
FXS = fiks executive software
GR = groups
HDB = historical data base
HDLC = high level data link control
HDX = half duplex
HEM = hemmeligt
HIPO = hierarchy plus input-process-output
ID = identification
INT DIST = internal distribution
IMF = inbound message file
I/O = input/output
IOS = input/output system
ITA = international telegraph alphabet
ITM = interactive terminal monitor
KSR = keyboard send and receive
LF = line feed
LITSYNC = litton synchronous line protocol
LP = line printer
LTU = line termination unit
LCFH = LTUX configuration file handler
MBC = main bus controller
MDS = message distribribution subsystem
MEDE = message entry and distribution
equipment
MEM = memory
MES = message entry subsystem
MJF = message journal file
MMD = mini module drive
MOM = minutes of meeting
MR = message reference
MRF = message retrieval file
MSG = message
MSUT = medium speed user terminal
MTCB = message transition control block
MUX = multiplexer
MTF = message text files
MLF = message log file
NA = not applicable
NAK = not acknowledgement
NBS = national bureau of standards
(US)
NC = nato confidential
NH = normal handling
NICS = nato integrated communications
system
NODE = fiks node processor
NPDN = nordic public data network
NR = nato restricted
NS = nato secret
NSC = network supervision and control
NU = nato unclassified
NT = nics tare
OJT = on the job training
OMF = outbound message file
OMNI = omnicoder crypto equipment
OPR = operator
ORIG = originator
OLD = online diagnostic
PDB = preparation data base
PIP = printer interface process
PQM = printer queuer module
PROM = programmable read only memory
PSH = previledged service handling
module
PSM = process start module
PSU = power supply unit
PTP = paper tape punch
PTR = paper tape reader
PSP = product specification
Q = queue
RAM = random access memory
RDF = routing directory file
REST = restricted
RI = routing indicator
ROM = read only memory
ROP = receive only printer
RRM = restart recovery module
RR = receiver ready packet
SCC = system control center
SCM = system conroller and memory
SDM = special delivery module
SECR = secret
SFS = supervisory functions subsystem
SH = special handling
SHD = special handling designator
SIC = subject indicator code
SMD = storage module drive
SMF = simplified message format
SOT = start of transmission
SPECAT = special category
SPX = simplex
SRS = storage subsystem
STANAG = standard nato agreement
SYN = synchronization character
SRR = retrieval subsystem
SPS = system product specification
SGP = system generation procedure
SCCLDD = software configuration control
library description document
SCCP = software configuration control
procedure
SIP = SCC interface process
SPM = SIP protocol machine
SWD = SIP watchdog
TARE = (nics) telegraph automatic relay
equipment
TBI = to be inserted
TBD = to be defined
TBS = to be supplied
TCB = terminal control block
TCM = terminal command module
TDX = time divisioned multiplexing
TEF = temporary edit file
TI = transmission identification
TIOM = terminal I/O module
TMF = text mask file
TMC = terminal monitor system
TOR = time of receipt
TOSCA = tote system computer assisted
TP = teleprinter
TRF = temporary remarks file
TSEC = topsecret
TSN = transmission serial number
TTJ = til tjenestebrug
TTY = teletype
UKL = uklassificeret
UNCL = unclassified
USP = user security profile
VDU = visual display unit
V24/V28 = v-series CCITT recommendations
definition of interchange circuits
between DTE and DCE
VDD = version description document
WD = Watchdog
X21/X25 = packet switching CCITT recommendations
YHM = yderst hemmeligt
2 A̲P̲P̲L̲I̲C̲A̲B̲L̲E̲ ̲D̲O̲C̲U̲M̲E̲N̲T̲S̲
FIKS SYSTEM PSP
FIX/1000/PSP/0038
CR80 AMOS, KERNEL, PRODUCT SPECIFICATION
CSS/302/PSP/0008
CR80 AMOS, I/O SYSTEM, PRODUCT SPECIFICATION
CSS/006/PSP/0006
CR80 AMOS, CRITICAL REGIONS, PRODUCT SPEC.
CSS/303/PSP/0009
CR80 TDX DRIVER
CSS/314/PSP/0013
FIKS APPLICATION S/W DEVELOPMENT STANDARDS
FIX/0100/MAN/0005
3 I̲N̲T̲R̲O̲D̲U̲C̲T̲I̲O̲N̲
3.1 D̲e̲f̲i̲n̲i̲t̲i̲o̲n̲ ̲a̲n̲d̲ ̲C̲o̲n̲v̲e̲n̲t̲i̲o̲n̲s̲ ̲o̲f̲ ̲D̲a̲t̲a̲ ̲T̲y̲p̲e̲s̲
P̲a̲s̲c̲a̲l̲ operates on the following 3 b̲a̲s̲i̲c̲ enumeration
types:
Characters (CHAR)
Booleans (BOOLEAN)
and Integers (INTEGER)
The types BIT and BITSTRINGS are unknown in Pascal.
However, AMOS is able to support biststring operations,
therefore it is found practical to describe the representation
of the types here.
S̲w̲e̲l̲l̲: The basic types are:
BYTE or CHAR (= 8 bits),
INTEGER (= 16 bits = 1 word),
LONG (= 2 words).
The type BOOLEAN must be explicityly declared as BOOLEAN
= (FALSE,TRUE);
The A̲s̲s̲e̲m̲b̲l̲e̲r̲ operates on the following 5 basic enumeration
types:
Bit
Bitstring
Characters
Integers
Long integerts (double words)
3.1.1 S̲t̲a̲n̲d̲a̲r̲d̲ ̲C̲o̲n̲v̲e̲n̲t̲i̲o̲n̲s̲ ̲f̲o̲r̲ ̲W̲o̲r̲d̲s̲ ̲a̲n̲d̲ ̲B̲y̲t̲e̲s̲
On files the data are sotred as byte strings starting
with byte 0. In the CR80 the data are stored in 16
bit words as follows:
Bit 15 8 7 0
(Byte 1) (Byte 0)
MSB LSB
3.1.2 C̲h̲a̲r̲a̲c̲t̲e̲r̲ ̲C̲o̲n̲v̲e̲n̲t̲i̲o̲n̲s̲
All characters are internally represented as ASCII
characters according to the following table (Decimal
value/Character):
P̲a̲s̲c̲a̲l̲
Normally 1 characater is stores per CR80 word:
̲1̲5̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲8̲ ̲7̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲0̲ ̲
^̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲^̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲^̲
(Byte 0)
But AMOS supports a packing technique so that 2 characters
can be stored per word. Thus the character array "CHAR1"
can be packed as follows:
̲1̲5̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲8̲ ̲7̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲0̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲H̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲C̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ …0f…N…0e…
̲ ̲ ̲0̲1̲0̲0̲ ̲ ̲ ̲ ̲1̲0̲0̲0̲ ̲ ̲ ̲ ̲ ̲0̲1̲0̲0̲ ̲ ̲ ̲0̲0̲1̲1̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲R̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲A̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ …0f…N+1…0e…
̲ ̲ ̲0̲1̲0̲1̲ ̲ ̲ ̲ ̲0̲0̲1̲0̲ ̲ ̲ ̲ ̲ ̲0̲1̲0̲0̲ ̲ ̲ ̲0̲0̲0̲1̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲1̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ …0f…N+2…0e…
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲0̲0̲1̲1̲ ̲ ̲ ̲0̲0̲0̲1̲ ̲ ̲ ̲ ̲ ̲ ̲
S̲w̲e̲l̲l̲
A variable cannot be declared as BYTE or CHAR, but
only as an ARRAY of CHAR. This emphasizes the fact
that byte arrays in Swell will always be packed with
2 characters per word.
A variable of one character must be declared as:
ONE ̲CHAR=ARRAY ^0..0^ OF CHAR;
A̲s̲s̲e̲m̲b̲l̲e̲r̲
Nowmally 2 characters are stored per CR80 word:
1̲5̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲8̲ ̲7̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲0̲
^ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲^̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲^
(Byte 1) (Byte 0)
3.1.3 B̲o̲o̲l̲e̲a̲n̲ ̲R̲e̲p̲r̲e̲s̲e̲n̲t̲t̲i̲o̲n̲
Booleans are normally represented as one CR80 word:
# 0000 = FALSE
# 0001 = TRUE
3.1.4 I̲n̲t̲e̲g̲e̲r̲ ̲C̲o̲n̲v̲e̲n̲t̲i̲o̲n̲s̲
Integers are normally stored in one CR80 word on the
format of two's complement.
Thus the integers -3, -1, 0, +1, +73 are stores as
follows:
Bit 15 …0e……0e… ̲ ̲ ̲…0f……0f… Byte 1 …0e……0e… ̲ ̲ ̲…0f……0f… 8 7 …0e……0e… ̲ ̲ ̲…0f……0f… Byte 0 …0e……0e… ̲ ̲ ̲…0f……0f… 0
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
MSB LSB
-3 = 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 1
-1 = 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
0 = 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
+1 = 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1
+73 = 0 0 0 0 0 0 0 0 0 1 0 0 1 0 0 1
Long integers are also stored as two's complement,
but in two CR80 words:
M̲S̲B̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲L̲S̲B̲
^̲ ̲B̲y̲t̲e̲ ̲1̲ ̲ ̲ ̲ ̲ ̲ ̲.̲ ̲ ̲ ̲ ̲B̲y̲t̲e̲ ̲0̲ ̲ ̲ ̲^̲ # N
^̲ ̲B̲y̲t̲e̲ ̲3̲ ̲ ̲ ̲ ̲ ̲ ̲.̲ ̲ ̲ ̲ ̲B̲y̲t̲e̲ ̲2̲ ̲ ̲ ̲^̲ # N+1
^
…0e…-…0f… Sign bit
3.1.5 P̲a̲s̲c̲a̲l̲ ̲S̲e̲t̲s̲,̲ ̲R̲e̲c̲o̲r̲d̲s̲ ̲a̲n̲d̲ ̲A̲r̲r̲a̲y̲s̲
The address of a parameter that takes up more than
1 word is the address of the first parameter acccording
to the following scheme:
LONG ̲INTEGER: ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲
addr ^ ̲L̲e̲a̲s̲t̲ ̲s̲i̲g̲n̲i̲f̲i̲c̲a̲n̲t̲
̲ ̲ ̲^
addr+1 ^ ̲M̲o̲s̲t̲ ̲ ̲s̲i̲g̲n̲i̲f̲i̲c̲a̲n̲t̲
̲ ̲ ̲^
SET: ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲
addr ^ ̲1̲5̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲0̲^
addr+1 ^ ̲3̲1̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲1̲6̲^
^ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲^
^ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲^
^ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲^
^ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲^
^ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲^
addr+t ^1̲2̲7̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲1̲1̲2̲^
Member No. n is included
in the set if and only
if bit No. n is 1.
ARRAYS: Arrays are laid out in
lexicographical order.
Example:
A: ARRAY 'A' .. 'B'; 1..2
OF INTEGER;
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
A ^'A',1^ ^ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲^ addr
A ^'A',2^ ^ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲^ addr+1
A ^'B',1^ ^ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲^ addr+2
A ^'B',2^ ^ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲^ addr+3
RECORDS: A record is laid out so that
the first field gets the lowest
address and the last field the
highest address.
Example:
R: RECORD
I,J: INTEGER;
CASE B: BOOLEAN OF
FALSE: (C:CHAR);
TRUE: (L: LONG ̲INTEGER)
END;
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
I ^ ^ addr
^̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲^̲
J ^ ^ addr+1
^̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲^̲
B ^ ^ addr+2
^̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲^̲
C ^ ^ addr+3
^̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲^̲ …0f……0f…L…0e……0e…
^ ^
^̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲^̲ addr+4
S̲w̲e̲l̲l̲: The above address scheme also applies to Swell.
N̲o̲t̲e̲: Multidimentional arrays and arrays of records
are not allowed!
3.1.6 N̲a̲m̲i̲n̲g̲ ̲o̲f̲ ̲I̲d̲e̲n̲t̲i̲f̲i̲e̲r̲s̲
The Identifiers in Pascal or asemly language should
be named according to "FIKS APPLICATION S/W DEVELOPMENT
STANDARDS".
A̲s̲s̲e̲m̲b̲l̲e̲r̲
letter
identifier :: = letter
digit
The length of an identifier is free. However, the identifier
contains more than 6 characters, only the first 5 characters
and the last character are treated.
3.2 P̲a̲s̲c̲a̲l̲ ̲a̲n̲d̲ ̲A̲s̲s̲e̲m̲b̲l̲y̲ ̲L̲a̲n̲g̲u̲a̲g̲e̲ ̲C̲o̲n̲v̲e̲n̲t̲i̲o̲n̲s̲
Sequential Pascal is employed as high level language
for FIKS Application S/W. The language is defined in:
Per Brinch Hansen &
Alfred C. Hartmann:
Sequential Pascal Report
California Istitute of
Technology 1975.
The implementation dependant restrictions to the above
referenced definition are described in:
CR80 System One Utility
Pascal Compiler Reference Manual
CSS/006/RFM/0001
The interface between a Pascal program and the surrounding
system is defined by means of the so called prefix.
The prefix lists the procedures and functions directly
available to the user as they are integrated the Pascal
interpreter.
Inclusion of new prefix procedures is possible following
the guide lines given in:
CR80 System One
Guidelines for Design of Assembler
Prefix Routines
CSS/006/EWP/0002
and
CR80 AMOS KERNEL, PSP
CSS/302/PSP/0008
For coding in assembly language refer to:
CR80 AMOS
Assembler, Users Manual
CSS/401/USM/0042
S̲w̲e̲l̲l̲:̲ For coding in Swell language refers to:
Swell 80
Reference Manual
CSS/425/RFM/0002
4 T̲Y̲P̲E̲S̲ ̲A̲N̲D̲ ̲C̲O̲N̲S̲T̲A̲N̲T̲S̲
4.1 P̲r̲e̲f̲i̲x̲
Refer to Standard S/W Parts.
4.2 E̲r̲r̲o̲r̲ ̲C̲o̲d̲e̲s̲
4.2.1 E̲r̲r̲o̲r̲ ̲C̲o̲d̲e̲s̲ ̲f̲o̲r̲ ̲I̲n̲t̲e̲r̲a̲c̲t̲i̲v̲e̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲s̲
When an error occurs durintg execution of an interactive
procedure, the error will be displayed on the following
format:
? - G : NNN
G̲ ̲i̲s̲ ̲a̲ ̲g̲r̲o̲u̲p̲ ̲n̲u̲m̲b̲e̲r̲:̲
G
1 syntax errors
2 procedure/semantic errors
3 security violation
4 IOS error
5 MTCB error
6 QACCESS error
The error message is printed by MES or SFS using the
ITRANSFER Procedure of the ITM.
N̲N̲N̲ ̲i̲s̲ ̲a̲ ̲s̲e̲r̲i̲a̲l̲ ̲n̲u̲m̲b̲e̲r̲ ̲i̲n̲s̲i̲d̲e̲ ̲t̲h̲e̲ ̲g̲r̲o̲u̲p̲
For IOS errors the following subgroups are used:
100:1FF Kernel errors
200:2FF IOS in UP errors
300:3FF IOS FMS system errors
400:4FF IOS FMS user errors
500:5FF DMA errors
600:6FF IOS terminal errors
4.2.2 E̲r̲r̲o̲r̲ ̲C̲o̲d̲e̲s̲ ̲f̲r̲o̲m̲ ̲A̲p̲p̲l̲i̲c̲a̲t̲i̲o̲n̲ ̲P̲r̲o̲g̲r̲a̲m̲s̲
This section is a list of all possible error codes
that can be generted by various CR80 Software Components
in an opertional FIKS Node/MEDE or FIKS SCC. i.e. codes
originating from:
1. Standard AMOS System.
2. FIKS Modification of AMOS System.
3. FIKS Application Software.
4.2.2.1 F̲o̲r̲m̲a̲t̲ ̲o̲f̲ ̲E̲r̲r̲o̲r̲ ̲L̲o̲g̲g̲i̲n̲g̲
The errors generted in the FIKS System is reported
by MON (ERROR)-call (ref. CR80 AMOS KERNEL, CSS/006/PSP/0006)
and logged by the ESP-process in the following format:
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲
^W̲D̲H̲^ ERR ^T̲A̲G̲^ ^N̲A̲M̲E̲^ NUM: ^L̲A̲B̲H̲^ ^L̲A̲B̲D̲^ COD: ^C̲O̲D̲^̲
^A̲C̲T̲I̲O̲N̲^
Where the variable items (framed) is given in the following:
WHD = Watchdog header
= 6 B 9 T P
^ ^ ^ ^ ̲Equipment
^ ^ ^ P: Processor
^ ^ ^ R: Red TDX-controller
^ ^ ^ B: Black TDX-controller
^ ^ ^ ̲ ̲ ̲Type
^ ^ F: Fatal
^ ^ N: Non fatal
^ ^ ̲ ̲ ̲ ̲ ̲Counter 0 or 1
^ ̲ ̲ ̲ ̲ ̲ ̲ ̲Branch id
O: Branch ONE
T: Branch TWO
WDH is only printed if transparent
WD-mode is used.
NAME = Name of logging process
LABH = Error label hexadecimal value
LABD = Error label decimal value
COD = Error code hexadecimal value
ACTION = Action to be taken
I̲G̲N̲O̲R̲E̲D̲:̲
No action. Logging is done for INFO- purpose.
LOCAL ̲FIX ̲UP:
…0e……0e… ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲…0f……0f…
An error, that may be remedied by the applicaton software
or by intervention of the system opertor, has occured.
Error code and label together will define the case.
DISCARD ̲DISK ONE/TWO
…0e……0e… ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲…0f……0f…
A hardware error on one of the disks has occured. This
disk will be discrded, i.e. diskoperations in the future
will only take place on the other disk.
BGPS ̲IO ̲DISORDER
…0e……0e… ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲…0f……0f…
This logging is meant as a warning. A background process
has not finished its IO-operations going on within
reasonable time. If the error still exists after 3
loggings done with 10 seconds interval, then the action
will be changed to SWITCHOVER.
BGPS ̲CR ̲DISORDER
…0e……0e… ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲…0f……0f…
Analogous with BGPS ̲IO ̲DISORDER. Instead of IO-operations
it is here a question about 'critical region'-operations.
S̲W̲I̲T̲C̲H̲O̲V̲E̲R̲ (for Node/MEDE)
A fatal error has occured. The only possibility for
continuation of the processing is to pass through a
switch-over procedure. This will automatically be done
by the Watchdog.
OPERATION ̲FAIL (for SCC)
…0e……0e… ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲…0f……0f…
A fatal error has occured. The system cannot continue
the processing.
STANDBY ̲OFF
…0e……0e… ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲…0f……0f…
A fatal error has occured in the standby procesor.
This will in the future not be available incase SWITCHOVER
is needed.
At all action except SWITCHOVER, OPERTION ̲FAIL and
STANDBY ̲OFF, the logging process will automatically
be restarted.
4.2.2.2 E̲r̲r̲o̲r̲ ̲C̲o̲d̲e̲ ̲L̲i̲s̲t̲i̲n̲g̲s̲
K̲E̲R̲N̲E̲L̲ ̲E̲R̲R̲O̲R̲ ̲C̲O̲D̲E̲S̲ ref. to CR80
AMOS KERNEL
CSS/302/PSP/0008
C̲r̲i̲t̲i̲c̲a̲l̲ ̲r̲e̲g̲i̲o̲n̲s̲
CODE ^ DESCRIPTION ^ Comment
̲ ̲ ̲ ̲ ̲ ̲^̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲^̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
^ ^
#001 ^ Unknown function ^
#002 ^ Illegal address ^ Outside
process
bounds
#003 ^ Unknown region ^
#004 ^ Region is not
entered ^
#005 ^ Invalid PCB-index ^
#006 ^ Invalid region
name ^
#007 ^ Violation in
region space ^
#008 ^ Too many regions ^ No
free
control
blocks
^ ^
C̲o̲m̲p̲l̲e̲t̲i̲o̲n̲ ̲f̲r̲o̲m̲ ̲C̲r̲e̲a̲t̲e̲ ̲P̲r̲o̲c̲e̲s̲s̲
CODE ^ Description ^ Comment
̲ ̲ ̲ ̲ ̲ ̲^̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲^̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
^ ^
#001 ^ Too many processes ^ No
free
control
blocks
#002 ^ Illegl address ^ Outside
process
bounds
#003 ^ Classification
too high ^
#004 ^ Too many capabilities ^
#005 ^ Invalid name ^
#006 ^ Invalid CPU ^
#007 ^ Invalid priority ^
^ ^
These codes can only by generated by the ESP-process,
where the associated error label will be NUM:
#2BD, 701.
K̲E̲R̲N̲E̲L̲ ̲E̲R̲R̲O̲R̲ ̲C̲O̲D̲E̲S̲
O̲t̲h̲e̲r̲ ̲K̲e̲r̲n̲e̲l̲ ̲e̲r̲r̲o̲r̲s̲
CODE ^ Description ^ Comments
̲ ̲ ̲ ̲ ̲ ̲^̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲^̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
^ ^
#00E ^ Unknown monitor
procedure ^
#101 ^ Trap or illegal
instruc- ^
^ truction executed ^
#102 ^ Parity error ^ in
memory
#103 ^ Timeout ^ referenced
memory
or
^ ^ device
missing
#105 ^ Failed to lookup
process ^
#106 ^ Illegal address ^ Outside
process
bounds
#107 ^ Illegal event
id ^
#108 ^ Illegal receiver
or ^
^ sender of message ^
#109 ^ Invalid message
state ^
#10A ^ Invalid interrupt
param. ^
#10B ^ Invalid interrupt
param. ^
#10C ^ Invalid item
type ^
#10D ^ Message overrun ^ Attempt
to
use
too
many
^ ^ message
buffers.
#10E ^ Illegal call
of monitor ^ PROCESSPCB
only
^ procedure ^ allowed
for
RTC
#11E ^ Not allowed
to call ^
^ CREATEPROCESS ^
^ ^
The associated error labels at this codes will
always be the relative program location where
the erroneous instruction was executed.
I̲O̲-̲S̲Y̲S̲T̲E̲M̲ ̲E̲R̲R̲O̲R̲ ̲C̲O̲D̲E̲S̲ ref to:
CR80 AMOS I/O SYSTEM
CSS/302/PSP/0008
CODE ^ Descripton ^ Comment
̲ ̲ ̲ ̲ ̲^̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲^̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
^ ^
#201 ^ End of file ^ Number of transferred
bytes
^ ^ is 0.
#202 ^ No free file descriptors ^
#203 ^ Illegal file descriptors ^
#204 ^ No free IO-control blocks ^
#205 ^ Illegal IO-control block ^
#206 ^ No free streams ^
#207 ^ Illegal stream ^
#208 ^ No free transfer list ^
^ elements ^
(1)#209 ^ Illegal address ^ Outside
process
bounds.
#20A ^ Illegal buffer list element^
#20B ^ File not open ^
#20C ^ Different file system ^
#20D ^ Unknown file system ^ Driver not ready
(1)#20E ^ Illegal command ^
(1)#20F ^ IO-system error ^
#210 ^ Not enough space ^ At IO-initializing
#211 ^ Illegal mode ^
#212 ^ Illegal memory parameter ^
#213 ^ No buffer space ^
#214 ^ Not connected ^ Error when
#215 ^ Not output mode ^ using streams
#216 ^ Not input mode ^
#217 ^ Element overflow ^
#218 ^ Syntax error ^
^ ^
(1) The associated error labels at thse codes will
always be the relative program location where
the erroneous MON(IO)-call was executed.
F̲I̲L̲E̲ ̲S̲Y̲S̲T̲E̲M̲ ̲E̲R̲R̲O̲R̲ ̲C̲O̲D̲E̲S̲ ref. to:
CR80 AMOS, FMS,
S̲y̲s̲t̲e̲m̲ ̲e̲r̲r̲o̲r̲s̲ Disk Cache Manager
CSS/920/PSP/0047
CODE ^ Description ^ Comment
̲ ̲ ̲ ̲ ̲^̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲^̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
^ ^
#300 ^ DCB pool empty ^ Reconfiguration
#301 ^ VCB pool empty ^ of the FMS-systems
#302 ^ FCB pool empty ^ may be necessary.
#303 ^ CAP pool empty ^
#304 ^ DDCB pool empty ^
#306 ^ Alloc size too large ^
#307 ^ No public access rights ^ These error may
be
#308 ^ Illegal page number ^ caused by a corrupt
#309 ^ Illegal BFD entry ^ volume. DISK
#30A ^ Illegal FCB links ^ SALVATION must
be
^ ^ attempted.
#30C ^ Inconsistent list ^
#30D ^ Illegal system file ^ Software errors
#30E ^ Recovery stack overflow ^
#310 ^ Unexpected driver answer ^
#312 ^ Sector not present ^
#313 ^ Unknown DCM Operation type ^
#314 ^ Invalid sector descriptor ^
^ painter ^ Disk Cache errors
#315 ^ Illegal write id ^
#316 ^ Already write claimed ^
#317 ^ Not write claimed ^
#318 ^ Invalid device ^
#319 ^ Illegal sector numer ^
^ ^
F̲I̲L̲E̲ ̲S̲Y̲S̲T̲E̲M̲ ̲E̲R̲R̲O̲R̲ ̲C̲O̲D̲E̲S̲ ref. to:
CR80 AMOS, FMS,
U̲s̲e̲r̲ ̲e̲r̲r̲o̲r̲s̲ File Manager
CSS/920/PSP/0048
CODE ^ Description ^ Comment
̲ ̲ ̲ ̲ ̲^̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲^̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
^ ^
#400 ^ Non existing device ^
#401 ^ Illegal device kine ^
#402 ^ Illegal CR80 address ^
#403 ^ Device name in use ^
#404 ^ Illegal unit ^
#405 ^ Illegal submit ^
#406 ^ Wrong volume name ^ Home block corrupted?
#407 ^ Non existing volume ^ Volume not mounted.
#408 ^ Volume mounted ^ Requested operation
^ ^ not allowed when
volume
^ ^ mounted.
#409 ^ Different volumes ^ Illegal ENTER-command
#40A ^ Illegal file descriptor ^ File not open.
#40B ^ Illegal file organisation ^
#40C ^ Illegal allocation size ^
#40D ^ Illegal area size ^
#40E ^ Illegal write ^ Attempt to write
in
^ ^ a directory.
#40F ^ File closed ^ File closed before
^ ^ operation was
finished.
#410 ^ Files opened ^ Dismount is not
allowed
^ ^ if some files
are opened
#411 ^ No file to accept ^
#412 ^ Non existing user ^
#413 ^ User already active ^
#414 ^ No connection ^ File not open
for calling
^ ^ user.
#416 ^ Illegal caller ^ Not system user.
#417 ^ Other users ^ Attempt to reset
a file
^ ^ opened to other
users.
#419 ^ Out of range ^ Illegal parameters.
#41B ^ File full ^ Attempt to write
beyond
^ ^ maximum size.
#41C ^ Access control list full ^
#41D ^ Protection failure ^ Violation against
^ ^ protection rules.
#420 ^ Illegal directory ^
#421 ^ Name already exists ^ In the specified
directory
#422 ^ Non existing name ^ In the specified
directory
F̲I̲L̲E̲ ̲S̲Y̲S̲T̲E̲M̲ ̲E̲R̲R̲O̲R̲ ̲C̲O̲D̲E̲S̲ ref. to:
CR80 AMOS, FMS,
U̲s̲e̲r̲ ̲e̲r̲r̲o̲r̲s̲ File Manager
CSS/920/PSP/0048
CODE ^ Description ^ Comment
̲ ̲ ̲ ̲ ̲^̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲^̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
^ ^
#423 ^ Not allocatable ^ Not enough free
space left
^ ^ on the volume.
^ ^ Local fixup code
#425 ^ Kind unit conflict ^
#426 ^ Kind controller conflict ^
#428 ^ Illegal file information ^ Illegal parameter
^ type ^
#429 ^ Not a dual disk ^
#42A ^ Illegal discard ^
#42C ^ Unknown command ^
#42D ^ Bad sector during format ^
#42E ^ Bad sector table full ^ Too many bad
sectors.
#42F ^ Unit is used ^ Already assigned.
#430 ^ Volume is used ^ Already mounted.
#431 ^ Not reserved ^ Reservation of
device
^ ^ is needed for
executing of
^ ^ command.
#432 ^ Already reserved ^ Device reserved
by another
^ ^ user.
#433 ^ Illegal Start Dualize ^ No discarded
disk in a
^ ^ dual disk.
#434 ^ Illegal Finish Dualize ^ No disk is dualizing.
#435 ^ Ilegal Dualize Sector ^ No disk is dualizing.
F̲I̲L̲E̲ ̲S̲Y̲S̲T̲E̲M̲ ̲E̲R̲R̲O̲R̲ ̲C̲O̲D̲E̲S̲
U̲s̲e̲r̲ ̲e̲r̲r̲o̲r̲s̲ (hardware)
CODE ^ Description ^ Comment
̲ ̲ ̲ ̲ ̲^̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲^̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
^ ^
#441 ^ Device timeout ^ Device is not
able to
^ ^ respond
#442 ^ Write protected drive ^
#443 ^ Unexpected disk interface ^ Device failure
-
^ status. ^ Power off?
#444 ^ Data or sync error ^ Corrupted sector
on
^ ^ disk.
#445 ^ Address or sync error ^ Corrupted sector
on
^ ^ disk.
#446 ^ Bad sector ^ Sector marked
as bad.
#447 ^ Write protected sector ^ Sector marked
as
^ ^ write protected
#448 ^ Illegal sector ^
#449 ^ Timing error ^
#44A ^ Subbus overun ^
#44B ^ Parity error ^
#44C ^ Bad sector read ^ of sector not
in
^ ^ bad sector table.
#44D ^ Bad home block ^ Disk cannot be
used
#451-^ Same as #441 - #44D ^ Recovered by
discarding
#45D ^ except for the disk with ^ the affected
disk
^ IO-address 200 of a dual ^
^ disk ^
#461-^ Same as #441 - #44D ^ Recovered by
discarding
#46D ^ except for the disk with ^ the affected
disk
^ IO-address 204 of a dual ^
^ disk. ^
#4FF ^ FMS-timeout ^ No response from
the
^ ^ file system.
The errors that can be recovered by discarding a disk
is handled on system level (i.e. no application interference
necessary).
The associated error lable at error #4FF will, for
every process except ESP, be the relative program location
where the call (via the IO-system) to the FMS-system
was done.
F̲I̲L̲E̲ ̲S̲Y̲S̲T̲E̲M̲ ̲E̲R̲R̲O̲R̲ ̲C̲O̲D̲E̲S̲ ref to:
CR80 DMA Link Driver
D̲M̲A̲ ̲e̲r̲r̲o̲r̲s̲ (user processor) CSS/006/PSP/0003
CODE ^ Description ^ Comment
̲ ̲ ̲ ̲ ̲^̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲^̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
^ ^
#501 ^ Port error ^
#502 ^ Illegal command ^
#503 ^ Transfer list error ^
#504 ^ Transmission error ^
#505 ^ Aborted ^
#506 ^ Stopped ^ Generated by
the IO-
^ ^ system.
T̲D̲X̲-̲D̲R̲I̲V̲E̲R̲ ̲E̲R̲R̲O̲R̲ ̲C̲O̲D̲E̲S̲ ref to:
CR80 TDX Driver
CSS/314/PSP/0013
CODE ^ Description ^ Comment
̲ ̲ ̲ ̲ ̲^̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲^̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
^ ^
#601 ^ Consecutive NAK's, give up ^
#602 ^ Parity error ^ in HOST memory
#603 ^ Timeout during ^ no respone from
HOST
^ assign of driver ^
#605 ^ Buffer overflow ^ input TDX-controller
^ Frame buffer timeout ^ output error?
#606 ^ DMA-error ^ HOST-CR80
#607 ^ Timeout during ^ Local fixup.
I.e.
^ input/output ^ the process is
restarted
^ ^ after error logging.
#609 ^ Command format error ^ System error
#60B ^ Illegal log-line-id ^ System error
#60C ^ Unknown protocol type ^
#60D ^ No available protocol ^ Resource error
^ conroutine. ^
#60E ^ No available protocol ^ Resource error
^ descriptor ^
#60F ^ No available data ^ Resource error
^ buffer link ^
#613 ^ Line busy ^ Remove off the
line
^ ^ not allowed
#615 ^ Illegal speed index ^
#616 ^ Assign state illegal ^ Illegal assign/deassign
^ ^ command.
#617 ^ Log-lines open ^ Deassign not
allowed
#618 ^ Host interface reserved ^ Assign not allowed
^ ^
#6FF ^ TDX-driver timeout ^ No response from
TDX-
^ ^ driver.
^ ^ The associated
error label,
^ ^ will for every
process
^ ^ except ESP, be
the relative
^ ^ program location
where the
^ ^ call (via the
IO-system)
^ ^ was done.
^ ^ After logging
of the error,
^ ^ the process is
restarted.
^ ^ (Local fixup)
^ ^
Q̲A̲C̲C̲E̲S̲S̲ ̲E̲R̲R̲O̲R̲ ̲C̲O̲D̲E̲S̲ ref. to:
QACCESS MONITOR
PSP
FIX/1256/PSP/0078
CODE ^ Decription ^ Comments
̲ ̲ ̲ ̲ ̲^̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲^̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
^ ^
#801 ^ No queue elments available ^ Local fixup
^ ^ (resource error)
#801 ^ Operation failed ^
#801 ^ Illegal opertion code ^ System/
#802 ^ Invalid queue number ^ Application
#802 ^ Invalid terminal number ^ errors
#802 ^ Index exceeds length ^
#802 ^ Not a group queue ^
#803 ^ Queue is empty ^
#804 ^ First entry not active ^
#805 ^ Queue overflow ^ Local fixup
#806 ^ First entry active ^
^ ^
The error codes #801 and #805 are local fixup- errors.
i.e. the process is restarted after logging is done.
It is then up to the applicaton to recover from the
error.
(Only for FIKS Node/Mede- systems).
M̲T̲C̲B̲ ̲E̲R̲R̲O̲R̲ ̲C̲O̲D̲E̲S̲ ref. to:
MTCB MONITOR PSP
FIX/1256/PSP/0066
CODE ^ Decription ^ Comments
̲ ̲ ̲ ̲ ̲^̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲^̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
^ ^
#901 ^ PCB-index out of range ^ System parameter
error
#902 ^ MTCB-init is not done ^
#903 ^ MTCB-index out of range ^
#904 ^ MTCB not in use ^
#905 ^ All save area used ^
#906 ^ Subsystem number out of ^
^ range ^
#907 ^ No MTCB available ^ Local fixup
#908 ^ Illegal update code ^ Does not correspond
to
^ ^ subsystem number.
#909 ^ MTCB use count greater ^ Not expected
^ than 1. ^
#90A ^ File exists already ^
#90B ^ No IMF-space available ^ Local fixup
#90C ^ No PDB-file available ^ Local fixup
#90D ^ No file reference ^
#90E ^ No file in use ^
#90F ^ File use count is 0 ^ Not expected
#910 ^ MTCB use cound overflow ^
#911 ^ File use count overflow ^
^ ^
The error codes #907, #90B, #90C are local fixup- errors.
i.e. The process is restarted after logging is done.
It is then up to the application to recover from the
error.
(Only for FIKS Node/Mede- systems)
L̲C̲F̲H̲-̲E̲R̲R̲O̲R̲S̲ ref. to:
LCFH MONITOR PSP
FIX/1256/PSP/0055
CODE ^ Decription ^ Comments
̲ ̲ ̲ ̲ ̲^̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲^̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
^ ^
#AXX ^ Unexpected byte received ^ Local fixup
^ (byte = #XX) ^
#ABB ^ Timeout during ^ Local fixup
^ create log line. ^
^ ^
These errors are all local fixup- errors.
T̲D̲X̲-̲M̲O̲N̲I̲T̲O̲R̲ ̲E̲R̲R̲O̲R̲ ̲C̲O̲D̲E̲S̲ ref to:
(used by the NSS-process) NSS SUBSYSTEM PSP
FIX/1154/PSP/0001
CODE ^ Description ^ Comment
̲ ̲ ̲ ̲ ̲^̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲^̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
^ ^
#B01 ^ Timeout when polling ^ Local fixup code
^ LTUX-device ^
#B02 ^ No answer when polling ^ Local fixup code
^ LTUX-device ^
#B03 ^ Missing packet ^ Local fixup code
^ ^ -trunk reopened
^ ^
r̲e̲:̲ ̲B̲0̲1̲ ̲+̲ ̲B̲0̲2̲
The associated error label-hex value will contrin bus
and device given by (bit layout).
1̲5̲ ̲ ̲ ̲1̲4̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲8̲ ̲7̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲0̲
^ ^ ^ ^
^
^ ̲ ̲.̲ ̲ ̲ ̲.̲ ̲ ̲ ̲.̲ ̲ ̲^̲ ̲ ̲ ̲.̲ ̲ ̲ ̲.̲ ̲ ̲ ̲.̲ ̲ ̲^̲ ̲ ̲ ̲.̲ ̲ ̲ ̲.̲ ̲ ̲ ̲.̲ ̲ ̲^̲ ̲ ̲ ̲.̲ ̲
̲ ̲.̲ ̲ ̲ ̲.̲ ̲ ̲^
^
^ Device no.
^
BUS: O/1 for Red/Black TDX
R̲e̲.̲ ̲B̲0̲3̲
The asociated error label will contain the following
information:
1̲5̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲8̲ ̲7̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲4̲ ̲3̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲0̲
^ ^ ^ ^
^
^ ̲ ̲ ̲.̲ ̲ ̲ ̲.̲ ̲ ̲ ̲.̲ ̲ ̲^̲ ̲ ̲ ̲.̲ ̲ ̲.̲ ̲ ̲.̲ ̲ ̲ ̲^̲ ̲ ̲ ̲.̲ ̲ ̲ ̲.̲ ̲ ̲ ̲.̲ ̲ ̲ ̲^̲ ̲ ̲ ̲.̲
̲ ̲ ̲.̲ ̲ ̲ ̲.̲ ̲ ̲ ̲^
ASCII value of Trunk serial Precedence
neighbour node number level
O̲L̲D̲ ̲E̲R̲R̲O̲R̲ ̲C̲O̲D̲E̲S̲ ref to:
(Online diagnostic) OLD SUBSYSTEM PSP
FIX/1200/PSP/0072
CODE ^ Decription ^ Comments
̲ ̲ ̲ ̲ ̲^̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲^̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
^ ^
E00 ^ Successful test ^ Ignore
E01 ^ CPU-ERROR-CPU number 0 ^ Error label contains
E11 ^ CPU-ERROR-CPU number 1 ^ group number
of
^ ^ the failig instruction.
EX2 ^ RAM-ERROR ^ On page X.
^ ^ Error label contains
^ ^ address of first
fault.
E03 ^ PROM-ERROR ^ (On page 0).
^ ^ Error Label contains
^ ^ address of first
fault.
^ ^
5 C̲O̲N̲F̲I̲G̲U̲R̲A̲T̲I̲O̲N̲ ̲P̲A̲R̲A̲M̲E̲T̲E̲R̲S̲
5.1 C̲o̲n̲f̲i̲g̲u̲r̲a̲t̲i̲o̲n̲ ̲T̲a̲b̲l̲e̲
The configuration parameters, which are used when the
FIKS-system is operating, are stored in the critical
region with name: C̲O̲N̲F̲I̲G̲
and absolute location:
page: = 0
address: = #F780
It is created and loaded from disk file C̲O̲N̲F̲ by the
ESP-process at intialization point.
The layout is as follows:
Item- Updated
i̲n̲d̲e̲x̲ ̲ ̲ ̲ ̲C̲o̲n̲t̲e̲n̲t̲s̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲b̲y̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
0 Pointer to MTCB-parameters
1 Pointer to QACCESS-parameters
2 Pointer to RDF-parameters
3 Pointer to Constant Block
4-5 Spares
M̲T̲C̲B̲-̲p̲a̲r̲a̲m̲e̲t̲e̲r̲s̲
6 Page of MTCB data
7 Offset in page of MTCB data
8 Size of MTCB data area
9 Max of MCB-index
10 Max of processes initialized
11 Numbers of MTCB's-total
12 Numbers of IMF-files
13 Numbers of PDB-files
14 MTCB LOWER THRESHOLD
15 PDB LOWER THRESHOLD
16-17 Spares
Q̲A̲C̲C̲E̲S̲S̲-̲p̲a̲r̲a̲m̲e̲t̲e̲r̲
18 Page of QACCESS-area
19 Offset in page of QACCESS-area
20 Number of message terminals
21 Maximum number of terminals
22 Threshold of print queues
23 Total number of queue elements at MEDE
24 Threshold of queue elements at non priviledged
call
25 Spares
Item- Updated
i̲n̲d̲e̲x̲ ̲ ̲ ̲ ̲C̲o̲n̲t̲e̲n̲t̲s̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲b̲y̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
R̲D̲F̲-̲p̲a̲r̲a̲m̲e̲t̲e̲r̲s̲
26 Page of RDF-area
27 Offset in page of RDF-area
28 Size of RDF-area
29-33 Spares
C̲o̲n̲s̲t̲a̲n̲t̲ ̲B̲l̲o̲c̲k̲
34 Branch id (1/2) ESP
35 Start/restart flag (0/1) ESP
36 Status of standby branch
(0/1 = not available/available) ESP
37 Status of discs
(DISK 2/1 OFF/ON = BIT 8/1 OFF/ON) ESP
38 Logical number of log printer
39 Node MEDE is (ASCII)
40 Message Log flag SFS/PIP
41 DT Terminal number
42 FODCCIS Terminal number
43 FODCCIS Link status CTERM/CPIP
(0/1/2/3 for
Not existing/Closed/Open/Failed)
44 Sum of VDU's
45 Sum of TP's
46 Sum of PTP's
47 Sum of PTR's
48-49 Spares
50 First free memory location on page 0 ESP
51 " " " " " " 1 ESP
52 " " " " " " 2 ESP
53 " " " " " " 3 ESP
Item- Updated
i̲n̲d̲e̲x̲ ̲ ̲ ̲ ̲C̲o̲n̲t̲e̲n̲t̲s̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲b̲y̲ ̲
̲ ̲ ̲ ̲ ̲ ̲
M̲e̲m̲o̲r̲y̲ ̲M̲a̲p̲
54 Last available address on page 0
55 " " " " " 1
56 " " " " " 2
57 " " " " " 3
O̲n̲l̲i̲n̲e̲ ̲d̲i̲a̲g̲n̲o̲s̲t̲i̲c̲s̲ ̲s̲t̲a̲t̲u̲s̲
58 Status of CPU's OLD
(CPU 1/0 not ok/ok = bit 8/1 OFF/ON)
59 Status of RAM OLD
(not ok/ok = 0/1)
60 Status of PROM OLD
(not ok/ok = 0/1)
61-63 Spares
P̲s̲e̲u̲d̲o̲ ̲T̲e̲r̲m̲i̲n̲a̲l̲s̲ ̲(̲L̲o̲g̲ ̲P̲r̲i̲n̲t̲e̲r̲s̲)̲
64-65 SCC Conversion LOG
66-67 Transaction LOG
68-69 Spare Pseudo Terminal
70-71 Spare Pseudo Terminal
66-127 Spares
Note:
When using CONFIG in connection with SWELL-programming,
refer to FIKS-prefix file CONFIG ̲TYPE.S.
6 Q̲U̲E̲U̲E̲S̲
7 C̲O̲N̲T̲R̲O̲L̲ ̲B̲L̲O̲C̲K̲S̲
7.1 M̲T̲G̲B̲ ̲G̲e̲n̲e̲r̲a̲l̲ ̲L̲a̲y̲o̲u̲t̲ ̲a̲n̲d̲ ̲C̲o̲n̲t̲e̲n̲t̲
The MTCB is used as message identification (see 7.1.1)
or parameter block (see 7.1.2).
Figure 7.1 gives the general layout of both types of
MTCB's.
Control Word
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
^ ^ ^ ^ ^ ^
^
0 ^Q…0f…1…0e… ^Q…0f…2…0e… ^ Q…0f…3…0e… ^Q…0f…4…0e… ^ Q…0f…5…0e… ^ Q…0f…6…0e…
^
^̲ ̲ ̲ ̲^̲ ̲ ̲ ̲^̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲^̲ ̲ ̲ ̲^̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲^̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲^̲
15 14 13 12 11 10 9 8 7 6 5 4 3 2
1 0
Real or Pseudo MTCB (depending on Q…0f…2…0e…)
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
^
^
1 ^
^
^
^
^
^
2 ^
^
^
^
^
^
3 ^
^
^
^
^
^
4 ^ See details in sections
^
^ 7.1.1 and 7.1.2
^
^
^
5 ^
^
^
^
^
^
6 ^
^
^
^
^
^
7 ^
^
^̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲^̲
^
^
8 ^ Temporary file spare printer
^
^̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲^̲
Figure 7.1
MTCB Layout
MTCB Control word Content
name Q…0f…1…0e… value 0,1
Q…0f…1…0e…=1 MTCB in use Q…0f…2…0e… -Q…0f…7…0e… has meaning
Q…0f…1…0e…=0 MTCB not in use. The rest of word is
pointer to next free.
name Q…0f…2…0e… value 0,1
Q…0f…2…0e…=1 MTCB is normal MTCB
Q…0f…2…0e…=0 MTCB is pseudo MTCB
name Q…0f…3…0e… value 0,1,2
Q…0f…3…0e… = 0 No temporary file space allocated
Q…0f…3…0e… = 1 IMF file allocated
Q…0f…3…0e… = 2 PDB file allocated
Whenever temporary file space is allocated
Q…0f…5…0e… gives number of actual users.
MTCB control word content
a) Q…0f…2…0e… = 1 (Real MTCB)
name Q…0f…4…0e… value 0,1
Q…0f…4…0e… = 1 Message on HDB
Q…0f…4…0e… = 0 HDB not referenced.
name Q…0f…5…0e… value 0-31
Counter for number of file users whenever
(Q…0f…3…0e… =1 or 2) temporary file space used.
name Q…0f…6…0e… value 0-63
Counter for number of MTCB users.
b) Q…0f…2…0e… =0 (Pseudo MTCB)
name Q…0f…4…0e… value always 0
name Q…0f…5…0e… value 0-31
Counter for number of users of temporary file
space.
(Q…0f…3…0e… = 1 or 2)
name Q…0f…6…0e…
Counter for number of MTCB users.
Temporary file space pointer.
A pointer to either PDB or IMF file Values:
Q…0f…3…0e… = 0 0
Q…0f…3…0e… = 1 Area number in IMF file
Q…0f…3…0e… = 2 File number in PDB file pool
7.1.1 M̲e̲s̲s̲a̲g̲e̲ ̲I̲d̲e̲n̲t̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
Messages are referenced via the MTCB. The MTCB points
to either a disc-file or the Historical data-base.
MTCBs identifying messages are at the Node/MEDEs generated
by the Message Entry Subsystem and the Nodal Switch
subsystem. After release of a message from the MES
and after entering the message on a disc file by the
NSS, messages are only read off the disc.
Whenever a subsystem wants to read a message identified
by an MTCB, the message is taken from the Historical
data base for the cases where the message resides there.
For cases where the message is not on the Historical
data base the file is referenced.
7.1.1.1 M̲e̲s̲s̲a̲g̲e̲ ̲T̲r̲a̲n̲s̲i̲t̲i̲o̲n̲ ̲a̲t̲ ̲N̲o̲d̲e̲-̲M̲E̲D̲E̲
The functins at the Node-MEDE are performed by the
following subsystems/processes:
Message Entry Subsystem
Supervisory Function Subsystem
Message Distribution Subsystem
Nodal Switch Subsystem
Storage Subsystem
Retrievel Subsystem
Printer Interface Process
SCC Interface Process.
The following message transition cases can be identified
(Refer figure 7.1.1-1).
1. MES internal
coordination, release
2. MES release to MDS for local or outbound delivery
3. MDS to NSS for outbound delivery
3a. MDS to SIP for messages with NATO-ANO's
4. MDS to SRS for storage
5. MDS to PIP for local printout
6. SRR to PIP for retrieval with hardcopy
7. SRR to MES for retrieval with display
8. Spare.
9. NSS to MDS for inbound messages and orbiting messages.
10. NSS internal for message relaying
(simultaneous to MEDE-delivery)
11. Spare
12. MES to PIP for distribute and retrieve + distribute
13. SRR to MES for retrieve in case retrieve + distribute
14. MES to PIP for 10 minute time out on SH messages
PIP makes an enqueueing as described in 8 (14a).
15 SRR to MES for Readdressing
16. NSS to SIP for messages to collocated SCC
17. SIP to NSS for messages from collocated SCC to
network and MEDE
18. Spare
19. MDS to SFS for control messages
20. SFS to NSS for control messages
N̲o̲t̲e̲: If the FODCCIS Link exists then PIP/MES
can be replaced by CPIP/CTERM.
Figure 7.1.1-1
Message Transition Node-MEDE
Functional description of transition cases.
Note: Some of these transitions will take place concurrently.
1. MES internal
A message in preparation is identified by an MTCB.
Messages are sent to coordination and release identified
by MTCBs.
Remarks are sent by means of pseudo-MTCBs with
allocated file-space.
2. MES release to MDS
The MES queues the MTCB to the MDS according to
precedence. The queue monitor will make a reserve
MTCB. After successful queueing, the MES will make
release MTCB.
3. MDS to NSS for outbound delivery
Simultaneous to the MEDE distribution and storage
of the message the NSS will have a queue entry
identifying the message.
3a. On N/M E and K messages with NATO-ANO's are sent
to SIP
4. MDS to SRS for storage
The MDS will timestampt the message and queue it
to the SRS for storage on the HDB. When the storage
has been performed, the SRS will mark the MTCB
with the reference to the HDB and all future read
of MTCB will point to the HDB for access to message.
5. MDS to PIP for print out
The MDS will queue the MTCB to a number of terminal
queues for local printout.
6. SRR to PIP for retrieval with hardcopy
Whenever 1-10 messages found as a result of a retrieval
request from MES an MTCB for each will be queued
to the PIP for printout (when hardcopy specified).
These MTCBs will all reference the HDB for access
to message.
7. SRR to MES for retrieval with display
Whenever 1-10 messages found as a result for a
retrieval request from the MES an MTCB for ech
will be queued for display.
9. NSS to MDS for inbound messages
Inbound messages are queued by the NSS to the MDS
for local delivery and storage.
10. NSS internal for message relaying
NSS relays messages simultaneous to MEDE distribution
and storage.
12. MES to PIP for distribute and retireve + distribute
The MES distributes messages from the RT queue
and messages obtained by retrieve for distribution
to PIP for printout. The queuing is according to
message precedence.
13. SRR to MES for retrieve in case retrieve + distribute
The SRR queues the retrieved message to the RT
queue and sends a signal to the terminal process.
14. Spare
15. SRR to MES for retrieve in case readdressing
The SRR queues the retrieved message to the RD
queue and sends a signal to the terminal process.
16. NSS to SIP for messages to collocated SCC.
The NSS queues messages for a active, collocated
SCC to the SIP input queues by precedence.
17. SIP to NSS for messges from collocated SCC to network.
The SIP queues messages with Node destination or
network destination to the NSS.
18. Spare
19. MDS to SFS for control messages.
The MDS queues control messages to the SF queue.
20. SFS to NSS for outbound control messages.
The SFS queues control messages of MEDE type to
the NSS for forwarding over network to SCC.
Parameter description Real MTCB's Refer figure 7.1.1-2
for general layout.
Name APREC Value 0-6
Action precedence
0 S Super-Flash
1 Z Flash
2 Y
3 O
4 P Priority
5 M
6 R Routine
Name IPREC Value 0-6
Info precedence
As action precedence. If INFO precedence
not available, equal to Action precedence.
Name CLASS Value 0-14
Refer to Section 8.7
Name SPEC Value 0-3
Specat value
0: not specat
1: ATOMAL
2: CRYPTOSECURITY
3: EXCLUSIVE
Name MAIN TYPE Value 0-3
Message type
0: Narrative message
3: Node type control message
1: MEDE type control message
Name Length Value 12-9000
Message length
in bytes, always even
Name HDB ̲ADDRESS Value 0-110269
Name Additional information
Split in words 4,5,6,7
Details described for each case
15 14 13 12 11 10 9 8 7 6 5 4 3 2
1 0
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
^ ^ ^ ^ ^
^ ^
1 ^ APREC ^ IPREC ^ CLASS ^ SPEC ^ TYPE
^ Spare ^
^̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲^̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲^̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲^̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲^̲ ̲ ̲ ̲ ̲ ̲ ̲
̲^̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲^̲
^
^
2 ^ HDB ̲ADDRESS
^
^̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ^
^
^ ^
3 ^ LENGTH
^ ^
^̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲^̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲^̲
^
^
4 ^ WORD 4
^
^
^
^
^
5 ^ WORD 5
^
^ Additional
^
^ information
^
6 ^ WORD 6
^
^
^
^
^
7 ^ WORD 7
^
^̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲^̲
Figure 7.1.1-2
Real MTCB layout
Description of parameters in each case.
Real MTCB layout
Case 1 MES internal
(MES to PIP)
Loaded Modified
P̲a̲r̲a̲m̲e̲t̲e̲r̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲V̲a̲l̲u̲e̲ ̲ ̲ ̲ ̲ ̲ ̲M̲E̲S̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲M̲E̲S̲,̲P̲I̲P̲*̲
APREC X
IPREC X
CLASS X
SPEC X
TYPE 0 X
LENGTH X
HDB ̲ADDRESS -
WORD 4
WORD 5 Defined For MES
WORD 6 MES design use, see below
WORD 7 x
W 4 :
W 5 : DTG in (For status display)
W 6 : message length, excluded binary heder and
address list
W 7(left) : originator terminal number
W 7(right): status of message
0 : PRE , in preparation pool
1 : REL , sent for release
2 : COO , sent for coordination
3 : OUT , sent for print out
4 : PNF , preparation not finished
* Enqueued to PIP via pseudo MTCB.
PIP to modify status of W7 (right) if status of
messge = 3: OUT, sent for print out.
Real MTCB layout
2. MES release to MDS for local and outbound delivery
Loaded Modified
P̲a̲r̲a̲m̲e̲t̲e̲r̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲V̲a̲l̲u̲e̲ ̲ ̲ ̲ ̲ ̲ ̲M̲E̲S̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲M̲D̲S̲ ̲ ̲ ̲ ̲ ̲
APREC Loaded X
IPREC Loaded X
CLASS Loaded X
SPEC Loaded X
TYPE 0 X
LENGTH Loaded X
HDB ̲ADDRESS -
Word 4
Word 5
Word 6 Address list offset*
Word 7 0
*) Bytes, even.
Real MTCB layout
case 3 MDS to NSS for outbound delivery
Loaded Modified
P̲a̲r̲a̲m̲e̲t̲e̲r̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲V̲a̲l̲u̲e̲ ̲ ̲ ̲ ̲ ̲ ̲M̲D̲S̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲N̲S̲S̲ ̲ ̲ ̲ ̲ ̲
APREC Loaded
IPREC Loaded
CLASS Loaded
SPEC Loaded
TYPE 0
LENGTH Loaded
HBD ̲ADDRESS*
WORD 4 Routing ** X X
WORD 5 Mask X X
WORD 6 Retrieval X
WORD 7 time X
*) Loaded if messge on HDB
**) One bit per destination Node/MEDE excluding
local MEDE.
Real MTCB layout
case 3a MDS to SIP for messages with NATO-ANO's
(only on N/M E and K)
Loaded Modified
P̲a̲r̲a̲m̲e̲t̲e̲r̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲V̲a̲l̲u̲e̲ ̲ ̲ ̲ ̲ ̲ ̲M̲D̲S̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
APREC Loaded
IPREC Loaded
CLASS Loaded
SPEC Loaded
TYPE 0
LENGTH Loaded
HBD ̲ADDRESS*
WORD 4 Routing ** X
WORD 5 Mask X
WORD 6 Retrieval X
WORD 7 time X
*) Loaded if message on HDB
**) One bit per destination Node/MEDE,
If E is local MEDE then bit K is set
If K is local MEDE then bit E is set
Real MTCB layout
Case 4 MDS to SRS for storage
Loaded Modified
P̲a̲r̲a̲m̲e̲t̲e̲r̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲V̲a̲l̲u̲e̲ ̲ ̲ ̲ ̲ ̲ ̲M̲D̲S̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲S̲R̲S̲ ̲ ̲ ̲ ̲ ̲
APREC Loaded
IPREC Loaded
CLASS Loaded
SPEC Loaded
TYPE Loaded
LENGTH Loaded
HDB ̲ADDRESS - X
WORD 4 Reserved for
WORD 5 NSS
WORD 6 Retrieval* X
WORD 7 time X
*) MDS queues MTCB's with increasing retrieval time
to
the SRS.
Real MTCB layout
Case 5 MDS to PIP for local printout
Loaded Modified
P̲a̲r̲a̲m̲e̲t̲e̲r̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲V̲a̲l̲u̲e̲ ̲ ̲ ̲ ̲ ̲ ̲M̲D̲S̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲P̲I̲P̲ ̲ ̲ ̲ ̲ ̲
APREC Loaded
IPREC Loaded
CLASS Loaded
SPEC Loaded
TYPE 0
LENGTH Loaded
HDB ̲ADDRESS*
WORD 4 Reserved for
WORD 5 NSS
WORD 6 Retrieval** X
WORD 7 time X
*) Loaded if message on HDB
**) Loaded if not SH message.
Real MTCB layout
Case 6 SRR to PIP for retrieval with hardcopy
Loaded Modified
P̲a̲r̲a̲m̲e̲t̲e̲r̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲V̲a̲l̲u̲e̲ ̲ ̲ ̲ ̲ ̲ ̲S̲R̲R̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲P̲I̲P̲ ̲ ̲ ̲ ̲ ̲
APREC Loaded X
IPREC Loaded X
CLASS Loaded X
SPEC 0 X
TYPE 0 X
LENGTH Loaded X
HDB ̲ADDRESS Loaded X
WORD 4 -
WORD 5 -
WORD 6 Retrieval X
WORD 7 time X
Real MTCB layout
Case 7 SRR to MES for retrieval with display
Loaded Modified
P̲a̲r̲a̲m̲e̲t̲e̲r̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲V̲a̲l̲u̲e̲ ̲ ̲ ̲ ̲ ̲ ̲S̲R̲R̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲P̲I̲P̲ ̲ ̲ ̲ ̲ ̲
APREC Loaded X
IPREC Loaded X
CLASS Loaded X
SPEC 0 X
TYPE 0 X
LENGTH Loaded X
HDB ̲ADDRESS Loaded X
WORD 4 -
WORD 5 -
WORD 6 Retrieval X
WORD 7 time X
Real MTCB layout
Case 9 NSS to MDS for inbound or orbiting message.
Loaded Modified
P̲a̲r̲a̲m̲e̲t̲e̲r̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲V̲a̲l̲u̲e̲ ̲ ̲ ̲ ̲ ̲ ̲N̲S̲S̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲M̲D̲S̲ ̲ ̲ ̲ ̲ ̲
APREC Loaded X
IPREC Loaded X
CLASS Loaded X
SPEC Loaded X
TYPE 0 or 2 X
LENGTH Loaded X
HDB ̲ADDRESS - X
WORD 4 Reserved for
WORD 5 NSS
WORD 6 Address list
offset X
WORD 7 1 or 2 or 3* X
*) 1 = Normal case
2 = Orbiting message
3 = MEDE delivery + orbiting
Real MTCB layout
Case 10 NSS internal for message relaying (simultaneous
to MEDE delivery).
Loaded Modified
P̲a̲r̲a̲m̲e̲t̲e̲r̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲V̲a̲l̲u̲e̲ ̲ ̲ ̲ ̲ ̲ ̲N̲S̲S̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
APREC
IPREC
CLASS
SPEC
TYPE
LENGTH *
HDB ̲ADDRESS
WORD 4
WORD 5
WORD 6
WORD 7
*) In case of relay only NSS may dispose When simultaneous
to MEDE or SCC delivery cases 9 and 16 applies.
Real MTCB layout
Case 12 MES to PIP for distribute and retrieve
and distribute .
Loaded Modified
P̲a̲r̲a̲m̲e̲t̲e̲r̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲V̲a̲l̲u̲e̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲M̲E̲S̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲P̲I̲P̲ ̲ ̲ ̲ ̲ ̲
APREC** Loaded
IPREC** Loaded
CLASS Loaded
SPEC Loaded
TYPE 0
LENGTH Loaded
HDB ̲ADDRESS*
WORD 4 Reserved
WORD 5 NSS
WORD 6 Retrieval
WORD 7 time
*) Loaded if message on HDB
**) In the case Retrieve and distribute value 6
Real MTCB layout
Case 13 SRR to MES for retrieve and distribute
Loaded Modified
P̲a̲r̲a̲m̲e̲t̲e̲r̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲V̲a̲l̲u̲e̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲S̲R̲R̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲M̲E̲S̲ ̲ ̲ ̲ ̲ ̲
APREC Loaded X
IPREC Loaded X
CLASS Loaded X
SPEC 0 X
TYPE 0 X
LENGTH Loaded X
HDB ̲ADDRESS Loaded X
WORD 4 -
WORD 5 -
WORD 6 Retrieval X
WORD 7 time X
Real MTCB layout
Case 15 SRR to MES for readdressing
Loaded Modified
P̲a̲r̲a̲m̲e̲t̲e̲r̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲V̲a̲l̲u̲e̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲S̲R̲R̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲M̲E̲S̲ ̲ ̲ ̲ ̲ ̲
APREC Loaded X
IPREC Loaded X
CLASS Loaded X
SPEC 0 X
TYPE 0 X
LENGTH Loaded X
HDB ̲ADDRESS Loaded X
WORD 4 -
WORD 5 -
WORD 6 Retrieval X
WORD 7 time X
Real MTCB layout
Case 16 NSS to SIP for messages to colocated SCC
Loaded Modified
P̲a̲r̲a̲m̲e̲t̲e̲r̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲V̲a̲l̲u̲e̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲N̲S̲S̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲S̲I̲P̲ ̲ ̲ ̲ ̲ ̲
APREC Loaded X
IPREC Loaded X
CLASS Loaded X
SPEC Loaded X
TYPE Loaded X
LENGTH Loaded X
HDB ̲ADDRESS*
WORD 4 Reserved for
WORD 5 NSS
WORD 6 Used in NSS queuing
WORD 7 to MDS queue
*) Loaded if message is on Local MEDE HDB
Real MTCB layout
Case 17 SIP to NSS for messages from colocated
SCC to network and MEDE.
Loaded Modified
P̲a̲r̲a̲m̲e̲t̲e̲r̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲V̲a̲l̲u̲e̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲S̲I̲P̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲N̲S̲S̲ ̲ ̲ ̲ ̲ ̲
APREC Loaded X
IPREC Loaded X
CLASS Loaded X
SPEC Loaded X
TYPE Loaded X
LENGTH Loaded X
HDB ̲ADDRESS -
WORD 4 Routing* X X
WORD 5 Mask X X
WORD 6 Address list
offset X
WORD 7 1 X
*) Bits set for which routing is wanted, including
local MEDE if addressed.
Real MTCB layout
Case 19 MDS to SFS for control messages.
Loaded Modified
P̲a̲r̲a̲m̲e̲t̲e̲r̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲V̲a̲l̲u̲e̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲M̲D̲S̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲S̲F̲S̲ ̲ ̲ ̲ ̲ ̲
APREC Loaded
IPREC *
CLASS Loaded
SPEC Loaded
TYPE 2
LENGTH Loaded
HDB ̲ADDRESS -
WORD 4 Reserved
WORD 5 for NSS
WORD 6 *
WORD 7 1 or 3 **
*) Loaded with values WORD 6 and 7 in control message,
but has no meaning in this context.
**) A value of 3 indicates an orbiting control message,
which should be deleted by the SFS, and an alarm
should be enqueued in the AL queue.
Real MTCB layout
Case 20 SFS to NSS for outbound control messages.
Loaded Modified
P̲a̲r̲a̲m̲e̲t̲e̲r̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲V̲a̲l̲u̲e̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲S̲F̲S̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲N̲S̲S̲ ̲ ̲ ̲ ̲ ̲
APREC -
IPREC -
CLASS -
SPEC -
TYPE 2 X X
LENGTH Loaded X X
HDB ̲ADDRESS -
WORD 4 Routing mask* X X
WORD 5 X X
WORD 6 -
WORD 7 -
*) One bit set per destination MEDE, SCC.
7.1.1.2 M̲e̲s̲s̲a̲g̲e̲ ̲T̲r̲a̲n̲s̲i̲t̲i̲o̲n̲ ̲a̲t̲ ̲t̲h̲e̲ ̲S̲C̲C̲
The functions at the SCC are performed by the following
subsystems/processes:
o Nodal Switch Subsystem
o Network Supervision and Control Subsystem
o Network Statistic Subsystem
o Messae Service Subsystem
o NICS-TARE Subsystem
o ISH-collocated N/M Interface (CIP) Process
The following message transition cases can be identified.
Refer to figure 7.1.1-3.
Figure 7.1.1-3
MTCB Transition
F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲D̲e̲s̲c̲r̲i̲p̲t̲i̲o̲n̲ ̲o̲f̲ ̲T̲r̲a̲n̲s̲a̲c̲t̲i̲o̲n̲ ̲C̲a̲s̲e̲s̲
N̲a̲r̲r̲a̲t̲i̲v̲e̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲:̲
N1. N̲S̲S̲ ̲t̲o̲ ̲I̲S̲H̲-̲C̲I̲P̲ ̲f̲o̲r̲ ̲i̲n̲b̲o̲u̲n̲d̲ ̲d̲e̲l̲i̲v̲e̲r̲y̲ ̲(̲M̲D̲Q̲)̲
The NSS will queue inbound messages, i.e. narrative
messages with SCC or NICS-TARE as destination to
the ISH-CIP for distribution.
N2. I̲S̲H̲-̲C̲I̲P̲ ̲t̲o̲ ̲N̲S̲S̲ ̲f̲o̲r̲ ̲o̲u̲t̲b̲o̲u̲n̲d̲ ̲d̲e̲l̲i̲v̲e̲r̲y̲ ̲(̲T̲Q̲)̲
The ISH-CIP will queue narrative messages having
destinations within the FIKS network to the NSS.
N3. I̲S̲H̲-̲C̲I̲P̲ ̲t̲o̲ ̲M̲S̲S̲ ̲f̲o̲r̲ ̲c̲o̲n̲v̲e̲r̲s̲i̲o̲n̲ ̲(̲C̲Q̲4̲)̲
The ISH-CIP will queue narrative messages, which
have to be converted from SMF to ACP127 format
before transmission to NICS-TARE.
N4. I̲S̲H̲-̲C̲I̲P̲ ̲t̲o̲ ̲M̲S̲S̲ ̲f̲o̲r̲ ̲c̲o̲n̲v̲e̲r̲s̲i̲o̲n̲ ̲(̲C̲Q̲3̲)̲
The ISH-CIP will queue narrative messages, which
have to be converted from ACP127 (enclosed in a
SMF envelope) to SMF before the message is returned
to the FIKS network.
N5. I̲S̲H̲-̲C̲I̲P̲ ̲t̲o̲ ̲M̲S̲S̲ ̲f̲o̲r̲ ̲c̲o̲n̲v̲e̲r̲s̲i̲o̲n̲ ̲(̲C̲Q̲2̲)̲
The ISH-CIP will queue narrative messages, which
have to be converted from SMF to ACP127 (enclosed
in a SMF envelope) before the messge is returned
to the FIKS network.
N6. I̲S̲H̲-̲C̲I̲P̲ ̲t̲o̲ ̲M̲S̲S̲ ̲f̲o̲r̲ ̲i̲n̲t̲e̲r̲c̲e̲p̲t̲ ̲(̲I̲Q̲)̲
The ISH-CIP queues messages, which have been returned
from NSS because of transmission error, or unrecognized
messages retrieved from MDQ, to the MSS for interception.
N7. M̲S̲S̲ ̲t̲o̲ ̲I̲S̲H̲-̲C̲I̲P̲ ̲f̲o̲r̲ ̲o̲u̲t̲b̲o̲u̲n̲d̲ ̲d̲i̲s̲t̲r̲i̲b̲u̲t̲i̲o̲n̲ ̲(̲N̲M̲)̲
MSS queues narrative messges with destination within
the FIKS network to the ISH-CIP for distribution.
The messages may hereby be SMF or SMF messages
enclosing an ACP127 message.
N8. M̲S̲S̲ ̲i̲n̲t̲e̲r̲n̲a̲l̲ ̲(̲I̲Q̲)̲
A message in error by conversion is delivered for
intercept.
N9. M̲S̲S̲ ̲t̲o̲ ̲N̲T̲S̲ ̲f̲o̲r̲ ̲m̲e̲s̲s̲a̲g̲e̲ ̲t̲r̲a̲n̲s̲m̲i̲s̲s̲i̲o̲n̲ ̲(̲N̲T̲)̲
The MSS queues an outbound message, i.e. with NICS-TARE
as destiation, to the NTS.
N10.N̲T̲S̲ ̲t̲o̲ ̲M̲S̲S̲ ̲f̲o̲r̲ ̲m̲e̲s̲s̲a̲g̲e̲ ̲c̲o̲n̲v̲e̲r̲s̲i̲o̲n̲ ̲(̲C̲Q̲1̲)̲
The NTS queues an ACP127 formatted message, i.e.
with destinations within the FIKS network, to the
MSS.
N11.M̲S̲S̲ ̲t̲o̲ ̲H̲S̲P̲,̲ ̲p̲r̲i̲n̲t̲o̲u̲t̲ ̲(̲R̲E̲P̲)̲
During intercept handling, the MSS may deliver
a narrative message concerning the intercept event
to the HSP for printout.
M̲T̲C̲B̲ ̲L̲a̲y̲o̲u̲t̲ ̲f̲o̲r̲ ̲N̲a̲r̲r̲a̲t̲i̲v̲e̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲
Figure 7.1.1-4
SCC Narrative Message MTCB General Format
…0c…insert table…0c…
…0c…insert table…0c…
Layout for: REAL ̲IX and REAL ̲2X
Figure 7.1.1-5
MTCB Layout for Cases: Narrative Message Between NSS and ISH
Layout for: REAL ̲3X, REAL ̲4X, REAL ̲5X and REAL ̲7X
Figure 7.1.1-6
MTCB Layout for Cases: Narrative Messages Between ISH and MSS
Layout for: REAL ̲6X and REAL ̲8X
Figure 7.1.1-7
MTCB Layout for Cases: Narrative Message for Intercept
Table 7.1.1-1
Case 6 and 8, MTCB Variables
Layout for: REAL ̲9X
Figure 7.1.1-8
MTCB Layout for Case 9: Narrative Message MSS to NTS
Layout for: REAL ̲10X
Figure 7.1.1-9
MTCB Layout for Case: Narrative Message NTS to MSS
C̲o̲n̲t̲r̲o̲l̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲:̲
C1. N̲S̲S̲ ̲t̲o̲ ̲I̲S̲H̲-̲C̲I̲P̲ ̲f̲o̲r̲ ̲i̲n̲b̲o̲u̲n̲d̲ ̲d̲e̲l̲i̲v̲e̲r̲y̲ ̲(̲M̲D̲Q̲)̲
The NSS will queue inbound messages, i.e. control
messages with SCC as destination, to the ISH-CIP
for distribution.
C2. I̲S̲H̲-̲C̲I̲P̲ ̲t̲o̲ ̲N̲S̲S̲ ̲f̲o̲r̲ ̲o̲u̲t̲b̲o̲u̲n̲d̲ ̲d̲e̲l̲i̲v̲e̲r̲y̲ ̲(̲T̲Q̲)̲
The ISH-CIP will queue `control messages havig
destinations within the FIKS network (this includes
the remote SCC) to the NSS.
C3. I̲S̲H̲-̲C̲I̲P̲ ̲t̲o̲ ̲N̲S̲C̲ ̲d̲e̲l̲i̲v̲e̲r̲y̲ ̲(̲C̲M̲)̲
The ISH-CIP queues all incoming control messages,
which are not ISH internal, to the NSC.
C4. N̲S̲C̲ ̲t̲o̲ ̲I̲S̲H̲-̲C̲I̲P̲ ̲f̲o̲r̲ ̲o̲u̲t̲b̲o̲u̲n̲d̲ ̲d̲i̲s̲t̲r̲i̲b̲u̲t̲i̲o̲n̲ ̲(̲N̲C̲)̲
The NSC queues outgoing control messages to the
ISH-CIP.
C5. N̲S̲C̲ ̲t̲o̲ ̲N̲E̲S̲ ̲s̲t̲a̲t̲i̲s̲t̲i̲c̲a̲l̲ ̲d̲a̲t̲a̲ ̲r̲e̲c̲o̲r̲d̲ ̲d̲e̲l̲i̲v̲e̲r̲y̲ ̲(̲N̲S̲)̲
The NSC hands over statistical data records received
from the FIKS network to the NES.
C6. N̲E̲S̲ ̲t̲o̲ ̲N̲S̲C̲ ̲s̲t̲a̲t̲i̲s̲t̲i̲c̲a̲l̲ ̲d̲e̲l̲i̲v̲r̲y̲ ̲(̲C̲M̲)̲
Upon completion of statistic generation, the NEC
delivers the result in a control messge, to the
NSC.
C7. N̲S̲C̲ ̲t̲o̲ ̲H̲S̲P̲,̲ ̲c̲o̲n̲t̲r̲o̲l̲ ̲m̲e̲s̲s̲a̲g̲e̲ ̲(̲R̲E̲P̲)̲
NSC sends control message to HSP in order to supervise
how reports and diagnostics should be output to
the printer.
C8. M̲S̲S̲ ̲t̲o̲ ̲N̲T̲S̲ ̲L̲i̲n̲k̲ ̲C̲o̲n̲t̲r̲o̲l̲ ̲B̲l̲o̲c̲k̲s̲ ̲(̲I̲L̲Q̲)̲
The MSS forwards Link Control Blocks to the NTS
for transmission.
C9. N̲T̲S̲ ̲t̲o̲ ̲M̲S̲S̲ ̲L̲i̲n̲k̲ ̲C̲o̲n̲t̲r̲o̲l̲ ̲B̲l̲o̲c̲k̲s̲ ̲(̲I̲L̲Q̲)̲
Received Link Control Blocks are delivered to the
MSS for onward processing.
M̲T̲C̲B̲ ̲L̲a̲y̲o̲u̲t̲ ̲f̲o̲r̲ ̲C̲o̲n̲t̲r̲o̲l̲ ̲M̲e̲s̲s̲a̲g̲e̲s̲
Figure 7.1.1-10
General Control Message MTCB Format (Except Case C2)
DATA DESCRIPTION FOR C̲o̲n̲t̲r̲o̲l̲ ̲M̲e̲s̲s̲a̲g̲e̲ ̲M̲T̲C̲B̲ ̲F̲o̲r̲m̲a̲t̲
…0c…insert table…0c…
Layout for: REAL ̲1CX
Figure 7.1.1-11
Control Message MTCB Format for Case C1
Layout for: REAL ̲2CX
ROUTM 0,1 , pleae refer to binary header description (Sec. 10.2)
Figure 7.1.1-12
Control Message MTCB Format for Case C2
…02…A̲S̲M̲-̲M̲e̲s̲s̲a̲g̲e̲:̲
…02…Refer to NICS TARE FIKS INTERFACE UPDATE,
…02…FXA/SDS/002, sec 2.1 for detailed description
…02…of the function of the ASM-message
1 + 2) Byte offset in message (incl. bin. header)
Figure 7.1.1-13
SCC ASM Message MTCB General Format
