So I have a few reports that I need to FTP burst to different locations. They will all be bursting on the same burst VALUE, but depending on what report it is, each report will have a different DEST. Is it possible to have a compute field in the fex that creates the dynamic list:


TABLE FILE LIST
PRINT VALUE
COMPUTE DEST/A20V = '/Home/' || '&FOLDER_NAME' || '/' || VALUE || '.pdf';
ON TABLE PCHOLD
END

and have &FOLDER_NAME come from the main fex?

I tried to provide this as a parameter in the schedule under Task/Paramaters but without any luck.
I also tried to create a hold file in the main fex and access it from the dynamic list fex but to no avail. Is this even possible?
The fex that creates the dynamic list, is it run before or after the main fex?

quote:

Is this even possible?

My favorite anser to this is: Yes, we can do that in WebFOCUS.

I create the Dynamic Distribution List (DDL) in "the main fex" which creates a XML file which in turn is used as the DDL in the Distribution section of the RC job.

Great. Glad to hear its possible. A noob follow up question then:

So if the main fex is creating the list on the fly, how do you reference that in the Distribution section of the RC job?

Hi,

Refer to below forum posts. You need to use RC system variables to get necessary details.

Page 12 of below best practice document.
http://documentation.informati...stpractices_7611.pdf


http://forums.informationbuild...087036216#4087036216


Hope this will give you an idea. At runtime, reading BOTSCHED and BOTPARAM table using SCHEDULEID you can meet your requirement.

Thanks,
Ram

This message has been edited. Last edited by: Ram Prasad E,

Hi Ram,

Thanks for the document.
It seems however that those RC parameters like &DSTSCHEDID are available in the procedures called from the tasks in the RC schedule, but they are not available in the fex called to retrieve the dynamic list (the Dynamic Address Procedure in the Distribution tab of ReportCaster). Or am I wrong?

It occasionally happens to us if two RC schedules finish about the same time that one schedule will use the dynamic list created by the other schedule.
Do you have a way to prevent this?

Martin.