Hi,

I'm running session tipcs5201m000 Generate Planned PRP Orders with system performance boosters set up.

When I execute the process from session, all shells are opened and the process concludes correctly, for this I setup my user and password on the BW and check box as default in BW Configuration.

I added the session tipcs5201m000 on a Job, and when I started with session ttaad5203m000 - Activate Jobs, the session also runs with multi shells on parallel and concludes correctly.

But actually I want to run the job via Unix with rc.statjob, but when its executed indicates runtime error, and the /baan/bse/log/log.comdll0200 file indicates:
root710;tipcs5201m000();client:Unable to start server(s) 1,2,3,4,5,6,7,8,9,10,11,12 after timeout of 120 seconds.
root710;tipcs5201m000();ppmt123ib:Unable to start server(s) 1,2,3,4,5,6,7,8,9,10,11,12 after timeout of 120 seconds.

Is there something else to be configured in order to run parallel shells from UNIX. :confused:

Thanks

Not that I am aware of. Most of our batch job is below. We had something like that happen to us after a servicepack. We worked with infor to get it resolved. Been too long for me to remember the solution. And we no longer run it since we converted to Oracle.

#!/bin/sh
#
USER=bsp; export USER
TERM=vt100; export TERM
MAX_RETRY=1000; export MAX_RETRY
RDS_FULL=100; export RDS_FULL
ORA_MAX_ARRAY_FETCH=100; export ORA_MAX_ARRAY_FETCH
ORA_MAX_ARRAY_INSERT=100; export ORA_MAX_ARRAY_INSERT
BSE_TMP=/tmp; export BSE_TMP
echo "Job W101_0 New Server Started at " `date` | mailx -s
cd /apps/baan/baaniv/bse/etc
./rc.startjob W101_0
exit 0

Thanks Mark, Just one question.

If I run on Unix the rc.startjob, how is related the windows BW to the Unix session, how its supposed to open the session or how is the setup?

Or in Unix I have to define something to indicate BW user passsword to be able to open multiple shells?

I'm confused

Thanks!

Not sure I get the questions - but in UNIX the way I recall it was the job is run in the background. There is no client to connect to - so things like client2server, etc. do not work. It is just running the session as described in the job.

The job I posted using runs our weekly GRP run with tipgc5201m00b - the only thing we ever used boosters on that I recall. So looking at the job there is nothing special to be done for multiple shells. I do recommend logging a case with infor on this - we had something like this 3 or 4 years ago. If I recall correctly they would time out also, but I am not sure. Infor worked with us until we had it working.

Thanks Mark, I'll log a case with Infor to work on this.

Regards