List of changes for portingset: 9.3f ------------------------------------------------------------------------ pset2019_4: # 82127 (BDUX78771): bshell db.check.restricted() with xcomp reference Date: Mon, 24 Feb 2020 16:24:45 +0100 Created on: pset2019_4 Type: bugfix _Problem Description (Customer terms)_ 3GL: db.check.restricted() does not hanlde inter company references correctly. _Test Procedure_ regression tests _Affected Executables_ bshell _Motive source_ InforXtreme:668712 ------------------------------------------------------------------------ pset2019_4: # 82104 (BDUX78736): D713068: Item (tcibd001.item) with Cyrillic characters causes MR_INDEXOUT when navigating in session Inventory 360 (whwmd4300m000) Date: Fri, 21 Feb 2020 15:42:59 +0100 Created on: pset2019_4 Type: bugfix _Problem Description (Customer terms)_ Item (tcibd001.item) with Cyrillic characters causes MR_INDEXOUT when navigating in session Inventory 360 (whwmd4300m000) _Test Procedure_ See Problem Description (Customer terms) _Affected Executables_ bshell _Motive source_ InforXtreme:713068 ------------------------------------------------------------------------ pset2019_4: # 82101 (BDUX78747): RSA Encryption and Digital Signing Date: Fri, 21 Feb 2020 15:16:30 +0100 Created on: pset2019_4 Type: enhancement _Problem Description (Customer terms)_ rsa.encrypt() and rsa.verify.signature added for rsa private/public key encryption and digital signing Functions: function global long rsa.encrypt(const string pub_key_file, const string data_in, long data_in_len, long padding_scheme, ref string output) function global boolean rsa.verify.signature(const string pub_key_file,long digest_type, const string digest,const string signature) _Test Procedure_ Regression Tests added ------------------------------------------------------------------------ pset2019_4: # 82044 (BDUX78714): oracle: oracle 12.1 out of support Date: Wed, 12 Feb 2020 13:32:22 +0100 Created on: pset2019_4 Type: porting specific change _Problem Description (Customer terms)_ Oracle 12.1 not supported anymore. Premier Support (PS) ended Jul 31, 2018 and one year of free Extended Support (ES) was in effect until July 31, 2019. _Affected Executables_ ora_srv ------------------------------------------------------------------------ pset2019_4: # 81769 (BDNT78326): StartFirst: change Documentation info in startfirst dialog/menu. Date: Mon, 06 Jan 2020 15:53:30 +0100 Created on: r2019_3 Type: bugfix _Problem Description (Customer terms)_ StartFirst: change Documentation info in startfirst dialog/menu. _Motive source_ TCS:800-233855 ------------------------------------------------------------------------ pset2019_4: # 81756 (BDUX78218): AMT hashlocs are incorrectly calculated Date: Mon, 06 Jan 2020 12:40:52 +0100 Created on: pset2019_4 Type: bugfix _Problem Description (Customer terms)_ AMT tracing is missing location of source files. _Affected Executables_ all ------------------------------------------------------------------------ pset2019_4: # 81730 (BDNT78278): new copyright text Date: Thu, 02 Jan 2020 11:10:08 +0100 Created on: pset2019_4 Type: enhancement _Problem Description (Customer terms)_ New copyright and version ------------------------------------------------------------------------ pset2019_4: # 81720 (BDUX78259): Bshell: Some allocation patterns give huge memory fragmentation, resembling memory leak Date: Thu, 26 Dec 2019 11:35:59 +0100 Created on: pset2019_4 Type: bugfix _Problem Description (Customer terms)_ Since the 9.3d porting set some memory allocation patterns result in a huge fragmentation of the memory heap. Increasingly larger blocks on the heap will never be reused, because multiple blocks cannot be merged. The following program demonstrates this: function main() { string a(1,1) based string b(1,1) based string c(1,1) based long i i = 3 while i < 10000 alloc.mem( a, 333, i ) alloc.mem( b, 777, i ) alloc.mem( c, 547, i ) i = i + 1 endwhile } The bshell executing this program uses many GiBs of memory. _Workaround_ Use better allocation patterns, e.g. increase the size of the arrays with a factor 1.4. _Test Procedure_ Run the program in the Problem Description (Customer Terms). The program should use more and more memory, because it increases the size of every array. However, it should not use many GiBs of memory, but more like 0.5GiB at the most. _Affected Executables_ bshell ------------------------------------------------------------------------ pset2019_4: # 81621 (BDUX78108): string arrays with Multilanguage elements leak memory Date: Fri, 13 Dec 2019 14:17:59 +0100 Created on: pset2019_4 Type: bugfix _Problem Description (Customer terms)_ Memory leak when using Multi Language Fields with certain reports (like cisli0811 and clisli0311) when using string arrays _Workaround_ in 3GL when memory is allocated call set.mem( array, "") _Test Procedure_ regtest _Affected Executables_ bshell6.2 _Motive source_ InforXtreme:706161 ------------------------------------------------------------------------ pset2019_4: # 81541 (BDUX78011): D688494: SQL: SELECT with CASE and MLE results in error 205 (SQLState 23000: MLV constraint: lang not available) Date: Wed, 04 Dec 2019 11:33:28 +0100 Created on: Mussorgsky Type: bugfix _Problem Description (Customer terms)_ SQLState 23000: MLV constraint: lang not available (205) when running an extension for a table MLE enabled. _Workaround_ Either do not use a CASE with an MLE columns as result, of disable MLE for that column. _Test Procedure_ Enable MLE for a column, and execute an SQL statement containing that column as the result of a CASE expression in the SELECT clause. _Affected Executables_ Bshell DB drivers ------------------------------------------------------------------------ pset2019_4: # 81406 (BDUX77791): D704185: Sales Contract - Terms & Conditions Link results in Database Error 221 Date: Thu, 21 Nov 2019 10:30:35 +0100 Created on: r2019_3 Type: bugfix _Problem Description (Customer terms)_ Sales Contract - Terms & Conditions Link results in Database Error 221 _Test Procedure_ Sales Contract - Terms & Conditions Link A regression test has been enhanced to verify that a record can be linked to/unlinked from an object. _Affected Executables_ Bshell ------------------------------------------------------------------------ pset2019_4: # 81298 (BDUX77729): Totals not correct after changing layout in Report Designer Date: Mon, 11 Nov 2019 16:57:05 +0100 Created on: pset2019_4 Type: bugfix _Problem Description (Customer terms)_ When a report is created which displays totals by production order. When printing this report standard in LNUI, the behavior is correct. When printing the report to Report Designer and modifying the height of the specific layout (or any other change not related to the total field), the total calculation is not correct anymore. It seems that changing a layout in Report Designer has an impact on the total calculation. In our opinion, this is not correct. This is a result of the combination of the print condition and the calculation in the personalization (as the layout with the filed is personalized as well) _Workaround_ NA _Test Procedure_ change something in the report to make a personalization with totals, like printing in bold. _Affected Executables_ repgen _Motive source_ InforXtreme:675840 ------------------------------------------------------------------------ pset2019_4: # 81276 (BDNT77584): split minmax init into mininit and maxinit Date: Thu, 07 Nov 2019 09:16:53 +0100 Created on: r2019_3 Type: bugfix _Problem Description (Customer terms)_ First "total by order" always print 0 in "Quantity Delivered" column. _Workaround_ Do not have a min and a max on the report. _Test Procedure_ have report with both min and max and see that only one is correct. _Affected Executables_ Repgen _Motive source_ InforeXtreme: 681879 ------------------------------------------------------------------------ pset2019_4: # 81244 (BDUX77690): Call Graph Profiler: disable jump.retry.point for PROFILE_TRAMPOLINE Date: Fri, 01 Nov 2019 16:24:49 +0100 Created on: Mussorgsky Type: bugfix _Problem Description (Customer terms)_ Sometimes the bshell can start looping or crashing when using PROFILE_TRAMPOLINE=retry.* _Workaround_ Don't use PLATFORM_TRAMPOLINE=retry.* _Affected Executables_ bshell6.2 ------------------------------------------------------------------------ pset2019_4: # 81165 (BDUX77621): Bugfix: overwriting string literal Date: Thu, 24 Oct 2019 15:10:42 +0200 Created on: r2019_3 Type: bugfix _Problem Description (Customer terms)_ Some code overwrote a string literal if it was called with a nullptr. This has been changed. _Test Procedure_ Built with the dev6. ------------------------------------------------------------------------ pset2019_4: # 81142 (BDNT77570): mb.type: allow void argument, especially string array Date: Tue, 22 Oct 2019 16:27:49 +0200 Created on: r2019_3 Type: enhancement _Problem Description (Customer terms)_ Bshell function mb.type now accepts void argument, in order to allow to determine the type (sb or mb) of an unallocated based string array. _Motive source_ TCS:800-232020 ------------------------------------------------------------------------ pset2019_4: # 81072 (BDNT77329): file.mv should move file with read permissions if directory permissions are correct. Date: Tue, 15 Oct 2019 16:17:48 +0200 Created on: Mussorgsky Type: bugfix _Problem Description (Customer terms)_ the file.mv does not move the file when permissions of file is read only and the directory permissions are correct. _Workaround_ change permissions or do a copy/remove action. _Test Procedure_ execute the file.mv function on a file with only read permissions, but the directory permissions full. _Affected Executables_ bshell _Motive source_ InforXtreme:697598