Re: SAVRST authority issue

Paul

> I was wondering why when I save a program with private
> authorities to a save file and then restore the
> program to a different library I lose the private
> authority.

Actually, you don't lose the private authorities, they are right where
they always were.  :)   Private authorities to an object (such as a
file) are stored in the user profile object, and not in the file
object.  That's an important thing to understand about private
authorities...

So if you save a copy of file "ITEM", and then restore the file to
another library, PHIL's profile still records the fact that he has
*ALL authority to the original "ITEM" file.  This newly restored file
"ITEM" in a new library?  Well User Profile PHIL has never even been
told that this new file exists, so it can't be authorised to it.
(This would mean that the suggested RSTAUT command would not work
either)

If you want object level security, then every time you introduce a new
object to your system you must manage the authority to that new
object.  There is no "automatic security feature" that will guess what
authority you want assigned to new objects, so you have to do it
yourselve.

In this case I would reccommend that after you restore the object, run
the GRTOBJAUT command, and use the original "ITEM" file as a
"referenced object".  It's one extra step, but it will get you want
you want.

jte