z/OS 2.1 added Job Class Security to RACF. It was previously provided by an exit.
I do not recall if (either exit or z/OS 2.1) uses a SAF profile, but the capability is there... Re: 1 - The user ID should be sufficient Re: 2 - See above Re: 2A - See above. Re: 2B - IMO use HASPUX06. This is much earlier in the process. HTH, <snip> Two topics on job submission 1: the JES SMF records (I think type 26) include a submitter ID but _not_ the name of the submitting address space. I've created a SHARE request to add that information.. please, if you are a SHARE member read the proposed requirement and vote on it. 2: I believe in recent JES2 incarnations that internal reader use happens in the address space of the "submitter". I am trying to find a method to restrict a certain job class to only being used by the production job scheduler. 2A: Does a SAF profile exist to protect job class? 2B: If not, is it better to use IEFUJV or a JES exit to restrict this use? </snip> ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
