XYGATE User Authentication Reference Manual

XYGATE
®
User Authentication
™
(XUA) 1.85 Reference Manual
Appendix A: The UACONF File
XYPRO Technology Corporation 236 Proprietary and Confidential
A54: PERUSE_OBJECT
The argument to the PERUSE_OBJECT keyword is the full program name of the
Peruse program you wish to have XUA “drop” you into when running reports. Sites that
use XYPRO’s combined SPOOLCOM and PERUSE program (XSP) will want to put
that object name here. Otherwise, put the NonStop server standard PERUSE here.
Syntax:
PERUSE_OBJECT <peruse object file name>
During installation, even if a user specifies a partially qualified Peruse object, XUA will
put a fully qualified entry in the UACONF file. During installation XUA will search for
$*.XYGATESP.PERUSE. If multiple files are found, the first one will be used.
If this keyword is omitted from the UACONF, the XUA_REPORT macro will use
PERUSE.
Examples:
PERUSE_OBJECT $SYSTEM.XYGATESP.PERUSE
PERUSE_OBJECT $SYSTEM.SYSTEM.PERUSE
A55: PHANDLE_MISMATCH_CHECK
This keyword is required as a workaround due to an anomaly in the protocol phandle
of Safeguard that identifies the process doing the logon. The UACONF file requires
that the PHANDLE_MISMATCH_CHECK be set to OFF to disable the Safeguard
code.
Syntax:
PHANDLE_MISMATCH_CHECK { ON | OFF }
Example:
PHANDLE_MISMATCH_CHECK OFF
The default value is OFF.