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 have set up a call to a remote server, calling it this way:
EXEC TESTLOGN AT VMEDASRV KEEP;
In that focexec I write:
SQL SQLDBC SET DBCLOGON vmlogin/username,password
. . . which seems to connect correctly and allow for data to be returned within itself. However, I would expect that session to remain alive, including the SET command within it. When I come back to Maintain and attempt to do a FOR ALL NEXT to the same table I test within the focexec, I get an invalid user error. Does anyone know -- does KEEP actually work correctly? Is there a system setting that I need to invoke?
J.
Posts: 1012 | Location: At the Mast | Registered: May 17, 2007
Update -- after reading the help files with exceptional care, I have discovered that the KEEP option only keeps the session open for future EXECs, not for calls from the Maintain code itself (i.e., For-All-Next, Revise, or Delete, etc.) This is a non-starter for me so I likely will not pursue this issue further.
J.
Posts: 1012 | Location: At the Mast | Registered: May 17, 2007
Good Morning John Just a slight correction. The KEEP command tells Maintain to KEEP the external procedure in memory, so if we EXEC it again, we don't have to perform I/O to get it. The reverse, DROP, says we are not going to save this procedure in memory.
If you perform an EXEC that sets up FILEDEFS or ALLOCATES on a Server, you can then do a CALL to manipulate the data. We do this sometimes for USE commands for SU and flat file allocations. But, this is for data files. I am honestly not sure what would happen with system commands.
However, there IS a SYSMGR command that allows you to set system variables from inside a Maintain procedure. If you do need to persue this, check out that command.
Mark
Posts: 663 | Location: New York | Registered: May 08, 2003