The following OpenESQL use case scenarios show the appropriate SQL compiler directive options to set for each to ensure its ultimate success:
| Type of Program | Scenario | SQL Compiler Directive Options |
|---|---|---|
| COBOL | Maximize performance and talk to an SQL Server data store via a .NET data provider | SQL(DBMAN=ADO, TARGETDB=MSSQLSERVER, BEHAVIOR=OPTIMIZED) |
| COBOL | ANSI compliant, and talk to an SQL Server data store via an ODBC driver | SQL(DBMAN=ODBC, TARGETDB=MSSQLSERVER, BEHAVIOR=ANSI) |
| COBOL or PL/I | Maximize performance, not worry about mainframe compatibility, and talk to an Oracle data store via an ODBC driver | SQL(DBMAN=ODBC, TARGETDB=ORACLE, BEHAVIOR=OPTIMIZED) |
| COBOL | Mimic Oracle Pro*COBOL functionality for SQL cursors, and talk to an Oracle data store via .NET data provider | SQL(DBMAN=ADO, TARGETDB=ORACLE, BEHAVIOR=ANSI) |