Assigning service class depending on system
Hi, Is it possible to assign a service class depending on the system the job is running on? We are running z/OS 1.9. TIA Gadi -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Assigning service class depending on system
""??? ?? ???"" wrote in message news:... > Hi, > > > > Is it possible to assign a service class depending on the system the job is running on? > > > > We are running z/OS 1.9. > > > > TIA > > > > Gadi > The Classification Rules are run when the job enters the system, so the Service class is already defined when job starts executing. Kees. ** For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch Airlines) is registered in Amstelveen, The Netherlands, with registered number 33014286 ** -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Assigning service class depending on system
>Is it possible to assign a service class depending on the system the job is >running on? Yes. SI/SIG System Instance (Group) We are running z/OS 1.9. Been around since OS/390, IIRC. - Too busy driving to stop for gas! -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Assigning service class depending on system
how about by Qualifier Type "SSC", or Subsystem Collection Name, in Classification Rule for JES. 2009/5/27 גדי בן אבי > Hi, > > > > Is it possible to assign a service class depending on the system the job is > running on? > > > > We are running z/OS 1.9. > > > > TIA > > > > Gadi > > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO > Search the archives at http://bama.ua.edu/archives/ibm-main.html > -- Cobe Xu Best Regards --- zOS Performance & Capacity Analyst E2E Performance Analyst Email: cob...@gmail.com --- -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Assigning service class depending on system
>The Classification Rules are run when the job enters the system, so the >Service class is already defined when job starts executing. Incorrect. You can use System Instance, or System Instance Group in the classificatio section, by sub-system. At my last shop, we did it to encourage TSO users to sign on to development, rather than production. TSODEV was set up as IMP=1, and a relatively large first period. It was under SI DEVD -- obviously the names have been changed to protect the guilty. On the Production machine, the service class was set to IMP=4, and a very small period one. It ran below production batch. It can be done, and I've found a couple of uses for it, but, along with CPU/Memory Critical, it violates the architecture of the WLM. (Some [now retired] IBM Performance people agreed with me, but it's here to stay) - Too busy driving to stop for gas! -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Assigning service class depending on system
"Ted MacNEIL" wrote in message news:<471434171-1243413448-cardhu_decombobulator_blackberry.rim.net-4713 484...@bxe1305.bisx.prod.on.blackberry>... > >The Classification Rules are run when the job enters the system, so the Service class is already defined when job starts executing. > > Incorrect. > You can use System Instance, or System Instance Group in the classificatio section, by sub-system. > Yes, but still the SC is determined when the job is submitted, not when the job starts to run on one of the systems of the MAS. And that is what Gadi asked, dependent on where the job runs. Kees. ** For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch Airlines) is registered in Amstelveen, The Netherlands, with registered number 33014286 ** -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Assigning service class depending on system
>Yes, but still the SC is determined when the job is submitted, not when the >job starts to run on one of the systems of the MAS. And that is what Gadi >asked, dependent on where the job runs. Depends on the job type, and whether you are using WLM-Managed INITs or not. TSO, STC, ASCH, all support System Name (SY -- not SI, as I originally [and incorrectly] stated). JES2 supports it, according to the manual, but I couldn't figure out (in my skimming), whether it's submitting, converting, or executing system, and whether WLM-Managed INITs make a difference. When I have more time, I'm going to take a closer look. - Too busy driving to stop for gas! -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Assigning service class depending on system
On Wed, 27 May 2009 08:29:34 +, Ted MacNEIL 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:mark.zel...@zurichna.com 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 lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Assigning service class depending on system
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 TNGHIGHBAT 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:ibm-m...@bama.ua.edu] On Behalf Of Mark Zelden Sent: Wednesday, May 27, 2009 8:08 AM To: IBM-MAIN@bama.ua.edu Subject: Re: Assigning service class depending on system On Wed, 27 May 2009 08:29:34 +, Ted MacNEIL 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:mark.zel...@zurichna.com 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 lists...@bama.ua.edu 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 lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Assigning service class depending on system
>However, SY is not valid for a JOB, which is what the OP requested. I went back to the manual and checked. You are correct, but with my bad eyesight, I had to download the PDF and rotate the table on page 72, to figure it out. There has to be a better way to present that than a table rotated 90 degrees! Of course, I could just spring for new glasses. >It is valid for TSO, STC, OMVS, ASCH, SAP, and TCP (I think that is the entire >list). If SYSH is SAP, which I don't believe it is, then yes except for TCP. The table indicates that it is not. And, as I've already stated, I did mean SY/SYG. It's been so long since I've done it, that I'd forgotten. - Too busy driving to stop for gas! -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Assigning service class depending on system
"Diehl, Gary" wrote in message news:<448c07246fdb244e86554e7f2c6ee7a904f42...@a0116-xpo0114-s.swdc.ad.a llstate.com>... > 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!). There is a big difference in between Jes batch and DDF is this area. With DDF the work is classified when it starts execution, so the "current system" will be the system where the work runs. In the case of batch the work is classified when it enters the system and put on the input queue to be selected and processed later by one the the Jes members in the MAS complex. In this case, the "current system" is not necessarily the system where the work will run. This subject is quite similar to "system symbols in batch" and its related dilemma's. Kees. ** For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch Airlines) is registered in Amstelveen, The Netherlands, with registered number 33014286 ** -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Assigning service class depending on system
Another I didn't mention before could be to use automation or the IWMRESET WLM API to change the service class after the job is running. ISTR some examples in MVS Update (Xephon) or one of the other pubs to do this. Mark -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group - ZFUS G-ITO mailto:mark.zel...@zurichna.com z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/ Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html On Wed, 27 May 2009 09:01:59 -0500, Diehl, Gary wrote: >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 TNGHIGHBAT >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:ibm-m...@bama.ua.edu] On >Behalf Of Mark Zelden >Sent: Wednesday, May 27, 2009 8:08 AM >To: IBM-MAIN@bama.ua.edu >Subject: Re: Assigning service class depending on system > >On Wed, 27 May 2009 08:29:34 +, Ted MacNEIL >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:mark.zel...@zurichna.com >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 lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Assigning service class depending on system
>Another I didn't mention before could be to use automation or the IWMRESET WLM >API to change the service class after the job is running. Hey, Rube! Can you say 'Goldberg'? Sometimes, the job runs so quickly that it's not worth the effort. You can set up Service Class by Transaction (Job) Class. So, I would just assign job classes to specific systems, if you truly need it. But, I think the whole concept defeats the purpose of shared SPOOL (old-timer's name for MAS). Just my opinion. - Too busy driving to stop for gas! -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Assigning service class depending on system
On Wed, 27 May 2009 14:13:08 +, Ted MacNEIL wrote: >>It is valid for TSO, STC, OMVS, ASCH, SAP, and TCP (I think that is the entire list). > >If SYSH is SAP, which I don't believe it is, then yes except for TCP. It is not the same as SAP. >The table indicates that it is not. You are correct. I had just checked the WLM dialogs on a 1.9 system and when using a "?" SY showed up as valid for TCP. But all types did. That was fixed in 1.10. Regarding SAP, since it isn't a standard WLM subsystem, the same is true... it showed all classification types as valid when I used a question mark to display the valid types. So I really don't know if SY is valid or not for SAP (it probably isn't). It's a moot point since DB2 V8 anyway, because SAP uses DDF now instead of ICLI. Mark -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group - ZFUS G-ITO mailto:mark.zel...@zurichna.com 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 lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: (CORRECTION) Assigning service class depending on system
My bad.
It's SY -- System Name
And SYG -- System Name Group.
I double checked the manual -- should have done that beforehand.
Sorry! (8-{[}
--Original Message--
From: (yahoo) Ted MacNEIL
Sender: IBM Mainframe Discussion List
To: IBM Mainframe Discussion List
ReplyTo: IBM Mainframe Discussion List
Sent: May 27, 2009 04:37
Subject: Re: Assigning service class depending on system
>The Classification Rules are run when the job enters the system, so the
>Service class is already defined when job starts executing.
Incorrect.
You can use System Instance, or System Instance Group in the classificatio
section, by sub-system.
At my last shop, we did it to encourage TSO users to sign on to development,
rather than production.
TSODEV was set up as IMP=1, and a relatively large first period.
It was under SI DEVD -- obviously the names have been changed to protect the
guilty.
On the Production machine, the service class was set to IMP=4, and a very small
period one.
It ran below production batch.
It can be done, and I've found a couple of uses for it, but, along with
CPU/Memory Critical, it violates the architecture of the WLM.
(Some [now retired] IBM Performance people agreed with me, but it's here to
stay)
-
Too busy driving to stop for gas!
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
-
Too busy driving to stop for gas!
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
