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 [email protected] 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 [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
