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 mate, At my previous site we got around this problem by having a Control table that marked the program name as running = Y and the start and end date. We ran the etl's every 20 mins and also set a limit on how many each Rcaster task would take. So when the next job started it could process new table updates as it would query the Control table and know that the updates were still in progress or complete. One Control table on the Source system had Date / Time stamp. The NT server had the same table and compared the dates thus knowing if an extract was required and the other NT Control table was then checked to see if a prior task had already flagged the job as underway. This solved our issue for long running updates.
Webfocus Release 7.6.11 Unix EXL2K
Posts: 5 | Location: Rhodes | Registered: October 27, 2013
Hi mate, At my previous site we got around this problem by having a Control table that marked the program name as running = Y and the start and end date. We ran the etl's every 20 mins and also set a limit on how many each Rcaster task would take. So when the next job started it could process new table updates as it would query the Control table and know that the updates were still in progress or complete. One Control table on the Source system had Date / Time stamp. The NT server had the same table and compared the dates thus knowing if an extract was required and the other NT Control table was then checked to see if a prior task had already flagged the job as underway. This solved our issue for long running updates.
Webfocus Release 7.6.11 Unix EXL2K
Posts: 5 | Location: Rhodes | Registered: October 27, 2013