Implementation Differences Between Micro Focus COBOL and Enterprise COBOL

If you are moving your native Enterprise COBOL programs to a Micro Focus COBOL environment and building them for use with Java programs, these are the main differences that you need to be aware of when implementing Java interoperability, and any additional actions you may need to take to implement the interoperability in a Micro Focus COBOL environment:

	Enterprise COBOL	MF COBOL	Action
Calling static Java methods	Generates COBOL stub programs that then must be built to a shared library by an additional utility.	The Compiler generates and builds the necessary calling methods, using the JNI, under the covers. It does not require Java to be initiated first in order for COBOL to call into Java. Method overloading supported.	No managing or linking of additional stub programs required; simply compile to executable. See Example 1 - COBOL Calling Java Static Method
Java shareable and Java callable methods	The cjbuild utility is used to link and generate COBOL stub programs, the progs.java and strg.java programs, and also compiles the generated Java files.	The genjava utility generates the progs.java and strg.java programs. The javac command automatically compiles all the necessary generated Java files.	See The genjava Utility and the various build examples (Building and Running Native COBOL that Interoperates with Java)
Directives	JAVAIOP	A number of individual directives are used. Package name must be specified at compile time	See Language Features - Java Interoperability for a list of directives.

These are just the main fundamental differences, and you should use this documentation in conjunction with the IBM documentation for a full list of differences

Note: These differences reflect the current Micro Focus COBOL product against Enterprise COBOL 6.4.0.