When reading your email again I think you are really trying to solve a different problem.
You have long running jobs. How a file is sized, 10 cylinders used in a 10 cylinder data set or 10 cylinders used in a 100 cylinder data set, is not going to change how fast a job runs. The extra 90 cylinders are just never looked at. BUT, if you have 10 cylinders of data that is poorly blocked and takes 100 cylinders to hold it, THAT is a different question. That will take more time to process. I have not been in DASD performance for a long time, so I don't know of any CBT file or commercial product that has something that can analyze RECFM/LRECL/BLKSIZE relationships. Or maybe I totally missed her question. Christopher Y. Blaicher BMC Software, Inc. Austin Development Labs (512) 340-6154 The comments made are my personal opinions. BMC Software, Inc. makes no representations or promises regarding the reliability, completeness, or accuracy of the information provided in this discussion; all readers agree not to rely on this information or take any action against BMC Software in response to this information. -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Lizette Koehler Sent: Thursday, April 26, 2007 7:36 AM To: IBM-MAIN@BAMA.UA.EDU Subject: Better way to count records We are trying to determine if the space allocation is efficient for these files. There has been a lot of copying of JCL over the years and we feel that perhaps this is causing some issue because a lot of the files are being resized by DTS Software (DIF and SRS). This we believe is adding to the long run times of these jobs. If the files could be sized better, then perhaps the jobs would not run as long. All thoughts and opions are appreciated. Lizette ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
