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.
Thanks Waz, ! SET is super helpful. I didn't know about it. I'm new and learning. I still don't know what is at the root of my main issue, which is the value assigned to EDATEMP when I run WF from a .bat job triggered by a scheduler. ! SET shows EDATEMP as: EDATEMP=C:\Windows\system32 (Strange to me)
When I run WF via a Browser using WFServelet there is no EDATEMP but rather an EDATEMP0 (zero) which is set as I expect and the report runs properly. Is EDATEMP0 normal behavior in 7.7.04? EDATEMP0=E:\ibi\srv77\wfs\edatemp
So, when I run WF from a .bat file EDATEMP=C:\Windows\system32, this cannot be correct. Any thoughts out there on resolving that or EDATEMP0? If so, please provide your feedback. Thanks. rvb
WF 7.1.7 on Win Server 2003 migrating to WF 7.7.04 on Win Server 2008 HTML, RTF, Excel and PDF
In WF 7.1.7 we call ibiweb.exe: E:\ibi\WebFOCUS71\client71\wfc\web\cgi\ibiweb.exe -v IBIF_ex=gtCECPr IBIC_user=robot SUITS=robot FOCNAME=gtCECPr CRITNAME=cpts
IBI has told me that ibiweb.exe is not viable after 7.1.7. In 7.7.04 I have been instructed to use tscom300.exe as shown below.
E:\ibi\srv77\home\bin\tscom300.exe -edaconf E:\ibi\srv77\wfs -x EX gtCECPr IBIC_USER=ROBOT,SUITS=ROBOT,FOCNAME=gtCECPr,CRITNAME=cpts
This is causing us to re-write all of our bat files that call WF. If anyone thinks we can still use ibiweb.exe in our new 7.7.04 environment please let me know.
WF 7.1.7 on Win Server 2003 migrating to WF 7.7.04 on Win Server 2008 HTML, RTF, Excel and PDF
So what you're actually doing is to have the scheduler call the tscom300 program. Which in fact is the router that will assign the command given to an agent. The former method, ibiweb.exe, first goes through the process of initialising it's environment. tscomm300 doesn't do that, so it will just take the current dir as temp. What you could try is in your bat file that starts this, first cd to an appropriate temp dir. This will very likely solve the issue.
GamP
- Using AS 8.2.01 on Windows 10 - IE11.
in Focus since 1988
Posts: 1961 | Location: Netherlands | Registered: September 25, 2007
When we move from 5.5.3 to 7.6.4 I found when you use a scheduler e.g. AUTOSYS to start a WebFocus batch process, EDATEMP is the current directory when WebFocus started.
I ended up creating a separate folder for each batch job and starting WebFocus only after making that folder the current folder.
Jim Morrow Web Focus 7.6.10 under Windows 2003 MVS 7.3.3
Or you can just invoke a report using Java and JDBC as a stored procedure call. Better than RDAAPP as it can be completely dynamic and you can 3rd party scheduler to call the process. No problems with EDATEMP as you are calling the report in place.
"There is no limit to what you can achieve ... if you don’t care who gets the credit." Roger Abbott