Re: Object Authority

[Mike.Barton@xxxxxxxxxxxx]

>We have just migrated this weekend from a system/36 to an AS/400 and we are
currently having some problems with object >authority on our data-files.  All
our current applications still run in 36 environment so all our data files are
in 1 <library at the moment..  When a user creates a file, that user gets *all
authority to it but *public only gets change <Authority.  How do I stop this and
allow *public have *all authority automatically.  I know that this probably
sounds <like a really stupid question and is easy to fix but I am still getting
used to this system and am lost with some <issues.  I would be grateful if
someone could put me out of my misery and solve this one for me.

Keith
     when creating a new file, the default authority is *LIBCRTAUT.
Do a DSPLIBD {your library} to see what the create authority is for this
library.
You may find that it is *SYSVAL. In this case check the QCRTAUT system value
which
you will probably find to be *CHANGE.

     Normally it is best to use some form of group profile - all users have
a group profile (GRPPRF) of say QUSER and then set the OWNER to *GRPPRF. This
means
that any created objects are owned by QUSER and that all other users in the
group
have all athority to all objects.

Its your choice!

Mike


+---
| 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
+---