This is not a MacX problem. DECwindows applications may have features that
require keys not available on Macintosh keyboards. The keys you are
talking about are the top row of the numeric keypad. In an editor such as
EDT, these keys send the PFn keysyms and require special mapping.
VersaTerm-Pro works fine because it is a terminal emulator that correctly
sends the keysyms for these numeric keypad keys.
Page 17 of the PATHWORKS MacX User's Guide discussed this keyboard mapping
using a VAX/VMS application called MSAX$MODMAP. MSAX$MODMAP modifies and
displays mapping tables used by the X11 server to translate keystrokes to
key symbols. A mapping table tells the X Window System -- in this case,
MacX -- how to translate the keystrokes. The term keysymbol (or keysym)
refers to the individual location of a key as defined by the software.
MacX captures the signals generated by the keys specified in the mapping
table and translates them to key symbols that can be recognized by X11
client applications.
The remote command you used is fine. Once you are at the DECterm window
and before you start EDT, you should run the following command to map the
keyboard:
$ MCR MSAX$MODMAP MSA$EXAMPLES:MSAX$POSITIONAL_EXTENDED_KEYBOARD.DAT
You can choose to put this command in a command procedure to save typing.
I strongly suggest that you read about MacX keyboard mapping from the
manual to understand the other options available.