List of changes for portingset: 8.7a.01 MaintBartok: # 49541 (BDNT40871): Windows: Incorrect error message when attaching to shm fails Date: Tue, 8 Feb 2011 13:00:55 +0100 (CET) Created on: MaintBartok Type: bugfix Problem Description (Customer terms) If a bshell (or any other program) fails to attach to shared memory on Windows an incorrect message is given: OpenSemaphore( 'Note that mixing 32-bit and 64-bit executables is not possible.') failed (error 124424). Check whether Shared Memory Manager is running. Both the semaphore name and the error code are incorrect. Test Procedure Stop the Shared Memory Manager, and attempt to start a bshell. This will fail. Observe that a messages is logged and that the message contains the semaphore name and a valid error code. Affected Executables ntbshell, repgen, bic, any other executable attaching to shared memory MaintBartok: # 49481 (BDNT40829): LNCSA-481 Pass decimal separators to bshell Date: Thu, 3 Feb 2011 17:12:26 +0100 (CET) Created on: MaintBartok Type: bugfix Problem Description (Customer terms) The decimal separator character and thousands separator characters used in ERP screens does not follow the user settings in Windows regional options. To allow this, BW must be adapted to pass these regional settings to the ERP server. This fix only makes these settings available to the backend. A backend solution is needed to realy use these settings. Affected Executables BW.EXE Motive source ScrumStory:LNCSA-481 MaintBartok: # 49433 (BDUX40784): some ottstpmess messages cannot be translated Date: Mon, 31 Jan 2011 17:14:41 +0100 (CET) Created on: MaintBartok Type: bugfix Problem Description (Customer terms) The session timeout text cannot be translated Affected Executables bshell6.2 Motive source Defect nr: 300833 MaintBartok: # 49363 (BDUX37897): spt sessions: oracle error 1002 Date: Tue, 25 Jan 2011 17:22:26 +0100 (CET) Created on: MaintBartok Type: bugfix Problem Description (Customer terms) Customers running spt sessions (like tfsptdll0938 and whspthdll2200) get error ORA-01002 is simulation mode. The error is caused by an explicit abort.transaction() command that causes a rollback of the database to a point in time prior to the execution of an Oracle cursor. This cursor gets invalidated by this action. When the select loop continues with this cusor the error occurs. In normal operations the abort.transaction() is not called, but a commit.transaction() will be done. Aborts on errors are not a problem either as the logic normally jumps to the retry point. Test Procedure regression test Affected Executables ora_srv Motive source Infor365:272293 and 273259 and others. MaintBartok: # 49279 (BDNT40624): SSPI logon failed if blogind runs under local account Date: Tue, 18 Jan 2011 13:10:48 +0100 (CET) Created on: MaintBartok Type: bugfix Problem Description (Customer terms) SSPI login not possible on Windows 2008 and higher if Logic Service not running under system account identity. Test Procedure Install Logic Service by Infor Management snap-in and register logic service to run under a specific account. Observe that SSPI logon works after the logic service has been installed. No error should occur now. Affected Executables rexecd.exe Motive source TCS:800-175692 MaintBartok: # 49265 (BDNT40623): Text shadows remain in Calculator Date: Mon, 17 Jan 2011 14:11:15 +0100 (CET) Created on: MaintBartok Type: bugfix Problem Description (Customer terms) On windows Vista and Windows 7, when using the ERP Calculator after deleting some text, a shadow of the text remains visible. Test Procedure See problem description in Infor365: 292856 Affected Executables bw.exe Motive source Infor365:293328 MaintBartok: # 49137 (BDNT40464): First day of week in datepicker always monday Date: Thu, 6 Jan 2011 15:54:52 +0100 (CET) Created on: MaintBartok Type: bugfix Problem Description (Customer terms) The first day of week in the BW date-picker is always monday. Test Procedure See problem description in Infor365 defect: 294860 Affected Executables bw.exe Motive source Infor365:294860 MaintBartok: # 49117 (BDUX40421): Bic: crash on use of functions from DLL Date: Wed, 5 Jan 2011 15:22:23 +0100 (CET) Created on: Charpentier Type: bugfix Problem Description (Customer terms) Bic may crash if functions are used that are prototyped in a DLL. An example of such use is the following small program: #include function main() { string menucode(17) gbf.add.object(menucode, tt.menu.desc(menucode,"1"), 1, GBF.INTERIOR) } The crash is observed with the 8.7b and 8.8a porting sets. In the 8.7a porting set (and earlier) a (more or less) harmless memory corruption occurred. Test Procedure Compile a script such as in the Problem Description (Customer Terms) Affected Executables bic MaintBartok: # 49011 (BDUX40278): Bdbpre: escaping of new-lines of backslashes broken Date: Tue, 28 Dec 2010 10:36:22 +0100 (CET) Created on: MaintBartok Type: bugfix Problem Description (Customer terms) Bdbpre creates a corrupt dump if the data contains a new-line or backslash. It should escape the following characters using the corresponding escape sequence: character escape sequence --------------- --------------- new-line \\n backslash \\\ carriage return \\r hash \# separator \ (e.g. \, when the comma (,) is the separator) If the dump is imported using bdbpost, then it signals a corrupt record and the data is not imported correctly. Note, that this does not apply to dumps created with the -x option. This bug is introduced with porting set 8.7a. Workaround Use a bdbpre from the previous porting set. Test Procedure Create a pre dump of a table containing new-lines or backslashes (table ttdba015 is known for having backslashes in encrypted passwords). Use the -t option (do not use the -x option). Import the dump (preferably into a test company) and verify the data. Affected Executables bdbpre MaintBartok: # 48978 (BDUX40256): BDUX40153 build and test errors (send.wait) Date: Thu, 23 Dec 2010 12:03:11 +0100 (CET) Created on: MaintBartok Type: bugfix Problem Description (Customer terms) Fix test and build errors as introduced by BDUX40153 Affected Executables bshell6.2 MaintBartok: # 48961 (BDUX40153): send.wait() should not hang on a process id which is gone Date: Wed, 22 Dec 2010 13:51:49 +0100 (CET) Created on: MaintBartok Type: bugfix Problem Description (Customer terms) In WebUI and in combination of a float exception using PCF, WebUI appears to be hung. Test Procedure two reg tests have been added tests_bshell/send_wait_cancelation.test tests_bshell/send_wait_div_by_zero.test Affected Executables bshell6.2 Motive source ScrumStory:LNCPE-458 Infor 365 Defect: 291357 MaintBartok: # 48861 (BDUX38954): AMT: enhance reports Date: Thu, 16 Dec 2010 13:45:33 +0100 (CET) Created on: MaintBartok Type: enhancement Problem Description (Customer terms) AMT Report enhancments Affected Executables amt6.2 Motive source ScrumStory:LNCPE-191 MaintBartok: # 48765 (BDUX39895): Defect 285580: AMS table field roles inconsistent with table authorizations Date: Thu, 9 Dec 2010 12:01:24 +0100 (CET) Created on: MaintBartok Type: bugfix Problem Description (Customer terms) Table field authorizations are inconsistent with table authorizations. If a role is added that only gives "read" permission on a field, then the "write" permission granted by another role can be revoked. This is incorrect. The problem occurs when the first role has no field level authorizations, but has data level authorizations that grant "write" or "delete" permission, and the second role has a field level authorization that only grants "read" permission. In general, an extra role should *never* revoke permissions that are granted by another role. Test Procedure Suppose we have two roles. Role A grants "delete" permission on all data: role A ------ *:*:D Role B grants "read" permission on a field: role B ------ tcibd001.item:*:R If only role A is used then the field tcibd001.item can be edited on the form. If both rola A and role B are used then the field should be editable too. NOTE: An update (solution yet unknown) has to be used. Affected Executables bshell Motive source Infor365:285580 MaintBartok: # 48752 (BDUX40038): db.unbind(0) should not core dump Date: Wed, 8 Dec 2010 12:03:37 +0100 (CET) Created on: MaintBartok Type: bugfix Problem Description (Customer terms) db.unbind(0) shouldn't core dump a bshell but return an error instead Test Procedure tests_bshell/db.unbind.test Affected Executables bshell6.2 Motive source TCS:800-174817 MaintBartok: # 48746 (BDUX39998): 3gl Debugger: a command has to be entered twice to function Date: Tue, 7 Dec 2010 16:31:13 +0100 (CET) Created on: MaintBartok Type: bugfix Problem Description (Customer terms) Debugger command has to be typed twice sometimes Workaround type the command twice Test Procedure See TCS remark Affected Executables bshell6.2 Motive source TCS:800-172099 MaintBartok: # 48717 (BDUX39962): Defect 292899: Level-1 QP, AIX: Query with OR and ORDER BY returns no result Date: Fri, 3 Dec 2010 15:09:14 +0100 (CET) Created on: MaintBaanIVc Type: bugfix Problem Description (Customer terms) On AIX, level-1 a query with an OR on an index and with an ORDER BY returns no result. The same query worked fine with porting set 6.1c.11, but from 6.1c.12 it returns no result. An example of a failing query is the following: select tdpur045._index1 from tdpur045 where (tdpur045._index1={10007} or tdpur045._index1 = {0} ) order by tdpur045.orno Test Procedure Run a query such as the following, on AIX using level-1: select tdpur045._index1 from tdpur045 where (tdpur045._index1={10007} or tdpur045._index1 = {0} ) order by tdpur045.orno (Substitute 10007 with a value for which a record exists) Observe that the proper row is returned. Affected Executables all level-1 drivers Motive source Infor365:292899 MaintBartok: # 48690 (BDNT39972): Passing bwc file on bw command line problem on Windows 7 Date: Wed, 1 Dec 2010 16:12:59 +0100 (CET) Created on: MaintBartok Type: bugfix Problem Description (Customer terms) When starting from a commandline: BW.EXE .bwc, the following error message is shown: Could not load configuration file "\config\.bwc" Test Procedure See problem description in TCS. Affected Executables bw.exe Motive source TCS:800-176177 MaintBartok: # 48681 (BDNT39966): Problem with resizing multiple columns at the same time Date: Wed, 1 Dec 2010 14:30:49 +0100 (CET) Created on: MaintBartok Type: bugfix Problem Description (Customer terms) With a new BW version you cannot resize more than one column with one resize action anymore. Test Procedure See defect Infor365:294190 Affected Executables bw.exe Motive source Infor365:294190 MaintBartok: # 48678 (BDNT39961): Client should not call TssSetMinMaxValues Date: Wed, 1 Dec 2010 13:40:32 +0100 (CET) Created on: MaintAlbinoni Type: bugfix Problem Description (Customer terms) When BW runs on a server (in unicode mode) with high_ascii_tolerance set, a message "*** Error in TSSfind_locale: Can't find TSS characterset" appears in the BW Messages window. Test Procedure Create a file %BSE%\lib\defaults\all with contents: high_ascii_tolerance:1 and then run bw. Affected Executables bw.exe bwprint.exe MaintBartok: # 48631 (BDUX39901): fix core dump in getmac.c Date: Fri, 26 Nov 2010 10:08:05 +0100 (CET) Created on: MaintAlbinoni Type: bugfix Problem Description (Customer terms) Core dump when starting up a bshell in SlmClient.so on Linux This happens only after a lot of network traffic has been generated as reported by /proc/net/dev when enumerating for the network interfaces. Workaround It is not really a workaround but regularly rebooting the machine should work. Test Procedure 1) create a small 3gl program pmain: | start function main() {} | end 2) compile bic6.x ./pmain -o ./omain 3) bshell6.x -server -set SLM_ENABLED=1 ./omain the bshell should not crash any more Affected Executables SlmClient.so Motive source Infor365:292189 MaintBartok: # 48607 (BDUX39868): Defect 293607: ODBC: Multi-company query on multi-language column gives incorrect result Date: Wed, 24 Nov 2010 17:30:33 +0100 (CET) Created on: MaintBartok Type: bugfix Problem Description (Customer terms) This problem occurs with the ODBC/JDBC integration. A multi-company query on a multi-language column (MLE) gives an incorrect result. An example of such a query is the following: SELECT "company_nr" AS COMPANY_NO, "dimx" AS BUSINESS_DIM_CD, "desc" AS BUSINESS_DIMENSION_NM "dtyp" AS DIMENSION_TYPE, "atyp" AS SUMMARY_ACCOUNT, "pdix" AS PARENT_DIM_CD, "subl" AS LEVEL_NO FROM "tflgd010" WHERE company_nr IN (200,250,310,320,340) AND "dimx" = '000029514' Note that one of the columns is multi-language enabled (MLE). Test Procedure Run a multi-company query on a multi-language column. Observe that data from all companies is returned. Affected Executables All database drivers Motive source Infor365:293607 MaintBartok: # 48558 (BDUX39819): Repgen: Support more than 253 report fields Date: Fri, 19 Nov 2010 15:19:01 +0100 (CET) Created on: MaintBartok Type: bugfix Problem Description (Customer terms) Reports cannot contain more than 253 field elements, if the report must be sorted. Note that individual array field elements count as one field element. Test Procedure Compile reports, both with less than and more than 253 input field elements. Make sure the report has to be sorted, and verify that the result is correct. Affected Executables repgen MaintBartok: # 48449 (BDNT39635): Prevent window to activate when focus is set Date: Wed, 10 Nov 2010 16:53:46 +0100 (CET) Created on: MaintBartok Type: bugfix Problem Description (Customer terms) Open the session "Sales Order - Lines" (tdsls4100m900). Zoom to the details of the header. After modifying and saving data in the session "Sales Orders" (tdsls4100m000) session, this session goes to the background and the user is presented with the session "Sales Order - Lines" (tdsls4100m900) instead. Test Procedure See problem description in Infor365:289494 Affected Executables bw.exe Motive source Infor365:289494 MaintBartok: # 48445 (BDNT39702): Unexpected input language switching Date: Wed, 10 Nov 2010 16:51:51 +0100 (CET) Created on: MaintBartok Type: bugfix Problem Description (Customer terms) The input language automatically switches between English and Arabic and vice versa after zooming or after clicking with the mouse in an editable field. This occurs when on the client a BIDI language is enabled and when the backend is configured for a BIDI locale. Test Procedure See problem description in Infor365 defect: 292048 Affected Executables bw.exe Motive source Infor365:292048 MaintBartok: # 48434 (BDUX39672): AIX: floating point exception on frsp assembler instruction Date: Wed, 10 Nov 2010 15:07:34 +0100 (CET) Created on: MaintBartok Type: bugfix Problem Description (Customer terms) Floating Point Exception on 64bit porting set Workaround use AIX/32bit porting set or another platform. Test Procedure regression tests Affected Executables bshell Motive source TCS:800-173076 Inc:4007495 MaintBartok: # 48374 (BDUX39536): Bshell: run[.baan].prog does not truncate output and error file Date: Mon, 8 Nov 2010 10:30:25 +0100 (CET) Created on: MaintBartok Type: bugfix Problem Description (Customer terms) The 3GL functions run.prog() and run.baan.prog() have optional arguments to direct the standard output and error output of the program to a file. On Windows the output files are properly truncated before output is written, but on Unix the files are _not_ truncated. This may result in a corrupt output file if the output file already existed before the call. Workaround Remove the files before calling run.[baan.]prog(). Test Procedure Create a file with some contents, and use the run.prog() call to write to the same file. Observe that the file is properly truncated, in effect none of the original contents is visible. Affected Executables sh_server MaintBartok: # 48359 (BDUX39599): fixed false assert in regression test and div by zero in internal perl script Date: Fri, 5 Nov 2010 11:14:51 +0100 (CET) Created on: MaintBartok Type: bugfix Problem Description (Customer terms) Only an issue in debug porting sets, so not for customers. Test Procedure regtests Affected Executables bdbvalidate