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 usually do -INCLUDE procedures, but would prefer to keep this as is, as I EXEC this procedure and a few others in many applications. Hoping to limit my code remediation to those things that truly break going from v7.7 to v8! Will play with it again tomorrow morning...
What is P? If it's a string literal, perhaps the solution is to quote it? If it's not, then I'm not familiar with what you're doing and I'd appreciate a pointer
We use EX in WF8.1, also with parameters, and haven't seen the issue you describe. Then again, from the documentation it would appear that EXEC calls a maintain procedure, so perhaps not related to the issue? (-INCLUDE would be in the same boat though)
WebFOCUS 8.1.03, Windows 7-64/2008-64, IBM DB2/400, Oracle 11g & RDB, MS SQL-Server 2005, SAP, PostgreSQL 11, Output: HTML, PDF, Excel 2010 : Member of User Group Benelux :
So I would ask what you have within the focexec being executed? Also make sure that it is the one that you think it is by issuing the FOCEXEC extension of the WHENCE command -
WHENCE SET_CONN FOCEXEC
TThis message has been edited. Last edited by: Tony A,
In FOCUS since 1986
WebFOCUS Server 8.2.01M, thru 8.2.07 on Windows Svr 2008 R2
WebFOCUS App Studio 8.2.06 standalone on Windows 10
Posts: 5694 | Location: United Kingdom | Registered: April 08, 2004
Ahem (red faced), got back into this first thing this morning, and it looks like it's working fine, after all.
The EXEC version of the "Execute" command hits a procedure on the Reporting Server. From the Help:
"Note: When EXEC is used in Managed Reporting, it is important to note that there is a difference between EX and EXEC. EX statements coded in a procedure are processed by the WebFOCUS Client, which looks for the procedure in the Managed Reporting repository. Procedures that are referenced with an EXEC statement are not processed by the WebFOCUS Client, they are only passed to the WebFOCUS Reporting Server for processing, and these procedures are not looked for in the Managed Reporting repository."
By the way, I wrote that SET_CONN procedure so that I can dynamically connect to our Dev, QA, BA, or Prod database "on the fly" with one set of metadata files. Take a look at "Parameterizing Master and Access File Values Using Variables" in the Help.