GT.M provides semi-automatic installation procedures using VMSINSTAL. VMSINSTAL displays a series of prompts. If a prompt has a default, VMSINSTAL displays the default answer in brackets [ ] after the prompt. Pressing <RETURN> enters the default.

To access help on a question, respond to the question with a question mark (?).

Issue the following DCL command to invoke VMSINSTAL:

$ @SYS$UPDATE:VMSINSTAL GTMnnn device:

Replace device with the name of the device used to mount your GT.M software. Replace nnn with the version number of the current release (refer to the GT.M Release Notes). If you do not enter this complete command, the system will prompt you for this information later in this procedure.

The following messages display:

OpenVMS Software Product Installation Procedure Vx.x-x
It is dd-mmm-yyyy at hh:mm.
Enter a question mark (?) at any time for help.

If there are other users on the system, VMSINSTAL issues the following warning message and lists the users:

%VMSINSTAL-W-ACTIVE, The following processes are still active:

If the warning was issued, VMSINSTAL requests confirmation before continuing.

* Do you want to continue anyway [NO] ?

Fidelity strongly recommends that, prior to upgrading a GT.M version, all processes of the version being upgraded be exited and the database be rundown. Otherwise, unpredictable results may occur. An alternative method is to install the new release in a separate directory.

GT.M software can be installed with DECnet when there are active users on the system. Changing the distribution while users are actively using an earlier version of GT.M may work with some releases. However, if the database files are modified by the new release, or if recompilation of M code is required, all GT.M users should exit and the database(s) rundown before installing the new software. Refer to the Release Notes for the distribution to determine if this is necessary. An alternative is to install a new release in a different directory.

* Are you satisfied with the backup of your system disk [YES]?

Enter Y(es) to proceed, or <RETURN>. Press N(o) to terminate the installation.

If there are no other users or you elect to continue, VMSINSTAL requests verification for whether you have a good backup of your system disk.

* Are you satisfied with the backup of your system disk [YES]?

The installation of a GT.M distribution kit which does not update the database file format does not, by itself, put any part of a system except for older copies of GT.M in the target directory at risk (except with older copies of GT.M).

* Are you satisfied with the backup of your system disk [YES]?

Enter <RETURN> or Y(es) to proceed. Enter N(o) to terminate the installation.

If you did not enter a complete VMSINSTAL command, with all parameters, the installation presents the following prompts.

* Where will the distribution volumes be mounted:

Enter the device, controller type and unit for the media where the distribution is to be mounted, (e.g., MSA0, MUA0, DUA0, MTA0).

* Products:

Enter the GTMnnn, replacing "nnn" with the current version number, or enter an asterisk (*) to process all products on the distribution media.

* Options:

Press <RETURN> unless you wish to use VMSINSTAL options.

VMSINSTAL displays a message asking you to physically mount the first distribution volume set on the selected device.

If the volume set is not already mounted, physically mount it.

* Are you ready?

Enter Y(es) to proceed or N(o) to terminate the installation.

Beginning installation of GTM Vnn.n at hh:mm

This message confirms that VMSINSTAL has started the installation of GT.M.

%VMSINSTAL-I-RESTORE, Restoring product saveset A ...

This message confirms that VMSINSTAL has located GT.M on the distribution media.

If the system's OpenVMS version does not match the GT.M distribution or if the largest disk has inadequate disk storage space to complete the installation, VMSINSTAL displays a message and terminates the installation at this point.

* Do you want to purge files replaced by this installation [YES]?

Some organizations have a policy of testing new software before purging old files. Answer according to the guidelines of your organization.

Press <RETURN> or Y(es) if you want VMSINSTAL to remove old versions of files provided by the installation. Press N(o) to retain any old files.

If you enter N(o), VMSINSTAL does not purge as part of the installation. Make a note to purge after testing.

* Do you want the standard GT.M configuration (performs INSTALL) [YES]?

For new or standard installations, Fidelity provides a quick and easy route to install your new software version. If you do not store or name your files in the standard way noted, press N(o). If you press Y(es), the following will happen automatically:

If you answer N(o) to the standard configuration, the questions continue as follows:

* What UIC should own the GT.M distribution [SYSTEM]:

Assigning a SYSTEM UIC to a language processor such as GT.M simplifies system security. The UIC can be a name, a group name and a user name separated by a comma or a pair of octal codes separated by a comma, specifying the group and user.

If the identifier SYSTEM is not defined in your rights database, the installation uses [1,4] for the default owner.

Press <RETURN> to assign the SYSTEM UIC or another UIC.

* Do you want the GT.M distribution to go into a System Directory [YES]?

Storing a language processor such as GT.M on the system disk simplifies system security and operations. If you have severe space constraints, you may need to use a different volume.

Press <RETURN> or Y(es) to place GT.M in a sub-directory of SYS$COMMON. Press N(o) to choose a different directory.

If you choose to store GT.M in the system directory, the installation prompts:

* In what System Directory do you want to place GT.M [GTM_DIST]:

By default, VMSINSTAL installs the GT.M software in a directory used specifically to hold GT.M modules. Institutions not concerned with mixing software from different sources may elect to use SYSLIB (sys$library) instead of GTM_DIST.

Press <RETURN> to place the GT.M files in a sub-directory of SYS$COMMON called GTM_DIST or enter another sub-directory of SYS$COMMON.

If the sub-directory does not exist, VMSINSTAL creates it later in the installation. The sub-directory has Read and Execute protection for all user classes.

If you chose not to store GT.M in the system directory, the installation displays the next two prompts:

* On which device do you want to place GT.M []:

The disk must have enough space to store GT.M and must be mounted at all times when GT.M is in use. The disk name can be physical or logical.

Enter an appropriate disk name to store the GT.M software.

* In what directory on that device do you want to place GT.M [GTM_DIST]:

Press <RETURN> to place the GT.M software in the default directory [GTM_DIST] or enter another directory.

If the sub-directory does not exist, VMSINSTAL creates it later in the installation. The directory has Read and Execute protection for all user classes.

Independent of the placement of the software, the installation continues.

* What do you want to call the configuration database [GTC.CNF]:

The configuration database holds information which permits normal operation of products licensed from Fidelity. The installation generates command procedures which define a logical name directing configuration activity to this file. Using a single configuration database file for all Fidelity products simplifies system management.

Press <RETURN> to name the configuration database file GTC.CNF, or enter another file specification.

* Do you want GTMSTART.COM in the startup database [YES]?

Placing GTMSTART.COM in the startup database simplifies operations, particularly when using GT.CM. OpenVMS automatically activates programs and procedures in the startup database during every normal system startup. The principal alternatives are editing SYSTARTUP_VMS.COM or having special procedures for starting GT.M.

Press <RETURN> or Y(es) to place GTMSTART.COM in the startup database. Press N(o) to allow GT.M startup to be handled by other means.

If you do not place GTMSTART.COM in the startup database, the installation asks the following question:

* Do you want the GT.M .COM files in SYS$MANAGER [YES]?

Copying the command procedures to SYS$MANAGER allows system startup to access them through the OpenVMS startup database and generally simplifies operations. However, if you have multiple GT.M versions on your system at the same time, you do not want to have multiple copies of the command procedures in SYS$MANAGER.

* Do you want the GT.M help files in SYS$HELP [NO]?

Storing the help files with the rest of the distribution keeps the entire GT.M distribution together. Some organizations prefer to keep all help files in SYS$HELP.

Press <RETURN> or N(o) to leave the GT.M help files with the rest of the GT.M distribution. Press Y(es) to place the help files in SYS$HELP.

* Do you want to define GT.M commands to the System [YES]?

Making GT.M accessible to many users is simplified by defining the GT.M commands in the system DCLTABLES. The principal alternatives are having each process define the commands during process startup or GT.M initialization, or using additional command tables. A method which modifies the command tables more frequently reduces process performance.

Press <RETURN> or Y(es) to define GT.M commands in the SYSTEM DCLTABLES. Press N(o) to make the definition process specific.

* Do you want to define GT.M logical names in the System Table [YES]?

Making GT.M accessible to many users is simplified by defining the GT.M logical names in the system logical name table. The principal alternative is defining them at the group or process level. A method which modifies logical name tables more frequently reduces process performance.

Press <RETURN> or Y(es) to define the GT.M logical names in the system table. Press N(o) to direct the definitions to be process specific.

* Do you want to define the LNK$LIBRARY logical names [YES]?

LNK$LIBRARY_n logical names point to libraries that are included by default when performing an image LINK under OpenVMS. GT.M has libraries that must be available when linking GT.M images.

Press <RETURN> or Y(es) if you want the installation procedures to find the next two available LNK$LIBRARY_n logical names and define them to point to the appropriate GT.M libraries. Press N(o), if you do not want this to happen automatically.

	If users have a different logical name environment than that of the installing process, the installation may choose inappropriate LNK$LIBRARY logicals. In this case, edit the GTMLOGICAL.COM procedure produced by the installation.

* Do you want to run the IVP (performs INSTALL) [YES]?

This installation kit contains an Installation Verification Procedure (IVP) which can run as part of the installation process. The IVP performs basic tests to verify that the software has been installed successfully.

To complete the tests, the GT.M Program Authorization Key (PAK) must be properly configured in the configuration database and some of the components of GT.M must be INSTALLed (i.e., made known to OpenVMS).

Enter <RETURN> or Y(es) to run the Installation Verification Procedure at the end of the installation, or N(o) to complete the installation without the test.

If you entered NO to running the Installation Verification Procedure, the installation displays the following prompt:

* Do you want to compile the GT.M percent routines (performs INSTALL) [YES]?

GT.M includes a set of programmer tools, called percent (%) routines (e.g., date conversion programs, global lister).

Press <RETURN> or Y(es), if you want these routines extracted from the text library and compiled. Press N(o), if you do not want these routines extracted.

If you answered N(o) to running the Installation Verification Procedure, and N(o) to compiling the M percent utilities, the installation asks the following question:

* Do you want to INSTALL the GT.M shareable images now [YES]?

If the shareable images are not installed as part of the installation procedure, GTMSECSHR must still be installed before any process can run GT.M.

Press <RETURN> or Y(es) to install the images at the end of the installation. Press N(o) to defer installing the images.

* Do you want to have a default definition for GTM$ROUTINES [YES]?

The logical name, GTM$ROUTINES, specifies a list of the possible locations for your GT.M programs. This enables M to find the routine (program) you want to run even if it is not in your current default directory.

Press <RETURN> or Y(es), if you want a default search definition added to the command file executed during an M user login (GTMLOGIN.COM). Press N(o) if you do not want this logical set up.

If you answered Y(es) to having a default GTM$ROUTINES, the installation presents the following prompt:

* What is the search specification for the default GTM$ROUTINES 
[[],GTM$DIST:]: ?

When a user or application requests a routine which is not in the image, GTM$ROUTINES specifies the RMS directory list in which the routine may be located. The default causes the system to search for the routine first in the user's current default directory and then in the distribution directory GTM$DIST. The installation stores the utilities supplied by Fidelity Information Services in GTM$DIST. The routine search specification can be easily changed later.

Press <RETURN>, if you want to use the default definition for your GTM$ROUTINES logical names, or enter your own definition.

Because GTM$ROUTINES provides a string to GT.M and does not act as an OpenVMS search list, enclose the items in the list with quotation marks (" ") when the list has more than one item.

* Do you want to have a default definition for GTM$GBLDIR [YES]?

Defining a default logical name for GTM$GBLDIR simplifies the use of GT.M, particularly for new users. To use a GT.M database, a GT.M user needs a Global Directory (GD). The logical name, GTM$GBLDIR, provides the most convenient way to establish a current GD. The GD to which GTM$GBLDIR points may vary from process to process.

Press <RETURN> or Y(es) to add a definition of GTM$GBLDIR to GTMLOGIN.COM. Press N(o) to leave the definition of GD's to be handled by some other means.

If you answered Y(es) to having a default definition for GTM$GBLDIR, the installation presents the following prompt.

* What is the file specification for the default GTM$GBLDIR [MUMPS.GLD]

The specified Global Directory file does not need to exist at this time. The file specification can be partial or complete. A partial file specification usually serves for development and a complete specification for production. The file specification can be easily changed later.

Press <RETURN> to accept MUMPS.GLD as the file specification for GTM$GBLDIR or enter a different one.

When you have answered all the questions, the installation continues with the following messages:

The following command files are created [and copied to SYS$MANAGER]:
GTMINSTALL.COM
GTMLOGICALS.COM
GTMLOGIN.COM
GTMSTART.COM
GTMSTOP.COM

Each file contains its own user documentation.
All the questions have been asked.
Installation now proceeds without your manual intervention for about 10-15 minutes.

If you answered Y(es) to using the standard configuration or YES to running the Installation Verification Procedure, the installation displays the following message:

Finally the Installation Verification Procedure tests the installation.

The installation provides updates on its progress by displaying the following messages:

%VMSINSTAL-I-RESTORE, Restoring product saveset B ...
%VMSINSTAL-I-RESTORE, Restoring product saveset C ...
%GTM-I-CRECOM, Creating command files
%GTM-I-PREFIL, Preparing distribution files for installation
%GTM-I-FININS, Finalizing the installation.
%VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories...

VMSINSTAL may also display PURGE warning messages.

The purge messages indicate failure to purge files in use. This is probably caused by not terminating all GT.M processes from the previously installed versions.

Once you reach this point, VMSINSTAL has placed the GT.M files on your system. If a failure occurs after this point and you understand how to correct the problem, you do not have to repeat the VMSINSTAL.

If you answered Y(es) to the standard configuration or Y(es) to the Installation Verification Procedure, the following messages appear interspersed with actions:

* GT.M Installation Verification Procedure
Verifying GDE.
Verifying MUPIP.
Verifying DSE.
Verifying direct mode MUMPS.
Verifying LKE.
Verifying GT.M MUMPS compiler.
The GT.M validation has been completed on dd-mmm-yyyy at hh:mm:ss.

In any successful case, VMSINSTAL completes the installation with the confirmation message:

Installation of GTM vnn.n completed at hh.mm

If you did not start the installation process with a complete VMSINSTAL command with all the parameters, the system prompts for the next product to be installed.

Enter the products to be processed from the next distribution volume set.

* Products:

Press <CTRL-Z> to exit VMSINSTAL.

VMSINSTAL exits with the message:

VMSINSTAL procedure done at hh.mm
$

Review the .COM files. You may want to revise the .COM files, particularly after you have some experience with GT.M.

Refer to the OpenVMS System Manager's Manual: Essentials and the OpenVMS System Management Utilities Reference Manual for more information on installing images.

Physically unload the GT.M distribution media and store it in a safe place.

To ensure that all GT.M databases are properly closed before OpenVMS terminates, place a copy or invocation of GTMSTOP.COM in the site-specific shutdown procedure SYS$MANAGER:SYSHUTDWN.COM.

Fidelity distributes its GT.M language system and related products over the Internet. To get the products using this medium follow these steps: