• Subject: Re: User can't delete file
  • From: "Bob Crothers" <bob@xxxxxxxxxxxxxx>
  • Date: Sun, 24 Oct 1999 16:21:33 -0500
  • Organization: Cornerstone Communications

If you have OWNER(*GRPPRF), you will not know who really created the
object.

Instead, use GRPAUT(*ALL), which means when somebody creates an object,
it will still be owned by them, but everybody in the group will have
full authority to it.

I do agree that you should create a SYSOP profile that both ROB and
ANNA are members of.

JMHO
Bob Crothers

----- Original Message -----
From: John Earl <johnearl@powertechgroup.com>
To: <MIDRANGE-L@midrange.com>
Sent: Sunday, October 24, 1999 12:22 PM
Subject: Re: User can't delete file


>
>
> Jim Langston wrote:
>
> > We have one S36 procedure that runs that gives one user problems.
> >
> > This procedure creates a temp file in qs36f and leaves it when it's
> > done.
> > The beginning of the procedure deletes the file if it exists before
> > creating it.
> > We have 2 users that use this procedure, anna and rod, rod's user
group
> > is anna.
> >
> > When Rod runs the procedure, everything is fine and dandy.
> > When Anna runs the procedure after Rod does, an error occurs saying
she
> > is not allowed to delete the file.
>
> Even though Rod is a member of Anna's group, Anna does not
automatically get
> rights to stuff that Rod creates.   I think that what you are trying
to
> accomplish is to have the objects that Rod creates owned by Anna's
group.   Do
> this by specifying the OWNER(*GRPPRF) in Rod's profile.   This will
cause
> everything that Rod creates to be owned by user Anna.
>
> Or better still, create a group called SYSOP and have both Rod and
Anna be a
> member of it (with OWNER(*GRPPRF) of course) .   This way when Anna
eventually
> leaves the company, you don't have to fix the ownership of all of
those objects
> her group created.
>
> jte
>
>
>
> --
> John Earl
johnearl@powertechgroup.com
> The PowerTech Group                        206-575-0711
> PowerLock Network Security              www.400security.com
> The 400 School                                www.400school.com
> --
>
>
> +---
> | This is the Midrange System Mailing List!
> | To submit a new message, send your mail to MIDRANGE-L@midrange.com.
> | To subscribe to this list send email to
MIDRANGE-L-SUB@midrange.com.
> | To unsubscribe from this list send email to
MIDRANGE-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner/operator:
david@midrange.com
> +---
>

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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