WEBAUDIT parameter: Difference between revisions

From m204wiki
Jump to navigation Jump to search
m (misc formatting)
 
(One intermediate revision by one other user not shown)
Line 13: Line 13:
<dd> <var class="product">Sirius Mods</var> 6.9
<dd> <var class="product">Sirius Mods</var> 6.9
</dl>
</dl>
==Description==
==Description==
This parameter makes it possible to reduce the quantity of [[Tracking_system_activity_(CCAJRNL,_CCAAUDIT,_CCAJLOG)#Generating_an_audit_trail|audit trail]] data
This parameter makes it possible to reduce the quantity of [[Tracking system activity (CCAJRNL, CCAAUDIT, CCAJLOG)#Generating an audit trail|audit trail]] data
associated with [[Janus_Web_Server|Janus Web Server]] applications. The WEBAUDIT parameter is a
associated with [[Janus Web Server]] applications. The <var>WEBAUDIT</var> parameter is a
collection of bits that, when set, reduce the quantity of data sent to the [[Tracking_system_activity_(CCAJRNL,_CCAAUDIT,_CCAJLOG)#Using_the_CCAJRNL_data_set|Model 204 journal]]
collection of bits that, when set, reduce the quantity of data sent to the [[Tracking system activity (CCAJRNL, CCAAUDIT, CCAJLOG)#Using the CCAJRNL data set|Model 204 journal]]
or make it possible to reduce this quantity. The bits in WEBAUDIT are:
or make it possible to reduce this quantity. </p>
<p>
The bits in <var>WEBAUDIT</var> are: </p>


<dl>
<table class="thJustBold">
<dt>X'00000001'
<tr><th>X'00000001'</th>
<dd>Extends NOAUDIT capability, allowing NOAUDITW on the <var>[[MSGCTL_command|MSGCTL]]</var> command.
<td>Extends NOAUDIT capability, allowing NOAUDITW on the <var>[[MSGCTL command|MSGCTL]]</var> command.
<table class="noBorder">
<table>
<tr>
<tr>
<td><b>MSGCTL <var class="term">msg_no</var> NOAUDIT</b></td> <td>prevents <var class="term">msg_no</var> issued on any thread from going to the audit trail</td></tr>
<td><b>MSGCTL <var class="term">msg_no</var> NOAUDIT</b></td>  
<tr><td nowrap><b>MSGCTL <var class="term">msg_no</var> NOAUDITW</b></td> <td>prevents <var class="term">msg_no</var> issued on a Janus Web Server thread from going to the audit trail</td>
<td>Prevents <var class="term">msg_no</var> issued on any thread from going to the audit trail</td></tr>
</tr>
 
<tr><td nowrap><b>MSGCTL <var class="term">msg_no</var> NOAUDITW</b></td> <td>Prevents <var class="term">msg_no</var> issued on a Janus Web Server thread from going to the audit trail</td></tr>
</table>
</table>
See [[#Usage notes|Usage notes]] for more information.
<p>
See [[#Usage notes|Usage notes]] for more information. </p>
</td></tr>


<dt>X'00000002'
<tr><th>X'00000002'</th>
<dd>Suppress [[Application_Subsystem_development|APSY]] load since-last statistics for Janus Web Server threads.
<td>Suppress [[Application_Subsystem_development|APSY]] load [[Using system statistics#User since-last statistics|since-last statistics]] for Janus Web Server threads.
The resource usage associated with the APSY load such as CPU,
The resource usage associated with the APSY load such as CPU,
DKPRs, disk I/Os, etc. will be included in the EVAL since-last statistics
DKPRs, disk I/Os, etc. will be included in the EVAL since-last statistics
for the request. Since APSY load resource utilization is typically
for the request. Since APSY load resource utilization is typically
extremely minor relative to request evaluation, APSY load since-last
extremely minor relative to request evaluation, APSY load since-last
statistics do not provide much useful information.
statistics do not provide much useful information. </td></tr>


<dt>X'00000004'
<tr><th>X'00000004'</th>
<dd>Suppress APSY load since-last statistics for all threads. The resource
<td>Suppress APSY load since-last statistics for all threads. The resource
usage associated with the APSY load such as CPU, DKPRs, disk I/Os,
usage associated with the APSY load such as CPU, DKPRs, disk I/Os,
etc. will be included in the EVAL since-last statistics for the request.
etc. will be included in the EVAL since-last statistics for the request.
Since APSY load resource utilization is typically extremely minor relative
Since APSY load resource utilization is typically extremely minor relative
to request evaluation, APSY load since-last statistics do not provide much useful information.
to request evaluation, APSY load since-last statistics do not provide much useful information. </td></tr>


<dt>X'00000008'
<tr><th>X'00000008'</th>
<dd>Suppress &#x201C;NO USERID&#x201D; logout messages (M204.0353) for Janus Web
<td>Suppress &#x201C;NO USERID&#x201D; logout messages (M204.0353) for Janus Web Server threads. These messages are sometimes issued before a user
Server threads. These messages are sometimes issued before a user
logon, even though there is no user ID logged on the thread, so they are not useful. </td></tr>
logon, even though there is no userid logged on the thread, so they are not useful.


<dt>X'00000010'  
<tr><th>X'00000010'</th>
<dd>Suppress &#x201C;NO USERID&#x201D; logout messages (M204.0353) for all threads.
<td>Suppress &#x201C;NO USERID&#x201D; logout messages (M204.0353) for all threads. These messages are sometimes issued before a user logon, even
These messages are sometimes issued before a user logon, even
though there is no user ID logged on the thread, so they are not useful. </td></tr>
though there is no userid logged on the thread, so they are not useful.
</table>
</dl>


==Usage notes==
==Usage notes==
<p class="note"><b>Note:</b> The MSGCTL NOAUDIT enhancement should be used with caution. Preventing certain messages from going to the journal could make diagnosing certain problems more difficult.</p>
<p class="note"><b>Note:</b> The MSGCTL NOAUDIT enhancement should be used with caution. Preventing certain messages from going to the journal could make diagnosing certain problems more difficult.</p>


In any case, the MSGCTL NOAUDIT and NOAUDITW provide a neater and more fine-grained
In any case, the MSGCTL NOAUDIT and NOAUDITW provide a neater and more fine-grained way of reducing audit trail messages for Janus Web Server or other threads. Some good candidates for MSGCTL NOAUDIT or NOAUDITW are:
way of reducing audit trail messages for Janus Web Server or other threads.
<table class="thJustBold">
Some good candidates for MSGCTL NOAUDIT or NOAUDITW are:
<tr><th>M204.0099</th>
<dl>
<td>MINIMUM SERVSIZE FOR THESE TABLES = ... </td></tr>
<dt>M204.0099<dd> MINIMUM SERVSIZE FOR THESE TABLES = ...
 
<dt>M204.0131<dd> (Checkpoint completed or timed out messages)
<tr><th>M204.0131</th>
<dt>M204.0353<dd> (login/logout message that is essentially a shortened version of '''M204.0352''' that also gets logged to the journal)
<td>(Checkpoint completed or timed out messages) </td></tr>
<dt>M204.0608 <dd>FILE CLOSED: ...
 
<dt>M204.0619 <dd>GROUP FILE OPENED: ...
<tr><th>M204.0353</th>
<dt>M204.0620 <dd>FILE file OPENED (-- NO UPDATES ALLOWED)
<td>(login/logout message that is essentially a shortened version of '''M204.0352''' that also gets logged to the journal) </td></tr>
<dt>M204.0621 <dd>(Informational message indicating recovery status of file being opened)
 
<dt>M204.0622 <dd>(Informational message indicating the last update applied by the last rollforward for a file being opened)
<tr><th>M204.0608</th>
<dt>M204.0821 <dd>GROUP FILE CLOSED: ...
<td>FILE CLOSED: ... </td></tr>
<dt>M204.0858 <dd>GROUP group OPENED (-- NO UPDATES ALLOWED)
 
<dt>M204.1203 <dd>FILE file WAS LAST UPDATED ON ...
<tr><th>M204.0619</th>
<dt>M204.1238 <dd>(Informational message indicating the time the file was last recovered.)
<td>GROUP FILE OPENED: ... </td></tr>
 
<tr><th>M204.0620</th>
<td>FILE file OPENED (-- NO UPDATES ALLOWED) </td></tr>
 
<tr><th>M204.0621</th>
<td>(Informational message indicating recovery status of file being opened) </td></tr>
 
<tr><th>M204.0622</th>
<td>(Informational message indicating the last update applied by the last rollforward for a file being opened) </td></tr>
 
<tr><th>M204.0821</th>
<td>GROUP FILE CLOSED: ... </td></tr>
 
<tr><th>M204.0858</th>
<td>GROUP group OPENED (-- NO UPDATES ALLOWED) </td></tr>
 
<tr><th>M204.1203</th>
<td>FILE file WAS LAST UPDATED ON ... </td></tr>
 
<tr><th>M204.1238</th>
<td>(Informational message indicating the time the file was last recovered.) </td></tr>
</table>
<p>
The <var>NOAUD</var> parameter on Janus port definitions allows even more information to be suppressed from the audit trail on a port basis.
</p>


Under Sirius Mods version 6.9 and later, there is also a NOAUD parameter on Janus
port definitions that allow even more information to be suppressed from the audit trail on
a port basis.
</dl>
[[Category:System parameters]]
[[Category:System parameters]]
[[Category:Parameters]]
[[Category:Parameters]]

Latest revision as of 17:49, 11 December 2017

Janus Web audit trail reduction flags

Summary

Default value
X'00000000'
Parameter type
System
Where set
User 0 CCAIN parameters
Related products
All
Introduced
Sirius Mods 6.9

Description

This parameter makes it possible to reduce the quantity of audit trail data associated with Janus Web Server applications. The WEBAUDIT parameter is a collection of bits that, when set, reduce the quantity of data sent to the Model 204 journal

or make it possible to reduce this quantity.

The bits in WEBAUDIT are:

X'00000001' Extends NOAUDIT capability, allowing NOAUDITW on the MSGCTL command.
MSGCTL msg_no NOAUDIT Prevents msg_no issued on any thread from going to the audit trail
MSGCTL msg_no NOAUDITW Prevents msg_no issued on a Janus Web Server thread from going to the audit trail

See Usage notes for more information.

X'00000002' Suppress APSY load since-last statistics for Janus Web Server threads.

The resource usage associated with the APSY load such as CPU, DKPRs, disk I/Os, etc. will be included in the EVAL since-last statistics for the request. Since APSY load resource utilization is typically extremely minor relative to request evaluation, APSY load since-last

statistics do not provide much useful information.
X'00000004' Suppress APSY load since-last statistics for all threads. The resource

usage associated with the APSY load such as CPU, DKPRs, disk I/Os, etc. will be included in the EVAL since-last statistics for the request. Since APSY load resource utilization is typically extremely minor relative

to request evaluation, APSY load since-last statistics do not provide much useful information.
X'00000008' Suppress “NO USERID” logout messages (M204.0353) for Janus Web Server threads. These messages are sometimes issued before a user logon, even though there is no user ID logged on the thread, so they are not useful.
X'00000010' Suppress “NO USERID” logout messages (M204.0353) for all threads. These messages are sometimes issued before a user logon, even though there is no user ID logged on the thread, so they are not useful.

Usage notes

Note: The MSGCTL NOAUDIT enhancement should be used with caution. Preventing certain messages from going to the journal could make diagnosing certain problems more difficult.

In any case, the MSGCTL NOAUDIT and NOAUDITW provide a neater and more fine-grained way of reducing audit trail messages for Janus Web Server or other threads. Some good candidates for MSGCTL NOAUDIT or NOAUDITW are:

M204.0099 MINIMUM SERVSIZE FOR THESE TABLES = ...
M204.0131 (Checkpoint completed or timed out messages)
M204.0353 (login/logout message that is essentially a shortened version of M204.0352 that also gets logged to the journal)
M204.0608 FILE CLOSED: ...
M204.0619 GROUP FILE OPENED: ...
M204.0620 FILE file OPENED (-- NO UPDATES ALLOWED)
M204.0621 (Informational message indicating recovery status of file being opened)
M204.0622 (Informational message indicating the last update applied by the last rollforward for a file being opened)
M204.0821 GROUP FILE CLOSED: ...
M204.0858 GROUP group OPENED (-- NO UPDATES ALLOWED)
M204.1203 FILE file WAS LAST UPDATED ON ...
M204.1238 (Informational message indicating the time the file was last recovered.)

The NOAUD parameter on Janus port definitions allows even more information to be suppressed from the audit trail on a port basis.