Enables the tracing of both function calls for user-defined functions and their arguments.
Syntax
QX_TRACE_ARG_DUMP={any non-empty value}
Possible values:
|
disables the tracing of both function calls for user-defined functions and their arguments |
|
|
enables the tracing of both function calls for user-defined functions and their arguments |
Usage and examples
To be able to trace arguments for user-defined functions, you must first enable tracing the function calls themselves by setting QX_TRACE:
QX_TRACE=1
To ensure that function calls for user-defined functions are traced, you must define QX_TRACE_ARG_DUMP with any non-empty value (thus we recommend setting it to 1):
QX_TRACE_ARG_DUMP=1
If tracing of function calls for user-defined functions and their arguments is enabled, the tracing results are written to the log file created at every application launch.
These log files are located here:
QX_TRACE_ARG_DUMP must be set before the application is deployed.
QX_TRACE_ARG_DUMP applies at deployment and, if necessary, can be set in inet.env, env.properties, and environ.bat.
If you want to trace only function calls for user-defined functions(without their arguments), you must set the QX_TRACE environment variable.
To enable tracing of function calls for built-in functions, you must set QXDEBUG:
QXDEBUG = zT