Combining the environment variables DBHIF, DBTERM, and TERM gives the user a wide range of possibilities to adapt the terminal definition to his need and taste. The easiest way is to use the terminal descriptions from the distribution medium. If these files do not suit the user's need or taste, or if some other terminal type is to be used the key definitions can be adapted by means of "x_maketi". The result can be tested using "xvttest" and the step can be repeated until the user is satisfied. The user can choose the keyboard (DBHIF) and the terminal description file (DBTERM or TERM) he wants to work with.
Whenever there are strange effects in this area (like the tool not accepting a function key which should be known), the first thing to check is the usage date of the "terminfo" file ("$dbroot/terminfo" or "/usr/lib/terminfo") and of the "hif" file, if needed. The most likely error is the addition, removal, or change of an environment variable that influences the use of these description files.
For the call of an ADABAS tool, the following procedure is used:
The environment is searched for the variables "dbhif", "dbterm", and "term". With the first value found (in that order), the name of a "hif" file is constructed ("$dbroot/terminfo/term/<type>.hif"). If such a file is found its contents is taken as the function key definitions.
If "dbterm" is set "$dbroot/terminfo/?/$dbterm" is taken as terminal description file; otherwise, according to the standard, the terminal description file "/usr/lib/terminfo/?/$term" is used.
In case a "hif" file has been found, it only overrides the keyboard part of the terminal description file.
If a description change has no effect, it should be checked whether the new description file has been compiled by means of the program "tic" and whether the new "hif" file has been copied to "$dbroot/terminfo/term".