I have a working Enterprise COBOL compiler exit written in XLC C++. It functions "correctly" but it is consuming more CPU time than expected, and I have this suspicion that it is going through LE initialization on each entry.
The COBOL doc says of exit modules "The Enterprise COBOL compiler automatically manages a preinitialized Language Environment at compile time, and calls compiler exits within this environment. Therefore, the following rules apply: Compiler exits are run as subprograms instead of main programs. Compiler exits must not include logic for explicitly initializing or terminating Language Environment." I have not done anything real special in the C++ code. My entry point is *not* a "main" function and is declared extern "OS" void. I am pre-binding and linking pretty much as I have done for other C++ programs. I tell the binder simply INCLUDE, ENTRY and NAME with no reference to CEESTART. Is there something "special" that I should be doing differently? Phrasing the question differently, if an LE program loads an LE program by module name and then calls it, how should that called program be compiled and bound so as to avoid repeated LE initialization? Thanks, Charles ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
