If any users will be connecting to the system using a terminal or terminal emulator software then the tools will need to know about these
To detect the important editing keys the character sequences need to be stored on a terminal definition item. This is done using this screen TRMMAN
Function keys can be mapped for each emulation type. Use TRMMAN to set up the character sequence for each emultor and check these are detected by the system by running MVCHECKS with this emuator.
Applications should try to restrict themselves to function keys
1-8 as f10 may be intercepted by common desktop operating systems.
Substitute keys can be used at any point as the help key description
is setable. Use
TMDMAN
to setup key descriptions.
This allows flexibility in programming the keys. Internally
a key may be detected as F1 but it may be descibed as Shift-f2 and
mapped to this alternative key to the users just press the key that
is descibed in the help on the
Screen Footer
complex character sequences
or Escape sequences can be traced to a specific key
if they are set up properly here. A sequence may even be
an extension of another keys character sequence and still be detected
The system continues to match the keyboard input buffer
until a character is found that breaks the sequence.
So it’s possible to map one function key to (27)ME
and another to (27)M where (27) is the ESCAPE character.
The layout of the terminal definition is defined in Terminal definition layout
The file storing terminal definitions is set up in the screen System Files