Hello all,

We have two separate Baan IV environments, sharing the same license daemon, running on the same AIX box. Before the 2nd environment was added, I always could enter from an AIX command line:

ps -ef | grep bshell

to count the number of users logged into the system. Now if I execute that command, I can't tell which system the user is logged on to.

Does anyone know of a way to inquire into the number of users logged on to a specific environment? I have looked at shmmanager6.1 and bshell6.1 parameters, but have not come up with anything yet.

Any ideas?

Thanks,
Judy

Judy,

You can rename the bshell as bshell_dev, bshell_qa etc in the respective $BSE/lib/ipc_info files.

Then when you use the ps -ef | grep bshell_dev you can know the environment specific users who are currently logged in.

then execute the command -

$ ps -ef | grep bshell_dev | grep -v "grep bshell_dev" | wc -l

Hello NPRao...

Great idea! I knew about this option, but never thought about using it in this capacity. That should definitely do the trick!

Many thanks,
Judy

OK, here is my ipc_info, with the bshell change...

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

Yet, when I do the ps -ef | grep bshell, I still see the bshells represented as 'bshell', not bshell6.1_dev, like so...

aixdev:root:/baan4ct/bse/lib>ps -ef|grep bshell

bsp 65084 9804 0 13:58:14 - 0:00 bshell (bsp@TRWJK:1504/SOCKET) -1
545 5 6

Did I implement this change incorrectly?

Judy,

You made a mistake there, you have to change the entry and not the executable name....

Here is our info -

>cat ipc_info
bshell_user s ${BSE}/bin/bshell6.2
bshell_supp s ${BSE}/bin/bshell6.2
bshell_ctlm s ${BSE}/bin/bshell6.2
bshellOW6.2 s ${BSE}/bin/bshellOW6.2
bshellmig s ${BSE}/bin/bshell6.2
bshell.inst s ${BSE}/bin/bshell_inst6.2
audit s ${BSE}/bin/audit_srv6.2


After you make the change in the $BSE/lib/ipc_info file you also need to change the bshell name in the BW configuration file. Because if you remove the "bshell" entry in the ipc_info file then you cannot log into the system.

That was a resounding "DUH" on my part!

Thanks for setting me straight! It's working now.