• Fixed-length sequential and relative files created by Micro Focus programs are directly usable by isCOBOL programs.

• To manage variable-length sequential files, add the following entry to the configuration:

• To manage line sequential files that might contain 0x0A in the record due to COMP fields, add the following entry to the configuration:

• Variable-length relative files must be converted to fixed-length relative files as isCOBOL doesn’t support variable-length relative files. This kind of conversion can be done through a Micro Focus program that reads from the variable-length file and writes to the fixed-length file using the maximum record size from the input file as the record size of the output file.

• Indexed MF files are not handled by isCOBOL. They can be easily converted to JIsam or c-tree by ISMIGRATE (Index File Migration) utility. Choose "com.iscobol.io.ScanMF" as input file handler to let ISMIGRATE read Micro Focus files without the need of external components.

• By default, isCOBOL returns ANSI 2002 file status codes. In order to have the same Micro Focus file status code, add the following setting to the configuration:

• The file status "30" is returned when you you try to create a file where there are no write permissions. Micro Focus returns "37" instead.

• If the Micro Focus application worked on databases using the Database Connector feature, consider that the same feature can be obtained with isCOBOL by taking advantage of isCOBOL Database Bridge. If you choose the EDBI Generation with EDBIIS (two steps), then the -ca option should be used when launching the EDBI routine generator (edbiis). If you choose EDBI Generation at compile time (one step), then you should gather all your FDs in a dummy program and compile only that program with -ca Compiler option, as compiling all programs of a Micro Focus application with -ca is not suggested.