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 firstname.lastname@example.org for further assistance. Reference the community FAQ to learn more about the community.
Unfortunately you're an 7.1.3. In 7.6 and 7.7, there is an option for Default Processing for No Report to Distribute. You can set it to be treated as a Warning instead of an Error.
One option is to set the Notification in the schedule to Never. Then, write your own report to read the RC logs and create/distribute an error report. You can set it to run once a day to multiple times during the day.
Another option, but this would require changing each program, is to SET EMPTYREPORT = ON so that at least a heading is produced. Possibly you could add the SET command to your edasprof.prf.
WebFOCUS 7.7.05M, gen 144, Windows 2008 Server R2 64-bit, Tomcat 6.0.33, IIS 7.0, SQL Server, Excel 2013, PDF, HTML, FOCUS files.
Posts: 88 | Location: Seattle | Registered: March 29, 2007