List of changes for portingset: 9.5i ------------------------------------------------------------------------ pset2025_3: # 91386 (BDUX90063): LNW-19553: Update rest service header key. Date: Wed, 12 Nov 2025 08:29:23 +0100 Created on: pset2025_2 Type: bugfix _Problem Description (Customer terms)_ PIs defined in REST Service Management ttmtm6620m000 can be called by any company. _Affected Executables_ bshell _Motive source_ JIRA:LNW-19553 ------------------------------------------------------------------------ pset2025_3: # 91309 (BDUX90070): LNW-23075: libcurl functon was giving bad argument, buffer size to small Date: Tue, 21 Oct 2025 14:38:01 +0200 Created on: pset2025_3 Type: bugfix _Problem Description (Customer terms)_ Users attempting to refresh or retrieve a new access token by clicking the Get new access token button within the OAuth 2.0 parameter sets. Session are encountering the following error message: A libcurl function was gien a bad argument _Affected Executables_ bshell _Motive source_ CustomDefect:LNW-23075 ------------------------------------------------------------------------ pset2025_3: # 91272 (BDUX89772): LNW-18690: Remove invalid dd file. Date: Thu, 09 Oct 2025 13:12:54 +0200 Created on: pset2025_2 Type: bugfix _Problem Description (Customer terms)_ bdbpost importing a bigdump should not create missing runtime table DD files as it could cause "error 513" _Workaround_ N/A _Test Procedure_ Import new dd with corrupted data. After the error, reimport the same dd after fixing the corruption. _Affected Executables_ bdbpost _Motive source_ JIRA:LNW-18690 ------------------------------------------------------------------------ pset2025_3: # 91253 (BDUX90017): DBS log Plan enablement issue due to limited connection string buffer. Date: Mon, 06 Oct 2025 16:26:47 +0200 Created on: pset2025_2 Type: bugfix _Problem Description (Customer terms)_ Bshell fails to start if -set DBSLOG=04 is enabled to get the execution plan. _Workaround_ N/A _Test Procedure_ Sporadic issue - Starting bshell with DBSLOG=04 enabled reproduces the scenario. _Affected Executables_ bshell ------------------------------------------------------------------------ pset2025_3: # 91179 (BDUX89937): LNW-15728: Deatiled logging for audit error 254. Date: Thu, 18 Sep 2025 10:57:52 +0200 Created on: pset2025_1 Type: bugfix _Problem Description (Customer terms)_ When an audit error 254 occurs the error message presented to the user is missing the affected audit file. _Workaround_ N/A _Test Procedure_ Regression tests. _Affected Executables_ bshell _Motive source_ JIRA:LNW-15728 ------------------------------------------------------------------------ pset2025_3: # 91163 (BDNT89924): Patch for assuring to acknowledge newkey in libssh2. Date: Mon, 15 Sep 2025 11:41:56 +0200 Created on: pset2025_1 Type: bugfix _Problem Description (Customer terms)_ Sporadic error during the installation of LN for initiating secure communication to remote installation target. _Workaround_ Using version 1.10 is possible for SUSE and RedHat versions up to 8. _Test Procedure_ Due to the sporadic nature if the issue, installation process including SFTP and database functions done for both SUSE and RedHat 9, fourty times for each. _Affected Executables_ All executables using libssh2. ------------------------------------------------------------------------ pset2025_3: # 91065 (BDUX89794): Too many HTTP headers are hidden in the bshell trace file. Date: Wed, 06 Aug 2025 16:32:12 +0200 Created on: pset2025_2 Type: bugfix _Problem Description (Customer terms)_ What is the defect? (Description) Trace files created for HTTP requests contain the HTTP request including the headers at the top of the file, which is great! However a lot of important HTTP headers have a value . Also, certain API consumers, like Flex, will add their own HTTP headers, which also get the value . _Test Procedure_ RegTest _Affected Executables_ bshell6.2 _Motive source_ TCS:800-267147 ------------------------------------------------------------------------ pset2025_3: # 90971 (BDUX89675): LNW-20726: umask different when starting manually or by blogind Date: Fri, 11 Jul 2025 14:27:31 +0200 Created on: pset2025_2 Type: bugfix _Problem Description (Customer terms)_ it turned out that files being created by jobs, which are started using the job scheduler service being part of BSE service framework all get the unexpected permissions 640. This is wrong as any files being created by a user bshell started regularly gets expected permissions 660 _Workaround_ set umask of the user before starting the framework _Test Procedure_ tested on a support environment, remove comment from the files. _Affected Executables_ rc.start, rc.start_bseservice and rc.stop _Motive source_ CustomDefect:LNW-20726 ------------------------------------------------------------------------ pset2025_3: # 90931 (BDUX89621): some problem with adding - largecalls Date: Thu, 03 Jul 2025 13:16:53 +0200 Created on: pset2025_2 Type: bugfix _Problem Description (Customer terms)_ A main object using -largecalls linking against a dll which as varargs will display all kind of errors about illegal arguments _Test Procedure_ RegTest _Affected Executables_ bic6.2 ------------------------------------------------------------------------