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 am running webfocus from a bat file for example c: cd \ibi\srv77\wfs bin\edastart -f c:\ibi\srv77\wfs\bin\dailysave.t3i which works fine.
Now I want to do some post processing to copy the t3o file to a new location for checking.
When I add any doss commands to the end of the bat file they are ignored. If I comment out the call to edastart the dos commands work OK.
Is there something I need to do after the edastart call to return control to the DOS command processor?This message has been edited. Last edited by: Kerry,
Posts: 140 | Location: Adelaide South Australia | Registered: October 27, 2006
Your problem is that edastart keeps running until the WebFOCUS server is stopped. Only then will the DOS command processor continue to the next statement.
I'm not very familiar with DOS command execution, but on UNIX you can usually run a command "in the background", which forks off a new process to run the command in, after which the command processor will continue to the next statement.
Perhaps DOS has a similar feature, or perhaps edastart has an option to not run in the foreground.
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 :
I'm not very familiar with DOS command execution, but on UNIX you can usually run a command "in the background", which forks off a new process to run the command in, after which the command processor will continue to the next statement.
Perhaps DOS has a similar feature, or perhaps edastart has an option to not run in the foreground.
Its not the same, but you can use CALL to execute another batch file from the first one. I used to write batch files that dynamically created (and executed) batch files in parallel (well, not really, but since they spawned in separate processes, it appeared threaded).