Ted, I totally disagree. Configuring Q-Depth correctly from the get-go is just as important as configuring PAV and HYPERPAV correctly. I call it preventative maintenance.
I guess the approach you prescribe goes with your tag line :-) Ron > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On > Behalf Of Ted MacNEIL > Sent: Monday, August 18, 2008 12:58 PM > To: [email protected] > Subject: Re: [IBM-MAIN] Here we go again (was z/OS Hot Topics 19) > > >I don't know 'NIX internals, but I would find a queue depth of 4, let > alone 16 or 32 as totally unacceptable in z/OS land. That is what PAV > is for, to reduce the queue depth. > > Wrong answer. > What service is being delivered. > Is it acceptable? > YES ---> Monitor > NO ---> Fix whatever the problem is > Monitor > > Looking at things like Queue Depth when there is no problem is an "if > it ain't broke; don't fix it" issue. > > - > 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 ---------------------------------------------------------------------- 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
