Determining Keyboard Mapping

Shading, color, and key appearance are used in the Keyboard Setup dialog box to show how your keyboard is mapped. Cyan keys are mapped, by default, but their mappings can be changed.

Keys not appearing in cyan are not mapped. (Letter and number keys are not considered mapped because it is unlikely you would want to redefine the mappings for these keys.)

If you want to see how a key on the PC is mapped, click the key to select it; the key is selected. If this PC key is mapped to a terminal key, the corresponding key on the terminal keyboard, below, is also selected. For example, click the F1 key on the PC keyboard. It changes color, as does the F1 key (in 5250 sessions) or the PF1 key (in 3270 sessions) on the terminal keyboard. Click F1 on the PC keyboard again to clear the key.

Note: Num Lock key status affects the mapping: If you click the Num Lock key while the Keyboard Setup dialog box is open, you must exit and return to the dialog box before that change is reflected in the displayed keyboard mapping.

Some keys are mapped to Design Tool commands. For example, click the Caps Lock key on the PC keyboard. The terminal keyboard is replaced by a set of fields.

Caps Lock is mapped to the Design Tool command .Toggle(rc_CapsLockState), which turns capital letters on or off.

Click Caps Lock again to clear it.

If you click a modifier key (Alt, Ctrl, or Shift) on the PC keyboard, the color pattern on the remaining keys changes. For example, try clicking Alt. The keys that turn cyan are mapped to Alt. For example, in 5250 sessions, the F1 and D keys become cyan when you click Alt. This means that Alt+F1 and Alt+D are mapped in the Design Tool's default keyboard mapping.

Keys that appear dimmed when you click Alt, Ctrl, or Shift are currently mapped (in combination with the selected modifier key) and cannot be changed. Typically, these are keystrokes that are defined by Windows. For example:

© 1999-2007 Attachmate Corporation. All rights reserved. Terms of Use.