Jorge, Hipersort got some bad press when it first came out - Hiperspace thrashing when many sorts started around the same time.
Many sites resolved this by capping HIPERSORT, but after the problem was resolved many of those same sites have not gone back and removed the cap. This capping has reached MVS MYTH status, and I have seen some performance "gurus" walk in and insist that HIPERMAX is set to 0 or something small, even when there is no problem. I just want to check with you that you are not fixing something that isn't broken, and possibly slowing down some of your sorts in the process. (you may have met one of these gurus :)) Ron > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On > Behalf Of Jorge Arueira Campos > Sent: Saturday, 22 October 2005 4:45 AM > To: [email protected] > Subject: Question About DFSORT parameters > > Hello, > Someone know what are the parameters that We need use on batch, to > inibith > the utilization of HyperSpace instead SORTWORK (Dasd). > Thanks > Jorge Arueira Campos > System Specialist > Caixa Economica Federal > Sao Paulo - Brasil > > ---------------------------------------------------------------------- > 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
