Question:

Currently, under ACUCOBOL, I open a disk file using a working storage variable name. That variable holds a generic name which can be found in the configuration file. That generic name translates into a spooler command (e.g. "PRINTERHP -P lp -s -oraw -dhplaser").
How does isCOBOL handle filename expansion, and can I keep my files defined as SELECT ... from DISK? Are there any other changes I need to make to my ACUCOBOL-GT programs to get the same print behavior?

Accessing printers on a Linux machine works the same in isCOBOL as it does in ACUCOBOL-GT. You won't need to make any changes to your code.

For filename expansion, you should set the following variable in your properties file:

   iscobol.file.env_naming=1

1. How do I set up isCOBOL to access Vision files?
2. What ACUCOBOL-GT library routines are supported?
3. How do I get my screens to be the same size and spacing as when I run with ACUCOBOL?
4. Is there a way to have single set of source code that will compile with both ACUCOBOL and isCOBOL?
5. Does isCOBOL have a utility to migrate Vision files to MS-SQL and PostgreSQL ?
6. What compile options should I use for a program written for Acucobol-GT?
7. What is the easiest way to convert the ACUCOBOL-GT configuration file?