I need to know what the correlation is between the email distribution list in report caster and the email addresses listed in the botdest table. We have a web page that allows users to enter the burst values and email address (for distribution) that get inserted into the botdest table. The fex report that is generated, gets scheduled in reportcaster. I want to know if it is necessary to manually enter the email addresses into reportcaster when it is already in the botdest table. How does this work?

Thanks.

BOTDEST is where Report Caster stores the email addresses in distribution lists. So if the addresses are put there by something else, they are "in" report caster.

Do you know if there is any way to filter a report using a where clause in my fex that gets scheduled? I want to be able to filter on a range of values.

Thanks!

Don't know if this is related to your first question or not. And I'm not quite sure what the second question is. Report Caster runs the fex that is scheduled. If there is a WHERE clause in the fex, the data is filtered. If not, there is nothing else in RC that lets you add additional filters.

One way around this (there is always a way around things) that I frequently use when a job is run both on-demand and through RC is the following. I add an additional parm called &RCRUN and use -DEFAULT &RCRUN='N' in the fex.
By default, all the code, WHEREs, etc. that will be used ONLY by RC are skipped, branched around, an so on by testing the &RCRUN parm. Then when I set up the job in RC, I add the parameter value of 'Y' to the RCRUN &var under the advanced tab, along with any additional values or ranges of values to be used.
If it is run in RC, it uses additional filters. If not in RC, it does not use them.

Thanks Darin. I will give it a shot. Thanks for you help.

quote:

-DEFAULT &RCRUN='N'

Darin,

You could always use -SET &var = IF &DSTSCHEDID.EXISTS EQ 0 THEN 'N' ELSE 'Y' ;

T