How to Disable Statements
Turn off any of the function or control keys (or arrow keys in UNIX or VMS) by using one of the following methods:
• Replace the original mapping statement with a disabling statement in the same mapping file
• Comment out the original mapping statement and place a disabling statement in the same mapping file
• Place a disabling statement in a key map file of higher precedence than the original mapping statement
If you do not want to edit or comment out the original mapping statement, leave the original mapping statement as is and place the disabling statement in a mapping file of higher precedence. For example, to disable a key mapped to an object in an installation-level or terminal-type mapping file, put a disabling statement in a user or application-level mapping file. To disable a key mapped to an object in a user-level mapping file, put a disabling statement in an application-level mapping file.
Once disabled, a key remains disabled until used in a mapping statement within a mapping file of higher precedence. For a discussion of precedence in key mapping, see the Key Mapping Overview section specific to your environment.
A disabling statement has the following syntax:
pfN|controlX|uparrow|downarrow|rightarrow|leftarrow = off
Windows:
The following statements disable Control-A and PF7 when placed in a mapping file or position of higher precedence than any assignment statement for these keys:
controlA = off
pf7 = off
UNIX and VMS:
The following statements disable Control-A, PF7, and the Right Arrow key when placed in a mapping file or position of higher precedence than any assignment statement for these keys:
controlA = off
pf7 = off
rightarrow = off
While these statements are in effect, using these disabled keys produces a beep from the terminal.
To disable a FRS command in a UNIX or VMS environment, map the FRS command to a control or function key (or to an arrow key), and then disable that key.
Last modified date: 08/28/2024