4.4BSD/usr/share/man/cat1/mset.0

MSET(1)                      BSD Reference Manual                      MSET(1)

NNAAMMEE
     mmsseett - retrieve ASCII to IBM 3270 keyboard map

SSYYNNOOPPSSIISS
     mmsseett [--ppiicckkyy] [--sshheellll] [_k_e_y_b_o_a_r_d_n_a_m_e]

DDEESSCCRRIIPPTTIIOONN
     MMsseett retrieves mapping information for the ASCII keyboard to IBM 3270
     terminal special functions.  Normally, these mappings are found in
     _/_u_s_r_/_s_h_a_r_e_/_m_i_s_c_/_m_a_p_3_2_7_0 (see map3270(5)).  This information is used by
     the tn3270 command (see tn3270(1)).

     The default mmsseett output can be used to store the mapping information in
     the process environment in order to avoid scanning mmaapp33227700 each time
     ttnn33227700 is invoked.  To do this, place the following command in your
     _._l_o_g_i_n file:

           set noglob; setenv MAP3270 "`mset`"; unset noglob

     If the _k_e_y_b_o_a_r_d_n_a_m_e argument is not supplied, mmsseett attempts to determine
     the name of the keyboard the user is using, by checking the KEYBD envi-
     ronment variable.  If the KEYBD environment variable is not set, then
     mmsseett uses the user's terminal type from the environment variable TERM as
     the keyboard name.  Normally, mmsseett then uses the file map3270(5) to find
     the keyboard mapping for that terminal.  However, if the environment
     variable MAP3270 exists and contains the entry for the specified key-
     board, then that definition is used.  If the value of MAP3270 begins with
     a slash (`/') then it is assumed to be the full pathname of an alternate
     mapping file and that file is searched first.  In any case, if the map-
     ping for the keyboard is not found in the environment, nor in an alter-
     nate map file, nor in the standard map file, then the same search is per-
     formed for an entry for a keyboard with the name _u_n_k_n_o_w_n. If that search
     also fails, then a default mapping is used.

     The arguments to mmsseett are:

     --ppiicckkyy      When processing the various _m_a_p_3_2_7_0 entries (for the user's
                 keyboard, and all those encountered before the one for the
                 user's keyboard), mmsseett normally will not complain about en-
                 tries for unknown functions (like ``PFX1''; the --ppiicckkyy argu-
                 ment causes mmsseett to issue warning messages about these un-
                 known entries.

     --sshheellll      If the _m_a_p_3_2_7_0 entry is longer than the shell's 1024 environ-
                 mental variable length limit, the default mmsseett output cannot
                 be used to store the mapping information in the process envi-
                 ronment to avoid scanning _m_a_p_3_2_7_0 each time ttnn33227700 is in-
                 voked.  The --sshheellll argument causes mmsseett to generate shell
                 commands to set the environmental variables MAP3270,
                 MAP3270A, and so on, breaking up the entry to fit within the
                 shell environmental variable length limit.  To set these
                 variables, place the following command in your _._l_o_g_i_n file:

                       mset -shell > tmp ; source tmp ; /bin/rm tmp

     _k_e_y_b_o_a_r_d_n_a_m_e
                 When searching for the _m_a_p_3_2_7_0 entry that matches the user's
                 keyboard, mmsseett will use _k_e_y_b_o_a_r_d_n_a_m_e instead of determining
                 the keyboard name from the KEYBD or TERM environmental vari-
                 ables.

FFIILLEESS

     /usr/share/misc/map3270  keyboard mapping for known keyboards

SSEEEE AALLSSOO
     tn3270(1),  map3270(5)

HHIISSTTOORRYY
     The mmsseett command appeared in 4.3BSD.

4.3 Berkeley Distribution        June 6, 1993                                2