Re: Best way to "lock" a save file -- MIDRANGE-L

Subject: Re: Best way to "lock" a save file
From: Mark S Waterbury <mark.s.waterbury@xxxxxxxxxxxxx>
Date: Thu, 8 Jun 2017 16:27:09 -0400
List-archive: <http://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

Hi, John,

The ALCOBJ command has many restrictions on what kinds of objects you can "allocate" -- for example, you cannpt allocate a DSPF or PRTF or ICFF either ... :-/

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

Thanks,

Mark S. Waterbury

> On 6/8/2017 11:25 AM, John Yeung wrote:

At least up to 7.1, it seems we can't ALCOBJ a save file. So if we
want to lock it, do we ALCOBJ the library it's in? That seems...
imprecise.

If this is indeed the best we can do, is there some technical reason
why IBM didn't/won't provide a way to lock a save file?

John Y.

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Best way to "lock" a save file , John Yeung

This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.