AUDTERM (JANUS DEFINE parameter) - Revision history

JAL: minor formatting

2016-06-08T18:22:09Z

minor formatting

← Older revision		Revision as of 18:22, 8 June 2016
Line 7:		Line 7:
	<var>AUDTERM</var> specifies that terminal output '''is sent''' to the audit trail; <var>[[NOAUDTERM (JANUS DEFINE parameter)\|NOAUDTERM]]</var>, which is the default port setting, specifies that (non-compiler) terminal output '''is not sent''' to the audit trail.		<var>AUDTERM</var> specifies that terminal output '''is sent''' to the audit trail; <var>[[NOAUDTERM (JANUS DEFINE parameter)\|NOAUDTERM]]</var>, which is the default port setting, specifies that (non-compiler) terminal output '''is not sent''' to the audit trail.

	Note that some "print output" can be "captured" on a Sirius [[$lists\|$list]], a Janus [[Janus Sockets\|socket]], or a USE output stream, and thus it would not be sent as terminal output — to the audit trail or anywhere else. For further description of terminal output, see [[Janus Web Server application coding considerations#Determining which output is sent to the client\|"Determining which output is sent to the client"]] and [[$Sock_Capture#~~Print_capturing_hierarchy_and_other_considerations~~\|"Print capturing hierarchy and other considerations"]].		Note that some "print output" can be "captured" on a Sirius [[$lists\|$list]], a Janus [[Janus Sockets\|socket]], or a USE output stream, and thus it would not be sent as terminal output — to the audit trail or anywhere else. For further description of terminal output, see [[Janus Web Server application coding considerations#Determining which output is sent to the client\|Determining which output is sent to the client]] and [[$Sock_Capture#Print capturing hierarchy and other considerations\|Print capturing hierarchy and other considerations]].

	On a <var>[[JANUS DEFINE#type\|WEBSERV]]</var> port:		On a <var>[[JANUS DEFINE#type\|WEBSERV]]</var> port:
	<ul>		<ul>
			<li>Even with <var>AUDTERM</var> set on a <var>WEBSERV</var> port, terminal output is not sent to the audit trail if <var>[[$Web_On]]</var> is explicitly or implicitly set. </li>

	~~<li>Even with <var>AUDTERM</var> set on a <var>WEBSERV</var> port, terminal output is not sent to the audit trail if <var>[[$Web_On]]</var> is explicitly or implicitly set.~~		<li>The setting of <var>AUDTERM</var> (or <var>NOAUDTERM</var>) applies to all URLs on a <var>WEBSERV</var> port unless explicitly overridden by a <var>NOAUDTERM</var> (or <var>AUDTERM</var>) parameter on a <var>[[JANUS WEB ON]]</var> rule. </li>
	<li>The setting of <var>AUDTERM</var> (or <var>NOAUDTERM</var>) applies to all URLs on a <var>WEBSERV</var> port unless explicitly overridden by a <var>NOAUDTERM</var> (or <var>AUDTERM</var>) parameter on a <var>[[JANUS WEB ON]]</var> rule.
	</ul>		</ul>

	On a <var>[[JANUS DEFINE#type\|SRVSOCK]]</var> port:		On a <var>[[JANUS DEFINE#type\|SRVSOCK]]</var> port:
	<ul>		<ul>
			<li>The setting of <var>AUDTERM</var> (or <var>NOAUDTERM</var>) for a socket can be changed using the <var>[[$Sock_Set]]</var> function or the Socket object method Set. </li>
	<li>The setting of <var>AUDTERM</var> (or <var>NOAUDTERM</var>) for a socket can be changed using the <var>[[$Sock_Set]]</var> function or the Socket object method Set.
	</ul>		</ul>
	This parameter applies to all Janus "server" port types, and the default setting is <var>NOAUDTERM</var>.		This parameter applies to all Janus "server" port types, and the default setting is <var>NOAUDTERM</var>.

	~~Starting with Version 6.0, compared to earlier versions, any~~ <var>WEBSERV</var> port connection without an explicit <var>AUDTERM</var> or <var>NOAUDTERM</var> will probably generate fewer audit trail lines, as will any <var>[[JANUS DEFINE#type\|SDS]]</var> or <var>[[JANUS DEFINE#type\|OPENSERV]]</var> port. This should be a benefit, since most of this output is either uninteresting or already logged to the audit trail as ER, AD or MS lines. Logging these messages as RK lines as well is just a waste of journal space and I/O and makes application diagnosis and debugging from the audit trail more difficult because of the extra noise data. For <var>WEBSERV</var>, <var>OPENSERV</var>, or <var>SRVSOCK</var> applications that ~~wish~~ to explicitly audit information, the <var class="product">~~User Language~~</var> <var>Audit</var> statement should be used, not the <var>Print</var> statement.		Any <var>WEBSERV</var> port connection without an explicit <var>AUDTERM</var> or <var>NOAUDTERM</var> will probably generate fewer audit trail lines, as will any <var>[[JANUS DEFINE#type\|SDS]]</var> or <var>[[JANUS DEFINE#type\|OPENSERV]]</var> port. This should be a benefit, since most of this output is either uninteresting or already logged to the audit trail as ER, AD or MS lines. Logging these messages as RK lines as well is just a waste of journal space and I/O and makes application diagnosis and debugging from the audit trail more difficult because of the extra noise data. For <var>WEBSERV</var>, <var>OPENSERV</var>, or <var>SRVSOCK</var> applications that want to explicitly audit information, the <var class="product">SOUL</var> <var>Audit</var> statement should be used, not the <var>Print</var> statement.

	Valid for <var>WEBSERV</var>, <var>SDS</var>, <var>OPENSERV</var>, or <var>SRVSOCK</var> port types.		Valid for <var>WEBSERV</var>, <var>SDS</var>, <var>OPENSERV</var>, or <var>SRVSOCK</var> port types.
Line 34:		Line 33:
	<li>[[JANUS DEFINE#parmlist\|List of JANUS DEFINE parameters]]		<li>[[JANUS DEFINE#parmlist\|List of JANUS DEFINE parameters]]
	</ul>		</ul>


	[[Category:JANUS DEFINE parameters\|AUDTERM]]		[[Category:JANUS DEFINE parameters\|AUDTERM]]

JALWiccan: Automatically generated page update

2013-04-16T21:38:31Z

Automatically generated page update

← Older revision		Revision as of 21:38, 16 April 2013
Line 1:		Line 1:
	<span class="pageSubtitle"~~><section begin="desc" /~~>Send terminal output to audit trail~~<section end="desc" />~~</span>		<span class="pageSubtitle">Send terminal output to audit trail</span>

	<var>AUDTERM</var> is a parameter on <var>[[JANUS DEFINE]]</var>, which defines and sets characteristics of a Janus port.		<var>AUDTERM</var> is a parameter on <var>[[JANUS DEFINE]]</var>, which defines and sets characteristics of a Janus port.

JAL2 at 23:01, 1 March 2012

2012-03-01T23:01:16Z

← Older revision		Revision as of 23:01, 1 March 2012
Line 23:		Line 23:
	This parameter applies to all Janus "server" port types, and the default setting is <var>NOAUDTERM</var>.		This parameter applies to all Janus "server" port types, and the default setting is <var>NOAUDTERM</var>.

	Starting with Version 6.0, compared to earlier versions, any <var>WEBSERV</var> port connection without an explicit <var>AUDTERM</var> or <var>NOAUDTERM</var> will probably generate fewer audit trail lines, as will any SDS or <var>[[JANUS DEFINE#type\|OPENSERV]]</var> port. This should be a benefit, since most of this output is either uninteresting or already logged to the audit trail as ER, AD or MS lines. Logging these messages as RK lines as well is just a waste of journal space and I/O and makes application diagnosis and debugging from the audit trail more difficult because of the extra noise data. For <var>WEBSERV</var>, <var>OPENSERV</var>, or <var>SRVSOCK</var> applications that wish to explicitly audit information, the <var class="product">User Language</var> <var>Audit</var> statement should be used, not the <var>Print</var> statement.		Starting with Version 6.0, compared to earlier versions, any <var>WEBSERV</var> port connection without an explicit <var>AUDTERM</var> or <var>NOAUDTERM</var> will probably generate fewer audit trail lines, as will any <var>[[JANUS DEFINE#type\|SDS]]</var> or <var>[[JANUS DEFINE#type\|OPENSERV]]</var> port. This should be a benefit, since most of this output is either uninteresting or already logged to the audit trail as ER, AD or MS lines. Logging these messages as RK lines as well is just a waste of journal space and I/O and makes application diagnosis and debugging from the audit trail more difficult because of the extra noise data. For <var>WEBSERV</var>, <var>OPENSERV</var>, or <var>SRVSOCK</var> applications that wish to explicitly audit information, the <var class="product">User Language</var> <var>Audit</var> statement should be used, not the <var>Print</var> statement.

	Valid for <var>WEBSERV</var>, <var>~~[[JANUS DEFINE#type\|~~SDS]]</var>, <var>OPENSERV</var>, or <var>SRVSOCK</var> port types.		Valid for <var>WEBSERV</var>, <var>SDS</var>, <var>OPENSERV</var>, or <var>SRVSOCK</var> port types.

	Not valid for <var>[[JANUS DEFINE#type\|CLSOCK]]</var> or <var>[[JANUS DEFINE#type\|DEBUGGERCLIENT]]</var> port types.		Not valid for <var>[[JANUS DEFINE#type\|CLSOCK]]</var> or <var>[[JANUS DEFINE#type\|DEBUGGERCLIENT]]</var> port types.

JAL2 at 22:33, 1 March 2012

2012-03-01T22:33:52Z

← Older revision		Revision as of 22:33, 1 March 2012
Line 7:		Line 7:
	<var>AUDTERM</var> specifies that terminal output '''is sent''' to the audit trail; <var>[[NOAUDTERM (JANUS DEFINE parameter)\|NOAUDTERM]]</var>, which is the default port setting, specifies that (non-compiler) terminal output '''is not sent''' to the audit trail.		<var>AUDTERM</var> specifies that terminal output '''is sent''' to the audit trail; <var>[[NOAUDTERM (JANUS DEFINE parameter)\|NOAUDTERM]]</var>, which is the default port setting, specifies that (non-compiler) terminal output '''is not sent''' to the audit trail.

	Note that some "print output" can be "captured" on a Sirius $list, a Janus ~~Socket~~, or a USE output stream, and thus it would not be sent as terminal output &~~amp;~~mdash; to the audit trail or anywhere else. For further description of terminal output, see [[Janus Web Server application coding considerations#Determining which output is sent to the client\|"Determining which output is sent to the client"]] and [[$Sock_Capture#Print_capturing_hierarchy_and_other_considerations\|"Print capturing hierarchy and other considerations"]].		Note that some "print output" can be "captured" on a Sirius [[$lists\|$list]], a Janus [[Janus Sockets\|socket]], or a USE output stream, and thus it would not be sent as terminal output — to the audit trail or anywhere else. For further description of terminal output, see [[Janus Web Server application coding considerations#Determining which output is sent to the client\|"Determining which output is sent to the client"]] and [[$Sock_Capture#Print_capturing_hierarchy_and_other_considerations\|"Print capturing hierarchy and other considerations"]].

	On a <var>[[JANUS DEFINE#type\|WEBSERV]]</var> port:		On a <var>[[JANUS DEFINE#type\|WEBSERV]]</var> port:
	<ul>		<ul>

	<li>Even with <var>AUDTERM</var> set on a <var>WEBSERV</var> port, terminal output is not sent to the audit trail if $Web_On is explicitly or implicitly set.		<li>Even with <var>AUDTERM</var> set on a <var>WEBSERV</var> port, terminal output is not sent to the audit trail if <var>[[$Web_On]]</var> is explicitly or implicitly set.
	<li>The setting of <var>AUDTERM</var> (or <var>NOAUDTERM</var>) applies to all URLs on a <var>WEBSERV</var> port unless explicitly overridden by a <var>NOAUDTERM</var> (or <var>AUDTERM</var>) parameter on a <var>[[JANUS WEB ON]]</var> rule.		<li>The setting of <var>AUDTERM</var> (or <var>NOAUDTERM</var>) applies to all URLs on a <var>WEBSERV</var> port unless explicitly overridden by a <var>NOAUDTERM</var> (or <var>AUDTERM</var>) parameter on a <var>[[JANUS WEB ON]]</var> rule.
	</ul>		</ul>

JALWiccan: 1 revision

2012-03-01T22:26:34Z

1 revision

← Older revision	Revision as of 22:26, 1 March 2012
(No difference)

JAL2 at 22:26, 1 March 2012

2012-03-01T22:26:32Z

← Older revision		Revision as of 22:26, 1 March 2012
Line 7:		Line 7:
	<var>AUDTERM</var> specifies that terminal output '''is sent''' to the audit trail; <var>[[NOAUDTERM (JANUS DEFINE parameter)\|NOAUDTERM]]</var>, which is the default port setting, specifies that (non-compiler) terminal output '''is not sent''' to the audit trail.		<var>AUDTERM</var> specifies that terminal output '''is sent''' to the audit trail; <var>[[NOAUDTERM (JANUS DEFINE parameter)\|NOAUDTERM]]</var>, which is the default port setting, specifies that (non-compiler) terminal output '''is not sent''' to the audit trail.

	Note that some "print output" can be "captured" on a Sirius $list, a Janus Socket, or a USE output stream, and thus it would not be sent as terminal output — to the audit trail or anywhere else. For further description of terminal output, see [[Janus Web Server application coding considerations#Determining which output is sent to the client\|"Determining which output is sent to the client"]] and [[$Sock_Capture#Print_capturing_hierarchy_and_other_considerations\|"Print capturing hierarchy and other considerations"]].		Note that some "print output" can be "captured" on a Sirius $list, a Janus Socket, or a USE output stream, and thus it would not be sent as terminal output &mdash; to the audit trail or anywhere else. For further description of terminal output, see [[Janus Web Server application coding considerations#Determining which output is sent to the client\|"Determining which output is sent to the client"]] and [[$Sock_Capture#Print_capturing_hierarchy_and_other_considerations\|"Print capturing hierarchy and other considerations"]].

	On a <var>[[JANUS DEFINE#type\|WEBSERV]]</var> port:		On a <var>[[JANUS DEFINE#type\|WEBSERV]]</var> port:
Line 19:		Line 19:
	<ul>		<ul>

	<li>The setting of <var>AUDTERM</var> (or <var>NOAUDTERM</var>) for a socket can be changed using the $~~SOCK_SET~~ function or the Socket object method Set.		<li>The setting of <var>AUDTERM</var> (or <var>NOAUDTERM</var>) for a socket can be changed using the <var>[[$Sock_Set]]</var> function or the Socket object method Set.
	</ul>		</ul>
	This parameter applies to all Janus "server" port types, and the default setting is <var>NOAUDTERM</var>.		This parameter applies to all Janus "server" port types, and the default setting is <var>NOAUDTERM</var>.

JAL2 at 21:29, 1 March 2012

2012-03-01T21:29:42Z

← Older revision		Revision as of 21:29, 1 March 2012
Line 7:		Line 7:
	<var>AUDTERM</var> specifies that terminal output '''is sent''' to the audit trail; <var>[[NOAUDTERM (JANUS DEFINE parameter)\|NOAUDTERM]]</var>, which is the default port setting, specifies that (non-compiler) terminal output '''is not sent''' to the audit trail.		<var>AUDTERM</var> specifies that terminal output '''is sent''' to the audit trail; <var>[[NOAUDTERM (JANUS DEFINE parameter)\|NOAUDTERM]]</var>, which is the default port setting, specifies that (non-compiler) terminal output '''is not sent''' to the audit trail.

	Note that some "print output" can be "captured" on a Sirius $list, a Janus Socket, or a USE output stream, and thus it would not be sent as terminal output — to the audit trail or anywhere else. For further description of terminal output, see [[Janus Web Server application coding considerations#Determining which output is sent to the client\|"Determining which output is sent to the client"]] and [[$Sock_Capture#Print_capturing_hierarchy_and_other_considerations\|"~~Print_capturing_hierarchy_and_other_considerations~~"]].		Note that some "print output" can be "captured" on a Sirius $list, a Janus Socket, or a USE output stream, and thus it would not be sent as terminal output — to the audit trail or anywhere else. For further description of terminal output, see [[Janus Web Server application coding considerations#Determining which output is sent to the client\|"Determining which output is sent to the client"]] and [[$Sock_Capture#Print_capturing_hierarchy_and_other_considerations\|"Print capturing hierarchy and other considerations"]].

	On a <var>[[JANUS DEFINE#type\|WEBSERV]]</var> port:		On a <var>[[JANUS DEFINE#type\|WEBSERV]]</var> port:

JAL2 at 21:28, 1 March 2012

2012-03-01T21:28:38Z

← Older revision		Revision as of 21:28, 1 March 2012
Line 1:		Line 1:
	~~{{DISPLAYTITLE:AUDTERM}}~~
	<span class="pageSubtitle"><section begin="desc" />Send terminal output to audit trail<section end="desc" /></span>		<span class="pageSubtitle"><section begin="desc" />Send terminal output to audit trail<section end="desc" /></span>

Line 8:		Line 7:
	<var>AUDTERM</var> specifies that terminal output '''is sent''' to the audit trail; <var>[[NOAUDTERM (JANUS DEFINE parameter)\|NOAUDTERM]]</var>, which is the default port setting, specifies that (non-compiler) terminal output '''is not sent''' to the audit trail.		<var>AUDTERM</var> specifies that terminal output '''is sent''' to the audit trail; <var>[[NOAUDTERM (JANUS DEFINE parameter)\|NOAUDTERM]]</var>, which is the default port setting, specifies that (non-compiler) terminal output '''is not sent''' to the audit trail.

	Note that some "print output" can be "captured" on a Sirius $list, a Janus Socket, or a USE output stream, and thus it would not be sent as terminal output &~~amp;~~mdash; to the audit trail or anywhere else. For further description of terminal output, see [[Janus Web Server application coding considerations#Determining which output is sent to the client\|"Determining which output is sent to the client"]] and [[$Sock_Capture#Print_capturing_hierarchy_and_other_considerations\|"Print_capturing_hierarchy_and_other_considerations"]].		Note that some "print output" can be "captured" on a Sirius $list, a Janus Socket, or a USE output stream, and thus it would not be sent as terminal output — to the audit trail or anywhere else. For further description of terminal output, see [[Janus Web Server application coding considerations#Determining which output is sent to the client\|"Determining which output is sent to the client"]] and [[$Sock_Capture#Print_capturing_hierarchy_and_other_considerations\|"Print_capturing_hierarchy_and_other_considerations"]].

	On a <var>[[JANUS DEFINE#type\|WEBSERV]]</var> port:		On a <var>[[JANUS DEFINE#type\|WEBSERV]]</var> port:

JALWiccan: 1 revision

2012-03-01T21:27:35Z

1 revision

← Older revision	Revision as of 21:27, 1 March 2012
(No difference)

JAL2 at 21:27, 1 March 2012

2012-03-01T21:27:33Z

← Older revision		Revision as of 21:27, 1 March 2012
Line 8:		Line 8:
	<var>AUDTERM</var> specifies that terminal output '''is sent''' to the audit trail; <var>[[NOAUDTERM (JANUS DEFINE parameter)\|NOAUDTERM]]</var>, which is the default port setting, specifies that (non-compiler) terminal output '''is not sent''' to the audit trail.		<var>AUDTERM</var> specifies that terminal output '''is sent''' to the audit trail; <var>[[NOAUDTERM (JANUS DEFINE parameter)\|NOAUDTERM]]</var>, which is the default port setting, specifies that (non-compiler) terminal output '''is not sent''' to the audit trail.

	Note that some "print output" can be "captured" on a Sirius $list, a Janus Socket, or a USE output stream, and thus it would not be sent as terminal output — to the audit trail or anywhere else. For further description of terminal output, see [[Janus Web Server application coding considerations#Determining which output is sent to the client\|"Determining which output is sent to the client"]] and [[$Sock_Capture#Print_capturing_hierarchy_and_other_considerations\|"Print_capturing_hierarchy_and_other_considerations"]].		Note that some "print output" can be "captured" on a Sirius $list, a Janus Socket, or a USE output stream, and thus it would not be sent as terminal output &mdash; to the audit trail or anywhere else. For further description of terminal output, see [[Janus Web Server application coding considerations#Determining which output is sent to the client\|"Determining which output is sent to the client"]] and [[$Sock_Capture#Print_capturing_hierarchy_and_other_considerations\|"Print_capturing_hierarchy_and_other_considerations"]].

	On a <var>[[JANUS DEFINE#type\|WEBSERV]]</var> port:		On a <var>[[JANUS DEFINE#type\|WEBSERV]]</var> port:
Line 24:		Line 24:
	This parameter applies to all Janus "server" port types, and the default setting is <var>NOAUDTERM</var>.		This parameter applies to all Janus "server" port types, and the default setting is <var>NOAUDTERM</var>.

	Starting with Version 6.0, compared to earlier versions, any <var>WEBSERV</var> port connection without an explicit <var>AUDTERM</var> or <var>NOAUDTERM</var> will probably generate fewer audit trail lines, as will any SDS or <var>[[JANUS DEFINE#type\|OPENSERV]]</var> port. This should be a benefit, since most of this output is either uninteresting or already logged to the audit trail as ER, AD or MS lines. Logging these messages as RK lines as well is just a waste of journal space and I/O and makes application diagnosis and debugging from the audit trail more difficult because of the extra noise data. For <var>WEBSERV</var>, <var>OPENSERV</var>, or <var>SRVSOCK</var> applications that wish to explicitly audit information, the User Language <var>Audit</var> statement should be used, not the <var>Print</var> statement.		Starting with Version 6.0, compared to earlier versions, any <var>WEBSERV</var> port connection without an explicit <var>AUDTERM</var> or <var>NOAUDTERM</var> will probably generate fewer audit trail lines, as will any SDS or <var>[[JANUS DEFINE#type\|OPENSERV]]</var> port. This should be a benefit, since most of this output is either uninteresting or already logged to the audit trail as ER, AD or MS lines. Logging these messages as RK lines as well is just a waste of journal space and I/O and makes application diagnosis and debugging from the audit trail more difficult because of the extra noise data. For <var>WEBSERV</var>, <var>OPENSERV</var>, or <var>SRVSOCK</var> applications that wish to explicitly audit information, the <var class="product">User Language</var> <var>Audit</var> statement should be used, not the <var>Print</var> statement.

	Valid for <var>WEBSERV</var>, <var>[[JANUS DEFINE#type\|SDS]]</var>, <var>OPENSERV</var>, or <var>SRVSOCK</var> port types.		Valid for <var>WEBSERV</var>, <var>[[JANUS DEFINE#type\|SDS]]</var>, <var>OPENSERV</var>, or <var>SRVSOCK</var> port types.

← Older revision		Revision as of 21:29, 1 March 2012
Line 7:		Line 7:
	<var>AUDTERM</var> specifies that terminal output '''is sent''' to the audit trail; <var>[[NOAUDTERM (JANUS DEFINE parameter)\|NOAUDTERM]]</var>, which is the default port setting, specifies that (non-compiler) terminal output '''is not sent''' to the audit trail.		<var>AUDTERM</var> specifies that terminal output '''is sent''' to the audit trail; <var>[[NOAUDTERM (JANUS DEFINE parameter)\|NOAUDTERM]]</var>, which is the default port setting, specifies that (non-compiler) terminal output '''is not sent''' to the audit trail.

	Note that some "print output" can be "captured" on a Sirius $list, a Janus Socket, or a USE output stream, and thus it would not be sent as terminal output — to the audit trail or anywhere else. For further description of terminal output, see [[Janus Web Server application coding considerations#Determining which output is sent to the client\|"Determining which output is sent to the client"]] and [[$Sock_Capture#Print_capturing_hierarchy_and_other_considerations\|"~~Print_capturing_hierarchy_and_other_considerations~~"]].		Note that some "print output" can be "captured" on a Sirius $list, a Janus Socket, or a USE output stream, and thus it would not be sent as terminal output — to the audit trail or anywhere else. For further description of terminal output, see [[Janus Web Server application coding considerations#Determining which output is sent to the client\|"Determining which output is sent to the client"]] and [[$Sock_Capture#Print_capturing_hierarchy_and_other_considerations\|"Print capturing hierarchy and other considerations"]].

	On a <var>[[JANUS DEFINE#type\|WEBSERV]]</var> port:		On a <var>[[JANUS DEFINE#type\|WEBSERV]]</var> port:

← Older revision		Revision as of 21:27, 1 March 2012
Line 8:		Line 8:
	<var>AUDTERM</var> specifies that terminal output '''is sent''' to the audit trail; <var>[[NOAUDTERM (JANUS DEFINE parameter)\|NOAUDTERM]]</var>, which is the default port setting, specifies that (non-compiler) terminal output '''is not sent''' to the audit trail.		<var>AUDTERM</var> specifies that terminal output '''is sent''' to the audit trail; <var>[[NOAUDTERM (JANUS DEFINE parameter)\|NOAUDTERM]]</var>, which is the default port setting, specifies that (non-compiler) terminal output '''is not sent''' to the audit trail.

	Note that some "print output" can be "captured" on a Sirius $list, a Janus Socket, or a USE output stream, and thus it would not be sent as terminal output — to the audit trail or anywhere else. For further description of terminal output, see [[Janus Web Server application coding considerations#Determining which output is sent to the client\|"Determining which output is sent to the client"]] and [[$Sock_Capture#Print_capturing_hierarchy_and_other_considerations\|"Print_capturing_hierarchy_and_other_considerations"]].		Note that some "print output" can be "captured" on a Sirius $list, a Janus Socket, or a USE output stream, and thus it would not be sent as terminal output &mdash; to the audit trail or anywhere else. For further description of terminal output, see [[Janus Web Server application coding considerations#Determining which output is sent to the client\|"Determining which output is sent to the client"]] and [[$Sock_Capture#Print_capturing_hierarchy_and_other_considerations\|"Print_capturing_hierarchy_and_other_considerations"]].

	On a <var>[[JANUS DEFINE#type\|WEBSERV]]</var> port:		On a <var>[[JANUS DEFINE#type\|WEBSERV]]</var> port:
Line 24:		Line 24:
	This parameter applies to all Janus "server" port types, and the default setting is <var>NOAUDTERM</var>.		This parameter applies to all Janus "server" port types, and the default setting is <var>NOAUDTERM</var>.

	Starting with Version 6.0, compared to earlier versions, any <var>WEBSERV</var> port connection without an explicit <var>AUDTERM</var> or <var>NOAUDTERM</var> will probably generate fewer audit trail lines, as will any SDS or <var>[[JANUS DEFINE#type\|OPENSERV]]</var> port. This should be a benefit, since most of this output is either uninteresting or already logged to the audit trail as ER, AD or MS lines. Logging these messages as RK lines as well is just a waste of journal space and I/O and makes application diagnosis and debugging from the audit trail more difficult because of the extra noise data. For <var>WEBSERV</var>, <var>OPENSERV</var>, or <var>SRVSOCK</var> applications that wish to explicitly audit information, the User Language <var>Audit</var> statement should be used, not the <var>Print</var> statement.		Starting with Version 6.0, compared to earlier versions, any <var>WEBSERV</var> port connection without an explicit <var>AUDTERM</var> or <var>NOAUDTERM</var> will probably generate fewer audit trail lines, as will any SDS or <var>[[JANUS DEFINE#type\|OPENSERV]]</var> port. This should be a benefit, since most of this output is either uninteresting or already logged to the audit trail as ER, AD or MS lines. Logging these messages as RK lines as well is just a waste of journal space and I/O and makes application diagnosis and debugging from the audit trail more difficult because of the extra noise data. For <var>WEBSERV</var>, <var>OPENSERV</var>, or <var>SRVSOCK</var> applications that wish to explicitly audit information, the <var class="product">User Language</var> <var>Audit</var> statement should be used, not the <var>Print</var> statement.

	Valid for <var>WEBSERV</var>, <var>[[JANUS DEFINE#type\|SDS]]</var>, <var>OPENSERV</var>, or <var>SRVSOCK</var> port types.		Valid for <var>WEBSERV</var>, <var>[[JANUS DEFINE#type\|SDS]]</var>, <var>OPENSERV</var>, or <var>SRVSOCK</var> port types.