×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Create the safe file in QTEMP, last step is to move it where you need it to live. If the job aborts, the save file is most likely corrupt, so if it gets deleted, who really cares? Unless you are using a save file for something different than the normal saving of objects?
Chris Bipes
Director of Information Services
CrossCheck, Inc.
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of John Yeung
Sent: Thursday, June 08, 2017 2:32 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: Re: Best way to "lock" a save file
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.
midrange.com
