Re: Best way to "lock" a save file

Hi, John,

I would create a unique save file in QTEMP. with a name like "SAVF" + job number, and then do whatever your job wants to -- and you can rest assured that no one else can "See" or "touch" that save file, since it exists in your (per job) QTEMP library.

Then, when you're done doing whatever you are doing with that save file, you could move it into a permanent library, (perhaps a library that has *PUBLIC *EXCLUDE authority), or you could even copy the save file records into a permanent database file with RCDLEN(528) and where each "member" could be a saved copy of each unique "instance" of your "save file" ... If you need those save files to "persist." you can even ALCOBJ these physical file members, if you need to somehow "lock" them for a time.

You can always copy the *SAVF records from the PF member back into a QTEMP save file, e.g. to restore items from that save file, etc.

Does that help?

Mark S. Waterbury

> On 6/8/2017 5:32 PM, John Yeung wrote:

On Thu, Jun 8, 2017 at 4:27 PM, Mark S Waterbury
<mark.s.waterbury@xxxxxxxxxxxxx> wrote:

What exactly do you mean by "locked"? What actions are you trying to
prevent by "allocating" the object, presumably for *EXCLusive use?

Conceptually, the same thing as allocating a database file for
exclusive use. I don't want to allow the possibility that some other
job could rename or delete the save file, or alter the contents of the
save file in any way, until my job is done with it. And my job
shouldn't start working with that save file until it can be allocated
exclusively.

John Y.