Default language.

Tracing Terminology


The different types and levels of trace facility messages are described in this section, as well as the format of the trace output records.

Types of Trace Messages

The trace facility allows the generation of Log and Trace messages. They are divided into the different levels listed in the following table.

Types of Trace Messages

Type

Level

Log

Error

Warning

Information

Trace

Debug

Trace

Log messages describe error, warning, or informational situations. They are written to the “log” destination, rather than being conveyed through an error message returned to the user. In these situations there may be no actual user.

Trace messages are for internal use only and should only be used in consultation with Support staff during problem diagnosis. Given the nature of tracing, an extremely large volume of messages could be returned if not used correctly. Trace messages are written to the “trace” destination.

The messages can be routed by level to the various destinations as described in Trace Destinations.

Format of Trace Output

The format of the trace output lines is:

PP YYYYMMDDHHMMSSTHT X NNNNNNNN xxxxxxxxxxx....xx

Where:

  • PP is the SP ProcessorID (WPCID). This will be 00 if issued in the client environment or the Set Controller.
  • YYYYMMDDHHMMSSTHT is the time the message was written.
  • X is the trace/error type identifier and can have the following values:
    • D – Debug
    • T – Trace
    • I – Informational
    • W – Warning
    • E – Error.
  • NNNNNNNN is the internal Code Pipeline module which issued the trace output.
  • xxxxxxxxxxxxxxxxxxxxxxxxx is the message text. The trace output lines are written in chronological order.

 

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

BMC AMI DevX Code Pipeline 22.01