

Index


























- $, directive syntax:
- 4.2 Syntax
- 4GL_2000_CUTOFF variable:
- 4GL_2000_CUTOFF
- 4GL_8_DIGIT_CUTOFF variable:
- 4GL_8_DIGIT_CUTOFF
- 4GL_COLUMN_CASE variable:
- 4GL_COLUMN_CASE
- 4GL_CONVERT_DATES variable:
- 4GL_CONVERT_DATES
- 4GL_EXTRA_DB_COLS_OK variable:
- 4GL_EXTRA_DB_COLS_OK
- 4GL_IGNORED_SUFFIX_LIST variable:
- 4GL_IGNORED_SUFFIX_LIST
- 4GL_ILLEGAL_DATA variable:
- 4GL_ILLEGAL_DATA
- 5.1.2 Invalid Data Other Than Keys
- 4GL_JULIAN_BASE_DATE variable:
- 4GL_JULIAN_BASE_DATE
- 4.6 DATE Directive
A
- A_DBM_COMMIT_ON_BEGIN variable:
- A_DBM_COMMIT_ON_BEGIN
- A_DBM_DATABASE variable:
- A_DBM_DATABASE
- A_DBM_ERROR_MAP_FILE variable:
- A_DBM_ERROR_MAP_FILE
- A_DBM_LOCK_METHOD variable:
- A_DBM_LOCK_METHOD
- A_DBM_LOGIN variable:
- A_DBM_LOGIN
- A_DBM_NO_NULL_COLUMNS variable:
- A_DBM_NO_NULL_COLUMNS
- A_DBM_PASSWD variable:
- A_DBM_PASSWD
- A_DBM_QUOTE_IDENTIFIERS variable:
- A_DBM_QUOTE_IDENTIFIERS
- A_DBM_UNSIGNED_TINYINT variable:
- A_DBM_UNSIGNED_TINYINT
- A_DBM_USE_CHAR_FOR_BINARY variable:
- A_DBM_USE_CHAR_FOR_BINARY
- A_DBM_USE_SPACE_IN_DATES variable:
- A_DBM_USE_SPACE_IN_DATES
- A_INF_DUPLICATE_KEY variable:
- A_INF_DUPLICATE_KEY
- A_INF_NO_FINAL_TRANSACTION_ERROR variable:
- A_INF_NO_TRANSACTION_ERROR
- A_INFORMIX_ERROR_FILE variable:
- A_INFORMIX_ERROR_FILE
- A_MSSQL_ADD_IDENTITY variable:
- A_MSSQL_ADD_IDENTITY
- A_MSSQL_ADD_TIMESTAMP variable:
- A_MSSQL_ADD_TIMESTAMP
- A_MSSQL_CURSOR_OPTION variable:
- A_MSSQL_CURSOR_OPTION_1
A_MSSQL_CURSOR_OPTION_2
A_MSSQL_CURSOR_OPTION_3
- A_MSSQL_DATABASE variable:
- A_MSSQL_DATABASE
- A_MSSQL_DEFAULT_CONNECTION variable:
- A_MSSQL_DEFAULT_CONNECTION
- A_MSSQL_EXTRA_PROC variable:
- A_MSSQL_EXTRA_PROC
- A_MSSQL_FAST_ACCESS variable:
- A_MSSQL_FAST_ACCESS
- A_MSSQL_FORCED_INDEX variable:
- A_MSSQL_FORCED_INDEX
- A_MSSQL_LOCK_DB variable:
- A_MSSQL_LOCK_DB
- A_MSSQL_LOGIN variable:
- A_MSSQL_LOGIN
- A_MSSQL_MAX_CHARACTERS variable:
- A_MSSQL_MAX_CHARACTERS
- A_MSSQL_MAX_COLUMNS variable:
- A_MSSQL_MAX_COLUMNS
- A_MSSQL_NATIVE_LOCK_TIMEOUT variable:
- A_MSSQL_NATIVE_LOCK_TIMEOUT
- A_MSSQL_NO_23_ON_START variable:
- A_MSSQL_NO_23_ON_START
- A_MSSQL_NO_COUNT_CHECK variable:
- A_MSSQL_NO_COUNT_CHECK
- A_MSSQL_NO_DBCLOSE variable:
- A_MSSQL_NO_DBCLOSE
- A_MSSQL_NO_DBID variable:
- A_MSSQL_NO_DBID
- A_MSSQL_NO_RECORD_LOCKS variable:
- A_MSSQL_NO_RECORD_LOCKS
- A_MSSQL_NO_TABLE_LOCKS variable:
- A_MSSQL_NO_TABLE_LOCKS
- A_MSSQL_NT_AUTHENTICATION variable:
- A_MSSQL_NT_AUTHENTICATION
- A_MSSQL_PACKETSIZE variable:
- A_MSSQL_PACKETSIZE
- A_MSSQL_PASSWD variable:
- A_MSSQL_PASSWD
- A_MSSQL_ROWCOUNT variable:
- A_MSSQL_ROWCOUNT
- A_MSSQL_SELECT_KEY_ONLY variable:
- A_MSSQL_SELECT_KEY_ONLY
- A_MSSQL_SKIP_ALTERNATE_KEYS variable:
- A_MSSQL_SKIP_ALTERNATE_KEYS
- A_MSSQL_TRANSLATE_TO_ANSI variable:
- A_MSSQL_TRANSLATE_TO_ANSI
- A_MSSQL_UNLOCK_ON_EXECUTE variable:
- A_MSSQL_UNLOCK_ON_EXECUTE
- A_MSSQL_USE_DROPDOWN_QUERIES variable:
- A_MSSQL_USE_DROPDOWN_QUERIES
- A_MSSQL_VISION_LOCKS_FILE variable:
- A_MSSQL_VISION_LOCKS_FILE
- A_ODBC_COMMIT_ON_BEGIN variable:
- A_ODBC_COMMIT_ON_BEGIN
- A_ODBC_DATASOURCE variable:
- A_ODBC_DATASOURCE
- A_ODBC_ERROR_MAP_FILE variable:
- A_ODBC_ERROR_MAP_FILE
- A_ODBC_LOCK_METHOD variable:
- A_ODBC_LOCK_METHOD
- A_ODBC_LOGIN variable:
- A_ODBC_LOGIN
- A_ODBC_NO_NULL_COLUMNS variable:
- A_ODBC_NO_NULL_COLUMNS
- A_ODBC_PASSWD variable:
- A_ODBC_PASSWD
- A_ODBC_PRINT_LOG variable:
- A_ODBC_PRINT_LOG
- A_ODBC_QUOTE_IDENTIFIERS variable:
- A_ODBC_QUOTE_IDENTIFIERS
- A_ODBC_UNSIGNED_TINYINT variable:
- A_ODBC_UNSIGNED_TINYINT
- A_ODBC_USE_CHAR_FOR_BINARY variable:
- A_ODBC_USE_CHAR_FOR_BINARY
- A_ODBC_USE_SPACE_IN_DATES variable:
- A_ODBC_USE_SPACE_IN_DATES
- A_ORA_DEFER_CLOSE variable:
- A_ORA_DEFER_CLOSE
- A_ORA_DUPLICATE_KEY variable:
- A_ORA_DUPLICATE_KEY
- A_ORA_HINTS variable:
- A_ORA_HINTS
- A_ORACLE_ERROR_FILE variable:
- A_ORACLE_ERROR_FILE
- A_SYB_ADD_IDENTITY variable:
- A_SYB_ADD_IDENTITY
- A_SYB_ADD_TIMESTAMP variable:
- A_SYB_ADD_TIMESTAMP
- A_SYB_CURSOR_OPTION variables:
- A_SYB_CURSOR_OPTION_1
A_SYB_CURSOR_OPTION_2
A_SYB_CURSOR_OPTION_3
- A_SYB_DATABASE variable:
- A_SYB_DATABASE
- A_SYB_DEFAULT_CONNECTION variable:
- A_SYB_DEFAULT_CONNECTION
- A_SYB_EXTRA_PROC variable:
- A_SYB_EXTRA_PROC
- A_SYB_FAST_ACCESS variable:
- A_SYB_FAST_ACCESS
- A_SYB_FORCED_INDEX variable:
- A_SYB_FORCED_INDEX
- A_SYB_LOCK_DB variable:
- A_SYB_LOCK_DB
- A_SYB_LOGIN variable:
- A_SYB_LOGIN
- A_SYB_MAX_CHARACTERS variable:
- A_SYB_MAX_CHARACTERS
- A_SYB_MAX_COLUMNS variable:
- A_SYB_MAX_COLUMNS
- A_SYB_NATIVE_LOCK_TIMEOUT variable:
- A_SYB_NATIVE_LOCK_TIMEOUT
- A_SYB_NO_23_ON_START variable:
- A_SYB_NO_23_ON_START
- A_SYB_NO_COUNT_CHECK variable:
- A_SYB_NO_COUNT_CHECK
- A_SYB_NO_DBCLOSE variable:
- A_SYB_NO_DBCLOSE
- A_SYB_NO_DBID variable:
- A_SYB_NO_DBID
- A_SYB_NO_RECORD_LOCKS variable:
- A_SYB_NO_RECORD_LOCKS
- A_SYB_NO_TABLE_LOCKS variable:
- A_SYB_NO_TABLE_LOCKS
- A_SYB_PACKETSIZE variable:
- A_SYB_PACKETSIZE
- A_SYB_PASSWD variable:
- A_SYB_PASSWD
- A_SYB_ROWCOUNT variable:
- A_SYB_ROWCOUNT
- A_SYB_SELECT_KEY_ONLY variable:
- A_SYB_SELECT_KEY_ONLY
- A_SYB_SKIP_ALTERNATE_KEYS variable:
- A_SYB_SKIP_ALTERNATE_KEYS
- A_SYB_TRANSLATE_TO_ANSI variable:
- A_SYB_TRANSLATE_TO_ANSI
- A_SYB_UNLOCK_ON_EXECUTE variable:
- A_SYB_UNLOCK_ON_EXECUTE
- A_SYB_USE_DROPDOWN_QUERIES variable:
- A_SYB_USE_DROPDOWN_QUERIES
- A_SYB_VISION_LOCKS_FILE variable:
- A_SYB_VISION_LOCKS_FILE
- A4GL_COMMIT_COUNT variable:
- A4GL_COMMIT_COUNT
- A4GL_MAX_DATE variable:
- A4GL_MAX_DATE
- A4GL_MIN_DATE variable:
- A4GL_MIN_DATE
- accessing:data:
- 1.3 Accessing Data
- accessing:database:
- 1.5.3 Steps to Follow
- accounts, user:setting up for DBMaker:
- F.2.4 Acu4GL for DBMaker: Setting Up a User Account
- accounts, user:setting up for Microsoft SQL Server:
- B.2.3 Acu4GL for Microsoft SQL Server: Setting Up a User Account
- accounts, user:setting up for Oracle:
- C.2.5 Acu4GL for Oracle: Setting Up a User Account
- accounts, user:setting up for Sybase:
- E.4.1 Acu4GL for Sybase: Setting Up a User Account
- Acu4GL cursor, Oracle:
- C.2.4 Acu4GL for Oracle: Checking System Parameters
- Acu4GL, DBMaker:
- F.2 Acu4GL for DBMaker Installation and Setup for Windows and UNIX
- F.2.6 Acu4GL for DBMaker: Designating the Host Database
- F.6.3 Acu4GL for DBMaker: Native SQL Errors
- F.1 DBMaker Concepts Overview
- F.1.1 What Is DBMaker?
- F.5.3 Acu4GL for DBMaker: Data Type Mapping
- F.6.1 Acu4GL for DBMaker: Runtime Errors
- F.6.2 Acu4GL for DBMaker: Retrieving Errors
- F.2.3 UNIX Installation Steps for the Acu4GL for DBMaker Product
- F.7 Acu4GL for DBMaker: Common Questions and Answers
- F.6 Acu4GL for DBMaker: Troubleshooting
- F.1.2 DBMaker Structure
- F.3 Acu4GL for DBMaker and Filename Translation
- F.4 Acu4GL for DBMaker Configuration File Variables
- A_DBM_ERROR_MAP_FILE
- F.5 Acu4GL for DBMaker: Technical Information
- F.5.1 Acu4GL for DBMaker: Record and Table Locking
- F.5.2 Acu4GL for DBMaker: Limits and Ranges
- Acu4GL, DBMaker:binary large objects:
- F.1.1 What Is DBMaker?
- Acu4GL, DBMaker:client library:
- F.1.2 DBMaker Structure
- Acu4GL, DBMaker:client program:
- F.1.2 DBMaker Structure
- Acu4GL, DBMaker:communications:
- F.1.2 DBMaker Structure
- Acu4GL, DBMaker:configuration variables:
- F.4 Acu4GL for DBMaker Configuration File Variables
- Acu4GL, DBMaker:creating map files:
- A_DBM_ERROR_MAP_FILE
- Acu4GL, DBMaker:data types:
- F.5.3 Acu4GL for DBMaker: Data Type Mapping
- Acu4GL, DBMaker:designating the host database:
- F.2.6 Acu4GL for DBMaker: Designating the Host Database
- Acu4GL, DBMaker:FAQs:
- F.7 Acu4GL for DBMaker: Common Questions and Answers
- Acu4GL, DBMaker:filename interpretation:
- F.3 Acu4GL for DBMaker and Filename Translation
- Acu4GL, DBMaker:installation and setup:
- F.2 Acu4GL for DBMaker Installation and Setup for Windows and UNIX
- Acu4GL, DBMaker:limits and ranges:
- F.5.2 Acu4GL for DBMaker: Limits and Ranges
- Acu4GL, DBMaker:makefiles:
- F.2.3 UNIX Installation Steps for the Acu4GL for DBMaker Product
- Acu4GL, DBMaker:mapping COBOL data to DBMaker data:
- F.5.3 Acu4GL for DBMaker: Data Type Mapping
- Acu4GL, DBMaker:mapping data to COBOL:
- F.5.3 Acu4GL for DBMaker: Data Type Mapping
- Acu4GL, DBMaker:overview:
- F.1 DBMaker Concepts Overview
- Acu4GL, DBMaker:record and table locking:
- F.5.1 Acu4GL for DBMaker: Record and Table Locking
- Acu4GL, DBMaker:retrieving errors:
- F.6.2 Acu4GL for DBMaker: Retrieving Errors
- Acu4GL, DBMaker:runtime errors:
- F.6.1 Acu4GL for DBMaker: Runtime Errors
- Acu4GL, DBMaker:server program:
- F.1.2 DBMaker Structure
- Acu4GL, DBMaker:SQL errors:
- F.6.3 Acu4GL for DBMaker: Native SQL Errors
- Acu4GL, DBMaker:structure:
- F.1.2 DBMaker Structure
- Acu4GL, DBMaker:technical specifications:
- F.5 Acu4GL for DBMaker: Technical Information
- Acu4GL, DBMaker:troubleshooting:
- F.6 Acu4GL for DBMaker: Troubleshooting
- Acu4GL, Informix:
- A.3 Acu4GL for Informix Configuration File Variables
- A.5.1 Acu4GL for Informix: Supported Features
- A.1.1 Installation of the Acu4GL for Informix Product
- A.1.3 Acu4GL for Informix: Designating a Database
- A.1 Getting Started with Acu4GL for Informix
- A.5.2 Acu4GL for Informix: Limits and Ranges
- A.4 Informix 7.2 and 7.3 Performance
- A.6 Acu4GL for Informix: Troubleshooting
- A.5 Acu4GL for Informix: Technical Information
- A.6.1 Acu4GL for Informix: Runtime Errors
- A.2 Acu4GL for Informix and Filename Translation
- A.6.2 Acu4GL for Informix: Retrieving Errors
- A.1.2 Installing the Acu4GL for Informix Product
- A.7 Acu4GL for Informix: Common Questions and Answers
- Acu4GL, Informix:7.2 and 7.3 performance:
- A.4 Informix 7.2 and 7.3 Performance
- A.7 Acu4GL for Informix: Common Questions and Answers
- Acu4GL, Informix:and ANSI-mode databases:
- A.1 Getting Started with Acu4GL for Informix
- Acu4GL, Informix:compiling the sample program:
- A.1.2 Installing the Acu4GL for Informix Product
- Acu4GL, Informix:configuration variables:
- A.3 Acu4GL for Informix Configuration File Variables
- Acu4GL, Informix:creating a makefile:
- A.1.2 Installing the Acu4GL for Informix Product
- Acu4GL, Informix:creating a new runtime:
- A.1.2 Installing the Acu4GL for Informix Product
- Acu4GL, Informix:designating a database:
- A.1.3 Acu4GL for Informix: Designating a Database
- Acu4GL, Informix:FAQs:
- A.7 Acu4GL for Informix: Common Questions and Answers
- Acu4GL, Informix:features:
- A.5.1 Acu4GL for Informix: Supported Features
- Acu4GL, Informix:filename interpretation:
- A.2 Acu4GL for Informix and Filename Translation
- Acu4GL, Informix:getting started:
- A.1 Getting Started with Acu4GL for Informix
- Acu4GL, Informix:installation:
- A.1.1 Installation of the Acu4GL for Informix Product
- Acu4GL, Informix:libraries, shared:
- A.1.2 Installing the Acu4GL for Informix Product
- Acu4GL, Informix:limits:
- A.5.2 Acu4GL for Informix: Limits and Ranges
- Acu4GL, Informix:linking the runtime:
- A.1.2 Installing the Acu4GL for Informix Product
- Acu4GL, Informix:query optimizer:
- A.7 Acu4GL for Informix: Common Questions and Answers
- A.4 Informix 7.2 and 7.3 Performance
- Acu4GL, Informix:retrieving errors:
- A.6.2 Acu4GL for Informix: Retrieving Errors
- Acu4GL, Informix:runtime errors:
- A.6.1 Acu4GL for Informix: Runtime Errors
- Acu4GL, Informix:switching file systems:
- A.5 Acu4GL for Informix: Technical Information
- Acu4GL, Informix:technical specifications:
- A.5 Acu4GL for Informix: Technical Information
- Acu4GL, Informix:troubleshooting:
- A.6 Acu4GL for Informix: Troubleshooting
- Acu4GL, Informix:unsupported data types:
- A.5.2 Acu4GL for Informix: Limits and Ranges
- Acu4GL, Microsoft SQL Server:
- B.2.5 Acu4GL for Microsoft SQL Server: Designating the Host File System
- B.8 Acu4GL for Microsoft SQL Server: Common Questions and Answers
- B.7.1 Acu4GL for Microsoft SQL Server: Runtime Errors
- B.7.2 Acu4GL for Microsoft SQL Server: Retrieving Errors
- B.2.3 Acu4GL for Microsoft SQL Server: Setting Up a User Account
- B.1 Microsoft SQL Server Concepts Overview
- B.6 Acu4GL for Microsoft SQL Server: Technical Information
- B.2.2 Installing the Acu4GL for Microsoft SQL Server Product on a Client Machine
- B.7 Acu4GL for Microsoft SQL Server: Troubleshooting
- B.4 Acu4GL for Microsoft SQL Server Configuration File Variables
- B.5 Acu4GL for Microsoft SQL Server: Using the Database Table
- B.6.1 Acu4GL for Microsoft SQL Server: Table Locking
- B.6.3 Acu4GL for Microsoft SQL Server: Limits and Ranges
- B.2 Getting Started with Acu4GL for Microsoft SQL Server
- B.2.4 Acu4GL for Microsoft SQL Server: Setting Up the User Environment
- B.2.1 Acu4GL for Microsoft SQL Server Installation and Setup
- B.3 Acu4GL for Microsoft SQL Server and Filename Translation
- Acu4GL, Microsoft SQL Server:alternate REWRITE method:
- B.1 Microsoft SQL Server Concepts Overview
- Acu4GL, Microsoft SQL Server:configuration variables:
- B.4 Acu4GL for Microsoft SQL Server Configuration File Variables
- Acu4GL, Microsoft SQL Server:database table:
- B.5 Acu4GL for Microsoft SQL Server: Using the Database Table
- Acu4GL, Microsoft SQL Server:designating the host file system:
- B.2.5 Acu4GL for Microsoft SQL Server: Designating the Host File System
- Acu4GL, Microsoft SQL Server:FAQs:
- B.8 Acu4GL for Microsoft SQL Server: Common Questions and Answers
- Acu4GL, Microsoft SQL Server:filename interpretation:
- B.3 Acu4GL for Microsoft SQL Server and Filename Translation
- Acu4GL, Microsoft SQL Server:getting started:
- B.2 Getting Started with Acu4GL for Microsoft SQL Server
- Acu4GL, Microsoft SQL Server:installation on client:
- B.2.2 Installing the Acu4GL for Microsoft SQL Server Product on a Client Machine
- Acu4GL, Microsoft SQL Server:installation on NT server:
- B.2.2 Installing the Acu4GL for Microsoft SQL Server Product on a Client Machine
- Acu4GL, Microsoft SQL Server:installation:
- B.2.1 Acu4GL for Microsoft SQL Server Installation and Setup
- Acu4GL, Microsoft SQL Server:Microsoft SQL Server limits:
- B.6.3 Acu4GL for Microsoft SQL Server: Limits and Ranges
- Acu4GL, Microsoft SQL Server:Microsoft SQL Server ranges:
- B.6.3 Acu4GL for Microsoft SQL Server: Limits and Ranges
- Acu4GL, Microsoft SQL Server:overview:
- B.1 Microsoft SQL Server Concepts Overview
- Acu4GL, Microsoft SQL Server:retrieving errors:
- B.7.2 Acu4GL for Microsoft SQL Server: Retrieving Errors
- Acu4GL, Microsoft SQL Server:runtime errors:
- B.7.1 Acu4GL for Microsoft SQL Server: Runtime Errors
- Acu4GL, Microsoft SQL Server:security:
- B.1 Microsoft SQL Server Concepts Overview
- Acu4GL, Microsoft SQL Server:servers:
- B.1 Microsoft SQL Server Concepts Overview
- Acu4GL, Microsoft SQL Server:setting up a user account:
- B.2.3 Acu4GL for Microsoft SQL Server: Setting Up a User Account
- Acu4GL, Microsoft SQL Server:setting up the user environment:
- B.2.4 Acu4GL for Microsoft SQL Server: Setting Up the User Environment
- Acu4GL, Microsoft SQL Server:table locking:
- B.6.1 Acu4GL for Microsoft SQL Server: Table Locking
- Acu4GL, Microsoft SQL Server:table ownership:
- B.1 Microsoft SQL Server Concepts Overview
- Acu4GL, Microsoft SQL Server:technical specifications:
- B.6 Acu4GL for Microsoft SQL Server: Technical Information
- Acu4GL, Microsoft SQL Server:troubleshooting:
- B.7 Acu4GL for Microsoft SQL Server: Troubleshooting
- Acu4GL, ODBC:
- D.1.2 Origins of ODBC
- D.1.3 Restrictions
- A_ODBC_ERROR_MAP_FILE
- D.5 Acu4GL for ODBC: Technical Information
- D.5.1 Acu4GL for ODBC: Record and Table Locking
- D.5.2 Acu4GL for ODBC: Limits and Ranges
- D.5.3 Acu4GL for ODBC: Driver Requirements
- D.5.4 Acu4GL for ODBC: Data Type Mapping
- D.6 Acu4GL for ODBC: Troubleshooting
- D.6.1 Acu4GL for ODBC: Runtime Errors
- D.6.2 Acu4GL for ODBC: Retrieving Errors
- D.6.3 Acu4GL for ODBC: Native SQL Errors
- D.7 Acu4GL for ODBC: Common Questions and Answers
- D.1.4 ODBC Structure
- D.2 Acu4GL for ODBC Installation and Setup
- D.2.1 Installation
- D.2.3 Acu4GL for ODBC: Setting Up Data Sources
- D.2.5 Acu4GL for ODBC: Designating the Host File System
- D.2.6 Acu4GL for ODBC: Designating the Host Data Source
- D.3 Acu4GL for ODBC and Filename Translation
- D.4 Acu4GL for ODBC Configuration File Variables
- D.1 ODBC Concepts
- Acu4GL, ODBC:application:
- D.1.4 ODBC Structure
- Acu4GL, ODBC:configuration variables:
- D.4 Acu4GL for ODBC Configuration File Variables
- Acu4GL, ODBC:creating map files:
- A_ODBC_ERROR_MAP_FILE
- Acu4GL, ODBC:data sources:
- D.2.3 Acu4GL for ODBC: Setting Up Data Sources
- D.1.4 ODBC Structure
- Acu4GL, ODBC:data types:
- D.5.4 Acu4GL for ODBC: Data Type Mapping
- Acu4GL, ODBC:designating the host data source:
- D.2.6 Acu4GL for ODBC: Designating the Host Data Source
- Acu4GL, ODBC:designating the host file system:
- D.2.5 Acu4GL for ODBC: Designating the Host File System
- Acu4GL, ODBC:Driver Manager:
- D.1.4 ODBC Structure
- Acu4GL, ODBC:driver requirements:
- D.5.3 Acu4GL for ODBC: Driver Requirements
- Acu4GL, ODBC:driver test:
- D.5.3 Acu4GL for ODBC: Driver Requirements
- Acu4GL, ODBC:drivers:
- D.1.4 ODBC Structure
- Acu4GL, ODBC:FAQs:
- D.7 Acu4GL for ODBC: Common Questions and Answers
- Acu4GL, ODBC:filename interpretation:
- D.3 Acu4GL for ODBC and Filename Translation
- Acu4GL, ODBC:getting started:
- D.2 Acu4GL for ODBC Installation and Setup
- Acu4GL, ODBC:installation and setup:
- D.2.1 Installation
- Acu4GL, ODBC:limits and ranges:
- D.5.2 Acu4GL for ODBC: Limits and Ranges
- Acu4GL, ODBC:mapping COBOL data to ODBC data:
- D.5.4 Acu4GL for ODBC: Data Type Mapping
- Acu4GL, ODBC:mapping ODBC data to COBOL data:
- D.5.4 Acu4GL for ODBC: Data Type Mapping
- Acu4GL, ODBC:origins of ODBC:
- D.1.2 Origins of ODBC
- Acu4GL, ODBC:overview:
- D.1 ODBC Concepts
- Acu4GL, ODBC:record and table locking:
- D.5.1 Acu4GL for ODBC: Record and Table Locking
- Acu4GL, ODBC:restrictions:
- D.1.3 Restrictions
- Acu4GL, ODBC:retrieving errors:
- D.6.2 Acu4GL for ODBC: Retrieving Errors
- Acu4GL, ODBC:runtime errors:
- D.6.1 Acu4GL for ODBC: Runtime Errors
- Acu4GL, ODBC:SQL errors:
- D.6.3 Acu4GL for ODBC: Native SQL Errors
- Acu4GL, ODBC:structure:
- D.1.4 ODBC Structure
- Acu4GL, ODBC:technical specifications:
- D.5 Acu4GL for ODBC: Technical Information
- Acu4GL, ODBC:troubleshooting:
- D.6 Acu4GL for ODBC: Troubleshooting
- Acu4GL, Oracle:
- C.7 Acu4GL for Oracle: Troubleshooting
- C.2.4 Acu4GL for Oracle: Checking System Parameters
- C.6.2 Acu4GL for Oracle: Limits and Ranges
- C.7.2 Acu4GL for Oracle: Retrieving Errors
- C.2.5 Acu4GL for Oracle: Setting Up a User Account
- C.7.1 Acu4GL for Oracle: Runtime Errors
- C.6 Acu4GL for Oracle: Technical Information
- C.2.2 UNIX Installation Steps for the Oracle Acu4GL Product
- C.2.3 Installing the Product
- C.8 Acu4GL for Oracle: Common Questions and Answers
- C.6.1 Acu4GL for Oracle: Supported Features
- C.1 Oracle Concepts Overview
- C.2 Acu4GL for Oracle Installation and Setup
- C.2.1 Windows Installation Steps for the Acu4GL for Oracle Product
- C.2.6 Acu4GL for Oracle: Setting Up the User Environment
- C.2.7 Acu4GL for Oracle: Designating the Host File System
- C.2.8 Acu4GL for Oracle: Setting Up the Search Path
- C.2.9 Acu4GL for Oracle: Handling Transactions
- C.3 Acu4GL for Oracle and Filename Translation
- C.5 Acu4GL for Oracle: Using the Database Table
- Acu4GL, Oracle:automatic login:
- C.2.5 Acu4GL for Oracle: Setting Up a User Account
- Acu4GL, Oracle:checking system parameters:
- C.2.4 Acu4GL for Oracle: Checking System Parameters
- Acu4GL, Oracle:configured login:
- C.2.5 Acu4GL for Oracle: Setting Up a User Account
- Acu4GL, Oracle:creating a new runtime:
- C.2.3 Installing the Product
- Acu4GL, Oracle:cursors:
- C.2.4 Acu4GL for Oracle: Checking System Parameters
- Acu4GL, Oracle:database table:
- C.5 Acu4GL for Oracle: Using the Database Table
- Acu4GL, Oracle:designating host file system:
- C.2.7 Acu4GL for Oracle: Designating the Host File System
- Acu4GL, Oracle:FAQs:
- C.8 Acu4GL for Oracle: Common Questions and Answers
- Acu4GL, Oracle:features:
- C.6.1 Acu4GL for Oracle: Supported Features
- Acu4GL, Oracle:filename interpretation:
- C.3 Acu4GL for Oracle and Filename Translation
- Acu4GL, Oracle:getting started:
- C.2 Acu4GL for Oracle Installation and Setup
- Acu4GL, Oracle:installation for UNIX:
- C.2.2 UNIX Installation Steps for the Oracle Acu4GL Product
- Acu4GL, Oracle:installation for Windows:
- C.2.1 Windows Installation Steps for the Acu4GL for Oracle Product
- Acu4GL, Oracle:libraries, shared:
- C.2.3 Installing the Product
- Acu4GL, Oracle:linking the runtime:
- C.2.3 Installing the Product
- Acu4GL, Oracle:linking:
- C.2.1 Windows Installation Steps for the Acu4GL for Oracle Product
- Acu4GL, Oracle:makefiles:
- C.2.3 Installing the Product
- Acu4GL, Oracle:open_cursors:
- C.1 Oracle Concepts Overview
- Acu4GL, Oracle:Oracle file system limits:
- C.6.2 Acu4GL for Oracle: Limits and Ranges
- Acu4GL, Oracle:record locking:
- C.1 Oracle Concepts Overview
- Acu4GL, Oracle:retrieving errors:
- C.7.2 Acu4GL for Oracle: Retrieving Errors
- Acu4GL, Oracle:runtime errors:
- C.7.1 Acu4GL for Oracle: Runtime Errors
- Acu4GL, Oracle:security:
- C.1 Oracle Concepts Overview
- Acu4GL, Oracle:setting up the search path:
- C.2.8 Acu4GL for Oracle: Setting Up the Search Path
- Acu4GL, Oracle:setting up the user environment:
- C.2.6 Acu4GL for Oracle: Setting Up the User Environment
- Acu4GL, Oracle:setting up user accounts:
- C.2.5 Acu4GL for Oracle: Setting Up a User Account
- Acu4GL, Oracle:table ownership:
- C.1 Oracle Concepts Overview
- Acu4GL, Oracle:technical specifications:
- C.6 Acu4GL for Oracle: Technical Information
- Acu4GL, Oracle:transactions:
- C.1 Oracle Concepts Overview
- C.2.9 Acu4GL for Oracle: Handling Transactions
- C.6.1 Acu4GL for Oracle: Supported Features
- Acu4GL, Oracle:troubleshooting:
- C.7 Acu4GL for Oracle: Troubleshooting
- Acu4GL, Sybase:
- E.9 Acu4GL for Sybase: Common Questions and Answers
- E.7.2 Acu4GL for Sybase: Stored Procedures
- E.7.3 Acu4GL for Sybase: Limits and Ranges
- E.8 Acu4GL for Sybase: Troubleshooting
- E.8.1 Acu4GL for Sybase: Runtime Errors
- E.5 Acu4GL for Sybase and Filename Translation
- E.8.2 Acu4GL for Sybase: Retrieving Errors
- E.4.3 Acu4GL for Sybase: Designating the Host File System
- E.2 Getting Started with Acu4GL for Sybase
- E.6 Acu4GL for Sybase Configuration File Variables
- E.2.1 Sybase RDBMS Installation
- E.1 Sybase Concepts Overview
- E.3.2 Installation Steps on the UNIX Client
- E.3.3 Installation Steps on the UNIX or Windows NT Server
- E.7 Acu4GL for Sybase: Technical Information
- E.3.5 Installation Steps on the UNIX Server Machine
- E.3.6 Installation Steps on a Windows NT Server Machine - Windows Client
- E.4.1 Acu4GL for Sybase: Setting Up a User Account
- E.7.1 Acu4GL for Sybase: Record and Table Locking
- E.4.2 Acu4GL for Sybase: Setting Up the User Environment
- Acu4GL, Sybase:configuration variables:
- E.6 Acu4GL for Sybase Configuration File Variables
- Acu4GL, Sybase:creating a new runtime:
- E.3.2 Installation Steps on the UNIX Client
- Acu4GL, Sybase:creating stored procedures:
- E.3.5 Installation Steps on the UNIX Server Machine
- Acu4GL, Sybase:designating the host file system:
- E.4.3 Acu4GL for Sybase: Designating the Host File System
- Acu4GL, Sybase:FAQs:
- E.9 Acu4GL for Sybase: Common Questions and Answers
- Acu4GL, Sybase:filename interpretation:
- E.5 Acu4GL for Sybase and Filename Translation
- Acu4GL, Sybase:getting started:
- E.2 Getting Started with Acu4GL for Sybase
- Acu4GL, Sybase:installation and setup:
- E.2.1 Sybase RDBMS Installation
- Acu4GL, Sybase:installing stored procedures:
- E.3.5 Installation Steps on the UNIX Server Machine
- E.3.6 Installation Steps on a Windows NT Server Machine - Windows Client
- Acu4GL, Sybase:libraries, shared:
- E.3.2 Installation Steps on the UNIX Client
- Acu4GL, Sybase:linking the runtime:
- E.3.2 Installation Steps on the UNIX Client
- Acu4GL, Sybase:makefiles:
- E.3.2 Installation Steps on the UNIX Client
- Acu4GL, Sybase:overview:
- E.1 Sybase Concepts Overview
- Acu4GL, Sybase:retrieving errors:
- E.8.2 Acu4GL for Sybase: Retrieving Errors
- Acu4GL, Sybase:REWRITE method:
- E.1 Sybase Concepts Overview
- Acu4GL, Sybase:runtime errors:
- E.8.1 Acu4GL for Sybase: Runtime Errors
- Acu4GL, Sybase:security:
- E.1 Sybase Concepts Overview
- Acu4GL, Sybase:servers:
- E.1 Sybase Concepts Overview
- Acu4GL, Sybase:setting up a user account:
- E.4.1 Acu4GL for Sybase: Setting Up a User Account
- Acu4GL, Sybase:setting up the user environment:
- E.4.2 Acu4GL for Sybase: Setting Up the User Environment
- Acu4GL, Sybase:stored procedures:
- E.7.2 Acu4GL for Sybase: Stored Procedures
- Acu4GL, Sybase:Sybase limits:
- E.7.3 Acu4GL for Sybase: Limits and Ranges
- Acu4GL, Sybase:Sybase ranges:
- E.7.3 Acu4GL for Sybase: Limits and Ranges
- Acu4GL, Sybase:table locking:
- E.7.1 Acu4GL for Sybase: Record and Table Locking
- Acu4GL, Sybase:table ownership:
- E.1 Sybase Concepts Overview
- Acu4GL, Sybase:technical specifications:
- E.7 Acu4GL for Sybase: Technical Information
- Acu4GL, Sybase:troubleshooting:
- E.8 Acu4GL for Sybase: Troubleshooting
- Acu4GL, Sybase:upgrading stored procedures:
- E.3.6 Installation Steps on a Windows NT Server Machine - Windows Client
- E.3.5 Installation Steps on the UNIX Server Machine
- E.3.3 Installation Steps on the UNIX or Windows NT Server
- Acu4GL:
- 1.3.2 Data Dictionaries and Acu4GL
- 7.3.3 Field Names
- 1.5 How Acu4GL Works
- 7.2 Default Behavior
- 1.5.4 Summary
- 3.1 Data Dictionaries or XFDs
- 1.1 Welcome to Acu4GL
- 1.3.3 The ACUCOBOL-GT Plug-in and Acu4GL
- 1.4 Database Concepts
- 1.5.2 Data Dictionaries and Mapping
- 2.1 Getting Started
- C.1 Oracle Concepts Overview
- 7.3.1 How Do I Match Existing Text Fields?
- 7.3.2 How Do I Match Existing Numeric Fields?
- Acu4GL:ACUCOBOL-GT plug-in:
- 1.3.3 The ACUCOBOL-GT Plug-in and Acu4GL
- Acu4GL:case conversion in data:
- 7.2 Default Behavior
- Acu4GL:data dictionaries:
- 1.5.2 Data Dictionaries and Mapping
- 3.1 Data Dictionaries or XFDs
- 1.3.2 Data Dictionaries and Acu4GL
- Acu4GL:data format conversions:
- 7.2 Default Behavior
- Acu4GL:data sequencing:
- 7.2 Default Behavior
- Acu4GL:database compatibility:
- 1.1 Welcome to Acu4GL
- Acu4GL:database concepts:
- 1.4 Database Concepts
- Acu4GL:default behavior:
- 7.2 Default Behavior
- Acu4GL:field names:
- 7.3.3 Field Names
- Acu4GL:getting started:
- 2.1 Getting Started
- Acu4GL:how it works:
- 1.5 How Acu4GL Works
- Acu4GL:introduction:
- 1.1 Welcome to Acu4GL
- Acu4GL:matching COBOL fields to database fields:
- 7.2 Default Behavior
- Acu4GL:matching numeric fields to database fields:
- 7.3.2 How Do I Match Existing Numeric Fields?
- Acu4GL:matching text fields to database fields:
- 7.3.1 How Do I Match Existing Text Fields?
- Acu4GL:overview:
- 1.1 Welcome to Acu4GL
- Acu4GL:record locking:
- C.1 Oracle Concepts Overview
- Acu4GL:summary:
- 1.5.4 Summary
- ACUCOBOL-GT:
- 1.5 How Acu4GL Works
- 1.3.3 The ACUCOBOL-GT Plug-in and Acu4GL
- ACUCOBOL-GT:plug-in and Acu4GL:
- 1.3.3 The ACUCOBOL-GT Plug-in and Acu4GL
- ACUCOBOL-GT:runtime module:
- 1.5 How Acu4GL Works
- Acucorp, contacting:
- 2.2 Technical Support
- alfred, indexed file editor:
- 1.3.2 Data Dictionaries and Acu4GL
- 3.1 Data Dictionaries or XFDs
- Alpha directive:
- 4.3 ALPHA Directive
- alternate REWRITE method, Microsoft SQL Server:
- B.1 Microsoft SQL Server Concepts Overview
- ANSI-compliant directive:
- 4.2 Syntax
- ANSI-mode databases and Acu4GL for Informix:
- A.1 Getting Started with Acu4GL for Informix
- application, ODBC:
- D.1.4 ODBC Structure
- architecture, DBMaker:client/server:
- F.1.2 DBMaker Structure
- architecture, DBMaker:multiple-tier:
- F.1.3 DBMaker and Acu4GL Architecture
- architecture, DBMaker:single-tier:
- F.1.3 DBMaker and Acu4GL Architecture
- architecture, DBMaker:single-user:
- F.1.2 DBMaker Structure
- architecture, ODBC:
- D.1.4 ODBC Structure
- ASSIGN name, XFD:
- 3.2.6 Naming the XFD
- automatic login, Oracle:
- C.2.5 Acu4GL for Oracle: Setting Up a User Account
B
- BINARY directive:
- 4.4 BINARY Directive
- binary large objects, DBMaker:
- F.1.1 What Is DBMaker?
- BINARY numbers, illegal COBOL data:
- 5.1 Illegal COBOL Data
- Btrieve file systems:
- 1.3 Accessing Data
- building SQL statements:
- 1.5.3 Steps to Follow
C
- case conversions:
- 7.2 Default Behavior
- C-ISAM file systems:
- 1.3 Accessing Data
- client/server architecture, DBMaker:
- F.1.2 DBMaker Structure
- COBOL code and hyphens:
- 3.2.2 Defaults Used in XFD Files
- COBOL data, invalid.:
- 5.1 Illegal COBOL Data
- COBOL I/O translation:
- 1.5 How Acu4GL Works
- COBOL programs and sql.acu:
- 2.4.2 To Call sql.acu From a Program
- COBOL records, forming:
- 1.5.3 Steps to Follow
- COBOL:
- 9.1.1 Guidelines
- 7.2 Default Behavior
- F.5.3 Acu4GL for DBMaker: Data Type Mapping
- C.1 Oracle Concepts Overview
- D.5.4 Acu4GL for ODBC: Data Type Mapping
- 9.1.2 The WHERE Constraint
- 6.1 Preparing and Compiling Your COBOL Program
- COBOL:COMMIT verb:
- C.1 Oracle Concepts Overview
- COBOL:database interaction:
- 9.1.1 Guidelines
- COBOL:mapping data to DBMaker:
- F.5.3 Acu4GL for DBMaker: Data Type Mapping
- COBOL:mapping data to ODBC:
- D.5.4 Acu4GL for ODBC: Data Type Mapping
- COBOL:mapping DBMaker data to:
- F.5.3 Acu4GL for DBMaker: Data Type Mapping
- COBOL:mapping ODBC data to:
- D.5.4 Acu4GL for ODBC: Data Type Mapping
- COBOL:matching COBOL fields to database fields:
- 7.2 Default Behavior
- COBOL:modifying procedures:
- 9.1.2 The WHERE Constraint
- COBOL:preparing and compiling programs:
- 6.1 Preparing and Compiling Your COBOL Program
- COBOL:working with:
- 6.1 Preparing and Compiling Your COBOL Program
- columns, mapping:
- 3.2.1 Understanding How the Database Table Is Formed
- 1.5.2 Data Dictionaries and Mapping
- command line and sql acu:
- 2.4.1 Running sql.acu From the Command Line
- COMMENT directive:
- 4.5 COMMENT Directive
- COMMIT verb:
- C.1 Oracle Concepts Overview
- COMMIT_COUNT methods:
- C.1 Oracle Concepts Overview
- COMMIT_COUNT variable:
- COMMIT_COUNT
- communications, DBMaker:
- F.1.2 DBMaker Structure
- COMP-2 numbers, illegal COBOL data:
- 5.1 Illegal COBOL Data
- COMP-3 numbers, illegal COBOL data:
- 5.1 Illegal COBOL Data
- compatibility with databases:
- 1.1 Welcome to Acu4GL
- compiler:
- A.1.2 Installing the Acu4GL for Informix Product
- 1.5.3 Steps to Follow
- 4.8 NAME Directive
- 8.1.1 -Fx Option
- 9.2.1 Compile-time Errors
- 8.1.2 -Fo Option
- compiler:errors:
- 9.2.1 Compile-time Errors
- compiler:-F option:
- 1.5.3 Steps to Follow
- compiler:-Fo option:
- 8.1.2 -Fo Option
- compiler:-Fx option:
- 8.1.1 -Fx Option
- compiler:-Fx3 option:
- 8.1.1 -Fx Option
- compiler:-Fxa option:
- 8.1.1 -Fx Option
- compiler:sample program, Informix:
- A.1.2 Installing the Acu4GL for Informix Product
- compiler:-Zx option:
- 4.8 NAME Directive
- compiling:demonstration program:
- 2.5 The Demonstration Program
- compiling:preparing a COBOL program:
- 6.1 Preparing and Compiling Your COBOL Program
- conditions, OTHER:
- 4.13 WHEN Directive
- configuration variables:
- 9.1.2 The WHERE Constraint
- A.3 Acu4GL for Informix Configuration File Variables
- 1.5.4 Summary
- DEFAULT_HOST
- B.4 Acu4GL for Microsoft SQL Server Configuration File Variables
- XFD_DIRECTORY
- F.4 Acu4GL for DBMaker Configuration File Variables
- XFD_MAP_RESETS
- 4GL_CONVERT_DATES
- 4GL_2000_CUTOFF
- C.4 Acu4GL for Oracle Configuration File Variables
- 4GL_8_DIGIT_CUTOFF
- 4GL_EXTRA_DB_COLS_OK
- 4GL_COLUMN_CASE
- 3.2.6 Naming the XFD
- A4GL_COMMIT_COUNT
- D.4 Acu4GL for ODBC Configuration File Variables
- XFD_MAP
- 4.6 DATE Directive
- 4GL_JULIAN_BASE_DATE
- 1.5.3 Steps to Follow
- filename_HOST
- 8.2 Runtime Configuration Variables
- 4GL_IGNORED_SUFFIX_LIST
- E.6 Acu4GL for Sybase Configuration File Variables
- 4GL_ILLEGAL_DATA
- 5.1.2 Invalid Data Other Than Keys
- configuration variables:4GL_ILLEGAL_DATA:
- 5.1.2 Invalid Data Other Than Keys
- 4GL_ILLEGAL_DATA
- configuration variables:4GL_JULIAN_BASE_DATE:
- 4.6 DATE Directive
- 4GL_JULIAN_BASE_DATE
- configuration variables:DBMaker:
- F.4 Acu4GL for DBMaker Configuration File Variables
- configuration variables:DEFAULT_HOST:
- 1.5.4 Summary
- 1.5.3 Steps to Follow
- DEFAULT_HOST
- configuration variables:filename_HOST:
- filename_HOST
- configuration variables:HOST:
- 1.5.3 Steps to Follow
- configuration variables:Informix:
- A.3 Acu4GL for Informix Configuration File Variables
- configuration variables:Microsoft SQL Server:
- B.4 Acu4GL for Microsoft SQL Server Configuration File Variables
- configuration variables:ODBC:
- D.4 Acu4GL for ODBC Configuration File Variables
- configuration variables:Oracle:
- C.4 Acu4GL for Oracle Configuration File Variables
- configuration variables:overview:
- 8.2 Runtime Configuration Variables
- configuration variables:setting in runtime files:
- 1.5.3 Steps to Follow
- configuration variables:Sybase.:
- E.6 Acu4GL for Sybase Configuration File Variables
- configuration variables:WHERE constraint:
- 9.1.2 The WHERE Constraint
- configuration variables:XFD_DIRECTORY:
- XFD_DIRECTORY
- configuration variables:XFD_MAP:
- 3.2.6 Naming the XFD
- XFD_MAP
- configuration variables:XFD_MAP_RESETS:
- 3.2.6 Naming the XFD
- XFD_MAP_RESETS
- configured login, Oracle:
- C.2.5 Acu4GL for Oracle: Setting Up a User Account
- conflicts between field names:
- 7.3.3 Field Names
- contacting Acucorp:
- 2.2 Technical Support
- conversions:case:
- 7.2 Default Behavior
- conversions:data:
- 7.2 Default Behavior
- creating COBOL records:
- 1.5.3 Steps to Follow
- creating stored procedures, Sybase:
- E.3.5 Installation Steps on the UNIX Server Machine
- creating:dictionaries:
- 1.5.3 Steps to Follow
- creating:makefile, Informix:
- A.1.2 Installing the Acu4GL for Informix Product
- creating:map files, DBMaker:
- A_DBM_ERROR_MAP_FILE
- creating:Map files, ODBC:
- A_ODBC_ERROR_MAP_FILE
- creating:runtimes:
- A.1.2 Installing the Acu4GL for Informix Product
- C.2.3 Installing the Product
- E.3.2 Installation Steps on the UNIX Client
- creating:SQL statements:
- 1.5.3 Steps to Follow
- cursors:Oracle:
- C.2.4 Acu4GL for Oracle: Checking System Parameters
D
- data dictionaries:Acu4GL:
- 1.3.2 Data Dictionaries and Acu4GL
- data dictionaries:creating:
- 1.5.3 Steps to Follow
- data dictionaries:overview:
- 1.5.2 Data Dictionaries and Mapping
- data dictionaries:source code:
- 4.1 Directives
- data dictionaries:XFDs:
- 3.1 Data Dictionaries or XFDs
- data source, ODBC:
- D.2.6 Acu4GL for ODBC: Designating the Host Data Source
- D.2.3 Acu4GL for ODBC: Setting Up Data Sources
- D.1.4 ODBC Structure
- data, invalid database:
- 5.2 Invalid Database Data
- data, invalid key:
- 5.1.1 Invalid Key Data
- data:accessing:
- 1.3 Accessing Data
- data:existing:
- 7.1 Databases
- 7.3 Existing Database Files
- data:format conversion:
- 7.2 Default Behavior
- data:mapping COBOL to DBMaker:
- F.5.3 Acu4GL for DBMaker: Data Type Mapping
- data:mapping COBOL to ODBC:
- D.5.4 Acu4GL for ODBC: Data Type Mapping
- data:mapping DBMaker data to COBOL:
- F.5.3 Acu4GL for DBMaker: Data Type Mapping
- data:mapping DBMaker types:
- F.5.3 Acu4GL for DBMaker: Data Type Mapping
- data:mapping ODBC types to COBOL types:
- D.5.4 Acu4GL for ODBC: Data Type Mapping
- data:new:
- 7.1 Databases
- data:ODBC types:
- D.5.4 Acu4GL for ODBC: Data Type Mapping
- data:restructuring:
- 9.1.1 Guidelines
- data:searches:
- 9.1.1 Guidelines
- data:sequencing:
- 7.2 Default Behavior
- data:types not supported, Informix:
- A.5.2 Acu4GL for Informix: Limits and Ranges
- database data:
- 5.2 Invalid Database Data
- database table:
- C.5 Acu4GL for Oracle: Using the Database Table
- B.5 Acu4GL for Microsoft SQL Server: Using the Database Table
- DATABASE variable:
- DATABASE
- database:accessing:
- 1.5.3 Steps to Follow
- database:compatibility:
- 1.1 Welcome to Acu4GL
- database:concepts:
- 1.4 Database Concepts
- database:how the table is formed:
- 3.2.1 Understanding How the Database Table Is Formed
- databases:
- A.1 Getting Started with Acu4GL for Informix
- 7.1 Databases
- 7.3.3 Field Names
- 7.2 Default Behavior
- 7.3.1 How Do I Match Existing Text Fields?
- 7.3.2 How Do I Match Existing Numeric Fields?
- F.2.6 Acu4GL for DBMaker: Designating the Host Database
- 9.1.1 Guidelines
- A.1.3 Acu4GL for Informix: Designating a Database
- 7.3 Existing Database Files
- databases:ANSI-mode and Acu4GL for Informix support:
- A.1 Getting Started with Acu4GL for Informix
- databases:data sequencing:
- 7.2 Default Behavior
- databases:designating for Acu4GL for Informix:
- A.1.3 Acu4GL for Informix: Designating a Database
- databases:designating host for DBMaker:
- F.2.6 Acu4GL for DBMaker: Designating the Host Database
- databases:existing files:
- 7.3 Existing Database Files
- 7.1 Databases
- databases:field names:
- 7.3.3 Field Names
- databases:interaction with COBOL:
- 9.1.1 Guidelines
- databases:matching fields to COBOL:
- 7.2 Default Behavior
- databases:matching fields to numeric:
- 7.3.2 How Do I Match Existing Numeric Fields?
- databases:matching fields to text:
- 7.3.1 How Do I Match Existing Text Fields?
- databases:new files:
- 7.1 Databases
- databases:upgrading:
- 9.1.1 Guidelines
- DATE directive:
- 4.6 DATE Directive
- DATE fields, illegal COBOL data:
- 5.1 Illegal COBOL Data
- dates, invalid:
- 4.6 DATE Directive
- dates, Julian:
- 4.6 DATE Directive
- DBMaker structure:client/server architecture:
- F.1.2 DBMaker Structure
- DBMaker structure:multiple-tier architecture:
- F.1.3 DBMaker and Acu4GL Architecture
- DBMaker structure:overview:
- F.1.2 DBMaker Structure
- DBMaker structure:single-tier architecture:
- F.1.3 DBMaker and Acu4GL Architecture
- DBMaker structure:single-user architecture:
- F.1.2 DBMaker Structure
- DBMaker variables:
- A_DBM_LOCK_METHOD
- A_DBM_DATABASE
- A_DBM_ERROR_MAP_FILE
- A_DBM_NO_NULL_COLUMNS
- A_DBM_COMMIT_ON_BEGIN
- A_DBM_USE_CHAR_FOR_BINARY
- A_DBM_LOGIN
- F.4 Acu4GL for DBMaker Configuration File Variables
- A_DBM_USE_SPACE_IN_DATES
- A_DBM_PASSWD
- A_DBM_QUOTE_IDENTIFIERS
- A_DBM_UNSIGNED_TINYINT
- DBMaker, Acu4GL:binary large objects:
- F.1.1 What Is DBMaker?
- DBMaker, Acu4GL:client library:
- F.1.2 DBMaker Structure
- DBMaker, Acu4GL:client program:
- F.1.2 DBMaker Structure
- DBMaker, Acu4GL:concepts:
- F.1 DBMaker Concepts Overview
- DBMaker, Acu4GL:configuration variables:
- F.4 Acu4GL for DBMaker Configuration File Variables
- DBMaker, Acu4GL:creating map files:
- A_DBM_ERROR_MAP_FILE
- DBMaker, Acu4GL:data type mapping:
- F.5.3 Acu4GL for DBMaker: Data Type Mapping
- DBMaker, Acu4GL:database communication and control area:
- F.1.2 DBMaker Structure
- DBMaker, Acu4GL:designating host database:
- F.2.6 Acu4GL for DBMaker: Designating the Host Database
- DBMaker, Acu4GL:designating host file system:
- F.2.5 Acu4GL for DBMaker: Designating the Host File System
- DBMaker, Acu4GL:information:
- F.1 DBMaker Concepts Overview
- DBMaker, Acu4GL:installation and setup:
- F.2 Acu4GL for DBMaker Installation and Setup for Windows and UNIX
- DBMaker, Acu4GL:limits and ranges:
- F.5.2 Acu4GL for DBMaker: Limits and Ranges
- DBMaker, Acu4GL:makefiles:
- F.2.3 UNIX Installation Steps for the Acu4GL for DBMaker Product
- DBMaker, Acu4GL:mapping COBOL data to DBMaker data:
- F.5.3 Acu4GL for DBMaker: Data Type Mapping
- DBMaker, Acu4GL:mapping DBMaker data to COBOL:
- F.5.3 Acu4GL for DBMaker: Data Type Mapping
- DBMaker, Acu4GL:questions and answers:
- F.7 Acu4GL for DBMaker: Common Questions and Answers
- DBMaker, Acu4GL:record and table locking:
- F.5.1 Acu4GL for DBMaker: Record and Table Locking
- DBMaker, Acu4GL:retrieving errors:
- F.6.2 Acu4GL for DBMaker: Retrieving Errors
- DBMaker, Acu4GL:runtime errors:
- F.6.1 Acu4GL for DBMaker: Runtime Errors
- DBMaker, Acu4GL:server program:
- F.1.2 DBMaker Structure
- DBMaker, Acu4GL:setting up user account:
- F.2.4 Acu4GL for DBMaker: Setting Up a User Account
- DBMaker, Acu4GL:SQL errors:
- F.6.3 Acu4GL for DBMaker: Native SQL Errors
- DBMaker, Acu4GL:structure.:
- F.1.2 DBMaker Structure
- DBMaker, Acu4GL:technical specifications:
- F.5 Acu4GL for DBMaker: Technical Information
- DBMaker, Acu4GL:troubleshooting:
- F.6 Acu4GL for DBMaker: Troubleshooting
- declaring external variables:
- 9.1.2 The WHERE Constraint
- default behavior, Acu4GL:
- 7.2 Default Behavior
- DEFAULT_HOST variable:
- 1.5.3 Steps to Follow
- DEFAULT_HOST
- 1.5.4 Summary
- defaults, extended file descriptors:
- 3.2.2 Defaults Used in XFD Files
- definitions, record.:
- 3.2.2 Defaults Used in XFD Files
- demo.cbl.:
- 2.5 The Demonstration Program
- demonstration program:
- 2.5 The Demonstration Program
- designating databases, Acu4GL for Informix:
- A.1.3 Acu4GL for Informix: Designating a Database
- designating host data source, ODBC:
- D.2.6 Acu4GL for ODBC: Designating the Host Data Source
- designating host database, DBMaker:
- F.2.6 Acu4GL for DBMaker: Designating the Host Database
- designating host file system:
- F.2.5 Acu4GL for DBMaker: Designating the Host File System
- C.2.7 Acu4GL for Oracle: Designating the Host File System
- B.2.5 Acu4GL for Microsoft SQL Server: Designating the Host File System
- E.4.3 Acu4GL for Sybase: Designating the Host File System
- D.2.5 Acu4GL for ODBC: Designating the Host File System
- designating host file system:DBMaker:
- F.2.5 Acu4GL for DBMaker: Designating the Host File System
- designating host file system:Microsoft SQL Server:
- B.2.5 Acu4GL for Microsoft SQL Server: Designating the Host File System
- designating host file system:ODBC:
- D.2.5 Acu4GL for ODBC: Designating the Host File System
- designating host file system:Oracle:
- C.2.7 Acu4GL for Oracle: Designating the Host File System
- designating host file system:Sybase:
- E.4.3 Acu4GL for Sybase: Designating the Host File System
- dictionaries, data:Acu4GL:
- 1.3.2 Data Dictionaries and Acu4GL
- dictionaries, data:creating:
- 1.5.3 Steps to Follow
- dictionaries, data:overview:
- 1.5.2 Data Dictionaries and Mapping
- dictionaries, data:source code:
- 4.1 Directives
- dictionaries, data:XFDs:
- 3.1 Data Dictionaries or XFDs
- dictionary fields, summary:
- 3.2.3 Summary of Dictionary Fields
- directives:
- 4.4 BINARY Directive
- 4.8 NAME Directive
- 4.3 ALPHA Directive
- 4.13 WHEN Directive
- 3.2.2 Defaults Used in XFD Files
- 3.2.4 Identical Field Names
- 3.2.6 Naming the XFD
- 4.1 Directives
- 4.2 Syntax
- 7.3 Existing Database Files
- 3.2.1 Understanding How the Database Table Is Formed
- 4.5 COMMENT Directive
- 4.6 DATE Directive
- 4.7 FILE Directive
- 4.9 NUMERIC Directive
- 4.10 SECONDARY_TABLE Directive
- 4.11 USE GROUP Directive
- 4.12 VAR_LENGTH Directive
- directives:FILE:
- 3.2.6 Naming the XFD
- 4.7 FILE Directive
- directives:NAME:
- 4.8 NAME Directive
- 3.2.4 Identical Field Names
- directives:USE GROUP:
- 4.11 USE GROUP Directive
- 3.2.1 Understanding How the Database Table Is Formed
- 4.3 ALPHA Directive
- 3.2.2 Defaults Used in XFD Files
- directives:VAR_LENGTH:
- 4.12 VAR_LENGTH Directive
- 4.4 BINARY Directive
- directives:WHEN:
- 4.13 WHEN Directive
- 3.2.2 Defaults Used in XFD Files
- dmapi30.lib, DBMaker:
- F.1.2 DBMaker Structure
- dmserver program, DBMaker:
- F.1.2 DBMaker Structure
- dmsqlc program, DBMaker:
- F.1.2 DBMaker Structure
- document overview:
- 1.2 Document Overview
- drivers, ODBC:
- D.5.3 Acu4GL for ODBC: Driver Requirements
- D.1.4 ODBC Structure
E
- environment, user:
- E.4.2 Acu4GL for Sybase: Setting Up the User Environment
- D.2.4 Acu4GL for ODBC: Setting Up the User Environment
- C.2.6 Acu4GL for Oracle: Setting Up the User Environment
- B.2.4 Acu4GL for Microsoft SQL Server: Setting Up the User Environment
- errors, compile:
- 9.2.1 Compile-time Errors
- errors, retrieving:
- A.6.2 Acu4GL for Informix: Retrieving Errors
- C.7.2 Acu4GL for Oracle: Retrieving Errors
- E.8.2 Acu4GL for Sybase: Retrieving Errors
- B.7.2 Acu4GL for Microsoft SQL Server: Retrieving Errors
- D.6.2 Acu4GL for ODBC: Retrieving Errors
- F.6.2 Acu4GL for DBMaker: Retrieving Errors
- errors, runtime:
- B.7.1 Acu4GL for Microsoft SQL Server: Runtime Errors
- D.6.1 Acu4GL for ODBC: Runtime Errors
- A.6.1 Acu4GL for Informix: Runtime Errors
- C.7.1 Acu4GL for Oracle: Runtime Errors
- E.8.1 Acu4GL for Sybase: Runtime Errors
- F.6.1 Acu4GL for DBMaker: Runtime Errors
- errors, SQL:
- D.6.3 Acu4GL for ODBC: Native SQL Errors
- F.6.3 Acu4GL for DBMaker: Native SQL Errors
- existing database files:
- 7.1 Databases
- 7.3 Existing Database Files
- extended file descriptors:defaults:
- 3.2.2 Defaults Used in XFD Files
- extended file descriptors:directives, introduction:
- 4.1 Directives
- extended file descriptors:location:
- 3.2.2 Defaults Used in XFD Files
- extended file descriptors:mapping to other files:
- 3.2.6 Naming the XFD
- extended file descriptors:names:
- 3.2.6 Naming the XFD
- external variables, declaring:
- 9.1.2 The WHERE Constraint
F
- -F option:
- 1.5.3 Steps to Follow
- FAQs:
- C.8 Acu4GL for Oracle: Common Questions and Answers
- B.8 Acu4GL for Microsoft SQL Server: Common Questions and Answers
- A.7 Acu4GL for Informix: Common Questions and Answers
- F.7 Acu4GL for DBMaker: Common Questions and Answers
- D.7 Acu4GL for ODBC: Common Questions and Answers
- E.9 Acu4GL for Sybase: Common Questions and Answers
- features:Informix supported:
- A.5.1 Acu4GL for Informix: Supported Features
- features:Oracle supported:
- C.6.1 Acu4GL for Oracle: Supported Features
- field names:
- 3.2.4 Identical Field Names
- 3.2.5 Long Field Names
- fields:key:
- 3.2.2 Defaults Used in XFD Files
- fields:mapping:
- 3.2.1 Understanding How the Database Table Is Formed
- 1.5.2 Data Dictionaries and Mapping
- fields:matching COBOL to database:
- 7.2 Default Behavior
- fields:matching numeric to database:
- 7.3.2 How Do I Match Existing Numeric Fields?
- fields:matching text to database:
- 7.3.1 How Do I Match Existing Text Fields?
- fields:names:
- 7.3.3 Field Names
- FILE directive:
- 3.2.6 Naming the XFD
- 4.7 FILE Directive
- file input and output:
- 9.1.1 Guidelines
- file objects, DBMaker:
- F.1.1 What Is DBMaker?
- file systems, host:
- E.4.3 Acu4GL for Sybase: Designating the Host File System
- D.2.5 Acu4GL for ODBC: Designating the Host File System
- B.2.5 Acu4GL for Microsoft SQL Server: Designating the Host File System
- F.2.5 Acu4GL for DBMaker: Designating the Host File System
- C.2.7 Acu4GL for Oracle: Designating the Host File System
- file systems, indexed:
- 1.3 Accessing Data
- file systems, Informix:
- A.5 Acu4GL for Informix: Technical Information
- filename translation:
- D.3 Acu4GL for ODBC and Filename Translation
- A.2 Acu4GL for Informix and Filename Translation
- F.3 Acu4GL for DBMaker and Filename Translation
- C.3 Acu4GL for Oracle and Filename Translation
- B.3 Acu4GL for Microsoft SQL Server and Filename Translation
- E.5 Acu4GL for Sybase and Filename Translation
- filename_HOST variable:
- filename_HOST
- filenames:
- C.3 Acu4GL for Oracle and Filename Translation
- E.5 Acu4GL for Sybase and Filename Translation
- B.3 Acu4GL for Microsoft SQL Server and Filename Translation
- D.3 Acu4GL for ODBC and Filename Translation
- F.3 Acu4GL for DBMaker and Filename Translation
- A.2 Acu4GL for Informix and Filename Translation
- filenames:hyphens in:
- A.2 Acu4GL for Informix and Filename Translation
- E.5 Acu4GL for Sybase and Filename Translation
- F.3 Acu4GL for DBMaker and Filename Translation
- B.3 Acu4GL for Microsoft SQL Server and Filename Translation
- C.3 Acu4GL for Oracle and Filename Translation
- D.3 Acu4GL for ODBC and Filename Translation
- filenames:lowercase letters in:
- A.2 Acu4GL for Informix and Filename Translation
- E.5 Acu4GL for Sybase and Filename Translation
- D.3 Acu4GL for ODBC and Filename Translation
- F.3 Acu4GL for DBMaker and Filename Translation
- B.3 Acu4GL for Microsoft SQL Server and Filename Translation
- filenames:underscores in:
- E.5 Acu4GL for Sybase and Filename Translation
- C.3 Acu4GL for Oracle and Filename Translation
- D.3 Acu4GL for ODBC and Filename Translation
- B.3 Acu4GL for Microsoft SQL Server and Filename Translation
- A.2 Acu4GL for Informix and Filename Translation
- F.3 Acu4GL for DBMaker and Filename Translation
- filenames:uppercase letters in:
- C.3 Acu4GL for Oracle and Filename Translation
- files, database:existing:
- 7.3 Existing Database Files
- 7.1 Databases
- files, database:new:
- 7.1 Databases
- files, map:
- A_DBM_ERROR_MAP_FILE
- A_ODBC_ERROR_MAP_FILE
- files, Vision:
- 9.1.1 Guidelines
- FILLER definition:
- 4.13 WHEN Directive
- 3.2.2 Defaults Used in XFD Files
- final name, extended file descriptors:
- 3.2.6 Naming the XFD
- -Fo option:
- 8.1.2 -Fo Option
- format, data conversion:
- 7.2 Default Behavior
- forming COBOL records:
- 1.5.3 Steps to Follow
- forming the final XFD name:
- 3.2.6 Naming the XFD
- -Fx option:
- 8.1.1 -Fx Option
- -Fx3 option:
- 8.1.1 -Fx Option
- -Fxa option:
- 8.1.1 -Fx Option
G
- generic file handler:
- 1.3 Accessing Data
- getting help:
- 2.2 Technical Support
- getting started:
- A.1 Getting Started with Acu4GL for Informix
- B.2 Getting Started with Acu4GL for Microsoft SQL Server
- E.2 Getting Started with Acu4GL for Sybase
- C.2 Acu4GL for Oracle Installation and Setup
- D.2 Acu4GL for ODBC Installation and Setup
- 2.1 Getting Started
- group items and DATE directive:
- 4.6 DATE Directive
- group items:
- 3.2.2 Defaults Used in XFD Files
- growth, planning ahead:
- 9.1.1 Guidelines
- guidelines:existing database files:
- 7.3 Existing Database Files
- guidelines:performance:
- 9.1.1 Guidelines
H
- handling invalid dates:
- 4.6 DATE Directive
- Help menu, demonstration program:
- 2.5 The Demonstration Program
- help, getting:
- 2.2 Technical Support
- HIGH-VALUES, illegal COBOL data:
- 5.1 Illegal COBOL Data
- host data source, designating for Acu4GL for ODBC:
- D.2.6 Acu4GL for ODBC: Designating the Host Data Source
- host database, designating for Acu4GL for DBMaker:
- F.2.6 Acu4GL for DBMaker: Designating the Host Database
- host file systems, designating for Acu4GL:
- C.2.7 Acu4GL for Oracle: Designating the Host File System
- F.2.5 Acu4GL for DBMaker: Designating the Host File System
- E.4.3 Acu4GL for Sybase: Designating the Host File System
- B.2.5 Acu4GL for Microsoft SQL Server: Designating the Host File System
- D.2.5 Acu4GL for ODBC: Designating the Host File System
- HOST variable:
- 1.5.3 Steps to Follow
- how Acu4GL works:
- 1.5.1 What Is a Transparent Interface?
- 1.5 How Acu4GL Works
- hyphens and COBOL code:
- 3.2.2 Defaults Used in XFD Files
- hyphens in filenames:
- B.3 Acu4GL for Microsoft SQL Server and Filename Translation
- A.2 Acu4GL for Informix and Filename Translation
- F.3 Acu4GL for DBMaker and Filename Translation
- E.5 Acu4GL for Sybase and Filename Translation
- D.3 Acu4GL for ODBC and Filename Translation
- C.3 Acu4GL for Oracle and Filename Translation
I
- I/O requests, passing to the interface:
- 1.5.3 Steps to Follow
- identical field names:
- 3.2.4 Identical Field Names
- illegal COBOL data:
- 5.1.2 Invalid Data Other Than Keys
- 5.1 Illegal COBOL Data
- indexed file systems:
- 1.3.2 Data Dictionaries and Acu4GL
- 1.3 Accessing Data
- 3.1 Data Dictionaries or XFDs
- indexed file systems:alfred, editor:
- 3.1 Data Dictionaries or XFDs
- 1.3.2 Data Dictionaries and Acu4GL
- indexes and tables:
- 9.1.1 Guidelines
- Indicator area:
- 4.2 Syntax
- inf_inst program:
- A.1.2 Installing the Acu4GL for Informix Product
- INF_LOGIN variable:
- INF_LOGIN
- INF_PASSWD variable:
- INF_PASSWD
- Informix variables:
- MAX_CURSORS
- A_INF_NO_TRANSACTION_ERROR
- DATABASE
- INF_LOGIN
- INF_PASSWD
- A.3 Acu4GL for Informix Configuration File Variables
- A_INF_DUPLICATE_KEY
- A_INFORMIX_ERROR_FILE
- Informix variables:Open_cursors:
- MAX_CURSORS
- Informix, Acu4GL:7.2 and 7.3 performance:
- A.4 Informix 7.2 and 7.3 Performance
- A.7 Acu4GL for Informix: Common Questions and Answers
- Informix, Acu4GL:compile sample program:
- A.1.2 Installing the Acu4GL for Informix Product
- Informix, Acu4GL:configuration variables:
- A.3 Acu4GL for Informix Configuration File Variables
- Informix, Acu4GL:creating a new runtime:
- A.1.2 Installing the Acu4GL for Informix Product
- Informix, Acu4GL:data types not supported:
- A.5.2 Acu4GL for Informix: Limits and Ranges
- Informix, Acu4GL:database, designating:
- A.1.3 Acu4GL for Informix: Designating a Database
- Informix, Acu4GL:getting started:
- A.1 Getting Started with Acu4GL for Informix
- Informix, Acu4GL:installation:
- A.1.1 Installation of the Acu4GL for Informix Product
- Informix, Acu4GL:limits and ranges:
- A.5.2 Acu4GL for Informix: Limits and Ranges
- Informix, Acu4GL:linking runtime:
- A.1.2 Installing the Acu4GL for Informix Product
- Informix, Acu4GL:makefile:
- A.1.2 Installing the Acu4GL for Informix Product
- Informix, Acu4GL:query optimizer:
- A.7 Acu4GL for Informix: Common Questions and Answers
- A.4 Informix 7.2 and 7.3 Performance
- Informix, Acu4GL:questions and answers:
- A.7 Acu4GL for Informix: Common Questions and Answers
- Informix, Acu4GL:retrieving errors:
- A.6.2 Acu4GL for Informix: Retrieving Errors
- Informix, Acu4GL:runtime errors:
- A.6.1 Acu4GL for Informix: Runtime Errors
- Informix, Acu4GL:shared libraries:
- A.1.2 Installing the Acu4GL for Informix Product
- Informix, Acu4GL:supported features:
- A.5.1 Acu4GL for Informix: Supported Features
- Informix, Acu4GL:switching file systems:
- A.5 Acu4GL for Informix: Technical Information
- Informix, Acu4GL:technical tips:
- A.5 Acu4GL for Informix: Technical Information
- Informix, Acu4GL:troubleshooting:
- A.6 Acu4GL for Informix: Troubleshooting
- input, file:
- 9.1.1 Guidelines
- installation:
- C.2.1 Windows Installation Steps for the Acu4GL for Oracle Product
- B.2.1 Acu4GL for Microsoft SQL Server Installation and Setup
- E.2.1 Sybase RDBMS Installation
- F.2 Acu4GL for DBMaker Installation and Setup for Windows and UNIX
- D.2.1 ODBC Installation
- A.1.1 Installation of the Acu4GL for Informix Product
- B.2.2 Installing the Acu4GL for Microsoft SQL Server Product on a Client Machine
- C.2.2 UNIX Installation Steps for the Oracle Acu4GL Product
- 2.3 Installation
- installing stored procedures, Sybase:
- E.3.5 Installation Steps on the UNIX Server Machine
- E.3.6 Installation Steps on a Windows NT Server Machine - Windows Client
- interaction, databases and COBOL:
- 9.1.1 Guidelines
- interactive SQL.:
- B.2.1 Acu4GL for Microsoft SQL Server Installation and Setup
- interface:passing I/O requests to:
- 1.5.3 Steps to Follow
- interface:routines:
- 1.3.1 Interface Routines
- interpretation, filenames:
- B.3 Acu4GL for Microsoft SQL Server and Filename Translation
- introduction, Acu4GL:
- 1.1 Welcome to Acu4GL
- invalid:COBOL data.:
- 5.1 Illegal COBOL Data
- invalid:database data:
- 5.2 Invalid Database Data
- invalid:dates, handling:
- 4.6 DATE Directive
- invalid:key data:
- 5.1.1 Invalid Key Data
- invalid:other data:
- 5.1.2 Invalid Data Other Than Keys
- ISQL:
- A.1.2 Installing the Acu4GL for Informix Product
- B.2.1 Acu4GL for Microsoft SQL Server Installation and Setup
- E.2.1 Sybase RDBMS Installation
- issues, performance:
- 9.1 Performance Issues
J
- Julian dates:
- 4.6 DATE Directive
K
- key data, invalid:
- 5.1.1 Invalid Key Data
- key fields:
- 3.2.2 Defaults Used in XFD Files
- KEY IS phrase:
- 3.2.2 Defaults Used in XFD Files
L
- libraries, shared:
- A.1.2 Installing the Acu4GL for Informix Product
- C.2.3 Installing the Product
- E.3.2 Installation Steps on the UNIX Client
- library, DBMaker client:
- F.1.2 DBMaker Structure
- limitations, WHERE constraint:
- 9.1.2 The WHERE Constraint
- limits and ranges:
- B.6.3 Acu4GL for Microsoft SQL Server: Limits and Ranges
- D.5.2 Acu4GL for ODBC: Limits and Ranges
- E.7.3 Acu4GL for Sybase: Limits and Ranges
- F.5.2 Acu4GL for DBMaker: Limits and Ranges
- C.6.2 Acu4GL for Oracle: Limits and Ranges
- A.5.2 Acu4GL for Informix: Limits and Ranges
- linking Acu4GL for Oracle:
- C.2.1 Windows Installation Steps for the Acu4GL for Oracle Product
- linking runtime:Acu4GL for Informix:
- A.1.2 Installing the Acu4GL for Informix Product
- linking runtime:Acu4GL for Oracle:
- C.2.3 Installing the Product
- linking runtime:Acu4GL for Sybase:
- E.3.2 Installation Steps on the UNIX Client
- location, extended file descriptors:
- 3.2.2 Defaults Used in XFD Files
- locking, record:
- C.1 Oracle Concepts Overview
- D.5.1 Acu4GL for ODBC: Record and Table Locking
- F.5.1 Acu4GL for DBMaker: Record and Table Locking
- E.7.1 Acu4GL for Sybase: Record and Table Locking
- B.6.1 Acu4GL for Microsoft SQL Server: Table Locking
- locking, tables:
- B.6.1 Acu4GL for Microsoft SQL Server: Table Locking
- D.5.1 Acu4GL for ODBC: Record and Table Locking
- E.7.1 Acu4GL for Sybase: Record and Table Locking
- F.5.1 Acu4GL for DBMaker: Record and Table Locking
- login, automatic Oracle:
- C.2.5 Acu4GL for Oracle: Setting Up a User Account
- login, configured Oracle:
- C.2.5 Acu4GL for Oracle: Setting Up a User Account
- long field names:
- 3.2.5 Long Field Names
- lowercase letters in filenames:
- E.5 Acu4GL for Sybase and Filename Translation
- D.3 Acu4GL for ODBC and Filename Translation
- F.3 Acu4GL for DBMaker and Filename Translation
- B.3 Acu4GL for Microsoft SQL Server and Filename Translation
- A.2 Acu4GL for Informix and Filename Translation
- LOW-VALUES, illegal COBOL data:
- 5.1 Illegal COBOL Data
M
- makefiles:DBMaker:
- F.2.3 UNIX Installation Steps for the Acu4GL for DBMaker Product
- makefiles:Informix:
- A.1.2 Installing the Acu4GL for Informix Product
- makefiles:Oracle:
- C.2.3 Installing the Product
- makefiles:Sybase:
- E.3.2 Installation Steps on the UNIX Client
- managing drivers, ODBC:
- D.1.4 ODBC Structure
- map files, creating:
- A_DBM_ERROR_MAP_FILE
- A_ODBC_ERROR_MAP_FILE
- map files, creating:DBMaker:
- A_DBM_ERROR_MAP_FILE
- map files, creating:ODBC:
- A_ODBC_ERROR_MAP_FILE
- mapping:COBOL data to DBMaker:
- F.5.3 Acu4GL for DBMaker: Data Type Mapping
- mapping:COBOL data to ODBC data:
- D.5.4 Acu4GL for ODBC: Data Type Mapping
- mapping:columns and records:
- 3.2.1 Understanding How the Database Table Is Formed
- 1.5.2 Data Dictionaries and Mapping
- mapping:DBMaker data:
- F.5.3 Acu4GL for DBMaker: Data Type Mapping
- mapping:extended file descriptors:
- 3.2.6 Naming the XFD
- mapping:ODBC data types:
- D.5.4 Acu4GL for ODBC: Data Type Mapping
- mapping:other files to an XFD:
- 3.2.6 Naming the XFD
- matching:COBOL fields to database fields:
- 7.2 Default Behavior
- matching:numeric fields to database fields:
- 7.3.2 How Do I Match Existing Numeric Fields?
- matching:text fields to database fields:
- 7.3.1 How Do I Match Existing Text Fields?
- MAX_CURSORS variable:Informix:
- MAX_CURSORS
- MAX_CURSORS variable:Oracle:
- MAX_CURSORS
- menus, demonstration program:
- 2.5 The Demonstration Program
- modifying COBOL procedures:
- 9.1.2 The WHERE Constraint
- Microsoft SQL Server variables:
- A_MSSQL_NO_DBID
- A_MSSQL_NATIVE_LOCK_TIMEOUT
- B.4 Acu4GL for Microsoft SQL Server Configuration File Variables
- A_MSSQL_NO_COUNT_CHECK
- A_MSSQL_ADD_TIMESTAMP
- A_MSSQL_NO_DBCLOSE
- A_MSSQL_CURSOR_OPTION_1
A_MSSQL_CURSOR_OPTION_2
A_MSSQL_CURSOR_OPTION_3
- A_MSSQL_NO_RECORD_LOCKS
- 4GL_IGNORED_SUFFIX_LIST
- A_MSSQL_NO_TABLE_LOCKS
- A_MSSQL_EXTRA_PROC
- A_MSSQL_NO_23_ON_START
- A_MSSQL_FORCED_INDEX
- A_MSSQL_NT_AUTHENTICATION
- A_MSSQL_LOGIN
- A_MSSQL_PACKETSIZE
- A_MSSQL_MAX_COLUMNS
- A_MSSQL_PASSWD
- A_MSSQL_VISION_LOCKS_FILE
- A_MSSQL_DEFAULT_CONNECTION
- A_MSSQL_FAST_ACCESS
- A_MSSQL_LOCK_DB
- A_MSSQL_MAX_CHARACTERS
- A_MSSQL_ADD_IDENTITY
- A_MSSQL_DATABASE
- A_MSSQL_ROWCOUNT
- A_MSSQL_SELECT_KEY_ONLY
- A_MSSQL_SKIP_ALTERNATE_KEYS
- A_MSSQL_TRANSLATE_TO_ANSI
- A_MSSQL_UNLOCK_ON_EXECUTE
- A_MSSQL_USE_DROPDOWN_QUERIES
- Microsoft SQL Server variables:overview:
- B.4 Acu4GL for Microsoft SQL Server Configuration File Variables
- Microsoft SQL Server, Acu4GL:alternate REWRITE method:
- B.1 Microsoft SQL Server Concepts Overview
- Microsoft SQL Server, Acu4GL:configuration variables:
- B.4 Acu4GL for Microsoft SQL Server Configuration File Variables
- Microsoft SQL Server, Acu4GL:database table:
- B.5 Acu4GL for Microsoft SQL Server: Using the Database Table
- Microsoft SQL Server, Acu4GL:designating host file system:
- B.2.5 Acu4GL for Microsoft SQL Server: Designating the Host File System
- Microsoft SQL Server, Acu4GL:getting started:
- B.2 Getting Started with Acu4GL for Microsoft SQL Server
- Microsoft SQL Server, Acu4GL:installation on client:
- B.2.2 Installing the Acu4GL for Microsoft SQL Server Product on a Client Machine
- Microsoft SQL Server, Acu4GL:installation on NT server:
- B.2.2 Installing the Acu4GL for Microsoft SQL Server Product on a Client Machine
- Microsoft SQL Server, Acu4GL:installation:
- B.2.1 Acu4GL for Microsoft SQL Server Installation and Setup
- Microsoft SQL Server, Acu4GL:limits and ranges:
- B.6.3 Acu4GL for Microsoft SQL Server: Limits and Ranges
- Microsoft SQL Server, Acu4GL:overview:
- B.1 Microsoft SQL Server Concepts Overview
- Microsoft SQL Server, Acu4GL:questions and answers:
- B.8 Acu4GL for Microsoft SQL Server: Common Questions and Answers
- Microsoft SQL Server, Acu4GL:retrieving errors:
- B.7.2 Acu4GL for Microsoft SQL Server: Retrieving Errors
- Microsoft SQL Server, Acu4GL:runtime errors:
- B.7.1 Acu4GL for Microsoft SQL Server: Runtime Errors
- Microsoft SQL Server, Acu4GL:security:
- B.1 Microsoft SQL Server Concepts Overview
- Microsoft SQL Server, Acu4GL:servers:
- B.1 Microsoft SQL Server Concepts Overview
- Microsoft SQL Server, Acu4GL:setting up a user account:
- B.2.3 Acu4GL for Microsoft SQL Server: Setting Up a User Account
- Microsoft SQL Server, Acu4GL:setting up user environment:
- B.2.4 Acu4GL for Microsoft SQL Server: Setting Up the User Environment
- Microsoft SQL Server, Acu4GL:stored procedures.:
- B.6.2 Acu4GL for Microsoft SQL Server: Stored Procedures
- Microsoft SQL Server, Acu4GL:table locking:
- B.6.1 Acu4GL for Microsoft SQL Server: Table Locking
- Microsoft SQL Server, Acu4GL:table ownership:
- B.1 Microsoft SQL Server Concepts Overview
- Microsoft SQL Server, Acu4GL:technical specifications:
- B.6 Acu4GL for Microsoft SQL Server: Technical Information
- Microsoft SQL Server, Acu4GL:troubleshooting:
- B.7 Acu4GL for Microsoft SQL Server: Troubleshooting
- multiple indexes and tables:
- 9.1.1 Guidelines
- multiple record definitions:
- 4.13 WHEN Directive
- 3.2.2 Defaults Used in XFD Files
- multiple-tier architecture:
- F.1.3 DBMaker and Acu4GL Architecture
- D.1.4 ODBC Structure
N
- NAME directive:
- 3.2.4 Identical Field Names
- 4.8 NAME Directive
- names, extended file descriptors:
- 3.2.6 Naming the XFD
- names, fields:
- 7.3.3 Field Names
- 3.2.4 Identical Field Names
- 3.2.5 Long Field Names
- names, fields:
- 3.2.4 Identical Field Names
- new databases files:
- 7.1 Databases
- NUMERIC directive:
- 4.9 NUMERIC Directive
- numeric fields, matching to database:
- 7.3.2 How Do I Match Existing Numeric Fields?
O
- OCCURS definition:
- 3.2.2 Defaults Used in XFD Files
- ODBC structure:
- D.1.4 ODBC Structure
- ODBC variables:
- A_ODBC_LOGIN
- A_ODBC_NO_NULL_COLUMNS
- A_ODBC_DATASOURCE
- A_ODBC_UNSIGNED_TINYINT
- A_ODBC_USE_SPACE_IN_DATES
- A_ODBC_PASSWD
- A_ODBC_QUOTE_IDENTIFIERS
- A_ODBC_COMMIT_ON_BEGIN
- D.4 Acu4GL for ODBC Configuration File Variables
- A_ODBC_USE_CHAR_FOR_BINARY
- A4GL_MIN_DATE
- A_ODBC_LOCK_METHOD
- A_ODBC_ERROR_MAP_FILE
- A_ODBC_PRINT_LOG
- A4GL_MAX_DATE
- ODBC, Acu4GL:application:
- D.1.4 ODBC Structure
- ODBC, Acu4GL:concepts:
- D.1 ODBC Concepts
- ODBC, Acu4GL:configuration variables:
- D.4 Acu4GL for ODBC Configuration File Variables
- ODBC, Acu4GL:creating map files:
- A_ODBC_ERROR_MAP_FILE
- ODBC, Acu4GL:data sources:
- D.1.4 ODBC Structure
- D.2.3 Acu4GL for ODBC: Setting Up Data Sources
- ODBC, Acu4GL:data type mapping:
- D.5.4 Acu4GL for ODBC: Data Type Mapping
- ODBC, Acu4GL:designating host data source:
- D.2.6 Acu4GL for ODBC: Designating the Host Data Source
- ODBC, Acu4GL:designating host file system:
- D.2.5 Acu4GL for ODBC: Designating the Host File System
- ODBC, Acu4GL:Driver Manager:
- D.1.4 ODBC Structure
- ODBC, Acu4GL:driver requirements:
- D.5.3 Acu4GL for ODBC: Driver Requirements
- ODBC, Acu4GL:driver test:
- D.5.3 Acu4GL for ODBC: Driver Requirements
- ODBC, Acu4GL:drivers:
- D.1.4 ODBC Structure
- ODBC, Acu4GL:getting started:
- D.2 Acu4GL for ODBC Installation and Setup
- ODBC, Acu4GL:information:
- D.1 ODBC Concepts
- ODBC, Acu4GL:installation and setup:
- D.2.1 Installation
- ODBC, Acu4GL:limits and ranges:
- D.5.2 Acu4GL for ODBC: Limits and Ranges
- ODBC, Acu4GL:mapping COBOL data to ODBC data:
- D.5.4 Acu4GL for ODBC: Data Type Mapping
- ODBC, Acu4GL:mapping ODBC data types to COBOL data types:
- D.5.4 Acu4GL for ODBC: Data Type Mapping
- ODBC, Acu4GL:origins of ODBC:
- D.1.2 Origins of ODBC
- ODBC, Acu4GL:questions and answers:
- D.7 Acu4GL for ODBC: Common Questions and Answers
- ODBC, Acu4GL:record and table locking:
- D.5.1 Acu4GL for ODBC: Record and Table Locking
- ODBC, Acu4GL:restrictions:
- D.1.3 Restrictions
- ODBC, Acu4GL:retrieving errors:
- D.6.2 Acu4GL for ODBC: Retrieving Errors
- ODBC, Acu4GL:runtime errors:
- D.6.1 Acu4GL for ODBC: Runtime Errors
- ODBC, Acu4GL:setting up the user environment:
- D.2.4 Acu4GL for ODBC: Setting Up the User Environment
- ODBC, Acu4GL:SQL errors:
- D.6.3 Acu4GL for ODBC: Native SQL Errors
- ODBC, Acu4GL:structure:
- D.1.4 ODBC Structure
- ODBC, Acu4GL:technical specifications:
- D.5 Acu4GL for ODBC: Technical Information
- ODBC, Acu4GL:troubleshooting:
- D.6 Acu4GL for ODBC: Troubleshooting
- ODBC:
- D.1.1 What is ODBC?
- D.1.2 Origins of ODBC
- Open Database Connectivity:
- D.1 ODBC Concepts
- open_cursors variable:Oracle
- C.1 Oracle Concepts Overview
- MAX_CURSORS
- Open_cursors variable:Informix:
- MAX_CURSORS
- open_cursors variable:Oracle:
- C.1 Oracle Concepts Overview
- Options menu, demonstration program:
- 2.5 The Demonstration Program
- options, compiler:
- 8.1.2 -Fo Option
- ORA_LOGIN variable:
- ORA_LOGIN
- ORA_PASSWD variable:
- ORA_PASSWD
- Oracle cursors:
- C.2.4 Acu4GL for Oracle: Checking System Parameters
- Oracle variables:
- A_ORACLE_ERROR_FILE
- COMMIT_COUNT
- C.4 Acu4GL for Oracle Configuration File Variables
- USER_PATH
- USE_INVALID_CURSOR_LOGIC
- A_ORA_DUPLICATE_KEY
- A_ORA_HINTS
- A_ORA_DEFER_CLOSE
- MAX_CURSORS
- ORA_LOGIN
- ORA_PASSWD
- Oracle, Acu4GL:automatic login:
- C.2.5 Acu4GL for Oracle: Setting Up a User Account
- Oracle, Acu4GL:checking system parameters:
- C.2.4 Acu4GL for Oracle: Checking System Parameters
- Oracle, Acu4GL:configured login:
- C.2.5 Acu4GL for Oracle: Setting Up a User Account
- Oracle, Acu4GL:creating a new runtime:
- C.2.3 Installing the Product
- Oracle, Acu4GL:cursors:
- C.2.4 Acu4GL for Oracle: Checking System Parameters
- Oracle, Acu4GL:database table:
- C.5 Acu4GL for Oracle: Using the Database Table
- Oracle, Acu4GL:designating host file system:
- C.2.7 Acu4GL for Oracle: Designating the Host File System
- Oracle, Acu4GL:FAQs:
- C.8 Acu4GL for Oracle: Common Questions and Answers
- Oracle, Acu4GL:getting started:
- C.2 Acu4GL for Oracle Installation and Setup
- Oracle, Acu4GL:installation for UNIX:
- C.2.2 UNIX Installation Steps for the Oracle Acu4GL Product
- Oracle, Acu4GL:installation for Windows:
- C.2.1 Windows Installation Steps for the Acu4GL for Oracle Product
- Oracle, Acu4GL:limits and ranges:
- C.6.2 Acu4GL for Oracle: Limits and Ranges
- Oracle, Acu4GL:linking runtime:
- C.2.3 Installing the Product
- Oracle, Acu4GL:linking:
- C.2.1 Windows Installation Steps for the Acu4GL for Oracle Product
- Oracle, Acu4GL:makefiles:
- C.2.3 Installing the Product
- Oracle, Acu4GL:open_cursors:
- C.1 Oracle Concepts Overview
- Oracle, Acu4GL:questions and answers:
- C.8 Acu4GL for Oracle: Common Questions and Answers
- Oracle, Acu4GL:record locking:
- C.1 Oracle Concepts Overview
- Oracle, Acu4GL:retrieving errors:
- C.7.2 Acu4GL for Oracle: Retrieving Errors
- Oracle, Acu4GL:runtime errors:
- C.7.1 Acu4GL for Oracle: Runtime Errors
- Oracle, Acu4GL:SCO UNIX:
- C.2.3 Installing the Product
- Oracle, Acu4GL:security:
- C.1 Oracle Concepts Overview
- Oracle, Acu4GL:setting up the search path:
- C.2.8 Acu4GL for Oracle: Setting Up the Search Path
- Oracle, Acu4GL:setting up user accounts:
- C.2.5 Acu4GL for Oracle: Setting Up a User Account
- Oracle, Acu4GL:setting up user environment:
- C.2.6 Acu4GL for Oracle: Setting Up the User Environment
- Oracle, Acu4GL:shared libraries:
- C.2.3 Installing the Product
- Oracle, Acu4GL:supported features:
- C.6.1 Acu4GL for Oracle: Supported Features
- Oracle, Acu4GL:table ownership:
- C.1 Oracle Concepts Overview
- Oracle, Acu4GL:technical specifications:
- C.6 Acu4GL for Oracle: Technical Information
- Oracle, Acu4GL:transactions:
- C.2.9 Acu4GL for Oracle: Handling Transactions
- C.6.1 Acu4GL for Oracle: Supported Features
- C.1 Oracle Concepts Overview
- Oracle, Acu4GL:troubleshooting:
- C.7 Acu4GL for Oracle: Troubleshooting
- origins of ODBC:
- D.1.2 Origins of ODBC
- OTHER condition:
- 4.13 WHEN Directive
- output, file:
- 9.1.1 Guidelines
- overview:Acu4GL for Microsoft SQL Server:
- B.1 Microsoft SQL Server Concepts Overview
- overview:Acu4GL:
- 1.1 Welcome to Acu4GL
- overview:configuration variables:
- 8.2 Runtime Configuration Variables
- overview:data dictionaries:
- 3.1 Data Dictionaries or XFDs
- overview:DBMaker:
- F.1 DBMaker Concepts Overview
- overview:demonstration program:
- 2.5 The Demonstration Program
- overview:document:
- 1.2 Document Overview
- overview:extended file descriptors:
- 3.1 Data Dictionaries or XFDs
- 3.2.6 Naming the XFD
- overview:getting started:
- 2.1 Getting Started
- overview:installation:
- 2.3 Installation
- overview:multiple record definitions:
- 3.2.2 Defaults Used in XFD Files
- overview:ODBC:
- D.1 ODBC Concepts
- overview:Sybase:
- E.1 Sybase Concepts Overview
- ownership, tables:
- E.1 Sybase Concepts Overview
- C.1 Oracle Concepts Overview
- B.1 Microsoft SQL Server Concepts Overview
P
- parameters, Oracle system:
- C.2.4 Acu4GL for Oracle: Checking System Parameters
- performance:compile errors:
- 9.2.1 Compile-time Errors
- performance:compile warnings:
- 9.2.2 Compile-time Warnings
- performance:data searches:
- 9.1.1 Guidelines
- performance:database interaction with COBOL:
- 9.1.1 Guidelines
- performance:file input and output:
- 9.1.1 Guidelines
- performance:guidelines:
- 9.1.1 Guidelines
- performance:Informix 7.2 and 7.3:
- A.7 Acu4GL for Informix: Common Questions and Answers
- A.4 Informix 7.2 and 7.3 Performance
- performance:overview:
- 9.1 Performance Issues
- performance:planning ahead:
- 9.1.1 Guidelines
- performance:restructuring data:
- 9.1.1 Guidelines
- performance:runtime errors:
- A.6.1 Acu4GL for Informix: Runtime Errors
- B.7.1 Acu4GL for Microsoft SQL Server: Runtime Errors
- C.7.1 Acu4GL for Oracle: Runtime Errors
- D.6.1 Acu4GL for ODBC: Runtime Errors
- E.8.1 Acu4GL for Sybase: Runtime Errors
- F.6.1 Acu4GL for DBMaker: Runtime Errors
- performance:SQL errors:
- F.6.3 Acu4GL for DBMaker: Native SQL Errors
- D.6.3 Acu4GL for ODBC: Native SQL Errors
- performance:tables and multiple indexes:
- 9.1.1 Guidelines
- performance:transactions:
- 9.1.1 Guidelines
- performance:Vision files:
- 9.1.1 Guidelines
- planning ahead, growth:
- 9.1.1 Guidelines
- plug-in, ACUCOBOL-GT:
- 1.3.3 The ACUCOBOL-GT Plug-in and Acu4GL
- Position menu, demonstration program:
- 2.5 The Demonstration Program
- preparing a COBOL program:
- 6.1 Preparing and Compiling Your COBOL Program
- procedures:COBOL:
- 9.1.2 The WHERE Constraint
- procedures:Microsoft SQL Server:
- B.6.2 Acu4GL for Microsoft SQL Server: Stored Procedures
- procedures:Sybase.:
- E.7.2 Acu4GL for Sybase: Stored Procedures
- programs:and sql.acu:
- 2.4.2 To Call sql.acu From a Program
- programs:client, DBMaker:
- F.1.2 DBMaker Structure
- programs:COBOL, preparing and compiling:
- 6.1 Preparing and Compiling Your COBOL Program
- programs:DBMaker server:
- F.1.2 DBMaker Structure
- programs:demonstration.:
- 2.5 The Demonstration Program
- programs:inf_inst:
- A.1.2 Installing the Acu4GL for Informix Product
- programs:sample Informix:
- A.1.2 Installing the Acu4GL for Informix Product
Q
- query optimizer, Informix:
- A.7 Acu4GL for Informix: Common Questions and Answers
- A.4 Informix 7.2 and 7.3 Performance
- questions and answers:
- C.8 Acu4GL for Oracle: Common Questions and Answers
- A.7 Acu4GL for Informix: Common Questions and Answers
- D.7 Acu4GL for ODBC: Common Questions and Answers
- E.9 Acu4GL for Sybase: Common Questions and Answers
- F.7 Acu4GL for DBMaker: Common Questions and Answers
- B.8 Acu4GL for Microsoft SQL Server: Common Questions and Answers
R
- record definitions:
- 3.2.2 Defaults Used in XFD Files
- record locking:
- D.5.1 Acu4GL for ODBC: Record and Table Locking
- A4GL_COMMIT_COUNT
- E.7.1 Acu4GL for Sybase: Record and Table Locking
- F.5.1 Acu4GL for DBMaker: Record and Table Locking
- C.1 Oracle Concepts Overview
- record locking:COMMIT_COUNT=0:
- A4GL_COMMIT_COUNT
- C.1 Oracle Concepts Overview
- record locking:COMMIT_COUNT=-1:
- C.1 Oracle Concepts Overview
- A4GL_COMMIT_COUNT
- record locking:COMMIT_COUNT=n:
- C.1 Oracle Concepts Overview
- A4GL_COMMIT_COUNT
- Record menu, demonstration program:
- 2.5 The Demonstration Program
- records:forming COBOL:
- 1.5.3 Steps to Follow
- records:mapping:
- 3.2.1 Understanding How the Database Table Is Formed
- 1.5.2 Data Dictionaries and Mapping
- REDEFINES definition:
- 3.2.2 Defaults Used in XFD Files
- 4.13 WHEN Directive
- requests, passing I/O to interface:
- 1.5.3 Steps to Follow
- requirements, ODBC driver:
- D.5.3 Acu4GL for ODBC: Driver Requirements
- restrictions, ODBC:
- D.1.3 Restrictions
- restructuring data:
- 9.1.1 Guidelines
- retrieving errors:
- C.7.2 Acu4GL for Oracle: Retrieving Errors
- A.6.2 Acu4GL for Informix: Retrieving Errors
- F.6.2 Acu4GL for DBMaker: Retrieving Errors
- D.6.2 Acu4GL for ODBC: Retrieving Errors
- B.7.2 Acu4GL for Microsoft SQL Server: Retrieving Errors
- E.8.2 Acu4GL for Sybase: Retrieving Errors
- REWRITE method:
- E.1 Sybase Concepts Overview
- B.1 Microsoft SQL Server Concepts Overview
- routines, interface:
- 1.3.1 Interface Routines
- running SQL from the command line:
- 2.4.1 Running sql.acu From the Command Line
- running sql.acu:
- 2.4.2 To Call sql.acu From a Program
- running the demonstration program:
- 2.5 The Demonstration Program
- runtime errors:
- E.8.1 Acu4GL for Sybase: Runtime Errors
- B.7.1 Acu4GL for Microsoft SQL Server: Runtime Errors
- F.6.1 Acu4GL for DBMaker: Runtime Errors
- C.7.1 Acu4GL for Oracle: Runtime Errors
- D.6.1 Acu4GL for ODBC: Runtime Errors
- A.6.1 Acu4GL for Informix: Runtime Errors
- runtime module, ACUCOBOL-GT:
- 1.5 How Acu4GL Works
- runtime variables:
- 8.2 Runtime Configuration Variables
- runtime verification, demonstration program:
- 2.5 The Demonstration Program
- runtime:Acu4GL for Informix:
- A.1.2 Installing the Acu4GL for Informix Product
- runtime:Acu4GL for Oracle:
- C.2.3 Installing the Product
- runtime:Acu4GL for Sybase:
- E.3.2 Installation Steps on the UNIX Client
- runtime:linking Acu4GL for Informix:
- A.1.2 Installing the Acu4GL for Informix Product
- runtime:linking Acu4GL for Oracle:
- C.2.3 Installing the Product
- runtime:linking Acu4GL for Sybase:
- E.3.2 Installation Steps on the UNIX Client
S
- sample program, Acu4GL for Informix:
- A.1.2 Installing the Acu4GL for Informix Product
- SCO UNIX, relinking Oracle:
- C.2.3 Installing the Product
- search path, setting up for Acu4GL for Oracle:
- C.2.8 Acu4GL for Oracle: Setting Up the Search Path
- SECONDARY_TABLE directive:
- 4.10 SECONDARY_TABLE Directive
- security:
- E.1 Sybase Concepts Overview
- C.1 Oracle Concepts Overview
- B.1 Microsoft SQL Server Concepts Overview
- sequencing, data:
- 7.2 Default Behavior
- server program, DBMaker:
- F.1.2 DBMaker Structure
- servers:
- B.1 Microsoft SQL Server Concepts Overview
- E.1 Sybase Concepts Overview
- SETPOS:DBMaker:
- A_DBM_LOCK_METHOD
- SETPOS:ODBC:
- A_ODBC_LOCK_METHOD
- SETSTMTOPTION:DBMaker:
- A_DBM_LOCK_METHOD
- SETSTMTOPTION:ODBC:
- A_ODBC_LOCK_METHOD
- setting database-specific variables:
- 1.5.3 Steps to Follow
- setting files host:
- 1.5.3 Steps to Follow
- setting up:Acu4GL for DBMaker:
- F.2 Acu4GL for DBMaker Installation and Setup for Windows and UNIX
- setting up:Acu4GL for ODBC:
- D.2.1 Installation
- setting up:Acu4GL for Sybase:
- E.2.1 Sybase RDBMS Installation
- setting up:data sources, ODBC:
- D.2.3 Acu4GL for ODBC: Setting Up Data Sources
- setting up:search path for Oracle:
- C.2.8 Acu4GL for Oracle: Setting Up the Search Path
- setting up:user account for DBMaker:
- F.2.4 Acu4GL for DBMaker: Setting Up a User Account
- setting up:user accounts for Acu4GL for Microsoft SQL Server:
- B.2.3 Acu4GL for Microsoft SQL Server: Setting Up a User Account
- setting up:user accounts for Acu4GL for Oracle:
- C.2.5 Acu4GL for Oracle: Setting Up a User Account
- setting up:user accounts for Acu4GL for Sybase:
- E.4.1 Acu4GL for Sybase: Setting Up a User Account
- setting up:user environment for Acu4GL for Microsoft SQL Server:
- B.2.4 Acu4GL for Microsoft SQL Server: Setting Up the User Environment
- setting up:user environment for Acu4GL for ODBC:
- D.2.4 Acu4GL for ODBC: Setting Up the User Environment
- setting up:user environment for Acu4GL for Oracle:
- C.2.6 Acu4GL for Oracle: Setting Up the User Environment
- setting up:user environment for Acu4GL for Sybase:
- E.4.2 Acu4GL for Sybase: Setting Up the User Environment
- shared libraries:Acu4GL for Informix:
- A.1.2 Installing the Acu4GL for Informix Product
- shared libraries:Acu4GL for Oracle:
- C.2.3 Installing the Product
- shared libraries:Acu4GL for Sybase:
- E.3.2 Installation Steps on the UNIX Client
- single user architecture:
- F.1.2 DBMaker Structure
- single-tier architecture:
- D.1.4 ODBC Structure
- F.1.3 DBMaker and Acu4GL Architecture
- sources, data:designating host for ODBC:
- D.2.6 Acu4GL for ODBC: Designating the Host Data Source
- sources, data:ODBC:
- D.1.4 ODBC Structure
- sources, data:setting up for ODBC:
- D.2.3 Acu4GL for ODBC: Setting Up Data Sources
- SPACES, illegal COBOL data:
- 5.1 Illegal COBOL Data
- SQL errors:
- D.6.3 Acu4GL for ODBC: Native SQL Errors
- F.6.3 Acu4GL for DBMaker: Native SQL Errors
- SQL generation:
- 1.5 How Acu4GL Works
- SQL statements, building:
- 1.5.3 Steps to Follow
- sql.acu utility:
- 2.4 Using the sql.acu Program
- 2.4.2 To Call sql.acu From a Program
- starting the demonstration program:
- 2.5 The Demonstration Program
- statements, building SQL:
- 1.5.3 Steps to Follow
- stored procedures, Microsoft SQL Server:
- B.6.2 Acu4GL for Microsoft SQL Server: Stored Procedures
- stored procedures, Microsoft SQL Server:xxx_delete:
- B.6.2 Acu4GL for Microsoft SQL Server: Stored Procedures
- stored procedures, Microsoft SQL Server:xxx_insert:
- B.6.2 Acu4GL for Microsoft SQL Server: Stored Procedures
- stored procedures, Microsoft SQL Server:xxx_read:
- B.6.2 Acu4GL for Microsoft SQL Server: Stored Procedures
- stored procedures, Microsoft SQL Server:xxx_startnnn:
- B.6.2 Acu4GL for Microsoft SQL Server: Stored Procedures
- stored procedures, Microsoft SQL Server:xxx_update:
- B.6.2 Acu4GL for Microsoft SQL Server: Stored Procedures
- stored procedures, Sybase:
- E.3.5 Installation Steps on the UNIX Server Machine
- E.3.3 Installation Steps on the UNIX or Windows NT Server
- E.7.2 Acu4GL for Sybase: Stored Procedures
- E.3.6 Installation Steps on a Windows NT Server Machine - Windows Client
- stored procedures: Microsoft SQL Server:
- B.2.2 Installing the Acu4GL for Microsoft SQL Server Product on a Client Machine
- structure, DBMaker:
- F.1.2 DBMaker Structure
- structure, ODBC:
- D.1.4 ODBC Structure
- summary:Acu4GL:
- 1.5.4 Summary
- summary:dictionary fields:
- 3.2.3 Summary of Dictionary Fields
- support, technical:
- 2.2 Technical Support
- supported features:
- A.5.1 Acu4GL for Informix: Supported Features
- C.6.1 Acu4GL for Oracle: Supported Features
- switching file systems, Informix:
- A.5 Acu4GL for Informix: Technical Information
- Sybase variables:
- A_SYB_DEFAULT_CONNECTION
- A_SYB_UNLOCK_ON_EXECUTE
- A_SYB_NO_COUNT_CHECK
- A_SYB_NO_RECORD_LOCKS
- A_SYB_TRANSLATE_TO_ANSI
- A_SYB_PASSWD
- A_SYB_ROWCOUNT
- A_SYB_NO_DBCLOSE
- A_SYB_ADD_IDENTITY
- A_SYB_EXTRA_PROC
- A_SYB_ADD_TIMESTAMP
- A_SYB_FAST_ACCESS
- A_SYB_NO_TABLE_LOCKS
- A_SYB_FORCED_INDEX
- A_SYB_USE_DROPDOWN_QUERIES
- A_SYB_MAX_COLUMNS
- A_SYB_NO_DBID
- A_SYB_NATIVE_LOCK_TIMEOUT
- A_SYB_VISION_LOCKS_FILE
- E.6 Acu4GL for Sybase Configuration File Variables
- A_SYB_CURSOR_OPTION_1
A_SYB_CURSOR_OPTION_2
A_SYB_CURSOR_OPTION_3
- A_SYB_DATABASE
- A_SYB_SKIP_ALTERNATE_KEYS
- A_SYB_SELECT_KEY_ONLY
- A_SYB_NO_23_ON_START
- A_SYB_LOCK_DB
- A_SYB_LOGIN
- A_SYB_PACKETSIZE
- A_SYB_MAX_CHARACTERS
- Sybase, Acu4GL:concepts:
- E.1 Sybase Concepts Overview
- Sybase, Acu4GL:configuration variables:
- E.6 Acu4GL for Sybase Configuration File Variables
- Sybase, Acu4GL:creating a new runtime:
- E.3.2 Installation Steps on the UNIX Client
- Sybase, Acu4GL:creating stored procedures:
- E.3.5 Installation Steps on the UNIX Server Machine
- Sybase, Acu4GL:designating host file system:
- E.4.3 Acu4GL for Sybase: Designating the Host File System
- Sybase, Acu4GL:FAQs:
- E.9 Acu4GL for Sybase: Common Questions and Answers
- Sybase, Acu4GL:getting started:
- E.2 Getting Started with Acu4GL for Sybase
- Sybase, Acu4GL:information:
- E.1 Sybase Concepts Overview
- Sybase, Acu4GL:installation and setup:
- E.2.1 Sybase RDBMS Installation
- Sybase, Acu4GL:installing stored procedures:
- E.3.5 Installation Steps on the UNIX Server Machine
- E.3.6 Installation Steps on a Windows NT Server Machine - Windows Client
- Sybase, Acu4GL:limits and ranges:
- E.7.3 Acu4GL for Sybase: Limits and Ranges
- Sybase, Acu4GL:linking runtime:
- E.3.2 Installation Steps on the UNIX Client
- Sybase, Acu4GL:makefiles:
- E.3.2 Installation Steps on the UNIX Client
- Sybase, Acu4GL:questions and answers:
- E.9 Acu4GL for Sybase: Common Questions and Answers
- Sybase, Acu4GL:record and table locking:
- E.7.1 Acu4GL for Sybase: Record and Table Locking
- Sybase, Acu4GL:retrieving errors:
- E.8.2 Acu4GL for Sybase: Retrieving Errors
- Sybase, Acu4GL:REWRITE method:
- E.1 Sybase Concepts Overview
- Sybase, Acu4GL:runtime errors:
- E.8.1 Acu4GL for Sybase: Runtime Errors
- Sybase, Acu4GL:security:
- E.1 Sybase Concepts Overview
- Sybase, Acu4GL:servers:
- E.1 Sybase Concepts Overview
- Sybase, Acu4GL:setting up a user account:
- E.4.1 Acu4GL for Sybase: Setting Up a User Account
- Sybase, Acu4GL:setting up the user environment:
- E.4.2 Acu4GL for Sybase: Setting Up the User Environment
- Sybase, Acu4GL:shared libraries:
- E.3.2 Installation Steps on the UNIX Client
- Sybase, Acu4GL:stored procedures:
- E.7.2 Acu4GL for Sybase: Stored Procedures
- Sybase, Acu4GL:table ownership:
- E.1 Sybase Concepts Overview
- Sybase, Acu4GL:technical specifications:
- E.7 Acu4GL for Sybase: Technical Information
- Sybase, Acu4GL:troubleshooting:
- E.8 Acu4GL for Sybase: Troubleshooting
- Sybase, Acu4GL:upgrading stored procedures:
- E.3.5 Installation Steps on the UNIX Server Machine
- E.3.3 Installation Steps on the UNIX or Windows NT Server
- E.3.6 Installation Steps on a Windows NT Server Machine - Windows Client
- syntax:directives:
- 4.2 Syntax
- system parameters, Oracle:
- C.2.4 Acu4GL for Oracle: Checking System Parameters
- systems, host file:
- C.2.7 Acu4GL for Oracle: Designating the Host File System
- F.2.5 Acu4GL for DBMaker: Designating the Host File System
- E.4.3 Acu4GL for Sybase: Designating the Host File System
- B.2.5 Acu4GL for Microsoft SQL Server: Designating the Host File System
- D.2.5 Acu4GL for ODBC: Designating the Host File System
- systems, Informix file:
- A.5 Acu4GL for Informix: Technical Information
T
- table locking:
- B.6.1 Acu4GL for Microsoft SQL Server: Table Locking
- E.7.1 Acu4GL for Sybase: Record and Table Locking
- D.5.1 Acu4GL for ODBC: Record and Table Locking
- F.5.1 Acu4GL for DBMaker: Record and Table Locking
- table ownership:
- E.1 Sybase Concepts Overview
- C.1 Oracle Concepts Overview
- B.1 Microsoft SQL Server Concepts Overview
- tables:and multiple indexes:
- 9.1.1 Guidelines
- tables:database formation:
- 3.2.1 Understanding How the Database Table Is Formed
- tables:Microsoft SQL Server database:
- B.5 Acu4GL for Microsoft SQL Server: Using the Database Table
- tables:Oracle database:
- C.5 Acu4GL for Oracle: Using the Database Table
- technical support:
- 2.2 Technical Support
- technical tips:
- F.5 Acu4GL for DBMaker: Technical Information
- E.7 Acu4GL for Sybase: Technical Information
- B.6 Acu4GL for Microsoft SQL Server: Technical Information
- A.5 Acu4GL for Informix: Technical Information
- C.6 Acu4GL for Oracle: Technical Information
- D.5 Acu4GL for ODBC: Technical Information
- test, ODBC driver:
- D.5.3 Acu4GL for ODBC: Driver Requirements
- TEXT fields:
- 5.1 Illegal COBOL Data
- 7.3.1 How Do I Match Existing Text Fields?
- transactions:
- 9.1.1 Guidelines
- C.1 Oracle Concepts Overview
- C.6.1 Acu4GL for Oracle: Supported Features
- C.2.9 Acu4GL for Oracle: Handling Transactions
- translation, COBOL I/O:
- 1.5 How Acu4GL Works
- translation, filenames:
- A.2 Acu4GL for Informix and Filename Translation
- E.5 Acu4GL for Sybase and Filename Translation
- F.3 Acu4GL for DBMaker and Filename Translation
- B.3 Acu4GL for Microsoft SQL Server and Filename Translation
- D.3 Acu4GL for ODBC and Filename Translation
- C.3 Acu4GL for Oracle and Filename Translation
- troubleshooting:compile errors:
- 9.2.1 Compile-time Errors
- troubleshooting:compile warnings:
- 9.2.2 Compile-time Warnings
- troubleshooting:data searches:
- 9.1.1 Guidelines
- troubleshooting:database interaction with COBOL:
- 9.1.1 Guidelines
- troubleshooting:DBMaker:
- F.5 Acu4GL for DBMaker: Technical Information
- F.6 Acu4GL for DBMaker: Troubleshooting
- troubleshooting:file input and output:
- 9.1.1 Guidelines
- troubleshooting:guidelines:
- 9.1.1 Guidelines
- troubleshooting:Informix:
- A.5 Acu4GL for Informix: Technical Information
- A.6 Acu4GL for Informix: Troubleshooting
- troubleshooting:Microsoft SQL Server:
- B.6 Acu4GL for Microsoft SQL Server: Technical Information
- B.7 Acu4GL for Microsoft SQL Server: Troubleshooting
- troubleshooting:ODBC:
- D.6 Acu4GL for ODBC: Troubleshooting
- D.5 Acu4GL for ODBC: Technical Information
- troubleshooting:Oracle:
- C.6 Acu4GL for Oracle: Technical Information
- C.7 Acu4GL for Oracle: Troubleshooting
- troubleshooting:overview:
- 9.1 Performance Issues
- troubleshooting:planning ahead:
- 9.1.1 Guidelines
- troubleshooting:restructuring data:
- 9.1.1 Guidelines
- troubleshooting:runtime errors:
A.6.1 Acu4GL for Informix: Runtime Errors
- B.7.1 Acu4GL for Microsoft SQL Server: Runtime Errors
- C.7.1 Acu4GL for Oracle: Runtime Errors
- E.8.1 Acu4GL for Sybase: Runtime Errors
- F.6.1 Acu4GL for DBMaker: Runtime Errors
- troubleshooting:SQL errors:
- D.6.3 Acu4GL for ODBC: Native SQL Errors
- F.6.3 Acu4GL for DBMaker: Native SQL Errors
- troubleshooting:Sybase:
- E.8 Acu4GL for Sybase: Troubleshooting
- E.7 Acu4GL for Sybase: Technical Information
- troubleshooting:tables and multiple indexes:
- 9.1.1 Guidelines
- troubleshooting:transactions:
- 9.1.1 Guidelines
- troubleshooting:Vision files:
- 9.1.1 Guidelines
- D.5.4 Acu4GL for ODBC: Data Type Mapping
U
- underscores in filenames:
- A.2 Acu4GL for Informix and Filename Translation
- B.3 Acu4GL for Microsoft SQL Server and Filename Translation
- E.5 Acu4GL for Sybase and Filename Translation
- D.3 Acu4GL for ODBC and Filename Translation
- F.3 Acu4GL for DBMaker and Filename Translation
- C.3 Acu4GL for Oracle and Filename Translation
- unsupported data types, Informix:
- A.5.2 Acu4GL for Informix: Limits and Ranges
- UPDATECOLUMN:DBMaker:
- A_DBM_LOCK_METHOD
- UPDATECOLUMN:ODBC:
- A_ODBC_LOCK_METHOD
- upgrading databases:
- 9.1.1 Guidelines
- upgrading stored procedures, Sybase:
- E.3.5 Installation Steps on the UNIX Server Machine
- E.3.6 Installation Steps on a Windows NT Server Machine - Windows Client
- E.3.3 Installation Steps on the UNIX or Windows NT Server
- uppercase letters in filenames:
- C.3 Acu4GL for Oracle and Filename Translation
- USAGE DISPLAY numbers, illegal COBOL data:
- 5.1 Illegal COBOL Data
- USE GROUP directive:
- 4.3 ALPHA Directive
- 4.11 USE GROUP Directive
- 3.2.2 Defaults Used in XFD Files
- 3.2.1 Understanding How the Database Table Is Formed
- USE_INVALID_CURSOR_LOGIC variable:
- USE_INVALID_CURSOR_LOGIC
- user accounts:
- B.2.3 Acu4GL for Microsoft SQL Server: Setting Up a User Account
- C.2.5 Acu4GL for Oracle: Setting Up a User Account
- F.2.4 Acu4GL for DBMaker: Setting Up a User Account
- E.4.1 Acu4GL for Sybase: Setting Up a User Account
- user environment:
- D.2.4 Acu4GL for ODBC: Setting Up the User Environment
- E.4.2 Acu4GL for Sybase: Setting Up the User Environment
- B.2.4 Acu4GL for Microsoft SQL Server: Setting Up the User Environment
- C.2.6 Acu4GL for Oracle: Setting Up the User Environment
- USER_PATH variable:
- USER_PATH
- utilities, sql.acu:
- 2.4 Using the sql.acu Program
V
- VAR_LENGTH directive:
- 4.12 VAR_LENGTH Directive
- 4.4 BINARY Directive
- variables, configuration.:
- 8.2 Runtime Configuration Variables
- variables, external:
- 9.1.2 The WHERE Constraint
- VAX and RMS file systems:
- 1.3 Accessing Data
- verifying the runtime, demonstration program:
- 2.5 The Demonstration Program
- Vision file systems:
- 1.3 Accessing Data
- Vision files:
- 9.1.1 Guidelines
W
- warnings:compiler:
- 9.2.2 Compile-time Warnings
- warnings:database upgrades:
- 9.1.1 Guidelines
- Web plug-in, ACUCOBOL-GT:
- 1.3.3 The ACUCOBOL-GT Plug-in and Acu4GL
- WHEN directive:
- 3.2.2 Defaults Used in XFD Files
- 4.13 WHEN Directive
- WHERE constraint:
- 9.1.2 The WHERE Constraint
- working with COBOL:
- 6.1 Preparing and Compiling Your COBOL Program
X
- XFD_DIRECTORY variable:
- XFD_DIRECTORY
- XFD_MAP variable:
- 3.2.6 Naming the XFD
- XFD_MAP
- XFD_MAP_RESETS variable:
- 3.2.6 Naming the XFD
- XFD_MAP_RESETS
- XFDs:
- 1.3.2 Data Dictionaries and Acu4GL
- 3.2.6 Naming the XFD
- xxx_delete procedure:
- B.6.2 Acu4GL for Microsoft SQL Server: Stored Procedures
- E.7.2 Acu4GL for Sybase: Stored Procedures
- xxx_insert procedure:
- B.6.2 Acu4GL for Microsoft SQL Server: Stored Procedures
- E.7.2 Acu4GL for Sybase: Stored Procedures
- xxx_read procedure:
- E.7.2 Acu4GL for Sybase: Stored Procedures
- B.6.2 Acu4GL for Microsoft SQL Server: Stored Procedures
- xxx_startnnn procedure:
- E.7.2 Acu4GL for Sybase: Stored Procedures
- B.6.2 Acu4GL for Microsoft SQL Server: Stored Procedures
- xxx_update procedure:
- E.7.2 Acu4GL for Sybase: Stored Procedures
- B.6.2 Acu4GL for Microsoft SQL Server: Stored Procedures
Z
- -Zx option:
- 4.8 NAME Directive