Having successfully compiled, linked and attempted to execute your Foundation Classes program you may need to debug it.
There are three options available to help debug a CICS® Foundation Classes program:
A symbolic debugger allows you to step through the source of your CICS Foundation Classes program. Debug Tool, a component of CODE/370, is shipped as a feature with IBM® C/C++ for OS/390®.
To debug a CICS Foundation Classes program with a symbolic debugger, you need to compile the program with a flag that adds debugging information to your executable. For CICS Transaction Server for z/OS®, this is TEST(ALL).
For more information see Debug Tool User’s Guide and Reference.
The CICS Foundation Classes can be configured to write a trace file for debugging/service purposes.
In CICS Transaction Server for z/OS, exception trace is always active.
The CETR transaction controls the auxilliary and internal traces for all CICS programs including those developed using the C++ classes.
For the EXEC CICS API, there is a CICS facility called the Execution Diagnostic Facility (EDF) that allows you to step through your CICS program stopping at each EXEC CICS call. This does not make much sense from the CICS Foundation Classes because the display screen shows the procedural EXEC CICS call interface rather than the CICS Foundation Class type interface. However, this may be of use to programmers familiar with the EXEC CICS interface.
To enable EDF, use the pre-processor macro ICC_EDF - this can be done in your source code before including the file ICCMAIN as follows:
#define ICC_EDF //switch EDF on
#include "iccmain.hpp"
Alternatively use the appropriate flag on your compiler CPARM to declare ICC_EDF.
For more information about using EDF see "Execution diagnostic facility (EDF)" in CICS Application Programming Guide.
[[ Contents Previous Page | Next Page Index ]]