It is recommended to use "x_maketi" in the directory "$dbroot/terminfo".
See the description of "hif" files later on before using "x_maketi".
The tool has the following call syntax:
"x_maketi" uses an existing binary terminfo file as start data, this is taken from the tree rooted at the "$terminfo" value or, if that environment variable is not set, at "/usr/lib/terminfo". The terminal type is taken from the environment variable ("dbterm" or "term"). This type is used for the output file name "<$term>.ti" if the user does not get another type name by the option '-T' or force another file name by the option '-o'.
If the description does not yet exist the user must give the option '-I' to use some similar terminal description as input. In this case, the '-d' option should also be given to force a complete redefinition of all function keys.
If after calling "x_maketi" the cursor keys have not yet been defined, the user is asked to press the keys which serve to move the cursor. These keys are needed to navigate in the following menu. The tool displays a menu containing the names of all function keys which are known by the ADABAS tools; those keys for which the current terminal description contains a definition are underlined (if supported by the terminal).
The cursor is on a function displayed in the menu and can be moved up and down, left and right by the four cursor keys to point to any other function. For the key so addressed, its definition (corresponding character sequence) is shown in the field "current value". When the user presses a function key or a combination of function keys on the keyboard, the character sequence sent by the terminal is displayed and the pressed key or combination of keys is assigned to the current function. After the assignment, the tool waits 2 seconds, which is indicated by "waiting" displayed in the right upper corner of the screen.
But the user can also delete the assignment of a key by entering 'd'.
"x_maketi" is terminated by entering 'e', this causes the list of presently current values to be written to the output file.
If there are problems with the analysis of the character sequences (possible especially with remote login) "x_maketi" should be called with the '-e' option. In this case, every input must be
terminated by pressing the escape key three times. That key is labeled 
; if it is missing on the keyboard the code can also be generated by the combination of 
("control") and '[' (opening square bracket).
Examples:
DBTERM=dap4x x_maketi -T ba80-ct03
or
DBTERM=ba80-ct03 x_maketi -I dap4x
generates '$DBROOT/terminfo/ba80-ct03.ti' with the same
properties as the dap4x.
The resulting description file must then be compiled into a binary format. To protect the existing descriptions, the new binary file should not be written to the default tree (rooted at "/usr/lib/terminfo") but to the directory provided by ADABAS, "$dbroot/terminfo".
Using the Bourne shell, this is done by entering
TERMINFO=$DBROOT/terminfo tic -v <TERM>.ti
Using the C shell, the command sequence is:
setenv TERMINFO $DBROOT/terminfo
tic -v <TERM>.ti
unsetenv TERMINFO
This new description file will be used by the ADABAS tools if the user provides the environment variable "dbterm": not only does its value override that of "term", its existence also implicitly sets the environment variable "terminfo" to "$dbroot/terminfo", but only while working with ADABAS. After leaving an ADABAS tool, "terminfo" again has the previously set value.