This commit was generated by cvs2svn to track changes on a CVS vendor
[unix-history] / usr.bin / tn3270 / mset.1
CommitLineData
15637ed4
RG
1.\" Copyright (c) 1986, 1990 The Regents of the University of California.
2.\" All rights reserved.
3.\"
4.\" Redistribution and use in source and binary forms, with or without
5.\" modification, are permitted provided that the following conditions
6.\" are met:
7.\" 1. Redistributions of source code must retain the above copyright
8.\" notice, this list of conditions and the following disclaimer.
9.\" 2. Redistributions in binary form must reproduce the above copyright
10.\" notice, this list of conditions and the following disclaimer in the
11.\" documentation and/or other materials provided with the distribution.
12.\" 3. All advertising materials mentioning features or use of this software
13.\" must display the following acknowledgement:
14.\" This product includes software developed by the University of
15.\" California, Berkeley and its contributors.
16.\" 4. Neither the name of the University nor the names of its contributors
17.\" may be used to endorse or promote products derived from this software
18.\" without specific prior written permission.
19.\"
20.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
21.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
22.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
23.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
24.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
25.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
26.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
27.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
28.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
29.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
30.\" SUCH DAMAGE.
31.\"
32.\" @(#)mset.1 4.6 (Berkeley) 7/27/91
33.\"
34.Dd July 27, 1991
35.Dt MSET 1
36.Os BSD 4.3
37.Sh NAME
38.Nm mset
39.Nd retrieve
40.Tn ASCII
41to
42.Tn IBM
433270 keyboard map
44.Sh SYNOPSIS
45.Nm mset
46.Op Fl picky
47.Op Fl shell
48.Op Ar keyboardname
49.Sh DESCRIPTION
50.Nm Mset
51retrieves mapping information
52for the
53.Tn ASCII
54keyboard to
55.Tn IBM
563270 terminal
57special functions.
58Normally, these mappings are found
59in
60.Pa /usr/share/misc/map3270
61(see
62.Xr map3270 5 ) .
63This information is used by the
64.Xr tn3270
65command (see
66.Xr tn3270 1 ) .
67.Pp
68The default
69.Nm mset
70output can be used to store the mapping information in the process environment
71in order to avoid scanning
72.Nm map3270
73each time
74.Nm tn3270
75is invoked.
76To do this, place the following command in your
77.Pa .login
78file:
79.Bd -literal -offset indent
80set noglob; setenv MAP3270 "\(gamset\(ga"; unset noglob
81.Ed
82.Pp
83If the
84.Ar keyboardname
85argument is not supplied,
86.Nm mset
87attempts to determine the name of the keyboard the user is using,
88by checking the
89.Ev KEYBD
90environment variable.
91If the
92.Ev KEYBD
93environment variable is not set, then
94.Nm mset
95uses the user's terminal type from the environment variable
96.Ev TERM
97as the keyboard name.
98Normally,
99.Nm mset
100then uses the file
101.Xr map3270 5
102to find the keyboard mapping for that terminal.
103However, if the environment variable
104.Ev MAP3270
105exists and contains the entry for the specified keyboard, then that
106definition is used.
107If the value of
108.Ev MAP3270
109begins with a slash (`/') then it is assumed to be the full pathname
110of an alternate mapping file and that file is searched first.
111In any case, if the mapping for the keyboard is not found in
112the environment, nor in an alternate map file, nor in the standard map file,
113then the same search is performed for an entry for a keyboard with the name
114.Ar unknown .
115If that search also fails,
116then a default mapping
117is used.
118.Pp
119The arguments to
120.Nm mset
121are:
122.Pp
123.Bl -tag -width Fl
124.It Fl picky
125When processing the various
126.Pa map3270
127entries (for the user's keyboard,
128and all those encountered before the one for the user's keyboard),
129.Nm mset
130normally will not complain about entries for unknown functions (like
131.Dq PFX1 ;
132the
133.Fl picky
134argument causes
135.Nm mset
136to issue warning messages about these unknown entries.
137.It Fl shell
138If the
139.Pa map3270
140entry is longer than the shell's 1024 environmental variable
141length limit, the default
142.Nm mset
143output cannot be used to store the mapping information in the process
144environment to avoid scanning
145.Pa map3270
146each time
147.Nm tn3270
148is invoked.
149The
150.Fl shell
151argument causes
152.Nm mset
153to generate shell commands to set the environmental variables
154.Ev MAP3270 ,
155.Ev MAP3270A ,
156and so on, breaking up the entry to fit within the shell environmental
157variable length limit.
158To set these variables, place the following command in your
159.Pa .login
160file:
161.Bd -literal -offset indent
162mset -shell > tmp ; source tmp ; /bin/rm tmp
163.Ed
164.It Ar keyboardname
165When searching for the
166.Pa map3270
167entry that matches the user's keyboard,
168.Nm mset
169will use
170.Ar keyboardname
171instead of determining the keyboard name from the
172.Ev KEYBD
173or
174.Ev TERM
175environmental variables.
176.Sh FILES
177.Bl -tag -width /usr/share/misc/map3270 -compact
178.It Pa /usr/share/misc/map3270
179keyboard mapping for known keyboards
180.El
181.Sh SEE ALSO
182.Xr tn3270 1 ,
183.Xr map3270 5
184.Sh HISTORY
185The
186.Nm mset
187command appeared in
188.Bx 4.3 .