Neil, you mentioned that you were getting $HASP050: >90% JNUM messages during your problem time periods. Others have suggested PCE settings and some other ways to increase the number of internal readers, in order to increase throughput. Personally, I'd also look at ways to avoid JNUM > 90% and to increase the total number of jobs that can be in the system at any given time. Can you tell us your settings that control JNUM? Can you increase those values, without exceeding maximums (or third- party software limitations on job numbers, ranges, format of JOBID, etc)? That's where I'd start looking at to solve this issue.
Regards, Ulrich Krueger On Wed, 25 Jun 2008 18:23:59 -0400, Neil Duffee <[EMAIL PROTECTED]> wrote: >Hey there. I'm grasping at straws and am hoping someone remembers their >JES2 internals. I've looked in the JES2 Innita Tuna? manual (Ch 2. >Controlling JES2 processes) without success and can't find a RedBook >that helps. Perhaps someone remembers or can point me to a Fine Manual. >(I'll ETR otherwise.) > >Background: z/OS v1.7, DB2 v7. During our (peak) registration periods, >we experience occasional, un-explainable slow-downs in 1-3 minute bursts >on the order of 3-5 in a 2-3 day period. To date, no particular culprit >has been positively identified. Aside from 100% CPU & 20+ un- dispatched >tasks, one reported symptom is an increasing number of DB2 threads (from >OmegaMon) waiting for Stored Procedure start-ups ie. for WLM to start >another address space. (@15 TCBs each) Sure enough, once the dust >settles, there can be 10+ WLM address spaces that slowly disappear as >idle. > >This line of inquiry (among others) focuses on JES2's internal readers. >We suspect processes generating e-mail to students with a 1-1 ratio of >jobs to messages ie. 1 job=1 e-message, using SYSOUT=(*,INTRDR). (We're >also pursuing multi-step jobs since $HASP050: >90% JNUM has already been >encountered.) In a given scenario, we could have 200+ jobs with e- mail >(bulk to a large class) directed at INTRDR while WLM is trying to start >1-5 Stored Procedure address spaces via STCINRDR. > >So, the question is, presuming it's already working on INTRDR, how does >JES2 contend with this load? Are all the jobs in INTRDR converted then >JES2 switches to STCINRDR? Does STCINRDR have precedence for JES2 and >INTRDR is interrupted at the next JOB card? Are they simultaneous with >their own TCBs? Curious minds would like to know. (or even hear >speculation...) > >As mentioned before, if there's no satisfactory consensus, I'll pursue >an ETR and relay the response. Tks much folx. ---------------------------------------------------------------------- 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
