Frequently Asked Questions for isCOBOL Evolve


products: isCOBOL Evolve COBOL development, Java deployment for simplified software distribution and enhanced innovation

Answers on key issues for customers considering isCOBOL Evolve as part of their application implementations:

The following is a list of Frequently Asked Questions. Click on a question to see a specific answer (click on the question again to close the answer). Click here to show all answers:

Executive Overview

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? [+]

Development Environment

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? [+]

Moving to isCOBOL Evolve

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? [+]

isCOBOL Evolve and Java Technology

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? [-]
isCOBOL Evolve is not an ‘either or’ proposition. Developers are not forced to choose between programming either in COBOL or in Java. The isCOBOL Compiler creates pure Java immediate source code and then calls the Java compiler which translates the code into pure Java bytecode as the output. The clean, efficient Java code output is still COBOL-like in nature and can be called as Java classes.

Going forward, most organizations would likely wrap their COBOL programs as objects. Thus, you would not need to look at the source in the long-term, but could instead create object-oriented interfaces to the code. With isCOBOL Evolve, the wrapping can be done in Object-Oriented COBOL or Java with the same results. The resulting objects are stored as bytecode in Java class files, and one cannot distinguish between objects wrapped one way or the other.

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? [+]

back

Additional Information
		isCOBOL Overview
		Features & Benefits
		FAQ
		Getting Started

	Opening up our application to Java has proven easy, fast and efficient with isCOBOL. We are now able to deliver powerful multi-platform user interfaces to our customers and have been extremely pleased by the talented, responsive team at Veryant.
	Mr. Ugo Pagnini, Chief and Owner, Sintecop spa

Join our Community Keep updated on the latest product news and information
		Sign up here

© Veryant - All Rights Reserved
Veryant and isCOBOL are trademarks or registered marks of Veryant in the United States and other countries. All other marks are the property of their respective owners.