Debug the SPCall Program and SP1 Stored Procedure - Single-project Literal

Associate the JCLSPSL Region with the SPCall Project

1. In the Visual Studio Server Explorer, expand Micro Focus Servers > localhost.
2. Right-click JCLSPSL; then select Associate With Project > SPCall from the context menu.

Start the JCLSPSL Region

1. On the Server Explorer list, right-click JCLSPSL; then select Start from the context menu.
2. If you are using SQL Server authentication, check Server is secured; then provide your Username and Password.

   If you are using Windows authentication, skip this step.

3. Click OK.

Configure SQL Server Debug Properties

1. In Visual Studio, click View > SQL Server Object Explorer.
2. Expand SQL Server.
3. In the list of SQL Server instances, expand your SQL Server instance.
   Note: If your SQL Server instance is not listed:

   1. On the SQL Server Object Explorer, right-click SQL Server; then select Add SQL Server from the context menu.
   2. On the Connect to Server dialog box, type . (dot) into the Server name field; then click Connect.
   3. Repeat this step.
4. Expand Databases; then check the resulting list to ensure that SQLCLR_Test is listed.
5. Right-click your SQL Server instance; then select Application Debugging to turn it on. When Application Debugging is on, a check mark appears to its left.
6. Right-click your SQL Server instance again; then select Allow SQL/CLR Debugging to turn it on.
7. If prompted, click Yes.

Set Breakpoints

Set a breakpoint in SPCall and in SP1 in preparation for debugging the application.

1. In the Solution Explorer, double-click SPCall.cbl to open it in the COBOL editor.
2. In the COBOL editor, scroll to:

   exec sql
        call "SP1" (:countval INOUT)
   end-exec

3. In the leftmost column on the exec sql line, click to set a breakpoint.
4. From the Solution Explorer, open SP1.cbl.
5. Scroll to:

   call "A" using by reference lscountval

   and set a breakpoint.

Debug the Program and Stored Procedure

In this section, you use Enterprise Developer to debug the native COBOL program and the SQL CLR stored procedure.

1. From the Visual Studio main menu, click DEBUG > Start Debugging. This builds the project and puts the debugger in a wait state.
2. In the Solution Explorer, right-click the SPCall.jcl file; then select Submit JCL from the context menu.

   The JCL script calls the SPCall program and stops on the breakpoint you set in the SPCall.cbl file.

3. Click DEBUG > Attach to Process.
4. On the Attach to Process dialog box, click Select.
5. On the Select Code Type dialog box, click Debug these code types; then check the following boxes:
   • .NET (v4.5, v4.0)
   • T-SQL
6. Click OK.
7. On the Attach to Process dialog box, check Show processes from all users.
8. On the Available Processes list, select the sqlservr.exe entry that has the NT Service\MSSQLServer User Name.
9. Click Attach.
   Note: If a prompt appears, click Attach to clear it.
10. Click DEBUG > Step Into.

    The debugger steps into the managed SQL CLR stored procedure code. This demonstrates debugging in a mixed native/.NET environment.

11. To continue debugging, press F10; when the debugger reaches another breakpoint, press F10 again.
12. Press F5 to run the program to its completion.
13. Click Stop Debugging to stop the Debugger.

View JCL Execution Results

1. In the Enterprise Developer Output window, select Enterprise Server from the Show output from drop-down list.
2. CTRL-click the job output link.

   This opens the JCLSPSL tab, showing the Enterprise Server Job Output window.

3. Click SYSOUT.

   This shows the output from the SQL CLR Stored Procedure.

4. Close the JCLSPSL tab.

Stop the JCLSPSL Enterprise Server Region

• On the Server Explorer, right-click JCLSPSL; then select Stop from the context menu.