Mark, I read the original post differently, and my reading of it makes it sound like if he just does the catalog search it comes back in a matter of seconds, then when he hits the "shift right" button to get the space info, that is when he gets the horrendous response time. I don't think it is a catalog problem.
I.e., where Anthony says " If the Initial View is changed to 1. Volumes then the performance is much the same." , he means that he gets a 10 second response time, then when he shifts right to get the space info, release 12 comes back in seconds and release 13 takes 20 minutes. Anthony, can you enlighten us on this? If your initial display is Volume, do you get the 10 second response time on release 13? Rex -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Mark Zelden Sent: Tuesday, April 23, 2013 8:22 AM To: [email protected] Subject: Re: ISPF 3.4 Performance degradation on z/OS 1.13 On Mon, 22 Apr 2013 22:33:59 -0500, Anthony Fletcher <[email protected]> wrote: >We have a customer running on a z800 in a capped LPAR. >We just converted them from z/OS 1.12 to z/OS 1.13 and have found that >performance has degraded. > >They are looking at a list of data sets - approx 98,000 under a HLQ, >say ABCD with the Initial view set to 2. SPACE > >On z/OS 1.12 this list was retrieved in under 10 seconds On z/OS 1.13 >this list took 20 Minutes to return. > >If the Initial View is changed to 1. Volumes then the performance is >much the same. > >The view is paged right to get the space values, on the 1.12 system it comes >back in seconds > > on the 1.13 system it takes minutes to come back. > >Many of the 98,000 data sets are on TAPE or migrated. > >Anyone recognise a feature that came with z/OS 1.13 that might cause this >change in behaviour? > Hmmm. I don't think this is related to z/OS 1.13 per se. But obviously something seems wrong. The first thing I can think of is maybe the COFVLFxx member was not carried forward and catalogs are not using VLF or perhaps your client was using enhanced catalog sharing and that isn't active. But even so, from 10 seconds to 20 minutes seems extreme even without VLF or ECS. I say this because you mentioned that even the initial view of VOLUME takes a long time and that is just a catalog lookup and that has to be done before the space usage is looked at in the vtocs. What if you try doing some lists without a catalog? Use a HLQ and an generic volser like SYS* for example. Another thing you can try is to use the sample CSI (catalog search interface) exec SYS1.SAMPLIB(IGGCSIRX) or my modified sample from my web site (CATSRCH) and see how that performs. That could help narrow down the performance issue. Regards, Mark -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS mailto:[email protected] Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html Systems Programming expert at http://expertanswercenter.techtarget.com/ ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN The information contained in this e-mail may contain confidential and/or privileged information and is intended for the sole use of the intended recipient. If you are not the intended recipient, you are hereby notified that any unauthorized use, disclosure, distribution or copying of this communication is strictly prohibited and that you will be held responsible for any such unauthorized activity, including liability for any resulting damages. As appropriate, such incident(s) may also be reported to law enforcement. If you received this e-mail in error, please reply to sender and destroy or delete the message and any attachments. Thank you. NOTICE: This e-mail message, including any attachments and appended messages, is for the sole use of the intended recipients and may contain confidential and legally privileged information. If you are not the intended recipient, any review, dissemination, distribution, copying, storage or other use of all or any portion of this message is strictly prohibited. If you received this message in error, please immediately notify the sender by reply e-mail and delete this message in its entirety. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
