Compiling and Building Differences

Output File Formats
Each project compiles into a single file (.dll, .so or .exe), or to multiple files of the same file type with one output file for each source file (.dll, .so, .exe, .int, or .gnt). As well as an .lbr file, which contains a collection of .int and .gnt files on Windows, you now can use a .dll as the container for application components.

Compiler directives
When you upgrade your source code to Enterprise Developer some Compiler directives that were specifically designed for 16-bit systems now produce an error on compilation because they are no longer relevant. You should remove them from your code and directives files before you compile.

Linking
The static run-time system and the single-threaded run-time system on Windows are no longer required and they are not shipped with Enterprise Developer. Applications built with Enterprise Developer are now linked to the shared or dynamic run-time systems. On UNIX, you can link to the single-threaded or multi-threaded shared or dynamic run-time system.

Called Programs and Dependencies
At run time, called programs are found in the same way as before. However, there are some new ways to set COBPATH and copy files into a common folder.

File Handler
The File Handler .obj files are not available in Enterprise Developer. Enterprise Developer uses the File handler packaged in the mffh.dll file instead.

Makefile Conversion
You cannot use existing makefiles from inside Enterprise Developer for Eclipse without changing some Eclipse defaults and adopting a modified build process. Where makefiles invoke commands supported by Enterprise Developer they will continue to work as before. Please contact Micro Focus for more information on using existing makefiles.

OpenESQL Assistant
The OpenESQL Assistant data source names (DSNs) in Enterprise Developer must be configured as ODBC or XDB DSNs.

SQL Compiler Directive Options
When you upgrade your to Enterprise Developer, some SQL applications could require additional SQL Compiler directive options to avoid compiler errors.

XML PARSE Statement
In Net Express, Server Express, the default setting for the XMLPARSE Compiler directive is COMPAT, which causes the XML PARSE statement to return information and events for IBM Enterprise COBOL Version 3. In Enterprise Developer, the default is XMLPARSE(XMLSS), which returns information and events for IBM Enterprise COBOL Version 4.