On Monday 27 July 2009 14:45, Staller, Allan wrote: > A little while ago I had posed a question about having "applications" > libraries in the system LNKLST. Some were for it, some were against it. > One of the prominent reasons for being against it was the need to do > an LLA refresh after implementing any changes to an application library. > I agreed that this was a disadvantage and looked around to see > if I could get around it.
I suggest to look at the LINKLLA program which is available in file 183 of the CBT tape (since 1992) as well as here: http://gsf-soft.com/Freeware/ The LINKREFR example below shows a link-edit step which, also, refreshes LLA for the module specified on SYSLMOD. IIRC, I wrote the LINKLLA program in the late 1980s and used it until 1996. Frankly, I wish the BINDER had a REFRESH_LLA option when IBM started to distribute it. -- Gilbert Saint-Flour GSF Software http://gsf-soft.com/ EXAMPLES 1: invoke the linkage-editor then refresh LLA for the module; SYSLMOD DD specifies a member name, and the invocation JCL contains a SYSLIN DD //LINKREFR EXEC PGM=LINKLLA,PARM='LIST,MAP,RENT' //SYSLIN DD DSN=*.HLASM.SYSLIN,DISP=(OLD,PASS) //SYSLMOD DD DSN=<library-name(member)>,DISP=SHR //SYSPRINT DD SYSOUT=* 2: refresh LLA for a whole library (SYSLMOD DD does not specify a member). Do not call the linkage-editor. //WHOLELIB EXEC PGM=LINKLLA //SYSLMOD DD DSN=<library-name>,DISP=SHR //SYSPRINT DD SYSOUT=* 3: refresh LLA for only a member (SYSLMOD DD specifies a member) Do not call the linkage-editor. //ONEMBR EXEC PGM=LINKLLA //SYSLMOD DD DSN=<library-name(member)>,DISP=SHR //SYSPRINT DD SYSOUT=* ---------------------------------------------------------------------- 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
