List of changes for portingset: 6.1c.07.18 MaintBaanIVc: # 38362 (BDUX30290): bic6.1 crashes with -u and -f option and +1 literal on long datatype Date: Fri, 8 Feb 2008 14:06:20 +0100 (CET) Created on: MaintBaanIVc Type: bugfix Problem Description (Customer terms) The bic compiler crashes when there is an function call with plus sign (+1) as only argument. Example: TestFunctuin( +5 ) Workaround N/A Test Procedure Compiled the RDD test DLLs and done a regression test with them. Affected Executables bic6.1 Motive source SDIS:TECH-00000-03446 MaintBaanIVc: # 38300 (BDUX30230): pwdaging does not show a message when it should on AIX Date: Wed, 6 Feb 2008 11:26:16 +0100 (CET) Created on: MaintChopin Type: bugfix Problem Description (Customer terms) pwdaging does not show a message when it should give a warning about password expiration on AIX. Workaround n/a Test Procedure badmin6.2 -p -chkpwd Affected Executables badmin6.x MaintBaanIVc: # 38154 (BDUX30179): Add support for binding NULL values Date: Tue, 22 Jan 2008 14:34:11 +0100 (CET) Created on: MaintBaanIVc Type: bugfix Problem Description (Customer terms) Using the JDBC API with a null parameter value does not work: a protocol exception or SQLException comes up during the execute() of the query. Workaround Do not bind NULL values; binding a null value often indicates a programming error, and is rarely intentional. Test Procedure See the new added tests: these caused exceptions from JDBC execute calls, but not anymore. Affected Executables jbdb.jar jbdb MaintBaanIVc: # 38051 (BDUX30074): TECH-00000-03306: ipc_boot6.2 must ignore USER environment variable Date: Wed, 9 Jan 2008 12:49:26 +0100 (CET) Created on: MaintBaanIVc Type: bugfix Problem Description (Customer terms) When connecting to an AIX backend using rexec, ipc_boot6.2 is started with the USER environment variable set to the OS username. ipc_boot6.2 therefore uses this name as the 'Baan user name'. But if it is longer than 8 characters, then it is not a valid Baan user name, and ipc_boot6.2 stops with an error message, preventing the user to login. This problem will also occur on other systems where the rexec daemon passes the USER environment variable to the processes it starts. Workaround n/a Test Procedure See problem description. Affected Executables ipc_boot Motive source SDIS:TECH-00000-03306 MaintBaanIVc: # 38020 (BDUX30051): Bug in DB2 installer. Need to attach to instance before getting DB2 configuration settings Date: Mon, 7 Jan 2008 13:39:43 +0100 (CET) Created on: MaintBaanIVc Type: bugfix Problem Description (Customer terms) DB2 installation fails. MaintBaanIVc: # 38001 (BDUX30014): Jbdb: If BSE in connection parameters, ignore USER/BSE_USER environment variables Date: Thu, 3 Jan 2008 16:13:10 +0100 (CET) Created on: MaintBaanIVc Type: bugfix Problem Description (Customer terms) Using JDBC with BSE etc. in de connection parameter fails, if the USER (or Windows: BSE_USER) environment variable is set to a Baan user that does not exist on the remote system. The BSE_OSUSER parameter should be used, instead of USER or BSE_USER. Workaround Unset the USER and BSE_USER environment variables. Test Procedure See problem description. Affected Executables jbdb jbdb.jar MaintBaanIVc: # 37922 (BDNT29924): Oracle driver crashs if ora_hint_no_hints is used Date: Thu, 20 Dec 2007 14:20:00 +0100 (CET) Created on: MaintChopin Type: bugfix Problem Description (Customer terms) Use of resource variable ora_hint_no_hints resource crashs oracle database driver. Workaround Don't use ora_hint_no_hints resource. Test Procedure 1 - Set ora_hint_no_hints:1 in %BSE%\lib\defaults\db_resource 2 - Run BW with command : ttaad2500m000 Affected Executables ora8_srv MaintBaanIVc: # 37879 (BDUX29792): TCS 800-141718: kill.pgrp() does not kill all process in its process group Date: Tue, 18 Dec 2007 11:48:48 +0100 (CET) Created on: MaintBaanIVc Type: bugfix Problem Description (Customer terms) kill.pgrp() does not kill all processes in the given group, in some scenarios. Workaround n/a Test Procedure The following Porting Set test case works fine without the call to get.company(), but suddenly fails with it. This is based on a test case from Hans van Leeuwen's regression test suite. CONFIG BICEXTRAFLAGS="-d ottstp_stddll" /CONFIG BAAN3GL #define __OBJECT__ (getenv$("SQLREG_TMP") & "/object") function void main() { if background then main_child() else main_parent() endif } extern string channel(1) based function void main_child() { get.company() |<=<=<=<= triggers the problem <=<=<=<= at.base(parent,"parentchannel",1,channel,-1) channel = "11111" suspend(1000) channel = "33333" } extern string parentchannel(5) function void main_parent() { long pid2, pid3, gid parentchannel = "" pid2 = activate(__OBJECT__) suspend(200) ASSERT(pid2 <> 0) ASSERTSEQ(parentchannel, "11111") gid = set.pgrp(pid2, pid2) ASSERTSEQ(gid, pid2) parentchannel = "" pid3 = activate(__OBJECT__) suspend(200) ASSERT(pid3 <> 0) ASSERTSEQ(parentchannel, "11111") gid = set.pgrp(pid3,pid2) ASSERTSEQ(gid, pid2) kill.pgrp(pid2) suspend(2000) ASSERT(parentchannel <> "33333") } /BAAN3GL Affected Executables bshell Motive source TCS:800-141718 MaintBaanIVc: # 37404 (BDUX29358): bic Date: Fri, 16 Nov 2007 10:03:15 +0100 (CET) Created on: MaintBaanIVc Type: bugfix Problem Description (Customer terms) If a function that returns no value is used in a context that expects a value to be returned, then the bic compiler gives an error such as the following: assignment.test( 15): Error: Function 'f' returns no value. If the same functions is later properly used, then bic crashes. As an example, consider the following (incorrect) program. The first use of function f is incorrect and results in a compile error. The second use of the function f is correct and no error should be reported. However, bic crashes. function void f( long x, string s, long z ) { } function main() { long ret ret = f(3,"x",5) f(3,"x",8) } Test Procedure Compile the following source: function void f( long x, string s, long z ) { } function main() { long ret ret = f(3,"x",5) f(3,"x",8) } You should get the following error, bic should not crash and exit with exit code 1. ( 9): Error: Function 'f' returns no value. Affected Executables bic