Here are some information about settings for bshell (BaanIV).

1. Start with a bshell6.1 -? (ntbshell.exe on NT)

Usage: bshell6.1 [options] [program...]
options:

-vV : show program version
-r : show resources
-deftext : show bshell texts
-ba : connect with ba display server
-bx : connect with bx display server
-mdebug : display bshell messages sent to display server
-dbgdata : show datainput options (not for fields!)
-dbgobj : show object information
-dbgref : show reference paths
-dbgfun : debug functions
-dbgsrv : show bdb server type
-dbglck : show locking errors
-dbgmulact : show process actions (activate,sleep,kill etc.)
-dbgrefer : show references
-dbgbdbact : show bdb actions
-dbgfdev : debug file access
-dbgfile : show successfully opened sequential files
-dbgjvmi : show JavaVM integration actions
-dbgres : show loaded resources
-dbgtss : Show TSS-diagnostics and go to debugger on TSS-error
-dbgenums : show loading of enums
-dbginstr : show bshell cpu instructions
-dbgcpu : use debug version of the cpu
-dbgsrdduse : show srdd usage
-dbggpvar : debug get & putvar
-dbgsched : debug scheduler
-dbgpty : debug pty's
-dbgmem : show all memory statistics (see below)
-dbgmemtot : show total memory usage
-dbgmemblk : show memory usage per block
-dbgmemfree : show free memory list
-dbgmemused : show used memory list
-set var=val : set environment variable 'var' to 'val'
-logfile : log stdout/stderr output in
-keeplog : don't remove the logfile after ending the bshell
-appendlog : append to logfile (only useful with -logfile option)
-nolog : stdout and stderr will go to the controlling terminal
(if possible - on remote connection no output will appear)
-delay : delay for seconds before continuing
(useful for attaching with a debugger: set breakpoint
at the function 'delay_ready')
-nodebug : disable debugger.
-server : run as a server without UI

2. You can also get debug information from the Baan database driver by using -- -set TT_SQL_TRACE=value (or added values) to get info about Baan SQL queries beeing handled:

value description
000040 show queries wih their QID
000200 show query exec. times
002000 show calls of internal SQL functions
004000 show query eval. plan (client+server)
010000 show quey ev. plan (server)
020000 show all full table scans

3. Or use -- -set DBSLOG=value (or added values) to get debug info from the online processing of the database driver:

value description
0000001 data dict. info of tables
0000002 query info (sql level 1)
0000004 query info (sql level 2)
0000010 row action info
0000020 table action info
0000040 transaction info
0000100 dbms input/output data (sql level 2)
0000200 admin file info (sql drivers)
0000400 dbms sql statements
0001000 general debug statements
0002000 query processing info
0004000 data buffering info (communication)

4. Then you have other options like:

-- -set PACKAGE_COMB=package combination to login into specific package combination
-- -set BSE_COMPNR=company to login into specific company
-- -set USER=baan_user to login using a different user that the login one (use 1 system login with several Baan logins!)
-- -set RDS_FULL=value to define max. nr. rows transfered between client and server as one block (good for imports/exports)
-- -set BDB_DEBUG=value (like DBSLOG/TT_SQL_TRACE, less used...)
-- -set DS_AS=bshell_name [for ba6.1 only, to specify a specific bshell name from ipc_info]
-- -set BSE_TMP=temporary folder to use a different temporary folder 9other than $BSE/tmp)
-- -set BSE_LANG=value to change language (2=English, etc.)

Thanks Victor.

James

I have been trying to get hold of this info for ages..... Great.

HI,

This is an excelent thread.
I just have a question:
Is it possible to combine several options?
I tried to do something like this: -- -set TWO_TASK=baanIV -set BSE_COMPNR=803, but it has no effect.

Thank you.

You can use more than one of these - I have often used these 3 together in the command line:

-- -set PACKAGE_COMB=B40Cc4XX -set BSE_COMPNR=123 -set BSE_LANG=2

Bogdan,

That will not work if the company you specified is not on the same package combination of the user or the user has no access to it.

Hi,

I found some old info from my emails, which I wanted to share.

-- -set ENVIRONMENT VARIABLE=VALUE[, -set [ADDITIONAL ENVIRONMENT VARIABLES]=[VALUE],...]

Environment Variables
PACKAGE_COMB --> overrides the package combination in your user data.
BAAN_SCM_GRP --> sets your checkout directory so more everyone that uses the same group can see your changes.
SUPPRESS_WINHELP=1 --> if you choose help the baan help appears instead of the windows version of the baan help.
TEST_RETRY=X --> This variable indicates how often the system must go back to a retry point at the moment of committing. This cannot be used when testing different sessions with retry points parallel.
MAX_RETRY=X --> This variable indicates how often the system may return to a retry point as a result of an abort in an update action. Default: 10
CUNO_SRC=1 --> Is needed when exporting Baan components to Scopus

Thanks for the fish Prashant. Now will someone teach me how to fish :) ?

How does one find what the variables are that can be set? Where is the documentation for this? Does it change between versions of Baan?

Hi Vamsi,

I just found that info from my old back up emails... so I thought it might be useful to post here.

I did not find any more documentation. But I guess some of those variable which can be set, might be some global external variables from the bshell.

I have recently found 2 more new options

-- -set USE_BMASK_AS_ABSOLUTE=1 -set BMASK=02

I am wondering if there is any session in baan where we can set the default masks for file creations like in umask in UNIX.

I found few more options -

-set BAAN_WIN_TITLE=”BaaN-ERP-Series” would show the string “BaaN-ERP-Series” in the title of all Baan sessions.

Furthermore, there are some predefined strings that can be used in the window title string. They are:

%C Company Name
%c Company Number
%h Host Name
%p Package Combination
%S Session Name
%s Session Code
%u Userid

ok. I give.
How do I use/do this on an NT?

Hi Matt,

we are working on Unix. But I guess it should also work on NT too so you can test it out.

You can use those option from the BaaN Configuration File, Bshell environment and Commands.

I thought I read on a thread where output from these commands goes by default, but I cannot find it now.

Where on my NT would I find the file to see if this is working?

Does anyone know where I read that information before?
Thanks.

The output goes normally to the file %BSE%\tmp\bshell.<pid>.

If you use the options -keeplog -logfile <pathname\filename> you can redirect it to any place you like.

Han

-- -set UI=ascii

Hi,

is there an environment variable to specify the startup menu?


Thanks


Caner

Great info Thanks!!!!!!

This thread has an attached file on the same subject:

http://www.baanboard.com/baanboard/showthread.php?s=&threadid=6783

Uli

Hi,

I used the option Baan_Win_Title with menu browser and it works great but when I tried to use it with DEM browser, the system did not use the information I specified in the Baan_Win_Title. Is it possible to change the title bar in DEM browser just like in the menu browser?

regards,

Stephen

We have had a case in our support center about this issue and they (I think) made a new solution to solve this problem... search the knowledgebase.

Hi OmeLuuk,

Thank you for the information. I'll check it out.

Is there an equivalent of Baan_Win_Title in BaanIV or does it depend on the porting set of my Baan instance?

regards,

Stephen

It is dependend on portingset.

I have opened a case with Baan support regarding the BAAN_WIN_TITLE variable for BaanIVc4. Baan's response is that it is not support at this time; however, they have received a couple of cases in the last few weeks about this and have opened an Enhancement Request to backport this to BaanIVc4. They are attaching any cases regarding this to the Enhancement Request to show that there is a need.

I am asking anyone with BaanIVc4 to open a Baan case.(It can even be a priority 40) asking for information regarding BAAN_WIN_TITLE for BaaNIVc4. If there is enough demand then for it then it improves the possibility that Baan will do it.

We have multiple systems and multiple companies. We have users that have access across the systems and companies and it can get quite confusing for them. BAAN_WIN_TITLE would allow us to display the hostname and the company name in the title of each Baan window.

Originally we were looking to use different colors but BAAN_WIN_TITLE would work just as well and should be significantly easier to implement.

I have seen it working in the menu browser of baan IV, but in DEM there was some problem...

I would be curious as to what portingset and what bw client you saw it working on. According to Baan Support it isn't even an option for IVc4.

Apparently I do more ERP support than I ever remembered...
it indeed was on iBaanERP5.0c.

Tried just now, this is the result:Inserted undefined resource 'baan_win_title'
Setting resource 'baan_win_title' to '"4_BaanBoard"'

I found a new one -

need a debug flag to verify strings at the moment that they are added to an XML tree,
instead of when the tree is serialized

use -dbgxml flag

Where?

OmeLuuk,

Its a new bshell options as the other ones like -

-dbgdata : show datainput options (not for fields!)
-dbgobj : show object information
-dbgref : show reference paths
-dbgfun : debug functions
-dbgsrv : show bdb server type
-dbglck : show locking errors

Here is a new one for today -

You can use %f to display the filtername in the titlebar.

I found one more environment variable -

Audit management - Tools Technical Manual

File security for various audit management files
It is important that the audit_spec file has read permission for all users, and that
write permission is granted only to the administrator user. Otherwise users other
than the administrator can change the security parameter in the file, which would
allow them illegal access.
Audit server debugging options
For debugging purposes, a code is put in the audit server at appropriate stages to
print useful information. In normal usage, this printing is not enabled. You can
enable it by setting an AUDITLOG environment variable. You can print various
types of information by setting this variable to different values. The values must
be set as octals.
0001 General information.
0002 Print audit rows generated.
0004 Print audit-data dictionary for table.
0010 Print data structures such as information header, sequence header, and
transaction header.
The information is put in a log file. The name of the file is audit.log.pid of the
server. This file is created in the current directory of the audit server.

One more to the list-

The Bshell environment variable BAAN_ART_TRACE can be set for debugging the ARTM code in the application scripts.

0 Tracing disabled.

1 Basic tracing. Transactions are shown.

5 The trace information is send to the file $BSE/tmp/bshell.pid.


Application Response Time Measurement (ARTM) Debugging (http://www.baanboard.com/programmers_manual_baanerp_help_functions_artm_artm_debugging)

Hi there,

Does anybody know if BAAN_WIN_TITLE should work on C4 or not ?
I thought it was a "nice to have" and tried it, but can't seem to get this working.

Baan solution 81854 says ; " not for C4 " So my conclusion is that it's not going to work for me !

This is from the release notes of the Porting Set - 7.3a.03


Enable ART in $BSE/lib/defaults/all with
art_enable:1
art_trace:1
art_user:baan

Resource hide_format_errors set to 0 or 1 ($BSE\lib\defaults\all)

Problem Description (Technical terms)
By default join hints are enabled. Enabling join hints can give huge performance problem (as observed at the beta customer site)

Workaround
Disable the join hints by setting the resource msql_join_hint:NONE or the environment variable MSQL_JOINT_HINT:NONE

SITUATION DESCRIPTION:
For Financial and Logistic Company functionality is build in, in change company but there are no envirioment variables to influence the startup Financial and Logistic Company.

SOLUTION DESCRIPTION:
2 new envirioment variables are introduced.

BSE_LOG_COMPNR and BSE_FIN_COMPNR for logistic and financial company. These environment vars can be used simular to BSE_COMPNR

More Info -

SITUATION IDENTIFIED IN:
"Change Company" (ttdsk2003m000)

SITUATION DESCRIPTION:
For some customer configurations it is needed to switch to the financial company as soon a financial session is started. And also to switch to the logistical company as soon a logistic session is started. If a user forgot to change the company and does an action in the wrong company then this can have bad complications.

SOLUTION DESCRIPTION:
In the "User Data" session ttams1100s000 there are 2 extra fields added. "Logistical Company" and "Financial Company". These 2 fields are not mandatory and can stay empty. When empty the new functionality is not available. When these 2 fields are filled then the new functionality becomes active.


The new functionality is that a company switch to the logistic or to the financial company is done before the session is started.

In the new session ttaad1105m000 "Start Company by Module" you can specify per module if a session should be started in the Logistic or in the Financial Company. If the module of a session is not mentioned then it will be started in the actual company.

Change Company is also modified for this new functionality.
It shows the "Current Company" and the Logistic and Financial Company. All these 3 companies can be changed.

If in "Maintain User Data" the extra fields are not filled then the original change company dialog comes up.

This solution contains a Functional Addition. Please read solution 134994 for the background of Functional Changes.

SPECIAL INSTRUCTIONS:
To use the new functionality you also need the new worktop Version 2.2.28 See Solution 13964

I have merged the updates to this thread into the CMS and added a section for job management environment variables that were missing. See http://www.baanboard.com/node/1770

Another set option. If you are using Gemini Tools (you will at some point, we are using for LES - Leanware!).

-- -set NO_WORKTOP=1

Worktop is manditory for Gemini, but this overrides it so you can use bw client.

Another variable is USE_MSJAVA_DLL. Both have been updated in the wiki here http://www.baanboard.com/twiki/bin/view/Infouser/BaanConnectivity

Dear gurus
Can I use the below options in Baan IV,If so how??

---------------------------
I found few more options -

-set BAAN_WIN_TITLE=”BaaN-ERP-Series” would show the string “BaaN-ERP-Series” in the title of all Baan sessions.

Furthermore, there are some predefined strings that can be used in the window title string. They are:

%C Company Name
%c Company Number
%h Host Name
%p Package Combination
%S Session Name
%s Session Code
%u Userid

Thanks in advance
regards,
Jack

one more to the list ->

New BW option: -giveaway
Author K Van den Dool Creation Date: 07 Mar 2000 Alternate ID:
Solution No: 81488 Last Modified: 08 May 2003 Status: Published
Product: port6.1c.04.02 Sub Product: Session: bw.exe
Package: tt Version: B40 Release: c
Solution Type: KR:Question

Symptom information
Aanlog probleem
Not able to start BW using AT
possible to give password as parameter for Baan job
Error 997 with jobdaemon service.
Logon for batch processes
Case 944811 addressed giving access away to one user, how about a group of users
JOB-NA: Launching job via Job Scheduler, not saving the password in BECS

Solution description
VERSION(S):
BaanIVc, from BW version B40c.052 (Porting Set 6.1c.05 and onwards)
BaanERP, from BW version 7.1a. (Porting Set 7.1a)

SITUATION IDENTIFIED IN:
BW.exe

SITUATION DESCRIPTION:
User A saves the password into the bwc file, and User B tries to run this bwc file.
Because User B is not the same as User A, User B will be asked for the password.
This is a correct way of working of BW and implies security.

But, now User A wants to give away the right to log in Baan to User B, without making his password public to User B.

To make this possible, a new command line option for BW is introduced: -giveaway=<username> (or instead of the dash sign, you may also use the / sign: /giveaway=<username>)


SOLUTION DESCRIPTION:

>>>> Saving password information <<<<

When starting BW Configuration bw is started with the option /config. So,

bw.exe /config

starts BW Configuration.

Here you can switch on "Save Password" and type in the password.
After pressing Save (As) the following is done by bw.exe:

The password is encrypted, together with the current username.
So, when you are logged in Windows as user "baan", the password is encrypted together with username "baan".

The encrypted information is written to the bwc file.
When opening the bwc file using Notepad you will see the following line:

password64=82XG#^f"Tdt0GYF<+;3fB@]7.2n1>u'K9*I:t^cxx<:vZ{F<+;4fB@]1.2n1>f'D

for example.


>>>> Reading password information <<<<

At the moment you run the bwc file, containing the encrypted password, the following happens:

BW determines the current Windows login and checks whether the current Windows login equals to the username, encrypted together with the password. (read from the line "password64")

In case the current Windows login is the same as the username, encrypted together with the password no Login Dialog will pop up, and you can login Baan straight away using this password information.

In case the current Windows login is NOT the same as the username, encrypted together with the password the Login Dialog will pop up, asking you for the password. (Also when viewing the password field via BW Configuration, the password field is greyed out).

In this way password information can only be used by the person who saved this password information.


Give away your login credentials
=========================
A new BW option is introduced: /giveaway=<username>

When specifying this option, for example:

bw.exe /giveaway=baan /config test.bwc

the following happens when saving password information:

Now the password of the user, specified in the field "Connect As", is not encrypted with the current username, but encrypted with the username specified by the /username option.


EXAMPLE(S):

Situation 1:
-----------------
I am logged in Windows as user "jjohn", and open my bwc file "baanserver.bwc".

In fact, bw.exe is started as follows: bw.exe /config baanserver.bwc

The followng is specified:

Hostname: baanserver
Connect As: jjohn
Password: <password of jjohn>

Now, when pressing "Save (As)" the password of jjohn is encrypted together with username "jjohn".


Situation 2:
-----------------
I am logged in Windows as user "jjohn", and open my bwc file "baanserver.bwc", and specify the giveaway option:

so, bw.exe is started as follows: bw.exe /giveaway=psmith /config baanserver.bwc

The followng is specified:

Hostname: baanserver
Connect As: jjohn
Password: <password of jjohn>

Now, when pressing "Save (As)" the password of jjohn is encrypted together with username "psmith".

Now, user jjohn has given the "right" away to user psmith to run his bwc file, using his password information, without publishing the real password.
When user "psmith" is logged in Windows, and runs the "baanserver.bwc" configuration, he will not be asked for the password, as he has the right to "re-use" the password information of "jjohn". (Without knowing the password of user "jjohn").

Thank you every one. This is excellent thread.
Mur

SSA ERP LN 6.1 Programmer's Guide

DAL2 Test Mode
--------------------------------------------------------------------------------
Overview
By means of the DAL2_TEST_MODE environment variable it is possible to test different aspects of a DAL2 DAL from the User Interface. The DAL2_TEST_MODE environment variable must be set in the BW Configuration file and can have the following values:

Value Aspect Explanation

0 None Test mode is off

1 Derived fields
All display maintable fields are shown as input fields. This makes it possible to see whether derived fields are made readonly.

2 (Never) applicable, readonly and derived fields and (never) applicable standard and form commands (business methods)
Same as Mode 1 + All fields and commands stay enabled. In this way is is possible to see if the DAL blocks certain field changes and business methods.

3 Same as Mode 2 + updating dependent fields
Same as Mode 2 + Dependent fields are not updated (no defaulting).

Related topics
DAL2 Field hooks
DAL2 Business Method hooks
DAL2 Field dependencies
DAL2 and the 4GL Engine
DAL2 Test Mode

Applicable for all SSA Baan versions

-set PACKAGE_COMB= <packcomb>:
Sets the package combination and overrides the user data.
-set USER= <username>:
Changes the user who starts the bshell.
-set BSE_COMPNR= <compnr>:
Changes the company number for a Baan Software Environment.

Applicable for SSA Baan version 5.0 and later
-set SUPPRESS_WINHELP= <1>:
Uses ASCII Help instead of Windows Help.
-set BAAN_SCM_GRP= <value>:
Sets the baan scm group, which is used in an .fd file of development
systems.
-set BSE_STD_PROGRAM= <program name>:
Overrides the standard program, which Tools developers and support
personnel use.
-set BAAN_WIN_TITLE= <string>:
Creates a string that contains the title for the window, depending on the
formatting string set by environment variable BAAN_WIN_TITLE. The
following formatting variables are supported. You can also remove the
format variable and surrounding string if the value is considered empty.
To enable, place '<' and '>' around the substring to be removed. The
following table lists the variables and their description that are available with
the BAAN_WIN_TITLE:

Variable Description
%h Hostname
%c Company number
%C Company description
%f Name of current filter
%s Session code
%S Session description
%I Name of current index
%u Name of the user
%p Package combination
%o Window type
%d Nodebug

Command line example:
-set BAAN_WIN_TITLE="%h: %s : %S< [%c]>< (filter: %f)>"

If you run the ttadv2500m000 session in company 000 on host Saturn with
filter Tools, this results in the following window title:
Saturn: ttadv2500m000 : Sessions [000] (filter: Tools)

Applicable for SSA Baan ERP 5.2 and later
-set LTS_LANGUAGE= <language code>:
Sets the LTS language (overrides the user data).
-set LTS_RESOLVE_MODE= <mode>:
mode dump: Retrieve labels from LTS dump
mode database: Retrieve labels from the database
mode fallback: Retrieve labels from fallback

Applicable for SSA ERP LN 6.0 and later
-set CUSTOMIZE= <yes/no>
value NO: Disables customization.

-- -set UI=ascii
Very cool; now I need no longer to start ba6.1 to check that behavoiur.

However, the code normal code to see if we are running in ba6.1 (i.e.
get.display.date(srv_data) / if srv.type(srv_data) = DSBA ...) does not work here. Any ideas?

Baan IVc4 has a feature that seems to work in ASCI mode but not GUI: define session group/add sessions to group/assign session to User startup. the result is that when a user starts Baan, the session(s) in the group assigned to the user will display first. Great way to develop a "splash" screen for certain users.

But this seems to not work in GUI. I can add a session ID as the last parameter for starting bshell6.1 and the session does indeed start. But when I close the session, then Baan closes entirely. This is great if I want to give a user access to just one program, but not helpful for a splash screen where the user stays connected to Baan.

Any ideas? Thanks in advance.

It does work with BW - you just need to make sure your "bshell" in the bw configuration is set to bshell and not something weird.

Dave

It does work with BW - you just need to make sure your "bshell" in the bw configuration is set to bshell and not something weird.

Dave

Yes, I just tried it, using the "bshell" entry in the ipc_info file, as it just executes bshell6.1. Good suggestion; I would never have thought of it.

However, for all my users, I have them execute one of several other entries that execute another file in the /$BSE/bin folder, like bshellm. This script sets values for the tmp folder, etc., and sets the Time Zone for the user -- we have 4 locations in 3 different time zones. It also does some other checking, like UNIX password aging checking and forcing user to change password. I don't know any other way to do these things, but if there is so I can just execute bshell6.1, that might work. Any suggestions?

password ageing you can do from a startup session. The TZ stuff
would be tough.

Dave

Your last answer indicated I could use a startup session for password aging. I think what I'm trying to do is invoke a session at startup. Are you saying to maybe invoke a session upon startup for all users for password aging? Using the Baan Session Group/Session/User Default settings like I'm trying to use? Or is there another way to have a startup session?

it sounded like you use a bshell script to handle your password
ageing.. you could use a startup session.. or use bms_mask instead.

you can look at http://www.mr-paradox.com/passage.html for how i did it..

I've got to update the docs, but i could answer any questions about it you might have.

Dave

It does work with BW - you just need to make sure your "bshell" in the bw configuration is set to bshell and not something weird.

Dave

Okay, now I am really interested. I created a session group, I added two sessions to that session group, I entered that session group to my user data, created runtime, checked my bw configuration and my ipc_info file, loggin in (bw) - and: nothing happens; no automatically startup of any sessions. Hmmh. Could you please show me your bw configuration and ipc_info entry that works? Thanks.

Günther

bshell s 0 0 p ${BSE}/bin/bshell6.1

in BW config "Bshell" == "bshell"

Dave

SSA ERP LN 6.1 Programmers Guide

DAL2 Test Mode
--------------------------------------------------------------------------------
Overview
By means of the DAL2_TEST_MODE environment variable it is possible to test different aspects of a DAL2 DAL from the User Interface. The DAL2_TEST_MODE environment variable must be set in the BW Configuration file and can have the following values:

Value Aspect Explanation

0 None Test mode is off

1 Derived fields All display maintable fields are shown as input fields. This makes it possible to see whether derived fields are made readonly.

2 (Never) applicable, readonly and derived fields and (never) applicable standard and form commands (business methods)
Same as Mode 1 + All fields and commands stay enabled. In this way is is possible to see if the DAL blocks certain field changes and business methods.

3 Same as Mode 2 + updating dependent fields
Same as Mode 2 + Dependent fields are not updated (no defaulting).

Valid in LN Tools

DISABLE_DEBUGGER

Prevents 4 GL debug screens. Continues when a session is complied in debug mode. Has the same meaning as the ‘-nodebug’ option that can be added in the BW configuration screen. Example: DISABLE_DEBUGGER=1

BDB_ALWAYS_FLUSH

Note
Introduced in portingset 6.1c.08, 7.1d.09, 7.6a.02 and 7.6b (March 2005)
This environment variable is intended for test, trace and debug environments only

Problem

In the SSA ERP LN environment a DML (Data Manipulation Language like insert, update or delete) action is normally delayed. until the next query is going to be executed. Just before this next query the DML action will be done. This is done to keep the length of the lock that is caused by the DML operation to a minimum amount of time. When debugging, testing or tracing with e.g. Call Graph Profiler this behavior can give unexpected results. Unexpected results in a normal environment could be:
When a DML action hits a locked record, it will do the actual statements on the next query. When that next query is a normal query it looks very weird that the debugger goes back to a retry point on that query Time on a query looks extremely long (as a delete operation was executed before. This delete forced to check a reference in another table).

Solution

To force an immediate action on a DML action, the DML action could be extended with a third argument (eflag) but this can influence the behavior of the session and asks for additional coding.
Therefore the variable BDB_ALWAYS_FLUSH has been introduced. When setting the variable to a non-zero value like BDB_ALWAYS_FLUSH=1 all DML actions will be flushed immediately instead of being buffered.

English Start up of sessions very slow after install of FP2 and up. This is caused by count.
TOOLS VERSION(S):
7.6_a2

SITUATION DESCRIPTION:
Start up of sessions is very slow since FP2 or an higher version has been installed. Performance analysis will show a count which will be done at the start of every multi-occurrence session. This count is needed to determine the number of rows in the session. This is used to determine the position and size of the block in the vertical scroll bar of the session. Since FP2 the scroll bar can be on any position. There used to be only three positions of the scroll bar, namely: first record, last record and somewhere in between. Now you can actual see on which record it is.

This new functionality could lead to performance problems. An extra query needs to be executed at the start of every multi-occurrence session. The record count on Baan environments containing a lot of data could take a long time. This results in a slow start of sessions.

SOLUTION DESCRIPTION:
The record and the new scroll bar functionality can be disabled by adding the next line to the file $BSE/lib/bse_vars:

SCROLL_LIMIT=-1

On a Windows platform you have to add this variable via the Baan NT Manager (bentman) => Right Mouse click on LN ERP Icon => Environment Variables

SPECIAL INSTRUCTIONS:
None.

BSE_TRACE_DIR

From the Porting Set 8.4b release notes -

With this option you can specify a directory where the trace files are being stored.

SolutionID 151232
CreatedBy Not Known
CreatedOn 2000-07-06
ModifiedBy Not Known
ModifiedOn 2000-07-06
VerifiedBy
VerifiedOn

StatusDescription Published TypeDescription

Solution Description
English pla.ram Error:"Invalid database file format" coming from memory limitation
VERSION(S):

SITUATION IDENTIFIED IN:

ATTACHMENTS:

SITUATION DESCRIPTION:

These are the symptoms of a situation where memory usage exceeds available RAM
These conclusions come from a 300MB database in a 500MB RAM NT Station

The variable BC_MEMDIALOG was activated before the tests

0- When the memory of the server is completely allocated, a message appears on the server: Failed to allocate: 65536 bytes in "BCPoolAlloc". Used: 0 bytes.
1- When you click [OK] a small part of RAM is freed but memory remains allocated at 98%
2- A dialog box appears: "...invalid database file format."
3- Once the server window is closed memory is freed.

SOLUTION DESCRIPTION:
Current customers which use very large databases 200 to 300+ MBytes should have the variable BC_MEMDIALOG exported in the System or User environment. The variable must be activated on the server. This way we get the dialog box on the server indicating the error message "BCMEMPOOL failed to allocate 645556..... bytes of memory". The activation of the variable allows memory problems to be intercepted with more explicit error messages and without the need to trace the problem in a debug environment.

EXAMPLE(S):

WORK-AROUND:
None, NT 32 bit environment limitation

Messaging from bshcmd to bshell

From portingset 8.5a.03 the messaging from bshcmd to bshell is changed. The resource “no_ipc_msg_window” became meaningless, and therefore is replaced by the new resource “no_ipc_messaging”. If “no_ipc_messaging” has a non-zero value then bshcmd cannot be used to send messages to the bshell (also on Windows Terminal Server). The default value of “no_ipc_messaging” is zero (messaging enabled).

Hi guys, I just bumped in to this thread. Question, can the option " -- -set UI=ascii " be used just like that in the configuration's Bshell command line? Using BaaN 5.0c on Unix. When I try I don't see any difference and all windows are still started in GUI mode.

Hi en@frrom,

AFAIK ascii-mode from Baan V on upwards does only work for certain sessions like bdbpost and such for installation purposes. All other menues/sessions are for GUI only.
So I would guess that this switch might work for Baan IV, but will be ignored in later versions.
Just my 2 cent.

regards

Norbert