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. Moving forward, myibi is our community platform to learn, share, and collaborate. We have the same Focal Point forum categories in myibi, so you can continue to have all new conversations there. If you need access to myibi, contact us at email@example.com and provide your corporate email address, company, and name.
In a fex I would like to run a SQL Passthru command, but I would like to NOT set the DEFAULT_CONNECTION. Is there some other way to specify the connection? If I use SET DEFAULT_CONNECTION, it may override something else that occurs in the fex.
I would like to run a SQL Passthru command without altering what the default connection is.
If the first connection in edasprof.prf is zzz and I want to use a SQL Passthru command that needs to connect to aaa and which is included in all fexes, how do I access aaa without overriding the first connection zzz? Does SQL COMMIT undo the DEFAULT_CONNECTION that I used to connect to aaa?
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, Is it possible to put the SQL Passthru command in a separate fex and execute it with EX to run in a separate agent with its own database connection, so the original procedure keeps its own connection as well. If the SQL Passthru is dependant on all kind of parameters in the original procedure which would not be available in the EXecuted procedure, maybe you could dynamically create this procedure. Hope this works.
WebFocus 8206M, iWay DataMigrator, Windows, DB2 Windows V10.5, MS SQL Server, Azure SQL, Hyperstage, ReportCaster