SQL Code Generation Options

Before you begin compiling, testing, and executing your HCOSS code, consider what you want HCOSS to do for you.

To convert the mainframe SQL in my programs such that it works with SQL Server: Set the DIALECT SQL compiler directive option to MAINFRAME to convert all SQL, or MIXED to convert selected EXEC SQL statements in the code. To fully enable compile-time checking of converted SQL statements using SQL Server, set the DB, PASS and QUALIFIER directives along with DIALECT=MAINFRAME or DIALECT=MIXED. For additional information, see the DIALECT Statement Prefixes and the Application Progression from DB2 to SQL Server topics.
Only to embed SQL into the generated code: To have HCOSS simply embed SQL into the generated code, no compiler directive options are required. This is the default behavior.

The following table provides a quick reference to the SQL compiler directive options that affect code generation. For complete information on each, see the appropriate Reference topic.

SQL Compiler Directive Option	Generation Specifics	Advantages
None (default)	SQL remains embedded in object code	Simplicity
DIALECT¹	Converts DB2 SQL statements that are not compatible with SQL Server into equivalent T-SQL statements in most cases.	You do not need to convert DB2 statements to T-SQL. You can change the default schema when a program is bound, or in some cases, change the default schema at compile time using the QUALIFIER SQL compiler directive option.
¹ For additional information, see also the SQL Statement Prefixes for DIALECT Directive and the Building Applications topics.