You could set up a Scheduling Environment for Sysprog jobs (ONLY) and another one for everything else that's batch. During normal operation both are active on all sysplex LPARs. During the test window, turn OFF the "Everything Else" environment on the LPAR you're testing on, leaving only the Sysprog environment active. When testing is complete the "Everything Else" environment is set back on.
Maybe not the most efficient solution, but it will work. You'd need to make sure both environments are active after an IPL thru use of your automation software or else you'll be scratching your head wondering why batch isn't running. Dave Thorn * Senior Technology Analyst * SunGard Computer Services * 600 Laurel Oak Road, Voorhees, NJ, 08043 Tel 856 566-5412 * Mobile 609 781-0353 * Fax 856 566-3656 CONFIDENTIALITY: This e-mail (including any attachments) may contain confidential, proprietary and privileged information, and unauthorized disclosure or use is prohibited. If you received this e-mail in error, please notify the sender and delete this e-mail from your system. ---------------------------------------------------------------------- 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
