List of changes for portingset: 6.1c.06.05List of changes for portingset: 6.1c.06.05 MaintBaanIVc: # 14555 (BDUX8193): JDK1.3 support Date: Mon, 1 Jul 2002 14:55:17 +0200 Created on: MaintBaanIVc Type: porting specific change Problem Description (Customer terms) Can not use JRE1.3 on Solaris to load libjava.so Workaround Use JRE 1.1.8 or 1.2.x Test Procedure Run tmboaserver on a platform with JRE1.3. Create a file $HOME/jvm_options or $BSE/java/jvm_options. When $HOME/jvm_options is found $BSE/java/jvm_options will not be read. In that way a certain user can use its own options. $ java -help or java -X shows which options are availlable. For example: put in jvm_options: -Xmx=128000000 -hotspot MaintBaanIVc: # 14536 (BDNT8151): BW access violation in rowcolumn widget Date: Mon, 1 Jul 2002 11:29:00 +0200 Created on: MaintCorelli Type: bugfix Problem Description (Customer terms) An error takes place at various times while BW is running WinRunner scripts. A message box is received with the title: tcibd0101s000:General Item Data (675) dcaca314:bw.exe - Application Error. The contents of the message box reads "The instruction at "0x5f4012a1" referenced memory at "0x00000004". The memory could not be "read". Click on OK to terminate the program." Additional Information: The error regarding "referenced memory ... The memory could not be "read"" creates the following message in the NT event log: Event Type: Error Event Source: Baan Event Category: (7) Event ID: 1000 Date: 6/17/2002 Time: 6:42:31 AM User: NW\trnxrun1 Computer: E120677 Description: The description for Event ID ( 1000 ) in Source ( Baan ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. The following information is part of the event: Env Bse (\\dcac-nt-10\dcac_develop\baan\bw) Prog BW file \general\lib\al_1\al_wutil.c # 534 Keyword Stack trace Username trnxrun1 type S language 2 Process 0x54c ProcessSet trnxrun1@E120677:1356 Lasterror 0 Errno 0 bdberrno 0 Message Exception C0000005 (Access violation) TsRowColWidgetRec::changeLayoutPE+1C8 (1:000a9358) TsRowColWidgetRec::changeLayout+45 (1:000a8bf5) TsRowColWidgetRec::changeManaged+5E (1:000a838e) TsCompositeRec::doChangeManaged+4C (1:000b9c6c) TsCompositeRec::doChangeManaged+33 (1:000b9c53) TsCompositeRec::doChangeManaged+33 (1:000b9c53) TsCompositeRec::doChangeManaged+33 (1:000b9c53) TsWidgetRec::topRealize+16 (1:00077736) TsToolkit::realizeWidget+B (1:0006deab) TsRealizeWidget+12 (1:00068112) DmRealizeMWindow+15 (1:000633b5) DmCheckObjectResourceTable+2584 (1:0005d914) DmFreeArgList+46F (1:0006170f) DmChangeCompoundWidgetProc+13 (1:00060e93) DmChangeWinObject+125 (1:0005fc85) DmRequestTimerHandler+AA (1:00056baa) DmRequestInputHandler+5 (1:00056ac5) TsInputIdRec::streamCallbackProc+30 (1:000b9080) SocketData::processStreamData+1B (1:00022d3b) SocketData::processIncomingData+C9 (1:00022e29) SocketData::windowProc+1BD (1:0002306d) Test Procedure This failure only occured after extensive testing with WinRunner scripts. It probably occurs when a 4GL Find dialog is started. Motive source DF:208551 MaintBaanIVc: # 14518 (BDUX7878): DB: memory leak with auditing Date: Fri, 28 Jun 2002 14:42:08 +0200 Created on: MaintBaanIVc Type: bugfix Problem Description (Customer terms) "BW exits when we try to create very large number of records in Baan using a BOI." The insertion of a Purchase Order leads to starting a new session in the bshell (function server), the insertion of records, and the ending of the session. For each Purchase Order this procedure is followed. Each time a session is ended, an amount of memory is not freed. When a large amount of Purchase Orders is inserted, the bshell will abort because of memory exhaustion. This only happens when auditing is enabled on the table on which the inserts are done. Workaround If possible, disable auditing. Test Procedure Use the following test scripts (Baan3gl): Source t.c: function main() { long i, pid for i=1 to 1000 pid = activate("./s.o") wait( pid, WTHANG ) endfor } Source s.c (if needed, modify the source to use another table): table tdbtst120 function main() { error.bypass = 1 dbtst120.empno = 17 dbtst120.workdept = "A00" db.insert( tdbtst120, db.retry ) db.first( tdbtst120 ) abort.transaction() } Compile the scripts: bic6.1 ./t.c -o ./t.o bic6.1 ./s.c -o ./s.o Run the object t.o: bshell6.1 -server ./t.o Now observe the size of the bshell process (e.g. using ps -l). After an initial growth, it should very quickly stabilize. Scopus defectnumber(s) Scopus casenumber(s) Priority (e.g. 10) 124015 20 - Major Problem MaintBaanIVc: # 14508 (BDNT8150): BW4: explicitly set WINVER to 0x0400 Date: Fri, 28 Jun 2002 08:58:20 +0200 Created on: MaintBaanIVc Type: bugfix Problem Description (Customer terms) Bar menu problems when using RightToLeft mode on NT4 Test Procedure see Scopus call Motive source DF:124443 MaintBaanIVc: # 14474 (BDUX8081): JVM startup arguments Date: Tue, 25 Jun 2002 16:48:42 +0200 Created on: MaintBaanIVc Type: bugfix Problem Description (Customer terms) Can not use JRE1.3 on Solaris to load libjava.so Workaround Use JRE 1.1.8 or 1.2.x Test Procedure Run tmboaserver on a platform with JRE1.3. Create a file $HOME/jvm_options or $BSE/java/jvm_options. When $HOME/jvm_options is found $BSE/java/jvm_options will not be read. In that way a certain user can use its own options. $ java -help or java -X shows which options are availlable. For example: put in jvm_options: -Xmx=128000000 -hotspot MaintBaanIVc: # 14436 (BDUX8107): Correct the badfix for bdbpost skip table Date: Thu, 20 Jun 2002 17:04:18 +0200 Created on: MaintBaanIVc Type: bugfix Problem Description (Customer terms) Bdbpost gives the error message: "Can not read table definition (error 0)" Workaround No workaround. Test Procedure Create with bdbpre6.1 an export file. For example: $ bdbpre6.1 -N dbhvl011 -C 700 > dbhvl011700.dmp Recreate the table with bdbpost from the export file on an AIX system. For example: $ bdbpost6.1 -k < dbhvl011700.dmp The output of the old and wrong bdbpost likes: Default separator ('\0') taken Table M Idx RowCount Messages 00700 Can not read table definition (error 0) The output of the new and correct bdbpost likes: Default separator ('\0') taken Table M Idx RowCount Messages dbhvl011700 1 400 Create with bdbpre6.1 an export file of three tables. The first table should contain at least 1Kbyte of data. For example: $ bdbpre6.1 -k -N dbhvl011 dbhvl012 dbhvl013 -C 700 > table.dmp Create in the "storage" file of the used database a seperate line for the data of the first table. For example: (Oracle): dbhvl011:700:T:TABLESPACE datspace PCTFREE 80 PCTUSED 20 INITRANS 3 \ STORAGE(INITIAL 1K MAXEXTENTS 1) The aim of this line is that loading the data in this table will fail very soon. Recreate the tables with bdbpost from the export file. For example: $ bdbpost6.1 -nf < table.dmp The output of the old and wrong bdbpost likes: Default separator ('\0') taken Table M Idx RowCount Messages dbhvl011700 1 100 Can not commit transaction (error 520) Bdbpost6.1 stops after the failure in the first table. The output of the new and correct bdbpost likes: Default separator ('\0') taken Table M Idx RowCount Messages dbhvl011700 1 100 Can not commit transaction (error 520) dbhvl012700 1 2 dbhvl013700 1 2 Bdbpost6.1 continues after the failure in the first table. MaintBaanIVc: # 14412 (HYNT7829): MSQL: Locked error while issuing clear table:Scopus defect 123964 Date: Wed, 19 Jun 2002 11:49:58 +0200 Created on: MaintBaanIVc Type: bugfix Problem Description (Customer terms) MS-SQL Server returns locked error while clear table. Workaround Set a very high value for msql_lock_timeout, and msql_query_timeout. Test Procedure 1. Execute db.clear.table statement on a table with large ( >60,000 ) number of records. 2. Test for Locked error #1 ddcts508 TCRTBL 0 #1 ddcts508 RINS 0 -i = ddcts508.int = 1 #1 ddcts508 RINS 0 -i = ddcts508.int = 2 #2 ddcts508 RINS 0 -i = ddcts508.int = 1 ->gives locked error #1 ddcts508 DCOM 0 #2 ddcts508 DCOM 0 Motive source DF:123964 MaintBaanIVc: # 14385 (BDUX8006): OVERLEAP enable in bic Date: Mon, 17 Jun 2002 13:21:05 +0200 Created on: MaintReger Type: bugfix Motive source TCS:106-111860 MaintBaanIVc: # 14379 (BDUX8063): C-int merge fix for as400/os390 Date: Mon, 17 Jun 2002 09:56:38 +0200 Created on: MaintBaanIVc Type: porting specific change Motive source DF:207273 MaintBaanIVc: # 14333 (BDUX8011): make oj_help_opt_choose_index resource Date: Wed, 12 Jun 2002 12:09:18 +0200 Created on: MaintBaanIVc Type: bugfix Problem Description (Customer terms) Performance problem in session tdinv1553m00b with DB2 Level-2 Workaround n/a Test Procedure Use following qptool query : select tdinv150.item from tdinv150 where tdinv150.item refers to tiitm001 The dbs.log file will show the next query when oj_help_opt_choose_index is on (1). This is the default value. SQL> SELECT a.t_item FROM ( db2baan.ttdinv150653 AS a LEFT JOIN db2baan.ttiitm 001653 AS b ON b.t_item = a.t_item) WHERE (b.t_item = a.t_item OR b.t_item IS NU LL OR a.t_item IS NULL) When oj_help_opt_choose_index is off (0) the dbs.log file will show the next query. SQL> SELECT a.t_item FROM ( db2baan.ttdinv150653 AS a LEFT JOIN db2baan.ttiitm 001653 AS b ON b.t_item = a.t_item) WHERE b.t_item = a.t_item Motive source DF:121781 MaintBaanIVc: # 14325 (BDUX8026): C-Interface performance fixes Date: Wed, 12 Jun 2002 08:38:06 +0200 Created on: MaintBaanIVc Type: bugfix Problem Description (Customer terms) When using the Baan c-interface the created api can at times use up all (or most)of the CPU. Test Procedure Create a test api which calls a Baan dll function. The baan dll function should have some long suspend()'s coded in them. This simulates a long response from the Baan side. Run new api i(built agains new libci.a lib) and observe that the new functionality reduces cpu usage significantly. Motive source DF:207273 MaintBaanIVc: # 14322 (BDNT7612): Add -logtime option Date: Tue, 11 Jun 2002 14:21:22 +0200 Created on: MaintBaanIVc Type: bugfix Problem Description (Customer terms) Need to have the possibility to do bshell tracings with timestamps. Test Procedure Run following tracing: -dbgmulact -logtime -logfile trace -keeplog. Timestamps are added to the trace file. Motive source Scopus Defect 125547 MaintBaanIVc: # 14315 (BDUX7912): C-Interface Perf. Enhancement Date: Mon, 10 Jun 2002 11:52:13 +0200 Created on: MaintBaanIVc Type: bugfix Problem Description (Customer terms) When using the Baan c-interface the created api can at times use up all (or most)of the CPU. Test Procedure Create a test api which calls a Baan dll function. The baan dll function should have some long suspend()'s coded in them. This simulates a long response from the Baan side. Run new api i(built agains new libci.a lib) and observe that the new functionality reduces cpu usage significantly. MaintBaanIVc: # 14301 (BDNT7993): lost connection Date: Fri, 7 Jun 2002 14:52:04 +0200 Created on: MaintReger Type: bugfix Problem Description (Customer terms) When installing reger on W2k / Oracle 9, Error during dba_processing occured. Connection to server lost: fd_read 508: num_bytes -1 errno 0 Test Procedure Run BSI. Motive source TCS:100-127478 MaintBaanIVc: # 14288 (BDUX7991): option 2 for open.message does not a correct check. Date: Fri, 7 Jun 2002 11:19:25 +0200 Created on: MaintBaanIVc Type: bugfix Problem Description (Customer terms) According to the Baan help, open.message(...) should return -1 and not create a new mailbox when the parameter action is 2 and a mailbox does not already exist. This is not how open.message(...) seemed to be working Test Procedure execute the next command: function main() { long ret string in.queue(132) in.queue = creat.tmp.file$(bse.tmp.dir$()) ret = open.message(1, in.queue, 2) ret = open.message(1, in.queue, 0) ret = open.message(1, in.queue, 2) if len(in.queue) <= 128 then ret = seq.unlink(in.queue) endif } the ret should be -1 the first, the next time a value should be returned, and the last time the same value should be returned Motive source DF:208185 MaintBaanIVc: # 14272 (BDUX7911): Bad performance printing to direct printer Date: Tue, 4 Jun 2002 16:45:02 +0200 Created on: MaintBaanIVc Type: bugfix Problem Description (Customer terms) Printer (Mannesman Tally T-661) very slow after installation port. 6.1c.06.03 Workaround n/a Test Procedure print to a direct printer Motive source DF:124929 MaintBaanIVc: # 14268 (BDUX7828): Informix:Error on insert after dropping and recreating a table:TCS-100/126499 Date: Tue, 4 Jun 2002 16:41:16 +0200 Created on: DevEscher Type: bugfix Problem Description (Customer terms) None Test Procedure Logon to system Eddie. Go to directory "/home/dbregtr/reg_tests/ctsid108/tcid100/tc4" Run: "bdbpost6.2 -kn -c 623 < pre.dmp" The pre.dmp contains table ddcts550 in company 621 and 622. The "-c" option force that both tables are created in company 623. So table ddcts550 is created in company 623 and the rows are inserted. With a driver that does not include this fix the second post action fails with the error 502. Motive source TCS:100-126499 MaintBaanIVc: # 14262 (BDUX7959): Informix:Fixing error 410 on insert:TCS-100/127391 Date: Tue, 4 Jun 2002 16:35:01 +0200 Created on: MaintReger Type: bugfix Problem Description (Customer terms) None Test Procedure Run the following gcommand script #1 ddcts531 TDRTBL 0 -c 621 #1 ddcts531 RINS 0 -i -c 621 -E NO_TABLE = ddcts531.int1 = 1 #1 ddcts531 DABORT 0 #1 ddcts531 RINS 0 -i -c 622 = ddcts531.int1 = 1 (Company 622 has to be a logical company referring to the physical company 621) The driver should return error 506 ( Table does not exist ) for the second insert command. A driver without this fix would return the native error -401. Motive source TCS:100-127391 MaintBaanIVc: # 14231 (BDUX7964): Oracle driver should translate ORA-24345 into Baan error 512 Date: Fri, 31 May 2002 14:16:16 +0200 Created on: MaintCorelli Type: bugfix Problem Description (Customer terms) When a table column in Baan is shorter than the actual size in Oracle, truncation occurs during fetch. Depending on resource settings and Oracle version this can return error ORA-24345. Error ORA-24345 should be returned as E_BDB_DD_CORRUPT (bdb_errno 512) Test Procedure Modify the dtt.pd file. Change the length of ttdsca from 30 to 10 and run the following command: qptool6.2 -c 0 -q "select * from ttaad100" The old driver causes the following output containing the native Oracle error: Error 25345 Msg '' The new driver causes the expected error to occur: Error 512 Msg '' Do not forget to restore the dtt.pd file! Motive source TCS:106-124615 MaintBaanIVc: # 14221 (BDUX7963): Force compiler to use ANSI setting, since the default is K&R Date: Fri, 31 May 2002 09:39:07 +0200 Created on: MaintCorelli Type: porting specific change Problem Description (Customer terms) Due to compiler settings imake/cpp didn't compile, and therefore no build of the portingset could be started. Workaround Make ANSI the default since old compiler versions take K&R as default (or upgrade compiler) Test Procedure Build! MaintBaanIVc: # 14200 (BDNT7932): Nested queries: are not placed in busdoc correctly Date: Wed, 29 May 2002 19:42:53 +0200 Created on: MaintCorelli Type: bugfix Motive source TCS:100-125228 MaintBaanIVc: # 14181 (BDUX7900): Print with Baan user on AS400 DF123378 Date: Wed, 29 May 2002 08:42:20 +0200 Created on: MaintCorelli Type: bugfix Problem Description (Customer terms) The problem is that when printing on AS400 as Baan user and the Baan user is not known on the AS400 as Operating System user nothing is printed. E.g. a user (i.e. bsp310) is created and is working on AS400 as user bsp. If a print action is executed to Device Type: printer nothing is printed. Workaround Make sure that the Baan user is also known as a OS user. Test Procedure Login to Baan on an AS400 system using a user which is not known as OS user on the AS400. Try to print something to Device Type: printer. Motive source DF:123378 MaintBaanIVc: # 14171 (BDUX7929): Informix:Error 214 in drop table: 100-127317 Date: Wed, 29 May 2002 08:35:05 +0200 Created on: MaintReger Type: bugfix Problem Description (Customer terms) None Test Procedure Run the following gcommand script 1 ddcts502 TDRTBL -0 1 ddcts502 TDRTBL -1024 The first drop table command will fail due to references. The second one will succedd due to the IGNORE REFERENCES (1024) flag. A driver without this fix would cause the second command to fail as well. Motive source TCS 100-127317 MaintBaanIVc: # 14147 (BDNT7914): full installable problems in installer Date: Mon, 27 May 2002 10:12:06 +0200 Created on: MaintBaanIVc Type: bugfix Problem Description (Customer terms) Minor textual change in installer text + deliver new style ipc_info Workaround N/A Test Procedure Check after fresh new install that ipc_info in 3 column format is in $BSE/lib MaintBaanIVc: # 14136 (BDUX7848): Informix failure encountered on flush cursor Date: Fri, 24 May 2002 13:07:36 +0200 Created on: MaintBaanIVc Type: bugfix Problem Description (Customer terms) The log.informix ($BSE/log) is getting full with the following error : Log_mesg: Informix failure encountered on flush cursor. Workaround n/a Motive source DF:124021 MaintBaanIVc: # 14134 (HYUX7909): Informix:Map Informix error 217 to Baan error 512:TCS 100-126653 Date: Fri, 24 May 2002 13:04:32 +0200 Created on: MaintBaanIVc Type: bugfix Problem Description (Customer terms) None Test Procedure Modify the dd file for a table that already exists in the database by adding a new column. Now run a query on that column. The driver should return error 512. Motive source TCS:100-126653 MaintBaanIVc: # 14133 (HYUX7908): DB2:Map DB2 error 206 to Baan error 512:TCS 100-126655 Date: Fri, 24 May 2002 13:03:08 +0200 Created on: MaintBaanIVc Type: bugfix Problem Description (Customer terms) None Test Procedure Modify the dd file for a table that already exists in the database by adding a new column. Now run a query on that column. The driver should return error 512. Motive source TCS:100-126655 MaintBaanIVc: # 14127 (BDUX7884): bdbpost skips table on error. Date: Thu, 23 May 2002 11:59:50 +0200 Created on: MaintReger Type: bugfix Problem Description (Customer terms) bdbpost6.x skips loading next table. Workaround No workaround. Test Procedure Create with bdbpre6.2 an export file of three tables and drop the tables. For example: $ bdbpre6.2 -k -N dbhvl010 dbhvl011 dbhvl012 -C 700 > table.dmp Create in the "storage" file of the used database a line for the indexes of the first table with a not existing indexspace. For example: (Oracle): dbhvl010:611:I:TABLESPACE exist_not PCTFREE 5 INITRANS 3 Recreate the table with bdbpost from the export file. For example: $ bdbpost6.2 -knf < table.dmp The output of the old and wrong bdbpost likes: Default separator ('\0') taken Table M Idx RowCount Messages ----------- - --- -------- ---------------------- dbhvl010700 1 3 Adding indexes ...Can not creat index 1 (error 1959) mkdir error 22 dbhvl012700 1 6 Adding indexes ... The output of qptool shows that the second table isn't created. For example: $ qptool6.2 -q "select * from dbhvl011" -c 700 [0] SQLState QP999: Table does not exist (error 506) The output of the new and correct bdbpost likes: Default separator ('\0') taken Table M Idx RowCount Messages ----------- - --- -------- ---------------------- dbhvl010611 1 3 Adding indexes ...Can not creat index 1 (error 1959) dbhvl011611 1 3 Adding indexes ... dbhvl012611 1 6 Adding indexes ... The output of qptool shows that the second table is created. For example: $ qptool6.2 -q "select * from dbhvl011" -c 700 1 730570 985608869 'One ' 700 2 730571 985608876 'Two ' 700 3 730572 985439687 'Three ' 700 In both cases the exit code of bdbpost is unequal to zero because the index(es) of the first table can't be created. So the first table has no indexes after the import with bdbpost. Motive source DF:113869 MaintBaanIVc: # 14102 (BDNT7865): TCS 100-125228: Nested queries do not work Date: Wed, 22 May 2002 14:41:55 +0200 Created on: MaintCorelli Type: bugfix Problem Description (Customer terms) Nested queries (more than 2 deep) within OW are not handled correctly Motive source TCS:106-125228 MaintBaanIVc: # 14094 (BDUX7838): Informix:Database server termination:Scopus-119619 Date: Wed, 22 May 2002 12:08:54 +0200 Created on: MaintBaanIVc Type: bugfix Problem Description (Customer terms) Create some items using the session tiitm0101m000. Delete a bunch of items using tiitm0203m000. The session terminates with the error "Detected Database Server Termination." Workaround Turn off the prepare statement cache. Set inf_use_prepare_cahce:0 in $BSE/lib/defaults/db_resource. Test Procedure Delete a bunch of items (5 or more) using the session tiitm0203m000. With a driver that does not contain this fix, the session terminates with the message "Detected database server termination" and the user loses connection with the bshell. With this fix, the deletion of items will go through successfully. Motive source DF:119619 MaintBaanIVc: # 14076 (BDUX7858): DDC sample driver fix Date: Fri, 17 May 2002 08:37:56 +0200 Created on: MaintBaanIVc Type: bugfix Motive source DF:110764 MaintBaanIVc: # 14052 (BDNT7783): Fixed bug for full installable for Oracle installation Date: Mon, 13 May 2002 16:20:48 +0200 Created on: MaintBaanIVc Type: bugfix Motive source TCS:100-126389 MaintBaanIVc: # 14007 (BDUX7776): DDC Merge 4c Date: Thu, 2 May 2002 17:17:14 +0200 Created on: MaintBaanIVc Type: bugfix Problem Description (Customer terms) When run from the command prompt in background mode, the sample ddcdriver.exe was stopping without any information as to why. Workaround Since baan memory libraries are not available to users when compiling the sample driver, all references were removed so only standard C memory functions are used throughout DDC. Test Procedure Set all of the standard DDC environment variables and make sure that DDC_INITIATE is set to 3. Run ddcdriver and see the connection to bshell and then the processing of messages. Motive source DF:110764 MaintBaanIVc: # 14006 (BDNT7589): MSQL_SERVERHOST not taken in account by msql7_maint.exe Date: Thu, 2 May 2002 17:15:09 +0200 Created on: MaintBaanIVc Type: bugfix Problem Description (Customer terms) When running msql7_maint.exe in batch mode, the following is specified in the command file. E.g.: -F -OMSQL_LEVEL1=1,MSQL_SERVERHOST=SRV-NLD-BCI0 -F -abaanadm -mbaanadm -p)12I,M+Lq5%vb`#xI,bj|Xj\O"4u"q.Q -csa -iHB$BAkD?iE"^T]-vg2w5M&PgZ<^pr~;~ -Gbaandb -PpDOH9u~?Tkv~*3e!&t#