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 know ! works, but I never remember if it gets executed with the Dialog mananger commands (like -UNIX or -WINNT) or with the focus code stack (like UNIX or WINNT).
To add more confusion, look up the syntax for SYSTEM(...). The advantage of this over DOS, WINNT, !, and CMD is that because you prime an ampervariable with the result of the system command, WF will wait for the command to complete before it progresses. You can also then check that response and branch accordingly.
T
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
Thanks, Tony. I was not aware of the SYSTEM() function. That may be a good thing to use on Windows platform.
Even if ! is used for several operating systems, the operating system commands themselves (mostly) don't work on all platforms. So I think it might be dangerous to rely on it for cross-platform compatability.
We are moving from Unix Reporting Server to Windows Reporting server, which is why I have gotten into these issues. All the embedded operating system commands have to be replaced. And the paths