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 Ops Monitor for CMF 6.3.

TRACE (Report control statements)

The TRACE control statement produces the Trace Report.

TRACE
[ID={ALL|(0,1,2,...,99)}]
[,MODE={DIE|SRM|TCB}]
[,LIMIT=0|nnnn]
[,START=yyddd:hhmmss]
[,STOP=yyddd:hhmmss]

The trace formatter differs in architecture from other Analyzer reporters in that the trace formatter does not have a data collection phase. The trace records are formatted and written out as they are read. For this reason, a separate DCB is used to produce the Trace Report. The ddname for this DCB is allocated dynamically by the Analyzer, unless the optional DD statement, //CMXTRACE, is used to direct the output from the Trace Report.

The TITLE and LOCATION parameters from the HEADERS general control statement are not reproduced on the Trace Report. If a SUBTITLE statement is defined, it is displayed on the Trace Report.

Note

Records must be sorted by date and time when using the TRACE statement.

The TRACE statement uses data collected by the TRACE Extractor control statement.

Parameters

The parameters for the TRACE control statement are as follows:

ID=

specifies IDs for which the trace data is to be formatted

Valid ID values are 0 through 99 and ALL; the default is ALL. If ALL is defined, all encountered trace IDs are formatted.

If you specify a value for this parameter, the corresponding values must be specified in the TRACE Extractor control statement.

MODE=

specifies the types of trace entries to be formatted: DIE, SRM, or TCB

If you do not specify a mode, all modes are formatted.

LIMIT=

limits the number of entries to be processed

Valid values are any value from 0 through 9999; the default is 0. If 0 is defined, all entries encountered are formatted.

START=

specifies the starting date and time for selecting trace records

If START is not specified, selection begins with the first trace record encountered. The starting date and time is defined in the same manner as the start date-time value for the DATETIME control statement.

STOP=

specifies the ending date and time for selecting trace records

If STOP is not specified, selection terminates with the last trace record encountered. The ending date and time is defined in the same manner as the end date-time value for the DATETIME control statement.

Note

The DATETIME control statement affects the TRACE statement, but TRACE ignores all CYCLE, PERIOD, and SHIFT control statements. Data in the Trace Report is limited by the ranges defined in the DATETIME control statement, and in the START and STOP parameters of the TRACE control statement.

Examples

The following examples illustrate the use of the TRACE control statement.

Example
TRACE

This example produces the Trace report with all defaults in effect. These defaults are all modes and all IDs for the Analyzer date-time range, with no limit on the number of entries to be formatted.

Example
TRACE  ID=(0,8,9),MODE=SRM,LIMIT=5000,START=10145:113000,
       STOP=10145:143000

This example produces the Trace Report for only SRM-type entries with IDs of 0, 8, and 9. Only the first 5000 entries are formatted. Record selection begins at 1130 hours on May 25, 2010, and ends at 1430 hours on May 25, 2010.

Example
TRACE  LIMIT=100,MODE=SRM,ID=0

This example produces the Trace Report for only SRM-type entries. Only ID 0 is selected and only the first 100 entries are formatted.



 

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