When you startup Baan using bw is there somewhere that tells baan to run certain programs at time of login?

A few months ago we evaluated the Disus product on our test Baan server and I thought I had uninstalled it. But we have a problem that when a normal user logs on to the test server they get an error saying "no permission for tcdisbshellch" The tcdisbshellch session is the Disus Bshell Checker (idle logout) So when the user logs in I'm presumming that this session is trying to run but the user does not have authorisation through their DEM.

I thought maybe there would be something in the uxxx file under $BSE/lib/user directory but there isn't.

Is there anywhere else I can check?

Thanks

You can define session groups and assign them to users. Within these session groups you can define which sessions have to be started if the user log's on.

The session group is stored in the u<user> file in $BSE/lib, the session group definition is stored also somewhere in that directory.

However I am not sure if that bshell checker makes use of these options.

Rgrds,
Han

ttaad2107m000 (Maintain Session Groups) to define groups
ttaad2106m000 (Maintain Startup Sessions [per group]) to assign sessions to a group
ttaad2105m000 (Maintain User settings) to assign a group to a user.

More help (from KQ):

Maintain Session Groups (ttaad2107m000)
To group sessions which are started first after starting the bshell. With the session Maintain Startup Sessions (ttaad2106m000) you can specify which sessions belong to which group. In the session Maintain User Settings (ttaad2105m000) you can assign the session group to a user.

Maintain Startup Sessions (ttaad2106m000)
To group sessions which will be started automatically when a user starts the bshell. Prerequisite is that the session group has been assigned to that user in the session Maintain User Settings (ttaad2105m000).

Maintain User Settings (ttaad2105m000)
To specify defaults settings per user. The fields in this session are divided in two parts.
The first part consists of the general user settings. In this part you can assign a key map group and session group to the user. You can also specify if the debugger must be displayed in the same window or in separated windows.
The second part is only used for ASCII-terminals excepted the field "Sign During Input". In this part you can specify the colors of the BA menus.

I have checked the three sessions mentioned and we do not have anything set here.

What else could be calling this bshell checker?

Thanks

PJ

I would...

1. Check the BW client to see what program you are calling (eg. bshell)

2. Check the ipcinfo file to see what is being called by the rexec call from the client (perhaps a bshell wrapper script)

3. See if there is a reference to the Disus executable in the wrapper script.

Otherwise, send an email to Disus?

-- Jim

Jim,

Thanks for your reply.

1. We are calling bshell from the BW client.

2. Our ipc_info file looks like:

bshell s 0 0 p ${BSE}/bin/bshell6.1
bshell.inst s 0 0 p ${BSE}/bin/bshell_inst6.1
sh_server s 0 0 s ${BSE}/bin/sh_server6.1
audit s 501 510 p ${BSE}/bin/audit_srv6.1
fs6.1 s 303 335 m ${BSE}/bin/fs6.1
nserver s 0 0 s ${BSE}/bin/nserver6.1
bisam s 307 370 p ${BSE}/bin/bisam_srv6.1
btam s 307 370 p ${BSE}/bin/btam_srv6.1
informix s 305 350 p ${BSE}/bin/inf_srv6.1
oracle7 s 302 320 p ${BSE}/bin/ora7_srv6.1
oracle8 s 302 320 p ${BSE}/bin/ora8_srv6.1
sybase s 309 390 p ${BSE}/bin/syb_srv6.1
db2 s 310 301 p ${BSE}/bin/db2_srv6.1

I presume the above is fairly standard. Is this the file you were referring to?

We sent endless emails to Disus at the time of uninstalling their product but got fed up with the lack of response.

Regards

PJ

That does look normal (I don't know what nserver6.1 is but I assume it has nothing to do with that bshell checker).

What I would do now is try to run with some trace options: DBSLOG=077777 to trace your database actions and with -dbgobj and -dbgfdev and -dbgfile to trace the opening of files.

Regards,
Han

Has the bin/bshell6.1 been changed? Check to see if this is a binary or a wrapper script. I have seen some sites where the actual binary is renamed and the script is called from ipc_info.

I will bounce a message to my contacts at Disus if you will send me an email directly with your contact information.

-- Jim

It does not sound like this component was uninstalled correctly. Please contact me directly and we will assist you to resolve this issue. The support person on this product does not recall receiving any recent emails from any UK site? My email is: "chrisp@disus.com" or you can get me at the phone number below.

Chris.