_______________________________________________________________________________________
Note: This e-mail is subject to the disclaimer contained at the bottom of this message. _______________________________________________________________________________________ >Date: Thu, 10 Apr 2008 14:47:21 -0400 >.From: "King, Jeffrey E" <[EMAIL PROTECTED]>. >Subject: Re: VLF/LLA Management > >Stephen - > >I'm not sure if you are familiar with or running CA-PDSMAN, but it >provides a multitude of LLA management functions, including the >automatic updating of the LLA cache for individual members in libraries >being managed in Freeze mode. > >Regards, >Jeffrey King >CA >PDSMAN Principle Support Engineer >Columbus, Ohio USA >Tel: +1 614 785 2743 or x62743 >[EMAIL PROTECTED] Jeff, We actually have PDSMAN installed, but unfortunately it was part of the problem. Originally, the private library was managed by CA-Quickfetch & PDSMAN to manage the I/O for our IMS MPRS. We converted that to use LLA/VLF & PDSMAN. Unfortunately sometime later it dropped out of LLA management (IEACMD00 in SYS1.IBM.PARMLIB was the culprit - we thought that it was being managed by our automation system), but we never really noticed due to a processor & disk subsystem upgrades. I/O to this dataset averaged at about 1.5 Million per hour (thank you dynamic PAVS !). Then, a few weekends ago we upgraded CICS from TS2.2 to TS 3.1 & DB2 from V7 to V8, and whammo! I/O skyrocketed to nearly 5 Million per Hour (Dynamic PAVS saved our bacon, performance was very slow, but not enough to kill the application altogether). Strobe indicated that PDSMAN, whilst not the main culprit, was heavily involved in the I/O, specifically the SPFEDIT enq. Most of the I/O was actually directory searching. Putting the dataset back under LLA control dropped the I/O dramatically and resolved performance issues, but PDSMAN is still getting involved somehow in the I/O. So we are removing all PDSMAN parameter entries for this dataset, and when we are happy, we will re-review PDSMAN control for this dataset, based on Dev team requirements. The other thing is that this dataset is managed by our source management software, and we want to control when it gets refreshed, which is not necessarily at update time. Thanks for the interest though (the local PDSMAN support have also contacted me, and he is assisting in our research of this). Thanks & Regards, --------------------------------------------- Stephen Hall Team Leader - Host Systems Technology Services - Infrastructure INSURANCE AUSTRALIA GROUP (IAG) www.iag.com.au --------------------------------------------- _______________________________________________________________________________________ The information transmitted in this message and its attachments (if any) is intended only for the person or entity to which it is addressed. The message may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information, by persons or entities other than the intended recipient is prohibited. If you have received this in error, please contact the sender and delete this e-mail and associated material from any computer. The intended recipient of this e-mail may only use, reproduce, disclose or distribute the information contained in this e-mail and any attached files, with the permission of the sender. This message has been scanned for viruses with Symantec Scan Engine and cleared by MailMarshal. _______________________________________________________________________________________ ---------------------------------------------------------------------- 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
