Re: Minimum authority needed for CRTSAVF

[Charles Wilt <charles.wilt@xxxxxxxxx>]

Then only thing you need to save the system is *SAVSYS.

Just make sure the user has authority to the library where you are
putting the save files.

If it were me, I'd create a special library just for this.

HTH,
Charles

On Thu, Mar 25, 2010 at 10:29 AM, Grizzly Malchow
<grizzlym@xxxxxxxxxxxxxxxxxxxxx> wrote:
> We've recently purchased a "Rapid Recovery appliance" to handle our backups and disaster recovery. In order to backup the data on our i5 the software on the backup unit connects to our i5 via ftp and creates save files, saves data to the save files, and then gets the save files.
> I've created a user profile that will be used to do this. The user profile is setup with initial menu *SIGNOFF and USRCLS *SYSOPR. I figured I'd need *SAVSYS and *ALLOBJ. Is there a way to set it up without *ALLOBJ and still be able to create save files and save literally all of our information?
> I'm not a security guru, but I generally try to avoid granting *ALLOBJ authority. I tried only granting *SAVSYS authority, but then the user doesn't have authority to create save files.
> Thanks in advance.
> Griz
> --
> 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.