We used IFUJV to verify the user (not necessarily the submitter) was authorized to use the jobclass. We added profiles to one of the existing JES classes. We already had the exit in place for other purposes (e.g., validate accounting data) it was easy to add the additional check.
One potential disadvantage is that the check is not performed until the job is about to be dispatched. On our system that was seldom more than a few minutes so not an issue. > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of Tim Hare > Sent: Wednesday, January 07, 2015 8:15 AM > To: [email protected] > Subject: "submitter" restrictions? <snip> > 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? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
