XUA_ROLL_AUDIT issue fix for XUA 2.30
The fix for this issue is as follows:
TACL>VOLUME <tacl-installation-loc>
The below must be entered at a TACL, exactly as below including the blank line:
EDIT TACLSRC ;F7320 ;E
]
LOAD/KEEP 1/TACLSRC
XUA_ROLL_AUDIT
the fix is to be done just once and should fix the issue from occurring again.
The below will reload the change into a TACL environment should the error occur again:
VOLUME <tacl-installation-loc>
LOAD/KEEP 1/TACLSRC
XUA_ROLL_AUDIT
If you are unable to locate the solution needed or if you need additional assistance please Click Here to open a case from our Customer Care Portal.
Related Articles
XMA: SFG mover abends when SFG audit files roll over too quickly
Check the following items regarding Safeguard Audit on your NonStop: Look at and change the size of Safeguard audit files Review the sources of data Review the size of data Review what is being audited by reviewing Safecom Globals and auditing lists ...
XUA: No XUA audit records have been found since an FSE 43 occurred.
After resolving the FSE 43, the XUA SEEP ($XUA) must be bounced to start auditing. Example: $SYSTEM XYGATEUA 4> XUA_SAFECOM_BOUNCE
XMA: XUA Mover abends when processing XUA protocol types
Solution: Upgrade to XMA 2.45 or other Cause: XMA 2.43 and older could not properly extract protocol from XUA audits The issue is addressed in XMA Version 2.45 * ITID 245-13395 Update to Extract protocol type from XYGATE User Authentication (XUA) ...
XUA: The audit file is not being updated
One of the most probable causes is how the Audit file is secured. Check for any error messages such as error 48 in EMS. The audit file should be secured so that the owner of the AUDIT is the installation owner with "NUUU".
How to resize XOS audit files
TACL> VOLUME $<VOLUME>.<XYGATEOS INSTALLATION SUBVOLUME> TACL> RUN XOS INSTALL TACL> EDIT OSCONF Edit the line AUDIT <FILENAME> EXT(<PRIMARY>, <SECONDARY>, <MAX EXTENTS>) (size of an audit trail can be controlled with the EXT option) eg: TACL> AUDIT ...