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.
I have an application where the user enter parameters for a report. I load these parameters in a .foc file along with their userid and a processed_sw. We use a .foc file so we can keep a history.
I have set up a RC job that runs nightly. The RC job has a pre-processing step that reads the file looking for any unprocessed rows. If the count is 0, I set &&KILL_RPC to 'Y', the rest of the job is not run and the job is then rescheduled for the next night. If a row is found, the job is run and the excel output is emailed to the user. After the job runs, a post-processing fex is run to update the processed_sw of the request just run.
What I need to know is, is there an easy way to have the post-processing fex, resubmit the job? That is, I want the RC job to basically keep running itself until all of the requests have been processed.
I know I could process all of the requests at one time and burst the reports on userid to get each user their report. But a user could make multiple requests and those requests need to be kept separate, so I don't see bursting as a viable option.
Thanks.
In FOCUS since 1985. Prod WF 8.0.08 (z90/Suse Linux) DB (Oracle 11g), Self Serv, Report Caster, WebServer Intel/Linux.
Posts: 975 | Location: Oklahoma City | Registered: October 27, 2006
Hello, I'm very new to this forum, so execuse me if I'm asking wrong question. It looks like you keep track of records processed by RC and I'm looking for similar functionality: We are going to use ReportCaster for daily distribution of report. We don't want to send duplicate reports every day. The option we consider is to mark (Flag) records somehow in Database that such and such records were already sent. Is there a way to write Flag into SQL Database from WebFocus report (can we insert/update records in database from report)? If 'No', how can we avoid sending duplicate reports? Thank you. WF 7.1.6; SQL 2005; Report Caster
WF 7.6.4, Win XP, SQL 2005
Posts: 42 | Location: California | Registered: August 17, 2007