Re: Not authorized to command QSH in library QSHELL

Well, since qsh is shipped with *public *use and so is strqsh, watch him
change strqsh to match his change to qsh and now they both have *public
*exclude
:-)
Suppose he'll even say thank you for pointing out something he missed? :-)
And, after he updates this, strqsh won't work either.

There just has to be something you're missing.

Aren't there some newer auditing tracing functions to show all uses of
particular objects like QSH, STRQSH to see if access was only granted
because of program adoption, profile switching, etc?

On Fri, Apr 21, 2023 at 1:20 PM Rich Dotson <Rich.Dotson@xxxxxxxxxxx> wrote:

No. The program was compile through our source control system like all
the other programs on the system. No adoptive authority is occurring.

I changed the program to use the STRQSH command instead of QSH and it
works now. Turning it over to the admin guy to see if he can figure it
out
________________________________
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> on behalf of
Carel via MIDRANGE-L <midrange-l@xxxxxxxxxxxxxxxxxx>
Sent: Friday, April 21, 2023 12:38 PM
To: midrange-l@xxxxxxxxxxxxxxxxxx <midrange-l@xxxxxxxxxxxxxxxxxx>
Cc: Carel <coteijgeler@xxxxxxxxx>
Subject: Re: Not authorized to command QSH in library QSHELL

Does te batch progtram run under afoptive authority, compiled with
SECOFR level?


Op 21-4-2023 om 15:01 schreef Rich Dotson:

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://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.midrange.com%2Fmailman%2Flistinfo%2Fmidrange-l&data=05%7C01%7C%7C94987c15cb9d436364a108db4286ce30%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638176918967543560%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=2%2FBDHIdXXjlcNOrUNueQv9MPB1AtPiprk%2BBSz5h9qz8%3D&reserved=0
<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://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Farchive.midrange.com%2Fmidrange-l&data=05%7C01%7C%7C94987c15cb9d436364a108db4286ce30%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638176918967543560%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=l8RvICcOkJpXj2JgeSvyzEzmjBmEPFo5CqzvAYPUvME%3D&reserved=0
<https://archive.midrange.com/midrange-l>.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.

--
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.