Index
A
- Access data type mapping:
- 2.3.4 Access Data Type Compatibility
- ACUSQL_DATASET environment variable:
- ACUSQL_DATASET
- ACUSQL_INCLUDE environment variable:
- ACUSQL_INCLUDE
- ACUSQL_ORACLE environment variable:
- ACUSQL_ORACLE
- ACUSQL_PASSWORD environment variable:
- ACUSQL_PASSWORD
- ACUSQL_USER environment variable:
- ACUSQL_USER
- application execution:
- 4.1 Running Your Application
C
- CHAR, data type:
- 2.3.3 Oracle Data Type Compatibility
- 2.3.1 DB2 Data Type Compatibility
- 2.3.2 MSSQL Data Type Compatibility
- Connect Reset statement:
- 2.4.2 DISCONNECT Statement
- Connect statement:
- 2.4.1 CONNECT Statement
- current connection:
- 2.4.2 DISCONNECT Statement
D
- Data Division statements:
- 2.2 Data Division
- data types, matching SQL to COBOL:
- 2.3 Data Types
- Date, data type:
- 2.3.2 MSSQL Data Type Compatibility
- 2.3.1 DB2 Data Type Compatibility
- 2.3.3 Oracle Data Type Compatibility
- DB2 Connect:
- 1.3 Installation
- 1.2 Requirements
- 4.1 Running Your Application
- DB2 Connect: testing:
- 4.1 Running Your Application
- DB2:
- 1.4 Demonstration Programs
- 2.3.1 DB2 Data Type Compatibility
- 1.3 Installation
- 3.2.2 Invoking the Pre-compiler From the ACUCOBOL-GT Command Line
- 1.2 Requirements
- DB2: demonstration program:
- 1.4 Demonstration Programs
- DB2: host environments:
- 1.2 Requirements
- DB2: middleware:
- 1.2 Requirements
- 1.3 Installation
- DB2: reserved word list:
- 3.2.2 Invoking the Pre-compiler From the ACUCOBOL-GT Command Line
- DB2:data type mapping:
- 2.3.1 DB2 Data Type Compatibility
- debugging:
- 4.2 Debugging and File Tracing
- Decimal, data type:
- 2.3.2 MSSQL Data Type Compatibility
- 2.3.3 Oracle Data Type Compatibility
- 2.3.1 DB2 Data Type Compatibility
- demonstration programs:
- 1.4 Demonstration Programs
- directives, pre-compiler:
- 3.1 The ESQL Translation Process
- Disconnect statement:
- 2.4.2 DISCONNECT Statement
- Double, data type:
- 2.3.3 Oracle Data Type Compatibility
- 2.3.1 DB2 Data Type Compatibility
- 2.3.2 MSSQL Data Type Compatibility
E
- errors, pre-compiler:
- 3.4 Pre-compilation Errors
- ESQL translation:
- 3.1 The ESQL Translation Process
- EXEC SQL statement:
- 3.1 The ESQL Translation Process
F
- File Compiler Option dialog:
- 3.2.1 Using AcuSQL From Within AcuBench
- file tracing:
- 4.2 Debugging and File Tracing
H
- host-variables, in the Connect statement:
- 2.4.1 CONNECT Statement
- host-variables:
- 2.2 Data Division
- host-variables: defined:
- 2.2 Data Division
I
- IBM SQL:
- 2.1 Overview
- installation:
- 1.3.1 Installation Under Windows
- 1.3.2 Installation Under UNIX
- installation: UNIX:
- 1.3.2 Installation Under UNIX
- installation: Windows:
- 1.3.1 Installation Under Windows
- Integer, data type:
- 2.3.3 Oracle Data Type Compatibility
- 2.3.2 MSSQL Data Type Compatibility
- 2.3.1 DB2 Data Type Compatibility
- intermediate file:
- 3.1 The ESQL Translation Process
L
- large object data types (LOBs):
- 2.5 Limits and Restrictions
- 2.1 Overview
- Long Varchar, data type:
- 2.3.1 DB2 Data Type Compatibility
M
- MSSQL data type mapping:
- 2.3.2 MSSQL Data Type Compatibility
O
- ODBC API:
- 1.2 Requirements
- Oracle data type mapping:
- 2.3.3 Oracle Data Type Compatibility
P
- pre-compiler:
- 3.2 Using the Pre-compiler
- 3.2.1 Using AcuSQL From Within AcuBench
- 3.2.2 Invoking the Pre-compiler From the ACUCOBOL-GT Command Line
- 3.4 Pre-compilation Errors
- pre-compiler: errors:
- 3.4 Pre-compilation Errors
- pre-compiler: intermediate files:
- 3.2.1 Using AcuSQL From Within AcuBench
- pre-compiler: invocation:
- 3.2 Using the Pre-compiler
- pre-compiler: invoking from ACUCOBOL-GT:
- 3.2.2 Invoking the Pre-compiler From the ACUCOBOL-GT Command Line
- pre-compiler: options:
- 3.2.2 Invoking the Pre-compiler From the ACUCOBOL-GT Command Line
- pre-compiler: use in AcuBench:
- 3.2.1 Using AcuSQL From Within AcuBench
R
- Real, data type:
- 2.3.1 DB2 Data Type Compatibility
- 2.3.2 MSSQL Data Type Compatibility
- 2.3.3 Oracle Data Type Compatibility
- relaxed syntax checking:
- 3.2.2 Invoking the Pre-compiler From the ACUCOBOL-GT Command Line
- relinking:
- 1.3.2 Installation Under UNIX
- relinking:pre-compiler:
- 1.3.2 Installation Under UNIX
- relinking:runtime:
- 1.3.2 Installation Under UNIX
- reserved word list:
- 3.2.2 Invoking the Pre-compiler From the ACUCOBOL-GT Command Line
S
- source code preparation:
- 2.1 Overview
- SQL:
- 3.2.2 Invoking the Pre-compiler From the ACUCOBOL-GT Command Line
- 4.3 Error Messages
- SQL: error messages:
- 4.3 Error Messages
- SQL: relaxed syntax checking:
- 3.2.2 Invoking the Pre-compiler From the ACUCOBOL-GT Command Line
- SQLCA and SQLDA:
- 2.2 Data Division
- SQLCODE:
- 4.3 Error Messages
- SQLSTATE:
- 4.3 Error Messages
- syntax checking:
- 3.2.2 Invoking the Pre-compiler From the ACUCOBOL-GT Command Line
- 3.2 Using the Pre-compiler
- syntax checking:designated reserved word list:
- 3.2.2 Invoking the Pre-compiler From the ACUCOBOL-GT Command Line
- syntax checking:direct:
- 3.2.2 Invoking the Pre-compiler From the ACUCOBOL-GT Command Line
- 3.2 Using the Pre-compiler
- syntax checking:modes:
- 3.2 Using the Pre-compiler
- syntax checking:relaxed:
- 3.2.2 Invoking the Pre-compiler From the ACUCOBOL-GT Command Line
- 3.2 Using the Pre-compiler
- system requirements:
- 1.2 Requirements
T
- technical support:
- 1.5 Technical Support
- Time, data type:
- 2.3.1 DB2 Data Type Compatibility
- Timestamp, data type:
- 2.3.1 DB2 Data Type Compatibility
U
- UNIX:
- 1.3.2 Installation Under UNIX
- UNIX:installation:
- 1.3.2 Installation Under UNIX
V
- Varchar, data type:
- 2.3.2 MSSQL Data Type Compatibility
- 2.3.3 Oracle Data Type Compatibility
- 2.3.1 DB2 Data Type Compatibility