On 8 Mar 2012 09:51:54 -0800, in bit.listserv.ibm-main you wrote: >This would require a recompile of pretty much the entire application which is >around 11,000 load modules. This COBOL application is written in proprietary >object oriented COBOL and each load module represents an object oriented class >(for the most part). So a recompile of the entire application would require a >testing/migration effort that is too arduous for the application team. > >However, if we can just change the statically compiled BA4C1426 program and >relink it into the existing 11,000 load modules, it significantly reduces the >scope of the change to something that is more manageable from a testing and >migration effort.
Because of the way optimization works, BA4C1426 may not be a separate CSECT and may even be inline code with no actual CALL being issued. If you have a smart change management system that can trigger recompiles based on copybook changes, that is probably the way to go. The other choice is to scan the source library for all instances of COPY BA4C1426 and generate the compile jobs for these programs. Clark Morris > >Thanks, >Tim Zielke >CICS/MQ Systems Programmer >Aon Hewitt > > >-----Original Message----- >From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of >Scott Ford >Sent: Thursday, March 08, 2012 11:33 AM >To: [email protected] >Subject: Re: JCL example to relink a CSECT into an existing load module > >Tim, > >What wouldn't you want to compile and link the appropriate way ? Just curious >here and not judging...what's the reasoning ? Maybe other methods ... > >Sent from my iPad >Scott Ford >Senior Systems Engineer >www.identityforge.com > > > >On Mar 8, 2012, at 11:57 AM, Tim Zielke <[email protected]> wrote: > >> I sent the following to the CICS LISTSERV, and someone mentioned that the >> IBM-MAIN would be a better place for this type of inquiry. I did get some >> good JCL examples from the CICS LISTSERV, but if someone has some past >> experience of this working with specifically COBOL, that would be great. >> Some of these existing COBOL modules that will be relinked with the new >> BA4C1426 CSECT were compiled/linked under COBOL-II. We now use Enterprise >> COBOL 3.4 and the new BA4C1426 will be generated with Enterprise COBOL 3.4. >> >> Hello, >> >> We have 1000's of CICS COBOL programs that COPY in a COBOL source program >> called BA4C1426 and then statically call it. I have given some code >> examples of how this works below. In this example, COBOL program BA4C1976 >> does a COPY to bring in the COBOL source of BA4C1426 at compile time and >> then statically calls BA4C1426. >> >> 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. >> >> Would anyone have some examples of existing JCL of how to do the relink step >> of swapping in a new CSECT into an existing load module? >> >> I was going to research it, but was thinking someone on this list has >> already done it and would have an example already available. I didn't find >> any examples quickly with google searches. >> >> >> Here is an example of how a module like BA4C1976 references BA4C1426: >> >> Identification Division. >> * Object-Class PrsnDBPmtInstRef. >> Program-Id. BA4C1976. >> >> . >> . >> . >> Procedure Division using Self >> Client-Variables >> Global-Variables >> Arglist. >> . >> . >> . Call 'BA4C1426' >> Using DfhEiBlk DfhCommArea >> TV-023-PRSNDBPMTINSTRSLT-LS >> Client-Variables >> Global-Variables >> ParmList >> . >> . >> . >> COPY BA4C1426. >> >> End Program BA4C1976. >> >> >> The BA4C1426 source that is referenced by the "COPY BA4C1426" line is a >> COBOL program: >> >> Identification Division. >> * Object-Class PARNLIST. >> Program-Id. BA4C1426. >> . >> . >> . >> COBOL source >> . >> . >> . >> End Program BA4C1426. >> >> >> Thanks, >> Tim Zielke >> Aon Hewit >> CICS/MQ Systems Programmer >> >> >> ---------------------------------------------------------------------- >> For IBM-MAIN subscribe / signoff / archive access instructions, >> send email to [email protected] with the message: INFO IBM-MAIN > >---------------------------------------------------------------------- >For IBM-MAIN subscribe / signoff / archive access instructions, >send email to [email protected] with the message: INFO IBM-MAIN > >---------------------------------------------------------------------- >For IBM-MAIN subscribe / signoff / archive access instructions, >send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
