Focal Point
[SOLVED] TEMPPATH - what's under the hood?

This topic can be found at:
https://forums.informationbuilders.com/eve/forums/a/tpc/f/7971057331/m/1057054916

April 25, 2012, 09:13 PM
Rob Van Brunt
[SOLVED] TEMPPATH - what's under the hood?
-* GOOD: WF 7.1.7, Win 2003
-SET &T = TEMPPATH(80,'A80');
-* RETURNS e:\ibi\srv71\wfs\edatemp\ts001358

-* BAD: WF 7.7.04, Win 2008
-SET &T = TEMPPATH(80,'A80');
-* RETURNS C:\Windows\system32

-* BAD example is causing my applicaion to bomb. How does TEMPPATH work? Thanks, rvb

This message has been edited. Last edited by: Kerry,


WF 7.1.7 on Win Server 2003 migrating to WF 7.7.04 on Win Server 2008
HTML, RTF, Excel and PDF
April 25, 2012, 09:26 PM
Waz
It should pull the tscom's temp directory location.

Have you verified your edatemp location ?


Waz...

Prod:WebFOCUS 7.6.10/8.1.04Upgrade:WebFOCUS 8.2.07OS:LinuxOutputs:HTML, PDF, Excel, PPT
In Focus since 1984
Pity the lost knowledge of an old programmer!

April 25, 2012, 10:23 PM
Rob Van Brunt
Thank you Waz for pointing me in the right direction. I need to determine the edatemp location as you suggest. I will research that. rvb


WF 7.1.7 on Win Server 2003 migrating to WF 7.7.04 on Win Server 2008
HTML, RTF, Excel and PDF
April 25, 2012, 11:35 PM
Waz
If you issue the command ! set from a fex, do you see EDATEMP in the list ?


Waz...

Prod:WebFOCUS 7.6.10/8.1.04Upgrade:WebFOCUS 8.2.07OS:LinuxOutputs:HTML, PDF, Excel, PPT
In Focus since 1984
Pity the lost knowledge of an old programmer!

April 26, 2012, 01:44 PM
Rob Van Brunt
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
April 26, 2012, 05:40 PM
Waz
Ah, the missing piece of info.

How are you running WF from the batch file ?

Can you post it ?


Waz...

Prod:WebFOCUS 7.6.10/8.1.04Upgrade:WebFOCUS 8.2.07OS:LinuxOutputs:HTML, PDF, Excel, PPT
In Focus since 1984
Pity the lost knowledge of an old programmer!

May 01, 2012, 03:50 PM
Rob Van Brunt
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
May 07, 2012, 06:57 AM
GamP
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
May 09, 2012, 08:39 PM
Jim Morrow
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



May 09, 2012, 08:48 PM
Waz
You know, I wonder if it would be easier to use RDAAPP to do the call, it will create the proper temp directory.


Waz...

Prod:WebFOCUS 7.6.10/8.1.04Upgrade:WebFOCUS 8.2.07OS:LinuxOutputs:HTML, PDF, Excel, PPT
In Focus since 1984
Pity the lost knowledge of an old programmer!

May 09, 2012, 11:46 PM
dhagen
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
May 10, 2012, 12:27 AM
Waz
Yes, agreed.

I guess the web call is the best.

Just to confuse even more, you can use interp to call the servlet.


Waz...

Prod:WebFOCUS 7.6.10/8.1.04Upgrade:WebFOCUS 8.2.07OS:LinuxOutputs:HTML, PDF, Excel, PPT
In Focus since 1984
Pity the lost knowledge of an old programmer!

May 10, 2012, 08:26 PM
Rob Van Brunt
Thank you to all. I need to consider all of your input. Sorry for the delayed response. Over loaded. rvb


WF 7.1.7 on Win Server 2003 migrating to WF 7.7.04 on Win Server 2008
HTML, RTF, Excel and PDF