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 lists...@bama.ua.edu with the message: INFO IBM-MAIN

Reply via email to