pemcgriff
18th May 2004, 15:59
I am running a RS/6000 AIX environment. When we run batch jobs we are using the Baan to determine the schedule. My understanding of how it works is that a job scheduled for midnight would run and complete then reschedule itself for the next day. This seems to tie up a Baan license for each job that is on the schedule nomatter when the job is suppose to run.
My problem is that we are running a seperate instances of Baan for each geographic location. Therefore, we are tieing up several licenses to do batch processing. It is also my understanding that there is no way to tell when a job actually completes.
Is there a more effecient way to run batch jobs?
bshow1
18th May 2004, 19:19
Are you using Job Daemon? You should only need one license for each job daemon instance (one per company).
We used to use Job Daemon, but found it problematic. We now schedule all jobs through Unix cron and start them with rc.startjob. This only uses a bshell while the job is actually running, and uses a separate bshell for each job.
I set all our jobs as "Periodic" with a period of 1 hour. When you use rc.startjob, the status must be "Free" and the current time must be on or after the "Next Execution Date" on the job.
You can tell when a job has run by monitoring the ttaad500, ttaad510, ttaad511, and ttaad512 tables. We have custom scripts that monitor these and page us if the job has errors, etc.
EdHubbard
18th May 2004, 23:39
Not applicable to you but in a Windows environment you can use the Task Scheduler and as the previous contributor says set the Baan job to periodical.
pemcgriff
21st May 2004, 20:14
bshow1 - would you be open to talking to us on how to setup the rc.startjob and monitoring processes?
If so please email me at pemcgriff@buckman.com.
Brendan Shine
21st May 2004, 20:48
On our Unix systems we put the following Baan qptool query into a shell script called every hour via cron that checks to see if any jobs in a particular company are present with a status of "Waiting", "Canceled", "Runtime error", or "In Queue" and then if so an e-mail is generated notifying the appropriate person(s).
$BSE/bin/qptool6.1 -c$compnbr -q"select jsta, user, cjob, ttaad500.desc from ttaad500 where (jsta=2 or jsta=4 or jsta=5 or jsta=6)" >> $DIR/JobStatusTemp.txt 2>&1
# STATUS (jsta)
# 1=Free
# 2=Waiting
# 3=Running
# 4=Canceled
# 5=Runtime error
# 6=In queue
# 7=Blocked
# JOB NAME (cjob)