Section 6. Keyboard Labeling

 

We mention in Section 4that the InSight Dump Formatter attempts to connect to the MIB to resolve corresponding function codes and key label text for Keyboard events. In this section we describe how to define the key label texts in the MIB so that the InSight Dump Formatter will include the specified key labels in the output file.

 

An ASCII editable file, QSA_DB:qsalabls.dat, contains all configurable key information. Once an InSight terminal comes online with the InSight Controller Agent, this file is populated with default properties. These properties are also stored in the InSight controller database (MIB).

 

There are two ways that you can make changes to the key label texts.

 

You can use the InSight UI to configure the key labels which will write to the MIB, which in turn will write to QSA_DB:qsalabls.dat.

Or you can edit or replace this file with one you have edited with your favorite text editor.

 

The format of this file is as follows. For example the ENTER key has the following attributes:

fc080Text="Enter"

fc080Abbr="Enter"

fc080Alpha=" "

fc080TextColor="00000000"

fc080BackGroundColor="0000FFFF"

 

This states that for function code 80, the label text (fc080Abbr) is Enter.

 

The other attributes are used primarily for the UI when it presents to the user a graphical representation of the terminal keyboard.

 

After you have updated this file, the controller agent will detect that changes have been made and these changes are automatically imported into the MIB. The next time that the InSight Dump Formatter is run and connects to this MIB, the updated key label texts will appear next to the appropriate Keyboard Device Events Queueentry.

 

If the qsalabls.dat file is deleted, a new qsalabls.dat will be created by the InSight controller agent using the properties from its internal MIB.