Look at the object authority of the QSH/QSHELL command.
dspobjaut qshell/qsh *cmd
Does the profile have authority to the command? If not maybe the batch job
is gaining authority through adopted authority.
Another possibility is the batch job is using profile swapping and running
under a different profile.
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Rich
Dotson
Sent: Friday, April 21, 2023 6:01 AM
To: midrange-l@xxxxxxxxxxxxxxxxxx
Subject: Not authorized to command QSH in library QSHELL
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.
.
midrange.com
