Administration Guide > Diagnostic Tools > TRACE_DUMP

TRACE_DUMP

Script function: Supplies the values of the memory range in a trace file.

Syntax

TRACE_DUMP (Trace option, trace level, memory range[, memory range,...][, additional info])

Syntax	Description/format
Trace option	Trace setting Format: script variable or number Allowed values: "1" - TCP/IP "2" - databaseA database is an organized collection of data including relevant data structures. "4" - Srcall "5" - Memio "6" - JCL "7" - Memsv "8" - SNMP "9" - Zuxml "10" - Cache "12" - Ucds "13" - Xscript "14" - UC4global "16" - minimal
Trace level	Size of the trace Format: script variable or number The allowed values depend on the selected trace option.
Memory range	Memory range that is to be recorded Format: script literal or script variable Allowed values: "WORK MEMORY" "LOCAL MEMORY" "XML + XML-Handle" "DB + Table name(column name;column name;...)" "DB + Table name" "SCRIPT_VARA" "SCRIPT_PRG" "USER_TAB" "CLNT_TAB" "EX_TAB" "*_TAB" "GIVE_ME_ALL" Separate several memory ranges that are to be recorded with commas.
Additional info	Any additional text or information Format: script literal or script variable

Return codes
"0" - Trace was successful. "20208" - Trace level is not in the allowed area. "20209" - The indicated memory range is not supported. "20210" - The XML handle is wrong. "20211" - The table does not exist.

Comments

This script function only serves diagnostic purposes and must only be used in close cooperation with the support team.

To enable trace output, keep the following instructions in mind:

The indicated trace option must also be activated in the System Overview (in the properties of the server processes).
Additionally, the specified trace level must at least be as high as set in the properties.

The trace output is written to the file specified in the INI file of the Server (see [TRACE] section).

The script function LOG_DUMP works similarly but writes the result to the log file and considers all values.

Example

In the example below, a trace is activated for several memory ranges. The trace is successful when a database trace with at least one of four trace levels was activated in the properties of the server processes.

:SET &RET# = TRACE_DUMP(2,4, "DB + XAO(XAO_Idnr, XAO_MsgNr), LOCAL_MEMORY, SCRIPT_VARA", "Various Information")

Script element	Description
LOG_DUMP	Outputs values of the memory range to a log file
TRACE	Outputs values to a trace file