As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only.
Join the TIBCO Community TIBCO Community is a collaborative space for users to share knowledge and support one another in making the best use of TIBCO products and services. There are several TIBCO WebFOCUS resources in the community.
From the Home page, select Predict: WebFOCUS to view articles, questions, and trending articles.
Select Products from the top navigation bar, scroll, and then select the TIBCO WebFOCUS product page to view product overview, articles, and discussions.
Request access to the private WebFOCUS User Group (login required) to network with fellow members.
Former myibi community members should have received an email on 8/3/22 to activate their user accounts to join the community. Check your Spam folder for the email. Please get in touch with us at community@tibco.com for further assistance. Reference the community FAQ to learn more about the community.
Hi, We are storing the Burst value and email address in a table for each schedule name. We created a Fex based on this table with a Parameter for Schedule_name sothat it brings back right email address for the related schedule. Then we created a schedule and selected Dynamic Addrees as the Distibuution list option and picked the above procedure, but it did not prompt for the Schedule_name parameter. Is there any thing special we need to do to get Dynamic Address Procedure Parameters prompted in Rcaster ??
Thanks, DDThis message has been edited. Last edited by: Kerry,
WebFocus 7.7.01 Desktop: Windows and Server: Unix Excel, HTML, PDF
I don't believe that you can have prompting in a dynamic address procedure. Everything it needs to run must be available within the procedure or available in an external file that can be read.
Regards,
Darin
In FOCUS since 1991 WF Server: 7.7.04 on Linux and Z/OS, ReportCaster, Self-Service, MRE, Java, Flex Data: DB2/UDB, Adabas, SQL Server Output: HTML,PDF,EXL2K/07, PS, AHTML, Flex WF Client: 77 on Linux w/Tomcat
Posts: 2298 | Location: Salt Lake City, Utah | Registered: February 02, 2007
To pass the schedule name from the main Caster job, we perform a -WRITE of the name to a temporay text file in BASEAPP.
The DYNAMIC distro fex picks up the name from BASEAPP by doing a -READ. The same fex then DELETES the text file.
Simple example using the CAR file:
-*Main Caster Job fex
-DEFAULTS &SCHED_NAME='CAR1'
APP FI SCHED DISK baseapp/SCHED.TXT
-RUN
-WRITE SCHED &SCHED_NAME
TABLE FILE CAR
SUM SALES
BY COUNTRY
ON TABLE PCHOLD FORMAT HTML
END
-* DYNAMIC Distro fex
APP FI SCHED DISK baseapp/SCHED.TXT
-RUN
-READ SCHED, &SCHED_NAME
!del e:\mreprod\ibi\apps\baseapp\sched.txt
SET ASNAMES=ON
TABLE FILE SCHED
PRINT EMAIL_ADDRESS AS DEST
BY VALUE
IF SCHED_NAME EQ '&SCHED_NAME'
ON TABLE PCHOLD
END
Note that IBI confirmed, by way of a case I just opened, that using FOCCACHE to store the text file will not work. I thought using FOCCACHE would be a cleaner method instead of doing a delete.
quote:
Here is the relevant documentation on use of FOCCACHE:
"Each time a WebFOCUS user logs into the Managed Reporting (MR) environment a new session with its own foccache directory is created. Files that were stored in a prior foccache directory are no longer accessible. When the user logs out of MR the foccache directory used within that MR session is no longer accessible."
In the ReportCaster environment, there is no common session between the main procedure and the procedure invoked through the dynamic distribution list. Therefore FOCCACHE cannot be shared in this situation.
The IBI help person said that this has already been opened as an NFR so I added our name to the request.
In the meantime, storing the file in BASEAPP (or other folder of your choice) seems to be the best/easiest/only way to pass the schedule name to the DYNAMIC distro fex.
David
In FOCUS since 1985 - WF 8.009/8.104 Win 8 Outputs: ALL of 'em! Adapters: Sql Server Teradata Oracle
Thanks for the confirm. We do the same for some of our jobs - write out the parameters used to run the main job and then read them back in for the dynamic distribution list procedure. The lack of a common session would also preclude from just using a hold/save file in edatemp as well. (Additionally, there is the situation where the dist list proc doesn't even run on the same server as the main proc).
Regards,
Darin
In FOCUS since 1991 WF Server: 7.7.04 on Linux and Z/OS, ReportCaster, Self-Service, MRE, Java, Flex Data: DB2/UDB, Adabas, SQL Server Output: HTML,PDF,EXL2K/07, PS, AHTML, Flex WF Client: 77 on Linux w/Tomcat
Posts: 2298 | Location: Salt Lake City, Utah | Registered: February 02, 2007