What is isCOBOL Evolve?  [+]

What are the benefits of an isCOBOL Evolve approach?  [+]

How compatible is isCOBOL Evolve with my current COBOL?  [+]

What platforms does isCOBOL Evolve support?  [+]

My company is concerned about the future of COBOL, how does isCOBOL Evolve alleviate that concern?  [-]
Besides the natural benefit of serving as another choice in the COBOL market, isCOBOL Evolve preserves valuable COBOL code while offering companies the advantage of the Java platform. With the ability to treat COBOL programs as Java classes, your COBOL programs can be utilized by other Java classes just as if they were originally native Java code. Until then, Java can serve as the platform while COBOL serves as the language. The only items required to execute the outputted Java code are the JVM and the iscobol.jar file that implements the original COBOL verbs.

The Java community is vibrant and diverse, and the isCOBOL Compiler is built on top of a Java compiler that is over 12 years old. By 2005, it was estimated that approximately 4.5 million developers used Java technology and that over 2.5 billion Java technology-enabled devices were available worldwide(1). Java technology has recently been made freely available under the GPL license and that has only further opened new development opportunities for software developers. These figures, combined with the broad reaching industry support for Java from corporations such as IBM, Sun, HP, BEA, Oracle, Google and others ensures the security of Java technology for decades to come.

(1)The Java History Timeline - http://www.Java.com/en/Javahistory/timeline.jsp

What impact does isCOBOL Evolve have on developers?  [+]

What options are there for debugging isCOBOL environments?  [+]

Is there an IDE available with isCOBOL Evolve?  [+]

What data access options exist with isCOBOL Evolve?  [+]

Can data sources be mixed and matched within an application?  [+]

What advantages are there to using the Embedded SQL compiler available with the isCOBOL environment?  [+]

How hard is it to move to isCOBOL Evolve?  [+]

My code is sprinkled throughout the programs for Thin Client. What might I expect for a migration path for isCOBOL Evolve in this area?  [+]

What user interface (UI) features are not supported by isCOBOL Evolve?  [+]

Suppose I find a data inefficiency and want to write a new version of ‘get data,’ is that possible?  [+]

How does isCOBOL Evolve run COBOL programs in a Java environment?  [+]

After moving to isCOBOL Evolve, what am I maintaining – COBOL or Java source code? Also, what happens to highly commented COBOL code?  [+]

I’ve heard of COBOL being wrapped or converted to Java before, but developers tell me it is just turned into spaghetti code. What is unique about isCOBOL Evolve?  [+]

What about performance in general? Are there any performance issues moving from COBOL to Java technology?  [+]

I’ve seen specific issues where Embedded SQL (ESQL) generated at the Java level needs to be tweaked in order to perform correctly. How does isCOBOL Evolve address this?  [+]

How does isCOBOL Evolve facilitate integration between COBOL and non-COBOL application environments and platforms?   [+]

What if I want to distribute my isCOBOL application out to several different devices with a variety of look and feel, connectivity and file system requirements?   [+]

Can I run standard syntax COBOL programs at the PDA/CDC level with isCOBOL Evolve?  [+]