Some ideas: 1 - Set up SCHEDULING ENVIRONMENTS in WLM and use that to steer the jobs to the appropriate LPARs
2 - Set up initiators so that only certain classes are defined on PRD3 and 4 This presumes you aren't using all 36 classes already and could define some uniquely to PRD3/4. 3 - Use /*JOBPARM SYSAFF=PRD3 to ensure the jobs run only on the designated LPAR -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of SUBSCRIBE IBM-MAIN Ivan A. Ramos Sent: Thursday, August 12, 2010 15:35 To: [email protected] Subject: JES2 MAS member restriction We have two LPARs (PRD1,PRD2) on a MAS, but have included 2 more (PRD3,PRD4). Due to a special IBM pricing, we only wants that certain workload could run on the new ones. We have WLM and IRD working on our systems. Basically we would like to segment or restrict JOBs (Batch or TSO) from running where they are not suppose to. They should be balanced among the old lpars, but not able to run on the new ones and viceversa. Any idea on how to accomplish this? Any inputs would be really appreciated. ---------------------------------------------------------------------- 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 ---------------------------------------------------------------------- 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
