quote:

In WebFOCUS, HOLD files are saved to a temporary directory during processing and deleted after the connection to the server is broken.

I understand the HOLD files are temporary, but not entirely grasp the life or when/what circumstances these files are available. ie in
-INCLUDE
-EX
-EXEC
dd fex
recursive dd fex
-HTMLFORM
...

Or perhaps, I don't understand what is session? Appreciated for your advices.


Hua

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

Very basicly, a session is the duration of time between the start of your request (read: fex) until the end of your request. Anything between these two moments can be called a session. Your request will be started by the server and is sent to one of the agents available. It will start with a clean environment. After processign of the fex has completed, the environment in which your request was processed will be cleaned - thereby removing all files in the temporary directory.
You can influence this behaviour a bit by issueing the SET TEMPERASE=OFF command somewhere in your fex. This will prohibit the erasure of the temporary files from the agent's temp directory. This command is to be used with care - a request following yours will not start in a clean environment, which may cause unexpected results.

Thanks for your comment Gamp.

I realized my question is kind of vague. What I really want is that when a user launch an application, the main fex creates some hold files and the drill down fexes(or other ways of executing sub procedures) will be able to used them. And I don't mean to hold them to some perminant locations other users can access.
Clear as mud?
I can only refer to AS400 as I am familar with the environment, when I launch an application, I can set the activation level to higher call level or at current level to control the life of or when and how long the temparary file lasts. And by default, temp files are available to subsequent calls. How can I do the same in WF?

Upgrade to 7.6.5 so that you can use the FOCCACHE option which will do exactly what you need.

Or if you can't do that, create semi_permanent work directories for each invocation of the report using some sort of process id that you would delete let's say in a half an hour. I don't know how you would do that on AS/400, but we do it on our UNIX platform. Maybe this will give you an idea on something you could develop to do this.

Thanks Jinny.I will keep both of your advices in mind.


Hua