Hi,
I am working for starting connetware driver in back ground.
I am able to successfully start the driver by running unix shell program bnddc.sh and able to do the transactions. But the problem here is:

when I start Driver in back ground:

1. I start the function server and do some successful transactions.
2. I do transaction to get timeout error.
3. after I do successful transactions and it works ok!
4. If I do any unsuccessful transaction (such as which returns a message to connetware back like "Location blocked for warehouse" etc..) Connectware hangs.

But when I start Driver in foreground (through baan): everything works fine.

Problem Description (Technical terms)
While the bshell is running in background mode, data is still being written to ds_outstream and/or ds_instream. Since a data is not being picked up off of these, the limit is reached on that stream and no more processing is done.

Workaround
Run DDC in foreground mode.

Test Procedure
Ran ddc in background mode processing many more transactions than were previously processed.

Motive source
DF:212605

You would have to contact BaaN support and get the latest porting set for your BaaN Version.

Hi Prasanth,
I already verified that issue. But my problem is not stopping all transactions. After timeout error, all successful transactions are going fine. Only first unsuccessful transaction making driver to hang up. But when I ran in foreground mode it works fine. Only difference I observered is: DDC_LIST_START. Logs from Baan side are same for successful and unsuccessful transactions.