ok, we do run adoptive authority, but we do have our *jobd's as *public
*use....
I am told that is bad.
I read stuff about adoptive authority and a submitted job, and a new call
stack....
but that doesn't address the CPF1411 error I am getting on the SBMJOB
command
"not authorized to job description" when I change the *JOBDs to *PUBLIC
*EXCLUDE
I also read stuff about creating a different SBMJOB command, or adding
routing entries to our batch subsystems...
Is my only recourse, to create a *AUTL, to put on my *JOBD's, to only allow
those users I want to use those *JOBDs?
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.
midrange.com
