List of changes for portingset: 8.3a


DevCage: # 31670 (BDNT23848): Focus lost in session whinh2100m100

Date: Thu, 27 Jul 2006 14:51:12 +0200 (CEST)

Created on:  MaintSchoenberg
Type:        bugfix

Problem Description (Customer terms)
When in session whinh2100m100 and zooming to session whinh2120m000, when the quantity (in Order unit) 
is altered, and after pressing "save and close" in whinh2120m000 the originating session
whinh2100m100) has lost the focus, is only open in the background.

Test Procedure
See problem description in SDIS.

Affected Executables
bw.exe

Motive source
SDIS:ERP-00000-07804




DevCage: # 31668 (BDUX23826): CPM: delivery of Cognos ini (cogdmod.ini) files

Date: Thu, 27 Jul 2006 14:50:47 +0200 (CEST)

Created on:  DevCage
Type:        enhancement

Problem Description (Customer terms)
In order to deploy the CPM/ODBC solution, customized cogdmod.ini files have to 
be delivered for both analytics and decision stream.

Test Procedure
Compile and deliver a complete portingset. Install it, and check whether the 
cogdmod.ini files are installed in the $BSE/lib/cpm/... directories mentioned
above.

Affected Executables
deliver.exe




DevCage: # 31651 (BDUX23816): SHM issues on Linux

Date: Wed, 26 Jul 2006 14:11:51 +0200 (CEST)

Created on:  DevCage
Type:        porting specific change

Problem Description (Customer terms)
Bshell could not connect to Shared memory for the environment.

Workaround
1. manually edit shm_config and specify an shm_start_address:50000000 (or any other address in higher range), or...
2. use shm_compat_mode resource to use shm_param file again. The shm_compat_mode:1 line i
   need then to be added to $BSE/lib/defaults/all file

Test Procedure
Start shm, and then login to the environment. Check whether bshell is able to use shared memory (no error should occur)

Affected Executables
shmmanager6.1
and all other binaries (better logging)




DevCage: # 31647 (BDNT23814): Error in bdbpre

Date: Wed, 26 Jul 2006 10:56:32 +0200 (CEST)

Created on:  MaintBaanIVc
Type:        bugfix

Problem Description (Customer terms)
File becomes to big when we dump table tfgld410. 
Flush error in log.bdbpre, last record in first file not correctly written. 

Workaround
use bdbpre6.x with -M option. Use a value less 2 GByte.

Test Procedure
dump a large table tfgld410 table with sesperator. 

We used :

bdbpre6.1-N tfgld410  -t"|" -o /tmp/dump -C 300



Affected Executables
bdbpre6.x




DevCage: # 31616 (BDNT23779): Manual merge BDUX23689

Date: Fri, 21 Jul 2006 16:04:04 +0200 (CEST)

Created on:  DevCage
Type:        bugfix

Problem Description (Customer terms)
Corelli ServicePack19 (stnd) is not installable with portingset 8.2b. We use an 
environment with user locale SHIFTJIS_SUN.

Error -205 occured.

Workaround
n/a

Test Procedure
Install Corelli service pack 19 stnd on a japanese system.

Affected Executables
database drivers




DevCage: # 31615 (BDNT23774): Logon problems on windows to Baan

Date: Fri, 21 Jul 2006 15:27:43 +0200 (CEST)

Created on:  DevCage
Type:        bugfix

Problem Description (Customer terms)
Got message: Message [MR_BAD_USER] Not authorized to run as user 'system' when trying to start BW.

Test Procedure
Try to start BW.

Affected Executables
rexecd.exe (windows), blogind6.x (unix/AS400)




DevCage: # 31610 (BDUX23768): Do not check for Secu Files at all when FP0 or FP1

Date: Fri, 21 Jul 2006 13:28:29 +0200 (CEST)

Created on:  DevCage
Type:        bugfix

Problem Description (Customer terms)
When in FP0 and/or FP1 and trying to upgrade to FP2 or FP3 
there is a possibility that either a inconsistent tab.reg or a
tt security is on the system causing the system to be unusable.

Affected Executables
bshell6.2




DevCage: # 31606 (BDUX23728): DB2 issues during installation

Date: Fri, 21 Jul 2006 12:18:57 +0200 (CEST)

Created on:  DevCage
Type:        bugfix

Problem Description (Customer terms)
Installation failure on DB2, due to crashing db2v5_adm binary

Test Procedure
Try to install on DB2 (if DB2 is supported)

Affected Executables
db2v5_adm executable

Motive source
TCS:800-153724




DevCage: # 31596 (BDNT23647): Compile reports fails

Date: Fri, 21 Jul 2006 08:26:24 +0200 (CEST)

Created on:  MaintSchoenberg
Type:        bugfix

Problem Description (Customer terms)
Error while compiling reports using Baan5 and portingset 8.2b 

Test Procedure
Installed new repgen program and compile some reports

Affected Executables
repgen

Motive source
SDIS:TECH-00000-01077




DevCage: # 31564 (BDUX23677): Secu File Problems

Date: Wed, 19 Jul 2006 14:18:01 +0200 (CEST)

Created on:  MaintSchoenberg
Type:        bugfix

Problem Description (Customer terms)
With multiple package combination with the same tt security file
but with different other security files secu id for 'da' and others 
cannot be found.

Affected Executables
all

Motive source
SDIS:TECH-00000-01106




DevCage: # 31556 (BDUX23743): Informix Array Insert - performance improvment

Date: Wed, 19 Jul 2006 09:57:36 +0200 (CEST)

Created on:  MaintSchoenberg
Type:        bugfix

Problem Description (Customer terms)
Is it possible to improve insert performance when array interface is enabled ?

We need to create a table from sequential dump and it takes a very long time.

Workaround
n/a

Test Procedure
Set following values to your db_resource file

inf_init:0200000
inf_max_array_insert:100

Do bdbpost with a large sequential dump and compare the difference in time

bdbpost6.1 -k -m -n -f < dmp


Affected Executables
inf_srv6.2




DevCage: # 31533 (BDUX23654): Reconfig: do no audit all rows if only rcd_utc 
column is added

Date: Mon, 17 Jul 2006 11:12:44 +0200 (CEST)

Created on:  DevCage
Type:        bugfix

Problem Description (Customer terms)
If auditing is enabled on a table and the rcd_utc column is added, then reconfig
exports and imports all rows of the table.

This is unnecessary and very time consuming on big tables.

Workaround
Temporarily disable auditing on the table, add the rcd_utc column, and enable 
auditing on the table.

Test Procedure
Add the rcd_utc column on a table that is being audited, and observe that the
table is not completely exported and imported, but an "alter table" command is
used.

Affected Executables
bdbreconfig




DevCage: # 31527 (BDUX23702): Informix Array Insert not all rows inserted

Date: Thu, 13 Jul 2006 14:37:25 +0200 (CEST)

Created on:  DevCage
Type:        bugfix

Problem Description (Customer terms)
A table contains 1 row.
A bdbpre-dump (for the same table) contains 5 rows. One of those 5 rows has 
the same primary key as the row in the table.

Execute a bdbpost6.1 with -A (Append, Skip duplicates) option and array 
inserts off.

The 4 rows are added and one row gives a duplicate error and is skipped.
This is correct.
 
Repeat the test with array inserts on (inf_init:0200000).
The (array) insert fails with a duplicate error, and no row is added to the 
table at all.

Workaround
Two workaround are possible :

a.) disable array interface in db_resource file
b.) set inf_max_array_insert:1 in db_resource file

Test Procedure
see problem description

Affected Executables
inf_srv6.2




DevCage: # 31455 (BDNT23633): MSQL: can not start sessions

Date: Fri, 7 Jul 2006 11:17:27 +0200 (CEST)

Created on:  DevCage
Type:        bugfix

Problem Description (Customer terms)
MSQL: using the 8.3a porting set, is was not possible to start some
sessions when the driver was started in combo mode. Standalone worked
fine.

Workaround
run msql7_srv in stand-alone mode

Test Procedure
regression tests

Affected Executables
msql7_srv.dll




DevCage: # 31450 (BDNT23629): MSQL: data truncation on array columns

Date: Thu, 6 Jul 2006 17:23:44 +0200 (CEST)

Created on:  DevCage
Type:        bugfix

Problem Description (Customer terms)
MSQL: truncation errors on array columns

Test Procedure
regression tests

Affected Executables
msql_srv




DevCage: # 31447 (BDNT23624): TCS800-153556 When requesting help error messages 
appear

Date: Thu, 6 Jul 2006 16:22:38 +0200 (CEST)

Created on:  DevCage
Type:        bugfix

Problem Description (Customer terms)
When the user tries to get context sensitive help (by the question mark button)
the following message always appears:
"Cannot find the c:\Program Files\Baan\Baan Windows\bin\bw.hlp file.
 Do you want to try to find this file yourself?"


Workaround
Use key F1 on the Keyboard.

Test Procedure
See problem description.

Affected Executables
bw.exe

Motive source
TCS:800-153556




DevCage: # 31444 (BDUX23623): Informix array insert error -1422

Date: Thu, 6 Jul 2006 15:59:34 +0200 (CEST)

Created on:  DevCage
Type:        bugfix

Problem Description (Customer terms)
In case array interface is enabled and inf_max_array_insert is set > 1 
error -1422 appears.

Workaround
a) do not use array interface
or
b) set inf_max_array_insert:1

Test Procedure
Ensure following settings are set in your db_resource file:

inf_init:0200000
inf_max_array_insert:5     (default)

Run 3gl program and verify no error -1422 appears

function main()
{
	table tttaad050
		
	db.set.to.default(tttaad050)
	db.retry.point()
		
	ttaad050.syst = "test1"
	db.insert(tttaad050,DB.RETRY, db.skip.dupl)
	
	commit.transaction()
	db.retry.point()	
	ttaad050.syst = "test2"
	db.insert(tttaad050,DB.RETRY)
	commit.transaction()
	
}

Affected Executables
inf_srv6.2




DevCage: # 31419 (BDUX23586): TCS800-153545 Unable to see static local variables 
in debugger

Date: Tue, 4 Jul 2006 17:22:40 +0200 (CEST)

Created on:  MaintSchoenberg
Type:        bugfix

Problem Description (Customer terms)
It is not possible anymore to see the value of static local
variables in the debugger anymore.


Workaround
When entering the name of the variable in the debugger,
prepend the name with the function name.


Test Procedure
See problem description.

Affected Executables
bshell6.2


Motive source
TCS:800-153545




DevCage: # 31414 (BDNT23580): Informix array insert was not used

Date: Tue, 4 Jul 2006 16:08:32 +0200 (CEST)

Created on:  MaintCorelli
Type:        bugfix

Problem Description (Customer terms)
No array inserts are done when array interface is enabled.


Workaround
n/a

Test Procedure
enable array interface usage in db_resource file

inf_init:0200000

set DBSLOG=01770 and do a bdbpost -k -m -n -f

check the dbs.log file for PUT and FLUSH statements.
If this statements are found array insert was used.


Affected Executables
inf_srv6.2




DevCage: # 31401 (BDNT23570): TCS800-150272 Focus to first field

Date: Tue, 4 Jul 2006 15:18:00 +0200 (CEST)

Created on:  DevCage
Type:        bugfix

Problem Description (Customer terms)
In Session "Warehousing Order Type (whinh0610m000)". Create a new order type
and fill the header fields. When tabbing from the field "Receipt Procedure" the focus 
jumps back to the first field ("Warehousing Order Type") in stead of to the "Inspection Procedure" field.


Workaround
Just press a few Tabs and the focus is where it should be.

Test Procedure
See problem description.

Affected Executables
bw.exe

Motive source
TCS:800-150272




DevCage: # 31368 (BDUX23115): Eliminate usage of shm_param file

Date: Mon, 3 Jul 2006 09:40:18 +0200 (CEST)

Created on:  DevCage
Type:        enhancement

Problem Description (Customer terms)
Eliminate the need to run shm_values6.x if portingset was upgraded or otherwise.
The file $BSE/lib/shm_param needed to be too often, and is now obsolete.
The new file is $BSE/lib/shm_config which need only to be edited in case if the 
shared memory manager can't determine a SHM attach address

Test Procedure
Run shared memory manager (with eventually non-existing shm_param file)
After startup:
- an $BSE/lib/shm_config file should be created (containing only comments)
- additional log message in $BSE/lib/shmmanager.6.x.log regarding information about 
  the created SHM segment (e.g. size, attach address, ID). The ID can be used by (system's) ipcrm command (if needed)


Affected Executables
All executables using SHM (bshell, database drivers)




DevCage: # 31349 (BDUX23466): Increased limit of 256 Mb allocation per bshell to 
512 Mb on AIX

Date: Fri, 30 Jun 2006 13:54:19 +0200 (CEST)

Created on:  DevCage
Type:        porting specific change

Problem Description (Customer terms)
Under certain cases, a bshell may need to allocate more than 256 Mb memory, which is impossible on AIX

Workaround
- Shutdown BSE (all users should be logged of, otherwise SHM will not stop)
- run ldedit command on all binaries and shared libraries in $BSE/bin & shlib: ldedit -bmaxdata:0x20000000 
	This will increase the limit to 512Mb per binary.
	For more (tehcnical info), see: 
		- http://www-03.ibm.com/servers/aix/whitepapers/large_page.pdf 
		- http://publib.boulder.ibm.com/infocenter/tivihelp/v2r1/index.jsp?topic=/com.ibm.itame.doc/am60_perftune64.htm
		- http://publib.boulder.ibm.com/infocenter/pseries/v5r3/index.jsp?topic=/com.ibm.aix.doc/aixprggd/genprogc/lrg_prg_support.htm

Affected Executables
All

Motive source
Inquery 351617/SDIS:TECH-00000-01021 




DevCage: # 31311 (BDUX23339): Linux: floating point exceptions not handled 
correctly

Date: Thu, 29 Jun 2006 14:19:27 +0200 (CEST)

Created on:  MaintBaanIVc
Type:        porting specific change

Problem Description (Customer terms)
Linux porting set do not catch floating point exceptions generated by 3GL processing.
This gives a difference in the error handling between Linux and other Unix platforms.

Test Procedure
Regression tests

Affected Executables
bshell




DevCage: # 31304 (BDNT23402): Fixed dir.open resultcode on windows

Date: Wed, 28 Jun 2006 17:22:07 +0200 (CEST)

Created on:  MaintSchoenberg
Type:        bugfix

Problem Description (Customer terms)
On MS-Windows the function dir.open(""), so on an empty directory, returns a 
"1". This is wrong because a return value greater than zero means that the 
function succeed. The return value should be "-2" because the directory 
could not be opened.

The function dir.open.tree("") has the same problem.

This problem occurs on MS-Windows with BaanIVc and Corelli.
This problem doesn't occur on Unix.

Test Procedure
Run script below on a Windows system, result should be -2 

function main()
{
	long result
	string file(255)
	long return_type 
	long filesize 
	long mode 
	
	result = dir.open("")
	
	IF result >= 0 THEN			
		REPEAT
			file = dir.entry(result, TFILE, return_type, filesize, mode)
		UNTIL len(file) = 0
		result = dir.close(result)
	ENDIF	
}


Affected Executables
ntbshell.exe
dirtest.exe
sidtest.exe
timetest.exe

Motive source
TCS:800-141911




DevCage: # 31287 (BDUX23446): NQP: Single-group query gives bad performance

Date: Tue, 27 Jun 2006 14:16:23 +0200 (CEST)

Created on:  DevCage
Type:        bugfix

Problem Description (Customer terms)
A single-group query results in bad performance, because the grouping function
is not pushed to the database, but is done by the SQL processor.

An example of a single-group query is the following:

   select count(*)
   from dbtst120


Test Procedure
Execute the following query and observe that the COUNT is pushed to the database:

	select count(*)
	from dbtst120

The following query should result in just a single value (1):

	select 1
	from ( select count(*) from dbtst120 ) dt

Affected Executables
all database drivers




DevCage: # 31244 (BDUX23092): SQL ANSI substring function

Date: Thu, 22 Jun 2006 15:28:59 +0200 (CEST)

Created on:  DevCage
Type:        enhancement

Problem Description (Customer terms)
SQL substring() function was not supported

Test Procedure
Test scripts have been defined

Affected Executables
?




DevCage: # 31234 (BDUX23392): bshell debugger gives wrong outpunt for /u on 
Windows

Date: Thu, 22 Jun 2006 08:32:27 +0200 (CEST)

Created on:  DevCage
Type:        porting specific change

Problem Description (Customer terms)
Windows only: When debugging 3GL objects the /u option (print as UTC timestamp) prints
some kind of a format string instead of the actual value.

Workaround
Debug on Unix (all flavors), AS400 or even on OS390, as long as it is not Microsoft.

Test Procedure
Start the 3GL debugger. Print the value of a 'long' variable with the /u modifier. This
should show a timestamp.
See TCS remark.

Affected Executables
bshell

Motive source
TCS 800-145945




DevCage: # 31221 (BDUX23320): Users login with any password

Date: Tue, 20 Jun 2006 15:49:13 +0200 (CEST)

Created on:  MaintSchoenberg
Type:        bugfix

Problem Description (Customer terms)
The password of a user logging in with Baan Windows and Baan login protocol
is not checked. Users are able to login with any password, but empty.

Workaround
Use remote execute (rexec) and disable Baan login daemon.

Test Procedure
1) Configure Baan Windows to use Baan login protocol.
2) Try to login with the correct password and a wrong password

Affected Executables
blogind6.2
bshcmd6.2

Motive source
SDIS:TECH-00000-00931




DevCage: # 31219 (BDUX23349): Make handle.report.pool to accept more than 252 
input variables

Date: Tue, 20 Jun 2006 14:56:18 +0200 (CEST)

Created on:  DevCage
Type:        enhancement

Problem Description (Customer terms)
Some large reports have more than 252 input files. 
This cannot be handled because handle.report.pool() and other 3GL functions 
cannot handle more than 255 function arguments due to this limitation in the
3GL language.

Workaround
split up complex reports

Test Procedure
increase a tiv level to 1101 and recompile any report to see that 
the new interface is used

Affected Executables
bshell6.2
repgen6.2
bic_repgen

Motive source
TCS:800-141657




DevCage: # 31206 (BDUX23364): Project/Task: update bic_process as well for 
oipstat

Date: Mon, 19 Jun 2006 14:27:51 +0200 (CEST)

Created on:  DevCage
Type:        enhancement

Problem Description (Customer terms)
bic_bshell and bic_process contain both a declaration for oipstat


Test Procedure
compile ttgbfprocess




DevCage: # 31192 (BDUX23318): Project/Task: handle situation where there is no 
adv999 default

Date: Fri, 16 Jun 2006 11:12:48 +0200 (CEST)

Created on:  DevCage
Type:        enhancement

Problem Description (Customer terms)
Provide empty default when no default exists in record for ttadv999
in case of dynamic path elements

Affected Executables
bshell6.2




DevCage: # 31181 (BDUX23323): put.var is case sensitive

Date: Thu, 15 Jun 2006 17:06:38 +0200 (CEST)

Created on:  MaintSchoenberg
Type:        bugfix

Problem Description (Customer terms)
The function put.var() is not case insensitive. If the external variable is 
not defined lowercase, the function does not work.

E.g.

ret = put.var(process.id, "objectInfo", 10)

does not word, while

ret = put.var(process.id, "object.info", 10)

works fine.

Variable are stored lowercase in the object, and can therefore not be found 
in the put.var()

Test Procedure
Run script below, testVar should be 1

extern long testVar

function main ()
{
        testVar = 99
        put.var(pid, "testVar", 1)
}

Affected Executables
bshell

Motive source
TCS:800-147426




DevCage: # 31157 (BDUX23308): Only dynamic path objects are not linked into OIC

Date: Wed, 14 Jun 2006 11:40:22 +0200 (CEST)

Created on:  DevCage
Type:        enhancement

Problem Description (Customer terms)
Project/Task: don't store object in OBJECT_IN_CORE when 
a dynamic path element is found in object path.

Test Procedure
use -dbgobj and grep logfile on OBJECT_IN_CORE to see whether an object
is loaded in OIC list or not.

Affected Executables
bshell6.2




DevCage: # 31144 (BDUX23287): add support for Project Task in adv999

Date: Tue, 13 Jun 2006 14:30:12 +0200 (CEST)

Created on:  DevCage
Type:        enhancement

Problem Description (Customer terms)
Add support for Project/Task in bshell when accessing the
Runtime Dictionary table ttadv999
this table contains information about forms, reports etc on a session
and they might be different voor checked out sessions during 4GL development
The ttadv999 syntax is enhanced with {task1}..... entries in the string
to determine which entry belongs to a certain task in a project

Affected Executables
bshell6.2




DevCage: # 31140 (BDUX23274): iSeries: open binary files fails on V5R3

Date: Tue, 13 Jun 2006 14:13:01 +0200 (CEST)

Created on:  DevCage
Type:        bugfix

Problem Description (Customer terms)
During install of PMC tools an error 311 occurs.

Test Procedure
bsql6.2 -c 0 -q "select  ttiex180.* from  ttiex180 
	for update where  ttiex180.ukey = :ukey order by ttiex180._index1  with retry as prepared set"




DevCage: # 31126 (BDUX23226): Problem in auditing

Date: Mon, 12 Jun 2006 15:10:16 +0200 (CEST)

Created on:  MaintSchoenberg
Type:        bugfix

Problem Description (Customer terms)
No error message when audit server fails to start

Test Procedure
Added a Audit Host, in which the servername is incorrect


Affected Executables
Bshell

Motive source
SDIS:ERP-00000-04004




DevCage: # 31114 (BDUX23260): Dynamic file path element support for 4GL Studio

Date: Fri, 9 Jun 2006 12:58:58 +0200 (CEST)

Created on:  DevCage
Type:        bugfix

Problem Description (Customer terms)
enable support for Dynamic FD path handling.
Needed for 4GL Studio Project/Task
See DOCSEMEA 43698

Affected Executables
all




DevCage: # 31082 (BDUX23232): Oracla: MultiByte enables use_binary_columns for 
new installations

Date: Thu, 8 Jun 2006 09:07:58 +0200 (CEST)

Created on:  DevCage
Type:        enhancement

Problem Description (Customer terms)
Oracle MultiByte installs fail due to illegal byte streams in some tables.

Workaround
See solution #201452

Test Procedure
install

Affected Executables
ora_adm




DevCage: # 31065 (BDUX23211): repgen: sometimes the function 
r_repdll_tiv_check() is not generated

Date: Tue, 6 Jun 2006 17:05:47 +0200 (CEST)

Created on:  MaintSchoenberg
Type:        bugfix

Problem Description (Customer terms)
compile error: 'r_repdll_tiv_check' not found
during compile

Affected Executables
repgen6.2




DevCage: # 31050 (BDUX23192): Unicode: error 201 on changing old records having 
TSS strings that exceed PLEN

Date: Fri, 2 Jun 2006 15:15:35 +0200 (CEST)

Created on:  MaintSchoenberg
Type:        bugfix

Problem Description (Customer terms)
This problem might only occur in MultiByte or Unicode environments.
Error 201 (Row changed by other user) occurs on the deletion of a record that was locked with a delayed lock.

Probler Description (Technical terms)
When the database contains data that fits in a TSS field (bytes), but is wider than the domain
length (PLEN), the delayed locking compares the data from the database with the clipped data 
from the bshell.
This results in error 201 for strings that are too wide.

This problem can occur on records that were created with an older poring set than 7.6b.01, or
when data is exported and imported from another database with different constraints.

The check on PLEN should be added to the domain constraint checks.

Workaround
Change the records that give problems with GTM.

Affected Executables
bshell
bdbvalidate
bdbpost

Motive source
TCS:800-152880




DevCage: # 31046 (BDUX23198): TCS800-150156: std_gen6.2: max. number of groups 
increased to 100

Date: Fri, 2 Jun 2006 15:03:32 +0200 (CEST)

Created on:  MaintSchoenberg
Type:        bugfix

Problem Description (Customer terms)
TCS800-150156: A 4GL script cannot use group number higher than 50.

Workaround
n/a

Test Procedure
Create a 4GL script that contains only the following four lines:

	group.51:
	before.group:
	group.101:
	before.group:

Before this fix, compiling this script resulted in output that looked something
like this:

x(   1): ERROR: Label '51' not expected within a section
x(   2): ERROR: Section 'before.group' not expected
x(   3): ERROR: Label '101' not expected within a section
x(   4): ERROR: Section 'before.group' not expected

After this fix, instead the following errors should occur:

x(   3): ERROR: Label '101' not expected within a section
x(   4): ERROR: Section 'before.group' already defined

Affected Executables
std_gen

Motive source
TCS:800-150156




DevCage: # 31038 (BDUX23188): TCS800-152878 / Unicode: key.compare() sometimes 
declares different enums/bytes to be equal

Date: Fri, 2 Jun 2006 11:11:46 +0200 (CEST)

Created on:  MaintSchoenberg
Type:        bugfix

Problem Description (Customer terms)
TCS800-152878: The 4GL Engine sometimes erroneously reports "Record already
exists", because in those cases key.compare() erroneously reports that
different records (which only differ in enum and/or byte fields) are equal.

Workaround
n/a

Test Procedure
See defect.

Affected Executables
bshell

Motive source
TCS:800-152878




DevCage: # 31005 (BDUX23162): ERP-00000-04930: database users file queried 
incorrectly if OS and Baan user name have different case

Date: Tue, 30 May 2006 17:27:34 +0200 (CEST)

Created on:  MaintSchoenberg
Type:        bugfix

Problem Description (Customer terms)
When the OS user name contains a capital, the Baan user name also contains a
capital character, which makes it an invalid Baan user name (on BaanV and
later).

Workaround
n/a

Test Procedure
See above.

Affected Executables
bshell

Motive source
SDIS:ERP-00000-04930




DevCage: # 30935 (BDUX23080): bshell: string compare on code-features gives 
sometimes wrong result

Date: Tue, 23 May 2006 13:47:19 +0200 (CEST)

Created on:  MaintSchoenberg
Type:        bugfix

Problem Description (Customer terms)
Strings containing code features (see 3GL cf$() function), do not compare correctly.

Workaround
For single byte environments: Run in locale ISO-8859-1

Test Procedure
Test the following 3GL code in a locale that is not equal to ISO-8859-1:

function Error(string i(100))
	{
		message("Error in %s",i)
	}

	function Ok()
	{
	}

	function main()
	{
		string s1(10)
		string m1(10) MB

		s1 = "aa" & cf$(0) & "bb"
		m1 = "zz" & cf$(1) & "yy"

		if ( s1 = m1 )
		then
			Error("strcmp containing cf$()" )
		else
			Ok()
       		endif
	}


Affected Executables
bshell

Motive source
TCS 800-152766




DevCage: # 30888 (BDUX23025): Wrong compiler behaviour

Date: Fri, 19 May 2006 14:22:22 +0200 (CEST)

Created on:  MaintBaanIVc
Type:        bugfix

Problem Description (Customer terms)
Wrong compiler behaviour when we write var=var+1+1+1 instead of var=var+3

Workaround
N/A

Test Procedure
Compile and execute the folwing script

function main()
{
        long g
        long w
        long x

        g=0
        g=g+1+1     | g = 2

        w=0
        w=w+1+1+1   | w = 1 or coredump depends on OS

        x=0
        x=x+1+1+1+1 | x = 4
}

Affected Executables
Bic6.x

Motive source
SDIS:Erp-00000-04523




DevCage: # 30876 (BDNT22963): Compiling file in dos format on Unix

Date: Fri, 19 May 2006 10:52:50 +0200 (CEST)

Created on:  DevSchoenberg
Type:        bugfix

Problem Description (Customer terms)
Error when compiling files in dos format on unix.

Workaround
Define macros on one line, without CR/LF. Also in the script where the macros are used do not use 
CR/LF.
E.g. do not use:
	FILL.WITH.MESSAGE(log.message,
		whinhs4242,
		labelof("whinh200", DD.TABLE),
		labelof("whinh200.mint"),
		whinh200.mint)

but use:
	FILL.WITH.MESSAGE(log.message, whinhs4242, labelof("whinh200", DD.TABLE), labelof("whinh200.mint"), whinh200.mint)


Test Procedure
The test procedure is written in the request description. It is not easy to create the exact same
situation, so when possible use the described reproduction scenario.

Affected Executables
bic.exe, bic6.x

Motive source
SDIS:TECH-00000-00618




DevCage: # 30871 (BDUX23016): Bdbreconfig: BSE_REM with -p option does not work

Date: Fri, 19 May 2006 10:50:36 +0200 (CEST)

Created on:  DevSchoenberg
Type:        bugfix

Problem Description (Customer terms)
In a AS-MAS configuration bdbreconfig fails with the following error if the -p 
option is used:

	Package combination "b61au" does not exist.

Test Procedure
See Problem Description (Customer terms).

Affected Executables
bdbreconfig6.2




DevCage: # 30864 (BDUX23003): T800-146672: db.first with lock gives error after 
db.unbind is used

Date: Fri, 19 May 2006 10:35:50 +0200 (CEST)

Created on:  DevSchoenberg
Type:        bugfix

Problem Description (Customer terms)
A second db.call with lock fails if the transaction is aborted after db.unbind is used.

Test Procedure
Run the script above and observe that the result is okay.

Affected Executables
bshell

Motive source
TCS:800-146672