RE: wrkfcnusg frustrations

[Michael Quigley <MichaelQuigley@xxxxxxxxxx>]

+1 (well, +100)

Thanks,
Michael Quigley
Computer Services
www.TheWay.org

> -----Original Message-----
> message: 3
> date: Tue, 24 Jun 2025 14:25:41 -0400
> from: Rob Berendt <robertowenberendt@xxxxxxxxx>
> subject: wrkfcnusg frustrations
>
> Am I just being an angry bird by despising the proliferation of stuff requiring
> WRKFCNUSG?  For example STR...
> User QSECOFR not authorized to command STR...
> Joblog contains a message like ".... You need to obtain permission from your
> system administrator for function QIBM_..,_ADMIN"
> CHGFCNUSG FCNID(QIBM_..._ADMIN) USER(QSECOFR) USAGE(*ALLOWED)
> Now QSECOFR can use STR...
>
> ... is a redacted string so as not to draw attention to any one product but
> focus overall on this WRKFCNUSG proliferation.
>
> In my mind, if a shop is stupid enough to give *ALLOBJ to too many people
> then they can easily enough do a CHGFCNUSG FCNID(QIBM_..._ADMIN)
> ALLOBJAUT(*USED) and be done with it.  Who are we to judge?  All we're
> doing is making them perform extra steps.
> If everyone would use the same message id and I could simply trap that
> message, read the data and automatically do a CHGFCNUSG I'd be tempted.