Re: Not authorized to command QSH in library QSHELL

[Rob Berendt <robertowenberendt@xxxxxxxxx>]

Are you sure that the command is from the same library list?  Any chance
that batch jobs use a special library list in which you copied certain
commands and changed the authorization?  Try
WRKOBJ *ALL/QSH *CMD
I believe that the default is to have *PUBLIC with *USE to QSHELL/QSH
And the command is shipped with Allow limited user . . . . . . . . . . :
*NO

Object      Type      Library     Attribute
QSH         *CMD      QSHELL
QSH         *CMD      QSYS        PRX
QSH         *CMD      QSYSV7R3M0
QSH         *CMD      QSYSV7R4M0

On Fri, Apr 21, 2023 at 9:03 AM Rich Dotson <Rich.Dotson@xxxxxxxxxxx> wrote:

> We have an iSeries User Profile that we use specifically for our jobs that
> do QSHELL processing.  This profile currently runs multiple scheduled
> (batch) jobs that use the QSH command without issue.
>
> When I sign on with this profile to test a new program that uses the QSH
> command I receive the error message 'Not authorized to command QSH in
> library QSHELL'.
>
> How can the user profile be authorized when running the QSH in batch but
> not be authorized to run it from the command line?
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: https://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at https://archive.midrange.com/midrange-l.
>
> Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
> questions.