>Someone (sorry for got his name) said that with the new releases of the cobol compiler modules are no longer statically linked.
That was me. >I would guess though unless the binder execution specifies NCAL that syslib is still opened and there for read access has to be given. LE/370 is not in SYSLIB. It's usually in LNKLST -- sometimes LPA. >Even if you would take the coblib out of the concatenation the "other" user procs would have to be updated and that is no small feat when you have 500++ programmers scattered across several times zones. It's a complete replacement set of PROCs. Also, our users do not have user compile PROCs, and if they run into problems we ensure that they are using the standard set. >We were just barely able to talk to the local progs. Politics. No management direction and procedures. It fails and it's user written. Tough! Because of the above, we got to ENTERPRISE COBOL 3.2 from MVS/COBOL 1.2.2 (if it had been a wine, it would have been vintage) with little fuss and two months time. - -teD I’m an enthusiastic proselytiser of the universal panacea I believe in! ---------------------------------------------------------------------- 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
