Sorry - I have to believe this is a coding error. My guess is that many of the 60000 segments were re-read after every success selection (RELEASE) because the logic in the input procedure probably started retrieving over at the beginning of the database. Post the code.
On 3/27/07, GAVIN Darren * OPS EAS <[EMAIL PROTECTED]> wrote:
Does anyone know why when an Internal Sort is performed while a program also accessing a DLI Database That the amount of I/O against DLI increases by a few orders of magnitude? I had a program extracting data off a DLI Database inside a Sort Input phase. It was extracting only 181 records form 60,000 DLI Segments, but taking over 800,000K EXCP I/O and 10 minutes. When I instead just wrote the Sort Record to a Flat file and Eliminated the sort completely, It extract the same records, but only took 11,000 EXCP I/O and about 5 seconds. Thanks, Darren ---------------------------------------------------------------------- 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
