Re: Rename WRKUSRPRF

[Evan Harris <auctionitis@xxxxxxxxx>]

Hi James

You can't always solve a management problem with a technical solution. In
my view inappropriate assignment of authority is a management issue.

In this situation I would simply publish the instructions/expectations that
the user is expected to abide by and set up auditing to report on any
transgressions.

I would be certain to let every one involved know that there was no simple
way of preventing a disaser, and that auditing had been turned on and would
be reviewed for inappropriate activity.

If there are any SLAs or whatever I would obtain thje approrpiate
exemptions and confirmations of acceptance of risk.

Oh, and the auditors - I would definitely take them out to lunch for for
drinks when they turn up or otherwise let them know there was an exposure.


On Wed, Aug 30, 2017 at 8:01 AM, James Rich <james@xxxxxxxxxxx> wrote:

> For reasons beyond my control or influence, a user on a system has been
> granted QSECOFR authority.  We're concerned about a number of problems with
> that, but mostly the use (abuse) of the WRKUSRPRF command.
>
> Are there problems with renaming QSYS/WRKUSRPRF?  Can I simply RNMOBJ
> OBJ(QSYS/WRKUSRPRF) OBJTYPE(*CMD) NEWOBJ(NEWUSRPRF) and still be ok?
>
> James Rich
> --
> 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.
>
> Please contact support@xxxxxxxxxxxx for any subscription related
> questions.
>
> Help support midrange.com by shopping at amazon.com with our affiliate
> link: http://amzn.to/2dEadiD