DEBUG Command

ADDRESS PPQ Commands › Special PPQ Commands › DEBUG Command

DEBUG Command

The DEBUG command controls debugging trace output. You can prevent messages below a specified severity level from being traced, and you can specify what types of messages that you want to trace. Like the TRANSTATUS command, the DEBUG command is a diagnostic tool.

This command has the following format:

ADDRESS PPQ 'DEBUG [CATEGORY(hexbitfield)]
                 [CMDRESP (destination)]
                 [SEVERITY(severitylevel)] '

CATEGORY

(Optional) Specifies a mask for the category of message to be traced. Specify the hexbitfield value as a 32-bit hexadecimal string. Each bit position containing a 1 allows the trace utility (ASOTRACE.exe) to trace the corresponding message category.

Default: FFFFFFFF

This parameter specifies the bit assignments are as follows:

General Hex Code	Trace Type
FFFFFFFF	All
00000001	Startup
00000002	Initialization and termination
00000004	Manager thread
00000008	API entry point
00000010	Status

Hex Code	Trace Type
00000020	Control block
00000040	Packet
00000080	Memory allocation
00000100	High volume routine

Application Hex Code	Trace Type
00100000	Utility routine
00200000	PPQ
00800000	VOX
01000000	OCF
00200000	GLV

CMDRESP

(Optional) Directs return information, if any, to a specific destination. For a list of valid destination values, see the section Change the Default Return Destination with CMDRESP.

Default: REXX

SEVERITY

(Optional) Prevents tracing of messages with severity levels below the level specified for severitylevel. Valid severity levels are:

1: Error
2: Warning
3: Informational

4-8

Debug levels

Note: CA Technical Support specifies the appropriate debug trace level when necessary.

Default: 1