|
<snip>
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.
</snip>
Is the goal to stop the users from running SBMJOB from any command line?
Is the goal to stop the users from running SBMJOB even if imbedded within a program?
Or is the goal to make sure that the defaults are not preventing SBMJOB from running?
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.