Table of Contents
Advertisement
A3:
AUDIT (Filename)
This keyword determines the audit file specifications when a filename is defined.
Auditing is discussed in more detail in section 6.1,
on page 31.
Syntax:
AUDIT <filename> [EXT(pri,sec,max)] [NO_ROLL_MSGS]
EXT(x,x,x)
The optional EXT sub-keyword is used to specify the primary, secondary, and max
extents when an audit trail is created.
NO_ROLL_MSGS
The optional NO_ROLL_MSGS sub-keyword suppresses most EMS LOG audit file
messages that occur during the audit file rollover.
Example 1 below will send XDP audits to the file called XDPAUDIT in the subvolume
$SECURE.XDPAUDIT.
Example 1: How to configure XDP to audit to a diskfile
AUDIT $SECURE.XDPAUDIT.XDPAUDIT
The size of an audit trail can be controlled using the EXT(x,x,x) options. Example 2
below will set the XYGATEDP audit trail primary and secondary extents to 302 and the
max extents to 17.
Example 2: How to control XDP audit trail size
AUDIT $SYSTEM.XYGATEDP.AUDIT EXT(302,302,17)
If any of the diskfiles specified using the AUDIT keyword in the DPCONF file become
unavailable, which might occur if the audit file fills up or is renamed, the XDP server
will close the current file and attempt to recreate and re-open the original filename. If
the audit file named in the DPCONF entry is still unavailable, then XDP will wait and
retry the open operation.
Important! If the file error is an unretryable error, such as disk down, then XDP
processing will continue without auditing. When the disk comes back up, XDP will not
resume auditing. You must restart the server to resume auditing.
XYPRO Technology Corporation
®
XYGATE
Data Protection
Appendix A: The DPCONF File
™
Reference Manual
"AUDIT File
67
Considerations" starting
Proprietary and Confidential
Advertisement
Table of Contents
