Pavel Votava
21st April 2009, 13:08
I am new in INFOR ERL LN 6.1 and I have problems with job daemon. How can I enable and start job daemon on a Windows platform for more companies?
I use the Application server manger to manage Job daemon service. I am able to create a job daemon entry for one company, but I am not able to do it for more companies. Can anybody help me? I need an exemple how can I solve my problem.
Thanks.
Pavel Votava
Han Brinkman
22nd April 2009, 09:47
Hi Pavel,
If you want to use the jobdaemon for more companies than you have to use logical tables, i.e. share the job tables (ttaad500 - ttaad513 (not sure about the number)) to the physical company in which the user is logged in that's running the jobdaemon (probably baan).
Please search baanboard to find out about the pro's and con's using the jobdaemon.
Regards,
Han
toolswizard
22nd April 2009, 17:01
Don't use the Job Daemon if you need more than 1 company. You need to create command line files with the company to be run in the company variable, possible the user variable and package combination set, and a line to run the bshell with the job session as the process to run. Then schedule this with the windows scheduler. In windows explorer open your server, then the control panel, and you will find an icon for scheduled tasks. You will find an icon to add the task there for your command file.
Han Brinkman
22nd April 2009, 17:38
I agree that you probably should not use one jobdaemon for multiple companies for reasons mentioned before in other threads. However that's up to Pavel.
toolswizard
22nd April 2009, 18:45
If you want to run the same session for multiple companies, then it is suggested to use logical tables. When you want to schedule seperate runs for the companies, then it is suggested to use ASM or a native scheduler.
Instructions can be found in the ERPln Administrators Guide U8854 Chapter 12 for the 3 variations. I'll have to dig up a newer admin guide for Baan IV to see if it is mentioned there also. In the event of needing to postpone a run, rerun, or timing, my clients have found that individual job streams work best.