Overview [ Micro Focus COBOL System Reference, Volume 1 ] MPE/iX 5.0 Documentation
Micro Focus COBOL System Reference, Volume 1
Overview
Normally, the default keysbuilt into Adis should not need changing.
However, you may need to change the keys used to emulate a particular
dialect of COBOL.
The default set of keys used by your COBOL system is built into Adis.
Keybcf creates a file called cobkeympwhich contains the keystrokes that
are to be used for function keys and the keys Adis uses during an ACCEPT
operation. At run time, Adis checks for the presence cobkeymp in the
current directory. If the file is not found, then the COBOL system
directories are searched for the existence of cobkeymp. If the file is
found the set of keys defined in it are used. If not, the default set of
keys are used.
The Key Lists
The following lists of keys can be reviewed and altered by Keybcf:
* Adis function key list.
This list defines the keys which carry out specified functions
when you are executing an ACCEPT statement in a COBOL program.
See the chapter Standard Adis Key Functions for a description of
these keys.
*
Animator function key list.
This list is used by Animator and some other system programs.
* User function key list.
The user function key list defines the keys that are normally
returned to your program when a function key is pressed.
*
Compatibility function key list.
This list defines an alternative user key list that can be used if
you want to set up keys to be compatible with another dialect of
COBOL. If the values returned by such keys differ from the
standard user key list, you are advised to alter the compatibility
function key list rather than the user function key list. By
default, the compatibility function key list is configured for
compatibility with RM/COBOLV2.0 on UNIX.
ACCEPT/DISPLAY option 22 in Adiscf (see the section ACCEPT/DISPLAY
Options in chapter Adis Configuration Utility (Adiscf) for more
information) enables you to choose between using the user or
compatibility key lists.
By default, the user function keys are initially disabled. In order to
use these function keys during the execution of a program, you must first
enable them by calling the x"AF" library routine or by altering the
configuration using Adiscf.
The CRT STATUS clauseallows you to ascertain which function key was used
to terminate an ACCEPT operation. Full details on the use of this clause
can be found in your Language Reference.
cobkeymp Tables on UNIX
Values within the tables found in cobkeymp (or as the internal defaults)
which begin with the prefix KEY_ represent valuesthat have been
translated using the terminfo database and the UNIX terminal
handlinglibrary. These values are independent of the terminal you are
currently using, and thus you can define keys which are not actually
present on your particular keyboard.
You do not need to create a different cobkeymp file for each terminal
type on your system. Instead, try to ensure that your cobkeymp is
suitable for as many different types of terminal as possible. All
terminal specific decoding is done by the RTS using the terminfo
database. However, you may have to supply alternative keystrokesfor
those terminals which do not have special function keys. Full details on
the KEY_ values are given in your UNIX documentation.
If you decide to have multiple cobkeymp files
rather than using the above procedure, you can do this by renaming
cobkeymp and then setting up a dd_ environment variableat run time. For
example:
dd_cobkeymp=newname
causes the RTS to look for key configuration information in newname.
MPE/iX 5.0 Documentation