JANUS TRACE - Revision history

JAL: link repair

2016-09-14T22:08:59Z

link repair

← Older revision		Revision as of 22:08, 14 September 2016
Line 19:		Line 19:
	<li>IPV4 standard 32-bit "dotted-decimal" form: for example, <code>198.242.244.97</code>. </li>		<li>IPV4 standard 32-bit "dotted-decimal" form: for example, <code>198.242.244.97</code>. </li>

	<li>IPV6 standard (https://tools.ietf.org/html/rfc5952) 128-bit form: for example, <code>2011:0ab4:15a1:~~0000:0000~~:4a0e:0280:5274</code>		<li>IPV6 standard ([https://tools.ietf.org/html/rfc5952 RFC 5952]) 128-bit form: for example, <code>2011:0ab4:15a1::4a0e:0280:5274</code>
	<p>		<p>
	The IPV6 form is supported as of version 7.7 of Model 204.</p></li>		The IPV6 form is supported as of version 7.7 of Model 204.</p></li>

JAL: add IPV6 address format

2016-09-14T20:42:56Z

add IPV6 address format

← Older revision		Revision as of 20:42, 14 September 2016
Line 15:		Line 15:

	<tr><th><i>ipaddr</i></th>		<tr><th><i>ipaddr</i></th>
	<td>The remote IP address for which to set trace options. The IP address should be specified in standard ''dotted'' form: for example, 198.242.244.97. A host name cannot be specified on the <var>JANUS TRACE</var> command. If neither <var class="term">ipaddr</var> nor <var class="term">ipsubnet</var> is specified, the <var>JANUS TRACE</var> command is assumed to apply to all connections on the port.</td></tr>		<td>The remote IP address for which to set trace options. The IP address should be specified in either:
			<ul>
			<li>IPV4 standard 32-bit "dotted-decimal" form: for example, <code>198.242.244.97</code>. </li>

			<li>IPV6 standard (https://tools.ietf.org/html/rfc5952) 128-bit form: for example, <code>2011:0ab4:15a1:0000:0000:4a0e:0280:5274</code>
			<p>
			The IPV6 form is supported as of version 7.7 of Model 204.</p></li>
			</ul>
			<p>
			A host name cannot be specified on the <var>JANUS TRACE</var> command. </p>
			<p>
			If neither <var class="term">ipaddr</var> nor <var class="term">ipsubnet</var> is specified, the <var>JANUS TRACE</var> command is assumed to apply to all connections on the port.</p></td></tr>

	<tr><th><i>ipsubnet</i></th>		<tr><th><i>ipsubnet</i></th>

JAL: remove displaytitle

2016-01-27T21:37:24Z

remove displaytitle

Show changes

JAL: /* Syntax terms */

2013-08-21T20:34:05Z

Syntax terms

← Older revision		Revision as of 20:34, 21 August 2013
Line 25:		Line 25:
	<tr><th>1</th>		<tr><th>1</th>
	<td>Log the SQL request on SDS or URL rules processing on WEBSERV ports. This bit is useful on WEBSERV ports if there is confusion about which JANUS WEB rules apply to a particular URL.</td></tr>		<td>Log the SQL request on SDS or URL rules processing on WEBSERV ports. This bit is useful on WEBSERV ports if there is confusion about which JANUS WEB rules apply to a particular URL.</td></tr>

	<tr><th>2</th>		<tr><th>2</th>
	<td>Log RPC requests on OPENSERV ports. Show request headers on WEBSERV ports.</td></tr>		<td>Log RPC requests on OPENSERV ports. Show request headers on WEBSERV ports.</td></tr>

	<tr><th>4</th>		<tr><th>4</th>
	<td>Log generated <var class="product">User Language</var> (SDS ports only). Show form data on WEBSERV ports. This bit has no effect on OPENSERV ports. Using this bit on SDS ports can generate huge quantities of data so use it sparingly.</td></tr>		<td>Log generated <var class="product">User Language</var> (SDS ports only). Show form data on WEBSERV ports. This bit has no effect on OPENSERV ports. Using this bit on SDS ports can generate huge quantities of data so use it sparingly.</td></tr>

	<tr><th>8</th>		<tr><th>8</th>
	<td>Log in hex and char all activity on port (this allows TCP/IP level tracing).</td></tr>		<td>Log in hex and char all activity on port (this allows TCP/IP level tracing).</td></tr>

	<tr><th>16</th>		<tr><th>16</th>
	<td>Log Persistent Client State (cookies) on WEBSERV ports.</td></tr>		<td>Log Persistent Client State (cookies) on WEBSERV ports.</td></tr>

	<tr><th>32</th>		<tr><th>32</th>
	<td>Trace web response headers.</td></tr>		<td>Trace web response headers.</td></tr>

	<tr><th>64</th>		<tr><th>64</th>
	<td>Trace web response text.</td></tr>		<td>Trace web response text.</td></tr>

	<tr><th>128</th>		<tr><th>128</th>
	<td>Trace data between TCP and SSL.		<td>Trace data between TCP and SSL.
Line 44:		Line 51:
	The default for TRACE is 3 for SDS and OPENSERV ports, and it is 0 for WEBSERV ports and all others.		The default for TRACE is 3 for SDS and OPENSERV ports, and it is 0 for WEBSERV ports and all others.
	</td></tr>		</td></tr>
	<tr><th>OFF</th>
			<tr><th><var>OFF</var></th>
	<td>Indicates that no TRACE override is to be used for the specified IP address or addresses.		<td>Indicates that no TRACE override is to be used for the specified IP address or addresses.
	</td></tr></table>		</td></tr></table>

JALWiccan: Automatically generated page update

2013-04-16T17:32:08Z

Automatically generated page update

← Older revision		Revision as of 17:32, 16 April 2013
Line 1:		Line 1:
	{{DISPLAYTITLE:JANUS TRACE}}		{{DISPLAYTITLE:JANUS TRACE}}
	<span class="pageSubtitle"~~><section begin="desc" /~~>Set Janus TRACE level~~<section end="desc" />~~</span>		<span class="pageSubtitle">Set Janus TRACE level</span>

	This command sets or overrides the trace settings for the named Janus port(s), determining which, and how much, information is written to the Model 204 journal.		This command sets or overrides the trace settings for the named Janus port(s), determining which, and how much, information is written to the Model 204 journal.

Dme: /* Syntax */

2013-01-30T20:35:27Z

Syntax

← Older revision		Revision as of 20:35, 30 January 2013
Line 7:		Line 7:

	==Syntax==		==Syntax==
	<p class="syntax"~~><section begin="syntax" /~~> JANUS TRACE portname [ ipaddr \| ipsubnet ] value \| OFF		<p class="syntax">JANUS TRACE portname [ ipaddr \| ipsubnet ] value \| OFF
	~~<section end="syntax" />~~</p>		</p>

	===Syntax terms===		===Syntax terms===

JAL: /* Syntax terms */

2012-10-10T22:09:46Z

Syntax terms

← Older revision		Revision as of 22:09, 10 October 2012
Line 28:		Line 28:
	<td>Log RPC requests on OPENSERV ports. Show request headers on WEBSERV ports.</td></tr>		<td>Log RPC requests on OPENSERV ports. Show request headers on WEBSERV ports.</td></tr>
	<tr><th>4</th>		<tr><th>4</th>
	<td>Log generated User Language (SDS ports only). Show form data on WEBSERV ports. This bit has no effect on OPENSERV ports. Using this bit on SDS ports can generate huge quantities of data so use it sparingly.</td></tr>		<td>Log generated <var class="product">User Language</var> (SDS ports only). Show form data on WEBSERV ports. This bit has no effect on OPENSERV ports. Using this bit on SDS ports can generate huge quantities of data so use it sparingly.</td></tr>
	<tr><th>8</th>		<tr><th>8</th>
	<td>Log in hex and char all activity on port (this allows TCP/IP level tracing).</td></tr>		<td>Log in hex and char all activity on port (this allows TCP/IP level tracing).</td></tr>

Dme: /* Syntax terms */

2012-01-07T21:19:18Z

Syntax terms

← Older revision		Revision as of 21:19, 7 January 2012
Line 20:		Line 20:
	<td>The IP subnet for which to set trace options. The IP subnet can be specified either in the standard ''dotted'' subnet and mask form, for example, 198.242.244.0/255.255.255.0, or a ''dotted'' IP address followed by the number of subnet bits, as in 198.242.244.0-24. All bits that are not part of the subnet '''must''' be 0. If neither <var class="term">ipaddr</var> nor <var class="term">ipsubnet</var> is specified, the JANUS TRACE command is assumed to apply to all connections on the port.</td></tr>		<td>The IP subnet for which to set trace options. The IP subnet can be specified either in the standard ''dotted'' subnet and mask form, for example, 198.242.244.0/255.255.255.0, or a ''dotted'' IP address followed by the number of subnet bits, as in 198.242.244.0-24. All bits that are not part of the subnet '''must''' be 0. If neither <var class="term">ipaddr</var> nor <var class="term">ipsubnet</var> is specified, the JANUS TRACE command is assumed to apply to all connections on the port.</td></tr>
	<tr><th><i>value</i></th>		<tr><th><i>value</i></th>
	<td>The bit-mask integer value to use for tracing the indicated connections.		<td>The bit-mask integer value to use for tracing the indicated connections. This controls the quantity of trace information logged to the audit trail. You specify an integer that sums the values of the options you want to have logged:
	~~The TRACE setting~~ controls the quantity of trace information logged to the audit trail. You specify an integer that sums the values of the options you want to have logged:

	<table class="syntaxNested">		<table class="syntaxNested">

Dme: /* Usage notes */

2012-01-07T21:18:41Z

Usage notes

@@ Line 83: / Line 83: @@
 </li>
-<li>The TRACE setting controls the quantity of trace information logged to the audit trail. You specify an integer that sums the values of the options you want to have logged:
+<li>Setting the 8 bit may result in huge quantities of data going to the audit trail; this trace option logs RK lines of the form:
 <p class="code"> AP?: offxxx : xdxdxdxd ... | ccc...ccc |

Dme: /* Syntax terms */

2012-01-07T21:17:46Z

Syntax terms

@@ Line 20: / Line 20: @@
 <td>The IP subnet for which to set trace options. The IP subnet can be specified either in the standard ''dotted'' subnet and mask form, for example, 198.242.244.0/255.255.255.0, or a ''dotted'' IP address followed by the number of subnet bits, as in 198.242.244.0-24. All bits that are not part of the subnet '''must''' be 0. If neither <var class="term">ipaddr</var> nor <var class="term">ipsubnet</var> is specified, the JANUS TRACE command is assumed to apply to all connections on the port.</td></tr>
 <tr><th><i>value</i></th>
-<td>The bit-mask integer value to use for tracing the indicated connections. See the following page.</td></tr>
+<td>The bit-mask integer value to use for tracing the indicated connections.
 <tr><th>OFF</th>
 <td>Indicates that no TRACE override is to be used for the specified IP address or addresses.