Disable type mismatch processing
|
WSupported on Windows
|
USupported on Unix
|
VSupported on OpenVMS
|
NSupported in Synergy .NET
|
The SYNSEL_NUMALPHA_KEYS environment variable disables type mismatch processing in Synergy/DE 10.3.3d and higher.
Value
Any value.
Discussion
To avoid the possibility of not matching records that contain leading blanks instead of zeros, optimization was turned off in 10.3.3d for a Select with a Where expression that matches an alpha typed or untyped key. As a result, large Selects may run more slowly. In addition, Join (On) expressions that don’t match the ISAM file key type throw an $ERR_INVOPER exception. To avoid these issues, we recommend that you do the following:
- Update your ISAM file to include the correct type. However, as a temporary workaround, if you can’t immediately make the changes that will permanently correct the situation, you can set SYNSEL_NUMALPHA_KEYS=1 to ignore the key type mismatch check and thus keep your application from slowing down or failing with an %ERR_INVOPER exception.
- Ensure your repository sets the “Negative allowed?” value for fields used in this scenario to No, or use a positive range. Use fcompare -dv to verify that the field doesn’t contain any negative values or spaces.
Warnings about key mismatches are still logged if DBG_SELECT=2 is set.
When the file is on OpenVMS, SYNSEL_NUMALPHA_KEYS is set to on by default, since OpenVMS doesn’t support decimal keys.
Setting location
The environment.
Used by
Runtime
Examples
On Windows,
set SYNSEL_NUMALPHA_KEYS=1
