Folks,
I'm trying to determine if there is a way to delete the HOLD files temporarily stored in c:\ibi\apps\HeldFiles\ during program execution? We seem to have several gigabytes of Hold File remnants from past executions. I was wondering if there was some sort of 'clean up' process that the programmer could do to delete these files after execution to keep the space usage down.

- ABT

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

They shouldn't be there in the first place.

Default behaviour: HOLD files are temporarily stored in the agent's temporary directory (e.g. \srv76\wfs\edatemp\ts000002) - they get automatically deleted at the end of the request.

Non-default behaviour: Using "APP HOLD HeldFiles" or "APP HOLDDATA HeldFiles" commands, the HOLD files are permanently stored in c:\ibi\apps\HeldFiles\ which has to be manually cleaned up. There are very few reasons why you need to save the HOLD files - I can think of only two: 1) to use them in a subsequent drill-down; 2) to aid in debugging a program.

If they're being saved for reason 1, look into FOCCACHE - "Two applications are provided during installation: a default application called baseapp and an application containing sample files called ibisamp. In addition, when you connect to the server a temporary directory called foccache is added as the first directory in the search path. When you want to be able to reuse data within the same browser session, you can store the data in the form of a HOLD, SAVE, or SAVEB file in the foccache directory. As long as the browser session remains active, the files stored in the foccache directory can be referenced in requests.

If they're being saved for reason 2, you manually have to delete the files or set up a regularly scheduled job (via ReportCaster or some other tool) to delete the contents of the folder.

In a nutshell, the programmer can create a job in ReportCaster with the following code and schedule it to run every few minutes or so:

APP DELETEF HeldFiles

Francis,
As always, thanks. After a bit more investigation, they appear to be the second case (FILEDEF). I'll educate my users to only use ON TABLE HOLD AS unless they need to refer back to the file at a later time after the process completes.

Thanks!
- ABT