A significant new release, V5.2-000 is now available. This adds support for the Unicode™ 5.0.0 Standard (releases of Unicode™ and ISO/IEC-10646 track each other). The Unicode™ Standard provides a single encoding to represent every character in any major modern language, significantly expanding the usefulness of GT.M as an application development platform worldwide.
The GT.M database engine could always store arbitrary sequences of bytes as both subscripts and values. The engine is unchanged in V5.2-000.
What is new is that the sequences of bytes can either continue be interpreted as sequences of bytes or as sequences of characters encoded in UTF-8. Which interpretation applies is determined at the process level - the same database can concurrently be accessed by processes interpreting the contents as UTF-8 and processes not so interpreting the contents.
In order to use the functionality related to the Unicode™ Standard, GT.M V5.2-000 requires International Components for Unicode™ (ICU - http://icu.sourceforge.net) version 3.6 to be installed. Refer to the V5.2-000 release notes for details.
Effective V5.2-000, GT.M on the x86 GNU/Linux platform is compiled to require a 686 (Pentium Pro) or better CPU.
To use the software under the GNU General Public License (GPL -
http://www.gnu.org/licenses/gpl.txt) on x86 GNU/Linux and Tru64 UNIX and OpenVMS on Alpha/AXP, you can download the software from the GT.M project page at Source Forge (http://sourceforge.net/projects/sanchez-gtm). [GT.M on OpenVMS does not support the Unicode™ Standard.]
Customers who are using the software on licenses other than the GPL, and who have purchased GT.M support can download GT.M from the FTP site. Please contact GT.M support for the current URL/password when you are ready to download the software.
As a precaution against errors in transmission and other causes of damage to distribution files, checksums are available. Use "cksum <file>" to compute and print the checksum on UNIX/Linux platforms. Please note:
On the Alpha/AXP Tru64 UNIX platform, the environment variable CMD_ENV needs to be set to "xpg4" (e.g., with the shell command export CMD_ENV=xpg4) when using cksum.
For Alpha/AXP OpenVMS from the FTP site, please use the OpenVMS, use the checksum <file> command, which sets the symbol CHECKSUM$CHECKSUM to the checksum.
The GPPL distribution for the Alpha/AXP OpenVMS platform consists of OpenVMS save sets bundled together in a zip file. Please use cksum on a UNIX/Linux system to verify the checksums.
For software from the FTP site:
2160824576 145801 dbcertify_V52000_linux_i686_pro.tar.gz
1001895915 4499161 gtm_V52000_linux_i686_pro.tar.gz
624955066 152408 dbcertify_V52000_aix_rs6000_pro.tar.gz
3034540772 10136356 gtm_V52000_aix_rs6000_pro.tar.gz
2749471030 200786 dbcertify_V52000_hpux_parisc_pro.tar.gz
3906136440 6812994 gtm_V52000_hpux_parisc_pro.tar.gz
2439490162 210954 dbcertify_V52000_solaris_sparc_pro.tar.gz
4270187584 14546712 gtm_V52000_solaris_sparc_pro.tar.gz
1717385614 212153 dbcertify_V52000_osf1_alpha_pro.tar.gz
656324984 6422958 gtm_V52000_osf1_alpha_pro.tar.gz
GTCD52000.A : checksum = [1767203067]
GTCM52000.A : checksum = [1272030773]
GTDC52000.A : checksum = [3997038703]
GTM52000.A : checksum = [1449176647]
GTM52000.B : checksum = [1449176647]
GTM52000.C : checksum = [1449176647]
For software downloaded from Source Forge under the GPL:
3636218364 153086 dbcertify_V52000_linux_i686_pro.tar.gz
537805696 4507974 gtm_V52000_linux_i686_pro.tar.gz
3561327796 2738059 gtm_V52000_linux_i686_src.tar.gz
4224095878 219888 dbcertify_V52000_osf1_alpha_pro.tar.gz
2146313490 6433628 gtm_V52000_osf1_alpha_pro.tar.gz
150142956 2751749 gtm_V52000_osf1_alpha_src.tar.gz
1302867924 5454263 gtm_V52000_openvms_alpha_pro.zip
2548382587 4021162 gtm_V52000_openvms_alpha_src.zip
There is no difference in GT.M binaries released on Source Forge vs. the GT.M FTP site. However, since the software is released at Source Forge under the GPL, the packages include a COPYING file which alters the checksums. Source tarballs are available at Source Forge.
Please remember to use download using binary FTP.
For further information, please contact K.S. Bhaskar (ks.bhaskar@fnis.com).