I’m not certain what the use case is here, but I’ll bet you don’t really want to give everyone that authority, or at least based on your note a limited number.

The best way to accomplish this in my view is with an adopted authority CLP wrapper.
Take in parms that you need for the job, and craft a SMBJOB command as needed. Create your own command if it makes sense to do so.

That way you can accomplish your goal and maintain some level of control. I’ve even seen those programs encode a journal entry to a user journal in order to memorialize the job for later audit.

Jim Oberholtzer
Agile Technology Architects

On Dec 27, 2019, at 7:25 AM, Jay Vaughn <jeffersonvaughn@xxxxxxxxx> wrote:

so we have a need to submit a job under another specific user profile.

what is the best/cleanest method for implementing this?

obviously we can just specify the new user on the sbmjob user() parm, but
what about each individual user profile that may do the sbmjob, what is the
best/cleanest way to maintain those user authorized to the sbmjob user()
user profile?


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@xxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: https://amazon.midrange.com

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.