Absolutely doing static-link below the line should be your LAST choice. Consider:
1) Change static calls to CALL identifier for 24-bit code (Don't change DYNAM/NODYNAM compiler option) and use DATA(24). 2) As others have suggested, see if you need the assembler routines at all. If they are primarily "I/O" modules, check out the COBOL "EXTERNAL" attribute and see if you can't (easily) convert them to COBOL. One thing to be VERY careful of when doing "batch conversions" is to make certain you are aware of performance issues. I have seen VS COBOL II to Enterprise COBOL conversions that "died" because inadequate time was allocated for performance tuning (especially for LE run-time options and COBOL compiler options). My guess is that your Assembler is NOT "LE-enabled" which is an entire other area for consideration. If you have any Assembler "drivers" (rather than subroutines) this becomes a HUGE issue in such a conversion. "Leslie Wagner" <[email protected]> wrote in message news:<listserv%[email protected]>... > I am the original poster of this on bit.listserv.ibm-main. PJ Farley ccd it here - > thanks Pete! > > These assembler modules all do I/O against VSAM and QSAM files. Open, > close, gencb, modcb, acb macros mostly that I've seen so far. I'm still going > thru them. > > Some of them were upgraded from older DOS assembler code 37 years ago or > so. I think we want to take the path of least resistance here, but also wanted > to know just what we might be losing by taking that path. ---------------------------------------------------------------------- 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
