GT.M files require approximately 12,000 blocks of disk space. The installation kit temporarily requires 7 MB for Alpha and 4.5 MB for VAX.
Fidelity provides the GT.M files in VMSINSTAL (BACKUP) format in save sets named GTMnnn.a, where "nnn" identifies the version of GT.M and "a" identifies the alphabetically sequenced save set letters. The last save set contains the source code modules for the M "percent" utilities. The other files are:
|
GTMSECSHR.EXE |
A protected shareable image providing a mechanism for accessing selected system services. |
|
GTMSHR.EXE |
A shareable image containing the M run-time system and the compiler. |
|
GTM$DMOD.EXE |
An image for initiating Direct Mode. |
|
GTM$STOP.EXE |
An image which stops other GT.M images. |
|
MCOMPILE.EXE |
An image for initiating the M compiler directly from CLI. |
|
DSE.EXE |
An image containing the Data Structure Editor. |
|
GDE.EXE |
An image containing the Global Directory Editor. |
|
LKE.EXE |
An image containing the M Lock Editor. |
|
LMU.EXE |
An image containing the configuration management utility. |
|
MUPIP.EXE |
An image for performing data conversion and utility functions. |
|
GTMLIB.OLB |
A relocatable object file library containing the routine. GTM_MAIN, which is the mechanism that associates a user image and the GT.M run-time system. |
|
GTMSHR.OLB |
A shareable image symbol library containing universal symbols for the GTMSHR image. |
|
GTMZCALL.MLB |
A MACRO library for maintaining external call tables. |
|
GTMCOMMANDS.CLD |
A command definition file containing the MUMPS command. |
|
GTMCOLLECT.OPT |
A sample linker options file. |
|
GTM$DEFAULTS.MAR |
A macro source file containing default options for the GT.M run time environment. |
|
DSE.HLB |
A help library containing descriptions of the Data Structure Editor commands. |
|
GDE.HLB |
A help library containing descriptions of the Global Directory Editor commands. |
|
LKE.HLB |
A help library containing descriptions of the M LOCK Editor commands. |
|
LMU.HLB |
A help library containing descriptions of the configuration management commands. |
|
MUPIP.HLB |
A help library containing descriptions of the MUPIP commands. |
|
GTMINSTALL.COM |
A prototype procedure file which installs the GT.M images. |
|
GTMLOGICALS.COM |
A prototype procedure file containing the definition of logical names used by GT.M. |
|
GTMLOGIN.COM |
A prototype procedure file containing the definitions of symbols which invoke the GT.M utilities. |
|
GTMSTART.COM |
A prototype procedure file which invokes GTMINSTALL.COM and GTMLOGICALS.COM. |
|
GTMSTOP.COM |
A command file which stops all active GT.M processes and does a MUPIP RUNDOWN. |
Disk shadowing can yield significant performance improvements for typical M applications. Disk shadowing can reduce read access to the disk by 30 percent or more for a two disk shadow set. While read operations are significantly faster, there is a penalty for write operations. If your site uses applications which require heavy updating, disk shadowing may be inappropriate. For more information on disk shadowing, refer to the Volume Shadowing for OpenVMS or the OpenVMS System Manager's Manual: Essentials.
Disk striping also can yield significant performance improvements for typical M applications. Disk striping can improve the speed of both read and write operations. However, depending on your configuration, disk striping may reduce the mean time to failure of the disk system. Before deciding if this technique is appropriate for your site, refer to the OpenVMS documentation that describes which types are supported and how to use them.