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.
in multiple discussions I read about SET ALL = SQL. I can find information about SET ALL = OFF/ON/PASS but nowhere about SET ALL = SQL. Has somebody a hint?
Regards RonThis message has been edited. Last edited by: FP Mod Chuck,
I have to generally agree with Was here. SET ALL=SQL is not documented in the Command Language Reference all the way up to 8203.
So what happens is, if you decide to use it, and you have any problem in your code and ask for help from techsupport, they can tell you that you are using an undocumented feature and so there is no support for that. That leaves you really on your own.
Better to stick with things that are documented so you can tell IBI you're following the rules and things still don't seem to work right.
In that situation, IBI must pay more attention to your case because you are doing things that are in the docs.
Just be aware that your support options drop off pretty quickly if you're using undocumented commands.
For example: FPRINT is a great function to convert numeric data with decimals, not documented and I'm having issues with it 8202. Had to add that to the upgrade plan.
One other thing, I see this when there is an error with SQL Passthrough;
..... END -RUN ALL=SQL IS IGNORED, SUPERSEDED BY SHORTPATH=SQLThis message has been edited. Last edited by: Don Garland,
Thnx for all the input guys. I was just curious, because I couldn't find it anywhere. Now I know it is an undocumented feature. Maybe better not use it.