Additional improvements
isCOBOL compiler can now be integrated in Apache Ant builds. Ant is a software tool for automating software build processes implemented using Java and is well integrated in software for automation servers like Jenkins. These automation servers help automate the parts of software development related to building, testing, and deploying. Products like Jenkins and Ant are often used together to facilitate continuous integration and continuous delivery (CI/CD).
An integrated system to use isCOBOL from Apache Ant is now available to simplify the usage of isCOBOL compiler in Ant build script.
To use isCOBOL inside Ant script you can now add the following tags to the build configuration file:
<taskdef name="iscc" classname="com.iscobol.ant.iscc"/> |
or use the syntax:
<project name="HelloWorld" default="build" basedir="." xmlns:veryant="antlib:com.iscobol.ant"> |
The task name “iscc” provides a task to allow compilation, using the syntax shown below:
<!-- Cobol sources --> <property name="src.dir" location="." /> <!-- Java classes --> <property name="build.dir" location="prg" /> ... <iscc javacOptions="-classpath ${iscobol-classpath-prop} " nosummary="false" nowarn="true" noerr="true" force="true" options="-sp=../isdef" failOnError="true" destDir="${build.dir}"> <fileset dir="${src.dir}"> <include name="**/*.cbl"/> </fileset> </iscc> |
Files with a .cbl extension in the current folder and its subfolders are compiled, and the .class will be generated in the “prg” destination folder.
These are the details of supported options in the iscc Ant task:
• javac=path to specify the external javac compiler to be used, default is none
• javacOptions=options to pass options to the java complier, default is none
• nosummary=false to suppress the display of compiler summary information, default is true
• nowarn=true to enable or disable compiler warnings, default is false
• noerr=true to enable or disable compiler errors, default is false
• force=true to force compilation a COBOL program even if it is not out of date, default is false
• options=options to set the isCOBOL compiler options used by the iscc command, default is -jc
• failOnError=false to continue the build process even if the compiler reports a severe error, default is true
• destDir=path to specify the name of the folder where the compiler output is to be written, default is none
• fileset=fileset to set the standard Ant fileset, defining a group of COBOL sources to be compiled. For details on the syntax see: https://ant.apache.org/manual/Types/fileset.html
Database Bridge
The EDBI routines generated by the Database Bridge functionality when targeting PostgreSQL are now certified for PostgreSQL release 12.
EIS improvements
A new overload method in HTTPHandler class has been added to allow setting the generation of a DummyRoot parameter:
HTTPHandler:>displayEx(content, hasDummyRoot) |
The DummyRoot is an automatically generated root element added during the creation of the XML or JSON representation of a working storage item, if needed.
isCOBOL utilities improvements
The isCOBOL Server Panel now supports the Threads View and Thread stack even when the Application Server is executed with a JRE.
The graphical ISMIGRATE wizard can now read isCOBOL configuration files when it starts. This allows you to preload settings to be used in the wizard by using the iscobol.ismigrate.* and other relevant properties in configuration files, and referencing the configuration file when starting the wizard. Previously, these variables could only be used when running ISMIGRATE from the command line.
ISMIGRATE has also been expanded to extend existing files. This feature can be enabled from the command line by setting the configuration property:
iscobol.ismigrate_open_extend=true |