First try a representative sample of your code. Select a unit of code which exhibits the typical program usage from your application. This is an excellent method for validating whether the application will compile without errors.

At development time, LegacyJ recommends splitting the project into several logical projects that can each compile separately. This method is used to better manage a large number of files.

One project can depend upon another project. This is done by right-clicking project, selecting properties, then in Java Build Path's use the Projects tab. Each such project must compile on its own, but it may CALL to another project on which it depends. Cobol compiler and runtime settings are available under properties as well.

Don't bring in all the .cbl files at once. Bring in just one at first, then larger groupings as you learn the system. When a Cobol file is imported, it is automatically compiled since the PERCobol IDE uses incremental compilation. All files remain in a valid state wherever possible.

Last updated on December 28, 2009 by Daniel Myers