TRACE (JANUS DEFINE parameter): Difference between revisions
mNo edit summary |
mNo edit summary |
||
Line 9: | Line 9: | ||
The <var>TRACE</var> parameter is valid for all port types. | The <var>TRACE</var> parameter is valid for all port types. | ||
'''Note:''' The <var>TRACE</var> keyword was introduced in Version 6.0 of the | '''Note:''' The <var>TRACE</var> keyword was introduced in Version 6.0 of the <var class="product">Sirius Mods</var>. Before that, trace operations were controlled by the DEBUG keyword, which is no longer available as of Version 6.5. | ||
==See also== | ==See also== |
Revision as of 20:19, 2 March 2012
<section begin="desc" />TRACE xxx<section end="desc" />
TRACE is a parameter on JANUS DEFINE, which defines and sets characteristics of a Janus port.
This parameter specifies the initial TRACE setting for the port. The TRACE setting controls what Janus-related trace information is logged to the audit trail. The port TRACE setting can be overridden by the JANUS TRACE command.
Like the JANUS TRACE command, the TRACE parameter value is a bit mask integer that sums the values of the options that will be logged. The default value is 3 for SDS and OPENSERV ports, and it is 0 for WEBSERV and all other ports. For a description of the individual bit options and for more information about the TRACE setting, see JANUS TRACE.
The TRACE parameter is valid for all port types.
Note: The TRACE keyword was introduced in Version 6.0 of the Sirius Mods. Before that, trace operations were controlled by the DEBUG keyword, which is no longer available as of Version 6.5.