Tony, Yeah, I also thought. I am assuming, bad word, that the COBOL call will be resolved correctly
Sent from my iPad Scott Ford Senior Systems Engineer www.identityforge.com On Mar 8, 2012, at 12:56 PM, Tony Harminc <t...@harminc.net> wrote: > On 8 March 2012 11:57, Tim Zielke <tim.zie...@aonhewitt.com> wrote: > >> Our application team would like to change just the BA4C1426 code and then >> relink the change into the existing modules. So for the example below, >> BA4C1976 would not be recompiled, but the binder step would be run to update >> the existing BA4C1976 load module with a new CSECT for BA4C1426. > > I may well be missing the real question, and I don't know COBOL or its > potential intricacies, but it seems to me trivial to replace one CSECT > in an existing load module. Essentially you want to INCLUDE the new > module, INCLUDE the existing load module, and save the result. > Something like > > //SYSLMOD DD DSN=main.loadlib > //NEWMOD DD DSN=load.library.where.you.put.the.new.module > //SYSLIN DD * > INCLUDE NEWMOD(BA4C1426) > INCLUDE SYSLMOD(BA4C1976) > NAME BA4C1976(R) > > And that's it. > > Tony H. > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
