> -----Original Message----- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Mark Zelden > Sent: 06 April, 2017 16:58 > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: Unexplained delays in WLM managed jobclasses > > On Thu, 6 Apr 2017 12:08:25 +0000, Vernooij, Kees (ITOPT1) - KLM > <kees.verno...@klm.com> wrote: > > >Hello, > > > >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? > > > >Thanks in advance. > >Kees. > > > > If this is z/OS 2.2, there is a bug with JES2 keeping track of the > number of WLM INITs by > serviceclass. I saw it at one of my clients and the result was way too > much work getting > routed to one of the LPARs even when that LPAR was running at or close > to 100% and > that led to some batch delays. For example, $DSRVCLASS,LONG showed 150 > INITs > for one particular serviceclass while and SDSF "INIT WLM" command showed > about 20. > > See if you have APAR OA51343 and prereq's installed. > http://www-01.ibm.com/support/docview.wss?crawler=1&uid=isg1OA51343 > > The APAR talks about a zero or negative count, but we saw a high count. > It also > applies to z/OS 2.1 but we never say any problem on z/OS 2.1. We > started seeing > the problem when z/OS 2.2 was being rolled out to the first wave of > LPARs in > a large sysplex. > > > Regards, > > Mark > --
Great! We are 2.2 and we have the OA50359 fix, but the OA51343 fix was just late for our latest update. I will check the WLM init the next case I see the problem. Btw. INIT WLM shows the number of inactive WLM Initiators,while $DSRVCLASS shows total inits and active inits, the difference must be the INIT WLM initiators. We will apply this and see if the problem is solved. Is there any metric in SMF 99 showing these figures? Thanks, 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...@listserv.ua.edu with the message: INFO IBM-MAIN
