Just curious to see how different people have set up their automated jobs in Job Management. Do you set up an entry for each time period when jobs run (ex. Monday, Night, Month-end, etc.) or do you do it by session (ex. Process Delivered Sales Orders, Post Integrations, Process Hours Accounting, etc.)? Or do you do it a different way. What are the pro's and con's of your setup?

We're re-evaluating the way we have them set up and just looking for some info.

Thanks!

I manage all of my jobs via cron. In job management my job has a period of 1 minute and it is periodical.

The benefits are that if a problem occurs i can easily stop and restart the job.
I can manage dependencies by a fancy shell script that i wrote. And i can
easily manipulate performance variables like ORA_MAX_ARRAY* for specific jobs. Plus it's easy put traces on.

The only downside as far as i'm concerned is that it takes 1 license / job instead of 1 license / company (how it works with the Job daemon)

Also Cron never mysteriously "hangs" ;)

Dave

We have jobs defined and set per (group of) precess(es), i.e. all the sessions of the cycle for processing certain orders, all the certain report sessions of one category, etc. Some jobs contain only 1 or 2 sessions, others more than 30 (for instance when one printing session has to be executed several times, with different parameters..).

All the periodic jobs are scheduled and executed through the Windows task scheduler

Just curious to see how different people have set up their automated jobs in Job Management. Do you set up an entry for each time period when jobs run (ex. Monday, Night, Month-end, etc.) or do you do it by session (ex. Process Delivered Sales Orders, Post Integrations, Process Hours Accounting, etc.)? Or do you do it a different way. What are the pro's and con's of your setup?

We're re-evaluating the way we have them set up and just looking for some info.

Thanks!

Hello,
we have built our job managment based on business procedures and need.
(hourly , dayly , weekly , montly)
Some jobs only have 2, some 20 or 30 sessions.
All jobs are handled by an specific "job-users" cron. Every BaaN company has its own job user, so it is posible to manage the jobtime independent for each company.

Regards

We use the Baan job manager and use calenders for jobs which cannot be covered by the standard periods within the Baan job manager (ie. a job which needs to be run Monday and Thursday night).

We set the calenders up initially by using Exchange on the tools table ttaad507 to import the dates and times.

Cheers
Neal