Good Afternoon,

Concept check: Do I have to explicitly state something should go to foccache to ensure it is unique to a request / session?

For example:

http://forums.informationbuild...037050186#8037050186

If you search for the following it will lead you to the post I am interested in: "posted March 03, 2016 10:33 AM". I've included the little snippet of code below:


TABLE FILE HOLDEVERYTHINGDISTOFFICE
SUM
HOLDEVERYTHINGDISTOFFICE.SEG01.CLOSED_ALL_REQUESTS AS 'CLREQS'
ON TABLE NOTOTAL
ON TABLE HOLD AS HOLDCLOSEDTOTALS FORMAT FOCUS
END

-RUN
-READFILE HOLDCLOSEDTOTALS
-TYPE CLREQS IS &CLREQS


In that statement there is a hold "HOLDCLOSEDTOTALS". Since this does not define the hold as existing in foccache like so, ON TABLE HOLD AS 'foccache/HOLDCLOSEDTOTALS', does that mean it is possible for this file to not be secured to a unique request / session? Maybe that's okay in this persons case, I didn't read the entirety of what they are trying to achieve. I was searching for something else and stumbled across this code and thought, "I should ask about this", and decided to use this specific snippet as an example of what I'm looking at.

Thanks for any input.

This message has been edited. Last edited by: FP Mod Chuck,

Hi Sean,

Anything in FOCCACHE is protected, but is available to the user for the life of there session.

Anything in the EDATEMP/tsnnnnnn (location for HOLD and SAVE) is secured for the job run.

So both are secured.

Note: Note sure about connection pooling.

Okay, so I have a series of guids that are request specifc and should be cached as they are used in the "child" procedures of my main report procedure. If I want these to be nuked at the end of that main procedures run I should just use the normal hold without foccache then?

If I understand, yes

However, if there's an "APP HOLD" statement preceding the "ON TABLE HOLD AS {filename} FORMAT FOCUS" it will be a 'permanent' file and will be accessible to anyone who has access to that app folder as long as that file exists. It will also be overwritten by subsequent executions of another "ON TABLE HOLD AS {filename} FORMAT FOCUS" when preceded by the "APP HOLD" statements.

Summary: There's several pieces to this puzzle. There's also the "APP DELETEF" command to think about...