You should see a substantial reduction in I/O with SMB as is my experience.
I use a special DATACLAS in SMS for SMB as is required. John T. Abell Tel: 800-295-7608 Option 4 President International: 1-416-593-5578 Option 4 E-mail: [email protected] Fax: 800-295-7609 International: 1-416-593-5579 International Software Products www.ispinfo.com This email may contain confidential and privileged material for the sole use of the intended recipient(s). Any review, use, retention, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive on behalf of the named recipient), please contact the sender by reply email and delete all copies of this message. Also,email is susceptible to data corruption, interception, tampering, unauthorized amendment and viruses. We only send and receive emails on the basis that we are not liable for any such corruption, interception, tampering, amendment or viruses or any consequence thereof. -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Massimo Biancucci Sent: Tuesday, January 16, 2018 11:28 AM To: [email protected] Subject: Re: VSAM Performance - CPU reduction Arun, in my recent experiences I've got bif improvement using SMB (System Managed Buffer). If I'm not wrong both DS are EXTENDED so you could. Try coding into the DD "AMP=('ACCBIAS=SO')" for the main sequentially read file and "AMP=('ACCBIAS=DO')" for the second one. At the same time enlarge the REGION size. Depending on your HW configuration you could consider using compression on both DS. It will increase CPU time (or not so much if you've got zEDC) but could improve elapsed .... depending on CPU contention. Hope this helps. Regards. Massimo 2018-01-06 1:20 GMT+01:00 Arun Venkatratnam <[email protected] >: > Hi All, > > We are looking to improve the performance of a COBOL program that > processes 2 VSAM files. The first file is the I/P file and every > record read from the input VSAM file is searched for a matching record > in the other file and a report is written. The program also applies > some business rules while comparing each matching record. > > The I/P file is read sequentially while the other file is read in a > skip sequential basis. The test files that were used had 32M records > each while production files have 110M records each. > > Attached is the strobe report from the execution of the test job. The > test job takes nearly 7 CPU minutes and was profiled to capture about > 1 CPU minute of execution time. > > We are attempting to optimize the VSAM access to these files as it is > seen to take more than 50% of the CPU consumed by this job. > > In the 'Attribution of CPU execution time' section, we see that the > major contributors are the components 'QSAM INIT I/O & EXITS' (Module > IGZEQBL) and PARTITION COMMUNICATION. > > Could you please help us understand: > > 1.What these components are > 2.Why is QSAM access used instead of VSAM I/O access. > 3.What needs to be done to reduce the CPU consumption by these components. > > Thank you > > Arun > > > ------------------------------------------------------------ > ------------------------------------------------------------ > ------------------------------------------ > > 1Strobe* PERFORMANCE PROFILE PROGRAMA > 01/02/2018 PAGE 42 > > - #ACE ** ATTRIBUTION OF CPU EXECUTION > TIME ** > -.COBLIB IGZCPCO IGZEVIO VSAM INPUT/OUTPUT > ---------------------------WAS INVOKED BY--------------------- > -----------------VIA----------------------- CPU TIME % > XACTION MODULE SECTION DESCRIPTION MODULE > SECTION DESCRIPTION SOLO TOTAL > > .LELIB CEEBINIT LE/370 BATCH INIT/TERM > .32 .32 > .LELIB CEEBINIT LE/370 BATCH INIT/TERM > IGZEQBL QSAM INIT I/O & EXITS 1.93 1.93 > > XACTION MODULE SECTION LOCATION LINE SOURCE TEXT MODULE > SECTION DESCRIPTION > > PROGRAMA PROGRAMA 003522 > > 1.30 > 1.30 > > > ----- ----- > > > 3.55 3.55 > -.VSAM IDA019L1 VSAM RECORD MANAGEMENT > ---------------------------WAS INVOKED BY--------------------- > -----------------VIA----------------------- CPU TIME % > XACTION MODULE SECTION DESCRIPTION MODULE > SECTION DESCRIPTION SOLO TOTAL > > .LELIB CEEBINIT LE/370 BATCH INIT/TERM > IGZEQBL QSAM INIT I/O & EXITS 1.84 1.84 > .LELIB CEEBINIT LE/370 BATCH INIT/TERM > IGZEQBL CURRMEM QSAM INIT I/O & EXITS 4.34 4.38 > .LELIB CEEBINIT LE/370 BATCH INIT/TERM > IGZEQBL DVFILE QSAM INIT I/O & EXITS .03 .03 > .LELIB CEEBINIT LE/370 BATCH INIT/TERM > IGZEQBL PREVMEM QSAM INIT I/O & EXITS 22.48 22.51 > > XACTION MODULE SECTION LOCATION LINE SOURCE TEXT MODULE > SECTION DESCRIPTION > > PROGRAMA PROGRAMA 003522 > IGZCPCO CURRMEM PARTITION COMMUNICATION 4.15 4.19 > PROGRAMA PROGRAMA 003522 > IGZCPCO IGZEVIO VSAM INPUT/OUTPUT .57 .57 > PROGRAMA PROGRAMA 003522 > IGZCPCO PREVMEM PARTITION COMMUNICATION 16.80 16.80 > > > ----- ----- > > > 50.22 50.32 > > ---------------------------------------------------------------------- > 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 --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
