Re: authority issues with a QS36F file -- MIDRANGE-L

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.

Subject: Re: authority issues with a QS36F file
From: Scott Klement <midrange-l@xxxxxxxxxxxxxxxx>
Date: Thu, 22 Oct 2009 13:15:38 -0500
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/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

Clear the file instead of deleting it? (Is that all you need?)
You can run CLRPFM on a S/36 file, and you can even run it from within an OCL proc.

Booth Martin wrote:

authority issues with a QS36F file:

I have found a solution, but I do not like it. Probably others here have a better way.

Each month a file in Q36F is deleted and rebuilt. The file is owned by whomever last ran the OCL, and no one else can access it. I have no desire to start a rewrite of the application but I do have to allow others to use the file.

Any ideas?

Follow-Ups:

Sorting Question , Jon S

This mailing list archive is Copyright 1997-2026 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.