Debug the Program and Stored Procedure - SQLCLRTutorialSPGroupCall

Associate the JCLSPG Region with the SPCall Project

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

Start the JCLSPG Region

1. On the Server Explorer list, right-click JCLSPG; 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.

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. In the Solution Explorer, double-click SPCall.cbl to open in the COBOL editor.
2. In the COBOL Editor, scroll to:

   exec sql
        call "GETHIRE" (:EMP-PARM, :SQLXCODE)
   end-exec

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

   MOVE IN-EMP-TXT   TO DCLEMP

   and set a breakpoint.
6. Click Debug > Start Debugging. This builds the project and puts the debugger in a wait state.
7. In 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 at the beginning of the program. Press F5 to continue execution up to the breakpoint you set in the SPCall.cbl file.

8. Click Debug > Attach to Process.
9. On the Attach to Process dialog box, click Select.
10. On the Select Code Type dialog box, click Debug these code types; then check the following boxes:
    • Managed (.NET 4.x)
    • T-SQL
11. Click OK.
12. On the Attach to Process dialog box, check Show processes for all users.
13. On the Available Processes list, select the sqlservr.exe entry that has the NT Service\MSSQLServer User Name. If you are using a SQL Server named instance, the User Name to select will have the format NT Service\MSSQL$<instanceName>.

    .

14. Click Attach.
    Note: If a prompt appears, click Attach to clear it.
15. Click Debug > Step Into.

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

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