How hard is it to move to isCOBOL Evolve? [-]When considering a move to isCOBOL, Veryant can take a sample of your code and generate a complimentary Code Analysis Report that will tell you exactly how compatible your application is before any investment occurs on your side.
In terms of data, if data resides in flat files or is supported by a database such as Oracle, there is no data migration involved. If data resides in an indexed file system it can be moved to Veryant JISAM, isCOBOL ISAM Server or another database. To migrate data to another file system or database, you write a simple isCOBOL program that reads all of the records from your current file system and writes them to the file system or database of your choice, or use the included ‘ISMIGRATE’ utility which does this for you.
If you want to access an RDBMS such as Oracle or MySQL you can use the Veryant Database Bridge to generate an isCOBOL file system interface implemented with embedded SQL in COBOL. To do this, you add “iscobol.file.index=easydb” and the JDBC related properties for the particular database you want to use to your iscobol.properties file. When you run, COBOL I/O operations will be routed through the Veryant Database Bridge-produced interface which talks to the RDBMS through the JDBC driver provided by the database vendor.
Here are a few of the considerations that will need to be kept in mind during a move to isCOBOL Evolve:
- If COBOL source code is compiled with a batch file, shell script or makefile, the compiler name will need to be adjusted to iscc.
- Some compiler options may need to be adapted or renamed to be supported in the isCOBOL environment.
- Numeric format will needed to be declared:
- -dci IBM numeric format
- -dcd Data General binary numeric format
- -dca ACUCOBOL-GT numeric format
- -dcm Micro Focus numeric format
Transition services are also available for companies who would like to supplement in-house staff during such a move. For additional details, contact info@veryant.com.
Contact
