Re: BRMS Authorities

[Gord Hutchinson <gordm1@xxxxxxxxxxxxxxx>]

At the same time I posted my initial question, a colleague asked IBM about
the authorities needed to run console monitor to do the save.  The userid
needs *SAVSYS and also needs authority to the ENDTCP & STRTCP commands.


Gord



On Fri, Feb 6, 2015 at 11:48 AM, Jim Oberholtzer <
midrangel@xxxxxxxxxxxxxxxxx> wrote:

> True, and that's been in the system for many years, so no news there.
>
> The way to deflect that problem is to use a command exit that checks for
> the
> parameter and the user to see if that's authorized.   Most folks don't do
> the command exit (maybe they should) but the incidence of clearing an
> object
> is very rare.
>
> The last time I had it happen and operator decided to clean up the system
> overnight.  When files QSYSTAP and the sign on display file were cleared
> the
> system stopped.  Fortunately the file QSYSTAP can be easily recreated by
> hand, and we were able to restore all the files from the tape they were
> just
> backed up on.  That happened in about 1992.  Last time I've seen it happen.
>
> This is a better reason to use BRMS and have a user profile specified for
> the backups perform them.  Now the system runs the backup jobs from the
> scheduler, and full system saves are automated as well.    Human
> intervention is limited to mounting/demounting tapes.
>
> --
> Jim Oberholtzer
> Chief Technical Architect
> Agile Technology Architects
>
>
> -----Original Message-----
> From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
> Graap, Kenneth
> Sent: Friday, February 06, 2015 10:17 AM
> To: Midrange Systems Technical Discussion (midrange-l@xxxxxxxxxxxx)
> Subject: Re: BRMS Authorities
>
> *SAVSYS authority also allows a user who has it to effectively DELETE any
> object on the system by freeing it's storage... It is a VERY powerful
> special authority to give anyone.
>
>
>
> SAVOBJ OBJ(ANYOBJ)
>
>        LIB(ANYLIB)
>
>        DEV(*SAVF)
>
>        SAVF(ANYSAVF)
>
>        STG(*FREE)
>
>
>
> DLTF FILE(ANYSAVF)
>
>
>
> ANYOBJ is now gone.
>
>
>
> Help                         Storage (STG) - Help
>
>
>
>     Specifies whether the system storage that is occupied by the data
>
>     portion of the specified members (except for save files), modules,
>
>     programs, service programs, Structured Query Language (SQL)
>
>     packages, and journal receivers in the library being saved is freed
>
>     as part of the save operation.  Only the data portion of the objects
>
>     is freed, not the descriptions of the objects.
>
>
>
>     *KEEP
>
>         The storage occupied by the data portion of the objects being
>
>         saved is not freed.
>
>
>
>     *FREE
>
>         The storage occupied by the data portion of the specified
>
>         objects being saved is freed as part of the save operation.  The
>
>         storage for all the objects in a library is freed only after all
>
>         the objects in that library are saved successfully.
>
>
>
>
>
>
>
> Reply or Forwarded mail from: Kenneth E Graap
>
>
>
> -----Original Message-----
>
> From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
> Charles Wilt
>
> Sent: Thursday, February 05, 2015 11:56 AM
>
> To: Midrange Systems Technical Discussion
>
> Subject: Re: BRMS Authorities
>
>
> Kenneth
> Kenneth E. Graap
> NW Natural
> System Administrator for IBM Power Systems
> 503.226.4211 x5537
> http://www.linkedin.com/in/kennethgraap
>
>
>
> --
> 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.
>
>
> --
> 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.