Hi folks,
for our systems we CHOSE to perform some checking in JES2 EXIT6. This is to
catch "problem" jobs at submission, and to allow operations staff to later
modify those parameters if required.
the current exit performs checks on:
o Job Class - FACILITY JOBCLASS.x
o Time parm authorization - FACILITY [EMAIL PROTECTED]
These are to enable enforcement of local standards.
As yet we have been able to NOT implement RACF checking for permission to
code REGION parms. Such checking is being performed via the change
management process before the JCL gets promoted.
Using the exit made it simple to implement our requirements.
Regards
Bruce Hewson
ps: the RACROUTE call checking job class parm!
***********************************************************
************
* *
* validate job class card *
* *
***********************************************************
************
MVC X6RACROUTE
(RACF_RACROUTE_LENGTH),RACF_RACROUTE
OI X6RACROUTE+116,X'10' REQUEST WARNING STATUS IF SET
RACROUTE REQUEST=AUTH, C
MF=(E,X6RACROUTE), C
USERID=X6USERID, C
ATTR=READ, C
LOG=NOSTAT, C
ENTITY=(X6JOBCLASS), C
CLASS=RACF_CLASS, C
WORKA=X6RACWRK, C
RELEASE=1.9
*
*
LA R15,X6RACROUTE
USING SAFP,R15
*
CLC SAFPRRET,=F'0' Racf RC = 0
BNE JOB_CLASS_NOT_AUTH No - Cancel job
*
CLC SAFPRREA,=F'0' RACF reason code = 00
BE CLASS_OK Yes
*
CLC SAFPRREA,=F'4' RACF reason code = 04
BE CLASS_OK_WARNING Yes
*
----------------------------------------------------------------------
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
