Thanks, I did a couple of things, including $SJ-ing a number of jobs and things seemed to start moving again.
Kees. > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of Allan Staller > Sent: 06 April, 2017 14:55 > To: [email protected] > Subject: Re: Unexplained delays in WLM managed jobclasses > > Look for the "happy system" syndrome. > > I.e. the system is meeting it's SLA targets, so WLM feels no need to > start additional initiators. This will most likely require near real- > time IEHIBALL activity. > > Adjusting the Service Class Goals may help. > Also turn on SMF 99's and ask IBM for their opinion. > > In my experience with this phenomenon, this has been due to the *exact* > job mix running at that time. > > Something as trivial as starting an additional job is enough to stir the > pot and everything becomes "right" very quickly. > > Can't give you any direct advice, as the answer is "it depends". > > HTH, > > <snip> > We sometimes experience long delays in job initiation, which I cannot > explain. It concerns a WLM managed jobclass, which is filled by Control- > M. Every now and then, we see e.g. 4 jobs running and an accumulating > number of jobs in the input queue, up to more than 100, waiting for one > or more hours. When one job ends, the next job starts, but the number of > executing jobs remains 4. > > I have ruled out all obvious causes, such as a heavy loaded system, jobs > not eligible to run on that system etc. etc. > > From the Redbook "System Programmer's Guide to: Workload Manager" I > found that JES2 is only following WLM, it will start a job when WLM has > started an Initiator ("If there are no free initiators, jobs run > wherever another job finishes, or WLM starts new initiators."). The > $DSRVCLASS,LONG displays the number of initiators WLM has started for > JES2 to use. > > So the number of running job is fully determined by WLM and I am trying > to find out why WLM does not start more initiators. The first period of > the jobs has a Response Goal of 30 seconds. Since this includes a job's > Input Queue time and jobs were waiting for several hours in the input > queue, this only should have been a reason to start extra Initiators. > > I have produced SMF record 99 subtype 6 and it displays a lot of > information about the status of the Service Classes, like MPL-IN-TARGET > and MPL-OUT-TARGET, but I have the feeling that this applies to swapping > IN and OUT of already running tasks and does not say anything about jobs > in the Input Queue. > > My question is: which metrics can tell me more about WLM's decisions to > start Initiators, not start them or stop them? > </snip> > > > ::DISCLAIMER:: > ------------------------------------------------------------------------ > ------------------------------------------------------------------------ > ---- > > The contents of this e-mail and any attachment(s) are confidential and > intended for the named recipient(s) only. > E-mail transmission is not guaranteed to be secure or error-free as > information could be intercepted, corrupted, > lost, destroyed, arrive late or incomplete, or may contain viruses in > transmission. The e mail and its contents > (with or without referred errors) shall therefore not attach any > liability on the originator or HCL or its affiliates. > Views or opinions, if any, presented in this email are solely those of > the author and may not necessarily reflect the > views or opinions of HCL or its affiliates. Any form of reproduction, > dissemination, copying, disclosure, modification, > distribution and / or publication of this message without the prior > written consent of authorized representative of > HCL is strictly prohibited. If you have received this email in error > please delete it and notify the sender immediately. > Before opening any email and/or attachments, please check them for > viruses and other defects. > > ------------------------------------------------------------------------ > ------------------------------------------------------------------------ > ---- > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN ******************************************************** 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 [email protected] with the message: INFO IBM-MAIN
