Micro Focus Enterprise Developer 3.0 for Visual Studio 2017 > Programming > Data Access > Database Access > OpenESQL > SQL Server COBOL Stored Procedures > Post-deployment Script Requirements

Post-deployment Script Requirements

Restriction: This topic applies only to Visual Studio projects that include a stored procedure program called by Java, and also includes a stored procedure definition file that specifies the DATETIME2 parameter.

Java routines cannot call a SQL COBOL stored procedure that contains a TIMESTAMP parameter. Therefore, TIMESTAMP parameters in stored procedures that are called by Java routines must be changed to DATETIME2 to be compatible with Java calls. The Extract Schema tool converts TIMESTAMP to DATETIME2 automatically. However, Microsoft does not support DATETIME2 parameter types under .NET. During compilation and deployment with Enterprise Developer, DATETIME2 is changed to DATETIME. In this scenario, you must provide a post-deployment script that changes the DATETIME parameter back to DATETIME2 to ensure compatibility with Java. To do this:

Create the post-deployment script and add it to the project manually. See To add a post-deployment script for instructions on creating the script and adding it to the project.
Provide the SPD and COBOL wrapper program as objects in your Visual Studio COBOL project. See To create a stored procedure definition (SPD) file for further information. Once you have defined your stored procedure, the skeleton COBOL file is saved as the COBOL wrapper program when you save your project.
Enable automatic generation of code in the post-deployment script by editing the SPD file to add the following code to the top of the file:
```
POSTDEPLOY=ScriptPath\Name NAMESPACE=DefaultNameSpace;
```
Where ScriptPath\Name is the full path and filename of the post-deployment script file. If the path or filename contains spaces, enclose the entire path and filename in quotes. DefaultNameSpace is the default namespace used in the project, and which is used by the generated ALTER statement in the post-deployment script file. You can see the default namespace on the Application tab of your project properties.

Once all of this is in place, any DATETIME2 parameter that you code into the SPD file automatically generates the appropriate post-deployment code in the post-deployment script file.