List of changes for portingset: 6.1c.12


MaintBaanIVc: # 46016 (BDNT37428): min value for date not correct if only first 
option of index is given, only on level1

Date: Fri, 16 Apr 2010 09:01:48 +0200 (CEST)

Created on:  MaintBaanIVc
Type:        bugfix

Problem Description (Customer terms)
Error 205 when installing PMC solutions.

Workaround
use level 2, or change the query so all arguments of an index are passed


Test Procedure
on a level 1 database execute the mentioned query:
select * from ttiex190 where ttiex190._index1 = {1}
amd see if this is no longer giving error 205

Affected Executables
database drivers

Motive source
Infor365:268567




MaintBaanIVc: # 46005 (BDUX37411): string.scan function changed to handle 
doubles correctly

Date: Thu, 15 Apr 2010 11:06:12 +0200 (CEST)

Created on:  MaintAlbinoni
Type:        bugfix

Problem Description (Customer terms)
small values are not handled correctly by exchange

Workaround
read the double as a string, and use the val function to get it to a double

Test Procedure
Use for instance the next script:
function main() {
        long longval
        string stringval(15)
        double doubleval
        long ret

        ret=string.scan("1|--9.3116625523611e-12|aap","%d|%f|%s",longval,doubleval,stringval)
}


Affected Executables
bshell

Motive source
Infor365:217659




MaintBaanIVc: # 46003 (BDUX37416): Move SLM EOM date to 5 januari 2011

Date: Thu, 15 Apr 2010 10:55:53 +0200 (CEST)

Created on:  MaintBaanIVc
Type:        bugfix

Problem Description (Customer terms)
Move EOM date checking for objects to 5 januari 2011

Affected Executables
bshell6.1
srddinit6.1

Motive source
ScrumStory:LNCPE-339




MaintBaanIVc: # 45673 (BDNT37104): Baanman snapin incorrectly shows env strings: 
the block was not correctly terminated

Date: Wed, 17 Mar 2010 16:27:20 +0100 (CET)

Created on:  MaintAlbinoni
Type:        bugfix

Problem Description (Customer terms)
Baanman management snap-in may show corrupted text when showing the environment variables (i.e. BSE properties) of an BSE.

Test Procedure
Click right mouse button on a selected BSE in baanman, and choose properties. Use the Environment variables tab and observer that 
no strange/unreadable data is shown.

Affected Executables
baanman.dll




MaintBaanIVc: # 45618 (BDNT37002): 32-bit BW installation overwrites 64-bit 
files in shared infor directory on Windows

Date: Fri, 12 Mar 2010 12:19:14 +0100 (CET)

Created on:  MaintAlbinoni
Type:        bugfix

Problem Description (Customer terms)
BW mistakely uses c:\infor\erpln\commonx64 path during update.




MaintBaanIVc: # 45184 (BDUX36656): Db2 driver: DB2 does not support LIKE 
patterns that are not constant or that contain a subquery

Date: Fri, 29 Jan 2010 12:21:27 +0100 (CET)

Created on:  MaintAlbinoni
Type:        bugfix

Problem Description (Customer terms)
Executing the following query in ANSI mode on a DB2 database, results in an 
error.

	select empno 
	from dbtst120 
	where firstnme like 
		( select firstnme 
		  from dbtst120 
		  where empno = 10 )

DB2 reports the following error:

	SqlState=QP999, '[IBM][CLI Driver][DB2/LINUXX8664] SQL0132N  A LIKE 
	predicate or POSSTR scalar function is not valid because the first operand 
	is not a string expression or the second operand is not a string.  A LOCA', 
	NativeError=1132


Test Procedure
Use bsql6.2 to reproduce:

	bsql6.2 -p 16 -q "select ..."

The option -p 16 forces the SQL processor to use ANSI mode.

Affected Executables
db2v5_srv




MaintBaanIVc: # 45178 (BDUX36709): build broken... YES!!!!

Date: Fri, 29 Jan 2010 09:36:32 +0100 (CET)

Created on:  MaintBaanIVc
Type:        bugfix

Problem Description (Customer terms)
Broken build

Test Procedure
clearmake portingset

Affected Executables
bshell6.1




MaintBaanIVc: # 45166 (BDNT36635): Manual merge of BDUX36577 (clusterawareness 
of portingset)

Date: Thu, 28 Jan 2010 14:17:29 +0100 (CET)

Created on:  MaintBaanIVc
Type:        porting specific change

Problem Description (Customer terms)
Cluster admin extenstion DLLs are not supported (or very limited) on Windows 2008. 
Therefore the cluster part was rewritten/simplied to not using admin extension DLLs.

Affected Executables
cluster related binaries + due to backport of generic changes, nearly every other binary of the portingset.




MaintBaanIVc: # 45033 (BDUX36586): bshell, ...: corruption when handling DD with 
many child columns

Date: Tue, 12 Jan 2010 17:07:19 +0100 (CET)

Created on:  MaintBaanIVc
Type:        bugfix

Problem Description (Customer terms)
A recent change in table tfgld004 for FP7 results in the following error 
reported by bdbreconfig:

	Can't find child column - dictionary may contain conflicting versions or 
	could be corrupted

This problem occurs because the data dictionary for tfgld004 contains a lot of
so-called "combined columns", resulting in a buffer overrun in the porting set. 

Test Procedure
Create a DD with many conbined columns, so that the total length of the names of
the child columns exceeds 2048 bytes. Use this DD in any client (bshell, bsql, 
etc). The program should not crash and behave correctly.

Alternatively, use the new definition of tfgld004, which hosts 121 combined
columns.

Affected Executables
bdbpost
bdbpre
bdbreconfig
bshell
bsql
(and all others containing the qpd library)




MaintBaanIVc: # 44899 (BDNT36487): BW4: introduce sockets logging

Date: Tue, 22 Dec 2009 12:20:39 +0100 (CET)

Created on:  MaintBaanIVc
Type:        bugfix

Problem Description (Customer terms)
Users complain about the fact that after a Windows task switch, 
e.g. Excel is already open and switch to  Baan, the Baan application in the first moment is not responding

Affected Executables
bw

Motive source
SDIS:TECH-00000-05795




MaintBaanIVc: # 44892 (BDUX36481): Fix spelling mistake in message

Date: Tue, 22 Dec 2009 10:02:12 +0100 (CET)

Created on:  MaintBaanIVc
Type:        bugfix

Problem Description (Customer terms)
Fix spelling mistake in error message dealing with End of Maintenance Licenses

Affected Executables
bshell6.1




MaintBaanIVc: # 44871 (BDUX36438): Bshell: function 
xmlReplaceInvalidCharacters() to replace invalid XML characters

Date: Fri, 18 Dec 2009 14:58:25 +0100 (CET)

Created on:  MaintBaanIVc
Type:        bugfix

Problem Description (Customer terms)
Sending a BOD fails if the data contains characters that are invalid within an 
XML document.

According to [XMLSTD], the following Unicode characters are allowed in an XML 
document:

  Char ::=  #x9 | #xA | #xD | [#x20-#xD7FF] | [#xE000-#xFFFD] | [#x10000-#x10FFFF]

All other characters are forbidden. There is no possibility to escape them. The 
forbidden characters are:

	- ASCII control characters in the range [#x0-#x1F], except the allowed 
	  characters #x9 (Horizontal Tab), #xA (Line Feed), and #xD (Carriage Return);
	- Unicode surrogate characters in the range [#xD800-#xDFFF];
	- The <not a character> Unicode values #xFFFE and #xFFFF.

Test Procedure
Write a 3GL program that uses the XmlReplaceInvalidCharacters() function. Verify
that any character that is not valid (as described above), in the UTF-8 domain,
is replaced by the specified replacement character.

Affected Executables
bshell