On Wed, 6 Aug 2008 14:36:44 -0700, George Fogg <[EMAIL PROTECTED]> wrote:
>> We have a two system basic sysplex. Basically, SY1 is for "production >> only" and SY2 is from "not production only". Don't ask - politics. I do >> have a JES2 MAS. So now, we need some way to prevent a job from running >> on the "wrong" system. I currently have an IEFUJI exit which run on the >> "non production only" system which JCLs a job which has a "bad" jobname >> or job class. I don't really like this. Does anybody have any idea for a >> free-as-in-beer solution. Or do I just extend the IEFUJI exit to be >> bigger and hairier? >> >John >If I remember correctly, you have a RACF shop so use the NODES class to stop >inbound jobs and sysout from SY2 on the SY1 node. >For example: >RDEF SY2.USERJ.* UACC(NONE) This will stop jobs from entering SY1 from SY2 > >RDEF SY2.USERS.* UACC(NONE) This will stop sysout from SY2 to SY1 or use >RDEF SY2.USER*.* UACC(NONE) for jobs and sysout > >George Fogg > John says he has a JES2 MAS. How will NODES help him - it's all one node? Mark -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group - ZFUS G-ITO mailto:[EMAIL PROTECTED] z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/ Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html ---------------------------------------------------------------------- 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
