The gtm_dist environment variable specifies the path to the directory containing the GT.M system distribution. gtm_dist must be defined for each user. Users may want to define gtm_dist in the login file, or as part of the default system environment.

You can define gtm_dist as follows:

$ gtm_dist=<distribution directory>
$ export gtm_dist

For example, if the GT.M distribution is in /usr/local/gtm, enter:

$ gtm_dist=/usr/local/gtm

gtm_dist is used to establish communications with the GT.M gtmsecshr daemon and for the location of GT.M components.

Add $gtm_dist to the system environment variable PATH as follows:

$ PATH=$PATH:$gtm_dist
$ export PATH

The gtm_log environmental variable specifies a directory where the gtm_secshr_log file is stored. The gtm_secshr_log file stores information gathered in the gtmsecshr process. Fidelity recommends that a system-wide default be established for gtm_log so that gtmsecshr always logs its information in the same directory, regardless of which user's GT.M process invokes gtmsecshr.

The gtmgbldir environment variable identifies the global directory to be used. A global directory maps global variables to physical database files, and is required to access M global variables. Users who maintain multiple global directories must choose one to use. To automate this definition, define gtmgbldir in the user's login file.

The following is an example of a gtmgbldir definition:

$ gtmgbldir=/usr/staff/mumps.gld
$ export gtmgbldir

The gtmroutines environment variable specifies a directory search list of possible locations for M routines. This search enables GT.M to find the routine (program) that a user wants to run even if it is not in the current working directory. Fidelity Information Services recommends the inclusion of $gtm_dist in the list of directories specified in gtmroutines permits access to the Global Directory Editor (GDE) and to utility routines supplied with GT.M.

The following is an example of a gtmroutines definition, assuming that $ gtm_dist has been defined:

$ gtmroutines=". $gtm_dist"
$ export gtmroutines

This specifies that GT.M first search for a routine in the current directory, then in the distribution directory (included in the list because it contains the percent routines). Users may want the search list to contain these at a minimum; in addition, to including other directories. See "$ZROUTINES" section of the "Intrinsic Special Variables" chapter in the GT.M Programmer's Guide for details on gtmroutines syntax.

Users must set the environment variable TERM to a terminfo entry that accurately matches the terminal (or terminal emulator) settings. Refer to the terminfo man pages for more information on the terminal settings of the platform where GT.M needs to run.

Some terminfo entries may seem to work properly but fail to recognize function key sequences or position the cursor properly in response to escape sequences from GT.M. GT.M itself does not have any knowledge of specific terminal control characteristics. Therefore, it is important to specify the right terminfo entry to let GT.M communicate correctly with the terminal. Users may need to add new terminfo entries depending on their specific platform and implementation. The terminal (emulator) vendor may also be able to help.

GT.M uses the following terminfo capabilities. The full variable name is followed by the capname in parenthesis.

auto_right_margin(am), clr_eos(ed), clr_eol(el), columns(cols), \
cursor_address(cup), cursor_down(cud1), cursor_left(cub1), \
cursor_right(cuf1), cursor_up(cuu1), eat_newline_glitch(xenl), \
key_backspace(kbs), key_dc(kdch1), key_down(kcud1), key_left(kcub1), \
key_right(kcuf1), key_up(kcuu1), key_insert(kich1), keypad_local(rmkx), \
keypad_xmit(smkx), lines(lines).

GT.M sends keypad_xmit before terminal reads for direct mode and READs (other than READ *) if EDITING is enabled. GT.M sends keypad_local after these terminal reads.

GT.M uses ICU 3.6 to perform Unicode™-related operations. GT.M generates the distribution for Unicode only if ICU 3.6 (or above) is installed on the system. Therefore, install an appropriate ICU version before installing GT.M to perform functionality related to Unicode™. Note that the ICU installation instructions may not be the same for every platform.

This section describes all environment variables that a user must define to operate GT.M with Unicode support.

gtm_dist

The gtm_dist environment variable specifies the path to the directory containing the GT.M system distribution for Unicode. The distribution for Unicode is located in subdirectory utf8 under the GT.M distribution directory.

For example, if the GT.M distribution is in /usr/local/gtm, enter:

$ gtm_dist=/usr/local/gtm/utf8 ; 
$ export gtm_dist

Add $gtm_dist to the system environment variable PATH as follows:

$ PATH=$PATH:$gtm_dist
$ export PATH

gtm_dist is used to establish communications with the GT.M gtmsecshr daemon and for the location of GT.M components.

	GT.M generates the distribution for Unicode only if ICU 3.6 (or above) is installed on the system. Therefore, installing ICU is a prerequisite for GT.M to perform functionality related to Unicode.

$ gtmroutines=". $gtm_dist `echo $gtm_dist | sed 's/utf8\(\/\)*//'`"
$ export gtmroutines
echo $gtmroutines 
. usr/local/gtm/utf8 /usr/local/gtm/ 

GT.M operates in two mode - M mode and UTF-8 mode. Users can use either M mode or UTF-8 mode depending on the character set of the underlying data. Users must set GT.M to:

The following is a sample command sequence to change the system environment from M mode to UTF-8 mode. Assume that $ gtm_dist has been defined and is set to /usr/local/gtm:

gtmroutines=". $gtm_dist/utf8 $gtm_dist"
export gtmroutines
gtm_dist=$gtm_dist/utf8
export $gtm_dist
$gtm_chset="UTF-8"
$export gtm_chset 

The following is a sample command sequence to change the system environment from UTF-8 mode to M mode. Assume that $ gtm_dist has been defined and is set to /usr/local/gtm/utf8:

$gtm_dist=`echo $gtm_dist | sed 's/utf8\(\/\)*//'`"
$ export gtm_dist
$ gtmroutines=". $gtm_dist" 
$ export gtmroutines 
$ gtm_chset="M"

Execute the script gtmbase from that user's directory. Specify the complete path to the directory in which GT.M was installed:

$ /<gtm_dist pathname>/gtmbase

This script adds GT.M to that user's system path, defines GT.M environment variables required for normal use, and accordingly updates that user's login file (.profile file for Bourne shell or .cshrc for the C shell). The script defines the GTM environment variables as follows:

Now that user can run GT.M and its utilities without specifying a full path to the directory in which GT.M was installed.

Add following line to .profile or .cshrc file depending on the shell of that user.

In the Bourne shell add the following line to .profile:

<gtm_dist pathname>/gtmprofile 

In the C shell, add the followign line to .cshrc:

source <gtm_dist pathname>/gtmcshrc

In both cases, specify the required full path name to the directory where GT.M was installed.

This creates the GT.M environment variables (See Procedure 1 for the list of environment variables) and updates that user's system path to include the directory where GT.M is installed.

Define all the environment variables and aliases in the .profile file of that user. Production application users generally need commonly used commands in their .profile file as well.

Add the following files to that user's .profile file. Replace <dist dir area> with the directory in which GT.M is installed and <global directory path and file name> with the location of the global directory.

gtmgbldir=mumps.gld
export gtmgbldir          
gtm_dist=<gtm_dist pathname>
export gtm_dist
gtmroutines=". $gtm_dist"
export gtmroutines
gtmgbldir=<global directory path and file name>
export gtmgbldir
PATH=$PATH:$gtm_dist
export PATH