List of changes for portingset: 7.1d.10
MaintCorelli: # 26302 (BDUX18643): Wrongful message regarding Password expiration when logging in Baan
Date: Mon, 4 Jul 2005 12:04:23 +0200 (CEST)

Created on:  MaintCorelli
Type:        bugfix


Problem Description (Customer terms)
When logging in to Baan using BaanLogin protocol, and using NIS users which are not locally defined, 
the following error is reported: Error "password expired". And it is not possible to log in Baan.

Workaround
Do not have a max age of password set, or use Rexec protocol instead of BaanLogin protocol.


Test Procedure
Have a NIS user account, having "max password age" set to 26 weeks for example.
Do not have password expiration enabled in NIS.
Logging in Baan using BaanLogin protocol should work.
Tested at customer system. 

Affected Executables
blogind

Motive source
DF:224806


MaintCorelli: # 26283 (BDUX18831): Add function to indicate active Application Lock (prevent activating Session Timeout). Merge from bugf_BDUX18808.
Date: Fri, 1 Jul 2005 14:37:44 +0200 (CEST)

Created on:  MaintCorelli
Type:        bugfix


Problem Description (Customer terms)
With Session Timeout, the Bshell exits when a user is not active for a
long time. However, this also happens if one or more of the active sessions
have an Application Lock set.
When an Application Lock is active, the Bshell should not exit due to a
session timeout.

Test Procedure
Set session timeout to a low value, otherwise you have to wait
for a long time ;-)
Then start a session that sets an Application Lock. Do nothing and notice
that the Bshell is not exited after the session timeout.

Affected Executables
bshell6.2

Motive source
DF:225021


MaintCorelli: # 26275 (BDUX18827): Informix SDK for DEC downgraded to 2.60.FC1
Date: Fri, 1 Jul 2005 11:25:27 +0200 (CEST)

Created on:  MaintCorelli
Type:        bugfix


Problem Description (Customer terms)
Compilation of inf_srv6.2 failed with new Informix 2.90 SDK on DEC OSF4 
platforms.

Workaround
n/a


MaintCorelli: # 26253 (BDUX18267): Extend support level 2 mode on level 1 db_version
Date: Thu, 30 Jun 2005 11:11:58 +0200 (CEST)

Created on:  MaintCorelli
Type:        bugfix


Problem Description (Customer terms)
Can not use optimal level 2 queries on level 1 database 
at AS400. Some queries were resolved badly.


Workaround
Not possible

Test Procedure
Run purchage user of Baan benchmark kit 3.6e on AS400

Just use a query like with tracing DBSLOG=0400, DB4_LEVEL1=0
on Level 1 database
select count(*):c from ticpr301 where kocl gt; tckocl.charge
and compare with
select count(*):c from ticpr301 where kocl = tckocl.charge


Affected Executables
*_srv6.2



MaintCorelli: # 26237 (BDNT18781): Informix SDK used from clearcase now
Date: Wed, 29 Jun 2005 16:40:01 +0200 (CEST)

Created on:  MaintCorelli
Type:        bugfix


Problem Description (Customer terms)
Informix CSDK for Windows used from ClearCase now.

Workaround
n/a

Affected Executables
informix binaries


MaintCorelli: # 26227 (BDUX18787): JVMI: use SUN JRE as default on Windows
Date: Wed, 29 Jun 2005 14:57:28 +0200 (CEST)

Created on:  MaintCorelli
Type:        bugfix


Problem Description (Customer terms)
resource use_msjava_dll has default value 1, this means the MSJVM is used by default on Windows.
As the MSJVM will be phased out, the default should change to 0, which means that the SUN JRE is used for JavaVirtualMachineIntegration.

Workaround
set resource use_msjava_dll:0 when the SUN JRE should be used

Test Procedure
Open World on Windows with both MSJVM and SUN JRE.

Affected Executables
bshell


MaintCorelli: # 26214 (BDUX18788): core dump in pdaemon
Date: Wed, 29 Jun 2005 14:52:29 +0200 (CEST)

Created on:  MaintDvorak
Type:        bugfix


Problem Description (Customer terms)
pdaemon core dumps when starting up

Test Procedure
pdaemon starting thru $BSE/etc/rc.start should not generate a core dump 
of pdaemon

Affected Executables
pdaemon6.2

Motive source
TCS 800/147484


MaintCorelli: # 26203 (BDNT18775): Removed installshield 3 based bw from delivery
Date: Wed, 29 Jun 2005 11:53:18 +0200 (CEST)

Created on:  MaintCorelli
Type:        porting specific change


Problem Description (Customer terms)
Removed InstallShield 3 based BW setup from delivery. The MSI based setup should be used instead.

Workaround
N/A

Test Procedure
Check delivery on e.g. \\netapp\tools\Portingsets

Affected Executables
image builder


MaintCorelli: # 26188 (BDNT18749): Use new product ID for BW MSI installer
Date: Tue, 28 Jun 2005 15:50:55 +0200 (CEST)

Created on:  MaintCorelli
Type:        bugfix


Problem Description (Customer terms)
Adapt Corelli MSI BW installer such that it can be installed next to an MSI based BaanIV and Gemini version of BW.

Test Procedure
See problem desciption.

Affected Executables
setup.exe


MaintCorelli: # 26164 (BDUX18727): Upgrade to Informix CSDK 2.9 libraries
Date: Tue, 28 Jun 2005 09:30:16 +0200 (CEST)

Created on:  MaintCorelli
Type:        bugfix


Problem Description (Customer terms)
The old Inofrmix client SDK was not suppoerted anymore. Update to 2.90 was done.

Workaround
n/a

Affected Executables
inf_srv6.X


MaintCorelli: # 26126 (BDUX18678): QP: query hint kills index iteration
Date: Fri, 24 Jun 2005 15:07:59 +0200 (CEST)

Created on:  MaintCorelli
Type:        bugfix


Problem Description (Customer terms)
If a "no hints" or "first rows" hint is added to a query that would normally be
solved by the iterative technique, the driver no longer uses this iterative
technique but one of the other techniques (nested or filter).

All hints, except an index hint that hints an index that does not match the 
order by, should have no impact on the decision to iterate or not.

Test Procedure
Ensure that the iterative technique is set for the table under test. Verify this 
by executing example query 1 with DBSLOG=400 set. The dbs.log file should 
contain two queries on dbtst120. The first query should have a '=' operator on 
the first column of _index2 and a '>gt;' operator on the second column. The second
query should have a '>gt;' operator on the first column of _index2.

Run each of the tests above and observe (using DBSLOG=400) that the driver 
chooses to iterate in the proper cases.

Affected Executables
All database drivers

Motive source
DF:157253


MaintCorelli: # 26078 (BDUX18609): assertion fails in debug bshell
Date: Wed, 22 Jun 2005 11:51:48 +0200 (CEST)

Created on:  MaintBaanIVc
Type:        bugfix


Problem Description (Customer terms)
No customer problem (internal debug porting sets only)

Affected Executables
bshell
gcommand

Motive source
DF:155938


MaintCorelli: # 26066 (BDUX18655): S156792: ms sql level 1 - level 2 mixed does not work
Date: Tue, 21 Jun 2005 12:32:00 +0200 (CEST)

Created on:  MaintCorelli
Type:        bugfix


Problem Description (Customer terms)
If a set-up is created such that tables from one company are handled by a 
level-1 database driver and tables from another company are handled by a level-2 
database driver, error 9144 is issued on a MSQL driver. The dbs.log file shows 
that the incorrect index optimisation value is used.

Test Procedure
Modify the $BSE/lib/tabledef file, so that company 001 is handled by a level-1 
driver and company 002 is handled by a level-2 driver:

	*:001:informix.dbg(INFORMIXDIR=/usr3/informix,INFORMIXSERVER=baan1,INF_LEVEL1=1)
	*:002:informix.dbg(INFORMIXDIR=/usr3/informix,INFORMIXSERVER=baan1,INF_LEVEL1=0)

Modify the $BSE/lib/gt;/gt;_storage file, so that company 001 uses hash 
columns and company 002 doesn't:

	*:001:T:group:0011:10:INITIAL 16 NEXT 16 LOCK row
	*:001:I:group:0011:10:
	*:002:T:group:0400:10:INITIAL 16 NEXT 16 LOCK row
	*:002:I:group:0400:10:

Now create a table in both companies 001 and 002. Populate the table with some 
data. Using qptool, verify that the duplication from company 002 to 001 is done
properly:

	qptool -c 002 -q "select * from gt; where _compnr = 001 and _index1 = ..."

If you run above command with DBSLOG=01570, then observe that a line like the 
following is in the dbs.log file (note the correct idxopt value):

	Key values index 1, idxopt 11:

Also check that duplication from 001 to 002 is okay:

	qptool -c 001 -q "select * from gt; where _compnr = 002 and _index1 = ..."

Affected Executables
All database driver

Motive source
DF:156792


MaintCorelli: # 25955 (BDUX18470): Bshell starts looping after 49+ days
Date: Mon, 13 Jun 2005 10:49:31 +0200 (CEST)

Created on:  MaintCorelli
Type:        bugfix


Problem Description (Customer terms)
Bshell stops responding after (exactly)  49 days and 17 hours. Select statement reports
an invalid argument.

Workaround
Restart the bshell

Test Procedure
Start a tmboaserver or a netchange server and wait for 50 days
This issue is very hard to test. The starttime of the bshell is set and time has to
do the rest. One could try to do something with the system time, set is 49 days in the 
future.

Affected Executables
bshell6.x

Motive source
DF:154873


MaintCorelli: # 25918 (BDNT18502): In case of Webtop user defined startup sessions should be ignored
Date: Thu, 9 Jun 2005 08:43:40 +0200 (CEST)

Created on:  MaintBaanIVc
Type:        bugfix


Problem Description (Customer terms)
When a user had defined startup sessions (ttaad2106m000), he cannot log in to Baan using Webtop.
An error message pops up:
3GL programming error for DsNlinkObject: Object 0 not found in process ottstpstdlib (pid = 4)

Workaround
No workaround available.


Test Procedure
With sessions "Maintain Session Groups (ttaad2117m000)",  "Maintain Startup Sessions (ttaad2106m000)" and "Maintain User Settings (ttaad2105m000)"
link one or more startup sessions to a baan user.
Test if these startup sessions are starting when logging in with BW.
Secondly test if these startup sessions are ignored (not started) when logging in with Webtop. Also no errors should be reported as described in 
the problem text.

Affected Executables
bshell

Motive source
DF:156682


MaintCorelli: # 25897 (BDUX18501): Removed excape characters in informix database scripts
Date: Wed, 8 Jun 2005 09:38:34 +0200 (CEST)

Created on:  MaintCorelli
Type:        bugfix


Problem Description (Customer terms)
The informix database installation script shows escape characters on Linux.

Workaround
n/a

Test Procedure
run inf_install6.2

Affected Executables
inf_install6.2


MaintCorelli: # 25895 (BDUX18499): set.time.zone(): return 0 for empty string, to work around application bug
Date: Wed, 8 Jun 2005 09:26:45 +0200 (CEST)

Created on:  MaintMahler
Type:        bugfix


Problem Description (Customer terms)
set.time.zone("") (or any string containing only spaces) recently changed
meaning:
 - it used to return 0 and switch to GMT,
 - then it returned -1 and did nothing.
The former is incorrect, and the latter is more correct.  However, it turns out
that there are applications that erroneously call set.time.zone(""), and expect
return code 0.  This should (and will) be fixed in the applications, but
because of depency difficulties it is easier to solve this in the bshell.  So
the new meaning should be
 - return 0 and do nothing.

Workaround
Don't pass "" to set.time.zone().

Test Procedure
Trivial 3GL script.

Affected Executables
bshell


MaintCorelli: # 25844 (BDUX18456): bic_bshell: Improve argument name in change.password() signature
Date: Fri, 3 Jun 2005 13:01:37 +0200 (CEST)

Created on:  MaintMahler
Type:        bugfix


Problem Description (Customer terms)
The signature of change.password() conflicts with a macro 'new'.

Workaround
Don't pass a macro called 'new' (or 'old', or 'path', or 'x', or a zillion
others) as a bic command line option.

This really is an instance of "Doctor, it hurts when I do that." Says the
doctor: "Then don't do that."

Test Procedure
None.

Affected Executables
none


MaintCorelli: # 25838 (BDNT17877): Msql7_maint: pick up msql_serverhost from db_resource file.
Date: Fri, 3 Jun 2005 12:35:31 +0200 (CEST)

Created on:  MaintCorelli
Type:        bugfix


Problem Description (Customer terms)
Baan is installed on a Windows 2003 Cluster server, in combination with clustered SQL Server.
After creating a new database user in session ttdba0115m000 (Maintain Database Users), or changing the current password, you select this 
user and press "Convert Users". 
The conversion fails, and the following error is reported:
(ttdba01155) Error 1 occured while executing program.
After pressing OK, the following error is reported:
(ttdbadll02)
Error from Database Maintain program: test -1 1|Connect error 0 from
'Microsoft SQL-DMO (ODBC SQLState: 08001)' as 'sa' to server
'(local)'. gt;[Microsoft]gt;[ODBC SQL Server
Driver]gt;[Shared Memory]SQL Server does not exist or access
denied.


And the following error is logged in the Windows Event Log:

Env	 BaanIV (r:\baan4c)
Prog	 Msql7Adm.dll file R:\db\servers\MSQL\msqladm.cpp # 2287
Process	 0x3c8 Thread	 0x430
Lasterror	 0
Errno	 0
Message	Microsoft SQL-DMO (ODBC SQLState: 08001) returned error 0: [Microsoft][ODBC SQL Server Driver][Shared Memory]SQL Server does not exist or access denied.
[Microsoft][ODBC SQL Server Driver][Shared Memory]ConnectionOpen (Connect()).


Workaround
Create the datbase user or change the password manually using the SQL Server Enterprise Manager.

Test Procedure
Have Baan installed on a Windows2003 / SQL Server 2000 Windows cluster server.
Log in, and open session "Maintain Database Users" (ttdba0115m000).
It should be no problem to create a new database (inclusive conversion), or change the password of an existing user.
No errors should be reported.

Affected Executables
msql7_maint.exe

Motive source
DF: 224831


MaintCorelli: # 25830 (BDNT18442): New SSA Certificate from Verisign for BI
Date: Thu, 2 Jun 2005 13:10:03 +0200 (CEST)

Created on:  MaintCorelli
Type:        bugfix


Problem Description (Customer terms)
Verisign SSA Certificate was expired.
New Certificate Received via Jesse Allen.

Affected Executables
bisetup.class


MaintCorelli: # 25760 (BDNT18374): Installer issues on clustered W2003 SQL Server 2000
Date: Thu, 26 May 2005 08:48:47 +0200 (CEST)

Created on:  MaintCorelli
Type:        bugfix


Problem Description (Customer terms)
When installing Baan against a clustered SQL Server 2000 on Windows 2003, the installer does not work correctly.
Installer does not "recognize" the SQL Server instance on this configuration and some other problems.

Workaround
Install Baan against non-clustered Wndows/SQL Server, and make Windows/SQL Cluster after installing Baan
cluster aware. (And Baan also).

Test Procedure
Install BaanIVc on the following configuration:
Windows 2003 cluster
SQL Server 2000, installed in cluster mode. (So SQL Server 2000 is already cluster-aware, and supporting fail-over, before you start installing Baan. Note that in the past you needed to make SQL Server cluster-
aware after you installed Baan!).

Affected Executables
msqladm.dll
setup.ins (installer)

Motive source
DF:221771


MaintCorelli: # 25739 (BDUX18327): Increase of pty usage after BDUX17260
Date: Wed, 25 May 2005 10:33:17 +0200 (CEST)

Created on:  MaintBaanIVc
Type:        bugfix


Problem Description (Customer terms)
After installing portingset 6.1c.07.07 the following error was reported:
Errno 24 (The process file table is full) bdb_errno 0
Failed to open pty pair.
After increasing the number of pty's from 256 to 512 the problem was solved.
It looks like the pty usage increased after installing this portingset.

Workaround
Increase the number of available pty's on system level.
E.g. double the number of available pty's.

Test Procedure
Before logging into Baan, set the following in to the Command field of Bw Configuration:
-- -dbgpty -logfile ptytrace -keeplog
Log in Baan, and from the menubar select File->gt;Run Program.
Fill in: ksh, and check "Run External Program".
Press OK.
Now a terminal emulator is opened.
Type exit and leave the terminal emulator again, and log out Baan.
Afterwards check the ptytrace file, it should contain:

pty: opened master /dev/ptc fd 9
pty: opened slave /dev/pts/2 fd 10 PTY STRUCTURE       
PTY: proc	= ottstpvtemul_r
PTY: in		= 12
PTY: out	= 9
PTY: mfd	= 9
PTY: pfd	= 12
PTY: rpid	= 0
PTY: spid	= 32416
PTY: flags                
PTY: no input for process ottstpvtemul_r
pty: opend slave /dev/pts/2 fd 13

So 1 master pty should be opened.
In a wrong situation you will see 10 times "pty: opened master /dev/ptc fd ..".


Affected Executables
bshell

Motive source
DF:156103


MaintCorelli: # 25665 (BDUX18302): Tax API Diagnostics
Date: Fri, 20 May 2005 08:07:50 +0200 (CEST)

Created on:  MaintCorelli
Type:        bugfix


Problem Description (Customer terms)
Customers had no independent means of knowing if their environment was setup properly for use with Taxware or Vertex. They had to set everything up and then try to use it through Baan.

Workaround
Customer had to start Baan with various debugging environment variabls set in ord er to get any kind of diagnostic information to help them fix any kind of setup issues.

Test Procedure
After building a new api6.x (Unix only) or installing the new portingset (Windows) the api executable can be run from a command prompt with -dt (Taxware) or -dv (Vertex). This will dump a number of lines of information to the screen and if anything is wrong with the environment variables or the tax installation there should be a message included to help pinpoint what the issue is.

Affected Executables
api6.x/api.exe

Motive source
DF:224071


MaintCorelli: # 25536 (BDUX18161): Removed some double line (defines) in shm.h
Date: Wed, 4 May 2005 16:21:53 +0200 (CEST)

Created on:  MaintMahler
Type:        bugfix


Problem Description (Customer terms)
Because of a merge from another project some source lines are duplicated.

Workaround
N/A

Test Procedure
N/A

Affected Executables
shmvalues6.x
shmmanager6.x


MaintCorelli: # 25515 (BDUX18137): Enhance error messages
Date: Tue, 3 May 2005 16:14:55 +0200 (CEST)

Created on:  DevDvorak
Type:        bugfix


Problem Description (Customer terms)
String demotion when concating strings into a tmp string:

	string	desc80(80)	mb
	string	shortcut(10)	
	long	length

	length = len(desc80 & shortcut)

results in the length of bytes of the result string while 
number of characters is expected.
the temporary string created by the concat disregards the fact 
that one of the strings is a multibyte string

Workaround
in the example add:
	string 	temp.mb(90)	mb

change:
	temp.mb = desc80 & shortcut
	length = len(temp.mb)

Affected Executables
bshell6.2


MaintCorelli: # 25505 (BDUX18049): Long passwords on HP UX trusted security.
Date: Tue, 3 May 2005 11:36:17 +0200 (CEST)

Created on:  MaintBaanIVc
Type:        bugfix


Problem Description (Customer terms)
Using HP-UX OS in "Trusted Security" mode, and using BaanLogin protocol to log in Baan:
When using passwords bigger than 8 characters, you cannot log in Baan.
An Authorization Failure error is reported.

Workaround
Do not use passwords longer then 8 characters.

Test Procedure
You need to have a HP-UX system, running in "Trusted Security" mode.
When having such system, running Baan, set the user-password to a password longer then 8 characters.
(not longer then 25 characters).

You should be able to log in Baan using the Baan Login protocol when using password longer then 8 characters.

Affected Executables
blogind6.x

Motive source
DF:155293


MaintCorelli: # 25499 (BDUX18136): Unexpected locks on AIX platforms.
Date: Mon, 2 May 2005 16:43:28 +0200 (CEST)

Created on:  MaintMahler
Type:        bugfix


Problem Description (Customer terms)
Unexpected database locks are occured on AIX platforms. This problem was found
during a Gemini installation.

Workaround
n/a

Test Procedure
Test was done with a complete Gemini installation on AIX.
No easy test is available.

Affected Executables
inf_srv6.x


MaintCorelli: # 25428 (BDNT18008): Winstation test based on 7.1d.05
Date: Tue, 26 Apr 2005 11:54:27 +0200 (CEST)

Created on:  MaintCorelli
Type:        porting specific change


Problem Description (Customer terms)
Running a lot of users on NT might result in not able to start 
sort.exe or sh_server.exe processes due to some Windows
limitation. Special registry tuning is needed to over come this.
See solution 121503 for more information.
This solution might still not acceptable for all customers because
the registry settings might conflict with requirements of other
applicatons.

Workaround
See solution 121503

Test Procedure
Take a windows system, set the third argument of SharedSection
(See the solution) to a low value (e.g. 256 of less). Disable 
combo-mode in tabledef and try to a number of bshells (e.g. the
baan benchmark) One will notice that 30 users will run fine,
but running 40 users will result in errors on the console due
to not able to start sort.exe.
Set the resource 'no_ipc_msg_window:1' in $BSE/lib/defaults/all
and notice that one can at least run upto 400 users on the same
system.

Affected Executables
ntbshell.exe, *_srv.exe, bshcmd.exe


MaintCorelli: # 25404 (BDNT17986): Api messages invalid, error code 1
Date: Mon, 25 Apr 2005 10:58:56 +0200 (CEST)

Created on:  MaintCorelli
Type:        bugfix


Problem Description (Customer terms)
API message was invalid. Error code 0.
API request failed. Message was not sent. Error code 1.

Workaround
N/A

Affected Executables
api.exe


MaintCorelli: # 25388 (BDNT17475): Log errormessage when bshell cannot register at licence server.
Date: Fri, 22 Apr 2005 10:39:08 +0200 (CEST)

Created on:  MaintBaanIVc
Type:        bugfix


Problem Description (Customer terms)
When logging into Baan nothing happens, and the following error appears: 
1 : Error: Time out.
We do not understand what the problem is. What is timing out?

Workaround
No

Test Procedure
Could only be tested at customer system, where another application was listening on port 6003.
(port 6003 is the port being used by the Baan Licence server)

Affected Executables
bshell

Motive source
DF:155647


MaintCorelli: # 25369 (BDNT17416): Determination of mac address via Netbios not reliable.
Date: Wed, 20 Apr 2005 13:45:40 +0200 (CEST)

Created on:  MaintBaanIVc
Type:        bugfix


Problem Description (Customer terms)
BaanIVc installed and validated successfully. But after restart of the Windows2000 server, the Baan Licensing service does not start anymore.
The following error is logged in the Windows Event Log: Can't run - Please brand your software.
Also after applying use_enhanced_hostid:1 (refer to solution 131733) and re-validating Baan, the same problem comes back after a restart of the system.

Workaround
No

Test Procedure
It is not possible to define a test procedure for this problem.
The problem seems to be related to the number of times networkadapters/protocols/services were installed/uninstalled
at a Windows platform.

Affected Executables
licd.exe, licmon.exe, brand.exe, hostid.exe

Motive source
DF:155502


MaintCorelli: # 25367 (BDNT18011): Add new axbarcode.lic file
Date: Wed, 20 Apr 2005 12:22:22 +0200 (CEST)

Created on:  MaintCorelli
Type:        bugfix


Problem Description (Customer terms)
BwPrint: The barcode functionality is not enabled.
(Menu options regarding Barcode's are grayed out)

Workaround
Create the following registry setting:
HKLM\SOFTWARE\dLSoft\abc
key (type REG_SZ) "Current"
value data: "version 30"

Test Procedure
Have the new bwprint, axbarcode.ocx and axbarcode.lic installed.
Start BwPrint.
From the Help select Barcode Test.
The Barcode Test should show the barcode images.

Affected Executables
Bwprint

Motive source
DF:224085


MaintCorelli: # 25363 (BDUX17335): QP: Each sql_exec of query with _compnr = :1 scans through tabledef
Date: Wed, 20 Apr 2005 12:02:59 +0200 (CEST)

Created on:  MaintCorelli
Type:        bugfix


Problem Description (Customer terms)
A query that has a _compnr = :1 clause, gives bad performance if the tabledef
file has a lot of entries and the query is executed multiple times.

Affected Executables
bshell
qptool

Motive source
DF:153936


MaintCorelli: # 25317 (BDUX17937): expression range problem with float domains
Date: Thu, 14 Apr 2005 13:21:33 +0200 (CEST)

Created on:  DevDvorak
Type:        bugfix


Problem Description (Customer terms)
Field "Planning Factor" wrong calculation with decimals, Error 205 


Test Procedure
function main()
{
	double aa
	double bb
	double cc

	long e.id

	long aa.e
	long bb.e
	long cc.e

	e.id = expr.compile("$$ in [0.01,0.99]")

	aa = 0.01
	bb = 0.0099999997764825821
	cc = 0.99

|
|	 internally ranges are compared with a tolerance of 0.0000009
|

	aa.e = l.expr(e.id, aa)	 | returns 1
	bb.e = l.expr(e.id, bb)	 | used to return 0 returns 1 now
	cc.e = l.expr(e.id, cc)	 | returns 1

	aa = 0.009
	aa.e = l.expr(e.id, aa)	 | returns 0

	aa = 0.0099
	aa.e = l.expr(e.id, aa)	 | returns 0

	aa = 0.00999
	aa.e = l.expr(e.id, aa)	 | returns 0

	aa = 0.009999
	aa.e = l.expr(e.id, aa)	 | returns 0


	expr.free(e.id)

}

Affected Executables
bshell6.2, db drivers

Motive source
DF153060


MaintCorelli: # 25287 (BDUX17921): add override_java_sigusr2 resource
Date: Tue, 12 Apr 2005 16:22:23 +0200 (CEST)

Created on:  MaintCorelli
Type:        bugfix


Problem Description (Customer terms)
On Linux now and then the bshell hangs or a connection is broken after tmboaserver is started.

Test Procedure
start tmboaserver 
it succeeded already most of the times without this fix


Total number of changIDs displayed: 35