Building Applications

The following sample use case scenarios show typical SQL compiler directives you might set for HCOSS applications:

Type of Program	Scenario	SQL Compiler Directive Options
COBOL	Connect to the database for full SQL syntax checking during compilation	SQL(DBMAN=ODBC, TARGETDB=MSSQLSERVER, DB=`databaseName`, [PASS=`userid.password`, ] BEHAVIOR=OPTIMIZED, DIALECT=MAINFRAME)¹
COBOL	Do not connect to the database during compilation	SQL(DBMAN=ODBC, TARGETDB=MSSQLSERVER, BEHAVIOR=OPTIMIZED, DIALECT=MAINFRAME, NOCHECK)¹

In the IDE, you compile applications by building the projects that contain them. When you build an HCOSS application, you must first set appropriate SQL compiler directive options, and in most cases, establish a connection to your SQL Server database.

In addition to the standard SQL compiler directive options, HCOSS includes these specific options to handle SQL compatibility between DB2 and SQL Server:

DATE
DIALECT (required)
QUALIFIER
TIME

At a minimum, edit your project's SQL properties to set the following compiler directive options for the OpenESQL ESQL preprocessor to ensure that the build process generates the appropriate DBRMs and converts DB2 SQL into SQL Server SQL where necessary.

DBMAN - set this to ODBC.
TARGETDB - set this to a value of MSSQLSERVER.
DB - set this value to your SQL Server data source connection name
PASS - if your data source connection requires that you provide a user ID and password to connect, provide a user ID and password as follows:
userID.password
DIALECT - set this to a value of MAINFRAME.
DETECTDATE
INIT

Before compiling, unless you have specified the SQL(NOCHECK) directive, you must be connected to the database specified by the DB directive via an ODBC connection.