Runtime Framework
Overview
Source code compiled with isCOBOL needs a Runtime Framework to run. The Runtime is the engine that runs the application. The Runtime Framework consists of a number of libraries that provide all the functionality required to run the application. There are two kinds of library: Java jar libraries and operating system native libraries.
This is the list of the Java jar libraries that compose the isCOBOL Runtime Framework:
Library | Description |
|---|
bcmail-jdk14-1.38.jar bcprov-jdk14-1.38.jar bctsp-jdk14-1.38.jar javassist.jar | isCOBOL Profiler dependences |
charva.jar | support for "green" terminals |
commons-codec-1.9.jar commons-collection4.4.1.jar mxlbeans-2.6.0.jar poi-3.17.jar poi-ooxml-3.17.jar poi-ooxml-schemas-3.17.jar | provide the ability to manage XLS and XLSX files. They’re required by the Grid control export features. |
commons-logging-api.jar | implementations of commons-logging wrapper APIs |
commons-logging.jar | implementatinos of commons-logging |
ctree-rtg.jar | ctreej interface |
DJNativeSwing-SWT.jar DJNativeSwing.jar swt-<platform>.<bits>.jar | default web-browser control implementation. |
iscobol.jar | isCOBOL Compiler, Framework, Debugger and Application Server |
isupdater.jar | isCOBOL Software Updater tool |
isprofiler.jar | isCOBOL Profiler |
itext-2.1.7v3.jar | allow to generate PDFs for print files assigned to "-P PDF" |
jcalendar-1.3.3.jar | date-entry control implementation |
jcommon-1.0.13.jar jfreechart-1.0.19.jar | allow to create charts via java-bean technology |
jdom.jar | allow the COBFILEIO, EfdParser and XML2WRK to parse XML files |
jna.jar jna-platform.jar | allow the C$SYSTEM routine to create a process on Windows. Required also by the default web-browser control implementation. |
joe-1.3.jar | allow to execute joe scripts |
utility.jar | isCOBOL internal utilities |
These libraries are installed in the isCOBOL lib folder on all platforms. All these libraries are portable to different platforms except for "swt-<platform>.<bits>.jar" that includes native items and therefore is different on every operating system.
This is the list of native libraries included in the isCOBOL Runtime Framework:
Library | Description |
|---|
ctree | allow to interact with a c-tree server |
dyncall | allows programs compiled without -cp option to call dynamic link libraries |
dyncall_n | allows programs compiled with -cp option to call dynamic link libraries |
iscobolc | allows programs compiled without -cp option to be called by C programs |
iscobolc_n | allows programs compiled with -cp option to be called by C programs |
Terminal | Curses implementation (native part) of Charva. Note - This library is not available on the Windows 64 bit platform. |
On Windows systems these libraries are installed in the isCOBOL bin folder and have dll extension (e.g. bin\dyncall.dll).
On Linux/Unix systems these libraries are installed in the isCOBOL native/lib folder, they have the lib prefix and so extension (e.g. native/lib/libdyncall.so).
On Mac OSX systems these libraries are installed in the isCOBOL native/lib folder, they have the lib prefix and jnilib extension (e.g. native/lib/libdyncall.jnilib).
A program compiled with isCOBOL can be executed with the following command:
Note - On Windows this command should be launched from inside the isCOBOL Shell. Otherwise you need to set ISCOBOL and ISCOBOL_JRE_ROOT environment variables before using iscrun.
This command is a wrapper which automatically adds all of the JAR files listed above to the class path before executing java and passing ProgramName to it. When running on Windows, the following command can be used in the same way to call javaw.exe:
Javaw.exe runs the program without displaying the command line console window.
When using isrun.exe, since standard output and standard error are not available in this case, the console output printed on two files called "isrun_out.log" and “isrun_err.log” in the bin directory of isCOBOL.
Paths in
Program-Name are considered only if
iscobol.code_prefix is set. Relative paths in
Program-Name are appended to the code-prefix paths.