Tracing and Debugging Environment Variables

This topic lists environment variables relate to the tracing and debugging functionality.

CCITRACE

Part of the process to enable CCI tracing is to specify the degree of information that will be traced, which can be done by setting the CCITRACE environment variable as follows:

Syntax

CCITRACE=filename [options]

Parameters

• filename The name of the log file you want the trace output to go to. If you do not specify this parameter, the log file ccitrace.log is created in the current directory with all options set to their default states.
• options Any, or all, of the following:

/F or -F	logs the details of CCI API calls to the trace file. The default is OFF, unless a filename any other trace option is specified, in which case it is always ON.
/P or -P	logs the details of protocol-level calls to the trace file. The default is OFF. If this flag is OFF, then only the details of the CCI user-level API will be traced. If this flag is ON, the level of function tracing may be greatly increased.
/D or -D	logs the contents of all buffers passed to and from the CCI functions. The default is OFF. Data tracing may not be allowed if the application has been coded to prohibit data tracing for security reasons.

So to create a CCI trace file with the default name of ccitrc1.trc (with matching ccitrc1.idx file) which traces CCI API function flow, along with the underlying protocol function flow, but with no tracing of the user data passed to these calls, the value of the CCITRACE environment variable would be /P.

The CCI.INI file can also be used to control trace options, but any values specified by the CCITRACE environment variable will take precedence.

COBANIMOPT

Restriction: This environment variable applies to UNIX environments only.

Specifies additional directives to be used by Character Animator.

Syntax

COBANIMOPT=directive-list
export COBANIMOPT

Parameters

• directive-list A directive, or list of directives. Must not be a filename.

Comments

When you invoke Character Animator, it first reads the directives you have specified in COBANIMOPT and then uses any directives you specify in the command line (which might override some of the directives you set in COBANIMOPT).

Example

COBANIMOPT="MIXEDLANGDEBUG MULTITHREAD"
export COBANIMOPT

COBANIMSRV

Restriction: This environment variable applies to UNIX environments only.

Identifies which COBOL program a waiting Character Animator process should attach to.

Syntax

COBANIMSRV=progid
export COBANIMSRV

Parameters

• progid An identifier that is used to identify the program to which Character Animator will attach.

Comments

This environment variable is particularly useful for starting cross-session debugging.

Example

In one console session:

export COBANIMSRV=myid

myid is now a unique identifier that you can use to match Character Animator to a program. Type the command to start Character Animator:

cobanimsrv

The Character Animator waits for a COBOL program to start that has a matching identifier. In another console session:

export COBANIMSRV=myid
cobrun prog1.int

When prog1.int starts, the unique identifier myid matches that of Character Animator; therefore, Character Animator attaches to this process. In console session 1, the Character Animator main screen is displayed and the cursor placed on the first line of prog1.int.

COBIDY

Restriction: This environment variable applies to UNIX environments only.

Specifies the directory that Animator is to search for the information (.idy) file for the program being animated if it is not found in the same directory as the intermediate code (.int) file. Animator can update the information file to record information held between sessions.

Syntax

COBIDY=pathname
export COBIDY

Parameters

• pathname A list of search directories, each item separated by a colon.

CODEWATCH_SRCPATH

The location of source files for the debugger to use if none are found in directories specified when invoking CodeWatch

Values

• A list of search directories, each item separated by a semicolon (Windows) or colon (UNIX).

CODEWATCH_STBPATH

The location of STB files for the debugger to use if none are found in directories specified when invoking CodeWatch.

Values

• A list of search directories, each item separated by a semicolon (Windows) or colon (UNIX).

DBG_MVSPSKEL

The skeleton JCL for debugging.

ES_DDBG_PORT_RANGE

A range of ports to use for dynamic debugging.

You specify a range of port numbers using either a hyphen or a comma.

If you use a hyphen, the values you specify are the start and the end of the port range, and the second port number must be greater than the first.

If you specify a comma, the values you specify are the start of the port range and the number of ports available from the start of the range.

Syntax

UNIX:
ES_DDBG_PORT_RANGE=value
export ES_DDBG_PORT_RANGE

Windows:
ES_DDBG_PORT_RANGE=value

Values

• low_port-high_port

  or

• low_port,number_of_ports

Default

If this is not set, dynamic debugging will use random ports.

Examples

The following definition specifies that ports 8001 through 8040 are to be used:

ES_DDBG_PORT_RANGE=8001-8040

The following definition specifies the same ports but using a different format:

ES_DDBG_PORT_RANGE=8001,40

MFTRACE_ANNOTATIONS

The location of the trace files.

MFTRACE_CONFIG

The location of the CTF configuration file.

MFTRACE_LOGS

The location of the CTF log files.

MFTSO_DEBUG

Controls the display of debug messages.

TX_MQTRACE

Enables tracing in dfh0mqis for WebSphere MQ calls.