------------------------------------------------------------------------ pset2020_3: # 84023 (BDUX81284): permission for session check in wrong company due to compnr 0 fix Date: Fri, 18 Dec 2020 14:57:56 +0100 Created on: pset2020_3 Type: bugfix _Problem Description (Customer terms)_ For a normal user a AMS Role is defined where permissions are given to start sessions of the DA package in companies 1782, 1783 and 1784. When using Portingset 9.3i from the date 3 november 2020 the normal user does not have any problems starting session daxch0501m000 (Exchagne Schemes). However, on december 15 Portingset 9.3j has been installed and in the following Bflow test run a specific Bflow test fails. It fails with the message that the user does not have permissions to start session daxch0501m000. AMS Roles and the user definition are all defined and created in the Bflow test and this in not changed. The problem can also be reproduced without Bflow (see reproduction scenario) The problem can be 'fixed' by adding a new rule in the AMS Role defining the permission for package DA, specifically for Company 0000. In that case the normal user is able to start the session as he should. Where did the defect occur? (Session code, etcetera) The problem occurs on the Bflow environment, while logged in as normal user. How must the defect be solved? The user should be able to start the session in company 1782 as defined in AMS Role JUNIOR_3B. _Test Procedure_ bflow regtests _Affected Executables_ bshell6.2 ------------------------------------------------------------------------ pset2020_3: # 83928 (BDUX81165): DF748303: msql map ODBC failover error codes to knowd bdb_errno codes Date: Thu, 03 Dec 2020 14:26:46 +0100 Created on: pset2020_3 Type: bugfix _Problem Description (Customer terms)_ msql: uncatched odbc errors during failover _Test Procedure_ none _Affected Executables_ msql_srv _Motive source_ InforXtreme:748303 ------------------------------------------------------------------------ pset2020_3: # 83890 (BDNT81102): An error occurred while determining what data to stage (file lib/publish_tables_ce01026 is corrupt). Date: Thu, 26 Nov 2020 13:10:26 +0100 Created on: pset2020_2 Type: bugfix _Problem Description (Customer terms)_ Errors in log 'An error occurred while determining what data to stage (file 'lib/publish_tables_ce01026' is corrupt)' _Workaround_ N/A _Test Procedure_ Tested on the reproduction environment provided by support, see defect for more information. _Affected Executables_ Bshell _Motive source_ InforXtreme:743416 ------------------------------------------------------------------------ ------------------------------------------------------------------------ pset2020_3: # 83851 (BDUX81045): Sessions start in company 0 Date: Thu, 19 Nov 2020 15:34:59 +0100 Created on: pset2020_3 Type: bugfix _Problem Description (Customer terms)_ Suddenly sessions where started in Company 0 _Workaround_ Session Compile would add the additional new compnr start field in a ttadv999 record. _Test Procedure_ regtest _Affected Executables_ bshell6.2 ------------------------------------------------------------------------ pset2020_3: # 83806 (BDUX81001): crash in get_debug_in_debug_mode_ext due to stack overflow Date: Wed, 11 Nov 2020 16:25:18 +0100 Created on: pset2020_4 Type: bugfix _Problem Description (Customer terms)_ Crash with debug objects in combination with long filenames and long local variables _Test Procedure_ RegTest _Affected Executables_ bshell6.2 ------------------------------------------------------------------------ pset2020_3: # 83769 (BDUX80938): Start in Company 0 property Sessions - Portingset part Date: Tue, 03 Nov 2020 17:47:53 +0100 Created on: pset2020_3 Type: enhancement _Problem Description (Customer terms)_ User AMS Companies: Exclude tools sessions that switch to company 0000. _Affected Executables_ bshell6.2 _Motive source_ JIRA:LND2-33320 ------------------------------------------------------------------------ pset2020_3: # 83751 (BDNT80812): Fatal error 215 thrown while removing a record in tccom0101m000. Date: Thu, 29 Oct 2020 15:29:29 +0100 Created on: pset2020_2 Type: bugfix _Problem Description (Customer terms)_ Trying to delete a employee in session tccom0101m000 fails with fatal error. _Test Procedure_ Tested on the reproduction environment provided by support, see defect for more information. _Affected Executables_ Bshell _Motive source_ InforXtreme:727189 ------------------------------------------------------------------------ pset2020_3: # 83743 (BDUX80914): Various 3GL debugger issues Date: Wed, 28 Oct 2020 16:34:31 +0100 Created on: pset2020_3 Type: bugfix _Problem Description (Customer terms)_ Various problems with the 3GL debugger _Test Procedure_ RegTests _Affected Executables_ bshell6.2 bic6.2 _Motive source_ TCS:800-237641 ------------------------------------------------------------------------ pset2020_3: # 83672 (BDUX80811): D742935: SQL Server driver: writing BLOB data trashes the query plan cache Date: Fri, 16 Oct 2020 15:18:26 +0200 Created on: pset2020_2 Type: bugfix _Problem Description (Customer terms)_ The SQL Server query plan cache is being trashed by writing BLOBs. This is typical behavior of BOD publishing. _Test Procedure_ On one table write BLOBs of different lengths. In SQL Server verify that they result in one statement text. _Affected Executables_ msql_srv _Motive source_ InforXtreme:742935 ------------------------------------------------------------------------ pset2020_3: # 83648 (BDNT80774): BSE Services framework Bshell started automatically on UNIX / LINUX being part of rc.start framework. Date: Wed, 14 Oct 2020 16:37:53 +0200 Created on: pset2020_2 Type: bugfix _Problem Description (Customer terms)_ Cannot start the BSE Services framework Bshell automatically on UNIX / LINUX _Workaround_ N/A _Test Procedure_ Tested with support on an intern support machine. _Motive source_ InforXtreme:735335 ------------------------------------------------------------------------ pset2020_3: # 83531 (BDUX80616): looping bshell when debugging Date: Tue, 22 Sep 2020 11:17:12 +0200 Created on: pset2020_3 Type: bugfix _Problem Description (Customer terms)_ Bshell loops during debugging _Test Procedure_ enable debugging for LN IU and start BW with a listening port _Affected Executables_ bshell6.2 ------------------------------------------------------------------------ pset2020_3: # 83495 (BDUX80554): Crash in refresh_local_function_symbols_for_debug_local Date: Tue, 15 Sep 2020 14:53:36 +0200 Created on: pset2020_3 Type: bugfix _Problem Description (Customer terms)_ Problems with debugging Problems with missing DD's _Affected Executables_ bshell6.2 ------------------------------------------------------------------------ pset2020_3: # 83468 (BDUX80523): PROFILE_TRAMPOLINE does not work correctly Date: Thu, 10 Sep 2020 08:51:40 +0200 Created on: pset2020_3 Type: bugfix _Problem Description (Customer terms)_ The initial_debug_options PROFILE_TRAMPOLINE=stat.info,mb is not working zipped bshell.gehermani.305526 exceeds the 8mb -. not attached. Where did the defect occur? (Session code, etcetera) nlbawappsdev2 PACKAGE_COMB=ce01sy01 Company 551 How can the defect be reproduced? (Description of the test actions, step by step, starting from the main session) set initial_debug_options. restart start ttfmafileman select folder tmp exit _Test Procedure_ RegTests and defect description _Affected Executables_ bshell6.2 _Motive source_ TCS:800-229195 ------------------------------------------------------------------------ pset2020_3: # 83328 (BDUX80420): Debugging in the Cloud: move local symbols to extended header Date: Wed, 19 Aug 2020 17:38:56 +0200 Created on: pset2020_2 Type: bugfix _Problem Description (Customer terms)_ Debugging in the Cloud: - move local symbol names to the extended object header - read local symbol names only during debugging and/or specific trace levels _Workaround_ Accept memory increase _Test Procedure_ RegTests added _Affected Executables_ bshell6.2 bic6.2 bic_info6.2 _Motive source_ JIRA:LND2-32510