List of changes for portingset: 6.1c.07.13 MaintBaanIVc: # 32970 (BDNT25051): Not able to use BwConfig and BwPrint as user Administrator Date: Tue, 24 Oct 2006 15:18:31 +0200 (CEST) Created on: MaintBaanIVc Type: bugfix Problem Description (Customer terms) BwConfig and BwPrint cannot be started as user Administrator due to an extra check on long usernames. When the username is longer than 8 characters an application event is logged and the application will not start. Workaround Use a username with a maximum of 8 characters Test Procedure Right click on bwprint.exe. Choose 'Run as...'. Choose for user Administrator and enter the correct password. When bwprint does not start look in the eventviewer and check the events for bwprint. Same goes for BW.exe. Affected Executables BwConfig.dll BwPrint.exe Motive source SDIS:TECH-00000-01583 MaintBaanIVc: # 32942 (BDUX25045): JVMI: missing dir in LD_LIBRARY_PATH Date: Mon, 23 Oct 2006 09:19:40 +0200 (CEST) Created on: MaintBaanIVc Type: bugfix Problem Description (Customer terms) bshell hangs when JRE 1.3 is used on DEC/OSF Workaround add to $BSE/lib/bse_vars: LD_LIBRARY_PATH=/lib/alpha:/lib/alpha/classic:/lib/alpha/native_threads where is the directory of the installed JRE most times this is /usr/opt/java131 Test Procedure OW on DEC/OSF with JRE 1.3 Affected Executables bshell bjvmi.jar MaintBaanIVc: # 32935 (BDNT25037): baanman cannot start as user Administrator Date: Fri, 20 Oct 2006 16:12:53 +0200 (CEST) Created on: MaintBaanIVc Type: bugfix Problem Description (Customer terms) It is not possible to run MMC as user Administrator: c:\winnt\baan\bin\baammmc nor BaanNT manager by user administrator. Workaround Use the 'Run as..' feature in Windows. Start the BaanNT Manager as a real Baan user. Affected Executables baanman.dll Motive source SDIS:TECH-00000-01517 MaintBaanIVc: # 32790 (BDNT24865): wrong message in bdbreconfig Date: Fri, 13 Oct 2006 09:29:42 +0200 (CEST) Created on: MaintBaanIVc Type: bugfix Problem Description (Customer terms) With bdbreconfig -c following message is shown when a new index is added. Message : Reconfiguration without use of pre/post dump Key modification necessary However during bdbreconfig pre/post is done. Workaround n/a Test Procedure run bdbreconfig -c when a new index was added Affected Executables bdbreconfig6.1 MaintBaanIVc: # 32750 (BDUX24863): use javac 1.4 Date: Tue, 10 Oct 2006 15:36:36 +0200 (CEST) Created on: MaintBaanIVc Type: bugfix Problem Description (Customer terms) On HPUX the default SHLIB_PATH points to jre1.2, which is not supported anymore Test Procedure OW regression test Affected Executables bshell MaintBaanIVc: # 32741 (BDNT24852): Default optimization changed in msql_storage Date: Tue, 10 Oct 2006 12:31:14 +0200 (CEST) Created on: MaintBaanIVc Type: bugfix Problem Description (Customer terms) New installer will configure Baan IVc for level 2 database mode. The msql_storage file needs to be created with 0400 optimization for best performance. Currently 011 is set. This was best for level 1. Workaround n/a Test Procedure Install Baan IVc with new installer. Affected Executables msql7_adm.exe MaintBaanIVc: # 32599 (BDUX24743): JVMI: core dump within debug logging Date: Tue, 3 Oct 2006 11:59:42 +0200 (CEST) Created on: MaintBaanIVc Type: bugfix Problem Description (Customer terms) bshell crashes on Solaris when JVMI logging is enabled with -dbgjvmi Test Procedure start tmboaserver 2.7 on Solaris with enabled logging Affected Executables bshell libjvm2bvm MaintBaanIVc: # 32520 (FRUX24668): iSeries: vertex api Date: Thu, 28 Sep 2006 08:40:02 +0200 (CEST) Created on: MaintCorelli Type: bugfix Problem Description (Customer terms) Error in session tccom4530m000 When Jurisdiction is executed. Workaround the workaround solves part of the problem: add the VERTEX library to the user part of the system liblist Test Procedure see problem description Affected Executables api6.2 MaintBaanIVc: # 32478 (BDUX24634): SHM improved logging Date: Tue, 26 Sep 2006 10:31:32 +0200 (CEST) Created on: MaintCage Type: porting specific change Problem Description (Customer terms) Better error message if no SHM available. MaintBaanIVc: # 32224 (BDUX23966): Start session by code on commandline not allowed if no permission Date: Fri, 8 Sep 2006 12:28:59 +0200 (CEST) Created on: MaintBaanIVc Type: bugfix Problem Description (Customer terms) A security leak is present in the authorization of starting up sessions. When a user does not have the rights to start a session by code he is still able to start a session by adding the session name on the command line after ba6.1 or by adding the session name to the configuration when using BW. The way of authorizing user in BaanIV is quit complicatied, so also the use of user specific menus was introduced. The user only had the sessions in his menu where he was authorized to and was not allowed to start a session by entering the session code in the 'file' menu. But by typing the session code on the command line he was able to start the session anyway. Workaround A workaround could be to enter a complete authorization system for all users using the functionality present in BaanIV. This is a painstaking task. Test Procedure 1. Create a normal user 2. Disallow to user to start sessions by code 3. Enter the new resource in the $BSE/lib/defaults/all file: check_startup_perm:1 4. Run Baan by typing 'ba6.1 [session code]' or 4. Add a session code to the configuration in BW and start Baan The message popping up in the message windows should be: 'Error: No permission to start session [session code] by code' the check the exceptions create the file 'startses' in $BSE/lib and enter a specific session code, e.g. ttaad4500. Every sessioncode should be on a seperate line. When typeing 'ba6.1 ttaad4500' on the command line you should be able to run the session, if you have the privilege according to the authorization system within BaanIV itself. Affected Executables bshell Motive source SDIS:TECH-00000-00719 MaintBaanIVc: # 32181 (BDUX24375): Added message queue termination in api.c Date: Thu, 7 Sep 2006 09:47:46 +0200 (CEST) Created on: MaintCorelli Type: bugfix Problem Description (Customer terms) A few months ago we were having api issues of the processes hanging on our servers. A reboot of each application server was needed in order to clean up these api hung processes. We received a new version of api (7.1d.13) in order to fix this issue. Since the new version went into production, we have not had to reboot the application servers. Workaround Reboot Affected Executables Tax libraries Motive source SDIS:TECH-00000-01332 MaintBaanIVc: # 32118 (BDUX24299): TCS 800-150128 (std_gen: errors are reported twice) Date: Thu, 31 Aug 2006 16:55:13 +0200 (CEST) Created on: MaintBaanIVc Type: bugfix Problem Description (Customer terms) Not all std_gen compile errors were found. Some seemed to be reported twice. Workaround Not applicable Test Procedure script: field.xyz: when.field.changes script: display.all before.program: long y script: long x long y string z(10) z = x + y before.program: display.all() script: declaration: long a group.1: after.choice: Affected Executables std_gen6.1 Motive source TCS:800-150128 MaintBaanIVc: # 31945 (BDUX24164): SHM attach may fail on SUN Date: Thu, 24 Aug 2006 10:03:57 +0200 (CEST) Created on: MaintBaanIVc Type: bugfix Problem Description (Customer terms) SHM was not always accessible for database driver and/or bshell on SUN Test Procedure Run shmmanager, and then bshell, or bsql or qptool. Check that bsql/qptool/bshell can attach to SHM. Affected Executables shmmanager6.x MaintBaanIVc: # 31925 (BDUX24135): Backported SHM changes Date: Tue, 22 Aug 2006 17:47:52 +0200 (CEST) Created on: MaintBaanIVc Type: porting specific change Problem Description (Customer terms) Eliminate the need to run shm_values6.x if portingset was upgraded or otherwise. The file $BSE/lib/shm_param needed to be too often, and is now obsolete. The new file is $BSE/lib/shm_config which need only to be edited in case if the shared memory manager can't determine a SHM attach address Affected Executables All executables using SHM (bshell, database drivers) MaintBaanIVc: # 31840 (BDUX24009): Only root login allowed Date: Wed, 16 Aug 2006 09:44:37 +0200 (CEST) Created on: MaintCorelli Type: bugfix Problem Description (Customer terms) Be sure that USER env var is NOT set when blogind/rexecd.exe has been started, otherwise all users cannot login. Workaround unset USER before starting daemon. Test Procedure Try to login with blgond protocol and verify that you don't get authorization failures. MaintBaanIVc: # 31789 (BDUX23985): Always interpret idxopt value in /baan/b61a/bse/lib//_driver_param in octal Date: Mon, 14 Aug 2006 11:56:40 +0200 (CEST) Created on: DevCage Type: bugfix Problem Description (Customer terms) Performance problems at several customer sites on queries that do an index scan. Workaround Be aware that the idxopt value in $BSE/lib//_driver_param file needs a leading 0, so specify "014" instead of "14". Test Procedure Test for oracle driver (for others you can setup compareable tests, but you have the figure out the right values) Specify idxopt value "14" im the ora_driver_param file. DBSLOG=01400 bsql6.2 -c 0 -q "SELECT tfgld482.* FROM tfgld482 WHERE tfgld482._index2 < { 1,'x','y' } ORDER BY tfgld482._index2 desc as set with 1 rows" Note that this test will generate error 506 as the tf table does not exist in company 0, but that does not matter here. The generate Oracle-SQL in the dbs.log file will use the FILTER technique when using the old porting set, and the ITERATIVE approach when using the new one. Affected Executables all database drivers Motive source Spin off of Inquiries 348821 and 338108 MaintBaanIVc: # 31781 (BDUX23976): iSeries: connect fails Date: Fri, 11 Aug 2006 17:05:14 +0200 (CEST) Created on: MaintCorelli Type: bugfix Problem Description (Customer terms) bshell doesn't reply to ASM server on iSeries Test Procedure OW regressiontest Affected Executables bshell Motive source SDIS:TECH-00000-01159 MaintBaanIVc: # 31690 (BDUX23857): Core dump in rptcvt6.1 Date: Tue, 1 Aug 2006 09:53:05 +0200 (CEST) Created on: MaintBaanIVc Type: bugfix Problem Description (Customer terms) Core dump in rptcvt6.1 on SUN OS. Workaround n/a Test Procedure Execute following command with an input xml file. rptcvt6.1 -i input.xml -of om out.xml -e err Affected Executables rptcvt6.1 MaintBaanIVc: # 31655 (BDNT23836): Missing fix in 4c. Failed to start SHM Date: Wed, 26 Jul 2006 16:23:47 +0200 (CEST) Created on: MaintBaanIVc Type: bugfix Problem Description (Customer terms) SHM did not start: got bad user message on account system. MaintBaanIVc: # 31644 (BDNT23814): Error in bdbpre Date: Wed, 26 Jul 2006 10:55:51 +0200 (CEST) Created on: MaintBaanIVc Type: bugfix Problem Description (Customer terms) File becomes to big when we dump table tfgld410. Flush error in log.bdbpre, last record in first file not correctly written. Workaround use bdbpre6.x with -M option. Use a value less 2 GByte. Test Procedure dump a large table tfgld410 table with sesperator. We used : bdbpre6.1-N tfgld410 -t"|" -o /tmp/dump -C 300 Affected Executables bdbpre6.x Total number of changIDs displayed: 20