1MSET(1) 386BSD Reference Manual MSET(1) 2 3NNAAMMEE 4 mmsseett - retrieve ASCII to IBM 3270 keyboard map 5 6SSYYNNOOPPSSIISS 7 mmsseett [--ppiicckkyy] [--sshheellll] [_k_e_y_b_o_a_r_d_n_a_m_e] 8 9DDEESSCCRRIIPPTTIIOONN 10 MMsseett retrieves mapping information for the ASCII keyboard to IBM 3270 11 terminal special functions. Normally, these mappings are found in 12 /_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 13 the tn3270 command (see tn3270(1)). 14 15 The default mmsseett output can be used to store the mapping information in 16 the process environment in order to avoid scanning mmaapp33227700 each time 17 ttnn33227700 is invoked. To do this, place the following command in your 18 ._l_o_g_i_n file: 19 20 set noglob; setenv MAP3270 "`mset`"; unset noglob 21 22 If the _k_e_y_b_o_a_r_d_n_a_m_e argument is not supplied, mmsseett attempts to determine 23 the name of the keyboard the user is using, by checking the KEYBD envi- 24 ronment variable. If the KEYBD environment variable is not set, then 25 mmsseett uses the user's terminal type from the environment variable TERM as 26 the keyboard name. Normally, mmsseett then uses the file map3270(5) to find 27 the keyboard mapping for that terminal. However, if the environment 28 variable MAP3270 exists and contains the entry for the specified key- 29 board, then that definition is used. If the value of MAP3270 begins with 30 a slash (`/') then it is assumed to be the full pathname of an alternate 31 mapping file and that file is searched first. In any case, if the map- 32 ping for the keyboard is not found in the environment, nor in an alter- 33 nate map file, nor in the standard map file, then the same search is per- 34 formed for an entry for a keyboard with the name _u_n_k_n_o_w_n. If that search 35 also fails, then a default mapping is used. 36 37 The arguments to mmsseett are: 38 39 --ppiicckkyy When processing the various _m_a_p_3_2_7_0 entries (for the user's 40 keyboard, and all those encountered before the one for the 41 user's keyboard), mmsseett normally will not complain about en- 42 tries for unknown functions (like ``PFX1''; the --ppiicckkyy argu- 43 ment causes mmsseett to issue warning messages about these un- 44 known entries. 45 46 --sshheellll If the _m_a_p_3_2_7_0 entry is longer than the shell's 1024 environ- 47 mental variable length limit, the default mmsseett output cannot 48 be used to store the mapping information in the process envi- 49 ronment to avoid scanning _m_a_p_3_2_7_0 each time ttnn33227700 is in- 50 voked. The --sshheellll argument causes mmsseett to generate shell 51 commands to set the environmental variables MAP3270, 52 MAP3270A, and so on, breaking up the entry to fit within the 53 shell environmental variable length limit. To set these 54 variables, place the following command in your ._l_o_g_i_n file: 55 56 mset -shell > tmp ; source tmp ; /bin/rm tmp 57 58 _k_e_y_b_o_a_r_d_n_a_m_e 59 When searching for the _m_a_p_3_2_7_0 entry that matches the user's 60 keyboard, mmsseett will use _k_e_y_b_o_a_r_d_n_a_m_e instead of determining 61 the keyboard name from the KEYBD or TERM environmental vari- 62 ables. 63 64FFIILLEESS 65 66 /usr/share/misc/map3270 keyboard mapping for known keyboards 67 68SSEEEE AALLSSOO 69 tn3270(1), map3270(5) 70 71HHIISSTTOORRYY 72 The mmsseett command appeared in 4.3BSD. 73 744.3 Berkeley Distribution July 27, 1991 3 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133