I have a Baan job that executes session ttadv6420m000 (Print software components per package vrc) for every pvrc combination. This means the session is executed 12 times with different settings.
When I execute the job it freezes after executing about 2 to 4 sessions.
I checked ttaad500, 501 and 503 but they all seem ok.
I placed a trace on the job to find the problem but with the trace on the job it runs perfectly.
I placed a Unix sleep command after every job step to slow things down a bit but that didn't help.

Any suggestions what might be the problem here ?

thanks,

Walter

Hello,
Does the job consistantly freeze on the same session or a different session ? Is the job being run through the activate job session or is it just running through the job queue ?

Cheers
Neal

Hello Neal,

Most of the time it freezes on the same session. But when I activate/deactivate some sessions it freezes on another one.
The problem occurs both runnnig the job from the crontab or starting it by manualy with ttaad5203m000.
I am superuser and all permissions have been checked.

Going back to real basics do you get any unusual behaviour when you run the sessions manually and what device are you printing to ?

Cheers
Neal

When I execute the session with the same settings everything works fine.
All output per job step is written to an ascii file in $BSE_TMP where the filename reflects the name of the printed pvrc.
For those job steps that don't freeze it works just as I intended it to.

Output example:
-rw-rw---- 1 wg01 bsp 22372 Jan 30 13:54 ccB40Cc3lacc
-rw-rw---- 1 wg01 bsp 1134 Jan 30 13:54 ccB40Oc3live
-rw-rw---- 1 wg01 bsp 64872 Jan 30 13:55 ccB40Pc3pcm2
Where : cc = package, B40? = version, c3 = release, lacc etc = customer.

This time ccB40Pc3pcm2 freezes up after printing the last lines of data.

I did some more testing and guess what.
When I repeatedly print to an ascii file from any tools session, it tends to
freeze. So it has nothing to do with my job.

There was an error in our shell scripts that's executed by our ASCIF device.
It contained a path of our previous server.
It's solved now but I don't understand why it sometimes does and sometimes doesn't work.