In an earlier post that apparently went astray I noted that the scheme of copying the same non-trivial COBOL program into "around 11,000" other COBOL source programs is not---Let me be polite---a desirable one.
This single program should be compiled just once; and the object module thus produced should then be linked, specifying NCAL, into a library that is made available for the other compile-and-link operations. This done the binder will resolve the external reference to it in these "around 11,000" source programs by including it in the executable load modules produced by compiling and linking them. When this scheme is used the single program they all call will of course be a separate replaceable CSECT in these load modules. The question whether these operations will need to be done again any time soon also needs to be examined. If so, making this common routine a dynamically loaded one should be given very serious consideration (as an earlier poster pointed out in somewhat different terms). Dynamic loading is often used gratuitously; but in this situation, where many other routines invoke the same apparently volatile subroutine, it could very well be useful. John Gilmore, Ashland, MA 01721 - USA ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
