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'm getting the following error message when trying to put the results of a stored procedure into a hold file. For one database the hold statement works fine, but for the other database I get the error. My only assumption is that the database2 connection setting is different somehow. Any ideas?
So for database1 the hold works the way it should....
SET SQLENGINE = SQLMSS SQL SQLMSS SET DEFAULT_CONNECTION DATABASE1 SQL SQLMSS EX DATABASE1.dbo.db1StoredProcedure;
TABLE FILE SQLOUT PRINT * ON TABLE HOLD AS DB1SP END
but for database2 the hold throws error "SET SERVER DATABASE2 COMMAND FOR SQLMSS INTERFACE OUT OF SEQUENCE", and this error appears twice.
SET SQLENGINE = SQLMSS SQL SQLMSS SET DEFAULT_CONNECTION DATABASE2 SQL SQLMSS EX DATABASE2.dbo.db2StoredProcedure;
TABLE FILE SQLOUT PRINT * ON TABLE HOLD AS DB2SP END
If I remove the hold statement for DATABASE2, then the statement runs fine.This message has been edited. Last edited by: Web Guy,
I think you need a -RUN after the first END statement.
I've also cleaned up your code, though I can't test the updated code. You can set the SQL engine once. Then, since you've set the SQL engine, you don't need to specify it in subsequent SQL pass-through calls. And (I think) since you specify the database name in the procedure call, you don't need to set the default connection, though I haven't tested this...
SET SQLENGINE = SQLMSS
-RUN
SQL EX DATABASE1.dbo.db1StoredProcedure;
TABLE FILE SQLOUT
PRINT *
ON TABLE HOLD AS DB1SP
END
-RUN
SQL EX DATABASE2.dbo.db2StoredProcedure;
TABLE FILE SQLOUT
PRINT *
ON TABLE HOLD AS DB2SP
END
-RUN
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