Go Back > Forum > Baan Quick Support: Functional & Technical > Tools Administration & Installation

User login

Frontpage Sponsor


Google search

How big is your Baan-DB (just Data AND Indexes)
0 - 200 GB
200 - 500 GB
500 - 800 GB
800 - 1200 GB
1200 - 1500 GB
1500 - 2000 GB
> 2000 GB
Total votes: 33

Baanboard at LinkedIn

Reference Content

Thread Tools Display Modes
Old 12th February 2002, 07:17
julia0726 julia0726 is offline
Join Date: Oct 2001
Posts: 58
julia0726 is on a distinguished road
Baan: Baan IVc4 - DB: Informix - OS: IBM AIX
Question Inquiry on running jobs using job daemon and rc.startjob

Hi all,

Has anyone executed a job using "Job Daemon or rc.startjob" instead of their currently used "Activate Job"?

I have tried executing Job Daemon or rc.startjob in our office but it seems not working.

The following were the steps I have done please advise if I missed anything here.

1. Run the session Maintain Calendar. Create entry on this session e.g. TIME
2. Run the session Maintain Dates by Calendar. Create entry for the date and time.
3. Run the session Maintain Job Data with the following entries.

Desc: test job
User: bsp
Creation Date: 02-08-02
Periodical: yes
Job waiting after Execution: yes
Calendar: TIME
Period: 0
Finish Date:
Next excution date: same as Finish date
Maximum duration: 0
Status: Free
4. Make job for session to be executed:
I set the device to printer and also tried ASCIF (output to file)

5. On the command line I login as root and execute the command:
# rc.startjobdm.TEST

Please advise.


Reply With Quote
Old 12th February 2002, 10:00
Han Brinkman's Avatar
Han Brinkman Han Brinkman is offline
Join Date: Aug 2001
Location: The Netherlands
Posts: 1,158
Han Brinkman has a spectacular aura aboutHan Brinkman has a spectacular aura about
Baan: All - DB: Oracle/ms-sql/db2 - OS: *nix/windows


Most of the time you have to edit both scripts before they work. You have to specify the user in which it has to work. THe users should have the company as default in which the jobs are specified.

Furthermore the jobdm is really a deamon. You only have to start it, all jobs will start automaticly if the have the status 'in queue'.

For rc.startjob you have to change the user as well. That one you have to pass the name of the job since it only runs one job. The status of the job should be 'free'.

With the jobdaemon you should see a bshell ttaad????m000 process running, it also creates a application lock.

If it doesn't work, check the scripts, they write some logfiles which you can check.

Reply With Quote
Sponsored Links

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Job Daemon Hanging / Using crontab to run sessions from command line? rmarles Tools Administration & Installation 21 6th June 2018 14:47

All times are GMT +2. The time now is 22:07.

©2001-2018 - -