In our site we use LLA to faster access JCL library from Tivoli Workload Scheduler (with great benefits).
I never thought about VLF and that it could be not included in the game ! Manuals refer only "fetch access". I wrote a simple "sample" and I measured that only the fetch mechanism uses VLF. I think there's no way to upgrade it. Best regards. -----Messaggio originale----- Da: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] Per conto di Tom Rusnak Inviato: giovedì 15 giugno 2006 10.36 A: [email protected] Oggetto: LLA and Cobol copybook library Hi all, I have a production Cobol Copybook library that is accessed thousands of times a day during compiles. It's only updated during one 'promote' job in the evening. I'm looking to improve it's performance by getting LLA to manage the directory which has over 10,000 members. I update the LLA with the LIBRARIES(COPYBOOK.LIB) and FREEZE(COPYBOOK.LIB) statements and it appears to work. I can update a member and both ISPF and batch still see the before member. So far so good. My first question, is this a valid/acceptable use of LLA to manage non-loadlibraries? a "D LLA" command shows the library as frozen. However, a "D LLA,STATISTICS" doesn't show any MEMBERS FETCHED or DASD FETCHES. Peter Relson's module fetch monitor doesn't show access for the non loadmodule library. Any suggestions on how to monitor the progress? Finally, Is there any way to get VLF involved as well? All the best, Tom ---------------------------------------------------------------------- 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 ---------------------------------------------------------------------- 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
