Release notes for portingset: 7.6a.02 MaintMahler: # 25740 (BDUX18327): Increase of pty usage after BDUX17260 Date: Wed, 25 May 2005 10:33:23 +0200 (CEST) Created on: MaintBaanIVc Type: bugfix Problem Description (Customer terms) After installing portingset 6.1c.07.07 the following error was reported: Errno 24 (The process file table is full) bdb_errno 0 Failed to open pty pair. After increasing the number of pty's from 256 to 512 the problem was solved. It looks like the pty usage increased after installing this portingset. Workaround Increase the number of available pty's on system level. E.g. double the number of available pty's. Test Procedure Before logging into Baan, set the following in to the Command field of Bw Configuration: -- -dbgpty -logfile ptytrace -keeplog Log in Baan, and from the menubar select File->Run Program. Fill in: ksh, and check "Run External Program". Press OK. Now a terminal emulator is opened. Type exit and leave the terminal emulator again, and log out Baan. Afterwards check the ptytrace file, it should contain: pty: opened master /dev/ptc fd 9 pty: opened slave /dev/pts/2 fd 10 PTY STRUCTURE PTY: proc = ottstpvtemul_r PTY: in = 12 PTY: out = 9 PTY: mfd = 9 PTY: pfd = 12 PTY: rpid = 0 PTY: spid = 32416 PTY: flags PTY: no input for process ottstpvtemul_r pty: opend slave /dev/pts/2 fd 13 So 1 master pty should be opened. In a wrong situation you will see 10 times "pty: opened master /dev/ptc fd ..". Affected Executables bshell Motive source DF:156103 MaintMahler: # 25640 (BDUX18111): Support long OS usernames (merge from 4 Corelli projects) Date: Wed, 18 May 2005 14:34:08 +0200 (CEST) Created on: MaintMahler Type: bugfix Problem Description (Customer terms) Support long OS user names on SSA ERP LN. Workaround n/a Test Procedure See BDUX16755 Affected Executables all Motive source DF:217777 MaintMahler: # 25616 (BDUX18229): bdb_validate: incorrect handling of violation on array column Date: Fri, 13 May 2005 15:50:49 +0200 (CEST) Created on: MaintMahler Type: bugfix Problem Description (Customer terms) If a domain constraint on an array column is violated, bdbvalidate prints the column names and values of all columns that have some domain constraint. It does not print the primary key of the offending row. Test Procedure Find or create an array value that violates a domain constraint and execute bdbvalidate with the -R option. Observe that the report (-R option) shows the primary key of the offending row: dbtst120000 LECH 205 Error: Column dbtst120.phoneno, Domain s20p: LECH dbtst120000 LECH 205 _index1 = { 70 }, phoneno = ['19520 ','22171 ','32503 '] It should not be as follows (no primary key, but all columns and values) dbtst120000 LECH 205 Error: Column dbtst120.phoneno, Domain s20p: LECH dbtst120000 LECH 205 bonus = 700.000000, edlevel = 16, firstnme = 'EVA ', lastname = 'PULASKI ', phoneno = ['19520 ','22171 ','32503 '], salary = 36170.000000 Affected Executables bdbvalidate Motive source DF:154722 MaintMahler: # 25584 (BDUX18200): Merged project BDUX16280 (Avoid MB split in text columns) to ERP LN Date: Wed, 11 May 2005 12:14:18 +0200 (CEST) Created on: MaintMahler Type: bugfix Problem Description (Customer terms) On Oracle >= 9.2 and a MultiByte installation the fields tttxt010.text and some other fields of type BDB_STRING that contain binary data might look corrupted. Workaround NA Test Procedure NA Affected Executables ora8_srv msql_srv MaintMahler: # 25581 (BDNT18128): Api messages invalid, error code 1 Date: Wed, 11 May 2005 11:34:57 +0200 (CEST) Created on: MaintMahler Type: bugfix Problem Description (Customer terms) This project is merged from projects BDUX16512 (DF222576) and BDNT17986 (DF224800) Defect 222576: Having a significant number of hung api's and message queues. Defect 224800: API message was invalid. Error code 0. API request failed. Message was not sent. Error code 1. Workaround N/A Test Procedure After rebuilding the api (api6.2) and installing on a system with Third party tax enabled, test the following: 1) API still performs as before 2) kill off sh_server and verify that API goes away neatly and removes queues; it should also log messages to $BSE/log/log.api. 3) remove queues while the api is running and verify that it goes away neatly and removes queues (if not already), and logs message to $BSE/log/log.api Affected Executables api.exe The libraries (libtvtx.a, libtavp.a, libtaxb.a) can be used to build the apix.x which will be run from $BSE/bin. Motive source DF:222576 DF:224800 MaintMahler: # 25535 (BDUX18161): Removed some double line (defines) in shm.h Date: Wed, 4 May 2005 16:21:47 +0200 (CEST) Created on: MaintMahler Type: bugfix Problem Description (Customer terms) Because of a merge from another project some source lines are duplicated. Workaround N/A Test Procedure N/A Affected Executables shmvalues6.x shmmanager6.x MaintMahler: # 25520 (BDNT18154): Check during install or uninstall if com_baan_bclm.jar is locked Date: Wed, 4 May 2005 11:31:48 +0200 (CEST) Created on: MaintMahler Type: porting specific change Problem Description (Customer terms) Upgrade fails during file copy giving a mix of file versions Workaround Stop all SLM components (as specified) before performing an upgrade Test Procedure Force locking of com_baan_bclm.jar and do an upgrade Affected Executables SLM installer MaintMahler: # 25516 (BDUX18137): Enhance error messages Date: Tue, 3 May 2005 16:15:03 +0200 (CEST) Created on: DevDvorak Type: bugfix Problem Description (Customer terms) String demotion when concating strings into a tmp string: string desc80(80) mb string shortcut(10) long length length = len(desc80 & shortcut) results in the length of bytes of the result string while number of characters is expected. the temporary string created by the concat disregards the fact that one of the strings is a multibyte string Workaround in the example add: string temp.mb(90) mb change: temp.mb = desc80 & shortcut length = len(temp.mb) Affected Executables bshell6.2 MaintMahler: # 25509 (BDUX18001): Informix: Error -710 occured Date: Tue, 3 May 2005 16:13:37 +0200 (CEST) Created on: MaintMahler Type: bugfix Problem Description (Customer terms) Informix error -710 appears in log.informix and stops the application. The problem was found during installation of Gemini with SP1 and regression tests. Workaround n/a Test Procedure Ensure test table exists before running following gcommand script. #1 ddcts512 REQUAL 0 -i -E0 -ENOREC #2 ddcts512 TDRTBL 0 #2 ddcts512 DCOM 0 #1 ddcts512 REQUAL 0 -i -ENO_TABLE With the old driver the last statement was failed with error -1710. Affected Executables inf_srv6.x MaintMahler: # 25506 (BDUX18049): Long passwords on HP UX trusted security. Date: Tue, 3 May 2005 11:36:23 +0200 (CEST) Created on: MaintBaanIVc Type: bugfix Problem Description (Customer terms) Using HP-UX OS in "Trusted Security" mode, and using BaanLogin protocol to log in Baan: When using passwords bigger than 8 characters, you cannot log in Baan. An Authorization Failure error is reported. Workaround Do not use passwords longer then 8 characters. Test Procedure You need to have a HP-UX system, running in "Trusted Security" mode. When having such system, running Baan, set the user-password to a password longer then 8 characters. (not longer then 25 characters). You should be able to log in Baan using the Baan Login protocol when using password longer then 8 characters. Affected Executables blogind6.x Motive source DF:155293 MaintMahler: # 25497 (BDUX18136): Unexpected locks on AIX platforms. Date: Mon, 2 May 2005 16:43:11 +0200 (CEST) Created on: MaintMahler Type: bugfix Problem Description (Customer terms) Unexpected database locks are occured on AIX platforms. This problem was found during a Gemini installation. Workaround n/a Test Procedure Test was done with a complete Gemini installation on AIX. No easy test is available. Affected Executables inf_srv6.x MaintMahler: # 25473 (BDUX17736): BRQ000661: Optionally output errors/warnings in XML format Date: Thu, 28 Apr 2005 16:01:33 +0200 (CEST) Created on: MaintMahler Type: enhancement Problem Description (Customer terms) For 4GL Studio, bic should be able to deliver the compilation result in XML format. Workaround n/a Test Procedure See problem description. Affected Executables bic Motive source BRD:BRQ000661 MaintMahler: # 25451 (BDNT18089): Extra feature in imake.rules for SLM Date: Wed, 27 Apr 2005 16:20:11 +0200 (CEST) Created on: MaintMahler Type: enhancement Problem Description (Customer terms) AS/400 build SLM not working Test Procedure Check build procedure Affected Executables NA MaintMahler: # 25437 (BDNT18076): Check for locked files during SLM reinstall Date: Tue, 26 Apr 2005 16:19:57 +0200 (CEST) Created on: MaintMahler Type: enhancement Problem Description (Customer terms) Reinstall of SLM fails when an (old) SLM server is still running Workaround Stop SLM server and/or adopting clients before reinstall Test Procedure Do SLM reinstall (same installation directory) while SLM server is running Affected Executables SLM installer MaintMahler: # 25430 (BDNT18008): Winstation test based on 7.1d.05 Date: Tue, 26 Apr 2005 11:55:18 +0200 (CEST) Created on: MaintCorelli Type: porting specific change Problem Description (Customer terms) Running a lot of users on NT might result in not able to start sort.exe or sh_server.exe processes due to some Windows limitation. Special registry tuning is needed to over come this. See solution 121503 for more information. This solution might still not acceptable for all customers because the registry settings might conflict with requirements of other applicatons. Workaround See solution 121503 Test Procedure Take a windows system, set the third argument of SharedSection (See the solution) to a low value (e.g. 256 of less). Disable combo-mode in tabledef and try to a number of bshells (e.g. the baan benchmark) One will notice that 30 users will run fine, but running 40 users will result in errors on the console due to not able to start sort.exe. Set the resource 'no_ipc_msg_window:1' in $BSE/lib/defaults/all and notice that one can at least run upto 400 users on the same system. Affected Executables ntbshell.exe, *_srv.exe, bshcmd.exe MaintMahler: # 25418 (BDNT17769): Staging Wizard: upgrade to JDK1.5.0.02 Date: Mon, 25 Apr 2005 14:50:21 +0200 (CEST) Created on: MaintMahler Type: bugfix Problem Description (Customer terms) Staging Wizard has problems displaying Japanese directory names in the File Dialog correctly. Motive source TCS:800-143155 MaintMahler: # 25416 (BDUX18055): Remove useless licensing logging from the bshell log. Date: Mon, 25 Apr 2005 14:31:57 +0200 (CEST) Created on: MaintMahler Type: bugfix Problem Description (Customer terms) During closure of the bshell in some circumstances the bshell could log that some ProductID could not be found or some license could not be released. Since these messages where false, they are no longer logged. Test Procedure Check log file. Affected Executables bschell[nt][6.x][.exe] Motive source DF:224228 MaintMahler: # 25376 (BDNT18020): Add new axbarcode.lic file Date: Wed, 20 Apr 2005 16:22:15 +0200 (CEST) Created on: MaintMahler Type: bugfix Problem Description (Customer terms) BwPrint: The barcode functionality is not enabled. (Menu options regarding Barcode's are grayed out) Workaround Create the following registry setting: HKLM\SOFTWARE\dLSoft\abc key (type REG_SZ) "Current" value data: "version 30" Test Procedure Have the new bwprint, axbarcode.ocx and axbarcode.lic installed. Start BwPrint. From the Help select Barcode Test. The Barcode Test should show the barcode images. Affected Executables Bwprint.exe Motive source DF:224085 MaintMahler: # 25370 (BDNT17416): Determination of mac address via Netbios not reliable. Date: Wed, 20 Apr 2005 13:45:55 +0200 (CEST) Created on: MaintBaanIVc Type: bugfix Problem Description (Customer terms) BaanIVc installed and validated successfully. But after restart of the Windows2000 server, the Baan Licensing service does not start anymore. The following error is logged in the Windows Event Log: Can’t run - Please brand your software. Also after applying use_enhanced_hostid:1 (refer to solution 131733) and re-validating Baan, the same problem comes back after a restart of the system. Workaround No Test Procedure It is not possible to define a test procedure for this problem. The problem seems to be related to the number of times networkadapters/protocols/services were installed/uninstalled at a Windows platform. Affected Executables licd.exe, licmon.exe, brand.exe, hostid.exe Motive source DF:155502 MaintMahler: # 25358 (BDNT17998): Add uninstall checks Date: Wed, 20 Apr 2005 10:26:46 +0200 (CEST) Created on: MaintMahler Type: enhancement Problem Description (Customer terms) Uninstall can fail without error Test Procedure Perform uninstall while SLM server is still running Affected Executables SLM installation kit MaintMahler: # 25318 (BDUX17937): expression range problem with float domains Date: Thu, 14 Apr 2005 13:21:40 +0200 (CEST) Created on: DevDvorak Type: bugfix Problem Description (Customer terms) Field "Planning Factor" wrong calculation with decimals, Error 205 Test Procedure function main() { double aa double bb double cc long e.id long aa.e long bb.e long cc.e e.id = expr.compile("$$ in [0.01,0.99]") aa = 0.01 bb = 0.0099999997764825821 cc = 0.99 | | internally ranges are compared with a tolerance of 0.0000009 | aa.e = l.expr(e.id, aa) | returns 1 bb.e = l.expr(e.id, bb) | used to return 0 returns 1 now cc.e = l.expr(e.id, cc) | returns 1 aa = 0.009 aa.e = l.expr(e.id, aa) | returns 0 aa = 0.0099 aa.e = l.expr(e.id, aa) | returns 0 aa = 0.00999 aa.e = l.expr(e.id, aa) | returns 0 aa = 0.009999 aa.e = l.expr(e.id, aa) | returns 0 expr.free(e.id) } Affected Executables bshell6.2, db drivers Motive source DF153060 MaintMahler: # 25311 (BDUX17898): NQP: Improve performance of inner join in Ansi mode Date: Wed, 13 Apr 2005 16:09:05 +0200 (CEST) Created on: MaintMahler Type: bugfix Problem Description (Customer terms) A SQL statement containing an inner join performs badly if it is executed with the OpenWorld ODBC connector. Test Procedure Execute a query like the following with DBSLOG=400, for example using bsql with the -p16 option (prepare in ANSI mode): select * from dbtst190 a inner join dbtst120 b on a.empno = b.empno and a.company_nr = b.company_nr where a.company_nr in (0,1) and a.empno in (10,100000) Observe in the dbs.log file that both tables (and the join) are handled in a single query to the RDBMS. Affected Executables jbdb library all database driver MaintMahler: # 25288 (BDUX17921): add override_java_sigusr2 resource Date: Tue, 12 Apr 2005 16:22:32 +0200 (CEST) Created on: MaintCorelli Type: bugfix Problem Description (Customer terms) On Linux now and then the bshell hangs or a connection is broken after tmboaserver is started. Test Procedure start tmboaserver it succeeded already most of the times without this fix MaintMahler: # 25264 (BDNT17890): Sort: extra modification BDNT17786 Date: Mon, 11 Apr 2005 12:26:26 +0200 (CEST) Created on: MaintCorelli Type: bugfix Problem Description (Customer terms) Refer to project BDNT17786 Workaround Not applicable. Test Procedure Refer to BDNT17786 Affected Executables sort.exe Motive source DF:224137 MaintMahler: # 25250 (BDUX17689): 4GL Studio: load .dbg object version if available Date: Fri, 8 Apr 2005 16:47:52 +0200 (CEST) Created on: MaintMahler Type: enhancement Problem Description (Customer terms) BRQ000661: A function must be added that switches to 'debug mode', causing ".dbg" versions (which are stored in the same directory as the normal objects) to be loaded instead of the normal objects. This mode affects all processes that will be started from the current process. Workaround N/A Test Procedure See problem description. Affected Executables bshell Motive source BRD:BRQ000661 MaintMahler: # 25237 (BDNT17869): Solve msi build problem after BDNT17444 Date: Fri, 8 Apr 2005 12:00:52 +0200 (CEST) Created on: MaintMahler Type: bugfix Problem Description (Customer terms) After project BDNT17444 the msi build failed because the file axbarcode.lic could not be found anymore. Workaround Not applicable Test Procedure Make a msi build. It should not complain about axbarcode.lic anymore and built successfully. Affected Executables Baan ERP Client.ism Motive source DF:224085 MaintMahler: # 25227 (BDNT17860): BwPrint: Update of barcode control Date: Fri, 8 Apr 2005 10:38:10 +0200 (CEST) Created on: MaintMahler Type: bugfix Problem Description (Customer terms) Check the barcode output for Code39 and Extended Code39 with a barcode reader. The "-" in the extended Code39 is being represented as a "/M" character. The "-" in the extended Code39 should be represented as a "-" character. Workaround No workaround Test Procedure Tested by the customer, by scanning the Extended Code39 with "-" character. Affected Executables bwprint.exe Motive source DF:224085 MaintMahler: # 25200 (BDNT17786): Sort: incorrect name of sort files Date: Wed, 6 Apr 2005 11:33:54 +0200 (CEST) Created on: MaintCorelli Type: bugfix Problem Description (Customer terms) About 2 weeks ago started receiving the Sort Error 6 "No more files can be created in this moment" when running various reports in Baan. The tf module is of the most concern, because when printed out checks and received the error mentioned above, the checks came out in a Supplier # order, rather than Supplier Name alphabetical order and it took a lot longer to match them up to invoices, sorted in alphabetical order. Running on Windows 2000 (SP4) Workaround There is no really good workaround. Rebooting the server once a day might prevent the problem to happen. Test Procedure Problem is specific for Windows os, because Windows does not allow characters like "?" and ">" in the file name. So you need to test this on a Windows os. Further, you can only test this fix when you are sure that the pid of sort.exe consist of 6 digits or more. E.g. 150184. This happens only when you'r windows system is running for a longer time, and pid's becomes larger. If you have a pid of 6 digits (or more), you can run for example session ttadv4450m000 (Print Messages) to test. At "Sort by" select for example "Pack/VRC/Lang/Message" and at Package (From/To) select for example tc/tf. Now when running this session sort.exe will be called in the background and used to do the sorting. Sort should not generate error 6 "No more files can be created in this moment". Affected Executables sort.exe Motive source DF:224137 MaintMahler: # 25195 (BDNT17790): Job Daemon cannot be started Date: Wed, 6 Apr 2005 11:32:56 +0200 (CEST) Created on: MaintCorelli Type: bugfix Problem Description (Customer terms) Baan Job Deamon service couldn't be started anymore after 7.1d.08 installation Workaround Use the jobd.exe from the previous portingset (7.1d.07) Test Procedure Start the job daemon on windows, check the logging event viewer. Affected Executables jobd.exe Motive source DF:154634 MaintMahler: # 25138 (BDUX17540): NQP: support generic value expressions in set function specification Date: Fri, 1 Apr 2005 13:12:46 +0200 (CEST) Created on: MaintMahler Type: enhancement Problem Description (Customer terms) The Baan SQL language lacks support of generic value expressions in set function specifications (aggregates). It supports simple column references, but nothing else. For example, the following is not allowed: select avg( price * amount ) from orders For the Cognos ReportNet integration such support is required. Test Procedure Execute queries such as the following and observe that the result is correct. select avg( salary + bonus ) from dbtst120 group by edlevel Affected Executables bshell bdb library jbdb library bsql all database driver MaintMahler: # 25097 (BDUX17729): Overflow format error when printing to Windows printer on Linux Date: Wed, 30 Mar 2005 11:45:36 +0200 (CEST) Created on: MaintBaanIVc Type: bugfix Problem Description (Customer terms) When printing any report using a "Windows Printer" device you always got error "Overflow format='9999' 'value='xxxxxxxxxx' where 'xxxxxxxxxx' is a random number. This is only happening om Linux platforms. Workaround N/A Test Procedure On a Linux environment print any report to a windowsprinter. Use 'Print Preview'. A BW message will popup with an overflow error message. This fix will prevent the error. Affected Executables bshell6.x Motive source DF:154343 MaintMahler: # 25091 (BDUX17698): Shmmanager do not allow hash signs in shm_param file Date: Wed, 30 Mar 2005 08:32:19 +0200 (CEST) Created on: MaintCorelli Type: bugfix Problem Description (Customer terms) Shmmanager do not start on Linux Motive source TCS:800-146596 MaintMahler: # 25084 (BDUX17728): Page break does not trigger footer and header layout Date: Tue, 29 Mar 2005 15:37:00 +0200 (CEST) Created on: MaintMahler Type: bugfix Problem Description (Customer terms) Page break does not trigger footer and header layout's. Workaround No Test Procedure Refer to BDUX17716 Affected Executables repgen6.1 Motive source DF:154276 MaintMahler: # 25077 (BDUX17452): ARM library not loaded on AIX Date: Tue, 29 Mar 2005 10:15:59 +0200 (CEST) Created on: MaintCorelli Type: bugfix Problem Description (Customer terms) The ARM shared library is not loaded on AIX systems. Workaround Specify environment variable BAAN_ARM_LIB and specify the member module of the archive e.g. BAAN_ARM_LIB=libarm!shr Test Procedure Check if the library (archive) libarm.a is present on the server. In most cases it is located in /use/lib. Specify environment variable BAAN_ART_ENABLE, set it to 1 (BAAN_ART_ENABLE=1). Run Baan en check the logging of the bshell. If an error 8 is logged the libarm.a file is not of the correct type. Affected Executables bshell6.x Motive source DF:224091 MaintMahler: # 25041 (BDNT17648): Cannot login to Baan when PATH is too long Date: Wed, 23 Mar 2005 15:07:49 +0100 (CET) Created on: MaintCorelli Type: bugfix Problem Description (Customer terms) The system environment variable PATH became too long for Baan to be handled. Shortening the PATH variable solved the problem. This defect is logged to prevent this error from occurring. In case the PATH variable is too long to be handled, it should not cause the baan system to function. In stead the PATH should also be handled in case it is more than 1024 characters Workaround Take care that the value of PATH is smaller than 512KB, and the expanded value is smaller than 1024KB. (e.g. when PATH=%BSE%\bin;%PATH%, %BSE% and %PATH% will be expanded). Test Procedure Into the windows registry, HKEY_LOCAL_MACHINE\SOFTWARE\Baan\\Environment, add the following value: Name: PATH Value: insert a value which contains %BSE% and %PATH% for example. (like: %BSE%\bin;%PATH%) Take care that the system PATH variable is larger than 1024 characters. The following should be possible now: - logging in Baan - Start Baan NT Manager, right-click the environment, and select "Environment variables...". The window popping up should show you also the PATH variable correctly. - Start Baan MMC NT Manager, right-click the environment, and select "Properties" Select "Environment" tab now. The PATH variable should be displayed correctly now. Affected Executables rexecd.exe bentman.exe baanman.dll Motive source DF:154558 MaintMahler: # 24986 (BDUX17579): NQP: select array column indexed by non-selected column gives crash Date: Thu, 17 Mar 2005 17:22:50 +0100 (CET) Created on: MaintMahler Type: bugfix Problem Description (Customer terms) The database driver crashes if the select clause of SQL statement contains an array column indexed by another column that is not by itself in the select clause. The following query is an example: select dblarr(longarr[1]) from dbtst190 where empno = 10 Test Procedure Execute a query similar to the following query: select dblarr(longarr[1]) from dbtst190 where empno = 10 Affected Executables All database drivers MaintMahler: # 24979 (BDUX17624): TCS800-143724: Fix set.time.zone() regression of BDUX17127 Date: Thu, 17 Mar 2005 14:28:51 +0100 (CET) Created on: MaintMahler Type: bugfix Problem Description (Customer terms) When fixing TCS800-143724 regression was introduced: set.time.zone("Europe/Amsterdam ") does not work anymore on UNIX: trailing spaces were suddenly not stripped anymore, and the above call always returns -1. (Accidentally this still works correctly on Windows, because Windows does not support file names ending in spaces.) Workaround Call strip$() on the argument of set.time.zone(). Test Procedure See problem description. Affected Executables bshell Motive source TCS:800-143724 MaintMahler: # 24974 (BDUX17570): Extend xml tracing to catch invalid access to xml nodes (II) Date: Thu, 17 Mar 2005 11:35:44 +0100 (CET) Created on: DevDvorak Type: bugfix Problem Description (Customer terms) Not all access to invalid/freed xmlNodes where traced. Test Procedure See BDUX17398 Affected Executables bshell6.2 Motive source TCS:800-145787 MaintMahler: # 24908 (BDNT17555): BwPrint: postscript emits extra blank page Date: Fri, 11 Mar 2005 16:18:19 +0100 (CET) Created on: MaintMahler Type: bugfix Problem Description (Customer terms) When printing a postscript file, bwprint adds an extra white page at the end. Affected Executables bwprint.exe Motive source DF:153648 MaintMahler: # 24880 (BDUX17548): NQP: driver on Linux/Intel may crash on statement with order by Date: Thu, 10 Mar 2005 16:03:44 +0100 (CET) Created on: MaintMahler Type: bugfix Problem Description (Customer terms) If a statement contains a function in the select clause (such as enum_description), an order by clause and the statement results in a large row set, the database driver may crash. Problem occurs on Linux, Windows and Dec. Test Procedure Run the following command (on a little-endian platform): BAAN_SQL_CACHEROWS=2 bsql6.2 -q" select firstnme, enum_description(sex) from dbtst120 a order by 2 desc, 1 asc " The proper result set should be returned and the database driver should not crash. Affected Executables Bshell Bsql All database drivers MaintMahler: # 24842 (BDUX17482): NQP: Expose _compnr column as company_nr in Ansi mode Date: Fri, 4 Mar 2005 16:08:27 +0100 (CET) Created on: MaintMahler Type: bugfix Problem Description (Customer terms) The name of the _compnr column, as it is known in the Baan application, gives problems if used with Cognos ReportNet. The column "_compnr" is aliased as "C__compnr", which is not recognized by the SQL processor. Test Procedure Execute the following statement: bsql6.2 -p16 -q 'select * from dbtst100 where "company_nr" = 0' The output should be something like: deptno deptname mgrno location admrde company_nr ------ -------------------- ---------- -------------------- ------ ---------- A00 SPIFFY COMPUTER SERV 10 A00 0 B01 PLANNING 20 A00 0 C01 INFORMATION CENTER 30 A00 0 D01 DEVELOPMENT CENTER 0 A00 0 D11 MANUFACTURING SYSTEM 60 D01 0 D21 ADMINISTRATION SYSTE 70 D01 0 E01 SUPPORT SERVICES 50 A00 0 E11 OPERATIONS 90 E01 0 E21 SOFTWARE SUPPORT 100 E01 0 Note that the SQL processor accepts the expression "company_nr" = 0 and that the rightmost column's name in the output is "company_nr". Affected Executables bshell bsql jbdb library Motive source T800-145364 MaintMahler: # 24835 (BDUX17489): Error 850 during record insert Date: Fri, 4 Mar 2005 10:22:03 +0100 (CET) Created on: MaintMahler Type: bugfix Problem Description (Customer terms) It is not possible to insert a new record. The session gives the error message: Fatal error in insert. Test Procedure It is not possible to test this, because the problem can not be reproduced. Affected Executables db4_recio6.2 Motive source DF:146318 DevMahler: # 24814 (BDUX17155): T800-144998: Text_content() and enum_description() fail in ANSI parse mode Date: Wed, 2 Mar 2005 16:17:46 +0100 (CET) Created on: DevMahler Type: bugfix Problem Description (Customer terms) After the multi-company enhancement it is no longer possible to use the enum_description or text_content function, if the query is parsed in the ANSI mode. The following error is returned: The first operand of the enum_description function must identify a column of a table name In 'normal' (non-ANSI) mode it is still possible to use the enum_description and text_content functions. Test Procedure Execute the following command to test enum_description in 'normal' mode. bsql6.2 -q "select enum_description(sex) from dbtst120" Execute the following command to test enum_description on a derived table in 'normal' mode. bsql6.2 -q "select enum_description(sex) from (select * from dbtst120) d" Execute the following command to test enum_description in ANSI mode. bsql6.2 -p16 -q "select enum_description(sex) from dbtst120" Repeat the same tests for the text_content function. Affected Executables bshell bsql Client bdb library (shared BDB api) jbdb library Motive source T800-144998 DevMahler: # 24803 (BDUX17377): Fix HTML of Call Graph Profiler Date: Wed, 2 Mar 2005 10:00:14 +0100 (CET) Created on: DevMahler Type: bugfix Problem Description (Customer terms) Viewing a generated call graph profile in non-IE browser is not working OK. Jumping to queries of objects failed Workaround Use IE of patch generated profile Test Procedure Generate profile and try to explore in firefox (e.g. queries) Use try same with fix profile-generator and notice difference Affected Executables bshell Motive source TCS:800-145796 DevMahler: # 24776 (BDUX17398): Extend xml tracing to catch invalid access to xml nodes Date: Fri, 25 Feb 2005 11:48:30 +0100 (CET) Created on: DevMahler Type: bugfix Problem Description (Customer terms) E.g. NetChange server suffers from not reproducable failures and errors Workaround Source inspection Test Procedure Make nice 3GL allocate a xml node, try to access delete the node and try to access again. Replay with above mentioned trace options and one will notice a remark in trace file. X::::(1):action FreedNodeAccess(xmlWriteTo*) id 3 context -1 Affected Executables bshell Motive source TCS:800-145787 DevMahler: # 24749 (BDUX17405): OS version label in SHM_PARAM is from build machine Date: Wed, 23 Feb 2005 15:25:32 +0100 (CET) Created on: DevMahler Type: bugfix Problem Description (Customer terms) With the installation of a portingset that is build on a newer OS-version customers have to adjust their shm_param by rerunning shm_values as the shm_manager checks aginst the version number of the build instead of checking against the OS version of the runtime system. Test Procedure Run shmvalues6.x and check the label of the last part of the output. To check this in a running environment stop the shared memory, the create a new shm_param file using the new shmvalues6.x and finaly start the shared memory environment. It is important to check this on all Unix environments and Linux. Affected Executables shmvalues6.x shmmanager6.x Motive source DF:152251 DevMahler: # 24724 (BDUX17388): Upgrade Itanium compiler to A.06.00 Date: Tue, 22 Feb 2005 11:27:32 +0100 (CET) Created on: DevMahler Type: porting specific change Problem Description (Customer terms) Installation fails on a HP-UX 11.23 (Itanium) system. The BW error message is FATAL ERROR: index 15 out of dims [1] 6 Can not continue in ottiex1287 in DLL: ottstpamdll (dal.select) Reported by e-mail by Steven Agterhuis / Siebren Weiland by e-mail no 14 Feb 2005. Test Procedure The following script: function main() { long ret long n long dims(4) ret = create.new.symbol("ttaud335.attrs", DB.LONG, 29) bsh.mesg$(sprintf$("ret=%d", ret)) array.info(push.by.name("ttaud335.attrs"), n, dims) bsh.mesg$(sprintf$("array symbol: [%d] %d", n, dims(1))) } should output the following to the bshell trace file: ret=0 array symbol: [1] 29 Essential here is the '29': using compilers 5.56 and 5.57 the result was different. Affected Executables all DevMahler: # 24654 (BDUX17317): Refint: -c option does not check look-up references and Not Compulsory references are not ignored Date: Wed, 16 Feb 2005 13:02:56 +0100 (CET) Created on: DevMahler Type: bugfix Problem Description (Customer terms) Session ttaad4225m000 has the option "Check Validity of Reference". If this option is selected, only references that are "Restricted with Counters" are checked, not the "Check Runtime" references. The "Check Validity of Reference" option should check all references. Affected Executables refint Motive source DF:153309 DevMahler: # 24625 (BDNT17271): Junit test for jbdb Date: Thu, 10 Feb 2005 10:15:39 +0100 (CET) Created on: DevMahler Type: porting specific change Problem Description (Customer terms) There was no way to easily find out if jbdb is working. So a junit based test was added. This test sets up a connection to the database and executes a simple query. In order to run the test, this is required: - have jbdb (built) and junit.jar (/vobs/thirdparty/java/junit...) in the classpath - have jbdb shared library in the shared library path - have environment variable BSE defined - run by: java com.baan.jbdb.test.JbdbTest Workaround ? Test Procedure See above Affected Executables jbdb.jar DevMahler: # 24618 (BDUX17260): Bshell hang after executing shell() function Date: Wed, 9 Feb 2005 10:13:59 +0100 (CET) Created on: MaintBaanIVc Type: bugfix Problem Description (Customer terms) eproduction script: function main() { long ret ret = shell("rm test*", 0) } Execute 'ba6.1 ormtest'. bshell will lock once the shell() function is executed. Program hangs when executing the shell() function. Problem does not always occur when running the ormtest object in debug mode. Workaround No Test Procedure Run the following program script on an AIX5.3 system: function main() { long ret ret = shell("rm test*", 0) } Note: - take care that the file test* does not exist - do not run the object in debug mode Affected Executables bshell Motive source DF:222165 DevMahler: # 24614 (BDUX16899): DEC: Error in lp command Date: Wed, 9 Feb 2005 09:41:36 +0100 (CET) Created on: MaintBaanIVc Type: bugfix Problem Description (Customer terms) After printing to a device of type 'Printer' an error message occurs in $BSE/log/log.lp: 050209-09:18:19: Error in lp command (returning job id): Print job request-ID is: nlbap022-0 Workaround Ignore the message Test Procedure Print to a device of type 'Printer' and check log.lp Affected Executables lp6.x Motive source TCS:800-141526