MiniM. Saving time.

| About | Download | Tools | Knowledge Base | How to Buy |

MiniM Overview

Getting Started




Cache Tools

GT.M Tools

Knowledge Base




MiniM Additional Tools | Nov 19, 2016

GT.M Tools for FIS GT.M

Download GT.M Tools
* Requirements and Installers
* Installing on Windows
* Installing on Linux
* Installing on MacOSX
* Server Part
GT.M Tools
* Define Connections
* Global Editor
* Global Editor Settings
* Routine Editor
* Routine Editor Settings
Uninstall GT.M Tools
* Uninstalling on Windows
* Uninstalling on Linux
* Uninstalling on MacOSX
* Disable Server Part
Purchase GT.M Tools License
Documentation in one PDF file


Define Connections

GT.M Routine Editor and GT.M Global Editor both uses connection definition. It is set of data - TCP/IP address or TCP/IP host name of the GT.M server, TCP/IP port used by GT.M Tools daemon, and, optional, character encoding used to transfer data between server and client sides.

GT.M Tools offer to select, or edit, or define new connection definition. Versions for different operating systems can vary.

GT.M Tools Connections for Windows

One connection must have name, unique inside of all defined connections. Consult with system administrator what TCP/IP address or TCP/IP host name is used by GT.M server to connect to.

Edit Connection for Windows

Most important data what need to be know there is default value of TCP/IP port used by GT.M Tools daemon. By default installation it is number 5002. This value can be changed on the server and you must know real value.

GT.M Tools Connections for Linux

Edit Connection for Linux

GT.M Tools Connections for MacOSX

Edit Connection for MacOSX

Be careful with definition of character encoding. This is main rule how GT.M Routine Editor or GT.M Global Editor must decode and encode data sent from GT.M and to GT.M. Some global records, lines in routines or localised strings in compiler or error messages are required this rule to show characters correctly.

If you use character encoding other than used on the server, you will see it. Reconnect running GT.M Tools and edit connection definition again, choose right character encoding.

Both GT.M Tools automatically detect on connection what encoding is currently used by the server and read value of system variable


This variable can contains only two values - "M" and "UTF-8". If value is "M", GT.M Tools use character encoding as was specified in connection definition. And. if value of $zchset is "UTF-8", both tools does not use any character encoding and decoding, becouse client side use internal builtin UTF-8 encoding and data transfers as is, without any transformations and both sides works in native encoding.

All defined connection definitions are stored in Windows Registry or in secial subdirectories in depending of rules of client operating system. Both applications of GT.M Tools are used the same list of connection definitions and definition was defined in Global Editor will is visible by Routine Editor.

Global Editor

GT.M Global Editor shows global tree as a tree. Select in top of the window available global name. Or enter name of global (optional indices are possible) and press Enter.

GT.M Global Editor for Windows

Select need global node and editor in the bottom of window show the value of this global record if this record exists.

Data of global record can be viewed and edited as simple string in MUMPS notation.

GT.M Global Editor for Linux

At the right of data editor are two buttons - to write new value of this global record to database and to kill this global record.

GT.M Global Editor for MacOSX

Editing of node value uses MUMPS notation and there can be used non-printable characters with $c() function, other system builtin functions supported by GT.M and builtin system variables.

If GT.M Global Editor expects that value contains characters with code less than 32, then substitutes string with $C(...) function to produce MUMPS-readable value.

Editing non-printing characters

Global Editor Settings

Some global records GT.M Global Editor show as thee dots (...) or in short form. See current Global Editor settings to change this values.

This settings are used by GT.M Global Editor to prevent big time to fetch millions unneed record names.

Limitation for string length is used to prevent showing large unneed extra characters in tree. Data editor, of course, shows full global record as is.

To show data of global records correctly, combine character encoding and font.

Routine Editor

GT.M Routine Editor can load for editing, edit, save and compile routines on the GT.M server.

GT.M Routine Editor for Windows

GT.M Routine Editor can look different in depending of version and operating system.

GT.M Routine Editor for Linux

GT.M Routine Editor can search text in currently opened routine as such as in routines in the database. Search can use simple text and regular expressions. Regular expressions are very usable to find, for example text with any character inside, text only after beginning of line, etc.

GT.M Routine Editor for MacOSX

GT.M Routine Editor can import and export from currently connected GT.M database's globals and routines. Both export and import are use local filesystem, not a server. Routines and globals are transferred to and from the server by small parts, so import and export of big number of data can be long.

In most cases export and import of several routines are not so long.

Be careful while define export and import - GT.M Routine Editor support several formats, use really needed.

At bottom of the window GT.M Routine Editor contains two lists of output results - with compilation report and with search report. In both lists editor supports double-click on the line to going on the line with found substring or compilation error.

At the top of the window editor shows list with labels available in the currently editing routine and can going on the line with this label or with label and optional plus "+" sign and offset.

At any place of currently editing routine editor can detect substring which is possible label to going to and offer it in popup menu at right mouse click or showing context menu in MacOSX.

GT.M server have special database organization and stores routines in directories of server's file system. This is a set of directories and rule about location of routines is specified in the system variable $zgbldir. While GT.M Routine Editor opens existing routine, the place of this routine as a file directory on the server reads too and Routine Editor remembers about it and uses on saving.

If Routine Editor need to save newly created routine, he reads list of available directories for routine setted up by GT.M administrator and offers to select one of available directory and remember it to use later for this routine.

Select Routine Directory

On importing routines from routine archive Routine Editor offers to select directory too and apply this rule to all routines in this archive.

Directory list for routines on the server can have complex rules and Routine Editor uses fully qualified names, in full normalized form and removes duplicates if they are exist.

Routine Editor Settings

GT.M Routine Editor uses colored syntax highlighting. Syntax highlightning was developed using one of last GT.M version, but it can be not least. From time to time can be added some builtin system functions or system variables, so syntax highlightning must be corrected to be right for new GT.M version. Write to support of GT.M Routine Editor at and describe your needs and point to GT.M documentation of new language elements.

GT.M Routine Editor Options for Windows

GT.M Routine Editor Options for Windows

Bottom of GT.M Routine Editor window contains lists with results of translation of routines and with search results. If you see incorrect characters, you need to combine character encoding (setting of connection) and font.

GT.M Routine Editor Options for Linux

GT.M Routine Editor Options for MacOSX

All settings of GT.M Routine Editor are stored in depending of operating system - in Windows Registry or in special settings files in home user directory.

See next part, uninstalling GT.M Tools

Download GT.M Tools
Purchase GT.M Tools License
Documentation in one PDF file

Eugene Karataev

Copyright (C) Eugene Karataev
Info Support