Data access
• If the ACUCOBOL-GT application worked on databases using the Acu4GL interface, consider that the same feature can be obtained with isCOBOL by taking advantage of isCOBOL DatabaseBridge. The
-ca option should be used when launching the EDBI routine generator (edbiis).
• Veryant does not provide direct support on the Vision file system, but you’re allowed to convert your indexed files to a supported file system (JIsam or c-tree) easily with the
ISMIGRATE (Index File Migration) utility. Choose "com.iscobol.io.ScanVision" as input file handler to let ISMIGRATE read Vision files without the need of external components.
If you want to maintain Vision as file handler, Veryant can provide a special native library that is obtained by recompiling your ACUCOBOL-GT runtime. For the Linux/Unix platform a File Connector solution is also available.
See
The Vision File Connector for details about the File Connector solution. This solution is suggested unless you’re working on Windows, in that case contact Veryant for more information on the special native library.
Be aware that every solution has dependences to the ACUCOBOL-GT runtime libraries and needs a valid license in order to work.
• Fixed length sequential and relative files as well as variable length sequential files are compatible between ACUCOBOL-GT and isCOBOL assuming that you set the following variables in the configuration:
iscobol.file.linesequential=lseqacu iscobol.file.sequential=seqacu |
• Relative files with variable record length are not supported.
They must be converted to fixed length relative files by an ACUCOBOL-GT program that reads from the variable length file and writes to a fixed length file.
• By default, isCOBOL returns ANSI 2002 file status codes, while ACUCOBOL-GT returns ANSI 85 file status codes. You should set the
iscobol.file.status * property according with the following table:
value of FILE_STATUS_CODES in ACUCOBOL-GT configuration | value of iscobol.file.status in isCOBOL configuration |
|---|
not set | com.iscobol.io.FileStatus85 |
74 | com.iscobol.io.FileStatus74 |
85 | com.iscobol.io.FileStatus85 |
DG | com.iscobol.io.FileStatusDG |
VAX | com.iscobol.io.FileStatusVax |
IBM | com.iscobol.io.FileStatusIBM |
• Errors on DELETE FILE cannot be intercepted and handled by the COBOL program through Declaratives. Unless
iscobol.file.errors_ok is set to true, they cause the Framework to raise a Java exception.
• The file status "30" is returned when you you open a file whose path doesn't exist and when you try to create a file where there are no write permissions. ACUCOBOL-GT returns "35" and "37" respectively.
• The syntax “@server:filepath” in file names and file-prefix is not supported by isCOBOL. See
isCOBOL File Server for information about how to replace Acuserver with the isCOBOL File Server.