XYGATE Access Control Reference Manual

XYGATE
®
Access Control Reference Manual
Appendix D: XAC Interactive Commands
XYPRO Technology Corporation 237 Proprietary and Confidential
D8: <<OBEY
This command gives an OBEY command to any program even those that did not
previously have one. The commands executed from within the <filename> are
executed as if they were entered by the invoking user.
Syntax:
<<O <filename>
–or–
<<OBEY <filename>
Note: <filename> can be any file that contains text to execute.
>OBEY opens <filename> as the userid of the invoking user unless the keyword
TRACKUSERID is specified. In that case, <<OBEY will open <filename> as the userid
of the OBJECT program. We recommend that the ALIAS keyword always be used to
map a program’s built-in OBEY to use XAC’s <<OBEY so that all obey work is audited.
Example:
COMMAND TACL-PROD
DESCRIPTION "PRODUCTION TACL"
USER PROD.OWNER
OBJECT $SYSTEM.SYSNN.TACL
ACL $OPERATORS
NULLNULLSTOP TRACKUSERID
ALIAS_ALL_PROCESSES
OPENSBYOBJECTS $*.*.*
ALIAS "OBEY" "<<OBEY"
ALIAS "O " "<<OBEY"
When TACL’s built-in OBEY is used instead of XAC’s <<OBEY, the contents of the
OBEY file are not audited. By using XAC’s ALIAS to map TACL’s O and OBEY to
XAC’s <<OBEY, the user of the TACL is given the XAC Obey functionality
transparently. The ALIAS_ALL_PROCESSES, ALIAS_OSS_PROCESSES,
ALIAS_XYGATEAC_PROCESSES keywords are used to cause the mapping to be
carried to all programs started within this XAC session, XOA session and the program
located in XAC installed subvolume, respectively.