HP 3000 Manuals

Overview [ COBOL/HP-UX Operating Guide for the Series 700 and 800 ] MPE/iX 5.0 Documentation


COBOL/HP-UX Operating Guide for the Series 700 and 800

Overview 

Normally, the default keys 
built 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 cobkeymp 
which contains the keystrokes that are to be used for function keys and
the keys ADIS uses during an ACCEPT. At run time, ADIS looks for the
presence of cobkeymp in the current directory.  If the file is not found,
then the COBOL system directories are searched for the existence of the
cobkeymp file.  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 will carry out specified
       functions when you are executing an ACCEPT statement in a COBOL
       program.  These keys are described later in this chapter.

   *    

       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 wish 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/COBOL 
       V2.0 on UNIX.

       One of the accept/display options in the ADISCF program allows 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 clause 
       allows 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 the Language Reference.

       Values within the tables found in cobkeymp (or as the internal
       defaults) which begin with the prefix KEY_represent values 
       which have been translated using the terminfo database and the
       UNIX terminal handling 
       library.  See Figure 13-1 for details.  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 file 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 keystrokes 
       for 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 variable 
       at run-time.  For example:

            dd_cobkeymp=newname

       causes the RTS to look for key configuration information in
       "newname".

       KEYBCF does not accept keystrokes defined in Unixkmap. 



MPE/iX 5.0 Documentation