Hi there. I've been struggling the last 3 days trying to make Job Management work. Hope you can help me.

(1) When I click on "continue" in session "Activate Job", the status changes to "Waiting" and this session hangs indefinitely on my screen. I leave it overnight and discover the ffg morning that my job did not execute as scheduled.

(2) In session "Maintain Job Data", the status is "Free", I go to unix prompt and enter the command rc.startjob "myJob". The status remains "Free" and my job would not execute still.

what could be wrong? - thanks in advance:confused:

What version of Baan are you on, moroni? I have never seen a session activate job, I only know it as a command in job data, so I suspect you are on one of the newer releases.

Never the less, let me try to shed some light on this.

(1) The job status switches to waiting _after_ execution of the job when the 'Job waiting after execution' flag is checked in job data. I have never found the purpose of this option, maybe somebody else can explain that one.
What do you use to kick-off your job? When using the job daemon, the status of the job needs to be set to queued. When using cron or another scheduler, the job status need to be 'free'.

(2) Check the file rc.startjoberr in your tmp directory. That might give you some indication of what's wrong. if the file has not been (re)created, check the ownership of the file. If your account cannot overwrite that file, it will prevent rc.startjob from successful execution.

Hope this helps.

Hi francesco,

thanks for the reply.

Your remarks regarding rc.startjob really helped.

I just have one clarification. Will my job execute: (1) if there is no more available user license ("maximum users reached")?, (2) I am not logged in to baan?

Hi moroni,

Another tip for you if the, scripts attached to your sessions might be compiled in debuggers so it expects someone to click continue to proceed further.

you can use the bshell or the ba options like nodebug...


bshell6.2 -nodebug -server -set BSE_COMPNR=910 -set PACKAGE_COMB=b52astg ozmadmtest


and if you are in the older baan releases you might try this -

ba6.2 -- -nodebug ozmadmtest 2>${BSE_LOG}/test.log.$$
|* invoking a 3-GL script as a background process

ba6.2 -- -nodebug ttaad5203m000
|* activate the job session

Let me think here...

On 5b (and earlier versions), the job daemon uses ba6.x, rc.startjob uses a bshell (or is it the other way around? I always forget). ba6.2 does not consume a 'heavy' license, although during my latest licensing round with Baan, they told me that Baan no longer distinguishes between light and heavy users. (ba vs bshell).

If you are out of licenses, and your execution method requires one, the job will not execute.

You do not have to be logged in while executing a job (come to think of it, if you have restricted multiple logins and your job execution method uses an account that is logged in already then this might be another reason for faillure).
rc.startjob will go through the regular channels (ipc_info -> startscript -> bshell) to establish a connection.