XYGATE Access Control Reference Manual

XYGATE
®
Access Control Reference Manual
Appendix D: XAC Interactive Commands
XYPRO Technology Corporation 244 Proprietary and Confidential
D17: >XAC_AUDIT_OUTPUT
This command, unlike <<COMMENT, can only be used within a macro, and the
command must be entirely in uppercase or entirely in lowercase type. It causes the
text specified to be written to the audit file.
Syntax:
>XAC_AUDIT_OUTPUT <text>
Example:
Contents of file $SYSTEM.XYGATEQA.GTXACOUT
?TACL MACRO
#OUTPUT This will send the following two lines to the audit
#OUTPUT files, but not to the terminal.
#OUTPUT >XAC_AUDIT_OUTPUT This line is an audit line,
#OUTPUT >XAC_AUDIT_OUTPUT but it will not be displayed for the user!
Contents of ACACL Entry
COMMAND TACL-USER
GROUP,USER
OBJECT $SYSTEM.SYSNN.TACL
ACL *.* ALIAS:"*"
START_LOGGED_OFF TRACKUSERID NULLNULLSTOP
TRACKVOLUME
OPENSBYOBJECTS $*.*.*
From an execution session of TACL-USER
$VIK XYGATEQA 5> run GTXACOUT
This will send the following two lines to the audit
files, but not to the terminal.
$VIK XYGATEQA 6>
The contents of the audit file
2013-08-27 17:26:13.853165 XAC-C 001C676F5B69 [232,052] $X37P.#IN TACL-USER
QA.IK 000003 10.1.1.178 run GTXACOUT
2013-08-27 17:26:13.866881 XAC-O 001C676F5B69 [232,052] $X37P.#IN TACL-USER
QA.IK 000004 10.1.1.178 This line is an audit line,
2013-08-27 17:26:13.867611 XAC-O 001C676F5B69 [232,052] $X37P.#IN TACL-USER
QA.IK 000005 10.1.1.178 but it will not be displayed for the user!
This example shows that the plain output written using #OUTPUT displays on the
terminal, but all four #OUTPUT lines, including the two lines with
>XAC_AUDIT_OUTPUT commands, are written to the audit.