Synergex.SynergyDE.synrnt 10.3.1020

This package has no dependencies.

-- We added support for Windows 10. XCALL ENVRN will return 28
(OS_WINDOWS10) when a program is running on Windows 10.
[tr#36089]

-- Android API level 17 (4.2 Jelly Bean) is now the minimum
supported level for Android devices. [tr#36091]

-- We added support for the INITPORT subroutine to Synergy .NET.
Note that this is not supported for portable class libraries or
Windows Universal Platform apps. [tr#35846]

-- We added an optional timeout parameter to the %SS_CONNECT
socket routine. This specifies the number of seconds to wait for a
connection before the routine returns with an SS_ETIMEDOUT error.
If the timeout parameter is not specified, the routine will wait
indefinitely for either a successful connection or another error
to occur. [tr#35931]

-- Long exception messages caught by TRY-CATCH are now displayed
in full, rather than being truncated (with the message
"*** Warning: Message replacement too long ***"). [tr#36045]

-- We improved the way the Synergex.SynergyDE.Synrnt NuGet
package is installed so that the CopyLocal setting is now set to
True in all cases. Previously, it was sometimes set to False,
which caused runtime errors. [tr#35855]  

-- We improved the way the winerrpost.log file is generated and
updated. Previously, if an error that was logged to the file was
encountered in a loop, the file could grow to an enormous size
unless the error terminated the process. Furthermore, the
information logged in the file wasn't sufficient to help diagnose
errors. These issues have been corrected. [tr#35882]

-- In versions 9.5.1 through 10.3.1a, a READS on a channel opened
in input mode would perform poorly if updates or deletes were
simultaneously occurring on another channel or by another
process. This has been corrected. [tr#35936]

-- We made several improvements to the CurrentRFA method for the
Select.AlphaEnumerator and Select.RestrictedAlphaEnumerator
classes. This method now returns the correct RFA from a remote
server with SCSPREFETCH, and it now returns the correct GRFA when
a From class record is smaller than the actual ISAM file record.
Additionally, if the "Stored GRFA" attribute of an ISAM file is
configured, CurrentRFA now uses this attribute, which reduces CRC
calculation overhead for each enumeration. [tr#35915]

-- We fixed an issue that caused segmentation faults when using
i8 variables in Select.Where expressions on some 64-bit platforms
and devices. This fix also corrects a condition that could have
caused segmentation faults on these platforms when passing i8
arguments with %RXSUBR. [tr#35884]

-- Previously, the compiler did not translate logicals for the
cert_file or CA_file arguments for %HTTP_GET, %HTTP_PUT,
%HTTP_POST, or %HTTP_DELETE. This has been corrected. [tr#35836]

-- In versions 10.1.1 to 10.3.1a, a Select with a Where
expression that specified multiple adjacent segments would fail
to return all records that matched the criteria if it used EQ or
EQS for the first segment and GE, GES, LE, or LES for the second
and third segments. This has been corrected. [tr#35874]

-- Select now optimizes Where expressions regardless of the way
comparisons are ordered. Previously, (Where)(0 < key) would not
be optimized, even though (Where)(key > 0) was optimized.
Additionally, the order of GE, GES, LE, and LES comparisons would
sometimes prevent optimization for segmented keys when multiple
adjacent segments were compared. These issues have been
corrected. [tr#35871, tr#35623]

-- We fixed an issue that could prevent a Select from returning
all matching records when there was a type mismatch between a
numeric field type specified in the Where condition and the
defined key type in the file. As a result of this fix, field/key
type mismatches can no longer be optimized unless the runtime can
determine from the search criteria that no negative values will
be returned. This may result in a noticeable decrease in
performance unless the type mismatch is corrected or the Where
expression is changed. For example, if key1 is a decimal field
and it matches an alpha key, the Where expression (key1 < val)
will not be optimized. However, if the Where expression is
changed to (key1 > 0 .and. Key1 < val), it will be optimized if
val is greater than 0. Correctly typing Key1 as decimal in the
file will also result in optimization. [tr#35651]

-- A READS, FIND(MATCH:Q_SEQ), or WRITES following a Select now
generates an INVOPER ("Invalid operation") error if sequential
context has not been reestablished with a READ, FIND, or WRITE
statement. (Sequential context is undefined until it is
reestablished). Previously, there were cases where this was not
occurring. THIS CORRECTION MAY BREAK YOUR CODE. A program that
previously ran without generating a runtime error will now cause
an INVOPER error if sequential context is not reestablished as
described. [tr#35907]