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
Not that I have an answer but I wanted to confirm that you really meant 800,000
EXCP's and not 800,000,000 EXCP's. Correct? (800,000k = 800,000,000)
On Tue Mar 27 11:46 , GAVIN Darren * OPS EAS [EMAIL PROTECTED] sent:
Does anyone know why when an Internal Sort is performed while a program
Yes I had meant 800,000 (close to 80 times more EXCP from with the
internal sort)
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Gary Green
Sent: Tuesday, March 27, 2007 12:17 PM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: Cobol Internal sort
I can think of one POSSIBLE difference. If you have compiled with FASTSRT
compiler option (which I recommend that people ALWAYS use), then to get the
DL/I input you must be using an INPUT procedure. This puts this part (not
the OUTPUT part) into native COBOL (not FASTSRT) mode.
OTOH, when you
Sorry - I have to believe this is a coding error. My guess is that
many of the 6 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
2:17 PM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: Cobol Internal sort and DLI Databases
Sorry - I have to believe this is a coding error. My guess is that
many of the 6 segments were re-read after every success selection
(RELEASE) because the logic in the input procedure probably started
6 matches
Mail list logo
