Good Afternoon,

I have a series of Report Caster jobs that are set up to create daily hold files, these jobs are coded so that they know we have processed our daily load and that the current hold file is 1 day or more older than the current date.
If both of the statements above are true, the hold files will run and the previous day’s hold file will get overwritten. If current date = the load date and the current date = the hold file date, the fexes are set to not to execute, this works fine.

What I am having trouble with is that I have report caster set to run every 5 minutes and due to the number of fexes creating hold files, my report caster job takes about an hour to an hour and 15 minutes to process, so what happens is that report caster is not smart enough to know there is already a report caster job running the fexes or that there is a report caster job in the queue to run the fexes, instead another RC job kicks off, thus I get several RC jobs processing my hold files simultaneously.

I don't want to set RC for a specific time each day because I want RC processing these files as soon as our daily load finishes, this is normally between 3:00am and 6:00am. So what I am trying to figure out is if there is a way to create a procedure to tell report caster if there is currently a job with the same name that has already launched but not finished to not launch another job until the current job has finished, regardless of the RC interval run time setting.

This message has been edited. Last edited by: Kathleen Butler,

How about adding a Pre-processing Procedure to verify a database table date or some other indicator - then use the &&KILL_RPC Flag to stop processing?

Check the ReportCaster Development and Administration manual.