Guys, you should not be using job daemon. Job daemon is buggy and hard to implement in a multi-company environment which, I think most environments are multi-company.
I would suggest that you look at implementing jobs via the OS native jobs scheduling mechanism, e.g., Task Scheduler for windows, CRON for UNIX.
Also, do you guys know how annoying it was on windows servers to schedule jobs and see the windows constantly pop up? In recent porting sets Infor development enabled a way to start jobs using a parameter -server so in the startjob script there will be a line now that is
ntbshell -server ttaad5203m000
Way cooler than starting the .bwc profiles. It makes for a nicer administration of the server without fearing cancelling a crucial job in a live system as all jobs run silently this way.
Only disadvantages are, apparently you cannot use multi-bshell jobs with this method. But there are workarounds for that like setting those jobs up in a different server or PC even using the old method.
Hope this helps.