Create a backup copy of any existing version of GT.M before running the installation procedure. The installation procedure overwrites any existing version of GT.M in the installation target directory.

Never install a GT.M release into an existing directory overwriting another release that might be needed for research or recovery and never on the one currently in use. FIS recommends installing each version of GT.M in a separate directory using the naming convention /usr/lib/fis-gtm/version_platform , where version is the GT.M version being installed and platform is the hardware architecture. For example, /usr/lib/fis-gtm/V5.4-002B_x86_64.

Run the installation procedure as root for everything to install correctly. If using physical media, place it in the drive before starting.

Find or create a temporary directory to hold your GT.M distribution files and change to that directory.

Example:

$ cd /tmp

or

$ cd /usr/tmp

	When choosing a temporary directory, keep in mind the following points: Whether it is safe to use a directory (like /tmp) subject to concurrent use by the operating system, applications, and so on. Whether you can protect any sensitive information in temporary files with appropriate access permissions.

Copy the distribution to the current directory with a command similar to the following:

$ tar xovf /dev/rst0

	The name of the device and the tar options may vary from system to system.

The GT.M distribution contains various GT.M system administration scripts. These include:

configure      to install GT.M
gtmbase        to set up a default user environment
gtm            sets a default user environment and starts GT.M.     

For more information on using gtmbase and scripts, refer to Chapter 3: “Basic Operations”.

To start the GT.M installation procedure, execute the following script:

$./configure

The configure script displays a message like the following:

           GT.M Configuration Script
Copyright 2009, 2011 Fidelity National Information Services, Inc. Use of this
software is restricted by the provisions of your license agreement.

What user account should own the files? (bin) 

Enter the name of the user who should own GT.M distribution files. The default is bin. If there is no user with the name bin, the configure script asks for an alternate user who should own GT.M distribution files.

What group should own the files? (bin) 

Enter the name of the group who should own GT.M distribution files. The default is bin. If there is no group with the name bin, the configure script asks for an alternate group who should own GT.M distribution files.

Should execution of GT.M be restricted to this group? (y or n)

Choose y to restrict the ownership of your GT.M distribution to the specified group. This is a security-related option. By default, GT.M does not restrict the ownership to a group.

In what directory should GT.M be installed?

Enter a directory name, such as /usr/lib/fis-gtm/V5.4-002B_x86_64. If the directory does not exist, the configure script displays a message like the following:

Directory /usr/lib/fis-gtm/V5.4-002B_x86_64 does not exist. 
Do you wish to create it as part of this installation? (y or n)

Choose y to create the directory or n to cancel the installation.

Installing GT.M...

This is followed by a confirmation message for installing Unicode™ support.

Should unicode support be installed? (y or n)

Choose y to confirm. If you choose n, Unicode functionality is not installed.

	GT.M requires at least ICU Version 3.6 to install the functionality related to Unicode.

If you choose y, the configure script displays a message like the following:

Should an ICU version other than the default be used?

If you choose n, the configure script looks for the symbolic link of libicuuc.so to determine the default ICU version.

If you choose y, the configure script displays a message like the following:

Enter ICU version (at least ICU version 3.6 is required. 
Enter as <major-ver>.<minor-ver>):

Enter the ICU version number in the major-ver.minor-ver format. The configure script displays the following message:

All of the GT.M MUMPS routines are distributed with uppercase 
names. You can create lowercase copies of these routines 
if you wish, but to avoid problems with compatibility in 
the future, consider keeping only the uppercase versions 
of the files.

Do you want uppercase and lowercase versions of the MUMPS routines? (y or n).

Choose y to confirm. The configure script then displays the list of MUMPS routines while creating their lowercase versions. Then the script compiles those MUMPS routines and displays a message like the following:

Installation completed. Would you like all the temporary files removed from this directory? (y or n)

Choose y to confirm. FIS recommends deleting all temporary files.

Congratulations! GT.M is now installed on the system. Proceed to Chapter 3: “Basic Operations” to set up a default user environment.