1. Have you looked at adding STRNO on the VSAM definition or using RLS to provide the records to be instorage?
No, STRNO is not provided explicitly in the VSAM file definition.Strobe apparently shows the number of Strings is 48. RLS is also not used. 2. In your JCL for the job, have you coded BUFND, or BUFNI or BUFSP? Yes BUFND, BUFNI were provided. TEST.SYLFA4V.VTST.MEMBER.CLUSTER - BUFNI = 30, BUND=225. This file is accessed sequentially TEST.SYLFA4V.VTST.MEMBER.PREVDAY.CLUSTER BUFNI = 120, BUFND = 240. This file is accessed skip-sequentially. 3. 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? These are VSAM KSDS files, no AIX/PATH. 4. What are your share options? Share options are 2,3 . We also tried with 1,3 5. When was the Cobol program last compiled and lked? The program was compiled on 03/31/2017 6. What version of Cobol was being used when it was last compiled and lked? IBM ENTERPRISE COBOL FOR Z/OS 4.2.0 7. Has a review of the Cobol program logic been done to see if any performance can be gotten there? Not yet, we are looking to improve performance of all programs that do VSAM reads (mainly the ones that do SKIP SEQUENTIAL reads) 8. What version of z/OS are you running on? z/OS 02.01.00 9. Are there any other processes using this VSAM dataset when it is being accessed by this program? DB2, CICS, etc.... No, there are no other processes accessing the file. 10. Have you reviewed RMF Data to see if the DASD was performing well? Or if the program was preforming well RMF Disk activity reports were not reviewed. But, we did a stand-alone test to see if it was sequential access or skip sequential reads was the cause of high CPU. Resp: Reading through the entire file by sequential access took 90 CPU seconds while skip-sequential took nearly 230 CPU seconds. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
