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 was trying to debug an issue with a fex run via Report Caster. As we all know, things are different when run via Report Caster versus running online. One thing that's different is that SET MSG=ON does not provide the expected feedback in the task log.
This caused me a great deal of hardship yesterday.
Anyone else notice this? Has it been this way forever, or is this new bad behaviour?
Thanks,This message has been edited. Last edited by: Francis Mariani,
Francis
Give me code, or give me retirement. In FOCUS since 1991
Production: WF 7.7.05M, Dev Studio, BID, MRE, WebSphere, DB2 / Test: WF 8.1.05M, App Studio, BI Portal, Report Caster, jQuery, HighCharts, Apache Tomcat, MS SQL Server
Hi Francis, Up the line limit in the Admin console and turn echo on. We have to -TYPE &LINES after each step to see if the amount of data is correct and the JOINs are working correctly... Tom
Yep, I think the default is 1000 lines; we bump it up to 100,00 when we need to debug, then bring it back down once the fex runs properly... We'll turn the echo on/off once the step completes correctly, but, keep the -TYPE &LINES