I change bshell in ipc_info with ibshell.
When I try to start a job with ba6.2, I have the following messages:
Connecting with bshell...
ba6.2: Server 'bshell' not listed in ipc_info file.
ba6.2: cannot get the hostname of the server
ba6.2: ba6.2 failed to connect to bshell


Is there an option for ba6.2 to use ibshell instead of bshell ?
Thanks.

Basicly it should work, however on NT I have not accomplished it, if I am correct you should have an executable ibshell. On Unix a script will work.
On the other hand, ba6.2? It only used anymore for the jobdaemon, removing appl. locks etc. The ascii interface is no longer supported in BaanERP.

Kind regards,
Han

you're right, i'm using ba6.2 for the jobdeamon.
we have BaaNERP 5.0 b on unix

I am not so sure whether this will work without setting a specific environment variable. It might very well be that the ba6.2 executable is referring to the 'bshell' entry in $BSE/lib/ipc_info in a hard-coded way and that it is only possible to change the executable that the default 'bshell' entry is pointing to.

It works for BW - as you can specify the bshell variable but I have never tried getting it to work for BA.

and here is the line we've changed in ipc_info:

ibshell s 0 0 p ${BSE}/bin/bshell6.2

As stated in my previous post, the first part of your entry might be the problem:

ibshell s 0 0 p ${BSE}/bin/bshell6.2

What works for sure is something like:

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

- or -

bshell.new s 0 0 p ${BSE}/bin/bshell6.2_new

However the question is if the second alteration also works the BA or not. The ba6.2 executable might require:

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

I found a solution on BGS (110908). It says to set the environment variable DS_AS to the bshell name.
For my example: export DS_AS=ibshell.
I haven't try it yet...

That should work for sure. In the bw settings you have the option to specify the name of the bshell entry in ipc_info, for ba you have to set the environment variable.

Kind regards,
Han

I know the DS_AS environment variable but the use of it has always eluded me. The default $BSE/etc/rc.startjob script for instance has following line in it:

export DS_AS=ba
Now there's no ba entry in the default ipc_info so how does it match up?

We used a copy of the rc.startjob script adding this line:

DS_AS=ibshell ;export DS_AS

and we added this one in ipc_info:

ibshell s 0 0 p ${BSE}/bin/bshell6.2

and now we can use ba6.2 with the session ttaad5203m000 !!

Thanks everybody.

Somehow Baan makes it all work though not everything makes sense :) Yet something new learned again!