Debugging techniques in CL400

Debugging is an essential process in software development, and it's no different for CL400 programming. Fortunately, CL400 provides several tools and techniques to help you debug your programs effectively. Here are some of the most commonly used debugging techniques in CL400:

• Interactive Debuggers:

CL400 provides an interactive debugger called STRDBG (Start Debug). STRDBG allows you to step through your program one statement at a time, set breakpoints, and examine the values of variables and registers. Here's an example of how to use STRDBG:

In this example, we have started the interactive debugger for the MYPROGRAM program and allowed updates to the production library.

Once the debugger is started, you can use the following commands to control the execution of the program:

• F6 - Step over: Executes the current statement and stops at the next statement.

• F5 - Step into: Executes the current statement and stops at the first statement of any subroutines or functions called by that statement.

• F12 - Cancel: Cancels the debugging session and returns control to the command line.

• F14 - Set breakpoint: Sets a breakpoint at the current statement.

• Tracing Tools:

CL400 also provides tracing tools that allow you to trace the execution of your program and identify potential issues. The most commonly used tracing tool in CL400 is the TRCJOB (Trace Job) command. TRCJOB allows you to trace the system and user-defined messages sent to your job, as well as any program calls made by your job. Here's an example of how to use TRCJOB:

In this example, we have started tracing for the current job and redirected the output to the job log.

Once tracing is started, you can use the following commands to control the tracing:

• ENDTRC - Ends the tracing session.
• TRCOFF - Turns tracing off temporarily.
• TRCON - Turns tracing back on after it has been turned off.

Here's an example of how to use TRCJOB to trace a specific program:

In this example, we have started tracing for the MYPROGRAM program in the MYJOB job and redirected the output to the job log.

By using these tools and techniques, you can effectively debug your CL400 programs and identify any issues that may be present.