$ZVersion
$ZVersion
$ZV[ERSION] contains a string value specifying the currently installed GT.M. $ZV[ERSION] is a space-delimited string with four pieces as follows:
<product> <release> <OS> <architecture>is always “GT.M”. always begins with “V”, and has the structure V<DB_Format>.<major_release>-<minor_release>[<bug_fix_level>] where: - <DB_Format> identifies the block format of GT.M database files compatible with the release. For example, V4, V5, and V6. The <DB_Format> piece in $ZVERSION does not change even when a MUPIP UPRGRADE or MUPIP DOWNGRADE changes the DB Format element in the database fileheader.
- <major_release> identifies a release with major enhancements.
- <minor_release> identifies minor enhancements to a major release. The classification of major and minor enhancements is at the discretion of FIS.
- An optional <bug_fix_level> is an upper-case letter indicating bug fixes but no new enhancements. Note that GT.M is built monolithically and never patched. Even though a bug fix release has only bug fixes, it should be treated as a new GT.M release and installed in a separate directory.
is the host operating system name. is the hardware architecture for which the release of GT.M is compiled. Note that GT.M retains it original names for continuity even if vendor branding changes, for example, “RS6000”.
M routines cannot modify $ZVERSION.
| [Caution] | Warning |
| GT.M treats $ZVERSION as a literal at compile time. Therefore, always compile with the same version as that used at runtime. |
Example:
GTM>w $zversion
GT.M V6.0-003 Linux x86_64This example displays the current version identifier for GT.M.