I don't know of any standard interface that will control access to output
classes. I had a similar issue with job classes and eventually added profiles
of the form JOBCLASS.X to the JESJOBS class and issued RACROUTE authorization
requests in IEFUJV.
For output classes I would recommend checks in JES2 exit 6 since everything is
tokenized for you there.
"Perryman, Brian" <[EMAIL PROTECTED]> wrote:
snip
Secondly, we have one of those products that archives job output off the spool
(and into VSAM datasets). It's meant to be for production jobs only, but some
of the users have realised that this means they can keep some of their listings
for a few weeks with no effort on their part, so have started submitting their
jobs using the output class that feeds this archive product.
The second question then, is there a way in JES or RACF that will let me stop
non-production users writing to certain output classes?
---------------------------------
Do you Yahoo!?
Make Yahoo! your home page
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
