On Wed, 6 Aug 2008 15:23:04 -0500, McKown, John <[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? > What are you going to do in the IEFUJI? Suggestions: Unique job classes / inits, WLM scheduling environments, /*JOBPARM SYSAFF=. I think we discussed this not too long ago. Including what exits to use (or not use) and pros/cons. 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
