Space announcement This documentation space provides the same content as before, but the organization of the content has changed. The content is now organized based on logical branches instead of legacy book titles. We hope that the new structure will help you quickly find the content that you need.

Preparing a Program for Execution in Code Debug CICS C

Related topicS

Quick Reference

Overview

Installation-and-Configuration-Guide

Viewing Source

It is possible to debug a program without any preparation other than entering XPED and your program name. You work at the machine instruction level, set breakpoints and examine program storage using offsets. This process is called sourceless debugging. Sourceless debugging is valuable when working with programs that can’t be recompiled, such as vendor packages or production versions of programs.

For examples of sourceless debugging, see to Debugging Applications Without Source Code.

The typical method of debugging programs, however, is to use Code debug’s source-level support for C.

To take advantage of this support, you must run your C programs through the C language processor, which provides you with the following functionality during a debugging session:

  • Set one or more breakpoints to stop execution at any statement. Breakpoints may be:

–Unconditional: Halts program execution at the selected statement.

–Conditional: Halts program execution only if the specified condition is met.

  • Examine program storage by data name. C language data names are case-sensitive.
  • Select data fields for viewing during program execution.
  • Resume execution at any statement within the current function.
  • Change the execution point by statement number.
  • Examine the statement-level trace during or after execution.

Important

Certain C statements—such as macro invocations—may compile without generating any executable code. If you use the Source Listing screen (2.L) to set a breakpoint on a statement containing one of these verbs, the breakpoint will be placed on the actual executable line. If a conditional breakpoint already exists on that line, Code Debug will disallow the newer breakpoint and issue an error message.

Language processing lets you work with the code in the way you are accustomed to seeing it: at the source level. The next section discusses the BMC language processor and how to get source-level support.

This section provides information about the following topics:

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*