Try (watch the wrap): http://www-03.ibm.com/servers/resources/servers_eserver_zseries_zos_wlm_ pdf_cmgbatch_pdf_wlm_goal_based_initiator_management.pdf
http://www-03.ibm.com/servers/resources/servers_eserver_zseries_zos_wlm_ pdf_wlminits_pdf_wlminitsjm.pdf and http://www-03.ibm.com/servers/resources/servers_eserver_zseries_zos_wlm_ pdf_velocity_pdf_velocity.pdf for more detail. The JES2 classification rules should not classify work into common Service Classes between WLM Managed and JES managed inits. An appropriately aggressive goal may allow you to do what you want to do, but since WLM managed inits are sensitive to non-WLM managed work, the goal may need to be highly aggressive in order to accomplish your purpose. -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of John Mattson Sent: Monday, December 08, 2008 8:40 PM To: [email protected] Subject: Re: /*PRIORITY change without JCL change I have been doing RTFM on Jes Init & Tune Guide and find myself back in a quandry. My original purpose was to get an ever changing list of, overnight batch, critical path,jobs priority access to initiators without changing their JCL manually. But here is what I read in the Guide about WLM inits Batch jobs that are part of a critical path, such as the overnight ?batch window? should remain in JES managed job classes. Alignment of initiator mode and service classes: All jobs with the same service class should be managed by the same type of initiation. For example, if job classes A and B are both assigned to the HOTBATCH service class, and JOBCLASS(A) is MODE=WLM, while JOBCLASS(B) is MODE=JES, workload management will have a very difficult time managing the goals of the HOTBATCH service class without managing class B jobs. Queue delay measurements: If you have large job execution queues, the queue delay can dominate the response time or velocity. This may cause the system to not address other delays because it would not significantly affect the performance index (PI). Response time does not include TYPRUN=HOLD or JCLHOLD delays, but does include the following: Operational delays (jobs or job class held by operator command) System or resource affinity delay Scheduling delay because of class limits, duplicate jobnames Time waiting for an Initiator What I currently have is a lot of jobs waiting for a class "Q" initiator, and I want to get my "loved ones" to the init first. It looks like using WLM to get my priority jobs to the initiator faster may totally mess up WLM's calculations because it will start measuring all of that Waiting for Init Time. I think this puts me back at where I started. Perhaps what I need is an Exit which can read a list of Jobs and raise their Input Queue Priority. Can anyone suggest the "best" exit for this? Brian Westerman <[EMAIL PROTECTED]> Sent by: IBM Mainframe Discussion List <[email protected]> 12/03/2008 11:31 PM Please respond to IBM Mainframe Discussion List <[email protected]> Expire Date: 12/08/2010 To [email protected] cc Subject Re: /*PRIORITY change without JCL change You could write it as either a JES input exit (or text) or an SMF exit, either will work fine. There are several samples on the CBT tape that you can use as a start, but none that I'm aware of that do exactly what you want. Why not use JES's WLM options instead? Brian ---------------------------------------------------------------------- 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 ---------------------------------------------------------------------- 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
