I agree with Mark Zelden. When we looked at trying to find a way to put development batch in a different service class than production batch, when it runs on a different system in the sysplex but uses exactly the same job name (for testing - same in test as in production), we ended up with this same methodology as the answer. Lucky for us, our test systems share one MAS and the production systems share another, so we were able to differentiate based on SSC. I wish, though, that JES Selection List Rules allowed for individually named system images to be specified, it would make this sort of thing much easier (it surely did for DDF workloads!).
Here's kind of an example coding, one where a TNG for HIGHBAT high batch is separated by MAS (SSC from XCFGRPNM connector name in $DMASDEF), and one where initiator class A is separated using the same method. 1 TNG HIGHBAT 2 . SSC . H001NJE HIGHBAT HIGHBAT 2 . SSC . H101NJE DEVHBAT DEVHBAT 1 TC A 2 . SSC . H001NJE NORMBAT NORMBAT 2 . SSC . H101NJE DEVNBAT DEVNBAT This is particularly useful in a CECPLEX with mixed DEV and PROD systems, at 100% busy time, to help ensure that the PROD system gets the CPU and the DEV system gets starved out first (loves ones get the CPU, don't cha know). The service classes are defined so that production is higher in importance and velocity goal than development, to help things along. HTH, Gary Diehl Systems Administration "Water seeks it's own level" - Aristotle -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Mark Zelden Sent: Wednesday, May 27, 2009 8:08 AM To: [email protected] Subject: Re: Assigning service class depending on system On Wed, 27 May 2009 08:29:34 +0000, Ted MacNEIL <[email protected]> wrote: >>Is it possible to assign a service class depending on the system the job is running on? > >Yes. Possibly (more below). Definitely NO in a shared spool (MAS). >SI/SIG > >System Instance (Group) That is subsystem instance (not system instance) which is a valid qualifier for JES, but ITYM SY/SYG - which is system name. However, SY is not valid for a JOB, which is what the OP requested. It is valid for TSO, STC, OMVS, ASCH, SAP, and TCP (I think that is the entire list). > >We are running z/OS 1.9. > >Been around since OS/390, IIRC. SY has been around since OS/390 2.10. It was created to remove one of the inhibitors for some shops that could not get to goal mode since compatibility mode was going to be removed from the OS. You can classify in JES for SSC - Subsystem Collection Name. This is the JES2 MAS name or JES3 JESplex name. So if every system in the sysplex has its own JES spool, then the answer to the OP's question is Yes. Otherwise it's No. 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 ---------------------------------------------------------------------- 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
