Is it possible to stop/start the shared memory manager during normal use of Baan? Or is it advisable that everybody is logging of?

Spartacus

Do not try to stop it! (Shouldn't work anyway, but don't even try it, it might corrupt things.) Each and every process in Baan uses the shared memory pool, creating hooks and handles to it. That's the reason it shows the "# of ..." when stopping in a normal way.

Regards,
Nico

Thanks,

so we will do a rc.start and rc.stop


Spartacus

We have BaaN IV c4 installed on Win Nt 4.0, and we use BaaN NT Manager to do this, as told by u above it is advisable that we should stop the shared memorey using BaaN NT Manager, then how do i use this rc.start and rc.stop ???

do i have to use these commands on dos prompt ??


Waiting for your reply.

Hi learner

The rc.start and rc.stop script are part of the UNIX porting sets. On NT, the only way is using the Baan NT Manager.
Thus, you use the correct tools. Same applies as for UNIX however, namely never stop when users are active.

Regards,
Nico

Thanks for the info, i have one more doubt ofcourse that i not related with the shared memory.

how do i create a link between nt_bshell and inf_serve running in my task manager ?

I have baaN IV c4 with Win NT 4 and informix 9 as database.

Regards

Learner

Each client, when starting up, will initially start an ipc_boot. This will fire up the nt_bshell, which in turn fires up an inf_server to communicate with Informix. Thus, for every logged in user, there should be an nt_bshell and an inf_server process. Linking them? The only way that you could try, is by process ID. The ID's of belonging processes will be close together, if not following each other in number. But, if two client log on simultaneously, this will not necessarily be true. Thus, if I get the gist correctly, and you want to terminate a process (killing both nt_bshell and it's inf_server), the safe way will be to use bshcmd. Run this from a DOS prompt, from the %BSE%\bin directory. The options should be similar to those on UNIX (just ignore the 6.1 behind the command):

Usage: bshcmd6.1 [options] <bshell_pid>

-v : Print version
-p : Show process list
-m : Show memory usage
-d <dbglvl> : Set DEBUG_LEVEL to (octal) <dbglvl>
-k <pid> : Kill bshell process id <pid>
-e : Kill all bshell processes
-M "message" : Send "message" to bshell

-W <sec> : Wait until the previous issued command is executed
After this the previous command will be overwritten
-w <sec> : Wait <sec> seconds for bshell to execute command
-u <sec> : Send SIGUSR1 to bshell (wakeup). Only to be used in
combination with -w option. Waits <sec> seconds to
see if the command is executed.
-s : Show entire contents of logfile (if accessable)
-l : Print logfile name of bshell (for later examination)
-T "cmdstr" : Modify BDB_DEBUG or TT_SQL_TRACE (bshell) and DBSLOG,
TT_SQL_TRACE, {DBMS}PROF or {DBMS}STAT (drivers) tracing
variables.
"cmdstr" may contain multiple commands of the form:
<trace variable>=<value>: set variable to value
<trace variable>+<value>: add bits to variable
<trace variable>-<value>: remove bits from variable

Examples:

Show the process list (wait 10 seconds for response):
bshcmd6.1 -p -s -w 10 <bshell_pid>

Print memory usage to file and show file being used:
bshcmd6.1 -m -l <bshell_pid>

Set DEBUG_LEVEL to 02000:
bshcmd6.1 -d 02000 <bshell_pid>

Kill a bshell process with pid <pid>:
bshcmd6.1 -k <pid> <bshell_pid>

Set TT_SQL_TRACE to log interface calls:
bshcmd6.1 -T "TT_SQL_TRACE+02000" <bshell_pid>

- Only one command can be active (new commands will overwrite previous ones)
- Check the return value to see if a command has been processed (use
the -w option)