TRACE_DUMP

Use the TRACE_DUMP script function to supply the value of the memory range in a trace file.

Syntax

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

Parameters

  • TRACE_DUMP

    Supplies the value of the memory range in a trace file

  • Trace option

    Trace setting

    Format: script variable or number

    Allowed values:

    • 1 TCP/IP
    • 2 Database
    • 4 Srcall
    • 5 Memio
    • 6 JCL
    • 7 Memsv
    • 8 SNMP
    • 9 Zuxml
    • 10 Cache
    • 12 Ucds
    • 13 Xscript
    • 14 UC4global
    • 16 Minimal

  • Trace level

    Trace size

    Format: script variable or number

    The allowed values depend on the trace option that has been selected.

  • 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"

    Note: 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

    The trace was successful

  • 20208

    The trace level is not within the allowed range

  • 20209

    The indicated memory range is not supported

  • 20210

    The XML handle is wrong

  • 20211

    The table does not exist

Notes:

  • 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 Administration perspective (Defining Agent Tracing Settings).

    • 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 [TRACE] section of the INI file of the Automation Engine, see Automation Engine.

  • The script function LOG_DUMP works similarly but writes the result to the log file and considers all values. For more information, see LOG_DUMP.

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")

See also: