Limited supportBMC provides limited support for this version of the product. As a result, BMC no longer accepts comments in this space. If you encounter problems with the product version or the space, contact BMC Support.BMC recommends upgrading to the latest version of the product. To see documentation for that version, see BMC AMI Datastream for z/OS 7.1.

Using the TRACE facility

BMC AMI Defender

and several related programs including CZASEND implement a diagnostic facility called TRACE. The TRACE facility might be used, generally at the direction of BMC Support, as an aid in diagnosing problems.

The TRACE facility causes

BMC AMI Defender

to output specific types of additional diagnostic messages in the CZAPRINT data set. Otherwise, the product continues to run normally when TRACE is specified; however, TRACE should not be left switched on indefinitely in production due to the additional overhead and potential for large print volumes.

The TRACE option might be specified in identical form (except for slight differences in syntax due to the differing command environments) on

BMC AMI Defender

and CZASEND OPTIONS-statement, on  CONFIG-statement, on the OPTIONs or a similar statement of several related programs (see the documentation for the specific program), and on the START-command and MODIFY-command.

If TRACE is completely omitted, then it defaults to the previous state of TRACE; if TRACE is specified with no trace-types or with -ALL then all tracing is turned off.

Specify zero or more of the trace specifications in the following table (in any order). Prefix any of the specifications with - (a minus sign or hyphen) to indicate negation. The specifications are processed left to right.

Example

TRACE(ALL ‑XL ‑ENV) indicates all TRACE output except that the former is related to translation and the operating environment.

TRACE types

Wherever TRACE is permitted, it accepts zero or more of the following Trace types:

Type

Diagnostic messages

ALL

All of the trace outputs listed. Use with caution; more trace output is not necessarily better. A high volume of messages might obscure the real problem. ‑ALL (negated ALL) is useful for turning off all enabled traces, whatever they might be.

AUX

Functions related to auxiliary programs, see the AUXILIARY-statement

CICS

Functions related to CICS SMF record type 110 record processing, especially record flattening

COMP

SMF record compression-related processing

CSA

CSA initialization

DB2

(Does not apply to Datastream for Ops)DB2-related processing 

ENV

The z/OS operating environment

FILTER

Filter evaluation, see Troubleshooting-filtering-events

IPADDR

IP address processing

IPGENL

IP general

MEM

Certain memory allocations and deallocations

MEMFLD

Certain memory allocations and deallocations related to Fields

MISC

Miscellaneous

PARMs

Parameters

TAGS

Duplicate tags

TIMER

Functions related to Timer processing

TLS

SSL/TLS-related events

XDATA

Transmitted data (generates a fairly voluminous number of messages)

XL

Translation (generates a fairly voluminous number of messages)

Related topic

TRACE-facility-syntax


 

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