GT.M V5.3-004 adds major new functionality and platform support.
* Database encryption. GT.M on selected platforms can encrypt data in database and journal files. Encryption protects against unauthorized access to data by an unauthorized process which is able to access disk files, that is, encryption protects data at rest (DAR) to help improve security in cloud based application deployment, as well as making it easier for sites to comply with data protection standards such as PCI and HIPAA. A plug-in architecture facilitates use of your preferred encryption software. Details are in the GT.M Database Encryption Technical Bulletin (http://www.fidelityinfoservices.com/FNFIS/Markets/NonFinancialIndustries/Healthcare/GTM/UNIX-DatabaseEncryption.htm).
* Alias variables. Intended to provide an underlying technology for implementing an object layer, alias variables provide a layer of abstraction between the name of a local variable and an array analogous to that provided by M pass by reference in subroutine invocations. Multiple local variables can be aliases, and a SET or KILL to one acts as a SET or KILL to all. Alias container variables provide a way of storing a reference to a data-space in an M sparse array, which protects the associated array even when it’s not accessible through any current name. Details are in the GT.M Alias Variables Technical Bulletin (http://www.fidelityinfoservices.com/user_documentation/html/rn_tb/GT_M_Alias_Variables_Te.html).
On UNIX/Linux platforms, the database file size limit has been increased from 128M to 224M blocks. So using the popular 8KB block size, the largest database file that can be created is 1,792GB. Of course, since a complete database can consist of an arbitrary number database files, the size of a complete database can be truly enormous.
There are performance enhancements, among others, especially for applications that use Transaction Processing. Compilation is faster and uses less memory. MUPIP LOAD is much faster in UTF-8 mode. There are of course smaller enhancements, remedied misfeatures, and bug fixes. Details are in the GT.M V5.3-004 Release Notes (http://www.fidelityinfoservices.com/user_documentation/html/rn_tb/GT_M_V5_3_004_Release_N.html).
Source code and executables for FOSS (AGPL v3) software can be downloaded from Source Forge (http://sourceforge.net/projects/fis-gtm) for the x86 GNU/Linux and Tru64 UNIX & OpenVMS on Alpha/AXP platforms. Support on commercial terms is available on all platforms.
For anyone using MUMPS implementations on Alpha/AXP, http://www.fidelityinfoservices.com/FNFIS/Markets/NonFinancialIndustries/Healthcare/GTM/SuggestedPractices_1.htm describes how to migrate from your current MUMPS on Alpha/AXP OpenVMS to GT.M on x86 GNU/Linux in a series of small, reversible steps that removes the need for any big-bang conversion.