bkkland
30th August 2006, 20:38
How to create job with job daemon?
I have created job and status is "in queue", but it's never executed. Why? Please advise what did I miss?
Thank you so much!!
Kozure Ohashi
31st August 2006, 12:34
Dear bkkland,
what is your OS (missing in the profile).
Either on W2003 Server you have to start the Jobdaemon with the graphical Interface. (In former times it was called "baan windows nt manager"... i guess)
On Unix you have to start the jobdaemon. This will call your jobs "in queu".
Unix$> ps -ef | grep ttaad5260m000
(To check if it is already running). If not add it e.g. to the correct crontab.
Regards,
Kozure
mostrightfuture
31st August 2006, 16:12
HI Kozure Ohashi,
I have also the same problem, the Job daemon is started with the graphical UI called "Baan NT manager", but the job status is always remains "In Queue" and it never executed.
MRF
mig28mx
31st August 2006, 19:59
In your case, I suspect you have not started the job daemon.
You should started from Unix, using the comand:
$ rc.startjobdm
Doing this, every job with the status, in queue. Will be executed as per job defined.
Another way to run jobs is put the job as inactive and run from unix with the command:
$ rc.startjob "job"
If after this you are unable to run jobs, try to stop the jobdaemon with:
$ rc.stopjobdm
and restart the job daemon.
Hope this helps.
bdittmar
2nd September 2006, 16:04
How to create job with job daemon?
I have created job and status is "in queue", but it's never executed. Why? Please advise what did I miss?
Thank you so much!!
Hello,
sometimes the execution date and/or time of the job may cause a problem.
Please edit your profile with DB and OS. The help will be much better.
Regards
kaukul
7th March 2008, 06:31
Hi,
We r using "ERP LN FP2" with Windows 2K3 and SQL 2005.
When we start job manually using activate jobs, job executes at scheduled time, but it does not execute when kept in queue. BaaNJobdaemon is already active in services.
Regards,
Kaustubh
kaukul
7th March 2008, 10:17
I am able to schedule job management for single company...:) We are starting the service with a user ID that has default company same as the one we want to start the job in.
But can you tell me how to shedule jobs for multiple companies?
pconde
7th March 2008, 11:10
hi,
This is a common rule for baan you must have an user for each company: he can then start the jobs for this company but not for other companies.
Regards
Philippe
kaukul
7th March 2008, 13:11
yes, i have created diff users for diff companies...
but how to start multiple daemons in windows??
NPRao
7th March 2008, 20:48
but how to start multiple daemons in windows??
Kaustubh,
Please use search option to look for already discussed topics. Refer to the thread - Configuring Jobs (http://www.baanboard.com/baanboard/showthread.php?t=48116&highlight=job+windows)
Create a multiple Startjob.bat for every company/BWC.
kaukul
8th March 2008, 06:14
Thnx NPRao,
But my query is not answered in that thread. I am looking to run multiple job daemons, one for each company. Right now, I can run only one Job Daemon (which is for 000 company).
Is it possible to run multiple services in windows for multiple companies OR can any one tell me how to configure and run services via ASM?
Thnks in advance...
NPRao
10th March 2008, 21:31
Kaustubh,
Based on Hans & Murphy's notes from the thread, you can create a copy of startjob200.bat into startjob300.bat and run multiple job daemons for different companies. And make sure to create a bspxxx account for xxx company so that you have a unique batch account.
kaukul
11th March 2008, 06:51
Hi,
They r suggesting to run multiple Jobs (startjob.bat in $BSE\bin) and I am looking for multiple Job Daemons (jobd.exe in $BSE\bin).
Right now, I have started service BaanJobDaemon which executes the executable "jobd.exe" with login "job000" (000 is default company).
I need to run such services for at least 2 more production companies. One way could be to "share Job tables between these companies" and start Job Daemon with that company user.
But, I want to know and want to set if it is possible to have multiple "Job Daemon" services running on server...
Han Brinkman
11th March 2008, 08:43
As far as I know it is not possible to have multiple jobdaemons running.
Han
Kozure Ohashi
11th March 2008, 09:55
As far as i remember:
* edit all jobs in company 000
* run it with a juser from company 000
* in session ttaad5101m000, mask 2 you can define for which company you want to run the session.
Result: You should be able to run the jobs for e.g. company 100, 200, 300 , 400. But the root is company 000.
Regards,
Kozure
Han Brinkman
11th March 2008, 16:01
Kozure,
What you describe results still in one jobdaemon and that's not what Kaukul wants.
I haven't tried to use multiple jobdaemons since I prefer to use an external scheduler to run my jobs. Even not sure if it's possible.
Han
kaukul
12th March 2008, 04:56
As far as i remember:
* edit all jobs in company 000
* run it with a juser from company 000
* in session ttaad5101m000, mask 2 you can define for which company you want to run the session.
Result: You should be able to run the jobs for e.g. company 100, 200, 300 , 400. But the root is company 000.
Regards,
Kozure
Fo this, you have to share tables among companies and it is not possible to share tables between tools company and production companies, as the package combinations are different among them.
kaukul
12th March 2008, 05:05
Kozure,
What you describe results still in one jobdaemon and that's not what Kaukul wants.
I haven't tried to use multiple jobdaemons since I prefer to use an external scheduler to run my jobs. Even not sure if it's possible.
Han
We are able to run multiple job daemons on Unix server with BaaN IVc4:
We have created shell scripts like rc.startjobdm.<company number> and inside them, we are exporting user data.
In ERPLN + Windows, we are configuring a scheduled task that will start the Job Daemon with user having Production company as default one, but that is not working.
Han Brinkman
12th March 2008, 12:18
Thanks for sharing about the multiple jobdaemons.
However it's not something I prefer:
1. each jobdeamon uses a license;
2. bad performance if you run multiple jobs at the same time in one jobdaemon.
The advantage of it is that your users are able to schedule jobs. (If that is what you want.)
Regards,
Han