Sometimes I find Strobe reports misleading when reviewing them They do a great job in showing how the process is working. But performance analysis takes a lot of experience to be able to use them well.
QSAM is Queued Sequential Access Method - it is what is used to read your data and return it to your program for action. What I think you should do is to look at different areas you can control with your JCL and program You might be seeing issues with physical dasd retrieval of the data. But that is just a guess. Have you looked at adding STRNO on the VSAM definition or using RLS to provide the records to be instorage? In your JCL for the job, have you coded BUFND, or BUFNI or BUFSP? Could you provide the LISTC ENT(vsam-name-here) ALL for us to review? Is the File KSDS, ESD, or Does it have INDEX/PATH/AIX? What are your share options? When was the Cobol program last compiled and lked? What version of Cobol was being used when it was last compiled and lked? Has a review of the Cobol program logic been done to see if any performance can be gotten there? What version of z/OS are you running on? Are there any other processes using this VSAM dataset when it is being accessed by this program? DB2, CICS, etc.... Have you reviewed RMF Data to see if the DASD was performing well? Or if the program was preforming well The Strobe report will not be the final decision on what is going on with this process. RMF, JCL analysis, Program Analysis are all required to determine how to improve your process. Lizette > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of Arun Venkatratnam > Sent: Friday, January 05, 2018 11:29 PM > To: [email protected] > Subject: Re: VSAM Performance - CPU reduction > > Just to be clear. The similar behavior i am referring to is the strobe report > listing QSAM INIT I/O & EXITS and PARTITION COMMUNICATION as the top CPU > contributors. > > ---------------------------------------------------------------------- > 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
