Re: authority issues with a QS36F file

[Charles Wilt <charles.wilt@xxxxxxxxx>]

1) Replace it instead of deleting it
2) Change the authority after creating it
3) Create it in a job submitted under a particular user profile
4) Change the user profiles so that objects they create are owned by a
group profile.

Charles

On Thu, Oct 22, 2009 at 2:10 PM, Booth Martin <booth@xxxxxxxxxxxx> 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?
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.