I want to change $BSE_TMP directory for users with BW.
For my user (bsp, text interface), I use .profile to set $BSE_TMP

but for users that use BW, how I do for change this simple parameters?.


Thanks

Add this to the BW command in the corresponding BWC file -

-set BSE_TMP=/app/common/home/bsp

Ok. Thanks. I know this.
I wrote wrong my questions....

Which is the default file for users that they doesn't write anything on his *.bwc?

I've one server, with two BaaN applications, for two differents factories (two diferents binaries too).
a) $BSE=/prod/baan/bse
b) $BSE=/baan/B40c/bse

and actually I've for both Baan's $BSE_TMP=/tmp
and I want to separate this with out modify the 103 *.bwc, due to the users are in differents countries...

You could also try using $BSE/lib/bse_vars
and setting BSE_TMP in there, that file is selective though and may
or may not pick it up.

You could Remove your $BSE/tmp directory and create a symbolic link to the new directory.

Not really reccomended though, a lot of adding and deleting goes on in that directory.. too much of a chance for Baan to step on itself..

Dave

As Dave said, bse_vars and alos other locations might not always be picked up, depending on the protingset.

The cleanest way of doing it, is the following:

1) Change the ipc_info in $BSE/lib entry for bshell to point to a self written small script.

2) In this script set all environment variables you need, maybe even depending on your hostname odr username).

3) At the end of the script call
exec $BSE/bin/bshell6.1 $*

The procedure is described several times here on the board, just search for ipc_info. This approach is perfect, because both ASCII and GUI users will automatically use it, it is completely server based, no bwc entries etc.

You can also use it to implement features like password aging, blocking the application for specific user groups, avoiding double logins etc.

Man possibilities,

Regards

Markus

For system-wide, why don't you setup in rc.start?
Be careful if you use BaanLogin protocol, all BSE_TMP using it defined in rc.start_blogind.

What's effective in rc.start is only effective for the processes started in there:

shared memory timer
licence daemon
printer daemon
bisam
etc.

It will not effect the user processes. Wether the environment of blogind is inherited by the bshell processes is a interesting idea. Did somebody actually test this?

1. Refer to Jim's posting - Environment Variables (http://www.baanboard.com/baanboard/showthread.php?t=446&highlight=environment)

2. I think Markus idea will work as you can control the log files for all the users.

3. Whether the environment of blogind is inherited by the bshell processes is a interesting idea. Did somebody actually test this?
Yes. We have 3-5 different environments on a single Unix machine. If you have only one Blogin daemon per system, then it picks up all the environment variables belonging to the one you started up. Its more obviously visible if you define your own env variables in $BSE/lib/bse_vars (Refer to my #1 posting).
Therefore, we have 3-5 blogin daemons, running for each environment so that even if you bring down one environment (the one which has started the blogin daemon) the others can still work.

We have multiple BaanIV and V environments on the same server, and they can share the same blogind(port 7150.) We realized this because BaanV users generate big tmp file filled on BaanIV enviroment as we started blogind from BaanIV. You can login 2nd env. and echo $BSE_TMP which is the same as defined in rc.start_blogind.