$INCREMENT(gvn,expr) manages concurrency to avoid a rare spurious NUMOFLOW; previously, this the function could inappropriately issue that error, but never committed an incorrect result. (GTM-DE476835)

Proactive block split appropriately handles blocks with no records in them. Previously, under certain circumstances, proactive block split could try to induce a block split when the block had no records in it. This was only seen during development testing and not reported by a customer. (GTM-DE530712)

Trigger load operations involving many regions gracefully restart when a concurrent ONLINE ROLLBACK forces the process to restart transaction processing in each region. Previously, in such a situation, GT.M processes could terminate with an ASSERTPRO error. This error was only seen in development and not reported by a customer. (GTM-DE531077)

GT.M processes working on the second phase of a KILL operation (KILL-In-Progress), issue a DBROLLEDBACK error in the event an ONLINEROLLBACK changes the state of the database. Previously, GT.M processes would restart until the fourth retry acquiring the critical section on all participating regions before issuing such an error. This error was only seen in development and not reported by a customer. (GTM-DE531078)

GT.M disables proactive block splitting by default as well as within a TP transaction. FIS made this change after observing that, under certain conditions, the setting could incur spurious restarts and split blocks which were not subject to contention. To enable the feature outside of transaction processing, use a MUPIP SET -PROBLKSPLIT=n, where n is the number of nodes at which GT.M considers based on the number of restarts whether to split a block in advance of its becoming full. Previously, starting in V7.0-001, the default threshold for a proactive block split was 5 nodes and the feature applied to TP as well as non-TP. The performance issue was only ever observed in testing and not reported by a customer; it was not associated with any correctness or integrity concerns. (GTM-DE532295)

GT.M appropriately evaluates subscripts containing or depending on side effects in lock resource and global variable names. Previously, due to shifting of evaluations to avoid unnecessary global access while appropriately maintaining $REFERENCE, rare constructs with such subscripts could produce out-of-order side effects. In addition, the EXTENDED_BOOLEAN setting prevents such shifting entirely; previously, EXTENDED_BOOLEAN behavior was identical to that of the more efficient FULL_BOOLEAN. (GTM-DE506257)

GT.M produces an appropriate result from an equality test between zero (0) and a multiplicand of zero value that is the result of multiplying a non-integer value with zero (0). Previously, this odd combination could inappropriately indicate inequality. (GTM-DE507982)

GT.M appropriately reports a NUMOFLOW error for literal values when those literals are operated on at compile-time and the run-time variable equivalent would trigger the same error. This affects the unaryoperators ',+, and -. The effect of these operators on variables is unchanged. Previously, these operators sometimes did not correctly report a NUMOFLOW when called for. In the case of the negation operator, this could lead to reporting an incorrect result. (GTM-DE508852)

GT.M prevents compile-time errors in operations on literals within an XECUTE block from terminating the XECUTE without properly cleaning up the surrounding compilation environment. Previously, this could cause termination of compilation of the routine containing the XECUTE and failure to compile subsequent routines passed to the same GT.M process (GTM-DE510902)

SET @($ZWRTAC=expr) works for strings approaching 1MiB; previously such an indirect expression was limited to the maximum length of a source line. Also, the %ZSHOWVTOLCL utility routine now deals with more cases, such as such longer strings. (GTM-DE512004)

GT.M returns the correct value for a Boolean expression containing a subscripted local variable when that variable is affected by side-effects later in the expression and gtm_boolean>=1. Previously, GT.M evaluated the boolean using the value of the subscripted local after all side-effects. This issue did not affect unsubscripted local variables or globals of any kind. (GTM-DE513737)

GT.M correctly executes the $ETRAP/$ZTRAP exception handler at the time of expiry of $ZMAXTPTIME when the process holds a database critical section. Previously, due to a regression in V7.0-001, the $ZMAXTPTIME timer did not execute $ETRAP/$ZTRAP exception handler until the process released all database critical sections which could allow a transaction to materially exceed the specified $ZMAXTPTIME. (GTM-DE513980)

GT.M defers $ZTIMEOUT when its expiry happens during a TP transaction. $ZMAXTPTIME may interrupt a transaction, as optionally may MUPIP INTRPT initiated $ZINTERRUPT processing, but $ZTIMEOUT acts after a TROLLBACK or master TCOMMIT. Previously, GT.M allowed a $ZTIMEOUT expiry within a TP transaction. (GTM-DE519525)

Because it is a byte-oriented function, $ZTRANSLATE() does not issue a BADCHAR when operating on UTF-8 strings. Due to a regression in V6.3-013, this function incorrectly issued a BADCHAR error when the input string contained non-UTF-8 characters. There are two possible workarounds for this issue: 1) A targeted approach requiring code changes to enclose each use of $ZTRANSLATE() with VIEW "NOBADCHAR" and VIEW "BADCHAR"; ensures all UTF-8 data is handled appropriately. 2) A broad approach of defining gtm_badchar as zero or FALSE to disable BADCHAR checking through-out the application which disables detection of any improperly formatted UTF-8 strings. (GTM-DE525624)

GT.M on AIX correctly handles HANG arguments specifying more than 2 million seconds, or more than 24 days. Previously, inappropriate integer overflow caused larger values to hang for less time than expected, and capped the possible hang length on AIX at roughly 4300 seconds or approximately one hour and ten minutes. [AIX] (GTM-DE527213)

Specifying a second expression for $VIEW("JNLPOOL") provides a means of iterating through active Journal Pools. If the second expression is an empty string, the function returns the replication instance file name associated with the instance first attached by the process or the string "*" if the process has not previously engaged with any instance. If the file name specified in the second expression does not match the replication instance file name for any of the active Journal Pools the string "*" is returned. Otherwise the file name of the Journal Pool attached after the Journal Pool with the file name given in the second expression is returned. Note the two argument form of $VIEW("JNLPOOL") does not change the current Replication Instance. (GTM-F135040)

MUPIP REORG -UPGRADE, which completes the second phase of a V6 to V7 database transition, can run concurrently with other processing excepting other MUPIP REORG [-UPGRADE] processes. REORG -UPGRADE can work either by region or by file allowing administrator to run concurrent upgrade operations on different regions/files.

	FIS does not recommend running MUPIP REORG -UPGRADE with concurrent activity for MM database files on AIX due to a rare concurrency conflict.

MUPIP DOWNGRADE -VERSION=V63000A allows the current GT.M to downgrade a V6 database to the pre-V63000A EOF block format. Previously the downgrade function reported an unsupported error for a V7 versions. (GTM-F225097)

A process created by a JOB command that for any reason exits before becoming fully functional and independent avoids interfering with any data it may share with the process issuing the JOB command. GT.M also issues a PIDMISMATCH warning message to the operator log. Previously under rare conditions, such an "infant" process could inappropriately release resources belonging to its "parent," causing symptoms including damage to a statsdb database or to a routine repository. (GTM-DE476408)

^%RANDSTR limits the range argument upper limit to the actual number of characters available in the current character set - 256 for M mode and 65,536 for UTF-8 mode. Previously, a missing or defective upper limit caused the routine to perform unproductive processing that could consume unreasonable amounts of time. The workaround was to avoid inappropriate range arguments. (GTM-DE500856)

The GT.M compiler accepts source files with arbitrary extensions. FIS recommends using the .m extension for source files as our testing of that is very extensive, however there may be cases where other extensions serve a purpose. Previously, the compiler enforced an explicit or implicit .m extension for source files. (GTM-DE500860)

%YGBLSTAT warns about incorrect command line usage. Previously, the utility silently ignored command lines containing errors. (GTM-DE503394)

GTMSECSHR appropriately handles a rare condition when two processes attempt to start a GTMSECSHR process at a coincident time. Previously, this could start more than one GTMSECSHR process, and, although a single GTMSECSHR process handled all the requests, their shutting down produced syslog error messages. (GTM-DE506361)

The Direct Mode only RECALL command functions as documented; starting in V7.0-002 it always gave an error. (GTM-DE511969)