Quote Apologies. I missed to mention that depending on a record that matches in the 2nd file, there are some random reads that refer back to a previous record as per the business logic. Hence, the second file has to be VSAM. We also see a similar behavior with few other programs that do skip sequential reads on other VSAM files. Unquote
So do the two file match and utilise the VSAM (second file) for random read where it's required. You won't tune your way out of this. On Mon, Jan 8, 2018 at 6:03 AM, Gerhard Adam <[email protected]> wrote: > To me it still looks like you don't have enough index buffers. My > calculation suggests you need at least 137 buffers to keep the index set in > memory. > > > > Sent from my iPhone > > > On Jan 7, 2018, at 10:21 AM, Arun Venkatratnam < > [email protected]> wrote: > > > > Ron, > > > > About 80% of the records qualify from the second file. I tried running > the job with BUFND of 2 for the second file. It increased the EXCPs > significantly (from strobe report) on the data records for the 2nd file and > the CPU time went over the other runs and the elapsed time also increased. > The job runs better with higher values of BUFND for the second file. > > > > You had mentioned that the job reads 30 CI for every skip-seq access. > Could you please tell how did you arrive at that number. LISTCAT shows that > for a CISZ of 26KB, there are 30 CI in 1 CA. > > > > > > Thanks > > Arun > > > > ---------------------------------------------------------------------- > > For IBM-MAIN subscribe / signoff / archive access instructions, > > send email to [email protected] with the message: INFO IBM-MAIN > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > -- Wayne V. Bickerdike ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
