Micro Focus Enterprise Developer 3.0 for Visual Studio 2013 > Welcome > Product Information > Known Issues and Restrictions > Mainframe Programming and Management > HCO for SQL Server (HCOSS)

HCO for SQL Server (HCOSS)

HCOSS applications do not support dynamic SQL using the SQL Descriptor Area (SQLDA) when the application calls a SQL CLR stored procedure.
Under Enterprise Developer, no project templates are available for HCOSS applications at this time. For information on creating COBOL projects for HCOSS applications, see the tutorials in the %PUBLIC%\Documents\Micro Focus\Enterprise Developer\Samples\Mainframe\sql\hcoss directory. You can also view the samples in the Mainframe Samples Browser. See To start the Samples Browser for more information.
HCOSS SQL Server databases created with an Enterprise Developer version of 2.2 Update 2 HotFix 3 or earlier might be missing HCOSS-provided scalar functions. To ensure your scalar functions are up to date, run the InstallDigitsFunction.sql script against each of your HCOSS databases. The script is located by default in the %ALLUSERSPROFILE%\Micro Focus\Enterprise Developer\hcoss directory. The user running the script must have read, update, and create permissions for the database SYSIBM and dbo schemas.
Starting with Enterprise DeveloperEnterprise Developer 2.2 Update 1, HCOSS is not backwardly compatible with HCOSS databases created in earlier versions, and that also fit the following description:
- Use a 64-bit Enterprise Server
- SQL Server stored procedures called from an ODBC application
- Use DBRMLIB
To restore compatibility, recompile just the programs that call stored procedures. This resolves runtime error messages and greatly improves the performance of the calls to stored procedures.

For example, if you have a 64-bit HCOSS application that uses SQL compiler directive options DBMAN=ODBC and DBRMLIB, recompile programs that call stored procedures from COBOL or PL/I code.
Because z/OS DB2 supports date/time arithmetic using regular addition and subtraction operators but SQL Server requires the use of built-in functions to achieve the same results, you might be required to edit DB2 conversion functions for date/time special registers and labeled durations to provide clarification:
Remove parentheses

Change:
```
(CURRENT DATE) - (other_column) 
```
To:
```
CURRENT_DATE - other_column 
```
Add a DATE expression

Change:
```
column1 - column2 
```
To:
```
DATE(column1) - DATE(column2)
```
These rewritten expressions are still valid mainframe SQL, ensuring that portability is not sacrificed.