We don't use the system supplied jobds, leaving authority on system supplied objects as is.
If you don't and change them, you will find an OS upgrade will change them back to original settings.
We create and use are own for various applications with various authorities.
Paul
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Patrik Schindler
Sent: Monday, October 25, 2021 8:25 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: JOBD QBATCH on new installs
Hello,
last night I read the Work Management PDF — again. Every time, I grasp more and more of the concepts there.
I learned that the QBATCH job description has USER(QPGMR) set, and that this setting might pose a security risk if the authority for the JOBD is public=use: Every user with a user profile might run batch jobs under the authority of QPGMR.
When the OS is installed freshly, the mentioned JOBD has no public authority, effectively preventing any user to submit batch jobs via SBMJOB, which is a must-have for me.
I want to hear your opinions if it would be a good idea to still change authority to public=use, but also to change the JOBD parameter USER(*RQD). Or perhaps how you wold solve that dilemma.
Thanks!
:wq! PoC
--
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.
Help support midrange.com by shopping at amazon.com with our affiliate link:
https://amazon.midrange.com
midrange.com
