Ma CS: System Manual Vol. 2

SE R VE R
MA NUA L
ma cs
®
management administration communication system
System Manual Vol. 2

System tables
Innovation. Experience. Flexibility. Quality.

Server Manual Vol. 2 - System tables
Table of Contents
3. TABLES......................................................................................................................................................... 3
3.1. Table concept...................................................................................................................................................... 3
3.2. System table (sys.tab)............................................................................................................................................ 5
3.3. Basic configuration tables..................................................................................................................................... 6
3.3.1. Process Table (pn.tab).............................................................................................................................. 6
3.3.2. Connection Table (cn.tab, cnArr.tab, cnDep.tab, cnCs.tab)......................................................................... 8
3.3.3. Field format Table (ff.tab)......................................................................................................................... 9
3.3.4. Device Table (dv.tab)............................................................................................................................. 11
3.3.5. Time Parameter Table (at.tab)................................................................................................................. 13
3.3.6. Line format Table (lf.tab)........................................................................................................................ 13
3.3.7. Action Scheduler Table (as.tab)............................................................................................................... 14
3.3.8. File Table (fi.tab)................................................................................................................................... 14
3.3.9. Display Table (dp.tab)............................................................................................................................ 15
3.3.10. Selection Table (se.tab).......................................................................................................................... 17
3.3.11. External Error Checks (ec.tab)................................................................................................................ 19
3.3.12. CPU Table (cpu.tab).............................................................................................................................. 19
3.3.13. Message Table (msg.tab)....................................................................................................................... 20
3.3.14. Time Scheduler Table (ts.tab).................................................................................................................. 22
3.3.15. Watchdog table (wdog.tab).................................................................................................................... 23
3.4. Record description tables (xxx.dsc)....................................................................................................................... 23
3.5. Display content tables (dpc.xxx)........................................................................................................................... 26
3.6. Lookup tables.................................................................................................................................................... 27
3.6.1. Airports................................................................................................................................................ 27
3.6.2. Remarks............................................................................................................................................... 27
3.6.3. Airlines................................................................................................................................................. 28
3.6.4. Natures................................................................................................................................................ 28
3.6.5. Aircraft................................................................................................................................................. 28
3.7. Output handler specific tables............................................................................................................................. 28
3.7.1. Graphic-Terminal-Table.......................................................................................................................... 28
3.7.2. FIIB Tables............................................................................................................................................ 29
Page 2 ServerManual-Vol2_content_1.0062_rev00
3. TABLES
The FIDS (Flight Information Display System) keeps virtually all relevant data in memory-resident
tables when in operation. For throughput reasons, this is vital, particularly with reference to the
updating of information data on the display peripherals.
All tables are normally located in the directory/app/sint2/tab in the form of text files which
are read when the system is booted by the SYSTRT process and are converted into an internal
format.
3.1. Table concept

All tables used in FIDS are in the form of text. This offers the advantage of allowing them to be
generated, changed and read with any editor even on other systems in a problem free manner.
All these tables are read by the machine-independent, i.e. portable, software module
‚tabload ’ and converted into an internal format adapted to suit the machine used for each
installation. This module is used by the SYSTRT process when the system receives a cold boot
(‚No System Table Recovery’).
In terms of data organisation, a distinction is made between the following types of table:
KEY table
A KEY type of table has a key described in terms of a length and an offset. The length is
described by descriptor $KEYSIZ and the offset is defined by the descriptor $KEYLOC. KEY
tables are always sorted in rising numerical order and every key in the table must be unique.
Direct access to KEY tables are performed by a binary search (halving procedure).
Data sets are sorted by converting the KEY table into the internal format. The loading module
‚tabload ’ does not therefore require the data records to be sorted in advance in the table
presented in text form.
INDEX table
The INDEX type of tables do not have a key. Access to these is exclusively via the record
number in the table. The first valid record number is 0. The configuration of an INDEX table
is based on the largest index of a record in the table, provided that the tables has not been
given an oversize configuration by the directive $LIM. If the indices used in the table contain
gaps, dummy entries can appear in the table showing a data record length set to binary 0.
If you wish to save memory space, it is therefore necessary to use as many adjacent indices
as possible. Access to INDEX tables is extremely fast because every record address has to be
determined precisely.
The first component in the $FORMAT descriptor of an INDEX- and FIELD table must be of the
INTEGER (I) type. This indicates the access index of every data record. At a later point, this
component is not physically transferred to the data record.
FIELD tables
For data records which are required to have a dynamic structure and/or meant to be read
using user transactions, a record description is required. For every record description,
the FIDS has what is known as a record description table of the FIELD type. These tables
contain all the record descriptions (one table entry per field) of a data record. In terms of
data organisation, these are all INDEX tables. However, in contrast to these Index 0 is not
permitted. This data record is used internally. The first permitted field number (index) in a
data record is therefore 1.
The organisation type of a table is defined in the system table (sys.tab) for each individual
table.
In addition to actual table data, each table in the system contains up to 4 descriptors which
determine the size and organisation of the table. All descriptors contain a line of data and
begin with a key word (e.g. $LIM). A parameter entry follows after one or more blanks. The
key word can be entered in upper case or lower case and, as a rule, descriptors are usually
listed in the first lines of a table. However, this is not mandatory.
ServerManual-Vol2_1.0062_rev00 Page 3
The distinction is made between the following descriptors:
$KEYSIZ
This descriptor is only required for the KEY type of table and it indicates the key length of the
table record in characters/bytes. Only positive values are permitted. There is no default value.
Example: $KEYSIZ 5 (key length 5 characters)
$KEYLOC
If the key for a data record does not start at the beginning of a record, the offset (relative to
0) must be indicated. Only positive values or zero are permitted. The default value is 0. In this
case, the $KEYLOC descriptor can be omitted.
Example: $KEYLOC 2 (the key begins in the third character of the record)
$LIM
Normally, a table is configured implicitly, i.e. its size is initialised in accordance with the number
of data records in such a way that all data records fit in the table. If the $LIM descriptor is listed
in the table, the number of data records to be listed in the table can be determined with an
appropriate parameter entry. This is particular important for Lookup tables for which there is a
user function. This then makes it possible for users to insert any additional data records in the
table.
Example: $LIM 200 (table with maximum of 200 records)
$FORMAT
This descriptor informs the software module ‚tabload ’ of the format in which the text data
should exist in that table (i.e. strings, numerical values in various display modes etc.) The
components of a data record are separated from one another by commas.
Every component can be identified by a letter. The sequence of field components indicates the
physical field sequence in the data record..
Example: $FORMAT C,B,C2,I,I,>16
If ( $FORMAT DSC ) is specified, the format of a data record of the table is defined by the
connected FIELD table.
Example: ($FORMAT DSC) in the table ap.tab
The fields for this table are defined in the table ap.dsc. The connection between
the tables ap.tab and ap.dsc is done in the table sys.tab.
The following field components are permitted:
CHARACTER (C)
The field component ‚C’ indicates that the next character can be transferred in direct physical
form to the data record without conversion (e.g. C15 for 15 characters). In all field components,
leading and trailing blanks are eliminated. If explicit blanks are used in the CHARACTER- or
STRING component, these should be included in ‚„‘ (inverted commas).
STRING (>)
The field component ‚>‘ is equivalent to the ‚C’ component. However, the field is prepared
as a C-String, i.e. forced termination is zero. For example, if a string 20 characters in length
is defined with > 20, only 19 can be used in data records because the blank after the data
contains a zero terminator (‚C’ language concept).
INTEGER (I)
A leading ‚I’ designates an INTEGER component, i.e. a whole number follows which is
converted internally into a machine-dependent natural word size and/or register size and then
stored internally in binary form. The display can be decimal (e.g. 24, -3 or +8), hexadecimal
(e.g. $1B), octal (e.g. 057) or binary (e.g. %1001101) by using appropriate prefixes ($,0 and %) to
indicate these. Prefixes are only permitted in the decimal presentation mode. In the other display
modes, this preface function is performed by appropriate combinations of two characters.
Page 4 ServerManual-Vol2_1.0062_rev00
SHORT (S)
A whole number SHORT value can be entered in a similar way to the INTEGER component.
LONG (L)
A whole number of LONG values can be entered in a similar way to the INTEGER component.
BYTE (B)
In a similar way to the INTEGER component, a whole number value for a byte can be entered.
Data entry is restricted by the physical limitation to the values of $00 to $FF (hex.). Naturally
enough, this also applies to all other binary components (INTEGER, LONG, SHORT), the
physical size of which should be known on the target machine.
There are data default values for all components in a data record which apply if ever the
components in the data of a record are not indicated, or are only indicated by blanks. The
component types CHARACTER and STRING are set to blanks (STRING is also set to length 0 by
a zero terminator) and the binary types INTEGER, LONG, SHORT and BYTE have a default value
of 0.
It is not normally possible to record whitespace characters such as a tab or an ESC symbol in
a CHARACTER or STRING component. To make this possible, these components use a display
mode such as that used for C compilers. Whitespace characters are recorded with a ‚\’
(Backslash) character and octal display of a character is recorded in a string.
In addition to this octal display, there are also special symbols such as \t (tab), \n (linefeed),
\b (backspace), \f (formfeed), \r (carriage return) and \\ for the ‚\’ character itself. The
benefit of these special symbols is that any computer can convert them to the characters which
it uses.
Display of the octal bit pattern is only set to 3 characters if numerical ASCII characters follow
which have to be incorporated in the string as normal ASCII characters. For instance \33AB
is permitted and would give rise internally to hex. 1B4142, but \3312 would give rise to D932,
instead of 1B3132. The correct format here would be \03312.
Always ensure that a zero terminator is generated with \000. If this value is used in a STRING
component, the string is terminated at this point.
Example for a CHARACTER component with whitespace characters:
\00101\002\033A\nB\t (Hex: 01 30 31 02 1B 41 0A 42 09)
As a general principle, please note that any number of blank lines can be inserted in the text file
of a table alongside the descriptors and data records. They are simply ignored. Comments can
be introduced with the string ‚/*’. Everything which appears to the right of this is interpreted as
a comment.
If data records do not fit into one physical line, then this line must be terminated with ‚-’ and
can be continued in the next line in the first columne.
3.2. System table (sys.tab)

The system table (sys.tab) in FIDS/Linux is the „table of tables“. The start-up process SYSTRT
reads out this table, calculates the memory requirement for the sharable memory segment for
the system tables (SEG _ STH), the loads the tables using the ‚tabload ’ software module.
The system table is an INDEX type of table. Every table entry in the system table has a unique
number which is used in this table as an index. Table numbers 1-30 are reserved in the
system by basic functionality (0 is not used). All other table numbers can be used freely for
configurations.
A data record in the system table contains the following field components:
TABLE NUMBER,INTEGER (I)

Access index for the table
BCB ADRESS DUMMY,LONG (L)

This LONG component is a space mark for the internal byte offset of a given table in the system
table memory segment (SEG _ STH). No data are entered at this point.
TABLE DESCRIPTION LINK,INTEGER (I)

In the case of table containing data records for which there are record descriptions in a record
description table, the number of this table is entered at this point. With the record description
table itself, a backwards link to the data table must also be entered.
TABLE TYPE,CHARACTER (C)

At this point, the type of table is entered by a key letter. INDEX-Table (I), KEY-table (K) and
FIELD table or record description table (F).
CHANGE FLAG,CHARACTER (C)

If the data can be changed while the FIDS is running, this should be designated by entering the
letter ‚Y’. This is important because without this, access using semaphore SEM _ STH cannot be
synchronised.
RECOVERY FLAG,CHARACTER (C)

This flag determines whether a backup copy is made when required for a table which records
the current data status in the powered up system. In the event of a recovery start, the table
is then not loaded „cold“ by the ‚tabload ’ software module but is instead loaded from the
backup file.
This component has the following options: ‚N’ for no recovery, ‚Y’ for recovery and ‚X’ for tables
which should be loaded from the recovery file, even in the event of a cold start provided that
a recovery file exists. This is a worthwhile approach in practice, especially for lookup tables
containing data which change over time and for which, under certain circumstances, there is no
need to load a current set of cold start data records.
PATHNAME,STRING (>64)
All tables in the FIDS can be found in the directory /app/sint2/tab. The path name of every
table can be entered in this component. 63 characters are available for this. One character is
required for the zero terminator.
3.3. Basic configuration tables

The basic configuration tables form part of the system tables for which the functionality of the
FIDS is vital. In fundamental terms, this applies to tables numbers 1 to 29.
3.3.1. Process Table (pn.tab)
The process table (pn.tab), with a few exceptions, contains all processes which the FIDS requires
for its work, always depending on prevailing requirements. The process table is of the INDEX
type. The number of the process is used as an index. The table is read out by the mother
process BIGMAMA when the system is powered up. BIGMAMA then generates all the processes
listed in this table.
A data process table contains the following field components:
PROCESS NUMBER,INTEGER (I)

Access index for the table
PROCESS NAME,STRING (>16)

System name of process
BOUND UNIT,STRING (>16)

Name of the executable program. The path name is generated by the mother process
BIGMAMA, which generates all processes.
SWAPPING FLAG,CHARACTER (C)

This flag defines whether a process can be moved out to hard disk by the Linux operating
system or whether it is required to remain memory-resident at all times. This „non-swapping“ is
particularly interesting for processes which are required to achieve very rapid response times.
Once a process has been moved out to hard disc, it can at times take a couple of seconds until
this has been reloaded in memory and is able to perform its task. Swapping (Y), No Swapping
(N).
PROCESS TYPE,CHARACTER (C)

For internal purposes every process should be classified by this components. Distinctions are
made between control processes (C), daemon processes (D), transaction processes (T) and
output handler processes (O).
PROCESS ID,INTEGER (I)

This field component is a dummy for the process ID, which a process sets when it is generated
by the BIGMAMA mother process, once it has completed its initialisation work. In the event
of termination, a process returns its process ID to zero once it has completed its termination
work. The processes BIGMAMA and SYSDWN use this change in process ID to establish whether
the process has responded as expected. The process ID should be set to zero (default for an
INTEGER component).
NETWORK PORT NUMBER,INTEGER (I)

Processes which communicate via the network require for this a unique, logical number with
which they can be reached by others on the local computer. This is why the network port
number exists. There must not be any overlaps with the numbers issued by the Linux system. This
can be established by consulting the file /etc/services. There is no problem with numbers above
5000.
PRIORITY,INTEGER (I)
In order to change process priorities in the system when required, every process can be
assigned a priority which it sets itself during the initialisation phase. This is what is known as
a „nice value“ which can accept values of between -20 and 19. Priority -20 is the highest of
these.
PROCESS MODE BITS,INTEGER (I)

Every entry in the process table has a process mode word in which the process can be offset in
various modes in a bit-encoded manner. This occupies the 8-lowest value bits of a word, i.e. bit
0-7. Bit 0 is known as the RESPAWN bit. A process against which this bit is set whenever it is
terminated abnormally is regenerated (respawned) by the mother process BIGMAMA .
The TRACEMODE (Bit 1) is provided, in particular for the output handler processes. All
I/O data movements are displayed on the system console or written to a log file in dump
form (Hex.- and character display mode) when the process is running in TRACE mode. If the
TRACEMODE is set on a process, the display also shows which data have been received by this
input queue (software module ‚mget1’). A process can also be moved into TRACEMODE for
system runtime using the ‘tracemode’ commands.
The NO-WAIT-FOR-READY Bit (Bit 2) can be used if a process is intended to generate

its input queue and wait for data input before the system has been placed in READY status.
This is of interest, for example, for the OHDPRT which has to output loading messages for
the actual database on the printer before the time scheduler TIMSCH places the FIDS in the
READY status.
The PROCESS-LOGGING Bit (Bit 3) not used
NO MGET1 BLOCKING (Bit 4) means that the affected process can poll its input queue
using the mget1() function without blocking. This is important for some processes because
they do not respond sequentially to queue inputs but instead perform other work at the same
time.
The WRITE-DIRECT Bit (Bit 5) not used
Bit 6 of the „PROCESS MODE“ word is the NO _ OBSERVE bit. This bit is only of interest to
output handlers responsible for the output of information to display peripherals.
Once the bit has been set, a display controller which has been put „out of service“ by the
output handler responsible due to a defect or interrupt in communication can only be put
back into service by the relevant user command ‚UP‘. If this bit is not set, the output handler
process automatically attempts, at cyclical intervals, to re-establish contact with affected
controllers, provided it is prompted by the CMD _ CYCLE command (--> time scheduler table
ts.tab).
Bit 7 is know as the TESTMODE bit. This can be set in the process table, or by the
‚testmode‘ command which, in principle, operates like the ‚tracemode‘ command and
switches the bit on or off. This bit can be evaluated for each individual process. There is no
defined response when setting the bit.
MAX-QUEUE-ENTRY-SIZE,INTEGER (I)
Every process can use this entry to assign memory space to its input buffer. If there is insufficient
space in memory, a system message (SYSERR) is output to the console by the software module
‘callp’. Always ensure that the queue entry size of the ICPUT process does not exceed the
maximum system-dependent message size of the UDP service (1024 bytes). This precise
parameter is used by the ICINIS process for initialisation of slave computers.
TARGET CPU NUMBER,INTEGER (I)

Here, the logical CPU or computer number is entered on which the process is to run. Number
1 usually indicates the MASTER computer. Entering a zero means that this process is intended to
run on all computers defined in the CPU table (cpu.tab) on the FIDS/Linux network. An entry in
this component is covered by the logical CPU number from the CPU table (cpu.tab). Restrictions
are explained in the relevant chapter for multi-computer configurations.
TASK QUEUE SIZE,INTEGER (I)

Here, the size of input queue can be determined for every process. This indication should be
in bytes and it determines the memory allocation in the process queue segment on the relevant
target computer.
REFERENCE,INTEGER (I)
This component is used for task-specific process references and can be used in different ways
from one process to another, as required. The output handler processes use this component to
obtain a reference to their handler-specific table.
TRACE FILE,STRING (>32)

If a path name is entered at this point, the output which is generated when the TRACEMODE bit
of a process is set, is not written to the console but is instead written to the appropriate file. If
this file does not exist, it will be created.
UPDATE TIME INTERVAL,INTEGER (I)

The maximum difference between 2 queue inputs in seconds. The process ‚fthcheck ‘ verifies
the last queue update time of the process and restart it, if the update time interval is exceeded.
3.3.2. Connection Table (cn.tab, cnArr.tab, cnDep.tab, cnCs.tab)
Something known as a „connection“ can be made to all data records in the FIDS for which
there is a record description. This may be an interpreter expression used for a given record
in a file and which leads to an assessment of TRUE or FALSE. If an expression of this kind is
assessed as TRUE there is a second step in which the data record is assessed further and this is
linked to an assignment function.
In other words, depending on the contents of certain fields, other fields can be changed.
The software modules ‚sth’ and ‚fth’, all of which control changes in a central manner to
system tables and the actual database all use a software module which checks and executes
„connections“. Logical links of this kind are entered in the connection table (cn.tab) for system
tables, (cnArr.tab) for arrival flight table, (cnDep.tab) for departure table and (cnCs.tab) for
master-codeshare connection . These tables are of the KEY type. The access key covers several
fields. The connection table is searched by the relevant software module for all assessments
which suit the record description number of the file.
A data record in the connection table contains the following fields:
RECORD DESCRIPTION TABLE NUMBER,INTEGER (I)

The highest key term is the record description number, i.e. the table number under which the
record description of a file is entered in the system table (sys.tab).
FIELD NUMBER,INTEGER (I)

This is where the field number should be entered which determines changes to be made to a
different field. It is entirely possible for several field numbers to be contained in the assessment.
However, particular attention should be paid to ensuring that the correct processing sequence
is followed if any of these changes initiates recursive secondary changes. This field component
forms part of the access key.
CORRESPONDING FIELD NUMBER,INTEGER (I)

This is where to enter the field number which should be changed. This field component is part
of the access key.
CONTINUATION,CHARACTER (C)
If there are several identical pairs of field numbers (FIELDNUMBER and CORR. FIELD NUMBER)
due to a range of different assessment variants, the uniqueness of the access key and the
connection table should be protected by the alphanumeric character entered here.
This field component is part of the access key.
MAKE CONNECTION ALL TIME,CHARACTER (C)

Enter (N)o in this component whenever the assignment for TRUE assessment should only occur
when the CORR.FIELD has no contents, i.e. while it is still empty. Otherwise, enter (Y) yes at this
point. The target field contents are then reassessed on each occasion.
CONDITION/EXPRESSION,STRING (>170)
A STRING type of field component with dynamic length takes the assessment expression as well
as the assignment expression used whenever the assessment ends with TRUE. First of all, the
assessment expression is entered and separated by the keystroke sequence ‚\n’ (Newline), the
expression for assignment.
Example: [N80]==[>LN]\n [N27]=[*]
This can mean, to take one example, that the current time (*) is entered in the ACTUAL TIME
field (field number 27 in af.dsc ) when the REMARK field (field number 80 in af.dsc) has the
contents ‚LN‘ .
3.3.3. Field format Table (ff.tab)
The line format of print lines and display lines on display devices comprises 1 to N field formats
which, in overall terms, produce the line format. All field formats can be identified uniquely
by their field format number and are defined in the field format table (ff.tab). In overall terms,
it is possible to distinguish between two types of field format. On the one hand, there are field
formats with a reference to field numbers, i.e. the contents of a field for a data record is output,
and on the other hand there are data contents. The field format table is of the INDEX type. The
field format number represents the index and must be >0.
A data record in the field format table contains the following field components:
FIELDFORMAT NUMBER,INTEGER (I)

Access index for the table.

If the contents of a field should be output for a data record, the field number must be entered
here.
DESTINATION SIZE,INTEGER (I)

Output width of field in characters.
TEXT TABLE ENTRY NUMBER,INTEGER (I)

If an entry is to be output from the text table (tx.tab) or is to serve as the output format for time,
date or a numerical value, the number of the text table entry must be entered. Possible formats
are „99:99“ for a time or „ZZZ9“ for a 4-digit output with suppressed, leading zeros. A ‚9’
represents a numeral (0-9). To suppress leading zeros, the character ‚Z’ can be used. Other
characters which can be incorporated in the format are output at the same time.
TABLE LINK,INTEGER (I)

In the case of field translations of lookup table keys, the number of the lookup table should
be entered. In the case of text constants, this field is used as an output mutiplier for the text
constant provided that a value of >1 is indicated.
FIELD LINK,INTEGER (I)

In the case of field translations of lookup table keys, the field number of the lookup table record
should be entered here.
FORMAT,INTEGER (I)
The output format is set in a bit-encoded manner:
Bit 0: Right alignment
Bit 1: Left alignment
Bit 2: Reverse output
Bit 3: cut trailing spaces
Bit 4: center output
Bit 5: compress
Bit 6: uppercases
Bit 7: lowercases
Bit 8: no digits
Bit 9: no alpha
Bit 10: only alphas
Bit 11: only digits
Bit 12: terminate with NL \n 0x0a
Bit 13: terminate with CR \r 0x0d
Bit 14: terminate with FF \f 0x0c
Bit 15: terminate with TAB \t 0x09
Bit 16: Flight Number Digit portion only
Bit 17: ARABIC Translation
Bit 18: Use Translation Table
Bit 19: Application Bit 1 ( not used )
Bit 20: Application Bit 2 ( not used )
Bit 21: Ansi to Dos
Bit 22: Arabic adjustment
Bit 23: Unicode
TRANSLATION,CHARACTER (C)
If this involves a field in a lookup table field, i.e. if the contents can be used to access a record
in a lookup table, and if a field from the appropriate lookup table record is to be output instead
of the field contents which represent the key, enter a ‚Y‘ TRANSLATION. Otherwise, enter ‚N‘ for
(N)o translation.
TEXT TABLE REPRESENTATION,CHARACTER (C)

The contents of a field are represented by the index number in a text table entry. If a ‚Y‘ is
entered here as appropriate, the type of field must naturally be numerical since it is being used
as the access index for the text table (tx.tab). The text table entry is output here.
TEXT CONSTANT,STRING (>NNN)

At this point, a text constant with dynamic length can be indicated. In principle this involves the
same procedure as indication of a text table entry. The text string can feature any value at all
using octal presentation in the style of the „C“ language.
e.g. „\001\033A\003\004“
Basic rules for the creation of field formats:
If an output width is indicated, this is usually expressed in terms of its width. Otherwise, the
output width is implicit, i.e. it is determined by a text format (text table) or TEXT CONSTANT or
by the field length.
A text constant in the field format has priority over a text table entry.
If an explicit output width is indicated, output is either cut off as required or filled with blanks.
If the field which is to be output is a numerical, a time or a date field, an output format can
be specified by a text reference in the style of the Cobol language, e.g. „ZZZ9“ or „Z9:99“.
3.3.4. Device Table (dv.tab)
The device table (dv.tab) contains a list of all the peripheral devices connected to the Linux
computer including all the computers configured in the network i.e. in the CPU table (cpu.tab).
In detailed terms, these are the console, the interfaces, the display peripherals, etc.
The type of table is KEY, and the key term is the system-internal device name.
A data record in the device table contains the following fields:
DEVICE TYPE,CHARACTER (C)

This field categorises the peripherals as follows:
C=Console, E=Error Device, P=Printer, T=User PC, O=Output Handler Device (Controller),
X=External Clock, Y=Staff PC, Z=FIDS/Linux Network Computer , L=Interface
STATUS,BYTE (B)
The status of the device provides information about the logical status relative to the system. The
following initial status settings can be set 1=UP and 4=DOWN. With a user command, or on the
basis of communication problems with the peripherals, it is also possible to change internally
the status of the system which is running. When this happens, an appropriate message is
generated by the system.
WORDALIGNMENT,CHARACTER (C)
Dummy for word-sensitive, machine-dependent data alignment. This component is irrelevant in
terms of the application.
LINK FIELD,INTEGER (I)

This field component is only a space marker for internal purposes. Internally, device-specific
link connections are set here. (e.g. to the process table entry of the output handler process on
display controllers).
SERVICE MODE,INTEGER (I)

This field is used to save the “out of service” status of the device.
DEVICE NAME,STRING (>16)

Internal system name of the device. In all system messages which relate to this device this name
is used. The field represents that access key.
DEVICE DESCRIPTION,STRING (>64)

To provide a more thorough explanation for the user, this field makes it possible to indicate
an additional, application-related designation for the device. This designation can be used, in
particular for the DMU program.
RESERVED,STRING (>64)
RESERVED,STRING (>128)
DEVICE PATH/HOST NAME,STRING (>48)

Every peripheral device is addressed by device path or host name.
RESERVED,INTEGER (I)
CONTROLLER ADDRESS,INTEGER (I)

The numerical controller address for controller peripherals can be entered here.
TIMEOUT,INTEGER (I)
This is where the time-out time for each device can be entered, expressed in seconds. If a time
out occurs, and if RETRYS, where parameters for these have been set, have failed to yield
any success, an appropriate message is generated in the system and the device is set to DOWN
status.
RETRYS,INTEGER (I)
If a fault or time-out occurs when the controller peripherals are being addressed, retrys are
performed in accordance with this entry.
This parameter is used to enter the reset port of comservers, if available.
RESERVED,CHARACTER (C)
RESERVED,CHARACTER (C3)
RESERVED,CHARACTER (C16)
3.3.5. Time Parameter Table (at.tab)
All time-dependent control mechanisms in the FIDS can be set in variable fashion by so-called
time parameters. All these time parameters are summarised in the time parameter table (at.tab).
This table is of the KEY type. The access key is a time parameter number. The time parameters
1-19 are provided for system control. Some processes refer to this time parameter. All other
parameter numbers can be allocated freely within the system as and when this is possible (e.g.
in the selection table se.tab or connection table cn.tab) .
It is important in this context that time parameter 1 (time scheduler TIMSCH) represents the
smallest time unit in the system because the time scheduler checks all time-dependent actions in
the system at these intervals and initiates them when required.
A data record from the time parameter table contains the following field components:
TIME PARAMETER NUMBER,CHARACTER (C4)

Every time parameter is uniquely identified by a positive number which forms the access key in
ASCII format.
NUMBER OF TIME UNITS,INTEGER (I)

Number of time unit selected in the field component ‚TIME UNIT’ .
TIME UNIT,CHARACTER (C)

Time unit. Possible entries are:
(S)econd,
(M)inute,
(H)our,
(D)ay
(W)eek.
DESCRIPTION TEXT,STRING (>256)

Description text for the time parameter.
3.3.6. Line format Table (lf.tab)
The structure of output lines for printouts and displays are determined by a line format. This is
a sequence of field format numbers which must in turn be defined in the field format table (ff.
tab) and text. The lineformat can also include text constants and references to other line format
numbers.
All elements of the lineformat must be separated by ‚;’.
The line format table (lf.tab) is of the INDEX type. Every line format is uniquely identified by a
line format number. It must be numerical and >0 and, at the same time, represents the index.
Example:
20, /* This is the line format index

-15;- /* This is a reference to another line format number 15 from lf.tab
200;- /* This is a reference to field format number 200 from ff.tab
<W;- /* This is a text constant
201;- /* This is a reference to field format number 201 from ff.tab
>;- /* This is a text constant
…
All negative numbers are references to other line format numbers. Positive numbers are
references to the field format table (ff.tab).
The maximum length of aline format can actually be extended dynamically in the table. Simply
adapt the record description format using the descriptor $FORMAT.
An important point in conjunction with line formats is that the alternative line format (type ‘L’)
configured in the selection table (se.tab) must be physically aligned to the same length as the
standard line format entered in the appropriate display table or list table. This is important
because the output handler and use the data length of the standard line format for their internal
allocation of memory.
3.3.7. Action Scheduler Table (as.tab)
All changes to date records in the system (UPDATE, INSERT and DELETE), and all other function
codes are transferred to the action scheduler which consults the action scheduler table (as.tab)
to decide on a central basis which processes should be most affected by the actions initiated in
the system. This function is transferred to the processes defined.
The action scheduler table is of the KEY type. The access key comprises the components
RECORD DESCRIPTION TABLE NUMBER, FUNCTION CODE and PROCESS NUMBER .
A data record from the action scheduler table contains the following field components:

The record description numbers from the system table (sys.tab) is entered for the function codes
(U)pate, (D)elate and (I)nest, provided that a record description exists. If a record description
does not exist, or if a different function code is involved, enter a zero (default value). The record
description table number is part of the access key.
FUNCTION CODE,CHARACTER (C)

The function codes used at present are:
(U) Update
(D) Delete
(I) Insert
(T) Time Synchronisation
(C) Cycle Request for Output Handler Processors
(H) Hold
(G) Go/Continue
With the functions (I)nsert and (D)elete, the complete data record or the key of the record is
forwarded to the processes defined together with the function code and the record description
table number. In the case of the (U)pdate function, this only occurs if there is no record
description for the data record. It is also usually possible to record any number of additional
function codes in the action scheduler table as well. The function code is part of the access key.
PROCESS NUMBER,INTEGER (I20)

Number of processes to which the function is to be forwarded. Up to 20 processes can be
entered. The first process number is part of the access key.
FIELDNUMBERS,INTEGER (I)
In the case of the function code (U)pdate, field numbers can be specified which have to be
changed to enable the specified process to be prompted. The entry of field numbers separated
by commas must be terminated with a zero. The number of field numbers which can be
dynamically set with the table descriptor $FORMAT must be configured large enough.
If no field number is entered for the function code (U)pdate, the process is prompted at every
update. When updates occur, the action scheduler transfers a list of changed field numbers to
the target process.
3.3.8. File Table (fi.tab)
All files in FIDS/Linux, which are kept on permanent data carriers (hard disk, floppy etc.) and
which are not memory-resident are recorded in the file table (fi.tab).
The file table is of the INDEX.type. The access index is the file number. Some file numbers (e.g.
message logging) are assigned in a fixed form and must not be changed.
The data record and the file table contains the following field components:
FILE NUMBER,INTEGER (I)

Every file must be assigned a number from 1 to N as a unique identification. This number
serves as an access index for the file table.
FILE TYPE,CHARACTER (C)

All files are categorised by type. S = sequential files, I = sequentially-indexed files.
CPU SYNC,CHARACTER (C)

If ‚Y’ is entered here, this file should be transferred by the ICINIS process to any SLAVE
computer being initialised if there have been any changes to data records. The existence or
otherwise of differences is determined by the ‚FILE UPDATE TIME’. If there are differences
between the two computers, the file is transferred..
WORDALIGNMENT,CHARACTER (Cn)
Machine-dependent word alignment of the data records.

Table number of the (record description). This table must be entered in the system table (sys.
tab), provided that a record description for the file exists.
FILE REFERENCE ROTATION,INTEGER (I)
RECORD NUMBER LIMITATION,INTEGER (I)

Sequentially-indexed files (Type ‚I’) can be restricted at data record level in a logical manner to
a defined number of records. If zero is entered here, the number of records is only limited by
the physically available memory area on the data carrier.
DIRECTORY,STRING (>32)
Directory of the file. The directory name of the file is linked to the file name for access to the
file.
FILE NAME,STRING (>16)

Name of the file. For message-logging files and history files, only enter the prefixes if the form
of storage is sequential. In this event, a date suffix is created because this is restricted on a daily
basis (One file per day).
FILE UPDATE TIME,(L)

Every change to a file is recorded by entering a time mark in this record component. This
UPDATE time is required to establish whether there is any need for file transfers in the course of
initialisation of SLAVE computers.
3.3.9. Display Table (dp.tab)
The display table (dp.tab) is the central table for the output handler processes. It contains
definitions of all display units working on the system. If there are any changes to the actual
database, the output handler process searches through the display table for the display units
assigned to it. One record should be recorded in this table for each logical display. The
display table is of the INDEX type.
One data record in the display table contains the following field components:
DISPLAY NUMBER,INTEGER (I)

Every display must be assigned a number from 1 to N as a unique identifier. This number acts
as an Access Index for the display table.
SYSNAM,STRING (>16)
Within in the system, and in all messages referring to the display, this internal system name is
used.
APPNAM,STRING (>24)
This field is used for more detailed explanation of the display.
CONTROLLER RECORD NUMBER,INTEGER (I)
This field component is only a place marker for an internal link to the controller which is defined
in the device table (dv.tab). At a software level, a link connection is created whenever -1 is
entered here.
DISPLAY CONTENTS TABLE NUMBER,INTEGER (I)
In this field, enter the table number of the display contents table for this display unit. A table of
this kind must be generated by entering it in the system table (sys.tab) to reserve space for the
memory-resident mirror of the display. The table number issued in the system table should be
entered here.
SELECTION NUMBER,INTEGER (I)
In this field, enter the selection number to be used in the selection table se.tab to filter the data
for the display. If this number is equal 0, the display contents table number (previous parameter
described above) is used as reference to se.tab.
STATUS,INTEGER (I)
Every display can be set here to an initial status. There are 2 options. (1=UP, 4=DOWN). A
display unit set to DOWN is not handled until it has been put into service by the user with the UP
function .
TIMECHAIN NUMBER,INTEGER (I)
In order to define central system parameters in the system, there is a file known as config.sys
which is read in and processed when the system is started by the boot programme SYSTRT. As
well as configuring the actual database, key fields, etc., it can also define the time chains in the
actual database in a flexible manner. Every time chain receives a number starting with 1. The
chronological sequence of the display defined by the time chain (e.g. 2 = estimated time) must
be entered here.
OUTPUT HANDLER PROCESS NUMBER,INTEGER (I)

All output handler processes are entered in the process table (pn.tab) by quoting a unique
process number. Since every output handler process searches for the displays which it is to
handle by consulting its process number in the display table, this must be indicated here.
FLIGHT TYPE,CHARACTER (C)

The highest selection stage for the display has already been made here in the display table. At
this location, the type of flight must be entered. Permitted options are (A)rrivals, (D)epartures
and (B)oth, i.e. mixed displays.
STILL DISPLAY,CHARACTER (C)

If deleted data records from the actual database are to remain on the display unit due to
selection criteria chosen, and if they are not to disappear until the next re-organisation, you
should enter (Y)es at this point, otherwise, enter (N)o. By and large, this is an option which
can be significant for splitflap tables to prevent unauthorised display of lines from records being
dropped from the display.
PAGE NUMBER,INTEGER (I)

If a display on a device is addressed by a page number, it is possible with this component to
configure the number of this page. Processing of this entry must always be handled by the
relevant output handler .
LINEFORMAT NUMBER,INTEGER (I)

All records in the display are created using a line format. At this point, the number of the line
format should be entered from the line format table (lf.tab) .
DELETED LINES,INTEGER
Internal use. This is a component which is used as a place marker for internal use. Here, an
output handler enters the number of lines of data which are actually being deleted. This is
required in order to establish when the next re-organisation should take place.
ROW INCREMENT,INTEGER (I)

If a physical display device contains several logical displays, a line offset relative to 0 should be
entered here, provided that the display does not start on the first line.
COLUMN INCREMENT,INTEGER (I)

If the data lines in the display do not start in the first column, an offset relative to 0 can be
entered here. The responsible controller must however support the appropriate location of the
write mark.
LAST REORGANISATION TIME,LONG (L)

Internal use. The output handler notes internally when the last reorganisation occurred on a
display.
TIME OF LAST FLIGHT,LONG (L)

Internal use. The output handler enters the time of the last data record on the display at this
point. This entry is a decision-making criterion for any data changes required on the display
unit.
NO FLIGHTS,INTEGER (I)
This field component is not used at present.. The intention here is to use a reference number to
the text table (tx.tab) which represents an output sequence used in cases where there is not flight
information for the display.
PRIOR DISPLAY,INTEGER (I)

If the display has a prior display feature, the display number (dp.tab) should be entered here.
It is important in this context that the prior display has a lower display number. All logical
assignments, such as TIMECHAIN NUMBER, output handler process etc. should be maintained
in uniform fashion on linked displays of this kind.
NEXT DISPLAY,INTEGER (I)

If the display has a next display feature, enter the display number here. The display number of
the next display must be higher. In all other respects, the same restrictions apply as to PRIOR
DISPLAY.
CONTROLLER,STRING (>16)
To establish a reference to the physical device of the controller, the internal system device name
from the device table (dv.tab) should be entered here.
GROUP,STRING (>16)
To establish a reference to the group name (grp4.tab ).
3.3.10. Selection Table (se.tab)
The selection table (se.tab) is used to perform information displays and selections for other
purposes. The individual selection records are allocated an interpreter expression which checks
their plausibility in conjunction with the data records (TRUE or FALSE). All related selection
records (e.g. for one display) have a cumulative effect (with the exception of alternative (L)
ineformat). The selection table is of the KEY type, where the key is created from the section type,
the reference number and a serial sort sequence field.
A data record from the selection table contains the following fields:
SELECTION TYPE,CHARACTER (C)

For information displays, we differentiate between the following types: (D)isplay, (E)nd-of-
Display and (L)ineformat. ‚D’ determines the pure record selection from the actual database.
‘E’ determines which data record should be the last one for a display and ‚L’ can define an
alternative line format for theoretically any standard line format (displays and expressions)
but the decision as to whether an alternative line format should be taken is determined by the
contents of the data record being output, on which the selection expression is to be applied.
The selection type (N)umber of records, can be used to select another line format for different
number of valid records to display.
Example: N,“ 416“,,,,,,[N1]>=[3]?[416]:([N1]==[2]?[415]:[414])
For this example, the standard line format defined in dp.tab is 416.
If we have 3 or more records to display ( condition [N1]>=[3] ), line format 416 will be
selected. For 2 records (condition [N1]==[2]), line format 415 is selected.
In all other cases, line format 414 is selected.
The last selection type is (F)unction. Here, a type of basic selection can be configured for
DataManager. The access key is the number of the table in sys.tab + 5000.
Example: F,“5008“,,,,,,[N1]>=[30]
For this example, the table number from sys.tab is 8. This is the time parameter table (at.tab
).If the user request the data of at.tab with Data Manager, only records with index 30 or higher
([N1]>=[30]) will be displayed.
When using SELECTION TYPE ‚L’, an alternative line format is recognised whenever an
assessment of several possibilities produces the answer TRUE (alternative). For all others, all the
expressions found must be TRUE (additive).
REFERENCE NUMBER,CHARACTER (C4)

The reference number for display selections (D and E) is the selection number or the display
contents table in dp.tab. For alternative (L)ine formats, the number of the standard line format
applies.
This component is part of the access key and is defined in ASCII form (CHARACTER/C4), to
ensure that it can be sorted in the system, regardless of the machine which performs the task
SORT SEQUENCE CHARACTER,CHARACTER (C)

If several selection records are required for the selection, the uniqueness of the access key is
achieved by entering an alphanumeric character in this field.
CONDITION TYPE,CHARACTER (C)

If there are several selection records for one selection, it is possible to define with the condition
type whether individual selections are linked with AND or OR. The symbol ‚|’ represents OR, and
the symbol ‚&’ represents AND. If nothing is specified, this is an AND link. It is only ever possible
to have one type of link for a selection comprising several data records, individually selected.
The advantage of this facility is that it makes it possible to split up more complex expressions
(summary) and to improve system performance.
SELECTION EXPRESSION,STRING (>NNN)

In the same way as in the connection table (cn.tab) an interpreter expression (internal
interpreter) is also used in the selection table. With selection types F and D, a record is selected
when the expression is TRUE. In contrast, (E)nd-of-display is reached whenever the expression
is assessed as FALSE. In the event of selection types ‚L’, if assessed as TRUE, the alternative
line format number (reference to line format table lf.tab) is sent back as the return value for a
„conditional assessment“ in the style of the „C“ language. The length of selection expression
can be set using the record description format ($FORMAT) in the selection table. The use of an
internal interpreter is explained in detail at another point in this system manual.
3.3.11. External Error Checks (ec.tab)
Every transaction program in the FIDS which manages files performs plausibility checks for these
files when changes are requested. On a standard basis, various checks are made on the basis
of field types based on the prevailing record description. It is not possible, for instance, to enter
letters in a numerical field etc. Once these checks have been completed by the transaction
process, and provided that no errors have occurred, the next step is to proceed with what is
known and an additional external check. In this, the program makes reference to the external
error check table (ec.tab). The reference number and, at the same time, the access key to table
ec.tab is the record description table number. The external error check table is of the KEY type.
Several fault checks can be entered in the table ec.tab for every record description existing in
the system. These have a cumulative effect.
A data record from the external error check table contains the following field components:
RECORD DESCRIPTION TABLE NUMBER,CHARACTER (C4)

Part of the access key for table ec.tab. The record description number should be indicated in
ASCII to ensure that a consistent machine-sorting process is achieved in the table, acting in
conjunctions with the VARIATION component.
VARIATION,CHARACTER (C4)
Variation field which serves to ensure the uniqueness of a access key when handling several
error check records. Owing to the fact that this field has 4 digits, the number of possible error
checks is virtually unlimited.
MESSAGE NUMBER,INTEGER (I)

The message number (reference to message table msg.tab) of a message should be entered in
this field component and output on the user terminal once the specified error occurs.
FIELD NUMBER REFEENCE,INTEGER (I)

In the event of an error, if the cursor is to be located on a specific field, the number of the field
from the record description should be entered here. If no entry is made, when an error occurs,
the cursor is located on the function field of the data record.
ERROR CHECK EXPRESSION,STRING (>NNN)

An interpreter expression should be entered here with is assessed by the internal interpreter on
the FIDS. If the plausibility content of the data record to be checked is TRUE, there is an error.
The transaction program terminates the error check and issues an error message.
The length of the assessment expression can be set using the $FORMAT descriptor .
3.3.12. CPU Table (cpu.tab)
The FIDS is designed to run in a network which can theoretically contain any number of Linux
computers and where all processes configured in the process table (pn.tab) are distributed
across the whole range of computers in the network. All these computers are defined in the
CPU table.
A data record in the CPU table contains the following field components.
LOGICAL CPU NUMBER,INTEGER (I)

The access index for the CPU table is a logical computer number. A valid CPU number must be
greater than zero. The MASTER computer always received number 1 by convention.
PHYSICAL CPU NUMBER,INTEGER (I)
Every computer knows from its local config.sys file (parameter $CPU) which physical CPU
number it has. Based on this number, it can consult the CPU table to obtain its logical CPU
number and thereby determine its function in the FIDS/Linux network.
CPUTYPE,CHARACTER (C)
This is where the type of computer should be entered. (M)aster, (S)tandby and (X) are the
possible for entries for all other computers. The type entered here is also used for the CPU
reference in system messages (message table msg.tab) .
Only one MASTER computer can be configured in the CPU table.
STANDBY CPU,INTEGER (I)

A standby CPU can be assigned to every computer. The logical CPU number of the standby
computer should be entered here (type ‚S’).
CPU MODE,INTEGER (I)

Various status settings can be set in bit fashion in this component. At present, only bit 0 is
defined. With this bit the RESTART option is set for the computer. If a fatal error occurs on this
computer, a new start is requested once the FIDS has been powered down by the STANDBY
computer, provided this is still possible. The computer will then adopt, in logical fashion,
the CPU number of the STANDBY computer which was previously responsible for it. Setting
this mode bit only has an effect if a responsible STANDBY computer has been entered in the
component ‘STANDBY CPU’ .
PHYSICAL DEVICE NAME,STRING (>16)

The physical network reference to the device table (dv.tab) should be entered here. This entry
must match the components ‚DEVICE NAME’ in the device table to obtain information about the
network address and the status of the computer.
SYSTEM NAME,STRING (>16)

This component is not used at present.
APPLICATION NAME,STRING (>24)

At this point, an application-dependent text for the relevant logical computer can be entered.
This text is output beside the device name in the ‘status summary’ function.
COMMUNICATION PROCESSES,INTEGER (I22)

The number of the processes :
ICGETPW
ICEGTPP
TICPUTP1
TICPUTP2
TICPUTP3
...
with commas seperated.
3.3.13. Message Table (msg.tab)
All messages generated in the FIDS and output on terminal and files etc. are summarised
centrally in the message table (msg.tab). All messages in the FIDS are prepared by the message
handler (msh) and directed to its intended destinations. The list of addresses for sending out a
message can be set individually on each defined message.
The message table is of the KEY type. The access key is the message number. Message
numbers are numbered from 0 to 9999, but numbers 0 to 100 are initially reserved for internal
system use. All other message numbers can be issued freely by utilising the external error check
table.
The structure of a message for output is as follows:
DD/MM/YY HH:MM (A,BX) PROCESS: message text................

The expression (A,BX) represents the CPU reference, i.e. the reference to the computer in
the FIDS/Linux network on which the message was generated. ‘A’ indicates the physical CPU
number (refer to CPU parameter in the config.sys), ‘B’ represents the logical CPU number
(reference to CPU table cpu.tab) and ‚X’ represents the logical CPU type (M)aster, (S)tandby or
(X) for all other computers). For example, (3.1M) means TIMSCH: this shows that the message
was issued by the time scheduler of the MASTER computer and the physical computer number 3
is that of the MASTER computer (logical computer number 1).
Date, time, CPU reference and name of process are suppressed for terminal outputs. Only the
actual message text is output here.
If the ERROR DEVICE FLAG has been set in the message definition and if the ‘system message
device’ is not addressable (e.g. printer switched off), the message can be redirected to the
console/dev/console.
The internal system message number 0 has a special function. If unforeseen faults occur in
the system procedure, this message is usually used and string variable ‚%s’ in the message
represents the English error message text. These texts are not therefore available in other
languages because they are ‘hard coded’ in the programs. This solution was adopted to avoid
creating an unnecessary number of messages for every eventuality, of a kind which seldom
occur. In normal cases one would never see this message.
A message in the message table is defined by the following field components:
MESSAGE NUMBER,CHARACTER (C4)

The message number is a unique access key for the message table.
BROADCAST FLAG,CHARACTER (C)

If something other than a blank was entered here, this message is a „broadcast message“, i.e.
this message is output to all user terminals.
SUPERVISOR FLAG,CHARACTER (C)

If something other than a blank is entered here, this message is output to a special message
window on the user terminal. This flag only acts in conjunction with the BROADCAST or
TERMINAL flag.
TERMINAL FLAG,CHARACTER (C)

Entry of a non-blank character indicates that this is a message directed to a specific user
terminal. This flag is normally set on all error messages which can occur in conjunction with
plausibility checks.
ERROR DEVICE FLAG,CHARACTER (C)

This flag has the effect of directing the message to the system message device (normally a
printer, device type ‚E’ in the device table dv.tab) .
MESSAGE FILE LOGGING,CHARACTER (C)

This flag ensures that the message is written to the message logging file.
CONSOLE MESSAGE FLAG,CHARACTER (C)

This message is output to the system console (device Type ‚C’ in the device table dv.tab)
whenever this flag is set.
MAIL MESSAGE FLAG,CHARACTER (C)

This flag has the effect of sending the message to one or more e-mail addresses. The
configuration of the e-mail addresses is done in the table mailrec.tab.
SMS MESSAGE FLAG,CHARACTER (C)

This flag has the effect of sending the message as SMS. The configuration of the phone
numbers is done in the table mailrec.tab.
MESSAGE TEXT,STRING (>55)

At this point the text of the message can be entered. Foreign languages are therefore not a
problem. The internal system messages mostly used numerical and/or alphanumeric parameters
designated by the space markers ‚%s’ and ‚%ld ’. ‚%s’ represents a string variable and ‚%ld ’
designates a numerical integer value. The position of these variables can be changed in the
message. The sequence within one variable type (e.g. with several integer variables ‚%ld ’ in a
message) cannot however be changed.
3.3.14. Time Scheduler Table (ts.tab)
The time scheduler table offers scope for placing any data in the input queue of any processes
at any intervals of time. This table is read through sequentially every time the TIMSCH process
is active. TIMSCH checks which processes are to be prompted and executes this command. It is
immaterial here whether the process runs on a local computer or on a remote computer in the
FIDS/Linux network.
The smallest time interval in which processes can be prompted is determined by the time
interval of the TIMSCH process itself.
This action is only performed by TIMSCH on the MASTER computer although TIMSCH runs on
every FIDS/Linux computer in the network.
The time scheduler table is of the KEY type. The unique access key is formed by the
component’s PROCESS NUMBER and FUNCTION CODE.
A data record in the time scheduler table contains the following field components
PROCESS NUMBER,INTEGER (I)
Number of process for which data should be placed in the input queue.
The PROCESS NUMBER is part of the access key.
FUNCTION CODE,CHARACTER (C)

Data can be placed in the queue of a process in the form of the action scheduler table structure
(ASTREC), as can any other data string. If a function code (e.g. (C)ycle) is entered here, the
data from a data record are entered in an ASTREC structure and sent to the target process. If
nothing is entered here, the PARA STRING is sent directly.
TIME UNIT,CHARACTER (C)

This component, in conjunction with the NUMBER OF UNITS component defines the interval of
time at which the process must be prompted. The options here are (S)econds, (M)inutes, (H)
ours, (D)ays, (W)eeks, (X)every day or (T) for the time parameter number, i.e. a reference
to the time parameter table (at.tab). If nothing is specified, the process is always prompted
whenever TIMSCH is active.
WORD ALIGNMENT,CHARACTER (C)

Word alignment.
NUMBER OF UNITS,INTEGER (I)

In conjunction with the TIME UNIT component, the number of time units is entered here or, in
the event of TIME UNIT (T), the number of time parameter is entered in the time parameter
table (at.tab). If nothing, or zero, is entered here, the process is always prompted whenever
TIMSCH is active.
LAST CALL,LONG (L)

Internal component. This is where TIMSCH enters the time of the last call.
PARA SIZE,INTEGER (I)

Length entry for date specified in PARA STRING. Entering a zero has the effect of implicitly
defining the length of data (zero terminator).
PARA STRING,(>NNN)
Variable length of data string for the target process. The length is set by the $FORMAT parameter
in the table. It is also possible to integrate control codes or whitespace characters in the data
block using the standard procedure (backslash + octal number).
3.3.15. Watchdog table (wdog.tab)
In order to control network availability of the computers in the FIDS network, keep-alive
telegrams are sent between the differents servers. In the case one server is not responding, It will
be set to status DOWN.
Before the local server sets an unreachable server to status DOWN, it will use the table ‚wdog.tab‘
to check the network.
If all or some of devices configured in the table ‚wdog.tab‘ are reachable using ping, the
unreachable server will be set to status DOWN.
If all devices configured in the table “wdog.tab” are unreachable using ping, the local server
will „show” the message ‚no contact to the network ‘ and wait for re-establishing the
connection to the network.
If one or more devices, which are configured in the table ‚wdog.tab‘, are removed from the
FIDS network or are out of service, the table ‚wdog.tab‘ must be reconfigured with devices
which are connected and UP.
The watchdog table record contains the following field components:
PHYSICAL CPU NUMBER, INTEGER(I)

Physical CPU number. This number acts as an Access Index for this table.
DEVICE TO PING, STRING(>16)

Up to 4 devices configured in dv.tab can be entered.
3.4. Record description tables (xxx.dsc)

Each dynamic table in the FIDS has what is known as a record description. A record description
is stored for each table in the system in its own table, referred to as the record description table.
This is incorporated in the system table (sys.tab). A record description table is always of the
FIELD type. In broad terms, this table is an extended index table in which the record number 0 is
used for different global informative descriptions and is reserved. The access index for a record
description table is the field number.
Record description tables, in accordance with a name convention, always receive the suffix
‚dsc’, e.g. af.dsc for the record description of data records in the actual database. This concept
makes the field structure of most data records in the FIDS entirely flexible. Also, with very few
exceptions, no field numbers were issued by the software (hardcoded) to achieve the highest
possible level of independence from applications and configurations.
Every record description table has the following field components:

The field number is the access index for a field in the record description table. Field numbers
must be >0. The ascending sequence of field numbers also represents the physical sequence
of fields in a data record. Since the record description tables are an INDEX concept, dummy
entries are stored in the table for all unused indices. For this reason, as many sequential field
numbers as possible should be allocated to save memory space.
FIELD OFFSET,INTEGER (I)

This field component is calculated by the system. This represents the offset of a field within the
data record. No entry is therefore required in this component.
FIELD SIZE,INTEGER (I)

Length of a field in bytes. If binary fields are defined, the machine-dependent word lengths
should be informed!!
FIELD TYPE 1,CHARACTER (C)

I = Internal Field
Fields which users cannot control with a processing function should be designated as
INTERN. Usually these fields are the ones whose content can only be manipulated by the
connection table (cn.tab, cnArr.tab and cnDep.tab).
C = ASCII Character
T = Time (actual database format HHMM+-D)

In binary storage, times in the actual database are stored in minutes since 1980. The time is
incremented by 1 in each case because zero represents that absence of a time entry.
D = Date in format DDMMYY

Date entries, whenever these have been filed in binary form, are stored in minutes since
1980.
H = Hour in format HHMM

Time entries (hours and minutes) are stored internally in minutes in binary form.
L = Lookup table reference field (e.g. Dest. IATA Code)

Fields of this type are checked against a lookup table which can be specified. The field
contents are used as a lookup table key and the lookup table is examined accordingly. If
there is no corresponding entry, the entry is rejected by the plausibility check.
F = Frequency
Special field for the frequency of a scheduled database data record. Permitted entries are the
numbers 1-7 , blanks, zero and ‘-’.
S = Signed integer (with prefix)
U = Unsigned integer (without prefix)

Numerical values. These fields are usually represented in ASCII form (FIELD TYPE 2) because
it is otherwise not possible to tell whether a field of this kind has any contents, or is empty,
because every value in binary form is valid.
This field component is used to control the internal record display of a field.. B = binary and
A = ASCII.

This field component is used to distinguish whether a field requires contents or whether it is
optional. In addition, the key fields are defined which always require contents, i.e. which are
not allowed to be empty. There are the following entry options: M = mandatory, O = optional,
K = key field and R = rotation key field. If no entry is made in this field, (O)ptional is used as a
default value.
FIELD TYPE 4,BYTE (B)

This field component is used for bit encoding of various field options which relate primarily to
field preparation. The following bit assignments are defined:
Bit 0: All blanks in the entry are eliminated and the content is left-aligned.
Bit 1: The content of the field is left-aligned.
Bit 2: The content of the field is right-aligned.
Bit 3: All alpha symbols in the contents are translated in upper case.
Bit 4: The entry is zero-terminated (C string).
Bit 5: A numerical value in the field is isolated and all alphanumeric characters are replaced
with blanks.
Bit 6: Rotation field (only actual and scheduled databases).
Bit 7: Flight number preparation with a blank (only actual and scheduled databases).
TABLE REFERENCE,INTEGER (I)

In lookup tables (type 1=L) the number defined for the lookup table in the system table (sys.tab)
should be entered against which the entry should be checked.
SOURCE FIELD REFERENCE,INTEGER (I)

The source field number is entered here for data records generated by other data records (e.g.
actual database record from the scheduled database by the INSFLT process).
FIELD NAME,CHARACTER (C4)

In this field component, a name up to 4 digits in lengths can be entered for the field which must
then be used by the user when operating the selection interpreter to address this field. If no field
name is entered, the selection interpreter cannot access the field.
CONTROL FIELD REFERENCE,INTEGER (I)

This is the number of a control field in the same table to save the modification time of the field.
CHANGE SOURCE FIELD REFERENCE,INTEGER (I)

This is the number of a control field in the same table to save the change source of the field.
The source of changes can have the following values:
1 = Field changed by user
2 = Field changed by internal rules
3 = Field changed by an external interface
4 = Field changed by an input device like BMID
COMMENT,CHARACTER (C64)
A description of the field which can be used in different client programs like Data Manager to
give the user more information.
EXPORT FLAG,INTEGER (I)

Internal use
CODE PAGE,INTEGER (I)

The Codepage of the field data can have the following values:

1200 Unicode
1250 Central Europe
1251 Cyrillic
1252 Latin I
1253 Greek
1254 Turkish
1255 Hebrew
1256 Arabic
1257 Baltic
1258 Vietnam
874 Thai
The default Codepage is 1252.

If the Code page 1200 (Unicode) is selected, 2 bytes are needed to save each character.
Example from ap.dsc:
3,,30,C,A,,%0010,,,ENGL,,,Airport English,1
7,,60,C,A,,%0010,,,UNIC,,,Airport Unicode,,1200
The field size of field ‚UNIC‘ is 60, but it is only possible to enter 30 characters in this field.
3.5. Display content tables (dpc.xxx)

DPC tables are necessary to maintain mirrors of displays in memory. Every display defined in
the display table (dp.tab) has to have a responsible DPC table. The number of physical lines in
a display is determined by the number of (dummy) entries in this table. Since the type of every
display line can be determined in variable fashion, it is also possible to record headlines and
comments, including control strings directly in the DPC table. All DPC tables are of the INDEX
type where the line number is the index.
A data record in a DPC table contains the following field components:
LINE NUMBER, INTEGER (I)

The line number should be issued in ascending order from 0, i.e. if the display contains 10
lines, line numbers 0-9 should be issued for the 10 entries.
LINE STATUS WORD, INTEGER (I)

This field contains the status of every line. The following bits are set for individual status settings:
Bit 0: Line is DOWN. (e.g. splitflap line error).
Bit 1: Line is logically and/or physically deleted.
Bit 2: Contents of line have been modified.
Bit 3: Line is OBSOLETE.
Bit 4: Line is DOWN by Administrator.
When changes are made to the information contents of displays, these are examined line
by line to find out whether anything has changed. If it has, the MODIFY bit (bit 2) is set. This
concept makes it possible to minimize I/O to the absolute minimum size. Lines of the TEXT
types should have their status setting preassigned with the MODIFY bit to ensure that text lines
(headlines etc.) are also issued when the system is booted. Since these settings normally never
change, with the exception of an UP function on the display, I/O output never occurs on these
lines.
LINE SIZE, INTEGER (I)

A data length can be explicitly specified for line of the TEXT type. If this entry is absent, the
data length is implicitly defined by the text itself. The length of text data is restricted by the field
component ‚DATA SIZE’. In lines of the INFO type, this field component is used internally for
defining data length and it cannot be assigned by the configuration.
PAGE NUMBER, INTEGER (I)

TABLE NUMBER, INTEGER (I)
DSC NUMBER, INTEGER (I)
These parameters are modified by the process GTHDL, which is controlling the monitors. The
process sets the parameters as follows:
PAGE NUMBER: The number of the page, where the line is displayed.
TABLE NUMBER: The number of the table in the page, where the line is displayed.
DSC NUMBER: Number of the description table in the table sys.tab. It is the identification of
the data source.
DUMMY, INTEGER (I)

Internal use.
LINE TYPE, CHARACTER (C)

This field defines the type of every display line. The following types are possible:
(I)NFO Standard line type for recording actual database data.
(T)EXT Line type for the output of texts such as headlines, comments, help pages etc.
(F)REEF Freeform lines
(N)O No Flight data
(L)INE Free Line
UPDATE TIME, LONG (L)

The time, when the data is sent to the display, is saved in this field.
KEY SIZE, INTEGER (C99)

This fields is only used for reserving space for the record key. The length in the record format of
the DPC table ($FORMAT) should be take into account (e.g. C13 for a key with a length of 13
bytes) and it is derived from the sum of lengths of key fields defined for the actual database in
the config.sys file.
DATA SIZE, INTEGER (C99)

This field is provided for information lines as a physical space mark for information data. The
actual length of an information line is determined by the line format of a display and can,
where applicable, involve several physical lines in the DPC table if DATA SIZE is too small for
recording the entire line. Using this mechanism, it is also possible to control several lines of
output. If DATA SIZE is greater than the length resulting from line format, LINE SIZE is set
accordingly by the relevant output handler and is then binding for output of data.
The DATA SIZE length is set by the $FORMAT descriptor, just like <KEY SIZE>.
3.6. Lookup tables

The term lookup tables covers a group of memory-resident tables which perform dynamic
extension and translation of information in the scheduled and actual databases. These tables
always have an ASCII key. All lookup tables are therefore of the KEY type. Fields of type 1 ‚L’ in
the record description table have their contents checked against lookup tables.
The following section provides a brief explanation of the most common types of lookup table.
It should be pointed out explicitly at this point that the record structure can differ, depending on
the application involved.
3.6.1. Airports
All display in FIDS/Linux receive their data from the actual database. Every data record in the
actual database normally contains a short code as a destination of provenance indicator which
can be used to access the airport lookup table (ap.tab) to obtain supplementary information
about where aircraft are flying to or from. Output handler processes responsible for controlling
the displays on different display peripherals use this lookup table, for example, to translate the
short code of an airport in the actual database date record into the corresponding longhand
form.
The record description table (ap.dsc) belonging to the airport lookup table is entered in the
system table (sys.tab) just like the lookup table itself, and like all other tables in the system.
3.6.2. Remarks
In a similar way to the airport codes in the airport lookup tables, remarks can also be used
in short form in the actual database. For display media, it is usually necessary to use another
display mode because the general public will not be able to understand the short codes. These
data supplements are controlled in a similar manner to the airport lookup table by the remark
lookup table (re.tab). The record description is contained in table re.dsc.
3.6.3. Airlines
Airlines are recorded in the airline lookup table using the IATA and ICAO codes. The concept
for using this lookup table, in a similar way to the other lookup tables, is not hard wired. For
example, the airline lookup table can be used for plausibility checks in the „Carrier“ field
(actual and scheduled databases).
The remark lookup table (al.tab). The record description is contained in table al.dsc.
3.6.4. Natures
Natures (flight types) are entered in the nature lookup table together with their codes, which
theoretically can be assigned freely. Use of this lookup table, just like all other lookup tables, is
not a hard wired concept.
The remark lookup table (na.tab). The record description is contained in table na.dsc.
A typical record description comprises the following field components:
NATURE CODE,CHARACTER (C4)

Nature code and access key for the nature lookup table.
MEANING,CHARACTER (C32)
Designation/explanation of the flight type.
PUBLIC DISPLAY INDICATOR,CHARACTER (C1)

A ‚Y‘ or ‚N‘ can be entered in this field to indicate whether a data record of this type should
be displayed on public displays or not (e.g. military flights only for staff displays). However,
this feature is not „hard wired“ and must be controlled by making appropriate entries in the
selection table (se.tab).
3.6.5. Aircraft
Aircraft (aircraft types) are recorded in the aircraft lookup table with their codes. The concept for
using this lookup table, just like that of other lookup tables is not hard wired. For example, the
aircraft lookup table can be used in system extensions (e.g. gate management system) to access
more detailed information about specific types of aircraft (e.g. not all types of aircraft can be
handled at all gates).
The remark lookup table (ac.tab). The record description is contained in table ac.dsc.
3.7. Output handler specific tables

Every output handler which services a group of display devices (e.g. FIIB tables), obtains its
information about the prevailing configuration from the display table (dp.tab) and field format
table (ff.tab). To avoid having to record all special features of all the different display peripheral
controllers in these tables, which sooner or later would make them impossible to follow, i.e.
too complex, handler-specific tables have been devised (e.g. fiib.tab for splitflap or gt4.tab for
monitors).
These tables are of the KEY type where the access key can theoretically have any name. In
practice, this is usually a controller name from the appropriate table (dv.tab). The information
entered here contains supplementary information for the appropriate controller and logical
display.
The record format of a record in a handler-specific table is defined separately for every handler
program and is encoded in „hard“ form in the handler module. The table should be recorded
in the system table. The reference to this table is produced in the process table (pn.tab) by
quoting the table number for the relevant handler process.
3.7.1. Graphic-Terminal-Table
The GTHDL process is responsible for controlling the monitors with ConVis or GT2 clients in the
FIDS. Controller/specific configuration information are saved by the output handler in the GT4.
TAB table.
There is only one GT table, regardless of whether the GTHDL handler was started in several
process copies or not.
The output handler obtains access to supplementary information by using the process name or
the device name as an access key:
Process name:
GTHDL0,,,,broadcast1
In this case, the process with process name GTHDL0 in the table pn.tab will broadcast the
time using the hostname ‚broadcast1‘. This hostname must be specified in the table /etc/
hosts.
Other entries can be added to broadcast the time to a different broadcast-IP:

GTHDL1,,,,broadcast2
Device name:
All devices are added automatically by the process SYSTRT at system start from the device
table dv.tab. The process uses the DEFAULT entry in GT4.TAB to generate the record for each
device. Other parameters, like default video mode or standby mode are loaded from the
table ‚srv.tab‘, where the changed parameters using DMU are saved.
3.7.2. FIIB Tables
The FIIB process is responsible for controlling the FIIB controller in the FIDS. Controller/specific
configuration informations are entered in the “fib.tab” table relating to the output handler.
All specific tables needed by the FIIB process are located in the folder “/app/sint2/tab/FIIB”.
3.7.2.1. FIIB Table
‚/app/sint2/tab/FIIB/fiib.tab‘
All FIIB controllers (dv.tab) and displays (dp.tab) should be entered with their system name
in this table, regardless of whether the configuration options are adopted or not. The output
handler can then obtain access to supplementary information by using this name as an access
key. There is only one FIIB table, regardless of whether the FIIB handler was started in several
process copies or not.
One data record in the FIIB Table contains the following field components:
REFERENCE KEY,STRING (>16)

Device-name or display name of the controller/display. This field component is the unique
access key in the SFC table.
IGNORE DEFECT LINES, INTEGER (I)

0 -> Defect lines will be set to status DOWN and filled with blanks
1 -> Defect lines messages from the FIIB will be ignored
NUMBER OF OBSOLETE LINES, INTEGER (I)

Number of obsolete lines must be entered in this field. For example, if this number is set to 4,
the FIIB will be reorganised when the 5th line become obsolete.
DUMMY, INTEGER (I)

Internal use.
TIME SYNC. INTERVAL, INTEGER (I)

Time synchronisation interval in min.
CLOCK LINE, INTEGER (I)

Line number of clock on display ( physical number starting by 1 ).
CLOCK NUMBER, INTEGER (I)

Number of clocks on line on display: 1 or 2
CLOCK STATUS, INTEGER (I)

Clock status ( 1= UP, 4 = DOWN)
DATE LINE, INTEGER (I)

Line number of date on display ( physical number starting by 1 ).
DATE OUTPUT FORMAT, STRING (>32)

The output format for the actual date. The same formats used by the C-function ‚strftime‘
can be configured.
MAX BUSY TIME, INTEGER (I)

Max busy time in seconds
MODUL TABLE, INTEGER (I)

Reference table number for Hour, Minute and Remark modules according to table sys.tab.
NEXT TIME SYNC., LONG(L)

Internal use.
3.7.2.2. MODULE Table
‚/app/sint2/tab/FIIB/mod.tab‘
The sequence list for SF Module Hours, Minutes and Remarks can be entered in this table.
One data record in the Module Table contains the following field components:
REFERENCE KEY,(C1)
The keys ‚H‘ and ‚M‘ are hard coded. The key ‚H‘ is used to access the sequence list for the
Hour module. The key ‚M‘ is used to access the sequence list for the Minute module.
All other keys are configurable and must be specified in the line format to access the correct
sequence list.
SEQUENCE LIST,STRING(>240)
The sequence list contains the ascii values, which must be send to the FFIB to change the flap
position.
Example: Sequence list of the remark module
012345…( Index )
W,“@@ACBFGEDLMONJKIHXY[Z^ _ ]\\TUWVRSQP01326754<=?>:;98()+*./\054$%‘&\042#! \
x60acbfgedlmonjk\x69hxy\x7B\x7A@“
To activate the flap position 2, the ascii code ‚A’ must be sent to the board.
To activate the flap position 3, the ascii code ‚C’ must be sent to the board.
To activate the flap position 4, the ascii code ‚B’ must be sent to the board.
…
Head office & production:
CoNRAC GmbH Developed / Designed / Made in Germany
Lindenstrasse 8 · D-97990 Weikersheim · Germany
Tel.: +49-7934-101-0 · Fax: +49-7934-101-101
Specification subject to change without prior notice.
info@conrac.de · www.conrac.de
GM ServerManual-Vol2_1.0062_rev00
DAtA MoDUL GRoUP
Subsidiaries & Sales Offices:

CoNRAC France - Paris CoNRAC MENA FZE - Dubai CoNRAC Latin America - bogota CoNRAC Sales office Northern
E-mail: info@conracfrance.fr E-mail: info@conrac.ae E-Mail: info@conrac.co Europe - Sweden
www.conrac.fr www.conrac.ae www.conrac.co E-mail: info@conrac.se
Tel.: +33-3-44 54 96 99 Tel.: +971-4-29 94 009 Tel./Fax: +57-1-34 65 338 www.conrac.se
Tel.: +46-42-21 29 39
CoNRAC Asia - Singapore CoNRAC South Africa - CoNRAC Sales office Southern CoNRAC Sales office Northern
E-mail: sales@conrac-asia.com Johannesburg Europe - Rome Europe - Norway
www.conrac-asia.com E-Mail: info@conrac.co.za E-mail: info@conrac.it E-mail: info@conrac.no
Tel.: +65-67 42 79 88 www.conrac.co.za www.conrac.it www.conrac.no
Tel.: +27-83-63 50 369 Tel.: +39-06-45 43 92 02 Tel.: +47-52-77 63 85

Ma CS: System Manual Vol. 2

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Ma CS: System Manual Vol. 2

Uploaded by

Copyright:

Available Formats

SE R VE R

management administration communication system

System Manual Vol. 2

Innovation. Experience. Flexibility. Quality.

3.1. Table concept

The distinction is made between the following descriptors:

\00101\002\033A\nB\t (Hex: 01 30 31 02 1B 41 0A 42 09)

3.2. System table (sys.tab)

TABLE NUMBER,INTEGER (I)

BCB ADRESS DUMMY,LONG (L)

TABLE DESCRIPTION LINK,INTEGER (I)

TABLE TYPE,CHARACTER (C)

CHANGE FLAG,CHARACTER (C)

RECOVERY FLAG,CHARACTER (C)

3.3. Basic configuration tables

3.3.1. Process Table (pn.tab)

PROCESS NUMBER,INTEGER (I)

PROCESS NAME,STRING (>16)

BOUND UNIT,STRING (>16)

SWAPPING FLAG,CHARACTER (C)

PROCESS TYPE,CHARACTER (C)

PROCESS ID,INTEGER (I)

NETWORK PORT NUMBER,INTEGER (I)

PROCESS MODE BITS,INTEGER (I)

 The NO-WAIT-FOR-READY Bit (Bit 2) can be used if a process is intended to generate

 The PROCESS-LOGGING Bit (Bit 3) not used

 The WRITE-DIRECT Bit (Bit 5) not used

TARGET CPU NUMBER,INTEGER (I)

TASK QUEUE SIZE,INTEGER (I)

TRACE FILE,STRING (>32)

UPDATE TIME INTERVAL,INTEGER (I)

3.3.2. Connection Table (cn.tab, cnArr.tab, cnDep.tab, cnCs.tab)

RECORD DESCRIPTION TABLE NUMBER,INTEGER (I)

FIELD NUMBER,INTEGER (I)

CORRESPONDING FIELD NUMBER,INTEGER (I)

MAKE CONNECTION ALL TIME,CHARACTER (C)

3.3.3. Field format Table (ff.tab)

FIELDFORMAT NUMBER,INTEGER (I)

FIELD NUMBER,INTEGER (I)

DESTINATION SIZE,INTEGER (I)

TEXT TABLE ENTRY NUMBER,INTEGER (I)

TABLE LINK,INTEGER (I)

FIELD LINK,INTEGER (I)

TEXT TABLE REPRESENTATION,CHARACTER (C)

TEXT CONSTANT,STRING (>NNN)

3.3.4. Device Table (dv.tab)

DEVICE TYPE,CHARACTER (C)

LINK FIELD,INTEGER (I)

SERVICE MODE,INTEGER (I)

DEVICE NAME,STRING (>16)

DEVICE DESCRIPTION,STRING (>64)

DEVICE PATH/HOST NAME,STRING (>48)

CONTROLLER ADDRESS,INTEGER (I)

3.3.5. Time Parameter Table (at.tab)

TIME PARAMETER NUMBER,CHARACTER (C4)

NUMBER OF TIME UNITS,INTEGER (I)

TIME UNIT,CHARACTER (C)

DESCRIPTION TEXT,STRING (>256)

3.3.6. Line format Table (lf.tab)

20, /* This is the line format index

3.3.7. Action Scheduler Table (as.tab)

RECORD DESCRIPTION TABLE NUMBER,INTEGER (I)

FUNCTION CODE,CHARACTER (C)

The NO-WAIT-FOR-READY Bit (Bit 2) can be used if a process is intended to generate

The PROCESS-LOGGING Bit (Bit 3) not used

The WRITE-DIRECT Bit (Bit 5) not used