XSM: XSM_REPORT not showing an audit file name.

• Related Articles

• XAC:REPMAC example of rolling over the AUDIT file and generating yesterday's XAC audit report

  Below is a custom REPMAC file. The lines in blue are for customized activities. ?tacl macro #frame [#push t_t1 t_t2 t_t3 t_t4 ] XAC_datetime_make 1 == put date computed and time of 00:00 into t_t1 #set t_t1 [XAC_dt_year4]-[XAC_dt_month]-[XAC_dt_day] ...

• XMA: OSS path and file name from Safeguard audit not showing up in XMA database or on SIEM

  OSS commands, such as 'cat', generate an "open" operation for the OSS file on which they were executed. The Safeguard audit for "open" operations caused by 'cat' do not show the OSS path and file name in the ObjectName field of the Safeguard record. ...

• XSM GUI: Safeguard audit log shows super.super instead of actual user ID

  The XSM audit trail contains the UserID used to logon to the GUI. For example, XYPRO Support \NODE Blank Date produced: 05-JUL-2018 14:19 Page: 1 Criteria:2018-07-05 08:28 to 2018-07-05 08:33 File:$SYSTEM.XYGATESM.AUDIT YYYY-MM-DD HH:MM:SS Command IP ...

• XOS: Why am I seeing \UNKNOWN in the XOS Audit Report?

  Below are two possible reasons "\unknown" is seen in a XOS Audit Report for node name: A. When the EXPLICIT_NODES is OFF and you try to execute a FUP program on \one node to purge a file on another you see \UNKNOWN on the SUBJECT-SYSTEM field as ...

• XOS: Audit File Error 45 - Missing Sequence Numbers

  If a disk file name is specified for the AUDIT and no disk file exists, the file is created with the default format of type E, rec 4000, block 4096, primary extent size 300 pages, secondary extent size 300 pages and maxextents set to 16. When an ...